Version: (using KDE 4.0.83) Installed from: Debian testing/unstable Packages OS: Linux When copying a link, I got the klipper pop-up. There I selected, "Open with Firefox". And boom, klipper crashed.
Application: Klipper (klipper), signal SIGSEGV Using host libthread_db library "/lib/i686/cmov/libthread_db.so.1". [Thread debugging using libthread_db enabled] [New Thread 0xb65e5720 (LWP 4543)] [New Thread 0xb49d6b90 (LWP 6998)] [KCrash handler] #6 URLGrabber::slotItemSelected (this=0x8544e48, action=0x85dcd98) at /usr/include/qt4/QtGui/qwidget.h:474 #7 0xb7ef782c in URLGrabber::qt_metacall (this=0x8544e48, _c=QMetaObject::InvokeMetaMethod, _id=3, _a=0xbff3de9c) at /tmp/buildd/kdebase-workspace-4.0.84/obj-i486-linux-gnu/klipper/urlgrabber.moc:78 #8 0xb71b7090 in QMetaObject::activate (sender=0x85d7650, from_signal_index=29, to_signal_index=29, argv=0xbff3de9c) at kernel/qobject.cpp:3010 #9 0xb71b7e12 in QMetaObject::activate (sender=0x85d7650, m=0xb7d782a8, local_signal_index=2, argv=0xbff3de9c) at kernel/qobject.cpp:3080 #10 0xb799d853 in QMenu::triggered (this=0x85d7650, _t1=0x85dcd98) at .moc/release-shared/moc_qmenu.cpp:156 #11 0xb799eceb in QMenuPrivate::_q_actionTriggered (this=0x8812058) at widgets/qmenu.cpp:1068 #12 0xb79a7946 in QMenu::qt_metacall (this=0x85d7650, _c=QMetaObject::InvokeMetaMethod, _id=8, _a=0xbff3e01c) at .moc/release-shared/moc_qmenu.cpp:98 #13 0xb6fa0b3a in KMenu::qt_metacall (this=0x85d7650, _c=QMetaObject::InvokeMetaMethod, _id=35, _a=0xbff3e01c) at /tmp/buildd/kde4libs-4.0.84/obj-i486-linux-gnu/kdeui/kmenu.moc:69 #14 0xb71b7090 in QMetaObject::activate (sender=0x85dcd98, from_signal_index=5, to_signal_index=6, argv=0xbff3e01c) at kernel/qobject.cpp:3010 #15 0xb71b7490 in QMetaObject::activate (sender=0x85dcd98, m=0xb7d725b8, from_local_signal_index=1, to_local_signal_index=2, argv=0xbff3e01c) at kernel/qobject.cpp:3100 #16 0xb75d23d1 in QAction::triggered (this=0x85dcd98, _t1=false) at .moc/release-shared/moc_qaction.cpp:216 #17 0xb75d2d3f in QAction::activate (this=0x85dcd98, event=QAction::Trigger) at kernel/qaction.cpp:1119 #18 0xb79a5164 in QMenuPrivate::activateAction (this=0x8812058, action=0x85dcd98, action_e=QAction::Trigger, self=true) at widgets/qmenu.cpp:1005 #19 0xb79a5c12 in QMenu::mouseReleaseEvent (this=0x85d7650, e=0xbff3e7cc) at widgets/qmenu.cpp:2160 #20 0xb6f9f475 in KMenu::mouseReleaseEvent (this=0x85d7650, e=0xbff3e7cc) at /tmp/buildd/kde4libs-4.0.84/kdeui/widgets/kmenu.cpp:452 #21 0xb76304f2 in QWidget::event (this=0x85d7650, event=0xbff3e7cc) at kernel/qwidget.cpp:6927 #22 0xb79a7e69 in QMenu::event (this=0x85d7650, e=0xbff3e7cc) at widgets/qmenu.cpp:2256 #23 0xb75d866c in QApplicationPrivate::notify_helper (this=0x84d2068, receiver=0x85d7650, e=0xbff3e7cc) at kernel/qapplication.cpp:3772 #24 0xb75e0df1 in QApplication::notify (this=0xbff3ef78, receiver=0x85d7650, e=0xbff3e7cc) at kernel/qapplication.cpp:3501 #25 0xb6ecdc8d in KApplication::notify (this=0xbff3ef78, receiver=0x85d7650, event=0xbff3e7cc) at /tmp/buildd/kde4libs-4.0.84/kdeui/kernel/kapplication.cpp:311 #26 0xb71a2541 in QCoreApplication::notifyInternal (this=0xbff3ef78, receiver=0x85d7650, event=0xbff3e7cc) at kernel/qcoreapplication.cpp:587 #27 0xb75e007e in QApplicationPrivate::sendMouseEvent (receiver=0x85d7650, event=0xbff3e7cc, alienWidget=0x0, nativeWidget=0x85d7650, buttonDown=0xb7d8e7d0, lastMouseReceiver=@0xb7d8e7d4) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:218 #28 0xb7649847 in QETWidget::translateMouseEvent (this=0x85d7650, event=0xbff3ecbc) at kernel/qapplication_x11.cpp:4067 #29 0xb76483cf in QApplication::x11ProcessEvent (this=0xbff3ef78, event=0xbff3ecbc) at kernel/qapplication_x11.cpp:3255 #30 0xb7671d14 in x11EventSourceDispatch (s=0x84d4ce8, callback=0, user_data=0x0) at kernel/qguieventdispatcher_glib.cpp:148 #31 0xb69c2978 in IA__g_main_context_dispatch (context=0x84d3c98) at /build/buildd/glib2.0-2.16.3/glib/gmain.c:2009 #32 0xb69c5bce in g_main_context_iterate (context=0x84d3c98, block=1, dispatch=1, self=0x84d21f0) at /build/buildd/glib2.0-2.16.3/glib/gmain.c:2642 #33 0xb69c611c in IA__g_main_context_iteration (context=0x84d3c98, may_block=1) at /build/buildd/glib2.0-2.16.3/glib/gmain.c:2705 #34 0xb71ccb48 in QEventDispatcherGlib::processEvents (this=0x84ccb10, flags= {i = -1074532760}) at kernel/qeventdispatcher_glib.cpp:325 #35 0xb7671415 in QGuiEventDispatcherGlib::processEvents (this=0x84ccb10, flags={i = -1074532712}) at kernel/qguieventdispatcher_glib.cpp:204 #36 0xb71a0c2a in QEventLoop::processEvents (this=0xbff3ef10, flags= {i = -1074532648}) at kernel/qeventloop.cpp:149 #37 0xb71a0dea in QEventLoop::exec (this=0xbff3ef10, flags={i = -1074532584}) at kernel/qeventloop.cpp:200 #38 0xb71a3495 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:845 #39 0xb75d84e7 in QApplication::exec () at kernel/qapplication.cpp:3304 #40 0xb7f042e1 in kdemain (argc=1, argv=0xbff3f054) at /tmp/buildd/kdebase-workspace-4.0.84/klipper/main.cpp:48 #41 0x08048592 in main (argc=0, argv=0x0) at /tmp/buildd/kdebase-workspace-4.0.84/obj-i486-linux-gnu/klipper/klipper_dummy.cpp:3 #42 0xb7da7450 in __libc_start_main () from /lib/i686/cmov/libc.so.6 #43 0x080484d1 in _start () #0 0xb7f25424 in __kernel_vsyscall ()
This is a duplicate of http://bugs.kde.org/show_bug.cgi?id=165133, I guess.
Created attachment 26006 [details] Backtrace I have the same problem with Klipper v0.9.7 (KDE 4.00.85 (KDE 4.0.85 (KDE 4.1 >= 20080703) "release 3.3", KDE:KDE4:Factory:Desktop / openSUSE_11.0). After restarting Klipper it works and is no longer reproducable within the same session, but now it does not do anything on "Open with Firefox" when copying an URL. It cannot be always reliably reproduced. Backtrace attached.
Created attachment 26120 [details] Klipper crash backtrace Additional instance of klipper crash
Same behaviour, slightly different kcrash report, attached. Klipper v0.9.7 in KDE 4.0.3 from package 4:4.0.3-0ubuntu2 on kernel 2.6.24-19-386, Firefox version 3.0, for what it's worth. Please note that Klipper/KDE3 v0.9.7 (Using KDE 3.5.9), to quote the About page, functions correctly in KDE 4.0.3.
Created attachment 26178 [details] Apparantly the same stacktrace as reported - now with debug symbols I can reproduce this crash now quite well: - I removed the klipperrc in my home directory to get a configuration from scratch - In a mail in KMail with some URL I choose "Copy Link Address" - Klipper offers a popup menu with atcions - I choose "Open with Firefox" It takes a while to open Firefox, but the Klipper action menu remains still open. - I choose "Open with Firefox" again from the same menu. - Klipper crashes with the stacktrace I attached here. Used environment: - OpenSUSE 11.0 - KDE 4.1 RC1 from the OpenSUSE KDE4 Desktop Factory repository kdebase4-workspace-4.0.98-12.1 kdebase4-workspace-debuginfo-4.0.98-12.1
Same behaviour in kubuntu 8.04 (v0.9.7 (KDE 4.1.00 (KDE 4.1.0), Kubuntu packages)): "Open with Mozilla" or "Open with Firefox" crashes klipper Приложение: Klipper (klipper), сигнал SIGSEGV [Thread debugging using libthread_db enabled] [New Thread 0xb6626720 (LWP 19284)] [New Thread 0xb4a7ab90 (LWP 21893)] [KCrash handler] #6 URLGrabber::execute (this=0x8106f38, command=0x6) at /build/buildd/kdebase-workspace-4.1.0/klipper/urlgrabber.cpp:250 #7 0xb7f195f6 in URLGrabber::slotItemSelected (this=0x8106f38, action=0x8187060) at /build/buildd/kdebase-workspace-4.1.0/klipper/urlgrabber.cpp:242 #8 0xb7f1a115 in URLGrabber::qt_metacall (this=0x8106f38, _c=QMetaObject::InvokeMetaMethod, _id=3, _a=0xbfea8edc) at /build/buildd/kdebase-workspace-4.1.0/obj-i486-linux-gnu/klipper/urlgrabber.moc:78 #9 0xb7ae44f9 in QMetaObject::activate () from /usr/lib/libQtCore.so.4 #10 0xb7ae4bc2 in QMetaObject::activate () from /usr/lib/libQtCore.so.4 #11 0xb7484db3 in QMenu::triggered () from /usr/lib/libQtGui.so.4 #12 0xb7485f9b in ?? () from /usr/lib/libQtGui.so.4 #13 0xb748b223 in QMenu::qt_metacall () from /usr/lib/libQtGui.so.4 #14 0xb6ec738a in KMenu::qt_metacall (this=0x82bd210, _c=QMetaObject::InvokeMetaMethod, _id=35, _a=0xbfea905c) at /build/buildd/kde4libs-4.1.0/obj-i486-linux-gnu/kdeui/kmenu.moc:69 #15 0xb7ae44f9 in QMetaObject::activate () from /usr/lib/libQtCore.so.4 #16 0xb7ae4930 in QMetaObject::activate () from /usr/lib/libQtCore.so.4 #17 0xb70b0dd1 in QAction::triggered () from /usr/lib/libQtGui.so.4 #18 0xb70b179f in QAction::activate () from /usr/lib/libQtGui.so.4 #19 0xb748ced1 in ?? () from /usr/lib/libQtGui.so.4 #20 0xb748f734 in QMenu::mouseReleaseEvent () from /usr/lib/libQtGui.so.4 #21 0xb6ec7059 in KMenu::mouseReleaseEvent (this=0x82bd210, e=0xbfea979c) at /build/buildd/kde4libs-4.1.0/kdeui/widgets/kmenu.cpp:452 #22 0xb710f4a4 in QWidget::event () from /usr/lib/libQtGui.so.4 #23 0xb748a845 in QMenu::event () from /usr/lib/libQtGui.so.4 #24 0xb70b7c0c in QApplicationPrivate::notify_helper () from /usr/lib/libQtGui.so.4 #25 0xb70bccd5 in QApplication::notify () from /usr/lib/libQtGui.so.4 #26 0xb6e0cef3 in KApplication::notify (this=0xbfea9f64, receiver=0x82bd210, event=0xbfea979c) at /build/buildd/kde4libs-4.1.0/kdeui/kernel/kapplication.cpp:311 #27 0xb7acf6a9 in QCoreApplication::notifyInternal () from /usr/lib/libQtCore.so.4 #28 0xb70b9e21 in QApplicationPrivate::sendMouseEvent () from /usr/lib/libQtGui.so.4 #29 0xb7123f0c in ?? () from /usr/lib/libQtGui.so.4 #30 0xb71226b1 in QApplication::x11ProcessEvent () from /usr/lib/libQtGui.so.4 #31 0xb714b3ba in ?? () from /usr/lib/libQtGui.so.4 #32 0xb6935dd6 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0 #33 0xb6939193 in ?? () from /usr/lib/libglib-2.0.so.0 #34 0xb693974e in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #35 0xb7afaf98 in QEventDispatcherGlib::processEvents () from /usr/lib/libQtCore.so.4 #36 0xb714b1b5 in ?? () from /usr/lib/libQtGui.so.4 #37 0xb7ace92d in QEventLoop::processEvents () from /usr/lib/libQtCore.so.4 #38 0xb7aceabd in QEventLoop::exec () from /usr/lib/libQtCore.so.4 #39 0xb7ad0d3d in QCoreApplication::exec () from /usr/lib/libQtCore.so.4 #40 0xb70b7567 in QApplication::exec () from /usr/lib/libQtGui.so.4 #41 0xb7f2774a in kdemain (argc=1, argv=0xbfeaa044) at /build/buildd/kdebase-workspace-4.1.0/klipper/main.cpp:48 #42 0x08048582 in main (argc=0, argv=0x81f2748) at /build/buildd/kdebase-workspace-4.1.0/obj-i486-linux-gnu/klipper/klipper_dummy.cpp:3 #0 0xb7f2f410 in __kernel_vsyscall ()
Latest news: The problem still exists in KDE 4.1.0 and latest upstream packages toward 4.1.1 / Qt 4.4.1. To remember: The problem occurs when the action is called twice from the same Klipper action popup menu, which isn't automatically closed after "clicking" on the "Open with Firefox" action. May the problem can be prevented by immediately closing the menu after clicking an action.
same problem with me, except one difference: klipper also crashes if it stays open and no second click will be made.
Created attachment 27669 [details] Backtrace of klipper crash in KDE 4.1.2 Confirm the bug still exists in KDE 4.1.2, when clicking the actions popup twice (it doesn't disappear after the first click). Version v0.9.7 Using KDE 4.1.2 "release 44.2" openSUSE 11.0 x86
On my system (kubuntu 8.04 with KDE 4.1.2), the Action associated with URLs includes an option to open with Firefox: ps x |grep -q '[f]irefox' && firefox -remote openURL(%s, new-window) || firefox %s Running this on the command line and substituting %s as appropriate, I get an error due to incorrect escaping: bash: syntax error near unexpected token `(' I've adjusted the action by adding extra quotes: ps x |grep -q '[f]irefox' && firefox -remote 'openURL(%s, new-window)' || firefox %s Now the "Open with Firefox" action works as expected. However, before I made this change, using the action would cause klipper to crash. Therefore, the code which handles the child process may have an error. Does it core if the shell exits unexpectedly (in this case with a return value of 258)?
I get the same crash as above with Klipper. Running version v0.9.7 with KDE 4.1.2 on Kubuntu Hardy Heron.
This happened to me with gentoo kde 4.1.2 klipper and still happens with gentoo 4.1.3 klipper. My gcc is 4.3.2 my system an amd 64
I can confirm this bug (running Klipper, Kmail in a gnome desktop environment) Anwendung: Klipper (klipper), Signal SIGSEGV (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)http://www.imakenews.com/ciscona-emeaenglish/index000319994.cfm?x=bdMH94Q,b7MRTyLQ (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 0x7fd5d79db6f0 (LWP 17925)] [New Thread 0x41ae7950 (LWP 17956)] (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) [KCrash handler] #5 0x00007fd5d75d7dbb in ?? () from /usr/lib/kde4/lib/libkdeinit4_klipper.so #6 0x00007fd5d75d819b in ?? () from /usr/lib/kde4/lib/libkdeinit4_klipper.so #7 0x00007fd5d75d8a87 in ?? () from /usr/lib/kde4/lib/libkdeinit4_klipper.so #8 0x00007fd5d6b508b6 in QMetaObject::activate () from /usr/lib/libQtCore.so.4 #9 0x00007fd5d60dc8a2 in QMenu::triggered () from /usr/lib/libQtGui.so.4 #10 0x00007fd5d60dd46e in ?? () from /usr/lib/libQtGui.so.4 #11 0x00007fd5d60e29ee in QMenu::qt_metacall () from /usr/lib/libQtGui.so.4 #12 0x00007fd5d5644925 in KMenu::qt_metacall () from /usr/lib/kde4/lib/libkdeui.so.5 #13 0x00007fd5d6b508b6 in QMetaObject::activate () from /usr/lib/libQtCore.so.4 #14 0x00007fd5d5d48527 in QAction::triggered () from /usr/lib/libQtGui.so.4 #15 0x00007fd5d5d48d30 in QAction::activate () from /usr/lib/libQtGui.so.4 #16 0x00007fd5d60e42ea in ?? () from /usr/lib/libQtGui.so.4 #17 0x00007fd5d56445c5 in KMenu::mouseReleaseEvent () from /usr/lib/kde4/lib/libkdeui.so.5 #18 0x00007fd5d5d9bf50 in QWidget::event () from /usr/lib/libQtGui.so.4 #19 0x00007fd5d60e2061 in QMenu::event () from /usr/lib/libQtGui.so.4 #20 0x00007fd5d5d4eacf in QApplicationPrivate::notify_helper () from /usr/lib/libQtGui.so.4 #21 0x00007fd5d5d50e89 in QApplication::notify () from /usr/lib/libQtGui.so.4 #22 0x00007fd5d55a61f1 in KApplication::notify () from /usr/lib/kde4/lib/libkdeui.so.5 #23 0x00007fd5d6b3c6b9 in QCoreApplication::notifyInternal () from /usr/lib/libQtCore.so.4 #24 0x00007fd5d5d54325 in QApplicationPrivate::sendMouseEvent () from /usr/lib/libQtGui.so.4 #25 0x00007fd5d5db337b in ?? () from /usr/lib/libQtGui.so.4 #26 0x00007fd5d5db20ab in QApplication::x11ProcessEvent () from /usr/lib/libQtGui.so.4 #27 0x00007fd5d5dd83d3 in ?? () from /usr/lib/libQtGui.so.4 #28 0x00007fd5d406f364 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0 #29 0x00007fd5d4072675 in ?? () from /usr/lib/libglib-2.0.so.0 #30 0x00007fd5d4072b5b in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #31 0x00007fd5d6b659df in QEventDispatcherGlib::processEvents () from /usr/lib/libQtCore.so.4 #32 0x00007fd5d5dd820f in ?? () from /usr/lib/libQtGui.so.4 #33 0x00007fd5d6b3bb35 in QEventLoop::processEvents () from /usr/lib/libQtCore.so.4 #34 0x00007fd5d6b3bc8b in QEventLoop::exec () from /usr/lib/libQtCore.so.4 #35 0x00007fd5d6b3dcd9 in QCoreApplication::exec () from /usr/lib/libQtCore.so.4 #36 0x00007fd5d75e3c08 in kdemain () from /usr/lib/kde4/lib/libkdeinit4_klipper.so #37 0x00007fd5d727a1c4 in __libc_start_main () from /lib/libc.so.6 #38 0x0000000000400649 in _start () #0 0x00007fd5d72f9b81 in nanosleep () from /lib/libc.so.6
I confirm this on kde-4.2 beta2(4.1.85). Backtrace is as below: Application: Klipper (klipper), signal SIGSEGV [?1034h[Thread debugging using libthread_db enabled] [Current thread is 0 (LWP 3488)] Thread 2 (Thread 0xb4c66b90 (LWP 4867)): #0 0xffffe430 in __kernel_vsyscall () #1 0xb6be5ef1 in select () from /lib/libc.so.6 #2 0xb7985e77 in QProcessManager::run (this=0x8068800) at io/qprocess_unix.cpp:301 #3 0xb78b684e in QThreadPrivate::start (arg=0x8068800) at thread/qthread_unix.cpp:185 #4 0xb7856175 in start_thread () from /lib/libpthread.so.0 #5 0xb6becdce in clone () from /lib/libc.so.6 Thread 1 (Thread 0xb675aad0 (LWP 3488)): [KCrash Handler] #6 URLGrabber::execute (this=0x818b7b0, command=0x6) at /usr/src/debug/kdebase-workspace-4.1.85/klipper/urlgrabber.cpp:250 #7 0xb80738ba in URLGrabber::slotItemSelected (this=0x818b7b0, action=0x8197748) at /usr/src/debug/kdebase-workspace-4.1.85/klipper/urlgrabber.cpp:242 #8 0xb80743bc in URLGrabber::qt_metacall (this=0x818b7b0, _c=QMetaObject::InvokeMetaMethod, _id=3, _a=0xbfcbfbec) at /usr/src/debug/kdebase-workspace-4.1.85/build/klipper/urlgrabber.moc:78 #9 0xb79bb740 in QMetaObject::activate (sender=0x81b4f58, from_signal_index=29, to_signal_index=29, argv=0xbfcbfbec) at kernel/qobject.cpp:3031 #10 0xb79bc4c2 in QMetaObject::activate (sender=0x81b4f58, m=0xb77ef8e8, local_signal_index=2, argv=0xbfcbfbec) at kernel/qobject.cpp:3101 #11 0xb740f783 in QMenu::triggered (this=0x81b4f58, _t1=0x8197748) at .moc/release-shared/moc_qmenu.cpp:156 #12 0xb7410a4b in QMenuPrivate::_q_actionTriggered (this=0x81b6220) at widgets/qmenu.cpp:1065 #13 0xb7419ce6 in QMenu::qt_metacall (this=0x81b4f58, _c=QMetaObject::InvokeMetaMethod, _id=8, _a=0xbfcbfd6c) at .moc/release-shared/moc_qmenu.cpp:98 #14 0xb7f9c7ca in KMenu::qt_metacall (this=0x81b4f58, _c=QMetaObject::InvokeMetaMethod, _id=35, _a=0xbfcbfd6c) at /usr/src/debug/kdelibs-4.1.85/build/kdeui/kmenu.moc:69 #15 0xb79bb740 in QMetaObject::activate (sender=0x8197748, from_signal_index=5, to_signal_index=6, argv=0xbfcbfd6c) at kernel/qobject.cpp:3031 #16 0xb79bbb40 in QMetaObject::activate (sender=0x8197748, m=0xb77e9c78, from_local_signal_index=1, to_local_signal_index=2, argv=0xbfcbfd6c) at kernel/qobject.cpp:3121 #17 0xb7039591 in QAction::triggered (this=0x8197748, _t1=false) at .moc/release-shared/moc_qaction.cpp:216 #18 0xb7039eff in QAction::activate (this=0x8197748, event=QAction::Trigger) at kernel/qaction.cpp:1125 #19 0xb7417504 in QMenuPrivate::activateAction (this=0x81b6220, action=0x8197748, action_e=QAction::Trigger, self=true) at widgets/qmenu.cpp:1002 #20 0xb7417fb2 in QMenu::mouseReleaseEvent (this=0x81b4f58, e=0xbfcc0458) at widgets/qmenu.cpp:2169 #21 0xb7f9b195 in KMenu::mouseReleaseEvent (this=0x81b4f58, e=0xbfcc0458) at /usr/src/debug/kdelibs-4.1.85/kdeui/widgets/kmenu.cpp:454 #22 0xb7097a52 in QWidget::event (this=0x81b4f58, event=0xbfcc0458) at kernel/qwidget.cpp:7163 #23 0xb741a2a9 in QMenu::event (this=0x81b4f58, e=0xbfcc0458) at widgets/qmenu.cpp:2265 #24 0xb703f82c in QApplicationPrivate::notify_helper (this=0x80603a8, receiver=0x81b4f58, e=0xbfcc0458) at kernel/qapplication.cpp:3803 #25 0xb7048081 in QApplication::notify (this=0xbfcc0cf8, receiver=0x81b4f58, e=0xbfcc0458) at kernel/qapplication.cpp:3528 #26 0xb7ebd15d in KApplication::notify (this=0xbfcc0cf8, receiver=0x81b4f58, event=0xbfcc0458) at /usr/src/debug/kdelibs-4.1.85/kdeui/kernel/kapplication.cpp:307 #27 0xb79a6a71 in QCoreApplication::notifyInternal (this=0xbfcc0cf8, receiver=0x81b4f58, event=0xbfcc0458) at kernel/qcoreapplication.cpp:587 #28 0xb704730e in QApplicationPrivate::sendMouseEvent (receiver=0x81b4f58, event=0xbfcc0458, alienWidget=0x0, nativeWidget=0x81b4f58, buttonDown=0xb7800c90, lastMouseReceiver=@0xb7800c94) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:212 #29 0xb70b19be in QETWidget::translateMouseEvent (this=0x81b4f58, event=0xbfcc0a2c) at kernel/qapplication_x11.cpp:3974 #30 0xb70b0add in QApplication::x11ProcessEvent (this=0xbfcc0cf8, event=0xbfcc0a2c) at kernel/qapplication_x11.cpp:3036 #31 0xb70d91bc in x11EventSourceDispatch (s=0x80681d8, callback=0, user_data=0x0) at kernel/qguieventdispatcher_glib.cpp:142 #32 0xb68bc0b8 in IA__g_main_context_dispatch (context=0x8067638) at gmain.c:2144 #33 0xb68bf753 in g_main_context_iterate (context=0x8067638, block=1, dispatch=1, self=0x8061918) at gmain.c:2778 #34 0xb68bf911 in IA__g_main_context_iteration (context=0x8067638, may_block=1) at gmain.c:2841 #35 0xb79d1208 in QEventDispatcherGlib::processEvents (this=0x805bca8, flags={i = -1077146648}) at kernel/qeventdispatcher_glib.cpp:319 #36 0xb70d8885 in QGuiEventDispatcherGlib::processEvents (this=0x805bca8, flags={i = -1077146600}) at kernel/qguieventdispatcher_glib.cpp:198 #37 0xb79a514a in QEventLoop::processEvents (this=0xbfcc0c90, flags={i = -1077146536}) at kernel/qeventloop.cpp:143 #38 0xb79a530a in QEventLoop::exec (this=0xbfcc0c90, flags={i = -1077146472}) at kernel/qeventloop.cpp:194 #39 0xb79a79a5 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:845 #40 0xb703f6a7 in QApplication::exec () at kernel/qapplication.cpp:3331 #41 0xb8081921 in kdemain (argc=1, argv=0xbfcc0dd4) at /usr/src/debug/kdebase-workspace-4.1.85/klipper/main.cpp:48 #42 0x080486d2 in main (argc=0, argv=0x8209f08) at /usr/src/debug/kdebase-workspace-4.1.85/build/klipper/klipper_dummy.cpp:3
4.1.96 installed and I'm getting the same thing: Application: Klipper (klipper), signal SIGSEGV 0x00007f8211da27e1 in nanosleep () from /lib64/libc.so.6 [Current thread is 0 (LWP 27820)] Thread 2 (Thread 0x41754950 (LWP 12692)): #0 0x00007f8211dca0c2 in select () from /lib64/libc.so.6 #1 0x00007f8214f2c40e in ?? () from /usr/lib64/qt4/libQtCore.so.4 #2 0x00007f8214e1c58f in ?? () from /usr/lib64/qt4/libQtCore.so.4 #3 0x00007f8214ba7047 in start_thread () from /lib64/libpthread.so.0 #4 0x00007f8211dd028d in clone () from /lib64/libc.so.6 #5 0x0000000000000000 in ?? () Thread 1 (Thread 0x7f82162f1700 (LWP 27820)): [KCrash Handler] #5 URLGrabber::execute (this=0x1223830, command=0x4000400000020) at /var/tmp/portage/kde-base/klipper-4.1.96/work/klipper-4.1.96/klipper/urlgrabber.cpp:250 #6 0x00007f8215effdfb in URLGrabber::slotItemSelected (this=0x1223830, action=0x12ce480) at /var/tmp/portage/kde-base/klipper-4.1.96/work/klipper-4.1.96/klipper/urlgrabber.cpp:242 #7 0x00007f8215f00641 in URLGrabber::qt_metacall (this=0x1223830, _c=QMetaObject::InvokeMetaMethod, _id=3, _a=0x7fff1e32f4d0) at /var/tmp/portage/kde-base/klipper-4.1.96/work/klipper_build/klipper/urlgrabber.moc:78 #8 0x00007f8214f69fd1 in QMetaObject::activate () from /usr/lib64/qt4/libQtCore.so.4 #9 0x00007f8214311522 in QMenu::triggered () from /usr/lib64/qt4/libQtGui.so.4 #10 0x00007f8214311e5e in QMenuPrivate::_q_actionTriggered () from /usr/lib64/qt4/libQtGui.so.4 #11 0x00007f821431939e in QMenu::qt_metacall () from /usr/lib64/qt4/libQtGui.so.4 #12 0x00007f8215babc25 in KMenu::qt_metacall (this=0x1223830, _c=32, _id=506655568, _a=0x1310720) at /var/tmp/portage/kde-base/kdelibs-4.1.96/work/kdelibs_build/kdeui/kmenu.moc:69 #13 0x00007f8214f69fd1 in QMetaObject::activate () from /usr/lib64/qt4/libQtCore.so.4 #14 0x00007f8213f09fb7 in QAction::triggered () from /usr/lib64/qt4/libQtGui.so.4 #15 0x00007f8213f0a720 in QAction::activate () from /usr/lib64/qt4/libQtGui.so.4 #16 0x00007f821431ad2d in QMenuPrivate::activateAction () from /usr/lib64/qt4/libQtGui.so.4 #17 0x00007f821431cac2 in QMenu::mouseReleaseEvent () from /usr/lib64/qt4/libQtGui.so.4 #18 0x00007f8215bab8c1 in KMenu::mouseReleaseEvent (this=0x1367f70, e=0x7fff1e330310) at /var/tmp/portage/kde-base/kdelibs-4.1.96/work/kdelibs-4.1.96/kdeui/widgets/kmenu.cpp:454 #19 0x00007f8213f6a358 in QWidget::event () from /usr/lib64/qt4/libQtGui.so.4 #20 0x00007f8214318a31 in QMenu::event () from /usr/lib64/qt4/libQtGui.so.4 #21 0x00007f8213f13a7e in QApplicationPrivate::notify_helper () from /usr/lib64/qt4/libQtGui.so.4 #22 0x00007f8213f1409a in QApplication::notify () from /usr/lib64/qt4/libQtGui.so.4 #23 0x00007f8215af6f61 in KApplication::notify (this=0x7fff1e330d90, receiver=0x1367f70, event=0x7fff1e330310) at /var/tmp/portage/kde-base/kdelibs-4.1.96/work/kdelibs-4.1.96/kdeui/kernel/kapplication.cpp:307 #24 0x00007f8214f532a8 in QCoreApplication::notifyInternal () from /usr/lib64/qt4/libQtCore.so.4 #25 0x00007f8213f1bf21 in QApplicationPrivate::sendMouseEvent () from /usr/lib64/qt4/libQtGui.so.4 #26 0x00007f8213f7f1ac in QETWidget::translateMouseEvent () from /usr/lib64/qt4/libQtGui.so.4 #27 0x00007f8213f7da36 in QApplication::x11ProcessEvent () from /usr/lib64/qt4/libQtGui.so.4 #28 0x00007f8213fa5ae5 in QEventDispatcherX11::processEvents () from /usr/lib64/qt4/libQtGui.so.4 #29 0x00007f8214f52815 in QEventLoop::processEvents () from /usr/lib64/qt4/libQtCore.so.4 #30 0x00007f8214f528f5 in QEventLoop::exec () from /usr/lib64/qt4/libQtCore.so.4 #31 0x00007f8214f54a8e in QCoreApplication::exec () from /usr/lib64/qt4/libQtCore.so.4 #32 0x00007f8215f0bc58 in kdemain (argc=1, argv=0x7fff1e330ec8) at /var/tmp/portage/kde-base/klipper-4.1.96/work/klipper-4.1.96/klipper/main.cpp:48 #33 0x00007f8211d2db74 in __libc_start_main () from /lib64/libc.so.6 #34 0x00000000004008a9 in _start ()
*** Bug 180677 has been marked as a duplicate of this bug. ***
Should be fixed in r918711.
Created attachment 31362 [details] Klipper crash backtrace (In reply to comment #18) > Should be fixed in r918711. What version is r918711 supposed to be? I'm still having this problem in Fedora 10 and KDE 4.2 (kdebase-workspace-4.2.0-8.fc10.i386). It was quite easy to reproduce for me. As described earlier; click "Open with Firefox" twice in the Klipper pop-up -> crash.
I can also confirm this on kde 4.2 final on opensuse 11.1.
@Eelko: The changes in "r918711" you can see here: http://websvn.kde.org/?view=rev&revision=918711 They were made on 30th of January in trunk. On the other hand, the bug is still present for me, too, on OpenSUSE 11.1, latest KDE 4.2 Factory updates: KDE Version: v0.9.7 (KDE 4.2.00 (KDE 4.2.0) "release 99", KDE:KDE4:Factory:Desktop / openSUSE_11.1) Application: Cut & Paste History Utility Operating System: Linux (i686) release 2.6.27.7-9-default Compiler: gcc I wonder whether the fix in r918711 concerns the KDE 4.2 branch(?). Isn't trunk the already the 4.3 trunk, and if yes, has this been backported to the 4.2 branch? Still open for me, too.
I opened a bugtracker issue for OpenSUSE, too, whether they applied the mentioned patch already from upstream: https://bugzilla.novell.com/show_bug.cgi?id=476355 I'd rather leave this issue open, until the bug fix can be confirmed by the users reporting here using KDE 4.2...
could be revision 918711 be backported on 42 branch ?
By the way, if I delete according klipperrc and let Klipper restore its default settings, the "Open with Firefox" command appears as ps x |grep -q '[f]irefox' && "firefox -remote openURL(%s, new-window)" || firefox "%s" Nevertheless, I'm quite sure this was already exactly the setting before, because I already compared it before with the default settings required by the developers. The second thing is, that after doing so the Klipper action menu closes now immediately after an action was chosen, thus, the crash can't occur any longer. Can anyone try this, too: 1. Quit Klipper (answer "Start" on the question whether to launch again on next KDE startup) 2. cd ~/.kde4/share/config (in OpenSUSE 11.1, or whatever the right dir is for you) 3. mv klipperrc klipperrc.bak 4. Restart Klipper 5. Re-enable Klipper actions 6. Retry the "Open with Firefox" action command In other words, there was an "old" setting remaining preventing the Klipper actio menu from closing(?) Can anyone confirm this? If yes, can that one please attach his klipperrc.bak here (if it doesn't contain security-relevant entries)? Even if renewing the default settings would be the workaround on horizon, crashes should not happen generally, right? ;-)
I tried above steps on opensuse 11.1 but I can still reproduce this issue. Action menu doesn't close and clicking again crashes klipper.
(In reply to comment #25) > I tried above steps on opensuse 11.1 but I can still reproduce this issue. > Action menu doesn't close and clicking again crashes klipper. Only for synchronizing: What does your `klipper --version` show? Here it is for me: Qt: 4.5.0-rc1 KDE: 4.2.00 (KDE 4.2.0) "release 99" Klipper: v0.9.7
Qt: 4.4.3 KDE: 4.2.00 (KDE 4.2.0) "release 99" Klipper: v0.9.7 BTW how did you get QT 4.5? (In reply to comment #26) > (In reply to comment #25) > > I tried above steps on opensuse 11.1 but I can still reproduce this issue. > > Action menu doesn't close and clicking again crashes klipper. > > Only for synchronizing: > What does your `klipper --version` show? > > Here it is for me: > Qt: 4.5.0-rc1 > KDE: 4.2.00 (KDE 4.2.0) "release 99" > Klipper: v0.9.7
(In reply to comment #27) > Qt: 4.4.3 > KDE: 4.2.00 (KDE 4.2.0) "release 99" > Klipper: v0.9.7 > > BTW how did you get QT 4.5? First of all: Now the crash happens for me again, too. The action menu wasn't closing again on activating the "Open with Firefox" command. There seems to be some time-critical problem (is it called "race condition"?). In other words: Forget about this configuration renaming, sorry. And some OpenSUSE-specific note for you: Qt 4.5 I got obviously using the additional repository: http://download.opensuse.org/repositories/KDE:/Qt/openSUSE_11.1 But be aware, I'm not sure whether the KDE 4.2 Factory repository maintainers recommend this ;-) Anyway, it seems not to play a role for this crashing issue.
I repeated stopping klipper, followed by removing klipperc and restarting klipper in a terminal: :~/.kde4/share/config> rm klipperrc :~/.kde4/share/config> klipper klipper(11698)/kdecore (KWin) KWindowInfo::geometry: Pass NET::WMDesktop to KWindowInfo Now I push "Enable Actions" and select an example string http://ix.de. The Klipper action menu opens. If I push "Open in Firefox" (while Firefox 3.0.6 is already running, configured as open new pages in tabs) the page is immediately opened in FF and the Klipper menu closes. But the console shows something weird: ~/.kde4/share/config> /bin/sh: firefox -remote openURL(http://ix.de, new-window): No such file or directory The default command seems to be bad for newer versions of Firefox, the -remote option doesn't seem to be recognized. Anyway, continuing: Repeating selecting different URLs, at the beginning, the action menu still closes immediately, but the console output shows this: /bin/sh: firefox -remote openURL(http://ix.de, new-window): No such file or directory /bin/sh: firefox -remote openURL(http://ix.de,, new-window): No such file or directory /bin/sh: firefox -remote openURL(http://download.opensuse.org/repositories/KDE:/Qt/openSUSE_11.1, new-window): No such file or directory After a while, the action menu stops closing on triggering a command: /bin/sh: firefox -remote openURL(https://bugs.kde.org/userprefs.cgi?tab=email, new-window): No such file or directory After clicking at the "Open with Firefox" command again, Klipper crashes: KCrash: Application 'klipper' crashing... sock_file=/home/rkrell/.kde4/socket-rkrell/kdeinit4__0 I just need to be patient :-)
> http://websvn.kde.org/?view=rev&revision=918711 That's a port of the app to KConfigXT. I honestly don't see how this is related to this bug (I also looked at the changed code), might it just be hiding the issue? Random bugs such as this one (see comment #3: "It cannot be always reliably reproduced.") can be highly susceptible to unrelated changes, for example the value of an uninitialized variable can change.
I also allowed klipper to reset its configuration. And then I got this: /bin/sh: -c: line 0: syntax error near unexpected token `(' /bin/sh: -c: line 0: `ps x |grep -q '[f]irefox' && firefox -remote openURL('https://bugs.kde.org/show_bug.cgi?id=165726', new-window) || firefox 'https://bugs.kde.org/show_bug.cgi?id=165726'' But if I then change the configuration to have double-quotes around the openURL bit, then it seems to work.
Yes, revision r918711 was the port of klipper to kconfigXT, but with this port I've also fixed a couple of crashes. This one was among them. It can't be backported to 4.2.x, because KDE 4.2 is feature frozen and this port is considered to be a feature. So to conclude: The bug is FIXED in trunk, wait for 4.3 guys.
It's not a feature, it fixes a crash bug. It MUST be fixed in 4.2.
It's a bug that was fixed by implementing certain feature. Feature can't be backported. Bug is fixed in trunk - there's no point in reopening it. Don't do that, that makes no sense. If you want this bug fixed in 4.2 please fix it yourself or find someone who'll fix it for you. Personally I have no time and motivation to do that, sorry.
Bugfixes can be backported. This port fixes a bug, ergo it can and should be backported. It does not even introduce any user-visible feature. (I see a changed string which can trivially be reverted, other than that all the changes are "behind the scenes".) That said, it is indeed not quite the easiest way to fix that bug and I still don't really understand how it fixes it. > If you want this bug fixed in 4.2 please fix it yourself I can do that, but it would be by simply backporting the revision...
Looks like the actual change which fixed it this change from the KConfigXT port branch: http://websvn.kde.org/?view=rev&revision=884829 (Or maybe this one? http://websvn.kde.org/?view=rev&revision=885045 But it doesn't look like it.) Revision 884829 should be OK to backport if it really fixes it, as it doesn't involve rewriting the whole configuration mechanism. :-) And looking at the code before the change, I think I understand the true cause of the crash now: it uses iterators on temporaries! If you think revision 884829 is still too much to backport, a minimal fix would probably be to just fix: ActionListIterator it( matchingActions( m_myClipData ) ); to: ActionList matchingActionsList = matchingActions( m_myClipData ); ActionListIterator it( matchingActionsList ); (but this theory is yet to be tested).
You see, I did some rearrangements in code structure which spread across several revisions. This revision might fix this particular bug (though i'm not sure, needs testing), but it's not necessary that it will apply cleanly to the 4.2 sources when applied separately. because it might depend on earlier changes. I'm not saying that this bug shouldn't be fixed in 4.2. It's just that i'm not on fixing it right now. And also I think that it is wrong to open this bug report for bug that *is* fixed in trunk. If such practise existed we'd have a lot of open bugs for every kde version :)
> And also I think that it is wrong to open this bug report for bug that *is* > fixed in trunk. I disagree, I think bug reports should be open until they're fixed in the release branch or until trunk becomes the new release branch (but it should be backported, the latter option is only for stuff which can't be backported for some good reason). The bug is not fixed for end users before that. That said, I realize this is unfortunately not common practice on this bug tracker, so I won't insist on reopening this particular bug. > If such practise existed we'd have a lot of open bugs for every kde version :) We wouldn't if bugfixes were systematically backported as they should be. Having to wait for the next new feature release (or use trunk ;-) ) to get one's bugs fixed kinda defeats the purpose of bugfix releases. (I also think being even slightly less strict about the feature freezes could get a lot more bugs fixed in the release branches, but I realize this bug is entirely the wrong place to argue this.)
@Dmitry: You might be good programmer, but you did not get the message how to get your software to the masses. I agree, it's not your duty to do anything with any bug, it volountary. I know this is not the thread to discuss basic issues about how to deal with opensource, but I need to give you some hints: - As you see from the history of this bug this is already a long-standing issue over several so called stable versions. There are many people installing stable branches for being able to use something at all. I cannot believe that it is the same for you in which state is the software you participate in during different development cycles. This is a crash which can be reproduced, no minor bug. - Not everyone here is a programmer, and if they are programmers they might have their own piece of code to care for. Be thankful for having your piece of code tested by a wide community, and do not kick them into their... you know what I mean ;-) - You say that there would be many bugs reported here if they would be reported against stable branches instead the trunk. I absolutely disagree, there will be many more reports against the trunk, because it won't even be pre-tested by the developers itself and a trunk is usually unstable. So please, if you know so good where this crash can happen there will be thousands of users (not KDE programmers) who will be thankful for having this crash fixed.
Hey, don't be offended :) I didn't kick anyone. At least that wasn't what i wanted to say. I just said that bug exists in 4.2, yes, but I currently have no time for fixing it in branch. I had time to port kicker to kconfigxt and I did that port. Along with it i fixed this bug. I closed it. It's fixed in trunk. I'm not a maintainer of kicker (at least currently) - I was just passing by with a patch :) That's the story. If anyone is willing to help millions of users and fix it in 4.2 I'd be only glad to see him doing this. But not me, not now. Maybe later. That was my message, maybe I used some wrong words while trying to deliver it originally :)
Ok, so thanks for the patch :-) My aim was only to tell you what happens around here, because usually are mainatiners of a certain piece of software interested in fixing crashes as soon as possible. But I don't understand why this issue here was closed while being reported against KDE 4.2 and not 4.3. It's about stabilizing towards 4.2.1. So this issue should stay open until it's not successfully tested, shouldn't it? BTW: It is the same if it will stay open until 4.3 is released, and closed later, in worst case. But closing this freezes any other potential activity, maybe of someone else who has got some time to fix it.
Well, that's a common practise we have in KDE - if bug is fixed in trunk, it should be set to FIXED. Alternatively this bug could be held open if kicker had several version tags in bugzilla - one version for 4.2 and another for trunk. Then, bug could be tagged as a 4.2's kicker bug. But unfortunately I didn't change kicker version after my change, so it's still the same in trunk and in 4.2... But really, I think that such discussions should be held in a private mail or on the mailing list as they clutter the bug history making it really hard for someone to get info about the actual bug later.
Sorry, but marking bugs fixed generally when they seem to be fixed in trunk from your point of view is not a common practise, but only your personal one. Bugs reported to stable branches are called "backports from trunk", and backports are actually done here. If the piece of code you sent cannot be backported this is not the reason for closing this issue. Please look around on this bug tracker. There will be almost half a year until 4.3 will be released! This bug is not fixed according to this report, that's the point and this belongs to this issue, not to a private mail conversation.
OK, I'm stopping to argue. If you know how KDE devs work with bugzilla better than devs do, then you have your point and I don't feel like repeating same stuff 100 times in a row :)
*** Bug 185810 has been marked as a duplicate of this bug. ***
I don't dare to change it's status, I'll leave that up to somebody else (see discussion above). For what it's worth, this bug still occurs in Fedora 10 with KDE 4.2.1.
I can also confirm on kde 4.2.1 in opensuse 11.1. Backtrace is as below: Application: Klipper (klipper), signal SIGSEGV [?1034h[Thread debugging using libthread_db enabled] [Current thread is 1 (Thread 0xb6385700 (LWP 4071))] Thread 2 (Thread 0xb48e4b90 (LWP 10681)): #0 0xffffe430 in __kernel_vsyscall () #1 0xb687f411 in select () from /lib/libc.so.6 #2 0xb7736477 in ?? () from /usr/lib/libQtCore.so.4 #3 0xb766474e in ?? () from /usr/lib/libQtCore.so.4 #4 0xb76021b5 in start_thread () from /lib/libpthread.so.0 #5 0xb68863be in clone () from /lib/libc.so.6 Thread 1 (Thread 0xb6385700 (LWP 4071)): [KCrash Handler] #6 URLGrabber::execute (this=0x81ed418, command=0x6) at /usr/src/debug/kdebase-workspace-4.2.1/klipper/urlgrabber.cpp:250 #7 0xb7ec293a in URLGrabber::slotItemSelected (this=0x81ed418, action=0x82265d0) at /usr/src/debug/kdebase-workspace-4.2.1/klipper/urlgrabber.cpp:242 #8 0xb7ec345c in URLGrabber::qt_metacall (this=0x81ed418, _c=QMetaObject::InvokeMetaMethod, _id=3, _a=0xbff1854c) at /usr/src/debug/kdebase-workspace-4.2.1/build/klipper/urlgrabber.moc:78 #9 0xb776ec88 in QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib/libQtCore.so.4 #10 0xb7770412 in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) () from /usr/lib/libQtCore.so.4 #11 0xb7169f33 in QMenu::triggered(QAction*) () from /usr/lib/libQtGui.so.4 #12 0xb716b72c in ?? () from /usr/lib/libQtGui.so.4 #13 0xb7174656 in QMenu::qt_metacall(QMetaObject::Call, int, void**) () from /usr/lib/libQtGui.so.4 #14 0xb7d9fd7a in KMenu::qt_metacall(QMetaObject::Call, int, void**) () from /usr/lib/libkdeui.so.5 #15 0xb776ec88 in QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib/libQtCore.so.4 #16 0xb776f0c0 in QMetaObject::activate(QObject*, QMetaObject const*, int, int, void**) () from /usr/lib/libQtCore.so.4 #17 0xb6d0d8e1 in QAction::triggered(bool) () from /usr/lib/libQtGui.so.4 #18 0xb6d0ee5f in QAction::activate(QAction::ActionEvent) () from /usr/lib/libQtGui.so.4 #19 0xb716b65c in ?? () from /usr/lib/libQtGui.so.4 #20 0xb7171deb in ?? () from /usr/lib/libQtGui.so.4 #21 0xb71728c2 in QMenu::mouseReleaseEvent(QMouseEvent*) () from /usr/lib/libQtGui.so.4 #22 0xb7d9e715 in KMenu::mouseReleaseEvent(QMouseEvent*) () from /usr/lib/libkdeui.so.5 #23 0xb6d6aaf3 in QWidget::event(QEvent*) () from /usr/lib/libQtGui.so.4 #24 0xb7174ca9 in QMenu::event(QEvent*) () from /usr/lib/libQtGui.so.4 #25 0xb6d13eec in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/libQtGui.so.4 #26 0xb6d1cb21 in QApplication::notify(QObject*, QEvent*) () from /usr/lib/libQtGui.so.4 #27 0xb7cbfa3d in KApplication::notify(QObject*, QEvent*) () from /usr/lib/libkdeui.so.5 #28 0xb77589db in QCoreApplication::notifyInternal(QObject*, QEvent*) () from /usr/lib/libQtCore.so.4 #29 0xb6d1bb8e in QApplicationPrivate::sendMouseEvent(QWidget*, QMouseEvent*, QWidget*, QWidget*, QWidget**, QPointer<QWidget>&) () from /usr/lib/libQtGui.so.4 #30 0xb6d8bb6e in ?? () from /usr/lib/libQtGui.so.4 #31 0xb6d8ac27 in QApplication::x11ProcessEvent(_XEvent*) () from /usr/lib/libQtGui.so.4 #32 0xb6db43ca in ?? () from /usr/lib/libQtGui.so.4 #33 0xb65329a8 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0 #34 0xb6536063 in ?? () from /usr/lib/libglib-2.0.so.0 #35 0xb6536221 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #36 0xb7784428 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4 #37 0xb6db3ac5 in ?? () from /usr/lib/libQtGui.so.4 #38 0xb7756ffa in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4 #39 0xb775743a in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4 #40 0xb77598e9 in QCoreApplication::exec() () from /usr/lib/libQtCore.so.4 #41 0xb6d13d67 in QApplication::exec() () from /usr/lib/libQtGui.so.4 #42 0xb7ed0981 in kdemain (argc=1, argv=0xbff197f4) at /usr/src/debug/kdebase-workspace-4.2.1/klipper/main.cpp:48 #43 0x08048712 in main (argc=0, argv=0x81bbde0) at /usr/src/debug/kdebase-workspace-4.2.1/build/klipper/klipper_dummy.cpp:3 By the way how to reopen a bug.
*** Bug 188253 has been marked as a duplicate of this bug. ***
In what version the bug is fixed? Can the fix be backported into 4.2-branch - it still crashes here with 4.2.2
*** Bug 191735 has been marked as a duplicate of this bug. ***
Doesn't look like it will be fixed in 4.2. Doesn't crash any longer in KDE 4.3 Beta1. But there are more long-standing problems with Klipper, which are subject to another issue on this bugtracker. Especially that the Klipper popup still doesn't close automatically on clicking an action and for the first time after starting Klipper it's necessary to copy an URL twice to the clipboard for getting the Klipper action menu popping up.
Trivial fix for the 4.2 branch as a patch (still not tested, Fedora packages currently building): http://cvs.fedoraproject.org/viewvc/rpms/kdebase-workspace/F-11/kdebase-workspace-4.2.4-kde%23165726-klipper-crash.patch?revision=1.1&view=markup Why has this been ignored for months when I even POSTED a fix in comment #36? Next time I'll just abuse my commit access and commit this stuff directly without asking anybody, I'm fed up of maintainers just not caring about fixing bugs in release branches!
+1 with devs only working on development branches, we'll never see a stable KDE4.
I did some quick testing of my patch, it appears to fix this issue, but as it isn't 100% reproducible, I'm not 100% sure.
SVN commit 977693 by kkofler: Don't use an iterator on a temporary. Should fix the crash when opening an action (#165726), some quick testing shows it's not reproducible. This was fixed in 4.3 as part of a larger refactoring (revision 884829). This commit is just the 2-line fix for the crash. It's unfortunately too late for 4.2.4 and there might not be any further 4.2.x release, but at least this is there for people to pick up now. CCBUG: 165726 M +2 -1 urlgrabber.cpp WebSVN link: http://websvn.kde.org/?view=rev&revision=977693