[Jaunty] System monitor crashed when trying to end a process (bluetoothd)

Bug #322445 reported by Markus Pfeiffer
96
This bug affects 6 people
Affects Status Importance Assigned to Milestone
gnome-system-monitor (Ubuntu)
Invalid
Medium
Unassigned
Nominated for Jaunty by Alexandre Demers
Nominated for Karmic by Alexandre Demers

Bug Description

Binary package hint: gnome-system-monitor

I tried to end the process "bluetoothd". System monitor (2.24.4-0ubuntu2) crashed with the attached error report.

ProblemType: Crash
Architecture: i386
DistroRelease: Ubuntu 9.04
ExecutablePath: /usr/bin/gnome-system-monitor
Package: gnome-system-monitor 2.24.4-0ubuntu2
ProcCmdline: gnome-system-monitor
ProcEnviron:
 LANG=en_US.UTF-8
 SHELL=/bin/bash
Signal: 5
SourcePackage: gnome-system-monitor
StacktraceTop:
 ?? () from /usr/lib/libgdk-x11-2.0.so.0
 _XError () from /usr/lib/libX11.so.6
 ?? () from /usr/lib/libX11.so.6
 _XReply () from /usr/lib/libX11.so.6
 XTranslateCoordinates () from /usr/lib/libX11.so.6
Title: gnome-system-monitor crashed with signal 5 in _XError()
Uname: Linux 2.6.28-5-generic i686
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Tags: apport-crash
Revision history for this message
Markus Pfeiffer (markus-pfeiffer) wrote :
Revision history for this message
Apport retracing service (apport) wrote : Symbolic stack trace

StacktraceTop:gdk_x_error (display=0x8aa0108, error=0xbfc08398)
_XError (dpy=0x8aa0108, rep=0x921bdf8)
process_responses (dpy=0x8aa0108, wait_for_first_event=0,
_XReply (dpy=0x8aa0108, rep=0xbfc084c0, extra=0, discard=1)
XTranslateCoordinates (dpy=0x8aa0108, src_win=137,

Revision history for this message
Apport retracing service (apport) wrote : Symbolic threaded stack trace
Changed in gnome-system-monitor:
importance: Undecided → Medium
Revision history for this message
Alexandre Demers (oxalin) wrote :

It seems System Monitor crashes whenever we try to kill or end a process that will not respond to the command. I reproduced it with gpsd on Ubuntu 9.10 alpha 5, updated on 09/09/09.

Try the following :
If you kill or end the application through System Monitor, it will crash System Monitor. However, the application will still be running.

If you try to kill the application using the command line "kill", the application will continue to run anyway.

So it seems related to a case where System Monitor doesn't handle correctly the error sent when an application can't be killed or ended. When this situation happens, System Monitor should not crash and, in the best case, should tell the user it wasn't able to kill or end the application correctly.

Revision history for this message
Pedro Villavicencio (pedro) wrote :

is this still an issue with karmic?

Changed in gnome-system-monitor (Ubuntu):
status: New → Incomplete
Revision history for this message
Pedro Villavicencio (pedro) wrote :

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to New. Thanks again!.

Changed in gnome-system-monitor (Ubuntu):
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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