plasma crashed with SIGSEGV

[Giblet5]

Binary package hint: kdebase-workspace

Adding an icon to the desktop plasmoid...

Intrepid, 2.6.27-3-generic x86, Xorg 1.5.0, Nvidia 177.70.
HW is nvidia 9800M GTS, Centrino 2 @ 2.26Ghz, 4GBs RAM

Possibly related: Xorg 1.5.0 has a problem unmapping windows if BackingStore is enabled. I have ARGBVisuals and triple-buffering enabled, trying to resolve Gnome issues.

ProblemType: Crash
Architecture: i386
Disassembly: 0xb80aa430:
DistroRelease: Ubuntu 8.10
ExecutablePath: /usr/bin/plasma
NonfreeKernelModules: nvidia
Package: kdebase-workspace-bin 4:4.1.1-0ubuntu5
ProcAttrCurrent: unconfined
ProcCmdline: /usr/bin/plasma
ProcEnviron:
 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 LANG=en_US.UTF-8
 SHELL=/bin/bash
Signal: 11
SourcePackage: kdebase-workspace
Stacktrace: #0 0xb80aa430 in ?? ()
StacktraceTop: ?? ()
ThreadStacktrace:

Title: plasma crashed with SIGSEGV
Uname: Linux 2.6.27-3-generic i686
UserGroups: adm admin cdrom dialout fuse lpadmin plugdev sambashare

[Apport retracing service (apport)]

StacktraceTop:?? ()

[Andreas Moog (ampelbein)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. Is this crash reproducible?

[Giblet5 (pw-byteshuffler)]

Yes, 100% reproducible.

AND it was my fault!

Refer to the mangled "banshee.desktop" attachment.

Install this in /usr/share/applications/kde4 and observe that there is
now a Banshee menu item with an Amarok icon. Drag that to your desktop
and wait a moment...

See?

It's a corner-case... But it's guaranteed that users will do this... Cuz
I did.

::P

On Fri, 2008-09-12 at 19:27 +0000, Andreas Moog wrote:
> Thank you for taking the time to report this bug and helping to make
> Ubuntu better. Is this crash reproducible?
>
> ** Attachment removed: "CoreDump.gz"
>
> http://launchpadlibrarian.net/17562858/CoreDump.gz
>
> ** Changed in: kdebase-workspace (Ubuntu)
> Status: New => Incomplete
>
> ** Visibility changed to: Public
>

[Alessandro Ghersi (alessandro-ghersi)]

I download your .desktop and cp in /usr/share/applications/kde4, drag in my deskop from the menu. Plasma not crashed. I can't reproduce it.

[Harald Sitter (apachelogger)]

Install kdebase-workspace-dbg and retrigger the crash in order to get a new trace.
Thank you

[Giblet5 (pw-byteshuffler)]

Since the updates yesterday, the crash handler no longer prompts me to
file bug reports when kwin or plasma crash.

I'm new to KDE4... Where does the crash info get dumped? It was
in /var/crash, but the newest file there is prior to system updates and
I can still make it crash every time.

.xsession-errors has the following:

kio_trash(7927) TrashImpl::infoForFile: 0 "banshee-1.desktop.desktop"
kio_trash(7927) TrashImpl::infoForFile: 0 "banshee.desktop"
QObject: Do not delete object, 'unnamed', during its event handler!
QObject: Do not delete object, 'unnamed', during its event handler!
kwin: X Error (error: <unknown>[DAMAGE+0], request:
XDamageDestroy[DAMAGE+2], resource: 0x1202fa4)
kwin: X Error (error: <unknown>[DAMAGE+0], request:
XDamageDestroy[DAMAGE+2], resource: 0x1202faa)
findServiceByDesktopPath: /usr/share/applications/kde4/amarok.desktop
not found

The QObject warning *could* be the problem... It's not always OK to
delete an instance from within an event handler. That could explain the
subsequent X error.

It'll be best if you give me the path of the crash data now that it no
longer dumps to /var/crash...

:P

On Sat, 2008-09-13 at 23:35 +0000, Harald Sitter wrote:
> Install kdebase-workspace-dbg and retrigger the crash in order to get a new trace.
> Thank you
>

[Harald Sitter (apachelogger)]

Neato.
Edit /etc/default/apport (e.g. with `kdesudo kate /etc/default/apport`) and change enabled to =0 then reboot (might be necessary, or maybe not ;-)

Then KCrash should launch instead of apport, which go the disadvantage of not being bound to launchpad like apport, but provides easier access to the backtrace. I suggest to reverse the above changes once you grabbed a backtrace with kcrash.

[Giblet5 (pw-byteshuffler)]

The xorg update this morning seems to have corrected the behavior.

I can't reproduce the problem now. It was 100% reproducible before the
Xorg update (and I had other problems...kwin for example) that seem to
be behaving more politely as well.

Now, if someone could either fix or eliminate network-manager......... ;)

Let me know if there's something you want me to try.

P

Harald Sitter wrote:
> Neato.
> Edit /etc/default/apport (e.g. with `kdesudo kate /etc/default/apport`) and change enabled to =0 then reboot (might be necessary, or maybe not ;-)
>
> Then KCrash should launch instead of apport, which go the disadvantage
> of not being bound to launchpad like apport, but provides easier access
> to the backtrace. I suggest to reverse the above changes once you
> grabbed a backtrace with kcrash.
>
>

[Jonathan Thomas (echidnaman)]

Reported fixed.