Bug 701910 - [abrt] gnome-system-monitor-2.28.0-7.el6: Process /usr/bin/gnome-system-monitor was killed by signal 7 (SIGBUS)
Summary: [abrt] gnome-system-monitor-2.28.0-7.el6: Process /usr/bin/gnome-system-monit...
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: gnome-system-monitor
Version: 6.2
Hardware: i686
OS: Linux
medium
medium
Target Milestone: rc
: ---
Assignee: Søren Sandmann Pedersen
QA Contact: Desktop QE
URL:
Whiteboard:
Depends On:
Blocks: 756082
TreeView+ depends on / blocked
 
Reported: 2011-05-04 09:11 UTC by Siddharth
Modified: 2018-11-14 12:49 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-01-09 21:02:07 UTC
Target Upstream Version:

Attachments (Terms of Use)
Backtrace, Dissassembly (95.10 KB, application/octet-stream)
2011-05-04 09:15 UTC, Siddharth 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Description Siddharth 2011-05-04 09:11:21 UTC 
Description of problem:
cmdline: gnome-system-monitor --show-system-tab
component: gnome-system-monitor
executable: /usr/bin/gnome-system-monitor
kernel: 2.6.32-71.el6.i686
rating: 0
reason: Process /usr/bin/gnome-system-monitor was killed by signal 7 (SIGBUS)
time: 1303979679
uid: 501 


Version-Release number of selected component (if applicable):
Red Hat Enterprise Linux Server release 6.0 (Santiago)
gnome-system-monitor-2.28.0-7.el6
architecture: i686

How reproducible:
random crash

Steps to Reproduce:
1.
2.
3.
  
Actual results:
gnome-system-monitor was crashed

Expected results:
gnome-system-monitor should not crashed

Additional info:
Comment 2 Siddharth 2011-05-04 09:15:16 UTC 
Created attachment 496736 [details]
Backtrace, Dissassembly
Comment 3 Vladimir Benes 2011-05-26 10:42:29 UTC 
hi,
can you still reproduce? I cannot on i686 rhel6.1.. any special features that can cause this?
Comment 10 Brian Gollaher 2012-01-09 21:02:07 UTC 
Closing as we have been unable to reproduce the bug.
Note You need to log in before you can comment on or make changes to this bug.