Bug 511329 – crash in Home Folder: i plugged my photocamera

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 511329 - crash in Home Folder: i plugged my photocamera


Summary:	crash in Home Folder: i plugged my photocamera


Status:	RESOLVED DUPLICATE of bug 355018

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:	2008-01-22 18:34 UTC by stefan.seeland
Modified:	2008-01-23 10:28 UTC

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

Description stefan.seeland 2008-01-22 18:34:14 UTC

What were you doing when the application crashed?
i plugged my photocamera


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

System: Linux 2.6.22-3-686 #1 SMP Mon Nov 12 08:32:57 UTC 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: gnome

Memory status: size: 72265728 vsize: 72265728 resident: 22212608 share: 15212544 rss: 22212608 rss_rlim: 4294967295
CPU usage: start_time: 1201021105 rtime: 736 utime: 680 stime: 56 cutime:0 cstime: 0 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/i686/cmov/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 0xb6daa6b0 (LWP 4706)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 186371

Thread 1 (Thread 0xb6daa6b0 (LWP 4706))

#0 __kernel_vsyscall
#1 waitpid
from /lib/i686/cmov/libpthread.so.0
#2 g_spawn_sync
from /usr/lib/libglib-2.0.so.0
#3 g_spawn_command_line_sync
from /usr/lib/libglib-2.0.so.0
#4 ??
from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
#5 <signal handler called>
#6 strcmp
from /lib/i686/cmov/libc.so.6
#7 ??
#8 ??
#0 __kernel_vsyscall



----------- .xsession-errors (28 sec old) ---------------------
get tw05i137 pop://tw05i137@pop.technikum-wien.at/
Find Items 0
/usr/bin/play soxio: Failed writing `default': unknown file type `ao'
/usr/bin/play soxio: Failed writing `default': unknown file type `ao'
/usr/bin/play soxio: Failed writing `default': unknown file type `ao'
/usr/bin/play soxio: Failed writing `default': unknown file type `ao'
/usr/bin/play soxio: Failed writing `default': unknown file type `ao'
/usr/bin/play soxio: Failed writing `default': unknown file type `ao'
get stefan.seeland@gmx.at pop://stefan.seeland%40gmx.at@pop.gmx.net/
Find Items 0
get tw05i137 pop://tw05i137@pop.technikum-wien.at/
Find Items 0
** (update-notifier:4720): WARNING **: no cdrom: disk
--------------------------------------------------

Comment 1 Cosimo Cecchi 2008-01-23 10:28:25 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 355018 ***