[Bug 322445] Re: [Jaunty] System monitor crashed when trying to end a process (bluetoothd)

2010-01-08 Thread Pedro Villavicencio
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

[Bug 322445] Re: [Jaunty] System monitor crashed when trying to end a process (bluetoothd)

2009-12-04 Thread Pedro Villavicencio
is this still an issue with karmic? ** Changed in: gnome-system-monitor (Ubuntu) Status: New = Incomplete -- [Jaunty] System monitor crashed when trying to end a process (bluetoothd) https://bugs.launchpad.net/bugs/322445 You received this bug notification because you are a member of

[Bug 322445] Re: [Jaunty] System monitor crashed when trying to end a process (bluetoothd)

2009-09-09 Thread Oxalin
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.

[Bug 322445] Re: [Jaunty] System monitor crashed when trying to end a process (bluetoothd)

2009-01-28 Thread Markus Pfeiffer
** Attachment added: CoreDump.gz http://launchpadlibrarian.net/21727071/CoreDump.gz ** Attachment added: Dependencies.txt http://launchpadlibrarian.net/21727072/Dependencies.txt ** Attachment added: Disassembly.txt http://launchpadlibrarian.net/21727073/Disassembly.txt ** Attachment

[Bug 322445] Re: [Jaunty] System monitor crashed when trying to end a process (bluetoothd)

2009-01-28 Thread Apport retracing service
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, ** Attachment removed: