Bug 155719

Summary: Backtrace after kget widget over taskbar movement crashes plasma
Product: [Unmaintained] plasma4 Reporter: Kubuntiac <user581>
Component: generalAssignee: Plasma Bugs List <plasma-bugs>
Status: RESOLVED WORKSFORME    
Severity: crash CC: arn.epsilon
Priority: NOR    
Version: unspecified   
Target Milestone: ---   
Platform: Ubuntu   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:
Attachments: Konsole output from re-running plasma
Screen shot of my missing desktop
Tale of Two Desktops
Dmesg output
crash backtrace
Screengrab showing 2 desktops inc. 2 x plasma hotspots

Description Kubuntiac 2008-01-14 08:00:51 UTC
Version:            (using KDE KDE 4.0.0)
Installed from:    Ubuntu Packages
OS:                Linux

I haven't managed to replicate this consistently but wanted to pass along the backtrace in case its useful. It happened just as I grabbed the Kget droptarget and moved it over the Desktop pager in the taskbar.

(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 -1248844064 (LWP 15524)]
[New Thread -1302496368 (LWP 15557)]
[New Thread -1322300528 (LWP 15543)]
[New Thread -1288062064 (LWP 15542)]
(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 15524)]

Thread 4 (Thread -1288062064 (LWP 15542)):
#0  0xffffe410 in __kernel_vsyscall ()
#1  0xb7b23676 in pthread_cond_wait@@GLIBC_2.3.2 ()
   from /lib/tls/i686/cmov/libpthread.so.0
#2  0xb7ef831d in pthread_cond_wait () from /lib/tls/i686/cmov/libc.so.6
#3  0xb7b7529d in QWaitCondition::wait () from /usr/lib/libQtCore.so.4
#4  0xb3428636 in ?? ()
   from /usr/lib/kde4/lib/kde4/plasma_containment_desktop.so
#5  0x082f8990 in ?? ()
#6  0x082f898c in ?? ()
#7  0xffffffff in ?? ()
#8  0x00000000 in ?? ()

Thread 3 (Thread -1322300528 (LWP 15543)):
#0  0xffffe410 in __kernel_vsyscall ()
#1  0xb7b23676 in pthread_cond_wait@@GLIBC_2.3.2 ()
   from /lib/tls/i686/cmov/libpthread.so.0
#2  0xb7ef831d in pthread_cond_wait () from /lib/tls/i686/cmov/libc.so.6
#3  0xb7b7529d in QWaitCondition::wait () from /usr/lib/libQtCore.so.4
#4  0xb3428636 in ?? ()
   from /usr/lib/kde4/lib/kde4/plasma_containment_desktop.so
#5  0x08322048 in ?? ()
#6  0x08322044 in ?? ()
#7  0xffffffff in ?? ()
#8  0x00000000 in ?? ()

Thread 2 (Thread -1302496368 (LWP 15557)):
#0  0xffffe410 in __kernel_vsyscall ()
#1  0xb7b23676 in pthread_cond_wait@@GLIBC_2.3.2 ()
   from /lib/tls/i686/cmov/libpthread.so.0
#2  0xb7ef831d in pthread_cond_wait () from /lib/tls/i686/cmov/libc.so.6
#3  0xb7b7529d in QWaitCondition::wait () from /usr/lib/libQtCore.so.4
#4  0xb3428636 in ?? ()
   from /usr/lib/kde4/lib/kde4/plasma_containment_desktop.so
#5  0x093a7554 in ?? ()
#6  0x093a7550 in ?? ()
#7  0xffffffff in ?? ()
#8  0x00000000 in ?? ()

Thread 1 (Thread -1248844064 (LWP 15524)):
#0  0xffffe410 in __kernel_vsyscall ()
#1  0xb7eaa6db in waitpid () from /lib/tls/i686/cmov/libc.so.6
#2  0xb7845c2b in ?? () from /usr/lib/kde4/lib/libkdeui.so.5
#3  0x000066be in ?? ()
#4  0x00000000 in ?? ()
#0  0xffffe410 in __kernel_vsyscall ()
Comment 1 Aaron J. Seigo 2008-01-14 08:07:04 UTC
would it be possible for you to install the debug packages and try and replicate this for a better backtrace? thanks =)
Comment 2 Kubuntiac 2008-01-15 03:46:13 UTC
Which packages exactly? I don't see anything like a libplasma-dbg /
plasma-debug. The closest I see in Kubuntu's repo's are libplasma1-dev
and extragear-plasma-dbg.

By the way, serious kudo's on keeping it all together for the recent
release Aaron. The fact you managed to stay a nice, relatively sane
human being through the last few months speaks volumes about you. The
fact you're still replying to bug reports so soon afterwards is even
more impressive! ;)

Rock on KDE4 (and the corner, plasma widget thingie lol)

On 14 Jan 2008 07:07:04 -0000, Aaron J. Seigo <aseigo@kde.org> wrote:
[bugs.kde.org quoted mail]
Comment 3 Aaron J. Seigo 2008-01-15 03:51:47 UTC
there should (hopefully!) be a kdebase-dbg package that likely has the debug symbols in it.

> By the way

thanks =)

> The fact you're still replying to bug reports

nah, this is easy and enjoyable part. writing and debugging code is one of my favourite things to do. =)
Comment 4 Aaron J. Seigo 2008-01-15 03:57:16 UTC
remembering that i have a gutsy system laying around here, i checked and the package is called kdebase-workspace-dbg
Comment 5 Kubuntiac 2008-01-17 23:45:21 UTC
Created attachment 23109 [details]
Konsole output from re-running plasma
Comment 6 Kubuntiac 2008-01-18 00:02:12 UTC
Created attachment 23111 [details]
Screen shot of my missing desktop
Comment 7 Kubuntiac 2008-01-18 00:03:29 UTC
K I installed the kdebase-workspace-dbg packages (all 684Mb! Sheesh.)

Trouble is that I'm not getting a specific crash now, rather the desktop just doesn't really work at all now, but doesn't crash. What I mean by that is that I get no wallpaper image - just white, the desktop icons come up, but each one also has a generic "10100101" icon over them also, the whole computer slows down to the point of taking about 5 minutes to load the workspace, the corner plasma "Zoom In / Out / Add widgets" now does nothing when the mouse hovers over it and right clicking on the desktop now does nothing. Alt+F2 and the menu still work though as other apps seem to. While there's no crash (and thus no crash report) I did manage to get the output in the first attachment by killing plasma in ksysguard and running it again from konsole. I've noticed I also get some kind of error sound now in KDE4 during the last stage of the splash screen (with the K logo) and also in KDE3 when the desktop icon is onscreen, so its entirely possible I've somehow hosed something nothing to do with KDE4 (although KDE3 continues to work fine).

Anyway, if this is all just here for if it's of use and I'll totally understand if there's more common bugs to solve atm

cheers!

Comment 8 Tommi Tervo 2008-01-18 08:37:11 UTC
*** Bug 156077 has been marked as a duplicate of this bug. ***
Comment 9 Kubuntiac 2008-01-19 19:09:06 UTC
A quick update:

After todays updates (from a quick glance some xorg/xorg-xephyr,libplasma1,kdebase stuff) I now have the desktop image back, however other symptoms remain. The desktop still beeps at me on the splash screen, it still takes an age to load up. The menu still takes 30 seconds or so to respond and there's still the "0101101" icons all over the screen.

What I did notice that may be of interest, is that if I drag on the desktop, it actually moves the entire desktop image, revealing another desktop image underneath! It takes about 4 minutes before it updates so I can see, but I tested it a couple of times and this definitely seems to be what's happening. I have my desktop set to switch images every 15 minutes, and when it does that only the "top" desktop changes. The bottom one remains an image I used for my desktop previously. Also, when I move the top desktop, it seems to leave the "100101" icons where they are, while the correct ones move with it (see the screengrab attached). I've also added my dmesg file to see if that gives any clues. I also just realised that maybe having a dual head setup could be related somehow, too.

Anyway hope this helps!
Comment 10 Kubuntiac 2008-01-19 20:01:24 UTC
Created attachment 23139 [details]
Tale of Two Desktops

The blue part of the screen is the "top" desktop which seems to be dragable and
updates periodically as I had set my desktop. The green leaves is the old
desktop image with the "101001" icons.
Comment 11 Kubuntiac 2008-01-19 20:06:48 UTC
Created attachment 23140 [details]
Dmesg output
Comment 12 Chani 2008-01-20 12:46:03 UTC
> After todays updates (from a quick glance some
> xorg/xorg-xephyr,libplasma1,kdebase stuff) I now have the desktop image
> back, however other symptoms remain. 


maybe this is a silly question, but when was the last time you deleted your 
plasma-appletsrc?
Comment 13 Kubuntiac 2008-01-20 23:05:23 UTC
Hmmm... given that I have no idea what plasma-appletsrc is I'd guess
the answer is "never". I installed KDE4 from the Kubuntu packages and
have only delved into compiling from source black magic once or twice.

Should I be deleting this, and if so how?

Thanks!
Comment 14 Kubuntiac 2008-01-20 23:33:08 UTC
For what it's worth I just noticed that when plasma is run in a konsole window it spits out hundreds of errors, all of which seem to start with:

"findServiceByDesktopPath:  not found"

I've tried doing a dpkg-reconfigure for libplasma1 and it didn't seem to do anything.
Comment 15 Chani 2008-01-21 05:40:37 UTC
kquitapp plasma; rm $KDEHOME/share/config/plasma-appletsrc; plasma

if $KDEHOME isn't set use ~/.kde or ~/.kde4 or wherever it is your kde4 
settings are kept.
Comment 16 Kubuntiac 2008-01-21 12:33:18 UTC
ALL HAIL CHANI: UBER KDE HACKER SUPREME!

Behold! For the first time in a week I have a working KDE4 desktop! Huzzah!
It's even looking slicker and snappier than when I last used used it, too.
:) I love open source like that.

As you can probably guess, your last suggestion worked... I even tried to do
the same thing that caused this in the first place and so far so good. Now
to see if I can crash something else heh, heh...
ALL HAIL CHANI: UBER KDE HACKER SUPREME!<br><br>Behold! For the first time in a week I have a working KDE4 desktop! Huzzah! It&#39;s even looking slicker and snappier than when I last used used it, too. :) I love open source like that.
<br><br>As you can probably guess, your last suggestion worked... I even tried to do the same thing that caused this in the first place and so far so good. Now to see if I can crash something else heh, heh...<br>
Comment 17 Maksim Melnikau 2008-01-23 18:51:27 UTC
Created attachment 23221 [details]
crash backtrace

Crashed when I try add widget.
Comment 18 Kubuntiac 2008-01-23 19:35:10 UTC
Actually, this doesn't seem  to be completely fixed after all. Things
have sped up, but the desktop file icons are invisible! You can't see
them, but if you click where they are they open. Strangely Ctrl + F12
still displays them.

I also am getting a message from time to time (often after launching
something from Krunner) that says:
"Sorry - Plasma: KLauncher could not be reached via D-Bus, error when
calling start_service_by_desktop_path:
empty"

Chani still rocks though for speeding up my KDE and giving me back my
desktop. :)

On 23 Jan 2008 17:51:27 -0000, Maksim Melnikau <maxposedon@gmail.com> wrote:
[bugs.kde.org quoted mail]
Comment 19 Kubuntiac 2008-01-28 01:58:22 UTC
Just noticed something to do with this bug.

Although it's not "draggable" like it was before, there still seems to be two desktops being drawn. I noticed that when booting KDE4, I see a background with the Blue EOS background and all the desktop icons first, then another background appears over the top of it (with the maple leaf image). If I configure desktop or anything like that it does it to the top desktop, but this one has no icons. I noticed that when I changed the screen resolution through nvidia-xconfig that the bottom desktop resized, but the top one didn't. I'm not too fussed about that, but it did let me get this screengrab that shows the 2 desktops quite nicely. :)
Comment 20 Kubuntiac 2008-01-28 02:00:30 UTC
Created attachment 23321 [details]
Screengrab showing 2 desktops inc. 2 x plasma hotspots
Comment 21 George 2008-03-15 14:47:22 UTC
i can´t get the crash when moving kget drop target over the pager in my taskbar. i´m using kde 4.0.2 and (apparently) it Worksforme
Comment 22 Kubuntiac 2008-06-13 20:37:51 UTC
Seems to have been resolved somewhere along the way.

Joy!