Bug 533710 – crash in Computer: Tentative d'ouverture 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 533710 - crash in Computer: Tentative d'ouverture d'...


Summary:	crash in Computer: Tentative d'ouverture d'...


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-18 14:48 UTC by ju.pryz
Modified:	2008-05-18 15:02 UTC

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

Description ju.pryz 2008-05-18 14:48:55 UTC

Version: 2.20.0

What were you doing when the application crashed?
Tentative d'ouverture d'un fichier régulier, choix de l'applications pour l'ouverture.


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

System: Linux 2.6.22-3-686 #1 SMP Sun Feb 10 20:20:49 UTC 2008 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10400090
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: SphereCrystal

Memory status: size: 86175744 vsize: 86175744 resident: 30924800 share: 16179200 rss: 30924800 rss_rlim: 4294967295
CPU usage: start_time: 1211122078 rtime: 221 utime: 208 stime: 13 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 0xb6b6e720 (LWP 4424)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 198024

Thread 1 (Thread 0xb6b6e720 (LWP 4424))

#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 g_str_equal
from /usr/lib/libglib-2.0.so.0
#8 ??
from /usr/lib/libeel-2-2.20.so
#9 ??
#10 ??
#0 __kernel_vsyscall



----------- .xsession-errors ---------------------
/etc/gdm/Xsession: Beginning session setup...
SESSION_MANAGER=local/ju-pc:/tmp/.ICE-unix/2905
** (gnome-settings-daemon:2963): WARNING **: L'ouverture du fichier « /etc/gnome/config/General.ad » a échoué : Aucun fichier ou répertoire de ce type
Avertissement du gestionnaire de fenêtres : La lecture du fichier de session enregistré /home/ju/.metacity/sessions/default0.ms a échoué : L'ouverture du fichier « /home/ju/.metacity/sessions/
seahorse nautilus module initialized
Initializing gnome-mount extension
(nautilus:2987): Eel-WARNING **: No extension, not implemented yet
seahorse nautilus module initialized
Initializing gnome-mount extension
(nautilus:4424): Eel-WARNING **: No extension, not implemented yet
--------------------------------------------------

Comment 1 A. Walton 2008-05-18 15:02:02 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 355018 ***