Bug 339562

Summary: Main thread(?) locked (in Plasma Next session)
Product: [Applications] amarok Reporter: Kyrylo Bohdanenko <kirill.bogdanenko>
Component: generalAssignee: KWin default assignee <kwin-bugs-null>
Status: RESOLVED DUPLICATE    
Severity: crash CC: cfeck
Priority: NOR    
Version: unspecified   
Target Milestone: ---   
Platform: Kubuntu   
OS: Linux   
See Also: https://bugs.kde.org/show_bug.cgi?id=338999
Latest Commit: Version Fixed In:
Sentry Crash Report:
Attachments: Amarok GUI freeze
KWin support information (compositioning enabled)
Here is what happens when resizing window with frozen GUI

Description Kyrylo Bohdanenko 2014-10-01 09:06:10 UTC
Sometimes it happens that application interface does not respond (graphically) to any user input. Also application interface does not redraw itself (i.e. window contents look like a static PNG image). And the bad thing is: screen locker can freeze too.

Sometimes it helps to press Alt+Tab hotkey to unfreeze the application GUI (task switching using mouse poiter does not help).

Reproducible: Sometimes

Steps to Reproduce:
1. Just do regular suff with you KF5 + Plasma5 installation

Actual Results:  
Some applications GUI (window contents) might randomly freeze

Expected Results:  
Applications' interface should not freeze

I am using Intel HD (Sandy Bridge) graphics card and X11 (1.16) and mesa 10.3.0 on top of Kubuntu Utopic (14.10) x86_64.

Though I am not really sure it's bug of kwin, but I do not know which component is exactly responsible for this bug.

If you need more additional inforation please do not hezitate to ask.
Comment 1 Kyrylo Bohdanenko 2014-10-01 09:11:52 UTC
Created attachment 88911 [details]
Amarok GUI  freeze

Here is a video, demonstrating a bug. You can see that Amarok gui does not respond to any actions (e.g. mouse hover and click events). Window header (decoration) is still responsive.

The bug can happen to any application on my desktop.
Comment 2 Christoph Feck 2014-10-01 16:48:45 UTC
Can you confirm that this never happens with compositing disabled (Ctrl+Shift+F12)?
Comment 3 Kyrylo Bohdanenko 2014-10-01 17:38:01 UTC
Eventually Ctrl+Shift+F12 hotkey does not work here... But looks like GUI does not freeze with compositioning disabled.

BTW I use OpenGL 2.0 with GLX interface
Comment 4 Thomas Lübking 2014-10-01 17:55:46 UTC
Most likely big or related to bug #338999 (thoug it refers to a general freeze)

intel (though ironlake there) + mesa 10.3 + GL 2.1 

This one here's interesting since either we do no longer receive damage events for the window or the texture got unhooked or the internal damage area is polluted.

Please:
- attach the output of "qdbus org.kde.KWin /KWin supportInformation" (w/ compositing enabled)
- check what happens when you resize such window (window borders or alt+rmb doesn't matter - even un/maximization should do)
Comment 5 Kyrylo Bohdanenko 2014-10-01 19:20:22 UTC
Created attachment 88920 [details]
KWin support information (compositioning enabled)

Here is Kwin support information
Comment 6 Kyrylo Bohdanenko 2014-10-01 19:22:48 UTC
Created attachment 88921 [details]
Here is what happens when resizing window with frozen GUI

Here's screen capture, when resizing frozen GUI.

Amarok again :)
Comment 7 Thomas Lübking 2014-10-01 19:48:09 UTC
Amarok doesn't respond to the sync request - the process seems actually frozen.

Since it's apparently compositing related:
1. you're actually using OpenGL 3.0 - try falling back to 2.1
2. you're likely also using glamor? (grep -i glamor /var/log/Xorg.0.log)
    -> set the acceleration method to "sna" in case
3. can you pot. gdb into amarok and dump backtraces of each thread when this happens? (See https://sourceware.org/gdb/current/onlinedocs/gdb/Threads.html for a gdb+threads crash course)
Comment 8 Kyrylo Bohdanenko 2014-10-10 12:01:45 UTC
Hi Thomas,

I have investigated the issue a little bit (though not used gdb on Amarok). And here are the results:

1) To no avail
2) grep -i glamor /var/log/Xorg.0.log
[    17.801] (WW) "glamoregl" will not be loaded unless you've specified it to be loaded elsewhere.
3) n/a

Though in the case, which is filmed on this video -- it was Amarok which freezed. It stopped playing (and working) right after the song finished. Can you please re-assign this bug to Amarok developers?

Also I have faced bug #338999 too.
Comment 9 Myriam Schweingruber 2015-04-18 16:06:27 UTC
We would need a backtrace for Amarok...
Comment 10 Kyrylo Bohdanenko 2015-04-19 19:11:56 UTC
Hi, I can no longer reproduce this bug. I guess this was related to https://bugs.kde.org/show_bug.cgi?id=338999 and the workaround
> export KWIN_USE_BUFFER_AGE=0
did helped me.
Comment 11 Thomas Lübking 2015-04-19 19:38:53 UTC

*** This bug has been marked as a duplicate of bug 338999 ***