Bug 158912 - Plasma crashes at start
Summary: Plasma crashes at start
Status: RESOLVED WORKSFORME
Alias: None
Product: plasma4
Classification: Plasma
Component: general (show other bugs)
Version: unspecified
Platform: openSUSE Linux
: NOR normal
Target Milestone: ---
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-03-07 16:51 UTC by Pilus
Modified: 2008-06-01 07:09 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Pilus 2008-03-07 16:51:24 UTC
Version:            (using KDE 4.0.2)
Installed from:    SuSE RPMs
Compiler:          Opensuse 10.3 KDE 4.0.2
OS:                Linux

I have opensuse 10.3 and I also added the KDE stable rep in YAST. So I updated to KDE 4.0.2 (KDE 4.0.1 was working fine). I use an old Compaq Armada M700 Notebook with an ATI grafic driver. I choose KDE 4.0.2 as Desktop at startup. I just see a few seconds the KDE status screen and then Plasma crashes.

Here the debug:
[?1034h(no debugging symbols found)
Using host libthread_db library "/lib/libthread_db.so.1".
(no debugging symbols found)
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 0xb624da30 (LWP 3663)]
0xffffe410 in __kernel_vsyscall ()
[Current thread is 0 (process 3663)]

Thread 1 (Thread 0xb624da30 (LWP 3663)):
#0  0xffffe410 in __kernel_vsyscall ()
#1  0xb66d38b0 in nanosleep () from /lib/libc.so.6
#2  0xb66d36b7 in sleep () from /lib/libc.so.6
#3  0xb79e89b9 in ?? () from /usr/lib/libkdeui.so.5
#4  0x00000001 in ?? ()
#5  0x00000000 in ?? ()
#0  0xffffe410 in __kernel_vsyscall ()
Comment 1 Markus Grob 2008-04-08 00:23:38 UTC
Have you tried it again with KDE 4.0.3? I think, you have to install the debug package to generate usable backtraces.
Comment 2 Markus Grob 2008-04-08 18:58:34 UTC
Like descibed in another bug, try this first:
remove your ~/.kde4/share/config/plasma-appletsrc and try again.
Comment 3 Jason Stubbs 2008-06-01 07:09:50 UTC
With 4.1 just around the corner, it's time to close off 4.0 bugs. If you get similar crashes with 4.1 please open a new bug with a full backtrace.