Bug 483059 – crash in Computer:

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 483059 - crash in Computer:


Summary:	crash in Computer:


Status:	RESOLVED DUPLICATE of bug 377443

Product:	nautilus
Classification:	Core
Component:	general
Version:	unspecified
Hardware:	Other All

Importance:	High critical
Target Milestone:	---
Assigned To:	Nautilus Maintainers
QA Contact:	Nautilus Maintainers

URL:
Whiteboard:

Duplicates:	483060 483061 483062 (view as bug list)
Depends on:
Blocks:

Reported:	2007-10-03 19:13 UTC by sulle
Modified:	2007-10-04 12:55 UTC

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

Description sulle 2007-10-03 19:13:36 UTC

What were you doing when the application crashed?



Distribution: openSUSE 10.2 (X86-64)
Gnome Release: 2.16.1 2006-11-28 (SUSE)
BugBuddy Version: 2.16.0

Memory status: size: 376283136 vsize: 376283136 resident: 6688768 share: 27959296 rss: 34648064 rss_rlim: 613370880
CPU usage: start_time: 1191438775 rtime: 44 utime: 40 stime: 4 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

Backtrace was generated from '/opt/gnome/bin/nautilus'

(no debugging symbols found)
Using host libthread_db library "/lib64/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 47223427265120 (LWP 8070)]
(no debugging symbols found)
0x00002af30d194c5f in waitpid () from /lib64/libpthread.so.0

+ Trace 167486

Thread 1 (Thread 47223427265120 (LWP 8070))

#0 waitpid
from /lib64/libpthread.so.0
#1 gnome_gtk_module_info_get
from /opt/gnome/lib64/libgnomeui-2.so.0
#2 <signal handler called>
#3 gtk_hsv_new
from /opt/gnome/lib64/libgtk-x11-2.0.so.0
#4 gtk_icon_theme_list_icons
from /opt/gnome/lib64/libgtk-x11-2.0.so.0
#5 nautilus_directory_ref
#6 POA_Nautilus_MetafileMonitor__init
#7 POA_Nautilus_MetafileMonitor__init
#8 g_type_create_instance
from /opt/gnome/lib64/libgobject-2.0.so.0
#9 g_object_set
from /opt/gnome/lib64/libgobject-2.0.so.0
#10 g_object_newv
from /opt/gnome/lib64/libgobject-2.0.so.0
#11 g_object_new_valist
from /opt/gnome/lib64/libgobject-2.0.so.0
#12 g_object_new
from /opt/gnome/lib64/libgobject-2.0.so.0
#13 POA_Nautilus_MetafileMonitor__init
#14 POA_Nautilus_MetafileMonitor__init
#15 POA_Nautilus_MetafileMonitor__init
#16 g_closure_invoke
from /opt/gnome/lib64/libgobject-2.0.so.0
#17 g_signal_override_class_closure
from /opt/gnome/lib64/libgobject-2.0.so.0
#18 g_signal_emit_valist
from /opt/gnome/lib64/libgobject-2.0.so.0
#19 g_signal_emit
from /opt/gnome/lib64/libgobject-2.0.so.0
#20 gtk_widget_show
from /opt/gnome/lib64/libgtk-x11-2.0.so.0
#21 POA_Nautilus_MetafileMonitor__init
#22 fm_directory_view_bump_zoom_level
#23 nautilus_clipboard_monitor_emit_changed
#24 nautilus_directory_async_state_changed
#25 nautilus_icon_container_request_update_all
#26 g_main_context_dispatch
from /opt/gnome/lib64/libglib-2.0.so.0
#27 g_main_context_prepare
from /opt/gnome/lib64/libglib-2.0.so.0
#28 g_main_loop_run
from /opt/gnome/lib64/libglib-2.0.so.0
#29 gtk_main
from /opt/gnome/lib64/libgtk-x11-2.0.so.0
#30 POA_Nautilus_MetafileMonitor__init
#31 __libc_start_main
from /lib64/libc.so.6
#32 g_cclosure_marshal_VOID__ENUM
#33 ??
#34 ??
#0 waitpid
from /lib64/libpthread.so.0

Comment 1 André Klapper 2007-10-04 12:55:47 UTC

Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade of gtk+.


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

Comment 2 André Klapper 2007-10-04 12:55:52 UTC

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

Comment 3 André Klapper 2007-10-04 12:55:54 UTC

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

Comment 4 André Klapper 2007-10-04 12:55:56 UTC

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