Bug 159333

Summary:	crash in plasma kde4
Product:	[Unmaintained] plasma4	Reporter:	juarez <honoriolima>
Component:	general	Assignee:	Plasma Bugs List <plasma-bugs-null>
Status:	RESOLVED INTENTIONAL
Severity:	crash	CC:	finex, honoriolima
Priority:	NOR
Version First Reported In:	unspecified
Target Milestone:	---
Platform:	Ubuntu
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

Description juarez 2008-03-14 23:53:25 UTC

Version:            (using KDE 4.0.2)
Installed from:    Ubuntu Packages

plasma.kcrash

(no debugging symbols found)
Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1238554944 (LWP 5730)]
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()
[Current thread is 0 (process 5730)]

Thread 1 (Thread -1238554944 (LWP 5730)):
#0  0xffffe410 in __kernel_vsyscall ()
#1  0xb7ec4e70 in nanosleep () from /lib/tls/i686/cmov/libc.so.6
#2  0xb7ec4ca7 in sleep () from /lib/tls/i686/cmov/libc.so.6
#3  0xb7859640 in ?? () from /usr/lib/kde4/lib/libkdeui.so.5
#4  0x00000001 in ?? ()
#5  0x00000000 in ?? ()
#0  0xffffe410 in __kernel_vsyscall ()

Comment 1 FiNeX 2008-03-15 10:47:26 UTC

1) please tell how to reproduce the crash
2) please, don't post backtrace with "(no debugging symbols found)". Follow the instructions on http://techbase.kde.org/Development/Tutorials/Debugging/How_to_create_useful_crash_reports for post backtrace.

Comment 2 Markus Grob 2008-04-08 00:45:05 UTC

It seems, that (K)ubuntu and KDE 4.0.2 generates troubles. Please try again with KDE 4.0.3 and rename ./kde4 to ./kde4_old and do the same with ./kde If it works after. Please close the bug.

Comment 3 Markus Grob 2008-04-08 19:39:41 UTC

First try to move/delete ~/.kde/share/config/plasmarc.

Comment 4 FiNeX 2008-05-05 15:26:12 UTC

@Juarez: could you try to follow the Markus hints?

Comment 5 Jason Stubbs 2008-06-01 07:39:15 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.