Bug 537617 – 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 537617 - crash in Computer:


Summary:	crash in Computer:


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-06-10 15:35 UTC by leangeder
Modified:	2008-06-10 19:08 UTC

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

Description leangeder 2008-06-10 15:35:56 UTC

Version: 2.20.0

What were you doing when the application crashed?



Distribution: Debian lenny/sid
Gnome Release: 2.22.2 2008-05-29 (Debian)
BugBuddy Version: 2.22.0

System: Linux 2.6.24-1-686 #1 SMP Thu May 8 02:16:39 UTC 2008 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10400090
Selinux: No
Accessibility: Disabled
GTK+ Theme: Deepgreen
Icon Theme: Mac_OS_X_Leopard_for_Debian_v1.4

Memory status: size: 83054592 vsize: 83054592 resident: 24399872 share: 15798272 rss: 24399872 rss_rlim: 4294967295
CPU usage: start_time: 1213112098 rtime: 267 utime: 241 stime: 26 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

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

Using host libthread_db library "/lib/i686/cmov/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread 0xb6c20720 (LWP 6069)]
0xffffe410 in __kernel_vsyscall ()

+ Trace 200041

Thread 1 (Thread 0xb6c20720 (LWP 6069))

#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 istr_hash
at nautilus-directory-async.c line 170
#7 ??
from /usr/lib/libglib-2.0.so.0
#8 ??
#0 __kernel_vsyscall



----------- .xsession-errors ---------------------
CALLBACK: fill-authentication!!!
connection_message_func(): Callback
CALLBACK: full-authentication!!!
connection_message_func(): Callback
CALLBACK: full-authentication!!!
connection_message_func(): Callback
CALLBACK: full-authentication!!!
(bug-buddy:6053): Gtk-WARNING **: Impossible de trouver le moteur de thème dans module_path : « ubuntulooks »
Initializing gnome-mount extension
seahorse nautilus module initialized
(nautilus:6069): Gtk-WARNING **: Impossible de trouver le moteur de thème dans module_path : « ubuntulooks »
(bug-buddy:6125): Gtk-WARNING **: Impossible de trouver le moteur de thème dans module_path : « ubuntulooks »
--------------------------------------------------

Comment 1 Cosimo Cecchi 2008-06-10 19:08:51 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 ***