Bug 254284 - Application: (kcmshell4), signal: Segmentation fault
Summary: Application: (kcmshell4), signal: Segmentation fault
Status: RESOLVED FIXED
Alias: None
Product: kpackagekit
Classification: Unmaintained
Component: general (other bugs)
Version First Reported In: unspecified
Platform: Ubuntu Linux
: NOR crash
Target Milestone: ---
Assignee: Steven M. Parrish
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-10-15 19:02 UTC by omega
Modified: 2011-03-07 22:27 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed/Implemented In:
Sentry Crash Report:


Attachments
New crash information added by DrKonqi (3.99 KB, text/plain)
2010-10-27 17:41 UTC, omega
Details

Note You need to log in before you can comment on or make changes to this bug.
Description omega 2010-10-15 19:02:30 UTC
Application: kcmshell4 ()
KDE Platform Version: 4.5.2 (KDE 4.5.2)
Qt Version: 4.7.0
Operating System: Linux 2.6.35-22-generic x86_64
Distribution: Ubuntu 10.10

-- Information about the crash:
- What I was doing when the application crashed:

i had this crash when i updating system packages with kpackagekit

The crash can be reproduced some of the time.

-- Backtrace:
Application: Modulo di controllo di KDE (kcmshell4), signal: Segmentation fault
[Current thread is 1 (Thread 0x7f64d98ae760 (LWP 23388))]

Thread 2 (Thread 0x7f64c5a8f710 (LWP 23396)):
#0  0x00007f64d92141d3 in __poll (fds=<value optimized out>, nfds=<value optimized out>, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:87
#1  0x00007f64d358e009 in ?? () from /lib/libglib-2.0.so.0
#2  0x00007f64d358e45c in g_main_context_iteration () from /lib/libglib-2.0.so.0
#3  0x00007f64d7e691e6 in QEventDispatcherGlib::processEvents (this=0x1e06170, flags=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:417
#4  0x00007f64d7e3ba02 in QEventLoop::processEvents (this=<value optimized out>, flags=) at kernel/qeventloop.cpp:149
#5  0x00007f64d7e3bdec in QEventLoop::exec (this=0x7f64c5a8edb0, flags=) at kernel/qeventloop.cpp:201
#6  0x00007f64d7d462fd in QThread::exec (this=<value optimized out>) at thread/qthread.cpp:490
#7  0x00007f64d7e1b5f8 in QInotifyFileSystemWatcherEngine::run (this=0x1d7c0c0) at io/qfilesystemwatcher_inotify.cpp:248
#8  0x00007f64d7d4927e in QThreadPrivate::start (arg=0x1d7c0c0) at thread/qthread_unix.cpp:266
#9  0x00007f64d6ad0971 in start_thread (arg=<value optimized out>) at pthread_create.c:304
#10 0x00007f64d922091d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112
#11 0x0000000000000000 in ?? ()

Thread 1 (Thread 0x7f64d98ae760 (LWP 23388)):
[KCrash Handler]
#6  0x00007f64d71ecb34 in parent (this=0x1e091f0) at ../../include/QtCore/../../src/corelib/kernel/qobject.h:250
#7  parentWidget (this=0x1e091f0) at ../../include/QtGui/../../src/gui/kernel/qwidget.h:1022
#8  QWidget::window (this=0x1e091f0) at kernel/qwidget.cpp:4182
#9  0x00007f64d71a8ab8 in QApplicationPrivate::dispatchEnterLeave (enter=<value optimized out>, leave=0x1e091f0) at kernel/qapplication.cpp:2651
#10 0x00007f64d71a8d7e in QApplicationPrivate::sendMouseEvent (receiver=0x1d4e6e0, event=0x7fff2a670350, alienWidget=0x1d4e6e0, nativeWidget=0x1d3bb70, buttonDown=<value optimized out>, lastMouseReceiver=<value optimized out>, spontaneous=true) at kernel/qapplication.cpp:3038
#11 0x00007f64d722c345 in QETWidget::translateMouseEvent (this=0x1d3bb70, event=<value optimized out>) at kernel/qapplication_x11.cpp:4403
#12 0x00007f64d722ac5c in QApplication::x11ProcessEvent (this=<value optimized out>, event=0x7fff2a670c70) at kernel/qapplication_x11.cpp:3536
#13 0x00007f64d72570e2 in x11EventSourceDispatch (s=0x1c3f130, callback=<value optimized out>, user_data=<value optimized out>) at kernel/qguieventdispatcher_glib.cpp:146
#14 0x00007f64d358a342 in g_main_context_dispatch () from /lib/libglib-2.0.so.0
#15 0x00007f64d358e2a8 in ?? () from /lib/libglib-2.0.so.0
#16 0x00007f64d358e45c in g_main_context_iteration () from /lib/libglib-2.0.so.0
#17 0x00007f64d7e69193 in QEventDispatcherGlib::processEvents (this=0x1c23f90, flags=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:415
#18 0x00007f64d7256a4e in QGuiEventDispatcherGlib::processEvents (this=0x1e091f0, flags=<value optimized out>) at kernel/qguieventdispatcher_glib.cpp:204
#19 0x00007f64d7e3ba02 in QEventLoop::processEvents (this=<value optimized out>, flags=) at kernel/qeventloop.cpp:149
#20 0x00007f64d7e3bdec in QEventLoop::exec (this=0x7fff2a670fa0, flags=) at kernel/qeventloop.cpp:201
#21 0x00007f64d76987de in QDialog::exec (this=0x1d77f80) at dialogs/qdialog.cpp:552
#22 0x00007f64d94c4968 in kdemain (_argc=<value optimized out>, _argv=<value optimized out>) at ../../kcmshell/main.cpp:285
#23 0x00007f64d9158d8e in __libc_start_main (main=<value optimized out>, argc=<value optimized out>, ubp_av=<value optimized out>, init=<value optimized out>, fini=<value optimized out>, rtld_fini=<value optimized out>, stack_end=0x7fff2a671838) at libc-start.c:226
#24 0x0000000000400669 in _start ()

Possible duplicates by query: bug 195682.

Reported using DrKonqi
Comment 1 omega 2010-10-27 17:41:42 UTC
Created attachment 52912 [details]
New crash information added by DrKonqi

kcmshell4 () on KDE Platform 4.5.2 (KDE 4.5.2) using Qt 4.7.0

- What I was doing when the application crashed:


i had this crash when i updating system packages with kpackagekit

-- Backtrace (Reduced):
#6  parent (this=0x1b31880) at ../../include/QtCore/../../src/corelib/kernel/qobject.h:250
#7  parentWidget (this=0x1b31880) at ../../include/QtGui/../../src/gui/kernel/qwidget.h:1022
#8  QWidget::window (this=0x1b31880) at kernel/qwidget.cpp:4185
#9  0x00007fb5060e3ab8 in QApplicationPrivate::dispatchEnterLeave (enter=<value optimized out>, leave=0x1b31880) at kernel/qapplication.cpp:2651
#10 0x00007fb5060e3d7e in QApplicationPrivate::sendMouseEvent (receiver=0x1b0edf0, event=0x7fff32618b70, alienWidget=0x1b0edf0, nativeWidget=0x1b280e0, buttonDown=<value optimized out>, lastMouseReceiver=<value optimized out>, spontaneous=true) at kernel/qapplication.cpp:3038
Comment 2 Daniel Nicoletti 2010-11-26 18:38:21 UTC
though I don't see why kcmshell is here (as KPackageKit does not use it).
It seems to be related to bug #253930
Which is Fixed but waiting for the updated package to come out.
Is that the same issue?