Bug 405873 – crash in Home Folder:

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 405873 - crash in Home Folder:


Summary:	crash in Home Folder:


Status:	RESOLVED DUPLICATE of bug 374002

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-02-08 19:51 UTC by ozk
Modified:	2007-02-09 01:04 UTC

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

Description ozk 2007-02-08 19:51:21 UTC

What were you doing when the application crashed?



Distribution: Fedora Core release 6 (Zod)
Gnome Release: 2.16.0 2006-09-04 (Red Hat, Inc)
BugBuddy Version: 2.16.0

System: Linux 2.6.19-1.2895.fc6 #1 SMP Wed Jan 10 18:50:56 EST 2007 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 70101000
Selinux: No
Accessibility: Disabled

Memory status: size: 457838592 vsize: 457838592 resident: 34050048 share: 19886080 rss: 34050048 rss_rlim: -1
CPU usage: start_time: 1170964196 rtime: 338 utime: 274 stime: 64 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

Backtrace was generated from '/usr/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 46912496342960 (LWP 6941)]
(no debugging symbols found)
0x0000003aa120d96f in waitpid () from /lib64/libpthread.so.0

+ Trace 109122

Thread 1 (Thread 46912496342960 (LWP 6941))

#0 waitpid
from /lib64/libpthread.so.0
#1 gnome_gtk_module_info_get
from /usr/lib64/libgnomeui-2.so.0
#2 <signal handler called>
#3 gtk_ui_manager_remove_ui
from /usr/lib64/libgtk-x11-2.0.so.0
#4 nautilus_marshal_BOOLEAN__POINTER
#5 fm_directory_view_bump_zoom_level
#6 fm_directory_view_update_menus
#7 fm_directory_view_bump_zoom_level
#8 g_source_get_current_time
from /lib64/libglib-2.0.so.0
#9 g_main_context_dispatch
from /lib64/libglib-2.0.so.0
#10 g_main_context_check
from /lib64/libglib-2.0.so.0
#11 g_main_loop_run
from /lib64/libglib-2.0.so.0
#12 gtk_main
from /usr/lib64/libgtk-x11-2.0.so.0
#13 POA_Nautilus_MetafileMonitor__init
#14 __libc_start_main
from /lib64/libc.so.6
#15 g_cclosure_marshal_VOID__ENUM
#16 ??
#17 ??
#0 waitpid
from /lib64/libpthread.so.0

Comment 1 Mariano Suárez-Alvarez 2007-02-09 01:04:15 UTC

Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but the maintainers need more information to fix the bug. Could you please answer the questions in the other report in order to help the developers?


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