Bug 518783 – crash in Open Folder: open "Open with"

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 518783 - crash in Open Folder: open "Open with"


Summary:	crash in Open Folder: open "Open with"


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-02-26 07:23 UTC by 9hoeger
Modified:	2008-02-26 19:54 UTC

See Also:
GNOME target:	---
GNOME version:	2.19/2.20

Description 9hoeger 2008-02-26 07:23:44 UTC

Version: 2.20.0

What were you doing when the application crashed?
open "Open with"


Distribution: Debian lenny/sid
Gnome Release: 2.20.3 2008-01-12 (Debian)
BugBuddy Version: 2.20.1

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: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: gnome

Memory status: size: 79880192 vsize: 79880192 resident: 22749184 share: 15597568 rss: 22749184 rss_rlim: 4294967295
CPU usage: start_time: 1204009973 rtime: 315 utime: 295 stime: 20 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 0xb6c956c0 (LWP 18508)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 190469

Thread 1 (Thread 0xb6c956c0 (LWP 18508))

#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 ---------------------
alarm-queue.c:2003 (alarm_queue_add_async) - 0x80c5f30
alarm-notify.c:337 (alarm_msgport_replied) - 0x80bb930: Replied to GUI thread
alarm-queue.c:581 (load_alarms_for_today) - From Tue Feb 26 08:13:06 2008
 to Tue Feb 26 08:13:06 2008
alarm-queue.c:518 (load_alarms) 
alarm-queue.c:547 (load_alarms) - Setting Call backs 
alarm-notify.c:349 (alarm_msg_received) - 0x80c9cf0: Received at thread b5c10b90
alarm-queue.c:2003 (alarm_queue_add_async) - 0x80c1e60
alarm-notify.c:337 (aGot Event! 33, -1
(gnome-panel:18507): Gtk-WARNING **: gtk_widget_size_allocate(): attempt to allocate widget with width -5 and height 24
Got Event! 33, -1
(nautilus:18508): Eel-WARNING **: No extension, not implemented yet
--------------------------------------------------

Comment 1 Cosimo Cecchi 2008-02-26 19:54:06 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 ***