Bug 500269 – crash in Open Folder:

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 500269 - crash in Open Folder:


Summary:	crash in Open Folder:


Status:	RESOLVED DUPLICATE of bug 454799

Product:	nautilus
Classification:	Core
Component:	general
Version:	2.18.x
Hardware:	Other All

Importance:	High critical
Target Milestone:	---
Assigned To:	Nautilus Maintainers
QA Contact:	Nautilus Maintainers

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2007-11-28 18:16 UTC by cupp
Modified:	2007-11-28 22:10 UTC

See Also:
GNOME target:	---
GNOME version:	2.17/2.18

Description cupp 2007-11-28 18:16:52 UTC

Version: 2.18.3

What were you doing when the application crashed?



Distribution: Fedora release 7 (Moonshine)
Gnome Release: 2.18.3 2007-11-13 (Red Hat, Inc)
BugBuddy Version: 2.18.0

System: Linux 2.6.23.1-21.fc7 #1 SMP Thu Nov 1 21:09:24 EDT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Bluecurve
Icon Theme: Bluecurve

Memory status: size: 157265920 vsize: 157265920 resident: 55861248 share: 38293504 rss: 55861248 rss_rlim: 4294967295
CPU usage: start_time: 1196252800 rtime: 1665 utime: 1275 stime: 390 cutime:0 cstime: 1 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 -1208334624 (LWP 3858)]
[New Thread -1244669040 (LWP 10108)]
(no debugging symbols found)
0x00110402 in __kernel_vsyscall ()

+ Trace 180001

Thread 2 (Thread -1244669040 (LWP 10108))

#0 __kernel_vsyscall
#1 ??
from /lib/libpthread.so.0
#2 ??
from /usr/lib/libgnomeui-2.so.0
#3 <signal handler called>
#4 strstr
from /lib/libc.so.6
#5 ??
#6 ??
from /usr/lib/libgnomevfs-2.so.0
#7 ??
#8 ??
#9 ??



----------- .xsession-errors ---------------------
report junk?? Monthly tips, resources and more from Adobe
fixme:winsock:WS_setsockopt Unknown IPPROTO_IP optname 0x00000013
fixme:winsock:WS_setsockopt Unknown IPPROTO_IP optname 0x00000013
fixme:winsock:WS_setsockopt Unknown IPPROTO_IP optname 0x00000013
fixme:winsock:WS_setsockopt Unknown IPPROTO_IP optname 0x00000013
fixme:winsock:WS_setsockopt Unknown IPPROTO_IP optname 0x00000013
fixme:winsock:WS_setsockopt Unknown IPPROTO_IP optname 0x00000013
fixme:winsock:WS_setsockopt Unknown IPPROTO_IP optname 0x00000013
fixme:winsock:WS_setsockopt Unknown IPPROTO_IP optname 0x00000013
(nautilus:3858): GLib-CRITICAL **: g_utf8_strdown: assertion `str != NULL' failed
Xlib: unexpected async reply (sequence 0x549f6)!
fixme:winsock:WS_setsockopt Unknown IPPROTO_IP optname 0x00000013
xscreensaver: 13:16:44: 0: unrecognised ClientMessage "_NET_WM_STATE" received
xscreensaver: 13:16:44: 0: for window 0x4e49ce9 (VCLSalFrame / OpenOffice.org 2.3)
--------------------------------------------------

Comment 1 Susana 2007-11-28 22:10:55 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 454799 ***