Summary: | klipper crashed with the --waitforwm cmdline option | ||
---|---|---|---|
Product: | [Unmaintained] kdelibs | Reporter: | Christoph Thielecke <crissi99> |
Component: | kdeui | Assignee: | kdelibs bugs <kdelibs-bugs> |
Status: | RESOLVED WORKSFORME | ||
Severity: | crash | CC: | asenlekoff, bug.correspondence, cfeck, death_jax, i_vohmin, justin.zobel |
Priority: | NOR | ||
Version: | 4.10.0 | ||
Target Milestone: | --- | ||
Platform: | Ubuntu | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
Christoph Thielecke
2011-11-23 11:07:39 UTC
I have always wonder the right usage of the --waitforwm option. In fact, it crashes almost every kde app I have tried when used in the form of "app --waitforwm". Also see bug 272926 and bug 171847. Can be reproduced! My KDE version is 7.4.2 -- Information about the crash: Following steps from discription -- Backtrace: Application: Klipper (klipper), signal: Segmentation fault [KCrash Handler] #7 0xb7184270 in _XFreeEventCookies () from /usr/lib/i386-linux-gnu/libX11.so.6 #8 0xb717f5db in XWindowEvent () from /usr/lib/i386-linux-gnu/libX11.so.6 #9 0xb7464dbc in ?? () from /usr/lib/libkdeui.so.5 #10 0xb7467cc8 in ?? () from /usr/lib/libkdeui.so.5 #11 0xb746897b in KApplication::KApplication(bool, KComponentData const&) () from /usr/lib/libkdeui.so.5 #12 0xb746e494 in KUniqueApplication::KUniqueApplication(bool, bool) () from /usr/lib/libkdeui.so.5 #13 0xb787a40c in kdemain () from /usr/lib/kde4/libkdeinit/libkdeinit4_klipper.so #14 0x0804850b in ?? () #15 0xb76d2113 in __libc_start_main () from /lib/i386-linux-gnu/libc.so.6 #16 0x08048531 in _start () KApplication references atom_NetSupported in parseCommandLine() before it is initialized. *** Bug 272926 has been marked as a duplicate of this bug. *** *** Bug 240546 has been marked as a duplicate of this bug. *** If anyone can test the "--waitforwm" option, here is the patch that fixes the crash: https://git.reviewboard.kde.org/r/103478/ The patch fixes the crash for me. No idea whether it causes regressions. *** Bug 315650 has been marked as a duplicate of this bug. *** Thank you for the crash reports. As it has been a while since this was reported, can you please test and confirm if this issue is still occurring or if this bug report can be marked as resolved. I have set the bug status to "needsinfo" pending your response, please change back to "reported" or "resolved/worksforme" when you respond, thank you. Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! |