Bug 433835 – 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 433835 - 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-04-27 10:31 UTC by spam
Modified:	2007-05-07 20:23 UTC

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

Description spam 2007-04-27 10:31:13 UTC

What were you doing when the application crashed?



Distribution: Gentoo Base System release 1.12.10
Gnome Release: 2.16.3 2007-04-05 (Gentoo)
BugBuddy Version: 2.16.0

Memory status: size: 339152896 vsize: 339152896 resident: 63148032 share: 21917696 rss: 63148032 rss_rlim: -1
CPU usage: start_time: 1177667006 rtime: 7595 utime: 7058 stime: 537 cutime:1023 cstime: 221 timeout: 0 it_real_value: 0 frequency: 100

Backtrace was generated from '/usr/bin/nautilus'

(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 47766854496432 (LWP 5348)]
[New Thread 1149409600 (LWP 7102)]
0x00002b7195159aef in waitpid () from /lib/libpthread.so.0

+ Trace 130869

Thread 1 (Thread 47766854496432 (LWP 5348))

#0 waitpid
from /lib/libpthread.so.0
#1 gnome_gtk_module_info_get
from /usr/lib/libgnomeui-2.so.0
#2 <signal handler called>
#3 gtk_ui_manager_remove_ui
from /usr/lib/libgtk-x11-2.0.so.0
#4 nautilus_marshal_BOOLEAN__POINTER
#5 fm_directory_view_bump_zoom_level
#6 fm_directory_view_pop_up_location_context_menu
#7 fm_directory_view_update_menus
#8 g_closure_invoke
from /usr/lib/libgobject-2.0.so.0
#9 g_signal_chain_from_overridden
from /usr/lib/libgobject-2.0.so.0
#10 g_signal_emit_valist
from /usr/lib/libgobject-2.0.so.0
#11 g_signal_emit_by_name
from /usr/lib/libgobject-2.0.so.0
#12 g_closure_invoke
from /usr/lib/libgobject-2.0.so.0
#13 g_signal_chain_from_overridden
from /usr/lib/libgobject-2.0.so.0
#14 g_signal_emit_valist
from /usr/lib/libgobject-2.0.so.0
#15 g_signal_emit_by_name
from /usr/lib/libgobject-2.0.so.0
#16 nautilus_module_initialize
from /usr/lib64/nautilus/extensions-1.0/libnautilus-burn-extension.so
#17 g_main_context_dispatch
from /usr/lib/libglib-2.0.so.0
#18 g_main_context_dispatch
from /usr/lib/libglib-2.0.so.0
#19 g_main_loop_run
from /usr/lib/libglib-2.0.so.0
#20 gtk_main
from /usr/lib/libgtk-x11-2.0.so.0
#21 POA_Nautilus_MetafileMonitor__init
#22 __libc_start_main
from /lib/libc.so.6
#23 ??
#24 ??
#25 ??
#0 waitpid
from /lib/libpthread.so.0

Comment 1 palfrey 2007-04-27 11:21:09 UTC

Thanks for taking the time to report this bug.
Unfortunately, that 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.
Can you get us a stack trace with debugging symbols? Please see
http://live.gnome.org/GettingTraces for more information on how to do so.
Thanks in advance!

Comment 2 Christian Kirbach 2007-05-07 20:23:35 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 ***