FAQ Search Today's Posts Mark Forums Read
» Video Reviews

» Linux Archive

Linux-archive is a website aiming to archive linux email lists and to make them easily accessible for linux users/developers.

» Sponsor

» Partners

» Sponsor

Go Back   Linux Archive > Debian > Debian KDE

LinkBack Thread Tools
Old 04-05-2012, 03:26 PM
Gerhard Horecky
Default Parallel boot breaks my Plasma Desktop Shell; KCrash tells about missing debug symbols

Dear all,

parallel boot breaks my Plasma desktop. After boot and login via kdm,
the Plasma desktop crashes.
Redoing a login usually fix that, so it seems to be time-dependent.
I suspect it is related to wicd (i. e. the readiness of wlan0).

I changed (months ago, a that time kdm had a too small timeout) in
/etc/init.d/rc the setting
CONCURRENCY=makefile to none. But alas, this is changed back to the
default setting
every time when sysv-rc is upgraded. This is a little nuisance.

I searched for bug reports or other related information, but to no avail.

So, I need some help in that matter.

Presumably I should file a bug.

KCrash told me that debug information is missing. I looked up the
debug section of the archive
and installed:

[INSTALL, DEPENDENCIES] kde-baseapps-dbg
[INSTALL, DEPENDENCIES] kde-runtime-dbg
[INSTALL, DEPENDENCIES] kde-workspace-dbg
[INSTALL] kdebase-dbg
[INSTALL] kdeplasma-addons-dbg
[INSTALL] kdeutils-dbg
[INSTALL] kdebase-workspace-dbg
[INSTALL] plasma-widget-networkmanagement-dbg

But KCrash tells me that more debug information is needed for the
following files:


So, please, can anybody tell me:

Do you think that this crash is a bug worthy to be filed to the Debian BTS?

Where can I find the missing debug symbols?

Or is there a plausible way to keep the CONCURRENCY=none setting? (But
I think that
keeping sysv-rc on hold would NOT be a good idea...)

Many Thanks in advance

Application: plasma-desktop (0.4)
KDE Platform Version: 4.7.4 (4.7.4)
Qt Version: 4.7.4
Operating System: Linux 2.6.32-5-686 i686
Distribution: Debian GNU/Linux testing (wheezy)

-- Information about the crash:
<In detail, tell us what you were doing when the application crashed.>
After login, waiting for the desktop to become ready.

The crash can be reproduced every time.

-- Backtrace:
Application: Plasma Desktop Shell (plasma-desktop), signal: Segmentation fault
Using host libthread_db library
[KCrash Handler]
#7 0xb62cb694 in QString:perator=(QString const&) () from
#8 0xaf855633 in ?? () from /usr/lib/kde4/plasma_engine_wicd.so
#9 0xb72f65d3 in Plasma:ataEngineManager::loadEngine
(this=0x9133fb0, name=...) at ../../plasma/dataenginemanager.cpp:136
#10 0xb7331bd5 in Plasma:ataEngineConsumer::dataEngine
(this=0x90c3228, name=...) at
#11 0xb72b30df in Plasma::Applet::dataEngine (this=0x92b3400,
name=...) at ../../plasma/applet.cpp:685
#12 0xb0566560 in ?? () from /usr/lib/kde4/plasma_applet_wicd.so
#13 0xb72d6647 in Plasma::ContainmentPrivate::initApplets
(this=0x90260d0) at ../../plasma/containment.cpp:463
#14 0xb72ec0f1 in Plasma::CoronaPrivate::importLayout (this=0x8f1bd60,
conf=..., mergeConfig=false) at ../../plasma/corona.cpp:1066
#15 0xb72ecf35 in Plasma::Corona::loadLayout (this=0x9049320,
configName=...) at ../../plasma/corona.cpp:278
#16 0xb72ed00e in Plasma::Corona::initializeLayout (this=0x9049320,
configName=...) at ../../plasma/corona.cpp:181
#17 0xb76d4ca1 in PlasmaApp::corona (this=0x8f03c08) at
#18 0xb76d500c in PlasmaApp::setupDesktop (this=0x8f03c08) at
#19 0xb76d6965 in PlasmaApp::qt_metacall (this=0x8f03c08,
_c=QMetaObject::InvokeMetaMethod, _id=14, _a=0x8fd4eb0) at
#20 0xb63816cd in QMetaObject::metacall(QObject*, QMetaObject::Call,
int, void**) () from /usr/lib/libQtCore.so.4
#21 0xb638c0d5 in QMetaCallEvent:laceMetaCall(QObject*) () from
#22 0xb63935ef in QObject::event(QEvent*) () from /usr/lib/libQtCore.so.4
#23 0xb637b8fa in QCoreApplication::event(QEvent*) () from
#24 0xb58b8f7d in QApplication::event(QEvent*) () from /usr/lib/libQtGui.so.4
#25 0xb58b4904 in QApplicationPrivate::notify_helper(QObject*,
QEvent*) () from /usr/lib/libQtGui.so.4
#26 0xb58b9c92 in QApplication::notify(QObject*, QEvent*) () from
#27 0xb6a1a511 in KApplication::notify (this=0x8f03c08,
receiver=0x8f03c08, event=0x8ff1178) at
#28 0xb637b31e in QCoreApplication::notifyInternal(QObject*, QEvent*)
() from /usr/lib/libQtCore.so.4
#29 0xb637eae4 in QCoreApplicationPrivate::sendPostedEvents(QObject* ,
int, QThreadData*) () from /usr/lib/libQtCore.so.4
#30 0xb637ec2c in QCoreApplication::sendPostedEvents(QObject*, int) ()
from /usr/lib/libQtCore.so.4
#31 0xb63a91a4 in postEventSourceDispatch(_GSource*, int (*)(void*),
void*) () from /usr/lib/libQtCore.so.4
#32 0xb2b09a3f in g_main_context_dispatch () from
#33 0xb2b0a170 in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
#34 0xb2b0a40a in g_main_context_iteration () from
#35 0xb63a95d7 in
QEventDispatcherGlib:rocessEvents(QFlags<QEventL oop::ProcessEventsFlag>)
() from /usr/lib/libQtCore.so.4
#36 0xb5969b9a in
QGuiEventDispatcherGlib:rocessEvents(QFlags<QEve ntLoop::ProcessEventsFlag>)
() from /usr/lib/libQtGui.so.4
#37 0xb637a33d in
QEventLoop:rocessEvents(QFlags<QEventLoop::Proce ssEventsFlag>) ()
from /usr/lib/libQtCore.so.4
#38 0xb637a581 in
QEventLoop::exec(QFlags<QEventLoop::ProcessEventsF lag>) () from
#39 0xb637ecda in QCoreApplication::exec() () from /usr/lib/libQtCore.so.4
#40 0xb58b2784 in QApplication::exec() () from /usr/lib/libQtGui.so.4
#41 0xb76b86eb in kdemain (argc=1, argv=0xbffc2bd4) at
#42 0x0804858b in main (argc=1, argv=0xbffc2bd4) at plasma-desktop_dummy.cpp:3

To UNSUBSCRIBE, email to debian-kde-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: CAEfK+ywxUcXcq=ztNDfGMWeCbqOwGFS-HVyH4e8JfLc62fvjwA@mail.gmail.com">http://lists.debian.org/CAEfK+ywxUcXcq=ztNDfGMWeCbqOwGFS-HVyH4e8JfLc62fvjwA@mail.gmail.com

Thread Tools

All times are GMT. The time now is 03:26 AM.

VBulletin, Copyright ©2000 - 2014, Jelsoft Enterprises Ltd.
Content Relevant URLs by vBSEO ©2007, Crawlability, Inc.
Copyright 2007 - 2008, www.linux-archive.org