Bug 510477 – crash in File Browser: Checking usb drive

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 510477 - crash in File Browser: Checking usb drive


Summary:	crash in File Browser: Checking usb drive


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-18 20:52 UTC by Francisco Espinoza
Modified:	2008-01-19 01:22 UTC

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

Description Francisco Espinoza 2008-01-18 20:52:23 UTC

Version: 2.18.3

What were you doing when the application crashed?
Checking usb drive


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: Nuvola
Icon Theme: Nuvola

Memory status: size: 109248512 vsize: 109248512 resident: 42770432 share: 16424960 rss: 42770432 rss_rlim: 4294967295
CPU usage: start_time: 1200658942 rtime: 384831 utime: 334263 stime: 50568 cutime:3 cstime: 3 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 0xb6d836b0 (LWP 5799)]
[New Thread 0xb2a72b90 (LWP 12275)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 185873

Thread 1 (Thread 0xb6d836b0 (LWP 5799))

#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 (13785 sec old) ---------------------
	->lsb/usr/hpijs/HP/HP-LaserJet_5200-hpijs.ppd (HP LaserJet 5200 Foomatic/hpijs - HPLIP 2.7.10[0]) and
	->hpijs/HP/HP-LaserJet_5200-hpijs.ppd (HP LaserJet 5200 Foomatic/hpijs - HPLIP 2.7.10)[0]

** (gnome-cups-add:6402): WARNING **: Two ppds have driver == 'hpijs - HPLIP 2.7.10'
	->lsb/usr/hpijs/HP/HP-LaserJet_5200L-hpijs.ppd (HP LaserJet 5200L Foomatic/hpijs - HPLIP 2.7.10[0]) and
	->hpijs/HP/HP-LaserJet_5200L-hpijs.ppd (HP LaserJet 5200L Foomatic/hpijs - HPLIP 2.7.10)[0]

** (gnome-cups-add:6402): WARNING **: Two ppds have driver == 'hpijs - HPLIP 2.7.10'
	->lsb/usr/hpijs/HP/HP-LaserJet_8000-hpijs.ppd (HP LaserJet 8000 Foomatic/hpijs - HPLIP 2.7.10[0]) and
	->hpijs/HP/HP-LaserJet_8000-hpijs.ppd (HP LaserJet 8000 Foomatic/hpijs - HPLIP 2.7.10)[0]

** (gnome-cups-add:6402): WARNING **: Two ppds have driver == 'hpijs - HPLIP 2.7.10'
	->lsb/usr/hpijs/HP/HP-LaserJet_8100-hpijs.ppd (HP LaserJet 8100 Foomatic/hpijs - HPLIP 2.7.10[0]) and
	->hpijs/HP/HP-LaserJet_8100-hpijs.ppd (HP LaserJet 8100 Foomatic/hpijs - HPLIP 2.7.10)[0]
...Too much output, ignoring rest...
--------------------------------------------------

Comment 1 Cosimo Cecchi 2008-01-19 01:22:35 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 ***