Bug 530696 – crash in File Browser: I was trying to open a d...

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 530696 - crash in File Browser: I was trying to open a d...


Summary:	crash in File Browser: I was trying to open a d...


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-30 08:41 UTC by anexwarrior
Modified:	2008-04-30 08:55 UTC

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

Description anexwarrior 2008-04-30 08:41:06 UTC

Version: 2.20.0

What were you doing when the application crashed?
I was trying to open a directory in a windows PC in my LAN network.


Distribution: Debian lenny/sid
Gnome Release: 2.22.1 2008-04-08 (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: 472027136 vsize: 472027136 resident: 46526464 share: 19701760 rss: 46526464 rss_rlim: 18446744073709551615
CPU usage: start_time: 1209044458 rtime: 2877 utime: 2415 stime: 462 cutime:23 cstime: 7 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 0x2b9273c6cb80 (LWP 12179)]
(no debugging symbols found)
0x00002b926d791edf in waitpid () from /lib/libpthread.so.0

+ Trace 196510

Thread 1 (Thread 0x2b9273c6cb80 (LWP 12179))

#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 (148607 sec old) ---------------------
Find Items 0
get s.martinez pop://s.martinez@correo.ziv.es/
Find Items 0
get s.martinez pop://s.martinez@correo.ziv.es/
Find Items 0
get s.martinez pop://s.martinez@correo.ziv.es/
Find Items 0
get s.martinez pop://s.martinez@correo.ziv.es/
Find Items 0
get s.martinez pop://s.martinez@correo.ziv.es/
Find Items 0
get s.martinez pop://s.martinez@correo.ziv.es/
Find Items 0
...Too much output, ignoring rest...
--------------------------------------------------

Comment 1 Cosimo Cecchi 2008-04-30 08:55:26 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 522534 ***