Bug 525735 – crash in Open Folder: trying to open an unknow...

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 525735 - crash in Open Folder: trying to open an unknow...


Summary:	crash in Open Folder: trying to open an unknow...


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-04-02 10:45 UTC by Isaque Galdino
Modified:	2008-04-03 01:02 UTC

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

Description Isaque Galdino 2008-04-02 10:45:24 UTC

Version: 2.20.0

What were you doing when the application crashed?
trying to open an unknowing file


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

System: Linux 2.6.22-3-amd64 #1 SMP Tue Feb 12 09:22:35 UTC 2008 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: gnome

Memory status: size: 345989120 vsize: 345989120 resident: 35753984 share: 17760256 rss: 35753984 rss_rlim: 18446744073709551615
CPU usage: start_time: 1207130877 rtime: 1102 utime: 960 stime: 142 cutime:13 cstime: 15 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 0x2b30d07ba180 (LWP 4415)]
[New Thread 0x40800950 (LWP 6630)]
(no debugging symbols found)
0x00002b30ca2c734f in waitpid () from /lib/libpthread.so.0

+ Trace 193993

Thread 1 (Thread 0x2b30d07ba180 (LWP 4415))

#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 ??
#0 waitpid
from /lib/libpthread.so.0



----------- .xsession-errors ---------------------
[Bridge] End of stream
MP4Audio : index max :121/121
EditorPacket:Read failed; retrying (were at seg 0sample 481024
/ 482666)
EditorPacket : End of *last* stream
 read failed, end of stream ? 
[Bridge] End of stream
MP4Audio : index max :121/121
EditorPacket:Read failed; retrying (were at seg 0sample 481024
/ 482666)
EditorPacket : End of *last* stream
 read
(nautilus:4415): Eel-WARNING **: No extension, not implemented yet
(nautilus:4415): Eel-WARNING **: No extension, not implemented yet
--------------------------------------------------

Comment 1 Cosimo Cecchi 2008-04-03 01:02:31 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 ***