Summary: | Plasma freezes from time to time on different occasions because of kwin_x11. | ||
---|---|---|---|
Product: | [Plasma] kwin | Reporter: | cameronpoe |
Component: | general | Assignee: | KWin default assignee <kwin-bugs-null> |
Status: | RESOLVED DUPLICATE | ||
Severity: | crash | CC: | bhush94, plasma-bugs, simonandric5 |
Priority: | NOR | ||
Version: | 5.4.3 | ||
Target Milestone: | --- | ||
Platform: | openSUSE | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: | |||
Attachments: | Freeze happened around 12:34 |
Description
cameronpoe
2016-01-04 19:01:56 UTC
It happened to my friend on a different laptop too. Created attachment 96457 [details]
Freeze happened around 12:34
My friend has ATI graphic card too.
I wrote mistake previously - cursor does move when Plasma freezes. Today it happened to me twice - both times when I tried opening Firefox and JDownloader2 at the same time. This time I logged in at tty1 and killed only one of those 2 kwin_x11 processes, then I went back to Plasma at tty7 and everything went normal (Plasma was unfreezed). Yesterday I start opening JDownloader2 and in a mean while I tried to open Dolphin and Plasma froze again instantly when Dolphin window pop up (JDowloader2 window did not appear jet). So I logged into tty1 and killed the other kwin_x11 of them 2 processes. This time when I came back to Plasma on tty7 it was still frozen so I had to kill the other kwin-x11 process as well and start a new one in Plasma, then it unfroze. This means only one of kwin_x11 processes is responsible for Plasma freeze. Unfortunately I can't remember which of them 2 was the buggy one (but I think the second one with higher ID number). It is not JDownloader2 fault because my friend doesn't have that program installed and still Plasma froze on his laptop when he had few default openSUSE Leap programs opened at the same time (Firefox, Dolphin and LibreOffice). Today when it happened I killed the first kwin_x11 with lower ID number and the Plasma unfroze on tty7 immediately. "So I logged into tty1 and killed the other kwin_x11 of them 2 processes. This time when I came back to Plasma on tty7 it was still frozen so I had to kill the other kwin-x11 process as well and start a new one in Plasma, then it unfroze. This means only one of kwin_x11 processes is responsible for Plasma freeze. Unfortunately I can't remember which of them 2 was the buggy one (but I think the second one with higher ID number)." Assuming bug #353428 - check whether one of the kwin processes is stopped and there's a drkonqi process holding it. The initial problem is the kwin crash, but we don't know for which reason it occurs. If you can, you can gdb into the stopped process and obtain a backtrace this way, getting us an idea why it crashed. *** This bug has been marked as a duplicate of bug 353428 *** (In reply to Thomas Lübking from comment #6) ...check whether one of the kwin processes is stopped... How do I do that in the tty1? (In reply to Thomas Lübking from comment #6) ...and there's a drkonqi process holding it... How do I check that exactly? (In reply to Thomas Lübking from comment #6) ...you can gdb into the stopped process and obtain a backtrace this way... How do I do that exactly step by step? This will list all kwin process, a drkonqi process holding kwin (and grep ;-) ps ax | grep kwin A stopped process will show a "T" in the status (sth. like "TN") where a running process would usually have an "S" ("SN") How to debug with gdb: https://community.kde.org/KWin/Debugging https://techbase.kde.org/Development/Tutorials/Debugging/Debugging_with_GDB |