Bug 416680 – crash in Open 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 416680 - crash in Open Folder:


Summary:	crash in Open Folder:


Status:	RESOLVED DUPLICATE of bug 363289

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-03-10 04:28 UTC by doorsrick
Modified:	2007-06-20 21:07 UTC

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

Description doorsrick 2007-03-10 04:28:17 UTC

What were you doing when the application crashed?



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

Memory status: size: 26816512 vsize: 0 resident: 112406528 share: 0 rss: 112406528 rss_rlim: 0
CPU usage: start_time: 102 rtime: 0 utime: 1173500417 stime: 0 cutime:366 cstime: 0 timeout: 335 it_real_value: 0 frequency: 31

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 805565872 (LWP 4037)]
(no debugging symbols found)
0x0f23a370 in __waitpid_nocancel () from /lib/libpthread.so.0

+ Trace 117369

Thread 1 (Thread 805565872 (LWP 4037))

#0 __waitpid_nocancel
from /lib/libpthread.so.0
#1 gnome_gtk_module_info_get
from /usr/lib/libgnomeui-2.so.0
#2 <signal handler called>
#3 _gtk_icon_cache_add_icons
from /usr/lib/libgtk-x11-2.0.so.0
#4 gtk_icon_theme_list_icons
from /usr/lib/libgtk-x11-2.0.so.0
#5 ??
#6 ??
#7 ??
#8 g_type_create_instance
from /usr/lib/libgobject-2.0.so.0
#9 g_object_set
from /usr/lib/libgobject-2.0.so.0
#10 g_object_newv
from /usr/lib/libgobject-2.0.so.0
#11 g_object_new_valist
from /usr/lib/libgobject-2.0.so.0
#12 g_object_new
from /usr/lib/libgobject-2.0.so.0
#13 ??
#14 ??
#15 ??
#16 ??
#17 g_cclosure_marshal_VOID__VOID
from /usr/lib/libgobject-2.0.so.0
#18 g_value_set_boxed
from /usr/lib/libgobject-2.0.so.0
#19 g_closure_invoke
from /usr/lib/libgobject-2.0.so.0
#20 g_signal_chain_from_overridden
from /usr/lib/libgobject-2.0.so.0
#21 g_signal_emit_valist
from /usr/lib/libgobject-2.0.so.0
#22 g_signal_emit
from /usr/lib/libgobject-2.0.so.0
#23 gtk_widget_show
from /usr/lib/libgtk-x11-2.0.so.0
#24 ??
#25 ??
#26 ??
#27 ??
#28 ??
#29 ??
#30 g_source_is_destroyed
from /usr/lib/libglib-2.0.so.0
#31 g_source_is_destroyed
from /usr/lib/libglib-2.0.so.0
#32 g_source_is_destroyed
from /usr/lib/libglib-2.0.so.0
#33 g_source_is_destroyed
from /usr/lib/libglib-2.0.so.0
#34 g_source_is_destroyed
from /usr/lib/libglib-2.0.so.0
#35 g_source_is_destroyed
from /usr/lib/libglib-2.0.so.0
#36 g_source_is_destroyed
from /usr/lib/libglib-2.0.so.0
#37 g_source_is_destroyed
from /usr/lib/libglib-2.0.so.0
#38 g_source_is_destroyed
from /usr/lib/libglib-2.0.so.0
#0 __waitpid_nocancel
from /lib/libpthread.so.0

Comment 1 palfrey 2007-03-10 23:36:50 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 André Klapper 2007-06-20 21:07:39 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.


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