Bug 261351 - KDE config tool (System Settings) crashes producing a Segment fault in X.
Summary: KDE config tool (System Settings) crashes producing a Segment fault in X.
Status: RESOLVED DUPLICATE of bug 225404
Alias: None
Product: kpackagekit
Classification: Frameworks and Libraries
Component: general (show other bugs)
Version: unspecified
Platform: Fedora RPMs Linux
: NOR crash
Target Milestone: ---
Assignee: Steven M. Parrish
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-12-27 08:49 UTC by George R. Goffe
Modified: 2012-07-06 14:51 UTC (History)
4 users (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 George R. Goffe 2010-12-27 08:49:53 UTC
Application: systemsettings (1.0)
KDE Platform Version: 4.5.4 (KDE 4.5.4)
Qt Version: 4.7.1
Operating System: Linux 2.6.35.10-74.fc14.i686 i686
Distribution (Platform): Fedora RPMs

-- Information about the crash:
configuring kde. I tried to select KWin in the keyboard shortcuts section when pow! I have been having troubles with the config application all night. Numerous core files from X.

-- Backtrace:
Application: System Settings (systemsettings), signal: Segmentation fault
[Current thread is 1 (Thread 0xb788c780 (LWP 10766))]

Thread 2 (Thread 0xabd1ab70 (LWP 10775)):
#0  0x00f13416 in __kernel_vsyscall ()
#1  0x006d9b06 in poll () from /lib/libc.so.6
#2  0x008a2dac in g_poll (fds=0xab400cc0, nfds=3, timeout=-1) at gpoll.c:132
#3  0x008928b7 in g_main_context_poll (context=0x9fa4cf0, block=1, dispatch=1, self=<value optimized out>) at gmain.c:3093
#4  g_main_context_iterate (context=0x9fa4cf0, block=1, dispatch=1, self=<value optimized out>) at gmain.c:2775
#5  0x0089304b in g_main_loop_run (loop=0x9fa4d70) at gmain.c:2988
#6  0x01130ed5 in gdbus_shared_thread_func (data=0x0) at gdbusprivate.c:277
#7  0x008bbbd0 in g_thread_create_proxy (data=0x9fa4d80) at gthread.c:1897
#8  0x007aaf19 in start_thread () from /lib/libpthread.so.0
#9  0x006e4c4e in clone () from /lib/libc.so.6

Thread 1 (Thread 0xb788c780 (LWP 10766)):
[KCrash Handler]
#7  0x02db5e16 in isSignalConnected (sender=0x9b36af8, m=0x11ea444, local_signal_index=9, argv=0xbf858a24) at kernel/qobject_p.h:220
#8  QMetaObject::activate (sender=0x9b36af8, m=0x11ea444, local_signal_index=9, argv=0xbf858a24) at kernel/qobject.cpp:3195
#9  0x011c3d7a in PackageKit::Transaction::finished (this=0x9b36af8, _t1=PackageKit::Enum::ExitFailed, _t2=0) at transaction.moc:203
#10 0x011bfcd0 in PackageKit::ClientPrivate::serviceUnregistered (this=0x9de3cd0) at clientprivate.cpp:75
#11 0x011c0160 in PackageKit::ClientPrivate::qt_metacall (this=0x9de3cd0, _c=QMetaObject::InvokeMetaMethod, _id=<value optimized out>, _a=0xbf858b98) at clientprivate.moc:75
#12 0x02da6b6b in QMetaObject::metacall (object=0x9de3cd0, cl=QMetaObject::InvokeMetaMethod, idx=5, argv=0xbf858b98) at kernel/qmetaobject.cpp:237
#13 0x02db6047 in QMetaObject::activate (sender=0x9ec3f30, m=0x2f9b7c4, local_signal_index=1, argv=0xbf858b98) at kernel/qobject.cpp:3272
#14 0x02f7ef84 in QDBusServiceWatcher::serviceUnregistered (this=0x9ec3f30, _t1=...) at .moc/release-shared/moc_qdbusservicewatcher.cpp:139
#15 0x02f7f067 in QDBusServiceWatcherPrivate::_q_serviceOwnerChanged (this=0x9ec3f40, service=..., oldOwner=..., newOwner=...) at qdbusservicewatcher.cpp:86
#16 0x02f7fa8e in QDBusServiceWatcher::qt_metacall (this=0x9ec3f30, _c=QMetaObject::InvokeMetaMethod, _id=3, _a=0xbf858d3c) at .moc/release-shared/moc_qdbusservicewatcher.cpp:91
#17 0x02f40a15 in QDBusConnectionPrivate::deliverCall (this=0x9fa6928, object=0x9ec3f30, msg=..., metaTypes=..., slotIdx=7) at qdbusintegrator.cpp:919
#18 0x02f4c3f8 in QDBusCallDeliveryEvent::placeMetaCall (this=0x9944360, object=0x9ec3f30) at qdbusintegrator_p.h:103
#19 0x02db5b4f in QObject::event (this=0x9ec3f30, e=0x9944360) at kernel/qobject.cpp:1211
#20 0x0373b26c in QApplicationPrivate::notify_helper (this=0x990fac8, receiver=0x9ec3f30, e=0x9944360) at kernel/qapplication.cpp:4445
#21 0x0373fed2 in QApplication::notify (this=0xbf8595dc, receiver=0x9ec3f30, e=0x9944360) at kernel/qapplication.cpp:3845
#22 0x04279f7b in KApplication::notify (this=0xbf8595dc, receiver=0x9ec3f30, event=0x9944360) at /usr/src/debug/kdelibs-4.5.4/kdeui/kernel/kapplication.cpp:310
#23 0x02da0333 in QCoreApplication::notifyInternal (this=0xbf8595dc, receiver=0x9ec3f30, event=0x9944360) at kernel/qcoreapplication.cpp:732
#24 0x02da4085 in sendEvent (receiver=0x0, event_type=0, data=0x98e28a8) at kernel/qcoreapplication.h:215
#25 QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=0, data=0x98e28a8) at kernel/qcoreapplication.cpp:1373
#26 0x02da425e in QCoreApplication::sendPostedEvents (receiver=0x0, event_type=0) at kernel/qcoreapplication.cpp:1266
#27 0x02dcdeb5 in sendPostedEvents (s=0x9906790) at kernel/qcoreapplication.h:220
#28 postEventSourceDispatch (s=0x9906790) at kernel/qeventdispatcher_glib.cpp:277
#29 0x00892192 in g_main_dispatch (context=0x9906710) at gmain.c:2149
#30 g_main_context_dispatch (context=0x9906710) at gmain.c:2702
#31 0x00892978 in g_main_context_iterate (context=0x9906710, block=1, dispatch=1, self=<value optimized out>) at gmain.c:2780
#32 0x00892c35 in g_main_context_iteration (context=0x9906710, may_block=1) at gmain.c:2843
#33 0x02dce02d in QEventDispatcherGlib::processEvents (this=0x98e2358, flags=...) at kernel/qeventdispatcher_glib.cpp:415
#34 0x037ee406 in QGuiEventDispatcherGlib::processEvents (this=0x98e2358, flags=...) at kernel/qguieventdispatcher_glib.cpp:207
#35 0x02d9f4ca in QEventLoop::processEvents (this=0xbf859534, flags=...) at kernel/qeventloop.cpp:149
#36 0x02d9f77a in QEventLoop::exec (this=0xbf859534, flags=...) at kernel/qeventloop.cpp:201
#37 0x02da4327 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1009
#38 0x03739078 in QApplication::exec () at kernel/qapplication.cpp:3719
#39 0x080571d8 in main (argc=) at /usr/src/debug/kdebase-workspace-4.5.4/systemsettings/app/main.cpp:49

Reported using DrKonqi
Comment 1 Dario Andres 2010-12-27 13:03:02 UTC
[Comment from a bug triager]
The backtrace looks related to the one in bug 225494, but it is not exactly the same.
Regards
Comment 2 George R. Goffe 2011-01-22 06:58:12 UTC
Howdy,

Do we have any status of this bug? I'm still getting crashes.

Regards,

George...
Comment 3 Jekyll Wu 2012-07-06 14:51:22 UTC

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