Bug 525291 – crash in Computer: open file

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 525291 - crash in Computer: open file


Summary:	crash in Computer: open file


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-03-31 10:27 UTC by lso333
Modified:	2008-03-31 17:53 UTC

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

Description lso333 2008-03-31 10:27:40 UTC

Version: 2.20.0

What were you doing when the application crashed?
open file


Distribution: Debian lenny/sid
Gnome Release: 2.22.0 2008-03-14 (Debian)
BugBuddy Version: 2.22.0

System: Linux 2.6.18-6-amd64 #1 SMP Sun Feb 10 17:50:19 UTC 2008 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 10400090
Selinux: No
Accessibility: Disabled
GTK+ Theme: SphereCrystal
Icon Theme: SphereCrystal

Memory status: size: 474624000 vsize: 474624000 resident: 43880448 share: 20791296 rss: 43880448 rss_rlim: 18446744073709551615
CPU usage: start_time: 1206839088 rtime: 1073 utime: 998 stime: 75 cutime:0 cstime: 3 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 0x2ad8e2a39180 (LWP 3696)]
(no debugging symbols found)
0x00002ad8dc5505ef in waitpid () from /lib/libpthread.so.0

+ Trace 193751

Thread 1 (Thread 0x2ad8e2a39180 (LWP 3696))

#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 strcmp
from /lib/libc.so.6
#6 g_str_equal
from /usr/lib/libglib-2.0.so.0
#7 ??
from /usr/lib/libeel-2-2.20.so
#8 g_main_context_dispatch
from /usr/lib/libglib-2.0.so.0
#9 ??
from /usr/lib/libglib-2.0.so.0
#10 g_main_loop_run
from /usr/lib/libglib-2.0.so.0
#11 gtk_main
from /usr/lib/libgtk-x11-2.0.so.0
#12 ??
#13 __libc_start_main
from /lib/libc.so.6
#14 ??
#15 ??
#16 ??
#17 ??
#18 ??
#19 ??
#20 ??
#21 ??
#22 ??
#0 waitpid
from /lib/libpthread.so.0



----------- .xsession-errors ---------------------
** (gnome-power-preferences:3087): WARNING **: Could not connect to DBUS daemon: Failed to connect to socket /var/run/dbus/system_bus_socket: 沒有此一檔案或目錄
** (gnome-power-preferences:3087): WARNING **: Either HAL or DBUS are not working!
** (gnome-power-preferences:3092): WARNING **: Failed to connect to socket /var/run/dbus/system_bus_socket: 沒有此一檔案或目錄
** (gnome-power-preferences:3092): WARNING **: Could not connect to DBUS daemon: Failed to connect to socket /var/run/dbus/system_bus_socket: 沒有此一檔案或目錄
** (gnome-power-preferences:3092): WARNING **: Either HAL or DBUS are not working!
(nautilus:3696): libgnomevfs-CRITICAL **: gnome_vfs_uri_get_parent: assertion `uri != NULL' failed
(nautilus:3696): libgnomevfs-CRITICAL **: gnome_vfs_uri_unref: assertion `uri != NULL' failed
(nautilus:3696): Eel-WARNING **: No extension, not implemented yet
--------------------------------------------------

Comment 1 Cosimo Cecchi 2008-03-31 17:53:00 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 ***