Bug 505313 – crash in File Browser: Intentando abrir un disp...

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 505313 - crash in File Browser: Intentando abrir un disp...


Summary:	crash in File Browser: Intentando abrir un disp...


Status:	RESOLVED DUPLICATE of bug 485526

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-23 22:31 UTC by Francisco Espinoza
Modified:	2007-12-24 14:30 UTC

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

Description Francisco Espinoza 2007-12-23 22:31:38 UTC

Version: 2.18.3

What were you doing when the application crashed?
Intentando abrir un dispositivo removible


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: 101752832 vsize: 101752832 resident: 35098624 share: 16330752 rss: 35098624 rss_rlim: 4294967295
CPU usage: start_time: 1198447013 rtime: 1443 utime: 1324 stime: 119 cutime:5 cstime: 4 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 0xb6dc06b0 (LWP 3659)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 182846

Thread 1 (Thread 0xb6dc06b0 (LWP 3659))

#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 (1779 sec old) ---------------------

** (gnome-cups-add:4037): WARNING **: Two ppds have driver == 'hpijs (recommended) - HPLIP 2.7.10'
	->lsb/usr/hpijs/HP/HP-DeskJet_5650-hpijs.ppd (HP DeskJet 5650 Foomatic/hpijs (recommended) - HPLIP 2.7.10[1]) and
	->hpijs/HP/HP-DeskJet_5650-hpijs.ppd (HP DeskJet 5650 Foomatic/hpijs (recommended) - HPLIP 2.7.10)[1]

** (gnome-cups-add:4037): WARNING **: Two ppds have driver == 'hpijs (recommended) - HPLIP 2.7.10'
	->lsb/usr/hpijs/HP/HP-DeskJet_5652-hpijs.ppd (HP DeskJet 5652 Foomatic/hpijs (recommended) - HPLIP 2.7.10[1]) and
	->hpijs/HP/HP-DeskJet_5652-hpijs.ppd (HP DeskJet 5652 Foomatic/hpijs (recommended) - HPLIP 2.7.10)[1]

** (gnome-cups-add:4037): WARNING **: Two ppds have driver == 'hpijs (recommended) - HPLIP 2.7.10'
	->lsb/usr/hpijs/HP/HP-DeskJet_5670-hpijs.ppd (HP DeskJet 5670 Foomatic/hpijs (recommended) - HPLIP 2.7.10[1]) and
	->hpijs/HP/HP-DeskJet_5670-hpijs.ppd (HP DeskJet 5670 Foomatic/hpijs (recommended) - HPLIP 2.7.10)[1]

** (gnome-cups-add:4037): WARNING **: Two ppds have driver == 'hpijs (recommended) - HPLIP 2.7.10
...Too much output, ignoring rest...
--------------------------------------------------

Comment 1 Cosimo Cecchi 2007-12-24 14:30:32 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 485526 ***