[kde] [Bug 441871] New: Plasma starts without dock and with glitches half of the times

David bugzilla_noreply at kde.org
Wed Sep 1 16:51:58 BST 2021


https://bugs.kde.org/show_bug.cgi?id=441871

            Bug ID: 441871
           Summary: Plasma starts without dock and with glitches half of
                    the times
           Product: kde
           Version: unspecified
          Platform: Debian testing
                OS: Linux
            Status: REPORTED
          Severity: normal
          Priority: NOR
         Component: general
          Assignee: unassigned-bugs at kde.org
          Reporter: david.cortes.rivera at gmail.com
  Target Milestone: ---

Created attachment 141223
  --> https://bugs.kde.org/attachment.cgi?id=141223&action=edit
xsession_errors_log

SUMMARY
After an update to KDE plasma 5.21.5 and frameworks 5.83.0, now roughly half of
the times when I start a new session, it does not start latte dock and seems to
have graphical glitches when trying to restart it (takes longer than usual to
restart, and before restarting sticks with roughly 3/4 of the screen from top
to bottom being in black while the rest shows a normal desktop).

It takes a full system restart for the issue to go away (not just a plasma
session restart), and next time plasma starts, it will do so with compositing
disabled.

The xsession-errors file (attached) shows this message many times:
Errors:

[2594:2594:0901/114421.740314:ERROR:shared_context_state.cc(73)] Skia shader
compilation error

STEPS TO REPRODUCE
1. Restart computer, wait until it launches KDE plasma.

OBSERVED RESULT
Plasma starts with issues, latte dock is not shown, has glitches when trying to
restart the computer.

EXPECTED RESULT
Should start flawlessly.

REPRODUCIBLE
Roughly half of the times it starts.

SOFTWARE/OS VERSIONS
Windows: 
macOS: 
Linux/KDE Plasma: 
(available in About System)
KDE Plasma Version: 5.21.5
KDE Frameworks Version: 5.83.0
Qt Version: 5.15.2

ADDITIONAL INFORMATION

-- 
You are receiving this mail because:
You are the assignee for the bug.


More information about the Unassigned-bugs mailing list