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 514231 - crash in Open Folder: search with a new locati...
crash in Open Folder: search with a new locati...
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: 2008-02-04 06:46 UTC by trendleforum
Modified: 2008-02-04 13:18 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description trendleforum 2008-02-04 06:46:54 UTC
Version: 2.18.3

What were you doing when the application crashed?
search with a new location set


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.14-60.fc7 #1 SMP Mon Jan 14 22:14:17 EST 2008 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks-Darjeeling
Icon Theme: Clearlooks

Memory status: size: 222126080 vsize: 222126080 resident: 96612352 share: 71856128 rss: 96612352 rss_rlim: 4294967295
CPU usage: start_time: 1202077098 rtime: 10369 utime: 9747 stime: 622 cutime:209 cstime: 54 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 -1208342816 (LWP 2704)]
[New Thread -1341084784 (LWP 10020)]
(no debugging symbols found)
0x00110402 in __kernel_vsyscall ()

Thread 2 (Thread -1341084784 (LWP 10020))

  • #0 __kernel_vsyscall
  • #1 waitpid
    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 (22 sec old) ---------------------
fixme:ntdll:find_reg_tz_info Can't find matching timezone information in the registry for bias 480, std (d/m/y): 2/11/2008, dlt (d/m/y): 9/03/2008
Window manager warning: Invalid WM_TRANSIENT_FOR window 0x480000b specified for 0x480000c (WM Recorde).
Window manager warning: Invalid WM_TRANSIENT_FOR window 0x480000b specified for 0x480000e (WM Recorde).
Window manager warning: Invalid WM_TRANSIENT_FOR window 0x480000b specified for 0x480000f ().
fixme:ntdll:find_reg_tz_info Can't find matching timezone information in the registry for bias 480, std (d/m/y): 2/11/2008, dlt (d/m/y): 9/03/2008
fixme:ntdll:find_reg_tz_info Can't find matching timezone information in the registry for bias 480, std (d/m/y): 2/11/2008, dlt (d/m/y): 9/03/2008
fixme:actctx:parse_depend_manifests Could not find dependent assembly L"Microsoft.Windows.Common-Controls"
err:ole:CoGetClassObject class {cfc399af-d876-11d0-9c10-00c04fc99c8e} not registered
err:ole:CoGetClassObject no class object {cfc399af-d876-11d0-9c10-00c04fc99c8e} could be created for context 0x1
err:ole:CoGetClassObject class {cfc399af-d876-11d0-9c10-00c04fc99c8e} not registered
err:ole:CoGetClassObject no class object {cfc399af-d876-11d0-9c10-00c04fc99c8e} could be created for context 0x1
fixme:ntdll:find_reg_tz_info Can't find matching timezone information in the registry for bias 480, std (d/m/y): 2/11/2008, dlt (d/m/y): 9/03/2008
(nautilus:2704): GLib-CRITICAL **: g_utf8_strdown: assertion `str != NULL' failed
Xlib: unexpected async reply (sequence 0x137395)!
--------------------------------------------------
Comment 1 Cosimo Cecchi 2008-02-04 13:18:57 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 ***