Maximus

maximus crashed with signal 5

Bug #412899 reported by Alexey Kotlyarov on 2009-08-13

8

This bug affects 1 person

Affects		Status	Importance	Assigned to	Milestone
	Maximus	Incomplete	Undecided	Unassigned
	maximus (Ubuntu)	Fix Released	Medium	Unassigned

Bug Description

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

Tags:

Revision history for this message

Alexey Kotlyarov (koterpillar) wrote on 2009-08-13:

#1

Dependencies.txt Edit (4.8 KiB, text/plain; charset="utf-8")
Disassembly.txt Edit (729 bytes, text/plain; charset="utf-8")
ProcMaps.txt Edit (26.2 KiB, text/plain; charset="utf-8")
ProcStatus.txt Edit (755 bytes, text/plain; charset="utf-8")
Registers.txt Edit (450 bytes, text/plain; charset="utf-8")
Stacktrace.txt Edit (303 bytes, text/plain; charset="utf-8")
ThreadStacktrace.txt Edit (329 bytes, text/plain; charset="utf-8")

Revision history for this message

Apport retracing service (apport) wrote on 2009-08-13: Stacktrace.txt (retraced)

#2

Stacktrace.txt (retraced) Edit (11.6 KiB, text/plain)

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,

Revision history for this message

Apport retracing service (apport) wrote on 2009-08-13: ThreadStacktrace.txt (retraced)

#3

ThreadStacktrace.txt (retraced) Edit (11.6 KiB, text/plain)

Changed in maximus (Ubuntu):
importance:	Undecided → Medium
tags:	removed: need-i386-retrace

Revision history for this message

Neil J. Patel (njpatel) wrote on 2009-08-26:

#4

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

Changed in maximus:
status:	New → Incomplete

Revision history for this message

Paul Larson (pwlars) wrote on 2009-09-24:

#5

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!

visibility:	private → public
Changed in maximus (Ubuntu):
status:	New → Incomplete

Revision history for this message

Alexey Kotlyarov (koterpillar) wrote on 2009-10-10:

#6

This does not happen anymore in latest Karmic.

Revision history for this message

Paul Larson (pwlars) wrote on 2009-10-10:

#7

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!

Changed in maximus (Ubuntu):
status:	Incomplete → Fix Released

Report a bug

This report contains Public information

Everyone can see this information.

You are

Subscribing...

Edit bug mail

Other bug subscribers

Bug attachments

Add attachment

Remote bug watches

Bug watches keep track of this bug in other bug trackers.