Bug 157599 - plasma crashes starting yakuake
Summary: plasma crashes starting yakuake
Status: RESOLVED FIXED
Alias: None
Product: plasma4
Classification: Plasma
Component: general (show other bugs)
Version: unspecified
Platform: Debian testing Linux
: NOR crash
Target Milestone: ---
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-02-10 13:55 UTC by Julià
Modified: 2008-02-10 20:10 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 Julià 2008-02-10 13:55:03 UTC
Version:            (using KDE 4.0.0)
Installed from:    Debian testing/unstable Packages

I started yakuake and plasma has crashed and restarted. If I type 'plsama' in the term it returns:
~$ plasma
<unknown program name>(2705)/ checkComposite: Plasma has an argb visual 0x8054170 58720257
<unknown program name>(2705)/ checkComposite: Plasma is COMPOSITE-less on 0x8054d40

the backtrace:

(no debugging symbols found)
Using host libthread_db library "/lib/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 0xb61d16c0 (LWP 3336)]
[New Thread 0xb3eb3b90 (LWP 6101)]
[New Thread 0xb4841b90 (LWP 3337)]
(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)
(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 (LWP 3336)]

Thread 3 (Thread 0xb4841b90 (LWP 3337)):
#0  0xffffe410 in __kernel_vsyscall ()
#1  0xb7adbaa5 in pthread_cond_wait@@GLIBC_2.3.2 ()
   from /lib/i686/cmov/libpthread.so.0
#2  0xb7e857bd in pthread_cond_wait () from /lib/i686/cmov/libc.so.6
#3  0xb7b2b7a4 in QWaitCondition::wait () from /usr/lib/libQtCore.so.4
#4  0xb4bfd324 in ?? () from /usr/lib/kde4/plasma_containment_desktop.so
#5  0x0812e540 in ?? ()
#6  0x0812e53c in ?? ()
#7  0xffffffff in ?? ()
#8  0xb4841280 in ?? ()
#9  0xb484133c in ?? ()
#10 0xb7da1548 in ?? ()
#11 0xb7b01096 in ?? () from /usr/lib/libQtCore.so.4
#12 0xb78a1400 in ?? () from /usr/lib/libkdeui.so.5
#13 0xb4c00785 in ?? () from /usr/lib/kde4/plasma_containment_desktop.so
#14 0xb4c0078c in ?? () from /usr/lib/kde4/plasma_containment_desktop.so
#15 0xb7f34ff4 in ?? () from /lib/ld-linux.so.2
#16 0xb7da1458 in ?? ()
#17 0xb4841318 in ?? ()
#18 0xb4841310 in ?? ()
#19 0xb4841300 in ?? ()
#20 0xb48412f4 in ?? ()
#21 0x0812e53c in ?? ()
#22 0xb4841354 in ?? ()
#23 0xb48412e4 in ?? ()
#24 0xb4841344 in ?? ()
#25 0x3f800000 in ?? ()
#26 0x00000002 in ?? ()
#27 0x00000001 in ?? ()
#28 0x00000001 in ?? ()
#29 0x0000000c in ?? ()
#30 0x0804fc34 in ?? ()
#31 0x00000000 in ?? ()

Thread 2 (Thread 0xb3eb3b90 (LWP 6101)):
#0  0xffffe410 in __kernel_vsyscall ()
#1  0xb7e71321 in select () from /lib/i686/cmov/libc.so.6
#2  0xb7bc41d7 in ?? () from /usr/lib/libQtCore.so.4
#3  0x00000012 in ?? ()
#4  0xb3eb32d8 in ?? ()
#5  0x00000000 in ?? ()

Thread 1 (Thread 0xb61d16c0 (LWP 3336)):
#0  0xffffe410 in __kernel_vsyscall ()
#1  0xb7e3738b in waitpid () from /lib/i686/cmov/libc.so.6
#2  0xb779f63b in ?? () from /usr/lib/libkdeui.so.5
#3  0x00000a57 in ?? ()
#4  0x00000000 in ?? ()
#0  0xffffe410 in __kernel_vsyscall ()




thanks a lot
Comment 1 Sebastian Sauer 2008-02-10 18:49:34 UTC
Hi Julià,

since the backtrace is somewhat useless, could you please install the debug-packages (*-dgb) to gain a more useful backtrace? 
 
also it would be nice to know, what you did before the crash. Did you add a new applet, changed some setting, ...?

Probably related are; 
 * bug #156207 
 * bug #157617
 * bug #157437 
 * bug #157158 
 * bug #157104 
 * bug #155719 
Comment 2 Sebastian Sauer 2008-02-10 18:55:10 UTC
I would suggest to mark this report as duplicate of bug #157599 if no useful backtrace can be reproduced.
Comment 3 Julià 2008-02-10 19:28:04 UTC
Hi!

before the crash I was working with Iceweasel and Okular, with kopete, akregator and amarok aplications runing. I didn't tray to add a new applet and I didn't changed anything in the configuration.

I tryed to install the debug packages but i couldn't found how to do it.

Thanks
Comment 4 Sebastian Sauer 2008-02-10 19:35:43 UTC
debian may provide debug-packagres. This means, that there is e.g. a "kdebase4" and a "kdebase4-dbg" around for KDE 4.0.x. The later are then the debug-packages and a "apt-get install kdebase4-dbg" should replace the "kdebase4" with the "kdebase4-dbg" package which then provides more useful backtraces if something crashes but is also slighly slower.
But be careful here since it may also the case, that you can destroy your kde-setup that way and if you are not familar with how to solve conflicts of packages it will be probably a difficult job to get everything working again...
Comment 5 Julià 2008-02-10 20:02:07 UTC
Hi,

I installed the -dbg packages and I upgraded the sistem, and now i couldn't reproduce the crash, so I not able to paste the new backtrace. But I think that it means that the bug is solved in the new version, is it?

thanks
Comment 6 Sebastian Sauer 2008-02-10 20:10:07 UTC
hehe, the usual phenomenon. Well, it may fixed, but may also just again one of the cases that just can't be reproduced all the time.

Anyway, if you can't reproduce this now, let's mark the report as fixed. Please feel free to reopen it, if it shows up again. Thanks for the feedback, Julià!