Bug 509001 – crash in Computer: je venais de connecter u...

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 509001 - crash in Computer: je venais de connecter u...


Summary:	crash in Computer: je venais de connecter u...


Status:	RESOLVED DUPLICATE of bug 355018

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:	2008-01-12 18:33 UTC by gedeon.legaut
Modified:	2008-01-13 12:01 UTC

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

Description gedeon.legaut 2008-01-12 18:33:43 UTC

Version: 2.18.3

What were you doing when the application crashed?
je venais de connecter un lecteur multimédia de salon en usb.
I had just connected a multimedia disk with usb.


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

System: Linux 2.6.22-3-486 #1 Mon Nov 12 07:53:08 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: 95338496 vsize: 95338496 resident: 31703040 share: 18399232 rss: 31703040 rss_rlim: 4294967295
CPU usage: start_time: 1200162795 rtime: 1080 utime: 602 stime: 478 cutime:1553 cstime: 109 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 0xb6dbf6b0 (LWP 4365)]
[New Thread 0xb57c1b90 (LWP 4676)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 185076

Thread 1 (Thread 0xb6dbf6b0 (LWP 4365))

#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 (12 sec old) ---------------------
** 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: don't know how to handle video/x-pn-realvideo, rmversion=(int)4, format=(int)1073741824, subformat=(int)17305632, width=(int)576, height=(int)304, framerate=(fraction)25/1
** (gnome-video-thumbnailer:4677): WARNING **: Could not take screenshot: no video info
** Message: don't know how to handle video/x-pn-realvideo, rmversion=(int)4, format=(int)1073741824, subformat=(int)17305632, width=(int)576, height=(int)304, framerate=(fraction)25/1
--------------------------------------------------

Comment 1 Cosimo Cecchi 2008-01-13 12:01:32 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 ***