Bug 531848 – crash in Computer: J'allais, via nautilus, ...

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 531848 - crash in Computer: J'allais, via nautilus, ...


Summary:	crash in Computer: J'allais, via nautilus, ...


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-05-06 22:35 UTC by eazeaze
Modified:	2008-05-06 22:43 UTC

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

Description eazeaze 2008-05-06 22:35:02 UTC

Version: 2.20.0

What were you doing when the application crashed?
J'allais, via nautilus, dans un dossier réseau situé sur une machine windows XP dont les autres dossiers partagés sont pourtant parfaitement acessibles et paramétrés de la même manière.


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 Sat Apr 19 04:31:04 UTC 2008 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 10400090
Selinux: No
Accessibility: Disabled
GTK+ Theme: ClearlooksClassic
Icon Theme: nuoveXT.2.2

Memory status: size: 444751872 vsize: 444751872 resident: 40816640 share: 18284544 rss: 40816640 rss_rlim: 18446744073709551615
CPU usage: start_time: 1210112503 rtime: 686 utime: 566 stime: 120 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

Backtrace was generated from '/usr/bin/nautilus'

(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 0x2b4cd66ae240 (LWP 3399)]
(no debugging symbols found)
0x00002b4ccfea4edf in waitpid () from /lib/libpthread.so.0

+ Trace 197084

Thread 1 (Thread 0x2b4cd66ae240 (LWP 3399))

#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 (32483 sec old) ---------------------
** (nm-applet:3687): WARNING **: <WARN>  nma_dbus_init(): org.freedesktop.DBus.Error.FileNotFound raised:
 Failed to connect to socket /var/run/dbus/system_bus_socket: Aucun fichier ou répertoire de ce type
** (nm-applet:3687): WARNING **: <WARN>  nma_dbus_init(): org.freedesktop.DBus.Error.FileNotFound raised:
 Failed to connect to socket /var/run/dbus/system_bus_socket: Aucun fichier ou répertoire de ce type
...Too much output, ignoring rest...
--------------------------------------------------

Comment 1 A. Walton 2008-05-06 22:43:15 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 ***