Bug 528159 – crash in Open Folder: access a shared folder o...

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 528159 - crash in Open Folder: access a shared folder o...


Summary:	crash in Open Folder: access a shared folder o...


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-15 06:47 UTC by bas_vanderpeet
Modified:	2008-04-15 07:22 UTC

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

Description bas_vanderpeet 2008-04-15 06:47:33 UTC

Version: 2.20.0

What were you doing when the application crashed?
access a shared folder on a windows computer.


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

System: Linux 2.6.24-1-amd64 #1 SMP Thu Mar 27 16:52:38 UTC 2008 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: gnome

Memory status: size: 424964096 vsize: 424964096 resident: 35647488 share: 17657856 rss: 35647488 rss_rlim: 18446744073709551615
CPU usage: start_time: 1208241175 rtime: 199 utime: 180 stime: 19 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/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 0x2b0eed5bdb80 (LWP 3916)]
(no debugging symbols found)
0x00002b0ee70e2edf in waitpid () from /lib/libpthread.so.0

+ Trace 195263

Thread 1 (Thread 0x2b0eed5bdb80 (LWP 3916))

#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 ??
from /usr/lib/libglib-2.0.so.0
#7 ??
#8 ??
#9 ??
from /usr/lib/libgnomevfs-2.so.0
#10 g_main_context_dispatch
from /usr/lib/libglib-2.0.so.0
#11 ??
from /usr/lib/libglib-2.0.so.0
#12 g_main_loop_run
from /usr/lib/libglib-2.0.so.0
#13 gtk_main
from /usr/lib/libgtk-x11-2.0.so.0
#14 ??
#15 __libc_start_main
from /lib/libc.so.6
#16 ??
#17 ??
#18 ??
#0 waitpid
from /lib/libpthread.so.0



----------- .xsession-errors (8 sec old) ---------------------
Debug: Done reading conf from /home/bas/.beagle/config/BeagleSearch.xml
Debug: Done reading conf from /etc/beagle/config-files/BeagleSearch.xml
Debug: Done reading conf from /home/bas/.beagle/config/Daemon.xml
Debug: Done reading conf from /etc/beagle/config-files/Daemon.xml
Got accel 65481, 0, 0
Got keycode 96
Got modmask 0
Got Event! 33, -1
Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x1c0005a (Buddy List)
Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.
Got Event! 33, -1
connection_message_func(): Callback
CALLBACK: fill-authentication!!!
connection_message_func(): Callback
CALLBACK: fill-authentication!!!
--------------------------------------------------

Comment 1 Gianluca Borello 2008-04-15 07:22:49 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 ***