Bug 400162 – crash in System Monitor: opened printer configura...

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 400162 - crash in System Monitor: opened printer configura...


Summary:	crash in System Monitor: opened printer configura...


Status:	RESOLVED INCOMPLETE

Product:	system-monitor
Classification:	Core
Component:	general
Version:	2.16.x
Hardware:	Other All

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

URL:
Whiteboard:

Duplicates:	410789 413900 423129 446235 (view as bug list)
Depends on:
Blocks:

Reported:	2007-01-24 11:37 UTC by camillo.imbimbo
Modified:	2011-11-11 10:03 UTC

See Also:
GNOME target:	---
GNOME version:	2.15/2.16

Description camillo.imbimbo 2007-01-24 11:37:00 UTC

Version: 2.16.1

What were you doing when the application crashed?
opened printer configuration and system monitor at
the same time


Distribution: Ubuntu 6.10 (edgy)
Gnome Release: 2.16.1 2006-10-02 (Ubuntu)
BugBuddy Version: 2.16.0

Memory status: size: 36233216 vsize: 0 resident: 36233216 share: 0 rss: 15659008 rss_rlim: 0
CPU usage: start_time: 1169638482 rtime: 0 utime: 376 stime: 0 cutime:306 cstime: 0 timeout: 70 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/tls/i686/cmov/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1224960336 (LWP 9987)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 104829

Thread 1 (Thread -1224960336 (LWP 9987))

#0 __kernel_vsyscall
#1 __waitpid_nocancel
from /lib/tls/i686/cmov/libpthread.so.0
#2 gnome_gtk_module_info_get
from /usr/lib/libgnomeui-2.so.0
#3 <signal handler called>
#4 __kernel_vsyscall
#5 raise
from /lib/tls/i686/cmov/libc.so.6
#6 abort
from /lib/tls/i686/cmov/libc.so.6
#7 g_logv
from /usr/lib/libglib-2.0.so.0
#8 g_log
from /usr/lib/libglib-2.0.so.0
#9 g_assert_warning
from /usr/lib/libglib-2.0.so.0
#10 gtk_tree_store_new
from /usr/lib/libgtk-x11-2.0.so.0
#11 gtk_tree_store_new
from /usr/lib/libgtk-x11-2.0.so.0
#12 gtk_tree_store_remove
from /usr/lib/libgtk-x11-2.0.so.0
#13 ??
#14 ??
#15 ??
#16 ??
#17 ??
#18 ??
#0 __kernel_vsyscall

Comment 1 André Klapper 2007-01-28 14:45:06 UTC

Thanks for taking the time to report this bug.
Unfortunately, the stack trace is missing some elements that will help a lot to solve the problem, so it will be hard for the developers to fix that crash.

Could you please help fixing this by installing some debugging packages [1], start Nautilus as normal, and try to reproduce the crash, if possible?

Once bug-buddy pops up, you can find the stacktrace in the 'Details', now containing way more information. Please copy that stacktrace and paste it as a comment here. Thanks in advance!

[1] Please install the following debug packages provided by Ubuntu: libglib2.0-0-dbg and libgtk2.0-0-dbg.

More details can be found here: http://live.gnome.org/GettingTraces

Comment 2 palfrey 2007-02-22 15:01:56 UTC

*** Bug 410789 has been marked as a duplicate of this bug. ***

Comment 3 Pedro Villavicencio 2007-03-03 00:49:48 UTC

*** Bug 413900 has been marked as a duplicate of this bug. ***

Comment 4 Pedro Villavicencio 2007-05-26 18:10:49 UTC

*** Bug 423129 has been marked as a duplicate of this bug. ***

Comment 5 Pedro Villavicencio 2007-06-12 02:06:56 UTC

*** Bug 446235 has been marked as a duplicate of this bug. ***

Comment 6 Benoît Dejean 2007-06-28 07:43:16 UTC

Thanks for taking the time to report this bug.
This bug report isn't very useful because it doesn't describe the bug well. If you have time and can still reproduce the bug, please read http://bugzilla.gnome.org/bug-HOWTO.html and add a description of how to reproduce this bug.

You'll also need to add a stack trace; please see http://live.gnome.org/GettingTraces for more information about how to do so. Thanks in advance!