Bug 287364 - klipper crashed with the --waitforwm cmdline option
Summary: klipper crashed with the --waitforwm cmdline option
Status: RESOLVED WORKSFORME
Alias: None
Product: kdelibs
Classification: Frameworks and Libraries
Component: kdeui (show other bugs)
Version: 4.10.0
Platform: Ubuntu Linux
: NOR crash
Target Milestone: ---
Assignee: kdelibs bugs
URL:
Keywords:
: 240546 272926 315650 (view as bug list)
Depends on:
Blocks:
 
Reported: 2011-11-23 11:07 UTC by Christoph Thielecke
Modified: 2021-01-12 04:34 UTC (History)
6 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 Christoph Thielecke 2011-11-23 11:07:39 UTC
Application: klipper (v0.9.7)
KDE Platform Version: 4.7.2 (4.7.2)
Qt Version: 4.7.4
Operating System: Linux 3.0.0-13-generic-pae i686
Distribution: Ubuntu 11.10

-- Information about the crash:
I started klipper manually in console using the following command:
klipper --nofork --waitforwm

and it crashed.

-- Backtrace:
Application: Klipper (klipper), signal: Segmentation fault
[KCrash Handler]
#7  0xb7082270 in _XFreeEventCookies () from /usr/lib/i386-linux-gnu/libX11.so.6
#8  0xb707d5db in XWindowEvent () from /usr/lib/i386-linux-gnu/libX11.so.6
#9  0xb7362dbc in KApplicationPrivate::parseCommandLine (this=0x9f9d978) at ../../kdeui/kernel/kapplication.cpp:877
#10 0xb7365cc8 in KApplicationPrivate::init (this=0x9f9d978, GUIenabled=true) at ../../kdeui/kernel/kapplication.cpp:478
#11 0xb736697b in KApplication::KApplication (this=0xbffe7140, GUIenabled=true, cData=...) at ../../kdeui/kernel/kapplication.cpp:387
#12 0xb736c494 in KUniqueApplication::KUniqueApplication (this=0xbffe7140, GUIenabled=true, configUnique=false) at ../../kdeui/kernel/kuniqueapplication.cpp:314
#13 0xb777940c in kdemain (argc=3, argv=0xbffe7234) at ../../klipper/main.cpp:44
#14 0x0804850b in main (argc=3, argv=0xbffe7234) at klipper_dummy.cpp:3

Reported using DrKonqi
Comment 1 Jekyll Wu 2011-11-23 11:36:24 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.
Comment 2 Asen Lekov 2011-11-25 18:18:06 UTC
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 ()
Comment 3 Christoph Feck 2011-11-28 15:05:22 UTC
KApplication references atom_NetSupported in parseCommandLine() before it is initialized.
Comment 4 Christoph Feck 2011-11-28 15:09:31 UTC
*** Bug 272926 has been marked as a duplicate of this bug. ***
Comment 5 Christoph Feck 2011-11-28 15:11:08 UTC
*** Bug 240546 has been marked as a duplicate of this bug. ***
Comment 6 Christoph Feck 2011-12-20 03:42:39 UTC
If anyone can test the "--waitforwm" option, here is the patch that fixes the crash:

https://git.reviewboard.kde.org/r/103478/
Comment 7 Jekyll Wu 2011-12-20 18:32:27 UTC
The patch fixes the crash for me. No idea whether it causes regressions.
Comment 8 Christoph Feck 2013-02-22 21:33:42 UTC
*** Bug 315650 has been marked as a duplicate of this bug. ***
Comment 9 Justin Zobel 2020-12-13 02:32:06 UTC
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.
Comment 10 Bug Janitor Service 2020-12-28 04:34:39 UTC
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!
Comment 11 Bug Janitor Service 2021-01-12 04:34:15 UTC
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!