Bug 345340 - Clicking Special Window/Application Settings in the window title bar context menu freezes kwin
Summary: Clicking Special Window/Application Settings in the window title bar context ...
Status: RESOLVED FIXED
Alias: None
Product: kwin
Classification: Plasma
Component: rules (show other bugs)
Version: git master
Platform: Other Linux
: NOR normal
Target Milestone: ---
Assignee: KWin default assignee
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-03-19 15:29 UTC by Eike Hein
Modified: 2021-03-10 00:35 UTC (History)
5 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Eike Hein 2015-03-19 15:29:31 UTC
kwin reproducably freezes when I click Special Window Settings or Special Application Settings in the window title bar context menu.

Reproducible: Always
Comment 1 Thomas Lübking 2015-03-19 17:38:22 UTC
Not here - actually nothing happens (I blame the SC4/KF5 crossmix to fail on "KToolInvocation::kdeinitExec()" to resolve "kwin_rules_dialog"

rules.cpp:991 RuleBook::edit(Client* c, bool whole_app)

can you check whether it blocks in "save();" or in KToolInvocation?
Latter is unlikely (should be fire and forget) and former would point the "everything freezes on KConfig invocation due to garbled cache files", but needs further investication (and is not blocking here for sure)
Comment 2 Martin Flöser 2015-03-20 07:11:24 UTC
neither here - I don't get a freeze, neither the dialog ad just a crash of kdeinit5 with useless backtrace.
Comment 3 Guido 2015-05-28 19:52:08 UTC
I can confirm the crash not the freeze
Comment 4 Simon Pfeifer 2015-06-08 22:50:17 UTC
I also can only confirm the crash not the freeze.

 //

Application: kdeinit5 (kdeinit5), signal: Segmentation fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f390caae780 (LWP 16129))]

Thread 2 (Thread 0x7f38f8c1d700 (LWP 16130)):
#0  0x00007f390b1ab8dd in poll () at ../sysdeps/unix/syscall-template.S:81
#1  0x00007f39096a2b72 in ?? () from /usr/lib/x86_64-linux-gnu/libxcb.so.1
#2  0x00007f39096a464f in xcb_wait_for_event () from /usr/lib/x86_64-linux-gnu/libxcb.so.1
#3  0x00007f38fb89d099 in ?? () from /usr/lib/x86_64-linux-gnu/qt5/plugins/platforms/libqxcb.so
#4  0x00007f390b51db0e in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x00007f3908df66aa in start_thread (arg=0x7f38f8c1d700) at pthread_create.c:333
#6  0x00007f390b1b6eed in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 1 (Thread 0x7f390caae780 (LWP 16129)):
[KCrash Handler]
#6  0x00007f39096a3304 in xcb_send_request () from /usr/lib/x86_64-linux-gnu/libxcb.so.1
#7  0x00007f39096a8269 in xcb_get_property () from /usr/lib/x86_64-linux-gnu/libxcb.so.1
#8  0x00007f390c16b470 in NETWinInfo::update(QFlags<NET::Property>, QFlags<NET::Property2>) () from /usr/lib/x86_64-linux-gnu/libKF5WindowSystem.so.5
#9  0x00007f38fb5c7443 in ?? () from /usr/lib/x86_64-linux-gnu/libkdeinit5_kwin_rules_dialog.so
#10 0x00007f38fb5a044f in kdemain () from /usr/lib/x86_64-linux-gnu/libkdeinit5_kwin_rules_dialog.so
#11 0x0000000000408716 in ?? ()
#12 0x000000000040a132 in ?? ()
#13 0x000000000040a6ee in ?? ()
#14 0x000000000040501b in main ()
Comment 5 Thomas Lübking 2015-06-09 08:13:06 UTC
That's embarrassingly not the same crash ;-)
-> bug #348472
Comment 6 EMR_Kde 2015-06-18 12:02:47 UTC
Just started happening when I upgrade F21 to F22 with KDE5
Comment 7 Thomas Lübking 2015-06-18 12:08:42 UTC
If you encounter a freeze, please move to VT2 (or ssh into the machine) and gdb attach to kwin:

$ echo 0 | sudo tee /proc/sys/kernel/yama/ptrace_scope # allow gdb to attach
$ gdb --pid `pidof kwin_x11` 2>&1 | tee kwin.gdb
> bt
[press enter until on the end of the stack]
> detach
> quit

and attach the backtrace here.
Comment 8 Justin Zobel 2021-03-10 00:32:25 UTC
Thank you for the bug report.

As this report hasn't seen any changes in 5 years or more, we ask if you can please confirm that the issue still persists.

If this bug is no longer persisting or relevant please change the status to resolved.