Bug 539507 – crash in Open Folder: Trying to connect to a W...

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 539507 - crash in Open Folder: Trying to connect to a W...


Summary:	crash in Open Folder: Trying to connect to a W...


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-06-21 18:50 UTC by pmlco
Modified:	2008-06-21 21:37 UTC

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

Description pmlco 2008-06-21 18:50:34 UTC

Version: 2.20.0

What were you doing when the application crashed?
Trying to connect to a Windows file share


Distribution: Debian lenny/sid
Gnome Release: 2.22.2 2008-05-29 (Debian)
BugBuddy Version: 2.22.0

System: Linux 2.6.24-1-686 #1 SMP Thu May 8 02:16:39 UTC 2008 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10400090
Selinux: No
Accessibility: Disabled
GTK+ Theme: Wasp
Icon Theme: Wasp

Memory status: size: 82001920 vsize: 82001920 resident: 28016640 share: 16019456 rss: 28016640 rss_rlim: 4294967295
CPU usage: start_time: 1214066749 rtime: 1088 utime: 1006 stime: 82 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 0xb6b6a720 (LWP 3028)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 201031

Thread 1 (Thread 0xb6b6a720 (LWP 3028))

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



----------- .xsession-errors (3944 sec old) ---------------------
	->lsb/usr/hpijs/HP/HP_Color_LaserJet_3000-ps.ppd (HP Color LaserJet 3000 Postscript (recommended))[1]

** (gnome-cups-add:9788): WARNING **: Two ppds have driver == 'Standard'
	->lsb/usr/postscript/HP/hp_color_LaserJet_3700.ppd.gz (HP Color LaserJet 3700 Postscript (recommended)[1]) and
	->lsb/usr/hpijs/HP/hp_color_LaserJet_3700-ps.ppd (HP Color LaserJet 3700 Postscript (recommended))[1]

** (gnome-cups-add:9788): WARNING **: Two ppds have driver == 'Standard'
	->lsb/usr/postscript/HP/HP_Color_LaserJet_3800.ppd.gz (HP Color LaserJet 3800 Postscript (recommended)[1]) and
	->lsb/usr/hpijs/HP/HP_Color_LaserJet_3800-ps.ppd (HP Color LaserJet 3800 Postscript (recommended))[1]

** (gnome-cups-add:9788): WARNING **: Two ppds have driver == 'Standard'
	->lsb/usr/postscript/HP/HP_Color_LaserJet_4500.ppd.gz (HP Color LaserJet 4500 v2014.200 Postscript (recommended)[1]) and
	->lsb/usr/hpijs/HP/HP_Color_LaserJet_4500-ps.ppd (HP Color LaserJet 4500 v2014.200 Postscript (recommended))[1]
...Too much output, ignoring rest...
--------------------------------------------------

Comment 1 A. Walton 2008-06-21 21:37:38 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 ***