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


Summary:	crash in Open Folder:


Status:	RESOLVED DUPLICATE of bug 417962

Product:	nautilus
Classification:	Core
Component:	general
Version:	2.18.x
Hardware:	Other All

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

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2007-10-05 19:00 UTC by Jack Tanner
Modified:	2007-10-08 11:07 UTC

See Also:
GNOME target:	---
GNOME version:	2.17/2.18

Description Jack Tanner 2007-10-05 19:00:12 UTC

Version: 2.18.3

What were you doing when the application crashed?



Distribution: Fedora release 7 (Moonshine)
Gnome Release: 2.18.3 2007-07-02 (Red Hat, Inc)
BugBuddy Version: 2.18.0

System: Linux 2.6.22.9-91.fc7 #1 SMP Thu Sep 27 20:47:39 EDT 2007 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: Permissive
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 576524288 vsize: 576524288 resident: 51761152 share: 25014272 rss: 51761152 rss_rlim: 18446744073709551615
CPU usage: start_time: 1191248920 rtime: 5184 utime: 4609 stime: 575 cutime:1 cstime: 13 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 46912496360512 (LWP 3277)]
0x0000003fc460d97f in waitpid () from /lib64/libpthread.so.0

+ Trace 168081

Thread 1 (Thread 46912496360512 (LWP 3277))

#0 waitpid
from /lib64/libpthread.so.0
#1 libgnomeui_segv_handle
at gnome-ui-init.c line 872
#2 <signal handler called>
#3 raise
from /lib64/libc.so.6
#4 abort
from /lib64/libc.so.6
#5 g_logv
from /lib64/libglib-2.0.so.0
#6 g_log
from /lib64/libglib-2.0.so.0
#7 g_assert_warning
from /lib64/libglib-2.0.so.0
#8 ??
#9 g_cclosure_marshal_VOID__ENUM
from /usr/lib64/libgtk-x11-2.0.so.0
#10 g_cclosure_marshal_VOID__ENUM
from /usr/lib64/libgtk-x11-2.0.so.0
#11 g_cclosure_marshal_VOID__ENUM
from /usr/lib64/libgtk-x11-2.0.so.0
#12 g_cclosure_marshal_VOID__ENUM
from /usr/lib64/libgtk-x11-2.0.so.0
#13 g_cclosure_marshal_VOID__ENUM
from /usr/lib64/libgtk-x11-2.0.so.0
#14 g_cclosure_marshal_VOID__ENUM
from /usr/lib64/libgtk-x11-2.0.so.0
#15 gtk_tree_row_reference_free
from /usr/lib64/libgtk-x11-2.0.so.0
#16 g_cclosure_marshal_VOID__ENUM
from /usr/lib64/libgtk-x11-2.0.so.0
#17 gtk_tree_view_set_cursor_on_cell
from /usr/lib64/libgtk-x11-2.0.so.0
#18 ??
#19 g_main_context_dispatch
from /lib64/libglib-2.0.so.0
#20 g_cclosure_marshal_VOID__ENUM
from /lib64/libglib-2.0.so.0
#21 g_main_loop_run
from /lib64/libglib-2.0.so.0
#22 gtk_main
from /usr/lib64/libgtk-x11-2.0.so.0
#23 main
#0 waitpid
from /lib64/libpthread.so.0



----------- .xsession-errors ---------------------
warning: difference appears to be caused by prelink, adjusting expectations
warning: .dynamic section for "/usr/lib64/libpoppler.so.1" is not at the expected address
warning: difference appears to be caused by prelink, adjusting expectations
warning: .dynamic section for "/usr/lib64/libstdc++.so.6" is not at the expected address (wrong library or version mismatch?)
warning: .dynamic section for "/lib64/libgcc_s.so.1" is not at the expected address
warning: difference appears to be caused by prelink, adjusting expectations
warning: .dynamic section for "/usr/lib64/libgnome-window-settings.so.1" is not at the expected address (wrong library or version mismatch?)
warning: .dynamic section for "/usr/lib64/libpanel-applet-2.so.0" is not at the expected address (wrong library or version mismatch?)
--------------------------------------------------

Comment 1 Cosimo Cecchi 2007-10-08 11:07:53 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 417962 ***