Bug 180677 - klipper crashes when a url is copied from kmail
Summary: klipper crashes when a url is copied from kmail
Status: RESOLVED DUPLICATE of bug 165726
Alias: None
Product: klipper
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Fedora RPMs Linux
: NOR crash
Target Milestone: ---
Assignee: Esben Mose Hansen
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-01-14 16:02 UTC by CybyDude
Modified: 2009-01-26 13:15 UTC (History)
1 user (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 CybyDude 2009-01-14 16:02:32 UTC
Version:           klipper 4.1.3-7 (using KDE 4.1.3)
OS:                Linux
Installed from:    Fedora RPMs

when a url is copied from kmail, klipper crashes

Application: 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)
[Thread debugging using libthread_db enabled]
[New Thread 0xb7fb0770 (LWP 2914)]
[New Thread 0xb6778b90 (LWP 7649)]
(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)
(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]
#6  0x002aad97 in ?? () from /usr/lib/libkdeinit4_klipper.so
#7  0x002ab35a in ?? () from /usr/lib/libkdeinit4_klipper.so
#8  0x002abe6c in ?? () from /usr/lib/libkdeinit4_klipper.so
#9  0x07a43df0 in QMetaObject::activate () from /usr/lib/libQtCore.so.4
#10 0x07a44b72 in QMetaObject::activate () from /usr/lib/libQtCore.so.4
#11 0x024ece43 in QMenu::triggered () from /usr/lib/libQtGui.so.4
#12 0x024ee10b in ?? () from /usr/lib/libQtGui.so.4
#13 0x024f72d6 in QMenu::qt_metacall () from /usr/lib/libQtGui.so.4
#14 0x02ba708a in KMenu::qt_metacall () from /usr/lib/libkdeui.so.5
#15 0x07a43df0 in QMetaObject::activate () from /usr/lib/libQtCore.so.4
#16 0x07a441f0 in QMetaObject::activate () from /usr/lib/libQtCore.so.4
#17 0x02118331 in QAction::triggered () from /usr/lib/libQtGui.so.4
#18 0x02118c9f in QAction::activate () from /usr/lib/libQtGui.so.4
#19 0x024f4b14 in ?? () from /usr/lib/libQtGui.so.4
#20 0x024f55a2 in QMenu::mouseReleaseEvent () from /usr/lib/libQtGui.so.4
#21 0x02ba5a25 in KMenu::mouseReleaseEvent () from /usr/lib/libkdeui.so.5
#22 0x02176692 in QWidget::event () from /usr/lib/libQtGui.so.4
#23 0x024f7899 in QMenu::event () from /usr/lib/libQtGui.so.4
#24 0x0211e62c in QApplicationPrivate::notify_helper ()
   from /usr/lib/libQtGui.so.4
#25 0x02126e21 in QApplication::notify () from /usr/lib/libQtGui.so.4
#26 0x02add71d in KApplication::notify () from /usr/lib/libkdeui.so.5
#27 0x07a2f1c1 in QCoreApplication::notifyInternal ()
   from /usr/lib/libQtCore.so.4
#28 0x021260ae in QApplicationPrivate::sendMouseEvent ()
   from /usr/lib/libQtGui.so.4
#29 0x0219064e in ?? () from /usr/lib/libQtGui.so.4
#30 0x0218f755 in QApplication::x11ProcessEvent () from /usr/lib/libQtGui.so.4
#31 0x021b7d8a in ?? () from /usr/lib/libQtGui.so.4
#32 0x00ad8238 in g_main_context_dispatch () from /lib/libglib-2.0.so.0
#33 0x00adb8e3 in ?? () from /lib/libglib-2.0.so.0
#34 0x00adbaa1 in g_main_context_iteration () from /lib/libglib-2.0.so.0
#35 0x07a597f8 in QEventDispatcherGlib::processEvents ()
   from /usr/lib/libQtCore.so.4
#36 0x021b7485 in ?? () from /usr/lib/libQtGui.so.4
#37 0x07a2d88a in QEventLoop::processEvents () from /usr/lib/libQtCore.so.4
#38 0x07a2da4a in QEventLoop::exec () from /usr/lib/libQtCore.so.4
#39 0x07a30105 in QCoreApplication::exec () from /usr/lib/libQtCore.so.4
#40 0x0211e4a7 in QApplication::exec () from /usr/lib/libQtGui.so.4
#41 0x002b9351 in kdemain () from /usr/lib/libkdeinit4_klipper.so
#42 0x080486e2 in _start ()
Comment 1 Dario Andres 2009-01-15 23:38:55 UTC
If you can reproduce the crash at will, may you read http://techbase.kde.org/Development/Tutorials/Debugging/How_to_create_useful_crash_reports and post a complete backtrace here? Thanks :)
Comment 2 Dario Andres 2009-01-25 13:34:44 UTC
The reporter sent me an email:
---------------------

hi
sorry for the delay in responding. my internet connection had been down.

i could reproduce the situation a couple of times. i couldnt get a screenshot
/ record video of that activity though. am confident of the steps involved in
stimulating the bug.

1. open kmail and open a mail with some hyperlink (as shown in the screen
shot).

2.      right click on the link and choose copy link location from the kmail's
context menu.

3.      klipper's action menu popups up.

4.      Choose open with default browser (I have edited it to make opera as my
default browser). (snapshot2)

5.      opera gets launched.

6.      Action menu popup still visible.

7.      Click on the same option once again.

8.      klipper crashes.

Thats about it.
Comment 3 Dario Andres 2009-01-25 15:13:54 UTC
The reporter sent me another email:
------------

further to my response sent a while ago about the bug,

I checked it out further and i guess the crash is due to the second click on
the action pop up of klipper after the first one ALREADY launches the
associated process.

am attaching the screen shot of the klipper crash for ur kind information.

------------

Can you take a look at http://fedoraproject.org/wiki/StackTraces to know howto generate a full backtrace (you will need to install kdebase-debuginfo), and then post the bactrace (the details in the KCrash dialog) here?

Thanks
Comment 4 Dario Andres 2009-01-26 13:04:55 UTC
The reporter sent me another email:
-----------------

here is the back trace.

===========
Application: Klipper (klipper), signal SIGSEGV
[Current thread is 1 (Thread 0xb800f770 (LWP 3007))]

Thread 2 (Thread 0xb67adb90 (LWP 3302)):
#0  0x00110416 in __kernel_vsyscall ()
#1  0x009853d1 in select () from /lib/libc.so.6
#2  0x06cec627 in QProcessManager::run (this=0x9f05a98) at
io/qprocess_unix.cpp:301
#3  0x06c1c75e in QThreadPrivate::start (arg=0x9f05a98) at
thread/qthread_unix.cpp:185
#4  0x00a5751f in start_thread (arg=0xb67adb90) at pthread_create.c:297
#5  0x0098d04e in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:130

Thread 1 (Thread 0xb800f770 (LWP 3007)):
[KCrash Handler]
#6  URLGrabber::execute (this=0x9f8fd78, command=0x6) at
/usr/src/debug/kdebase-workspace-4.1.4/klipper/urlgrabber.cpp:251
#7  0x002ab35a in URLGrabber::slotItemSelected (this=0x9f8fd78,
action=0x9fb30d8) at /usr/src/debug/kdebase-
workspace-4.1.4/klipper/urlgrabber.cpp:243
#8  0x002abe6c in URLGrabber::qt_metacall (this=0x9f8fd78,
_c=QMetaObject::InvokeMetaMethod, _id=3, _a=0xbf83dcac)
   at /usr/src/debug/kdebase-workspace-4.1.4/i386-redhat-linux-
gnu/klipper/urlgrabber.moc:78
#9  0x06d21df0 in QMetaObject::activate (sender=0xa000460,
from_signal_index=29, to_signal_index=29, argv=0xbf83dcac) at
kernel/qobject.cpp:3031
#10 0x06d22b72 in QMetaObject::activate (sender=0xa000460, m=0x76d0f08,
local_signal_index=2, argv=0xbf83dcac) at kernel/qobject.cpp:3101
#11 0x072e51c3 in QMenu::triggered (this=0xa000460, _t1=0x9fb30d8) at
.moc/release-shared/moc_qmenu.cpp:156
#12 0x072e648b in QMenuPrivate::_q_actionTriggered (this=0x9ff7e98) at
widgets/qmenu.cpp:1065
#13 0x072ef656 in QMenu::qt_metacall (this=0xa000460,
_c=QMetaObject::InvokeMetaMethod, _id=8, _a=0xbf83de2c) at .moc/release-
shared/moc_qmenu.cpp:98
#14 0x0796a30a in KMenu::qt_metacall (this=0xa000460,
_c=QMetaObject::InvokeMetaMethod, _id=35, _a=0xbf83de2c) at
/usr/src/debug/kdelibs-4.1.4/i386-redhat-linux-gnu/kdeui/kmenu.moc:69
#15 0x06d21df0 in QMetaObject::activate (sender=0x9fb30d8,
from_signal_index=5, to_signal_index=6, argv=0xbf83de2c) at
kernel/qobject.cpp:3031
#16 0x06d221f0 in QMetaObject::activate (sender=0x9fb30d8, m=0x76cb2a0,
from_local_signal_index=1, to_local_signal_index=2, argv=0xbf83de2c) at
kernel/qobject.cpp:3121
#17 0x06f10391 in QAction::triggered (this=0x9fb30d8, _t1=false) at
.moc/release-shared/moc_qaction.cpp:216
#18 0x06f10cff in QAction::activate (this=0x9fb30d8, event=QAction::Trigger)
at kernel/qaction.cpp:1125
#19 0x072ece94 in QMenuPrivate::activateAction (this=0x9ff7e98,
action=0x9fb30d8, action_e=QAction::Trigger, self=true) at
widgets/qmenu.cpp:1002
#20 0x072ed922 in QMenu::mouseReleaseEvent (this=0xa000460, e=0xbf83e508) at
widgets/qmenu.cpp:2169
#21 0x07968ca5 in KMenu::mouseReleaseEvent (this=0xa000460, e=0xbf83e508) at
/usr/src/debug/kdelibs-4.1.4/kdeui/widgets/kmenu.cpp:452
#22 0x06f6e6f2 in QWidget::event (this=0xa000460, event=0xbf83e508) at
kernel/qwidget.cpp:7163
#23 0x072efc19 in QMenu::event (this=0xa000460, e=0xbf83e508) at
widgets/qmenu.cpp:2265
#24 0x06f1668c in QApplicationPrivate::notify_helper (this=0x9f02008,
receiver=0xa000460, e=0xbf83e508) at kernel/qapplication.cpp:3803
#25 0x06f1ee81 in QApplication::notify (this=0xbf83edb8, receiver=0xa000460,
e=0xbf83e508) at kernel/qapplication.cpp:3528
#26 0x078a072d in KApplication::notify (this=0xbf83edb8, receiver=0xa000460,
event=0xbf83e508) at
/usr/src/debug/kdelibs-4.1.4/kdeui/kernel/kapplication.cpp:311
#27 0x06d0d1c1 in QCoreApplication::notifyInternal (this=0xbf83edb8,
receiver=0xa000460, event=0xbf83e508) at kernel/qcoreapplication.cpp:587
#28 0x06f1e10e in QCoreApplication::sendSpontaneousEvent (event=<value
optimized out>, receiver=0xa000460) at
../../src/corelib/kernel/qcoreapplication.h:212
#29 QApplicationPrivate::sendMouseEvent (receiver=0xa000460, event=0xbf83e508,
alienWidget=0x0, nativeWidget=0xa000460, buttonDown=0x76e2270,
lastMouseReceiver=@0x76e2274)
   at kernel/qapplication.cpp:2793
#30 0x06f886de in QETWidget::translateMouseEvent (this=0xa000460,
event=0xbf83eaec) at kernel/qapplication_x11.cpp:3980
#31 0x06f877e5 in QApplication::x11ProcessEvent (this=0xbf83edb8,
event=0xbf83eaec) at kernel/qapplication_x11.cpp:3042
#32 0x06fafe1a in x11EventSourceDispatch (s=0x9f05348, callback=0,
user_data=0x0) at kernel/qguieventdispatcher_glib.cpp:142
#33 0x00ad8238 in g_main_dispatch () at gmain.c:2144
#34 IA__g_main_context_dispatch (context=0x9f04720) at gmain.c:2697
#35 0x00adb8e3 in g_main_context_iterate (context=0x9f04720, block=1,
dispatch=1, self=0x9f021f8) at gmain.c:2778
#36 0x00adbaa1 in IA__g_main_context_iteration (context=0x9f04720,
may_block=1) at gmain.c:2841
#37 0x06d377f8 in QEventDispatcherGlib::processEvents (this=0x9f02220,
flags={i = 4}) at kernel/qeventdispatcher_glib.cpp:319
#38 0x06faf515 in QGuiEventDispatcherGlib::processEvents (this=0x9f02220,
flags={i = 4}) at kernel/qguieventdispatcher_glib.cpp:198
#39 0x06d0b88a in QEventLoop::processEvents (this=0xbf83ed50, flags={i = 4})
at kernel/qeventloop.cpp:143
#40 0x06d0ba4a in QEventLoop::exec (this=0xbf83ed50, flags={i = 0}) at
kernel/qeventloop.cpp:194
#41 0x06d0e105 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:845
#42 0x06f16507 in QApplication::exec () at kernel/qapplication.cpp:3331
#43 0x002b9341 in kdemain (argc=1, argv=0xbf83ee94) at /usr/src/debug/kdebase-
workspace-4.1.4/klipper/main.cpp:48
#44 0x080486e2 in main (argc=0, argv=0x9ff5ec0) at /usr/src/debug/kdebase-
workspace-4.1.4/i386-redhat-linux-gnu/klipper/klipper_dummy.cpp:3

=================

and as is obvious, kmail has got nothing to do with this. when any url copied
to clipboard, the klipper action menu pops up. choosing an action works
normally as expected. ideally the action popup should go off at this juncture.
but it doesnt. it persists. when the action is chosen again, klipper crashes.

hope this information helps.
regards
Comment 5 Dario Andres 2009-01-26 13:15:16 UTC
Thanks a lot :)

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