Bug 448804 – crash in Computer: festplattenzugriff

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


Summary:	crash in Computer: festplattenzugriff


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:

Depends on:
Blocks:

Reported:	2007-06-18 15:08 UTC by deecee83
Modified:	2007-06-19 15:59 UTC

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

Description deecee83 2007-06-18 15:08:53 UTC

What were you doing when the application crashed?
festplattenzugriff


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

Memory status: size: 301039616 vsize: 301039616 resident: 5918720 share: 18743296 rss: 24662016 rss_rlim: 669685760
CPU usage: start_time: 1182179320 rtime: 90 utime: 83 stime: 7 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 46963894321792 (LWP 4476)]
(no debugging symbols found)
0x00002ab69fbadc5f in waitpid () from /lib64/libpthread.so.0

+ Trace 141901

Thread 1 (Thread 46963894321792 (LWP 4476))

#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-06-19 15:59:19 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 377443 ***