Kubuntu 10.4 Segmentation Fault on Logoff,Restart,Shutdown

Bug #504375 reported by vmc on 2010-01-07
36
This bug affects 7 people
Affects Status Importance Assigned to Milestone
Ubuntu
Undecided
Unassigned

Bug Description

On every Restart, Shutdown, or Logoff there is a Segmentation fault.
I am limited on time as I have only 29 seconds to report. I am able to capture the information inside the crash dialogue.

Here's one:
Application: Plasma Workspace (kdeinit4), signal: Segmentation fault
[Current thread is 1 (Thread 0xb777c700 (LWP 1544))]

Thread 2 (Thread 0xab838b70 (LWP 1545)):
#0 0x002d2422 in __kernel_vsyscall ()
#1 0x00119e05 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/tls/i686/cmov/libpthread.so.0
#2 0x0367a2e7 in QWaitCondition::wait(QMutex*, unsigned long) () from /usr/lib/libQtCore.so.4
#3 0x017c9e82 in ?? () from /usr/lib/libQtNetwork.so.4
#4 0x0367938e in ?? () from /usr/lib/libQtCore.so.4
#5 0x0011580e in start_thread () from /lib/tls/i686/cmov/libpthread.so.0
#6 0x0039f93e in clone () from /lib/tls/i686/cmov/libc.so.6

Thread 1 (Thread 0xb777c700 (LWP 1544)):
[KCrash Handler]
#6 0x014d4535 in ?? () from /usr/lib/kde4/plasma_applet_systemtray.so
#7 0x014f37e2 in ?? () from /usr/lib/kde4/plasma_applet_systemtray.so
#8 0x014f45d6 in ?? () from /usr/lib/kde4/plasma_applet_systemtray.so
#9 0x014fa38f in ?? () from /usr/lib/kde4/plasma_applet_systemtray.so
#10 0x0377f95a in QMetaObject::metacall(QObject*, QMetaObject::Call, int, void**) () from /usr/lib/libQtCore.so.4
#11 0x0378e0db in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) () from /usr/lib/libQtCore.so.4
#12 0x014d6dc3 in ?? () from /usr/lib/kde4/plasma_applet_systemtray.so
#13 0x014d78cb in ?? () from /usr/lib/kde4/plasma_applet_systemtray.so
#14 0x014e5d94 in ?? () from /usr/lib/kde4/plasma_applet_systemtray.so
#15 0x03789eef in QObjectPrivate::deleteChildren() () from /usr/lib/libQtCore.so.4
#16 0x0379100d in QObject::~QObject() () from /usr/lib/libQtCore.so.4
#17 0x014e4135 in ?? () from /usr/lib/kde4/plasma_applet_systemtray.so
#18 0x03789eef in QObjectPrivate::deleteChildren() () from /usr/lib/libQtCore.so.4
#19 0x0379100d in QObject::~QObject() () from /usr/lib/libQtCore.so.4
#20 0x014d53c2 in ?? () from /usr/lib/kde4/plasma_applet_systemtray.so
#21 0x014f7802 in ?? () from /usr/lib/kde4/plasma_applet_systemtray.so
#22 0x02b9bea6 in Plasma::Containment::~Containment() () from /usr/lib/libplasma.so.3
#23 0x0619da0b in ?? () from /usr/lib/kde4/plasma_containment_panel.so
#24 0x02bb52be in Plasma::Corona::~Corona() () from /usr/lib/libplasma.so.3
#25 0x06b6649a in ?? () from /usr/lib/libkdeinit4_plasma-desktop.so
#26 0x06b82b8c in ?? () from /usr/lib/libkdeinit4_plasma-desktop.so
#27 0x06b87e10 in ?? () from /usr/lib/libkdeinit4_plasma-desktop.so
#28 0x0377f95a in QMetaObject::metacall(QObject*, QMetaObject::Call, int, void**) () from /usr/lib/libQtCore.so.4
#29 0x0378e0db in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) () from /usr/lib/libQtCore.so.4
#30 0x037df457 in QCoreApplication::aboutToQuit() () from /usr/lib/libQtCore.so.4
#31 0x0377d386 in QCoreApplication::exec() () from /usr/lib/libQtCore.so.4
#32 0x08711277 in QApplication::exec() () from /usr/lib/libQtGui.so.4
#33 0x06b6e0de in kdemain () from /usr/lib/libkdeinit4_plasma-desktop.so
#34 0x0804dff7 in _start ()

and another:
Application: KNetworkManager (knetworkmanager), signal: Segmentation fault
[KCrash Handler]
#6 0x0112dd92 in QWidgetPrivate::init(QWidget*, QFlags<Qt::WindowType>) () from /usr/lib/libQtGui.so.4
#7 0x0112e423 in QWidget::QWidget(QWidgetPrivate&, QWidget*, QFlags<Qt::WindowType>) () from /usr/lib/libQtGui.so.4
#8 0x0157098b in QMenu::QMenu(QString const&, QWidget*) () from /usr/lib/libQtGui.so.4
#9 0x07dee944 in ?? () from /usr/lib/qt4/plugins/inputmethods/libqimsw-multi.so
#10 0x07df026e in ?? () from /usr/lib/qt4/plugins/inputmethods/libqimsw-multi.so
#11 0x01722378 in QInputContextFactory::create(QString const&, QObject*) () from /usr/lib/libQtGui.so.4
#12 0x010ccd5a in QApplication::inputContext() const () from /usr/lib/libQtGui.so.4
#13 0x0111e698 in QWidgetPrivate::inputContext() const () from /usr/lib/libQtGui.so.4
#14 0x01121c1b in QWidget::inputContext() () from /usr/lib/libQtGui.so.4
#15 0x011796a6 in QWidget::destroy(bool, bool) () from /usr/lib/libQtGui.so.4
#16 0x011793f3 in QWidget::destroy(bool, bool) () from /usr/lib/libQtGui.so.4
#17 0x011793f3 in QWidget::destroy(bool, bool) () from /usr/lib/libQtGui.so.4
#18 0x011793f3 in QWidget::destroy(bool, bool) () from /usr/lib/libQtGui.so.4
#19 0x010dab56 in QApplication::~QApplication() () from /usr/lib/libQtGui.so.4
#20 0x00549b3a in KApplication::~KApplication() () from /usr/lib/libkdeui.so.5
#21 0x00550f28 in KUniqueApplication::~KUniqueApplication() () from /usr/lib/libkdeui.so.5
#22 0x08053ce3 in _start ()

KevinM (kevbert1) wrote :

Same problem here. I'm using Kubuntu 64bit kernel 2.8.32-9. Unfortunately I can't run Kubuntu as I immediately get the segfaults as soon as I've logged in (I'll attach a screenshot in a following post). As soon as the error windows are closed I just get a black screen and a white cursor and nothing else.
See also http://ubuntuforums.org/showthread.php?t=1359334

KevinM (kevbert1) wrote :

Attached syslog file. From Jan 7th 11.073729 things start to go wrong (Nvidia taints kernel).

KevinM (kevbert1) wrote :

Sorry, just to confirm Kubuntu kernel is -8 (and not -9). Attached screenshot of crash errors.

Asraniel (asraniel) wrote :

can you reproduce the bug with debug symbols installed? the backtrace is more or less useless like this. (except that one can see that the crash is in the systray)

Asraniel (asraniel) wrote :

you get it with kdebase-workspace-dbg
Why it is not installed in a developement version, only kubuntu developers know..

KevinM (kevbert1) wrote :

Asraniel. Can I install these debug symbols from a terminal prompt ? If so, what's the deb package ?
Thanks.

vmc (vmclark) wrote :

Kevin, here's the package name "kdebase-workspace-dbg_4%3a4.3.85-0ubuntu1_i386.deb"

vmc (vmclark) wrote :

I have it installed. I just need to know how to use it.

koso (koso) wrote :

I have the same problem ... mostly problem with knetworkmanager (at this time latest) for a long time. I was unable to get report when logging off, so I tried:

kquitapp knetworkmanager

and get:

Application: KNetworkManager (knetworkmanager), signal: Segmentation fault
[KCrash Handler]
#6 QHash<QWidget*, QHashDummyValue>::detach (this=0x911d478, parentWidget=0x0, f=...) at ../../include/QtCore/../../src/corelib/tools/qhash.h:299
#7 QHash<QWidget*, QHashDummyValue>::insert (this=0x911d478, parentWidget=0x0, f=...) at ../../include/QtCore/../../src/corelib/tools/qhash.h:749
#8 QSet<QWidget*>::insert (this=0x911d478, parentWidget=0x0, f=...) at ../../include/QtCore/../../src/corelib/tools/qset.h:176
#9 QWidgetPrivate::init (this=0x911d478, parentWidget=0x0, f=...) at kernel/qwidget.cpp:1119
#10 0x0118c423 in QWidget (this=0x8e78270, dd=..., parent=0x0, f=...) at kernel/qwidget.cpp:1039
#11 0x015ce98b in QMenu (this=0x8e78270, title=..., parent=0x0) at widgets/qmenu.cpp:1373
#12 0x04612944 in QMultiInputContext (this=0x8ec4388) at qmultiinputcontext.cpp:88
#13 0x0461426e in QMultiInputContextPlugin::create (this=0x8f8d5f8, key=...) at qmultiinputcontextplugin.cpp:83
#14 0x01780378 in QInputContextFactory::create (key=..., parent=0xbfdaa290) at inputmethod/qinputcontextfactory.cpp:160
#15 0x0112ad5a in QApplication::inputContext (this=0xbfdaa290) at kernel/qapplication.cpp:5183
#16 0x0117c698 in QWidgetPrivate::inputContext (this=0x8f8e118) at kernel/qwidget.cpp:279
#17 0x0117fc1b in QWidget::inputContext (this=0x8f8b408) at kernel/qwidget.cpp:298
#18 0x011d76a6 in QWidget::destroy (this=0x8f8b408, destroyWindow=true, destroySubWindows=true) at kernel/qwidget_x11.cpp:1100
#19 0x011d73f3 in QWidget::destroy (this=0x8f89888, destroyWindow=true, destroySubWindows=true) at kernel/qwidget_x11.cpp:1050
#20 0x011d73f3 in QWidget::destroy (this=0x8f8af50, destroyWindow=true, destroySubWindows=true) at kernel/qwidget_x11.cpp:1050
#21 0x011d73f3 in QWidget::destroy (this=0x8f85798, destroyWindow=true, destroySubWindows=true) at kernel/qwidget_x11.cpp:1050
#22 0x01138b56 in ~QApplication (this=0xbfdaa290, __in_chrg=<value optimized out>) at kernel/qapplication.cpp:1040
#23 0x0079334a in ~KApplication (this=0xbfdaa290, __in_chrg=<value optimized out>) at ../../kdeui/kernel/kapplication.cpp:896
#24 0x0079a738 in ~KUniqueApplication (this=0xbfdaa290, __in_chrg=<value optimized out>) at ../../kdeui/kernel/kuniqueapplication.cpp:372
#25 0x08053ce3 in main (argc=1, argv=0xbfdaa3e4) at ../../monolithic/main.cpp:47

vmc (vmclark) wrote :

I think it is the crash report that is now diverted to that debug symbols that I installed.

If that's the case we have a catch-22 scenario.

 On Shutdown, Logoff, or Restart, we have only 30seconds max to have that crash report capture the needed data and that is nearly enough time.

 I tried to find a way to lengthen any or all three and can't find it.

KevinM (kevbert1) wrote :

I've been able to install via tty prompt (I'm using 64 bit) and have generated the attached backtrace file.

vmc (vmclark) wrote :

Kevin, Are you sure your segmentation fault is the same as mine? I have no problem on logon.

And if you don't have seg fault on shutdown then I would say no. A differnt bug.

KevinM (kevbert1) wrote :

VMC. I think my segfault bug is different from your reported one, I did have segfaults on shutdown at one stage, but can't get that far now.
Koso. It looks like your segfault is another bug. I've also seen that one, but can't reproduce as again I can't get that far in Kubuntu any more.
I'm not sure how we should proceed.

KevinM (kevbert1) on 2010-01-15
Changed in ubuntu:
status: New → Confirmed
AdrianvV (adrianvv) wrote :

I've attached the text I get from the crash handler when running "kquitapp knetworkmanager". I get the same result on logging out. Might not be related since it's the RC.

kde4-config --version
Qt: 4.6.0
KDE Development Platform: 4.3.90 (KDE 4.3.90 (KDE 4.4 RC1))
kde4-config: 1.0

Linux brox 2.6.31-17-generic #54-Ubuntu SMP Thu Dec 10 17:01:44 UTC 2009 x86_64 GNU/Linux

vmc (vmclark) wrote :

Someone has this ALL reversed . Bug#512169 is a duplicated of this one. Bug#512169 was reported almost 3 weeks later. WTF?!

Alessandro Lanave (ingalex) wrote :

This bug affect mee too.

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

Other bug subscribers