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 502897 - crash in Open Folder:
crash in Open Folder:
Status: RESOLVED DUPLICATE of bug 454799
Product: nautilus
Classification: Core
Component: general
2.18.x
Other All
: High critical
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2007-12-10 18:31 UTC by cupp
Modified: 2007-12-12 11:59 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description cupp 2007-12-10 18:31:24 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.8-34.fc7 #1 SMP Thu Nov 22 23:05:33 EST 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: 140783616 vsize: 140783616 resident: 50176000 share: 38174720 rss: 50176000 rss_rlim: 4294967295
CPU usage: start_time: 1197301652 rtime: 777 utime: 562 stime: 215 cutime:6 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 -1208834336 (LWP 3708)]
[New Thread -1329607792 (LWP 7327)]
(no debugging symbols found)
0x00110402 in __kernel_vsyscall ()

Thread 2 (Thread -1329607792 (LWP 7327))

  • #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 ---------------------
fixme:winsock:WS_setsockopt Unknown IPPROTO_IP optname 0x00000013
fixme:winsock:WS_setsockopt Unknown IPPROTO_IP optname 0x00000013
xscreensaver: 13:28:18: -1: unrecognised ClientMessage "_NET_WM_STATE" received
xscreensaver: 13:28:18: -1: for window 0x30338b0 ((null) / (null))
xscreensaver: 13:29:17: 0: unrecognised ClientMessage "_NET_ACTIVE_WINDOW" received
xscreensaver: 13:29:17: 0: for window 0x300a775 (evolution / Evolution)
xscreensaver: 13:29:23: 0: unrecognised ClientMessage "_NET_ACTIVE_WINDOW" received
xscreensaver: 13:29:23: 0: for window 0x2e00002 (opera / Opera)
fixme:winsock:WS_setsockopt Unknown IPPROTO_IP optname 0x00000013
fixme:winsock:WS_setsockopt Unknown IPPROTO_IP optname 0x00000013
xscreensaver: 13:30:45: 0: unrecognised ClientMessage "_NET_WM_STATE" received
xscreensaver: 13:30:45: 0: for window 0x5208f03 (VCLSalFrame / OpenOffice.org 2.3)
(nautilus:3708): GLib-CRITICAL **: g_utf8_strdown: assertion `str != NULL' failed
Xlib: unexpected async reply (sequence 0xf2c0)!
--------------------------------------------------
Comment 1 Cosimo Cecchi 2007-12-12 11:59:40 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 ***