Bug 531024 – crash in Computer:

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 531024 - crash in Computer:


Summary:	crash in Computer:


Status:	RESOLVED DUPLICATE of bug 355018

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-02 08:41 UTC by gerard.amailland
Modified:	2008-05-02 23:22 UTC

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

Description gerard.amailland 2008-05-02 08:41:58 UTC

Version: 2.20.0

What were you doing when the application crashed?



Distribution: Debian lenny/sid
Gnome Release: 2.22.1 2008-04-08 (Debian)
BugBuddy Version: 2.22.0

System: Linux 2.6.25-0.slh.12-sidux-686 #1 SMP PREEMPT Tue Apr 29 20:45:42 UTC 2008 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10400090
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: gnome

Memory status: size: 89042944 vsize: 89042944 resident: 11460608 share: 9490432 rss: 11460608 rss_rlim: 4294967295
CPU usage: start_time: 1209717702 rtime: 6 utime: 5 stime: 1 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 0xb6cee720 (LWP 13659)]
(no debugging symbols found)
0xb80a7424 in __kernel_vsyscall ()

+ Trace 196661

Thread 1 (Thread 0xb6cee720 (LWP 13659))

#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 strcmp
from /lib/i686/cmov/libc.so.6
#7 ??
#8 ??
#0 __kernel_vsyscall



----------- .xsession-errors ---------------------
Impossible d'ouvrir le fichier de bureau /home/gamailland/Desktop/kcalc.desktop pour le lanceur du tableau de bord: Aucun fichier ou répertoire de ce type
Impossible d'ouvrir le fichier de bureau /home/gamailland/Desktop/kget.desktop pour le lanceur du tableau de bord: Aucun fichier ou répertoire de ce type
Initializing gnome-mount extension
seahorse nautilus module initialized
Impossible d'ouvrir le fichier de bureau /home/gamailland/Desktop/nvidia-settings.desktop pour le lanceur du tableau de bord: Aucun fichier ou répertoire de ce type
Impossible d'ouvrir le fichier de bureau /home/gamailland/Desktop/kcalc.desktop pour le lanceur du tableau de bord: Aucun fichier ou répertoire de ce type
Impossible d'ouvrir le fichier de bureau /home/gamailland/Desktop/kget.desktop pour le lanceur du tableau de bord: Aucun fichier ou répertoire de ce type
Initializing gnome-mount extension
seahorse nautilus module initialized
Initializing gnome-mount extension
seahorse nautilus module initialized
Initializing gnome-mount extension
seahorse nautilus module initialized
Initializing gnome-mount extension
seahorse nautilus module initialized
--------------------------------------------------

Comment 1 Cosimo Cecchi 2008-05-02 23:22:49 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 355018 ***