Ubuntu
gnome-system-monitor package

gnome-system-monitor keeps crashing with signal 7 (on a Jaunty booted from USB)

Bug #472437 reported by CoolKoon on 2009-11-03

This bug affects 1 person

Affects		Status	Importance	Assigned to	Milestone
	Gnome System Monitor	Expired	Critical	gnome-bugs #601762
	gnome-system-monitor (Ubuntu)	Invalid	Medium	Unassigned

Bug Description

Binary package hint: gnome-system-monitor

I am unable to start gnome-system-monitor at all, because each time I click on the appropriate button, the crash report dialog comes up. Nothing helps with this, not even running from console (it says "Bus error (core dumped)") nor sudoing to root (the same at the former).
Output of synaptic verion query:
gnome-system-monitor:
  Telepítve: 2.26.0.1-0ubuntu1
  Jelölt: 2.26.0.1-0ubuntu1
  Verziótáblázat:
*** 2.26.0.1-0ubuntu1 0
        500 http://archive.ubuntu.com jaunty/main Packages
        100 /var/lib/dpkg/status
(sorry, it's in Hungarian, "Telepítve"=Installed, "Jelölt"=Marked/Selected, "Verziótáblázat"=Version table)

ProblemType: Crash
Architecture: i386
DistroRelease: Ubuntu 9.04
ExecutablePath: /usr/bin/gnome-system-monitor
MediaBuild: Ubuntu 9.04 "Jaunty Jackalope" - Release i386 (20090420.1)
Package: gnome-system-monitor 2.26.0.1-0ubuntu1
ProcCmdline: gnome-system-monitor
ProcEnviron:
LANG=hu_HU.UTF-8
SHELL=/bin/bash
Signal: 7
SourcePackage: gnome-system-monitor
StacktraceTop:
?? () from /lib/ld-linux.so.2
?? () from /lib/ld-linux.so.2
?? () from /lib/ld-linux.so.2
?? () from /lib/ld-linux.so.2
?? () from /lib/ld-linux.so.2
Title: gnome-system-monitor crashed with signal 7
Uname: Linux 2.6.28-11-generic i686
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Tags:

Revision history for this message

CoolKoon (coolkoon) wrote on 2009-11-03:

Dependencies.txt Edit (3.6 KiB, text/plain; charset="utf-8")
Disassembly.txt Edit (474 bytes, text/plain; charset="utf-8")
ProcMaps.txt Edit (17.7 KiB, text/plain; charset="utf-8")
ProcStatus.txt Edit (770 bytes, text/plain; charset="utf-8")
Registers.txt Edit (489 bytes, text/plain; charset="utf-8")
Stacktrace.txt Edit (287 bytes, text/plain; charset="utf-8")
ThreadStacktrace.txt Edit (315 bytes, text/plain; charset="utf-8")

Revision history for this message

Apport retracing service (apport) wrote on 2009-11-12: Stacktrace.txt (retraced)

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

StacktraceTop:_dl_lookup_symbol_x (
_dl_relocate_object (scope=0xb8057748, lazy=1,
dl_main (phdr=0x8048034, phnum=288, user_entry=0xbfcc836c)
_dl_sysdep_start (start_argptr=0xbfcc83c0,
_dl_start (arg=0xbfcc83c0) at rtld.c:327

Revision history for this message

Apport retracing service (apport) wrote on 2009-11-12: ThreadStacktrace.txt (retraced)

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

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

MarcRandolph (mrand) on 2009-11-13

visibility:

private → public

Revision history for this message

WeatherGod (ben-v-root) wrote on 2009-11-13:

CoolKoon, for an additional bit of information, could you please run 'gnome-system-monitor' from the terminal, and then copy-n-paste the terminal output to this bug report?

Revision history for this message

C de-Avillez (hggdh2) wrote on 2009-11-13:

Setting as incomplete, waiting for reporter's reply.

Changed in gnome-system-monitor (Ubuntu):
status:	New → Incomplete

Revision history for this message

CoolKoon (coolkoon) wrote on 2009-11-13:

As I said earlier this is the only output I get: Bus error (core dumped)
After that a an error message window appears telling me that an application has crashed and asking me whether I want to restart it etc. Oddly it appeared only after the first time I ran gnome-system-monitor.

Revision history for this message

CoolKoon (coolkoon) wrote on 2009-11-13:

When I run the command from the console, that is. When I run it from a real (CTRL+F1 etc.) terminal, there are these additional errors:
[591959.442817] SQUASHFS error: sb_bread failed reading block 0x82088
[591959.442902] SQUASHFS error: Unable to read page, block 2081daa7, size 48d8
I guess these are kernel error messages (impossible to copy/redirect), and looks like they pretty much say that I should replace my squashfs file. Sorry for the false alarm. Is there some way to fix these errors BTW?

Revision history for this message

mv (marxistvegan) wrote on 2010-03-17:

I to have recently have this bug. I am running Karmic and when I run
gnome-system-manager from terminal all I receive is
Bus Error with no other details.

Bug Watch Updater (bug-watch-updater) on 2010-09-16

Changed in gnome-system-monitor:
importance:	Unknown → Critical
status:	Unknown → New

Revision history for this message

CoolKoon (coolkoon) wrote on 2010-09-16:

You might want to do the same as I did, that is go to text-mode terminal (CTRL+F1 or CTRL+F2 etc.) and try running it from there. This way you'll get the kernel messages dumped as well (which can be later reviewed using the "dmesg" command).

Bug Watch Updater (bug-watch-updater) on 2011-01-10

Changed in gnome-system-monitor:
status:	New → Incomplete

Bug Watch Updater (bug-watch-updater) on 2011-01-27

Changed in gnome-system-monitor:
status:	Incomplete → Expired

Revision history for this message

Dmitri Bachtin (damg) wrote on 2011-10-07:

#10

The upstream developers marked this bug report as expired because the reported GNOME version is not being supported anymore.

The squashfs errors you reported look like errors either in the image you installed or in the hardware (usb pen or RAM).

Do you still experience the problem?

Robert Roth (evfool) on 2012-01-21

Changed in gnome-system-monitor (Ubuntu):
status:	Incomplete → Confirmed
status:	Confirmed → Incomplete

Revision history for this message

Robert Roth (evfool) wrote on 2012-01-25:

#11

As no answer came from the reporter (CoolKoon) about the reproducibility of this issue, I am closing this as Invalid. Feel free to reopen this if you still experience this behavior. Please if you reopen this bug, also comment with the detailed steps on how to reproduce this issue.

Changed in gnome-system-monitor (Ubuntu):
status:	Incomplete → Invalid

Revision history for this message

CoolKoon (coolkoon) wrote on 2012-01-25:

#12

Actually I've written above that my Squashfs was bad (or there was a read error). So before replacing the whole image the problem was reproducible 100% of the time. After I've replaced the squashfs image with another one however the issue has stopped.

Revision history for this message

Robert Roth (evfool) wrote on 2012-01-25:

#13

Thanks CoolKoon, I missed that. So anyway, the problem doesn't seem like it was a System Monitor issue, but rather a problem with your squashfs file, so the Invalid status for the system monitor bug still stands.
---
Ubuntu Bug Squad volunteer triager
http://wiki.ubuntu.com/BugSquad

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

gnome-bugs #601762
[RESOLVED INCOMPLETE] Edit

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

Ubuntugnome-system-monitor package

gnome-system-monitor keeps crashing with signal 7 (on a Jaunty booted from USB)

Bug Description

Other bug subscribers

Bug attachments

Remote bug watches

Ubuntu
gnome-system-monitor package