Bug 391074 – crash in System Monitor: I tried to start yumex u...

After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.

Bug 391074 - crash in System Monitor: I tried to start yumex u...


Summary:	crash in System Monitor: I tried to start yumex u...


Status:	RESOLVED DUPLICATE of bug 389327

Product:	system-monitor
Classification:	Core
Component:	general
Version:	unspecified
Hardware:	Other All

Importance:	High critical
Target Milestone:	---
Assigned To:	System-monitor maintainers
QA Contact:	System-monitor maintainers

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2006-12-30 19:52 UTC by jseppola
Modified:	2011-11-11 10:03 UTC

See Also:
GNOME target:	---
GNOME version:	2.17/2.18

Description jseppola 2006-12-30 19:52:50 UTC

Version: 2.17.4.2

What were you doing when the application crashed?
I tried to start yumex updating of FC6


Distribution: Fedora Core release 6 (Rawhide)
Gnome Release: 2.17.2 2006-11-07 (Red Hat, Inc)
BugBuddy Version: 2.17.3

System: Linux 2.6.19-1.2891.fc7 #1 SMP Thu Dec 21 10:59:07 EST 2006 i686
X Vendor: The X.Org Foundation
X Vendor Release: 70101000
Selinux: No
Accessibility: Enabled

Memory status: size: 47501312 vsize: 0 resident: 47501312 share: 0 rss: 16285696 rss_rlim: 0
CPU usage: start_time: 1167508278 rtime: 0 utime: 92 stime: 0 cutime:64 cstime: 0 timeout: 28 it_real_value: 0 frequency: 0

Backtrace was generated from '/usr/bin/gnome-system-monitor'

(no debugging symbols found)
Using host libthread_db library "/lib/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1208260896 (LWP 2674)]
(no debugging symbols found)
0x00cdd402 in __kernel_vsyscall ()

+ Trace 98098

Thread 1 (Thread -1208260896 (LWP 2674))

#0 __kernel_vsyscall
#1 __waitpid_nocancel
from /lib/libpthread.so.0
#2 libgnomeui_module_info_get
from /usr/lib/libgnomeui-2.so.0
#3 <signal handler called>
#4 strlen
from /lib/libc.so.6
#5 giop_send_buffer_append_string
from /usr/lib/libORBit-2.so.0
#6 ORBit_marshal_value
from /usr/lib/libORBit-2.so.0
#7 ORBit_marshal_value
from /usr/lib/libORBit-2.so.0
#8 ORBit_marshal_any
from /usr/lib/libORBit-2.so.0
#9 ORBit_marshal_value
from /usr/lib/libORBit-2.so.0
#10 ORBit_marshal_value
from /usr/lib/libORBit-2.so.0
#11 ORBit_small_allocbuf
from /usr/lib/libORBit-2.so.0
#12 ORBit_small_invoke_stub
from /usr/lib/libORBit-2.so.0
#13 ORBit_small_invoke_stub_n
from /usr/lib/libORBit-2.so.0
#14 ORBit_c_stub_invoke
from /usr/lib/libORBit-2.so.0
#15 Accessibility_EventListener_notifyEvent
from /usr/lib/libspi.so.0
#16 ??
from /usr/lib/gtk-2.0/modules/libatk-bridge.so
#17 ??
from /usr/lib/gtk-2.0/modules/libatk-bridge.so
#18 exit
from /lib/libc.so.6
#19 __libc_start_main
from /lib/libc.so.6
#20 __cxa_pure_virtual
#0 __kernel_vsyscall



----------- .xsession-errors ---------------------
  File "/usr/lib/python2.5/site-packages/yumex/yumexBase.py", line 445, in build_package_lists
    self.doUpdateSetup()
  File "/usr/lib/python2.5/site-packages/yum/__init__.py", line 357, in doUpdateSetup
    self.pkgSack.simplePkgList())
  File "/usr/lib/python2.5/site-packages/yum/pack/usr/share/yumex/yumex: line 5:  2669 Tapettu                 /usr/bin/python /usr/share/yumex/yumexmain.pyc $*
GTK Accessibility Module initialized
Bonobo accessibility support initialized
** (gnome-system-monitor:2674): WARNING **: SELinux was found but is not enabled.
GTK Accessibility Module initialized
Bonobo accessibility support initialized
GTK Accessibility Module initialized
Bonobo accessibility support initialized
GTK Accessibility Module initialized
--------------------------------------------------

Comment 1 Susana 2006-12-30 20:28:49 UTC

Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.


*** This bug has been marked as a duplicate of 389327 ***