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

            Bug ID: 373697
           Summary: plasma panel freezes (typically after opening kwallet)
           Product: plasmashell
           Version: 5.8.4
          Platform: Debian unstable
                OS: Linux
            Status: UNCONFIRMED
          Severity: normal
          Priority: NOR
         Component: Panel
          Assignee: plasma-b...@kde.org
          Reporter: stefan.schwar...@gmx.net
  Target Milestone: 1.0

I am following debian testing. In the course of a system update I have recently
pulled in a change in the kde or an underlying component that causes the plasma
panel (only the panel) to lock up (become unrespsonsive to mouse clicks, clock
and animated icons (nm) do not update). I 'updated' to unstable with caused the
freeze to become more systematic. Typical packet versions: ibkf5plasma5 at
5.28.0, plasma components (-nm, -desktop, ...) at 5.8.4. Kernel is 4.8.11, Qt
5.7.1~20161021, intel graphics. I observe similar freezes currently also at
home on a PC with AMD/Radeon graphics. Freezes do not seem to depend on
compositing. I went from GL 3.1 to Xrender without changing the behavior
noticably. I cannot identify anything in journalctl, .xsession-errors, dmesg
and the like. 

Symptoms: sddm comes up, login, animated splash screen comes up, then animation
stops. Switching virtual console CTL-ALT-F1 and back to CTL-ALT-F7 gets rid of
the splash screen and exposes the desktop. At this point, the panel seems to
live (reacts to the mouse). Kwallet asks me for login info, after closing, the
panel is frozen. This has happened three times in a row which makes me
confident that I should be able to reproduce the problem. Before going to
'unstable', freezes occured at random times during work. Some applications
(Mathematica) would then freeze with the panel, then get unlocked after the
'killall plasmashell, plasmashell &' spell from a terminal.

I could help debugging (a little) if you tell me what to watch out for...

TIA, Stefan

-- 
You are receiving this mail because:
You are watching all bug changes.

Reply via email to