Bug 212472

Summary:	Klipper crashes if I click "disable popups"
Product:	[Unmaintained] klipper	Reporter:	Miro.Collas
Component:	general	Assignee:	Esben Mose Hansen <kde>
Status:	RESOLVED DUPLICATE
Severity:	crash	CC:	andresbajotierra, dimsuz
Priority:	NOR
Version First Reported In:	unspecified
Target Milestone:	---
Platform:	Ubuntu
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

Description Miro.Collas 2009-10-31 05:17:17 UTC

Version:            (using KDE 4.2.4)
OS:                Linux
Installed from:    Ubuntu Packages

Running on Linux Mint Gloria - KDE Community Edition

This backtrace appears to be of no use.
This is probably because your packages are built in a way which prevents creation of proper backtraces, or the stack frame was seriously corrupted in the crash.

(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 0xb645f700 (LWP 3683)]
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
0xb7f89430 in __kernel_vsyscall ()
[Current thread is 0 (process 3683)]

Thread 1 (Thread 0xb645f700 (LWP 3683)):
#0  0xb7f89430 in __kernel_vsyscall ()
#1  0xb6976780 in nanosleep () from /lib/tls/i686/cmov/libc.so.6
#2  0xb69765be in sleep () from /lib/tls/i686/cmov/libc.so.6
#3  0xb7e04d82 in ?? () from /usr/lib/libkdeui.so.5
#4  0xb7e05744 in KCrash::defaultCrashHandler () from /usr/lib/libkdeui.so.5
#5  <signal handler called>
#6  0xb726d6d2 in QMenu::findIdForAction () from /usr/lib/libQtGui.so.4
#7  0xb726eead in ?? () from /usr/lib/libQtGui.so.4
#8  0xb727576b in ?? () from /usr/lib/libQtGui.so.4
#9  0xb7276242 in QMenu::mouseReleaseEvent () from /usr/lib/libQtGui.so.4
#10 0xb7e7bf65 in KMenu::mouseReleaseEvent () from /usr/lib/libkdeui.so.5
#11 0xb6e50b43 in QWidget::event () from /usr/lib/libQtGui.so.4
#12 0xb7278629 in QMenu::event () from /usr/lib/libQtGui.so.4
#13 0xb6df9e9c in QApplicationPrivate::notify_helper () from /usr/lib/libQtGui.so.4
#14 0xb6e02b11 in QApplication::notify () from /usr/lib/libQtGui.so.4
#15 0xb7d94e0d in KApplication::notify () from /usr/lib/libkdeui.so.5
#16 0xb7846a3b in QCoreApplication::notifyInternal () from /usr/lib/libQtCore.so.4
#17 0xb6e01b7e in QApplicationPrivate::sendMouseEvent () from /usr/lib/libQtGui.so.4
#18 0xb6e71c06 in ?? () from /usr/lib/libQtGui.so.4
#19 0xb6e70ca7 in QApplication::x11ProcessEvent () from /usr/lib/libQtGui.so.4
#20 0xb6e9bc6a in ?? () from /usr/lib/libQtGui.so.4
#21 0xb66a6b88 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#22 0xb66aa0eb in ?? () from /usr/lib/libglib-2.0.so.0
#23 0xb66aa268 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0
#24 0xb7872438 in QEventDispatcherGlib::processEvents () from /usr/lib/libQtCore.so.4
#25 0xb6e9b365 in ?? () from /usr/lib/libQtGui.so.4
#26 0xb784506a in QEventLoop::processEvents () from /usr/lib/libQtCore.so.4
#27 0xb78454aa in QEventLoop::exec () from /usr/lib/libQtCore.so.4
#28 0xb7847959 in QCoreApplication::exec () from /usr/lib/libQtCore.so.4
#29 0xb6df9d17 in QApplication::exec () from /usr/lib/libQtGui.so.4
#30 0xb7f69291 in kdemain () from /usr/lib/libkdeinit4_klipper.so
#31 0x08048692 in _start ()
#0  0xb7f89430 in __kernel_vsyscall ()

Comment 1 Esben Mose Hansen 2009-10-31 08:20:02 UTC

I need some more information. What exactly did you do? Does it happen every time?

Comment 2 Miro.Collas 2009-10-31 08:25:43 UTC

OK, example. Copy a URL. Klipper opens. I don't want it to so I click "Disable popups". I get a message telling me how to re-enable, I click ok on that. Klipper crashes. Yes, every time.

Comment 3 Esben Mose Hansen 2009-10-31 10:46:25 UTC

Hm, not getting that here, but I do not have the exact version on hand. I'll live the report open and hope to catch a few more reports, so that we can narrow it down.

Comment 4 Dario Andres 2009-10-31 14:05:20 UTC

Isn't this the same as bug 185017 ( both backtrace and description are matching)
Thanks

Comment 5 Esben Mose Hansen 2009-10-31 16:54:44 UTC

Matches version and everything. Thank you Dario! Miro, it was fixed for 4.3, and the fix cannot be backported to 4.2. You might consider upgrading.

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

Comment 6 Miro.Collas 2009-10-31 18:51:03 UTC

Thanks for the rapid responses. I'll see how to update. :-)