Bug 529621 – crash in Open Folder: Clicked 'Open with other...

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 529621 - crash in Open Folder: Clicked 'Open with other...


Summary:	crash in Open Folder: Clicked 'Open with other...


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-23 22:28 UTC by yardcat
Modified:	2008-04-23 23:07 UTC

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

Description yardcat 2008-04-23 22:28:56 UTC

Version: 2.20.0

What were you doing when the application crashed?
Clicked 'Open with other application' ......boom!!  when trying to open a VIDEO_TS folder


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

System: Linux 2.6.24-1-486 #1 Thu Mar 27 17:00:17 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: 66473984 vsize: 66473984 resident: 21389312 share: 15237120 rss: 21389312 rss_rlim: 4294967295
CPU usage: start_time: 1208985819 rtime: 542 utime: 476 stime: 66 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 0xb6c35720 (LWP 6760)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 195969

Thread 1 (Thread 0xb6c35720 (LWP 6760))

#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 ---------------------
** Message: Reconnected OK.
** Message: GetValue variable 1 (1)
** Message: GetValue variable 2 (2)
** Message: GetValue variable 1 (1)
** Message: GetValue variable 2 (2)
** Message: GetValue variable 1 (1)
** Message: GetValue variable 2 (2)
** Message: GetValue variable 1 (1)
** Message: GetValue variable 2 (2)
** Message: GetValue variable 1 (1)
** Message: GetValue variable 2 (2)
Window manager warning: last_user_time (3075724336) is greater than comparison timestamp (2103258505).  This most likely represents a buggy client sending inaccurate timestamps in messages such as _NE
Window manager warning: 0x2600081 (Synaptic) appears to be one of the offending windows with a timestamp of 3075724336.  Working around...
(nautilus:6760): Eel-WARNING **: No extension, not implemented yet
--------------------------------------------------

Comment 1 Gianluca Borello 2008-04-23 23:07:56 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 ***