Bug 357536 - Plasma freezes from time to time on different occasions because of kwin_x11.
Summary: Plasma freezes from time to time on different occasions because of kwin_x11.
Status: RESOLVED DUPLICATE of bug 353428
Alias: None
Product: kwin
Classification: Plasma
Component: general (show other bugs)
Version: 5.4.3
Platform: openSUSE Linux
: NOR crash
Target Milestone: ---
Assignee: KWin default assignee
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-01-04 19:01 UTC by cameronpoe
Modified: 2016-01-14 15:04 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments
Freeze happened around 12:34 (117.92 KB, application/octet-stream)
2016-01-04 19:06 UTC, cameronpoe
Details

Note You need to log in before you can comment on or make changes to this bug.
Description cameronpoe 2016-01-04 19:01:56 UTC
It happens when I want to open some window or program or menu... Plasma totally freezes and I can't do anything (CTRL + ESC not working, CTRL + SHIFT + ESC not working, cursor not moving) except I can only change to text screen to tty1 (left ALT + CTRL + F1), log in and then I check and see there are 2 kwin_x11 processes (ps -e | grep kwin_x11) so I force kill them (kill -s kill ID), then I go back to tty7 (left ALT + CTRL + F7) and open krunner (left ALT + F2), type in and start new kwin+x11 and everything goes back to normal (Plasma unfreezes). I am using newest openSUSE Leap 42.1 with the newest updates up today. I have ATI graphic card in my laptop with radeon drivers. I send an attachment with system journal and the freeze happened around 12:34.

Reproducible: Sometimes

Steps to Reproduce:
1. Sometimes opening window or program or menu...
2. 
3.

Actual Results:  
Plasma totally freezes.

Expected Results:  
Should not freeze and window or program or menu should open.
Comment 1 cameronpoe 2016-01-04 19:03:16 UTC
It happened to my friend on a different laptop too.
Comment 2 cameronpoe 2016-01-04 19:06:54 UTC
Created attachment 96457 [details]
Freeze happened around 12:34

My friend has ATI graphic card too.
Comment 3 cameronpoe 2016-01-06 13:09:31 UTC
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).
Comment 4 cameronpoe 2016-01-09 12:10:27 UTC
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).
Comment 5 cameronpoe 2016-01-13 11:29:31 UTC
Today when it happened I killed the first kwin_x11 with lower ID number and the Plasma unfroze on tty7 immediately.
Comment 6 Thomas Lübking 2016-01-14 10:52:53 UTC
"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 ***
Comment 7 cameronpoe 2016-01-14 13:04:40 UTC
(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?
Comment 8 Thomas Lübking 2016-01-14 15:04:37 UTC
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