Bug 301665

Summary: Crashes after resume from Suspend-to-RAM
Product: [Unmaintained] kdelibs Reporter: Zilvinas Valinskas <zilvinas.valinskas>
Component: kdedAssignee: Unassigned bugs mailing-list <unassigned-bugs>
Status: RESOLVED WORKSFORME    
Severity: crash CC: cfeck, james.ellis
Priority: NOR    
Version: unspecified   
Target Milestone: ---   
Platform: Ubuntu   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description Zilvinas Valinskas 2012-06-11 16:40:34 UTC 
Application: kded4 ($Id$)
KDE Platform Version: 4.8.3 (4.8.3)
Qt Version: 4.8.1
Operating System: Linux 3.2.0-24-generic x86_64
Distribution: Ubuntu 12.04 LTS

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

Waking up laptop from 'Suspend-to-RAM'. Sometimes crashes.  Does not happen everytime. Most of the time Suspend-Resume works just fine.

The crash can be reproduced some of the time.

-- Backtrace:
Application: KDE Daemon (kdeinit4), signal: Segmentation fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f94a9cc9780 (LWP 1703))]

Thread 3 (Thread 0x7f948db3a700 (LWP 1712)):
#0  0x00007f94a74f9b03 in __GI___poll (fds=<optimized out>, nfds=<optimized out>, timeout=<optimized out>) at ../sysdeps/unix/sysv/linux/poll.c:87
#1  0x00007f94a4825ff6 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x00007f94a4826124 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x00007f94a8948426 in QEventDispatcherGlib::processEvents (this=0x7f94800008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:426
#4  0x00007f94a8917c82 in QEventLoop::processEvents (this=<optimized out>, flags=...) at kernel/qeventloop.cpp:149
#5  0x00007f94a8917ed7 in QEventLoop::exec (this=0x7f948db39dd0, flags=...) at kernel/qeventloop.cpp:204
#6  0x00007f94a8816fa7 in QThread::exec (this=<optimized out>) at thread/qthread.cpp:501
#7  0x00007f94a88f79ff in QInotifyFileSystemWatcherEngine::run (this=0x1127010) at io/qfilesystemwatcher_inotify.cpp:248
#8  0x00007f94a8819fcb in QThreadPrivate::start (arg=0x1127010) at thread/qthread_unix.cpp:298
#9  0x00007f94a4ee6e9a in start_thread (arg=0x7f948db3a700) at pthread_create.c:308
#10 0x00007f94a75054bd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112
#11 0x0000000000000000 in ?? ()

Thread 2 (Thread 0x7f948e33b700 (LWP 20501)):
[KCrash Handler]
#6  unlockInline (this=0x16e6ee8) at ../../include/QtCore/../../src/corelib/thread/qmutex.h:169
#7  unlock (this=0x7f948e33adb0) at ../../include/QtCore/../../src/corelib/thread/qmutex.h:121
#8  unlock (this=0x7f948e33adb0) at kernel/qeventloop.cpp:175
#9  ~QMutexLocker (this=0x7f948e33adb0, __in_chrg=<optimized out>) at ../../include/QtCore/../../src/corelib/thread/qmutex.h:115
#10 QEventLoop::exec (this=<optimized out>, flags=...) at kernel/qeventloop.cpp:230
#11 0x00007f94a8816fa7 in QThread::exec (this=<optimized out>) at thread/qthread.cpp:501
#12 0x00007f94a8819fcb in QThreadPrivate::start (arg=0x15d6530) at thread/qthread_unix.cpp:298
#13 0x00007f94a4ee6e9a in start_thread (arg=0x7f948e33b700) at pthread_create.c:308
#14 0x00007f94a75054bd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112
#15 0x0000000000000000 in ?? ()

Thread 1 (Thread 0x7f94a9cc9780 (LWP 1703)):
#0  0x00007f94a74f80bd in read () at ../sysdeps/unix/syscall-template.S:82
#1  0x00007f94a486088f in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x00007f94a4825abd in g_main_context_check () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x00007f94a4825f96 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x00007f94a4826124 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#5  0x00007f94a89483bf in QEventDispatcherGlib::processEvents (this=0xe8d7d0, flags=...) at kernel/qeventdispatcher_glib.cpp:424
#6  0x00007f94a7d43d5e in QGuiEventDispatcherGlib::processEvents (this=<optimized out>, flags=...) at kernel/qguieventdispatcher_glib.cpp:204
#7  0x00007f94a8917c82 in QEventLoop::processEvents (this=<optimized out>, flags=...) at kernel/qeventloop.cpp:149
#8  0x00007f94a8917ed7 in QEventLoop::exec (this=0x7fff426e7500, flags=...) at kernel/qeventloop.cpp:204
#9  0x00007f94a891cf67 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1148
#10 0x00007f94951abe55 in kdemain (argc=1, argv=0xf02780) at ../../kded/kded.cpp:924
#11 0x00000000004086a4 in launch (argc=1, _name=0x40b497 "kded4", args=<optimized out>, cwd=0x0, envc=<optimized out>, envs=<optimized out>, reset_env=false, tty=0x0, avoid_loops=false, startup_id_str=0x40b31e "0") at ../../kinit/kinit.cpp:746
#12 0x0000000000405a59 in main (argc=4, argv=0x7fff00000001, envp=0x7fff426e8700) at ../../kinit/kinit.cpp:1861

Reported using DrKonqi
Comment 1 Christoph Feck 2012-06-11 18:26:20 UTC 
If this can be reproduced, please try disabling kded modules to find out which of them causes the crash. For more information about kded4, please see http://kdepepo.wordpress.com/2011/05/11/troubleshooting-kded4-bugs/
Comment 2 Zilvinas Valinskas 2012-06-11 19:40:01 UTC 
This crash might happen before Suspend-To-RAM ... Not after resume from Suspend-To-RAM. Still .. I can't reproduce it everytime. Most of the time there is
no problem at all. Still what I have observed in the past it might be kmix + skype
... and kmixd ?

I'm no expert on KDE but i find it strange that there are no command line arguments
visible anywhere in crash report generated by KDE crash handler. Maybe kded starts services with different options (?).
Comment 3 Andrew Crouthamel 2018-10-29 22:42:10 UTC 
Dear Bug Submitter,

This bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? I am setting the status to NEEDSINFO pending your response, please change the Status back to REPORTED when you respond.

Thank you for helping us make KDE software even better for everyone!
Comment 4 Bug Janitor Service 2018-11-13 14:38:26 UTC 
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 5 Bug Janitor Service 2018-11-29 09:40:11 UTC 
This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!