Bug 493502 – crash in File Browser:

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 493502 - crash in File Browser:


Summary:	crash in File Browser:


Status:	RESOLVED DUPLICATE of bug 440988

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-11-04 20:33 UTC by learusb
Modified:	2007-11-05 07:46 UTC

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

Description learusb 2007-11-04 20:33:16 UTC

Version: 2.18.3

What were you doing when the application crashed?



Distribution: Debian lenny/sid
Gnome Release: 2.18.3 2007-07-03 (Debian)
BugBuddy Version: 2.18.1

System: Linux 2.6.21-2-amd64 #1 SMP Tue Jul 10 21:39:38 UTC 2007 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Glider
Icon Theme: Mist

Memory status: size: 404492288 vsize: 404492288 resident: 45895680 share: 17915904 rss: 45895680 rss_rlim: 18446744073709551615
CPU usage: start_time: 1194200186 rtime: 4812 utime: 4220 stime: 592 cutime:473 cstime: 122 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 0x2b93d6a3abc0 (LWP 22058)]
(no debugging symbols found)
0x00002b93d00c8c7f in waitpid () from /lib/libpthread.so.0

+ Trace 175213

Thread 1 (Thread 0x2b93d6a3abc0 (LWP 22058))

#0 waitpid
from /lib/libpthread.so.0
#1 ??
from /usr/lib/libgnomeui-2.so.0
#2 <signal handler called>
#3 raise
from /lib/libc.so.6
#4 abort
from /lib/libc.so.6
#5 g_logv
from /usr/lib/libglib-2.0.so.0
#6 g_log
from /usr/lib/libglib-2.0.so.0
#7 g_assert_warning
from /usr/lib/libglib-2.0.so.0
#8 ??
from /usr/lib/libgtk-x11-2.0.so.0
#9 ??
#10 ??
#11 g_sequence_sort_changed_iter
#12 ??
from /usr/lib/libgtk-x11-2.0.so.0
#13 gtk_list_store_set_valist
from /usr/lib/libgtk-x11-2.0.so.0
#14 gtk_list_store_set
from /usr/lib/libgtk-x11-2.0.so.0
#15 ??
from /usr/lib/libeel-2-2.18.so
#16 g_closure_invoke
from /usr/lib/libgobject-2.0.so.0
#17 ??
from /usr/lib/libgobject-2.0.so.0
#18 g_signal_emit_valist
from /usr/lib/libgobject-2.0.so.0
#19 g_signal_emit
from /usr/lib/libgobject-2.0.so.0
#20 eel_mime_set_default_application
from /usr/lib/libeel-2-2.18.so
#21 ??
from /usr/lib/libeel-2-2.18.so
#22 g_closure_invoke
from /usr/lib/libgobject-2.0.so.0
#23 ??
from /usr/lib/libgobject-2.0.so.0
#24 g_signal_emit_valist
from /usr/lib/libgobject-2.0.so.0
#25 g_signal_emit
from /usr/lib/libgobject-2.0.so.0
#26 ??
from /usr/lib/libgtk-x11-2.0.so.0
#27 ??
from /usr/lib/libgtk-x11-2.0.so.0
#28 ??
from /usr/lib/libgtk-x11-2.0.so.0
#29 ??
from /usr/lib/libgtk-x11-2.0.so.0
#30 ??
from /usr/lib/libgtk-x11-2.0.so.0
#31 g_closure_invoke
from /usr/lib/libgobject-2.0.so.0
#32 ??
from /usr/lib/libgobject-2.0.so.0
#33 g_signal_emit_valist
from /usr/lib/libgobject-2.0.so.0
#34 g_signal_emit
from /usr/lib/libgobject-2.0.so.0
#35 ??
from /usr/lib/libgtk-x11-2.0.so.0
#36 gtk_propagate_event
from /usr/lib/libgtk-x11-2.0.so.0
#37 gtk_main_do_event
from /usr/lib/libgtk-x11-2.0.so.0
#38 ??
from /usr/lib/libgdk-x11-2.0.so.0
#39 g_main_context_dispatch
from /usr/lib/libglib-2.0.so.0
#40 ??
from /usr/lib/libglib-2.0.so.0
#41 g_main_loop_run
from /usr/lib/libglib-2.0.so.0
#42 gtk_main
from /usr/lib/libgtk-x11-2.0.so.0
#43 main
#0 waitpid
from /lib/libpthread.so.0



----------- .xsession-errors (61497 sec old) ---------------------
** Message: drive = 0
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
** Message: drive = 0
...Too much output, ignoring rest...
--------------------------------------------------

Comment 1 André Klapper 2007-11-05 07:46:09 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 440988 ***