Bug 289165

Summary: kded crashed when I resumed from suspend to ram
Product: [Unmaintained] kdelibs Reporter: MartinG <gronslet>
Component: kdedAssignee: Unassigned bugs mailing-list <unassigned-bugs>
Status: RESOLVED DUPLICATE    
Severity: crash CC: lamarque
Priority: NOR    
Version: unspecified   
Target Milestone: ---   
Platform: Fedora RPMs   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description MartinG 2011-12-17 07:54:05 UTC
Application: kded4 ($Id$)
KDE Platform Version: 4.7.3 (4.7.3)
Qt Version: 4.8.0
Operating System: Linux 3.1.5-2.fc16.x86_64 x86_64
Distribution: "Fedora release 16 (Verne)"

-- Information about the crash:
- What I was doing when the application crashed:
Put laptop to suspend, then resumed. kded crashed. Was connected to wifi.

-- Backtrace:
Application: KDE Daemon (kded4), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
82	T_PSEUDO (SYSCALL_SYMBOL, SYSCALL_NAME, SYSCALL_NARGS)
[Current thread is 1 (Thread 0x7f6069a5b840 (LWP 1618))]

Thread 2 (Thread 0x7f605ccac700 (LWP 1631)):
#0  0x0000003354ce6a43 in __GI___poll (fds=<optimized out>, nfds=<optimized out>, timeout=<optimized out>) at ../sysdeps/unix/sysv/linux/poll.c:87
#1  0x0000003356c44f88 in g_main_context_poll (n_fds=1, fds=0x7f6050002250, priority=<optimized out>, timeout=-1, context=0x7f60500009a0) at gmain.c:3386
#2  g_main_context_iterate (context=0x7f60500009a0, block=<optimized out>, dispatch=1, self=<optimized out>) at gmain.c:3068
#3  0x0000003356c4544c in g_main_context_iteration (context=0x7f60500009a0, may_block=1) at gmain.c:3136
#4  0x000000335f9a6896 in QEventDispatcherGlib::processEvents (this=0x7f60500008c0, flags=<optimized out>) at kernel/qeventdispatcher_glib.cpp:426
#5  0x000000335f976c82 in QEventLoop::processEvents (this=<optimized out>, flags=...) at kernel/qeventloop.cpp:149
#6  0x000000335f976ed7 in QEventLoop::exec (this=0x7f605ccabd10, flags=...) at kernel/qeventloop.cpp:204
#7  0x000000335f878ad7 in QThread::exec (this=<optimized out>) at thread/qthread.cpp:501
#8  0x000000335f956a5f in QInotifyFileSystemWatcherEngine::run (this=0x23c8ba0) at io/qfilesystemwatcher_inotify.cpp:248
#9  0x000000335f87bb1b in QThreadPrivate::start (arg=0x23c8ba0) at thread/qthread_unix.cpp:298
#10 0x0000003355807d90 in start_thread (arg=0x7f605ccac700) at pthread_create.c:309
#11 0x0000003354cef3dd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:115

Thread 1 (Thread 0x7f6069a5b840 (LWP 1618)):
[KCrash Handler]
#6  QDBusAbstractInterface::asyncCallWithArgumentList (this=0x24f5470, method=..., args=...) at qdbusabstractinterface.cpp:495
#7  0x00007f605d6d9a78 in UnregisterAgent (in0=..., this=0x24f5470) at /usr/src/debug/libbluedevil-v1.9/x86_64-redhat-linux-gnu/bluedevil/bluezadapter.h:128
#8  BlueDevil::Adapter::unregisterAgent (this=<optimized out>, agentPath=<optimized out>) at /usr/src/debug/libbluedevil-v1.9/bluedevil/bluedeviladapter.cpp:364
#9  0x00007f605d4ba1d8 in AgentListenerWorker::unregister (this=0x7f6058002bf0) at /usr/src/debug/bluedevil-1.2.2/src/daemon/kded/agentlistenerworker.cpp:52
#10 0x00007f605d4b9c5b in AgentListener::~AgentListener (this=0x26cd960, __in_chrg=<optimized out>) at /usr/src/debug/bluedevil-1.2.2/src/daemon/kded/agentlistener.cpp:31
#11 0x00007f605d4b9c79 in AgentListener::~AgentListener (this=0x26cd960, __in_chrg=<optimized out>) at /usr/src/debug/bluedevil-1.2.2/src/daemon/kded/agentlistener.cpp:32
#12 0x000000335f990a18 in QObject::event (this=0x26cd960, e=<optimized out>) at kernel/qobject.cpp:1175
#13 0x0000003362dc96f4 in notify_helper (e=0x2926e70, receiver=0x26cd960, this=0x2111d60) at kernel/qapplication.cpp:4518
#14 QApplicationPrivate::notify_helper (this=0x2111d60, receiver=0x26cd960, e=0x2926e70) at kernel/qapplication.cpp:4490
#15 0x0000003362dce573 in QApplication::notify (this=0x7fff3678f820, receiver=0x26cd960, e=0x2926e70) at kernel/qapplication.cpp:4379
#16 0x0000003364c50396 in KApplication::notify (this=0x7fff3678f820, receiver=0x26cd960, event=0x2926e70) at /usr/src/debug/kdelibs-4.7.3/kdeui/kernel/kapplication.cpp:311
#17 0x000000335f977b4c in QCoreApplication::notifyInternal (this=0x7fff3678f820, receiver=0x26cd960, event=0x2926e70) at kernel/qcoreapplication.cpp:876
#18 0x000000335f97b5da in sendEvent (event=0x2926e70, receiver=0x26cd960) at kernel/qcoreapplication.h:231
#19 QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=0, data=0x20dc4d0) at kernel/qcoreapplication.cpp:1500
#20 0x000000335f9a6403 in sendPostedEvents () at kernel/qcoreapplication.h:236
#21 postEventSourceDispatch (s=0x2115770) at kernel/qeventdispatcher_glib.cpp:279
#22 0x0000003356c44a7d in g_main_dispatch (context=0x21148e0) at gmain.c:2425
#23 g_main_context_dispatch (context=0x21148e0) at gmain.c:2995
#24 0x0000003356c45278 in g_main_context_iterate (context=0x21148e0, block=<optimized out>, dispatch=1, self=<optimized out>) at gmain.c:3073
#25 0x0000003356c4544c in g_main_context_iteration (context=0x21148e0, may_block=1) at gmain.c:3136
#26 0x000000335f9a682f in QEventDispatcherGlib::processEvents (this=0x20dd990, flags=<optimized out>) at kernel/qeventdispatcher_glib.cpp:424
#27 0x0000003362e6c43e in QGuiEventDispatcherGlib::processEvents (this=<optimized out>, flags=<optimized out>) at kernel/qguieventdispatcher_glib.cpp:207
#28 0x000000335f976c82 in QEventLoop::processEvents (this=<optimized out>, flags=...) at kernel/qeventloop.cpp:149
#29 0x000000335f976ed7 in QEventLoop::exec (this=0x7fff3678f7b0, flags=...) at kernel/qeventloop.cpp:204
#30 0x000000335f97b8d5 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1148
#31 0x0000003360a08de5 in kdemain (argc=1, argv=0x7fff3678fbf8) at /usr/src/debug/kdelibs-4.7.3/kded/kded.cpp:924
#32 0x0000003354c2169d in __libc_start_main (main=0x400710 <main(int, char**)>, argc=1, ubp_av=0x7fff3678fbf8, init=<optimized out>, fini=<optimized out>, rtld_fini=<optimized out>, stack_end=0x7fff3678fbe8) at libc-start.c:226
#33 0x0000000000400741 in _start ()

This bug may be a duplicate of or related to bug 283365.

Possible duplicates by query: bug 284328, bug 283365.

Reported using DrKonqi
Comment 1 MartinG 2011-12-17 07:57:24 UTC
I see that the possibly related bug 283365 mentions bluedevil. Before entering suspend, I had been using bluetooth, and the laptop might have been connected with my mobile when entering suspend. Bluetooth on my mobile was turned off when the laptop came out of suspend.
Comment 2 Lamarque V. Souza 2011-12-17 14:10:02 UTC

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