Bug 194188

Summary:	plasma crashes after login
Product:	[Unmaintained] plasma4	Reporter:	mail
Component:	general	Assignee:	Plasma Bugs List <plasma-bugs-null>
Status:	RESOLVED DUPLICATE
Severity:	crash	CC:	andresbajotierra, aseigo, notmart
Priority:	NOR
Version First Reported In:	unspecified
Target Milestone:	---
Platform:	unspecified
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description mail 2009-05-26 19:38:57 UTC

Version:            (using KDE 4.2.3)
OS:                Linux
Installed from:    I Don't Know

Anwendung: Plasma-Arbeitsfläche (kdeinit), Signal SIGSEGV
0x00007fb09db5fcb0 in nanosleep () from /lib64/libc.so.6
[Current thread is 1 (Thread 0x7fb0a18a4750 (LWP 5036))]

Thread 1 (Thread 0x7fb0a18a4750 (LWP 5036)):
[KCrash Handler]
#5  0x00007fb0a13dc300 in QObject::setParent(QObject*) () from /usr/lib64/libQtCore.so.4
#6  0x00007fb09875ddf5 in Plasma::Containment::setWallpaper(QString const&, QString const&) () from /usr/lib64/libplasma.so.3
#7  0x00007fb09875e085 in Plasma::Containment::setDrawWallpaper(bool) () from /usr/lib64/libplasma.so.3
#8  0x00007fb0987602dd in Plasma::Containment::init() () from /usr/lib64/libplasma.so.3
#9  0x00007fb09876a54a in Plasma::Corona::loadLayout(QString const&) () from /usr/lib64/libplasma.so.3
#10 0x00007fb09876ba72 in Plasma::Corona::initializeLayout(QString const&) () from /usr/lib64/libplasma.so.3
#11 0x00007fb0961e1b38 in ?? () from /usr/lib64/libkdeinit4_plasma.so
#12 0x00007fb0961e3651 in ?? () from /usr/lib64/libkdeinit4_plasma.so
#13 0x00007fb0961e372f in ?? () from /usr/lib64/libkdeinit4_plasma.so
#14 0x00007fb0961d682c in kdemain () from /usr/lib64/libkdeinit4_plasma.so
#15 0x00000000004071fe in _start ()

Comment 1 Marco Martin 2009-05-26 21:38:04 UTC

this backtrace looks incomplete, please see
http://techbase.kde.org/Development/Tutorials/Debugging/How_to_create_useful_crash_reports

Comment 2 Dario Andres 2009-05-27 18:51:09 UTC

The backtrace looks like bug 192912 (which was introduced and fixed both on 4.3trunk, so it is strange it appears on 4.2.3..... a backport ?)

@mail@ekaiser.de: what is your Linux distribution?

Thanks

Comment 3 Aaron J. Seigo 2009-05-27 20:13:06 UTC

yes, exact same bug as in 192912 .. not sure how it ended up 4.2 either.

*** This bug has been marked as a duplicate of bug 192912 ***