maximus crashed with signal 5

[Alexey Kotlyarov]

Binary package hint: maximus

Happened right upon login, after gnome-settings-daemon crashed (with signal 5 as well).

ProblemType: Crash
Architecture: i386
Date: Thu Aug 13 14:38:47 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/maximus
Package: maximus 0.4.8-0ubuntu3
ProcCmdline: maximus
ProcEnviron:
 PATH=(custom, user)
 LANG=ru_RU.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-5.24-generic
Signal: 5
SourcePackage: maximus
StacktraceTop:
 ?? () from /usr/lib/libgdk-x11-2.0.so.0
 ?? () from /usr/lib/libbonoboui-2.so.0
 ?? ()
 ?? ()
 ?? ()
Title: maximus crashed with signal 5
Uname: Linux 2.6.31-5-generic i686
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

[Apport retracing service (apport)]

StacktraceTop:gdk_x_error (display=0x9ab9640, error=0xbfae3a9c)
bonobo_x_error_handler (display=0x9ab9640, error=0x2)
_XError (dpy=0x9ab9640, rep=0x9b1a620)
_XReply (dpy=0x9ab9640, rep=0xbfae3bb0, extra=0, discard=0)
XGetWindowProperty (dpy=0x9ab9640, w=4194308, property=333,

[Neil J. Patel (njpatel)]

Weird, looks like wnck got itself severely screwed up after g-s-d died. Has this happened again afterwards?

[Paul Larson (pwlars)]

We'd like to figure out what's causing this bug for you, but we haven't heard back from you in a while. Could you please provide the requested information? Thanks!

[Alexey Kotlyarov (koterpillar)]

This does not happen anymore in latest Karmic.

[Paul Larson (pwlars)]

Closing based on that last response, and on no further reports of this happening. If this happens again, please feel free to reopen or open a new bug. Thanks!