After resume from Suspend, kdeinit4 sometimes crashes

Bug #1335577 reported by Scott Pitcher on 2014-06-29
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Ubuntu
Undecided
Unassigned

Bug Description

Happens maybe every so often. We suspend this desktop several times a day. Maybe once every few weeks, following a resume, I see a dialog indicating that kdeinit4 has crashed. After this, my suspend and hibernate buttons are missing. I can still suspend the machine using "sudo pm-suspend". This works except of course that kde doesn't make the suspend noise.

The debug from the dialog ....

Application: KDE Daemon (kdeinit4), signal: Aborted
[Current thread is 0 (LWP 5374)]

Thread 4 (Thread 0xaf02ab40 (LWP 5394)):
#0 0xb5fd7d53 in ?? () from /lib/i386-linux-gnu/libc.so.6
#1 0xb5fa96a8 in pthread_mutex_lock () from /lib/i386-linux-gnu/libc.so.6
#2 0xb599e3f0 in g_mutex_lock () from /lib/i386-linux-gnu/libglib-2.0.so.0
#3 0xb595f1aa in g_main_context_iteration () from /lib/i386-linux-gnu/libglib-2.0.so.0
#4 0xb6dbd8e7 in QEventDispatcherGlib::processEvents () from /usr/lib/i386-linux-gnu/libQtCore.so.4
#5 0xae7004e0 in ?? ()
#6 0x00000001 in ?? ()
#7 0xb6ee8ff4 in ?? () from /usr/lib/i386-linux-gnu/libQtCore.so.4
#8 0xb6d89c50 in ?? () from /usr/lib/i386-linux-gnu/libQtCore.so.4
#9 0xb6d89e08 in ?? () from /usr/lib/i386-linux-gnu/libQtCore.so.4
#10 0xb6d897a9 in QEventLoop::exec () from /usr/lib/i386-linux-gnu/libQtCore.so.4
#11 0xb6c7294c in QThread::exec () from /usr/lib/i386-linux-gnu/libQtCore.so.4
#12 0xaf02a240 in ?? ()
#13 0xaf02a24c in ?? ()
#14 0x00000000 in ?? ()

Thread 3 (Thread 0xae56eb40 (LWP 5399)):
#0 0xb7760424 in __kernel_vsyscall ()
#1 0xb5f64d06 in nanosleep () from /lib/i386-linux-gnu/libc.so.6
#2 0xb5f64aff in sleep () from /lib/i386-linux-gnu/libc.so.6
#3 0xb754e3fe in ?? () from /usr/lib/libkdeui.so.5
#4 0x00000001 in ?? ()
#5 0x00000000 in ?? ()

Thread 2 (Thread 0xa88ffb40 (LWP 8273)):
#0 0xb7760424 in __kernel_vsyscall ()
#1 0xb5a2c5a2 in __lll_lock_wait () from /lib/i386-linux-gnu/libpthread.so.0
#2 0xb5a27ecb in _L_lock_891 () from /lib/i386-linux-gnu/libpthread.so.0
#3 0xb5a27e60 in pthread_mutex_lock () from /lib/i386-linux-gnu/libpthread.so.0
#4 0x00000000 in ?? ()

Thread 1 (Thread 0xb566b740 (LWP 5374)):
#0 0xb599e963 in g_private_get () from /lib/i386-linux-gnu/libglib-2.0.so.0
#1 0xb5982c44 in g_thread_self () from /lib/i386-linux-gnu/libglib-2.0.so.0
#2 0xb595e177 in g_main_context_acquire () from /lib/i386-linux-gnu/libglib-2.0.so.0
#3 0xb595ef18 in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
#4 0xb595f52b in g_main_loop_run () from /lib/i386-linux-gnu/libglib-2.0.so.0
#5 0xae6ed93c in polkit_authority_check_authorization_sync () from /usr/lib/i386-linux-gnu/libpolkit-gobject-1.so.0
#6 0x096aef78 in ?? ()
#7 0x0847d680 in ?? ()
#8 0x0a273f98 in ?? ()
#9 0x00000000 in ?? ()

scotty@officepc:~/.adobe$ cat /etc/issue
Ubuntu 12.04.4 LTS \n \l

Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general. It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it. You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage. You might also ask for help in the #ubuntu-bugs irc channel on Freenode.

To change the source package that this bug is filed about visit https://bugs.launchpad.net/ubuntu/+bug/1335577/+editstatus and add the package name in the text box next to the word Package.

[This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.]

tags: added: bot-comment
Changed in ubuntu:
status: New → Confirmed
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers