Bug 529259 – crash in File Browser: Exploring a SAMBA(smb) F...

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 529259 - crash in File Browser: Exploring a SAMBA(smb) F...


Summary:	crash in File Browser: Exploring a SAMBA(smb) F...


Status:	RESOLVED DUPLICATE of bug 522534

Product:	nautilus
Classification:	Core
Component:	general
Version:	2.20.x
Hardware:	Other All

Importance:	High critical
Target Milestone:	---
Assigned To:	Nautilus Maintainers
QA Contact:	Nautilus Maintainers

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2008-04-21 19:07 UTC by madian001
Modified:	2008-04-22 17:28 UTC

See Also:
GNOME target:	---
GNOME version:	2.21/2.22

Description madian001 2008-04-21 19:07:23 UTC

Version: 2.20.0

What were you doing when the application crashed?
Exploring a SAMBA(smb) Folder


Distribution: Debian lenny/sid
Gnome Release: 2.22.0 2008-03-14 (Debian)
BugBuddy Version: 2.22.0

System: Linux 2.6.24-1-686 #1 SMP Thu Mar 27 17:45:04 UTC 2008 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Human
Icon Theme: Nuvola

Memory status: size: 96976896 vsize: 96976896 resident: 32169984 share: 17125376 rss: 32169984 rss_rlim: 4294967295
CPU usage: start_time: 1208804758 rtime: 169 utime: 158 stime: 11 cutime:2 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/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 0xb6b8b720 (LWP 8667)]
[New Thread 0xb3ee7b90 (LWP 8684)]
(no debugging symbols found)
0xb759ff91 in waitpid () from /lib/libpthread.so.0

+ Trace 195800

Thread 1 (Thread 0xb6b8b720 (LWP 8667))

#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 ??
#6 ??
#7 ??
#8 ??
#9 ??
from /usr/lib/libglib-2.0.so.0
#10 ??
#11 ??
#12 ??
#13 ??
from /usr/lib/libglib-2.0.so.0
#14 ??
#0 waitpid
from /lib/libpthread.so.0



----------- .xsession-errors (1795 sec old) ---------------------
	->lsb/usr/postscript/Kyocera/Kyocera_Mita_Ci-1100_it.ppd.gz (Kyocera Mita Ci-1100[0]) and
	->lsb/usr/postscript/Kyocera/Kyocera_Mita_Ci-1100_fr.ppd.gz (Kyocera Mita Ci-1100)[0]

** (gnome-cups-add:7748): WARNING **: Two ppds have driver == 'Estándar'
	->lsb/usr/postscript/Kyocera/Kyocera_Mita_Ci-1100_pt.ppd.gz (Kyocera Mita Ci-1100[0]) and
	->lsb/usr/postscript/Kyocera/Kyocera_Mita_Ci-1100_it.ppd.gz (Kyocera Mita Ci-1100)[0]

** (gnome-cups-add:7748): WARNING **: Two ppds have driver == 'Estándar'
	->lsb/usr/postscript/Kyocera/Kyocera_Mita_CS-1650_en.ppd.gz (Kyocera Mita CS-1650[0]) and
	->lsb/usr/postscript/Kyocera/Kyocera_Mita_CS-1650_de.ppd.gz (Kyocera Mita CS-1650)[0]

** (gnome-cups-add:7748): WARNING **: Two ppds have driver == 'Estándar'
	->lsb/usr/postscript/Kyocera/Kyocera_Mita_CS-1650_es.ppd.gz (Kyocera Mita CS-1650[0]) and
	->lsb/usr/postscript/Kyocera/Kyocera_Mita_CS-1650_en.ppd.gz (Kyocera Mita CS-1650)[0]
...Too much output, ignoring rest...
--------------------------------------------------

Comment 1 Gianluca Borello 2008-04-22 17:28:56 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 522534 ***