Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#48052 - [kwin] UI freezes in plasma desktop at random when starting compose in Thunderbird

Attached to Project: Arch Linux
Opened by Mike Cloaked (mcloaked) - Friday, 05 February 2016, 22:08 GMT
Last edited by Antonio Rojas (arojas) - Saturday, 06 February 2016, 18:04 GMT
Task Type Bug Report
Category Upstream Bugs
Status Closed
Assigned To Antonio Rojas (arojas)
Felix Yan (felixonmars)
Architecture x86_64
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:

Occasionally when starting Thunderbird it takes longer than usual to start up and then when it does Thunderbird window has no normal decorations in the plasma desktop. Occasionally when Thunderbird appears to start normally then when starting a compose screen or replying to email, the compose window opens but without window decorations, and the desktop is largely frozen. All open programs appear stacked on the same screen, and all normal shortcuts fail attempts to move to a different virtual desktop. It is not possible to click between open programs, or to access the K menu.

Using Ctrl Alt Fx to move to a new VT is successful but returning to the graphical screen has the same symptoms as above.

If a spare area of the desktop is available it is possible to right click and access the "Leave" option to logout and log back in and this usually results in a normally behaving desktop again but closes all open programs in the process.

Sometimes it is possible to use the shortcut Alt-F2 to open krunner, and if so then issuing the command "kwin_x11 --replace" will repaint the screen and screen behaviour returns to normal without any loss of any running program.

Additional info:

This appears to be a kwin problem and has persisted through all versions of plasma from the initial 5 release. However this could be due to graphics rendering issues related to bugs in the qt5 packages, or mesa. The hardware on which this occurs on multiple machines for me all have Intel integrated graphics but with different graphics hardware versions. The hardware spans Ivybridge to Haswell processors with related onboard graphics.

* package version(s)

kwin 5.5.4-1

* config and/or log files etc.


Steps to reproduce:

Start Thunderbird and compose new mail or reply to existing mail. UI freezes.
This task depends upon

Closed by  Antonio Rojas (arojas)
Saturday, 06 February 2016, 18:04 GMT
Reason for closing:  Upstream
Comment by Mike Cloaked (mcloaked) - Friday, 05 February 2016, 22:23 GMT
Output of qdbus org.kde.KWin /KWin supportInformation
Comment by Antonio Rojas (arojas) - Friday, 05 February 2016, 23:23 GMT
please report this upstream, including a backtrace of the kwin crash
Comment by Mike Cloaked (mcloaked) - Saturday, 06 February 2016, 11:31 GMT
I have been trying to run gdb on kwin_x11 to get a backtrace, but after I unlock the security by doing "echo 0 | sudo tee /proc/sys/kernel/yama/ptrace_scope" so that gdb can access the ptrace then as soon as I run "gdb --pid=$(pidof kwin_x11)" then the entire desktop freezes and my only option is to reboot the machine (or isolate the graphical target and then return to it which means having to login again). Do you know of a way to get a backtrace for kwin_x11 that will continue through to a kwin crash so that I can record it? Once I can do that I will be happy to report upstream.
Comment by Mike Cloaked (mcloaked) - Saturday, 06 February 2016, 11:35 GMT
I think I have realised that trying to run gdb from a terminal on the plasma desktop is stopping the kwin process! So I suppose it has to be done from an ssh session or another VT.... once I have succeeded in doing that I will report upstream.
Comment by Mike Cloaked (mcloaked) - Saturday, 06 February 2016, 12:12 GMT
Using ssh to run gdb worked - upstream report at https://bugs.kde.org/show_bug.cgi?id=359064
Comment by Mike Cloaked (mcloaked) - Saturday, 06 February 2016, 13:12 GMT
OK my bug upstream is now linked to https://bugs.kde.org/show_bug.cgi?id=351839 and it seems is not fully resolved though might be solved with QT 5.6 - but in the meantime specifically changing to breeze window decorations I will test to see if this stops this crash occurring.

i.e. Settings -> Application Style -> Window Decorations - choose Breeze

Edit: Testing with the breeze window decorations has for several hours not produced a crash. So the workaround seems to have been successful.
Comment by Antonio Rojas (arojas) - Saturday, 06 February 2016, 18:04 GMT
ok thanks. Closing this as there's nothing we can do but wait for Qt 5.6

Loading...