kded4/kdeinit4 crashes with segmentation fault (segfault) after logging in in Quetzal

Bug #1073890 reported by Oliver Klee
22
This bug affects 4 people
Affects Status Importance Assigned to Milestone
colord-kde (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

I've updated my Kubuntu system from Precise Pangolin to Quantal Quetzal 12.10. The update went smooth. However, I now consistently get a segmentation fault in kded4 or kdeinit4 (one or the other) after I've logged in (using the graphic login). I can repeat this consistently by logging out and logging in again (without restarting my machine).

This is the information which I get for my crash (unfortunately, there are no additional debug symbols available for installation, it seems):

Application: KDE-Dienst (kdeinit4), signal: Segmentation fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[KCrash Handler]
#5 0x00007f08b6d1d40c in ?? () from /usr/lib/kde4/kded_colord.so
#6 0x00007f08d0f7a43e in QObject::event (this=0xf9a9b0, e=<optimized out>) at kernel/qobject.cpp:1195
#7 0x00007f08d030ce9c in QApplicationPrivate::notify_helper (this=this@entry=0xcf71c0, receiver=receiver@entry=0xf9a9b0, e=e@entry=0xfacee0) at kernel/qapplication.cpp:4562
#8 0x00007f08d031130a in QApplication::notify (this=0x7fff20f5f600, receiver=0xf9a9b0, e=0xfacee0) at kernel/qapplication.cpp:4423
#9 0x00007f08d1cde1d6 in KApplication::notify(QObject*, QEvent*) () from /usr/lib/libkdeui.so.5
#10 0x00007f08d0f6556e in QCoreApplication::notifyInternal (this=0x7fff20f5f600, receiver=receiver@entry=0xf9a9b0, event=event@entry=0xfacee0) at kernel/qcoreapplication.cpp:915
#11 0x00007f08d0f693f1 in sendEvent (event=0xfacee0, receiver=0xf9a9b0) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:231
#12 QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=0, data=0xc052b0) at kernel/qcoreapplication.cpp:1539
#13 0x00007f08d0f93a63 in sendPostedEvents () at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:236
#14 postEventSourceDispatch (s=0xcf56b0) at kernel/qeventdispatcher_glib.cpp:279
#15 0x00007f08cca63ab5 in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#16 0x00007f08cca63de8 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#17 0x00007f08cca63ea4 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#18 0x00007f08d0f93bf6 in QEventDispatcherGlib::processEvents (this=0xc077d0, flags=...) at kernel/qeventdispatcher_glib.cpp:424
#19 0x00007f08d03b1c1e in QGuiEventDispatcherGlib::processEvents (this=<optimized out>, flags=...) at kernel/qguieventdispatcher_glib.cpp:204
#20 0x00007f08d0f642bf in QEventLoop::processEvents (this=this@entry=0x7fff20f5f380, flags=...) at kernel/qeventloop.cpp:149
#21 0x00007f08d0f64548 in QEventLoop::exec (this=0x7fff20f5f380, flags=...) at kernel/qeventloop.cpp:204
#22 0x00007f08d0f69708 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1187
#23 0x00007f08bbecc3f0 in kdemain () from /usr/lib/kde4/libkdeinit/libkdeinit4_kded4.so
#24 0x00000000004085a2 in _start ()

This still occurs even if I rename my ~/.kde/ and ~/.kderc before logging in.

Revision history for this message
Oliver Klee (launchpad-oliverklee) wrote :

Removing the kde-config-tablet does not help. So this does not seem to be a duplicate of #596189.

affects: plasma-widget-networkmanagement (Ubuntu) → ubuntu
affects: ubuntu → kde4libs (Ubuntu)
Revision history for this message
Jonathan Thomas (echidnaman) wrote :

From the backtrace it looks like a crash in the colord-kde KDE daemon module.

affects: kde4libs (Ubuntu) → colord-kde (Ubuntu)
Revision history for this message
Oliver Klee (launchpad-oliverklee) wrote :

I also see the following line when calling dmesg:

[ 24.340699] kded4[3500] general protection ip:7fc546b1a40c sp:7fffb3da6640 error:0 in kded_colord.so[7fc546b07000+18000]

Revision history for this message
Daniel Nicoletti (dantti) wrote :

Does it crash if you start it from the terminal?
Did you try to reinstall colord-kde module?
Does System Settings -> Color module works for you?

This backtrace is really useless :(

Revision history for this message
Oliver Klee (launchpad-oliverklee) wrote :

Yes, it also crashes if I start it from the terminal:

klee@gonzales:~$ kded4
QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave.
QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave.
Fontconfig warning: "/etc/fonts/conf.d/50-user.conf", line 9: reading configurations from ~/.fonts.conf is deprecated.
QDBusObjectPath: invalid path "/modules/muon-notifier"
kded(10514): The kded module name ' "muon-notifier" ' is invalid!
Running Mixer_Backend destructor
Running Mixer_Backend destructor
Running Mixer_Backend destructor
Running Mixer_Backend destructor
Running Mixer_Backend destructor
Running Mixer_Backend destructor
Running Mixer_Backend destructor
Running Mixer_Backend destructor
Running Mixer_Backend destructor
Running Mixer_Backend destructor
Running Mixer_Backend destructor
Running Mixer_Backend destructor
Running Mixer_Backend destructor
Running Mixer_Backend destructor
Running Mixer_Backend destructor
Running Mixer_Backend destructor
KCrash: Attempting to start /usr/bin/kded4 from kdeinit
sock_file=/home/klee/.kde/socket-gonzales/kdeinit4__0
KCrash: Application 'kded4' crashing...
KCrash: Attempting to start /usr/lib/kde4/libexec/drkonqi from kdeinit
sock_file=/home/klee/.kde/socket-gonzales/kdeinit4__0
QSocketNotifier: Invalid socket 14 and type 'Read', disabling...

Revision history for this message
Oliver Klee (launchpad-oliverklee) wrote :

The System Settings -> Color module seems to work (at least it displays, and I can click around).

Revision history for this message
Oliver Klee (launchpad-oliverklee) wrote :

The crash does not occur after I have uninstalled colord-kde (and color), includes their configuration files.

However, if I reinstall colord-kde, I get the crash again.

Revision history for this message
Daniel Nicoletti (dantti) wrote :

ok,
please add this repo:
deb http://ddebs.ubuntu.com quantal main restricted universe multiverse
then install colord-kde-dbgsym, and please run:
gdb kded4 --nofork
run

when it crashes type: bt
and paste the new backtrace here.

Thanks.

Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in colord-kde (Ubuntu):
status: New → Confirmed
Revision history for this message
Henrik Harmsen (henrik-harmsen) wrote :
Download full text (5.0 KiB)

Same here.
This is on 12.10 kubuntu. Logging in via nomachine nx.

More backtrace from the crash deamon:

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 0x7f156e7e2780 (LWP 20953))]

Thread 2 (Thread 0x7f155c029700 (LWP 20955)):
#0 0x00007f15739dd303 in poll () from /lib/x86_64-linux-gnu/libc.so.6
#1 0x00007f15708d9d84 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2 0x00007f15708d9ea4 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3 0x00007f1574e09c16 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#4 0x00007f1574dda2bf in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#5 0x00007f1574dda548 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#6 0x00007f1574cdbb10 in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#7 0x00007f1574dbc478 in ?? () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#8 0x00007f1574cdeaec in ?? () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#9 0x00007f15711b2e9a in start_thread () from /lib/x86_64-linux-gnu/libpthread.so.0
#10 0x00007f15739e8cbd in clone () from /lib/x86_64-linux-gnu/libc.so.6
#11 0x0000000000000000 in ?? ()

Thread 1 (Thread 0x7f156e7e2780 (LWP 20953)):
[KCrash Handler]
#5 0x00007f157397859c in free () from /lib/x86_64-linux-gnu/libc.so.6
#6 0x00007f15756379a9 in XFree () from /usr/lib/x86_64-linux-gnu/libX11.so.6
#7 0x00007f156148f7a6 in XRRUpdateConfiguration () from /usr/lib/x86_64-linux-gnu/libXrandr.so.2
#8 0x00007f1559e7befc in ?? () from /usr/lib/kde4/kded_wacomtablet.so
#9 0x00007f1575b56f1e in KApplication::x11EventFilter(_XEvent*) () from /usr/lib/libkdeui.so.5
#10 0x00007f15741ef7bc in ?? () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4
#11 0x00007f15741ff7f0 in QApplication::x11ProcessEvent(_XEvent*) () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4
#12 0x00007f1574227fa2 in ?? () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4
#13 0x00007f15708d9ab5 in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#14 0x00007f15708d9de8 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#15 0x00007f15708d9ea4 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#16 0x00007f1574e09bf6 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#17 0x00007f1574227c1e in ?? () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4
#18 0x00007f1574dda2bf in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#19 0x00007f1574dda548 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#20 0x00007f1572156bc6 in ?? () from /usr/lib/x86_64-linux-gnu/libQtDBus.so.4
#21 0x00007f15721447fb in QDBusConnection::call(QDBusMessage const&, QDBus::CallMode, int) const () from /usr/lib/x86_64-linux-gnu/libQtDBus.so.4
#22 0x0000...

Read more...

Revision history for this message
Henrik Harmsen (henrik-harmsen) wrote :
Download full text (6.3 KiB)

I uninstalled colord-kde and now I got this instead:

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 0x7f44ddbea780 (LWP 21904))]

Thread 5 (Thread 0x7f44cb431700 (LWP 21906)):
#0 0x00007f44e05be05d in pthread_mutex_unlock () from /lib/x86_64-linux-gnu/libpthread.so.0
#1 0x00007f44dfd1ee51 in g_mutex_unlock () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2 0x00007f44dfce1c5c in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3 0x00007f44dfce1ea4 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#4 0x00007f44e4211c16 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#5 0x00007f44e41e22bf in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#6 0x00007f44e41e2548 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#7 0x00007f44e40e3b10 in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#8 0x00007f44e41c4478 in ?? () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#9 0x00007f44e40e6aec in ?? () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#10 0x00007f44e05bae9a in start_thread () from /lib/x86_64-linux-gnu/libpthread.so.0
#11 0x00007f44e2df0cbd in clone () from /lib/x86_64-linux-gnu/libc.so.6
#12 0x0000000000000000 in ?? ()

Thread 4 (Thread 0x7f44bfcfe700 (LWP 21918)):
#0 0x00007f44e05bcf69 in pthread_mutex_lock () from /lib/x86_64-linux-gnu/libpthread.so.0
#1 0x00007f44dfd1ee21 in g_mutex_lock () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2 0x00007f44dfce1193 in g_main_context_release () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3 0x00007f44dfce1d35 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#4 0x00007f44dfce21e2 in g_main_loop_run () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#5 0x00007f44bffea4a6 in ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
#6 0x00007f44dfd05645 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#7 0x00007f44e05bae9a in start_thread () from /lib/x86_64-linux-gnu/libpthread.so.0
#8 0x00007f44e2df0cbd in clone () from /lib/x86_64-linux-gnu/libc.so.6
#9 0x0000000000000000 in ?? ()

Thread 3 (Thread 0x7f44bf2f1700 (LWP 21921)):
#0 0x00007f44e2de5303 in poll () from /lib/x86_64-linux-gnu/libc.so.6
#1 0x00007f44dfce1d84 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2 0x00007f44dfce1ea4 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3 0x00007f44e4211c16 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#4 0x00007f44e41e22bf in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#5 0x00007f44e41e2548 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#6 0x00007f44e40e3b10 in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#7 0x00007f44c8872352 in KCupsConnection::run() () from /...

Read more...

Revision history for this message
Henrik Harmsen (henrik-harmsen) wrote :

Also got this:

Application: KWin (kwin), signal: Segmentation fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[KCrash Handler]
#5 0x00007f5decb7259c in free () from /lib/x86_64-linux-gnu/libc.so.6
#6 0x00007f5deaca69a9 in XFree () from /usr/lib/x86_64-linux-gnu/libX11.so.6
#7 0x00007f5dea8477a6 in XRRUpdateConfiguration () from /usr/lib/x86_64-linux-gnu/libXrandr.so.2
#8 0x00007f5decf1cee0 in ?? () from /usr/lib/kde4/libkdeinit/libkdeinit4_kwin.so
#9 0x00007f5decf0e848 in ?? () from /usr/lib/kde4/libkdeinit/libkdeinit4_kwin.so
#10 0x00007f5de7c727bc in ?? () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4
#11 0x00007f5de7c827f0 in QApplication::x11ProcessEvent(_XEvent*) () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4
#12 0x00007f5de7cab9d9 in ?? () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4
#13 0x00007f5de885d2bf in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#14 0x00007f5de885d548 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#15 0x00007f5de8862708 in QCoreApplication::exec() () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#16 0x00007f5decf10ed4 in kdemain () from /usr/lib/kde4/libkdeinit/libkdeinit4_kwin.so
#17 0x00007f5decb1076d in __libc_start_main () from /lib/x86_64-linux-gnu/libc.so.6
#18 0x00000000004006d1 in _start ()

Maybe this is a variant of
https://bugs.launchpad.net/bugs/985202

Revision history for this message
Henrik Harmsen (henrik-harmsen) wrote :

kdeinit4 stopped crashing after I switched from nx to x2go. So it seems I was actually bitten by https://bugs.launchpad.net/bugs/985202 even though it looked like it was this bug. However, maybe others have the same problem with this bug.,

Revision history for this message
Bill Weinel (bweinel) wrote :
Download full text (13.4 KiB)

kded4 in saucy salamander crashes immediatly after logging in and getting to the desktop.

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

Thread 6 (Thread 0x7f613fd68700 (LWP 1904)):
#0 0x00007f6158333f7d in poll () at ../sysdeps/unix/syscall-template.S:81
#1 0x00007f61554406a4 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2 0x00007f61554407ac in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3 0x00007f615976ba76 in QEventDispatcherGlib::processEvents (this=0x7f61380008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:426
#4 0x00007f615973d5ef in QEventLoop::processEvents (this=this@entry=0x7f613fd67db0, flags=...) at kernel/qeventloop.cpp:149
#5 0x00007f615973d8e5 in QEventLoop::exec (this=this@entry=0x7f613fd67db0, flags=...) at kernel/qeventloop.cpp:204
#6 0x00007f615963c88f in QThread::exec (this=<optimized out>) at thread/qthread.cpp:542
#7 0x00007f615963ef2f in QThreadPrivate::start (arg=0x16de170) at thread/qthread_unix.cpp:338
#8 0x00007f6155b1bf6e in start_thread (arg=0x7f613fd68700) at pthread_create.c:311
#9 0x00007f61583409cd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:113

Thread 5 (Thread 0x7f612f43b700 (LWP 1915)):
#0 0x00007f6158333f7d in poll () at ../sysdeps/unix/syscall-template.S:81
#1 0x00007f61554406a4 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2 0x00007f6155440b0a in g_main_loop_run () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3 0x00007f612f936b66 in ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
#4 0x00007f61554650f5 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#5 0x00007f6155b1bf6e in start_thread (arg=0x7f612f43b700) at pthread_create.c:311
#6 0x00007f61583409cd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:113

Thread 4 (Thread 0x7f612ea2e700 (LWP 1916)):
#0 0x00007f6155b1f05f in __pthread_mutex_unlock_usercnt (mutex=0x7f611c000a60, decr=<optimized out>) at pthread_mutex_unlock.c:52
#1 0x00007f61554803d1 in g_mutex_unlock () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2 0x00007f615543f830 in g_main_context_acquire () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3 0x00007f6155440565 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#4 0x00007f61554407ac in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#5 0x00007f615976ba76 in QEventDispatcherGlib::processEvents (this=0x7f611c0008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:426
#6 0x00007f615973d5ef in QEventLoop::processEvents (this=this@entry=0x7f612ea2dd70, flags=...) at kernel/qeventloop.cpp:149
#7 0x00007f615973d8e5 in QEventLoop::exec (this=this@entry=0x7f612ea2dd70, flags=...) at kernel/qeventloop.cpp:204
#8 0x00007f615963c88f in QThread::exec (this=<optimized out>) at thread/qthread.cpp:542
#9 0x00007f613d374fd7 in KCupsConnection::run() () from /usr/lib/libkcupslib.so
#10 0x00007f615963ef2f in QThreadPrivate::start (arg=0x1710170) at thread/qthread_unix.cpp:338
#11 0x00007f6155b1bf6e in s...

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.