Bug 205046 - entering sth in kpackagekit, just before it is crashed
Summary: entering sth in kpackagekit, just before it is crashed
Status: RESOLVED FIXED
Alias: None
Product: kpackagekit
Classification: Unmaintained
Component: general (other bugs)
Version First Reported In: unspecified
Platform: Unlisted Binaries Linux
: NOR crash
Target Milestone: ---
Assignee: Steven M. Parrish
URL:
Keywords:
: 209441 212571 (view as bug list)
Depends on:
Blocks:
 
Reported: 2009-08-25 09:14 UTC by Mathias D
Modified: 2010-08-19 00:56 UTC (History)
4 users (show)

See Also:
Latest Commit:
Version Fixed In: 0.5.0
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Mathias D 2009-08-25 09:14:54 UTC
Application that crashed: kpackagekit
Version of the application: 0.4.0
KDE Version: 4.3.00 (KDE 4.3.0)
Qt Version: 4.5.2
Operating System: Linux 2.6.28-12-generic x86_64
Distribution: Ubuntu 9.04

What I was doing when the application crashed:
I just started system and run kpackagekit. by typing into the textline kpackagekit crashes.

 -- Backtrace:
Application: KPackageKit (kpackagekit), signal: Segmentation fault
[KCrash Handler]
#5  QAction::activate (this=0x0, event=QAction::Trigger) at kernel/qaction.h:67
#6  0x00007f0ced7f8c40 in KpkAddRm::event (this=0x1c8a5b0, event=0x7fff01bc2ee0) at /usr/include/qt4/QtGui/qaction.h:203
#7  0x00007f0cf6b10f4d in QApplicationPrivate::notify_helper (this=0x1941530, receiver=0x1c8a5b0, e=0x7fff01bc2ee0) at kernel/qapplication.cpp:4056
#8  0x00007f0cf6b1a0cf in QApplication::notify (this=<value optimized out>, receiver=0x1c8a5b0, e=0x7fff01bc2ee0) at kernel/qapplication.cpp:3662
#9  0x00007f0cf95ad71b in KApplication::notify (this=0x7fff01bc50d0, receiver=0x1c88730, event=0x7fff01bc2ee0) at /build/buildd/kde4libs-4.3.0/kdeui/kernel/kapplication.cpp:302
#10 0x00007f0cf78ec6ac in QCoreApplication::notifyInternal (this=0x7fff01bc50d0, receiver=0x1c88730, event=0x7fff01bc2ee0) at kernel/qcoreapplication.cpp:610
#11 0x00007f0cf6ba66a4 in QKeyMapper::sendKeyEvent (keyWidget=0x1c88730, grab=<value optimized out>, type=QEvent::KeyPress, code=16777220, modifiers={i = 29110544}, text=@0x7fff01bc3100, 
    autorepeat=false, count=1, nativeScanCode=36, nativeVirtualKey=65293, nativeModifiers=0) at kernel/qkeymapper_x11.cpp:1675
#12 0x00007f0cf6ba8a02 in QKeyMapperPrivate::translateKeyEvent (this=0x1976090, keyWidget=0x1c88730, event=0x7fff01bc4d10, grab=false) at kernel/qkeymapper_x11.cpp:1645
#13 0x00007f0cf6b810e6 in QApplication::x11ProcessEvent (this=0x7fff01bc50d0, event=0x7fff01bc4d10) at kernel/qapplication_x11.cpp:3443
#14 0x00007f0cf6baa454 in x11EventSourceDispatch (s=0x19447c0, callback=0, user_data=0x0) at kernel/qguieventdispatcher_glib.cpp:146
#15 0x00007f0cf2e5520a in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#16 0x00007f0cf2e588e0 in ?? () from /usr/lib/libglib-2.0.so.0
#17 0x00007f0cf2e58a7c in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0
#18 0x00007f0cf7915a8f in QEventDispatcherGlib::processEvents (this=0x1915040, flags=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:327
#19 0x00007f0cf6ba9bdf in QGuiEventDispatcherGlib::processEvents (this=0x0, flags=<value optimized out>) at kernel/qguieventdispatcher_glib.cpp:202
#20 0x00007f0cf78eaf42 in QEventLoop::processEvents (this=<value optimized out>, flags={i = 29118464}) at kernel/qeventloop.cpp:149
#21 0x00007f0cf78eb314 in QEventLoop::exec (this=0x7fff01bc5040, flags={i = 29118544}) at kernel/qeventloop.cpp:201
#22 0x00007f0cf78ed5e4 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:888
#23 0x0000000000404332 in main (argc=5, argv=0x7fff01bc5458) at /build/buildd/kpackagekit-0.4/KPackageKit/main.cpp:62

Reported using DrKonqi
Comment 1 Dario Andres 2009-10-04 21:50:57 UTC
*** Bug 209441 has been marked as a duplicate of this bug. ***
Comment 2 Dario Andres 2009-10-04 21:51:39 UTC
I wonder if this could be related to bug 201814. Thanks
Comment 3 Dario Andres 2009-11-01 01:41:37 UTC
*** Bug 212571 has been marked as a duplicate of this bug. ***
Comment 4 Daniel Nicoletti 2010-08-19 00:56:24 UTC
This bug has been fixed in 0.5 releases.
Something was wrong with the keyboard events.

Thanks.