Bug 505024 – crash in File Browser: After mounting a pendriv...

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 505024 - crash in File Browser: After mounting a pendriv...


Summary:	crash in File Browser: After mounting a pendriv...


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-12-22 11:07 UTC by lopay
Modified:	2007-12-23 19:51 UTC

See Also:
GNOME target:	---
GNOME version:	2.19/2.20

Description lopay 2007-12-22 11:07:45 UTC

Version: 2.18.3

What were you doing when the application crashed?
After mounting a pendrive, i wanted to open Properties for one of the folders


Distribution: Debian lenny/sid
Gnome Release: 2.20.2 2007-11-29 (Debian)
BugBuddy Version: 2.20.1

System: Linux 2.6.23.9-custom #1 SMP Mon Dec 10 07:10:19 CET 2007 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Smoked Glass
Icon Theme: glass-icons

Memory status: size: 390295552 vsize: 390295552 resident: 38072320 share: 17330176 rss: 38072320 rss_rlim: 18446744073709551615
CPU usage: start_time: 1198309170 rtime: 1250 utime: 1067 stime: 183 cutime:1 cstime: 1 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 0x2b05322a9590 (LWP 24124)]
(no debugging symbols found)
0x00002b052b94a34f in waitpid () from /lib/libpthread.so.0

+ Trace 182632

Thread 1 (Thread 0x2b05322a9590 (LWP 24124))

#0 waitpid
from /lib/libpthread.so.0
#1 g_spawn_sync
from /usr/lib/libglib-2.0.so.0
#2 g_spawn_command_line_sync
from /usr/lib/libglib-2.0.so.0
#3 ??
from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
#4 <signal handler called>
#5 strcmp
from /lib/libc.so.6
#6 ??
#7 g_closure_invoke
from /usr/lib/libgobject-2.0.so.0
#8 ??
from /usr/lib/libgobject-2.0.so.0
#9 g_signal_emit_valist
from /usr/lib/libgobject-2.0.so.0
#10 g_signal_emit
from /usr/lib/libgobject-2.0.so.0
#11 ??
from /usr/lib/libgtk-x11-2.0.so.0
#12 g_closure_invoke
from /usr/lib/libgobject-2.0.so.0
#13 ??
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
from /usr/lib/libgobject-2.0.so.0
#16 gtk_list_store_remove
from /usr/lib/libgtk-x11-2.0.so.0
#17 gtk_list_store_clear
from /usr/lib/libgtk-x11-2.0.so.0
#18 ??
#19 g_closure_invoke
from /usr/lib/libgobject-2.0.so.0
#20 ??
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 nautilus_file_emit_changed
#24 nautilus_directory_emit_change_signals
#25 nautilus_file_changed
#26 ??
#27 ??
from /usr/lib/libgnomevfs-2.so.0
#28 g_main_context_dispatch
from /usr/lib/libglib-2.0.so.0
#29 ??
from /usr/lib/libglib-2.0.so.0
#30 g_main_loop_run
from /usr/lib/libglib-2.0.so.0
#31 gtk_main
from /usr/lib/libgtk-x11-2.0.so.0
#32 main
#0 waitpid
from /lib/libpthread.so.0



----------- .xsession-errors (8923 sec old) ---------------------
m| 121514
 wlan0:48476197  109478    0    0    0     0          0         0  9438832  102891    0    0    0     0       0          0
 wlan0:48494331  109521    0    0    0     0          0         0  9441520  102923    0    0    0     0       0          0
not trans
2688
m| 121514
 wlan0:48508589  109554    0    0    0     0          0         0  9444292  102956    0    0    0     0       0          0
not trans
5460
m| 121514
:images/receiving-good-signal-lock.png
|receiving-good-signal-lock.png
 wlan0:48522663  109587    0    0    0     0          0         0  9447064  102989    0    0    0     0       0          0
 wlan0:48536864  109620    0    0    0     0    
...Too much output, ignoring rest...
--------------------------------------------------

Comment 1 Susana 2007-12-23 19:51:48 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 ***