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 513221 - crash in Open Folder: searching files
crash in Open Folder: searching files
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-01-30 18:35 UTC by cyberey
Modified: 2008-01-30 18:38 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description cyberey 2008-01-30 18:35:33 UTC
Version: 2.18.3

What were you doing when the application crashed?
searching files 


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.12-52.fc7 #1 SMP Tue Dec 18 21:18:02 EST 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 88756224 vsize: 88756224 resident: 36577280 share: 20279296 rss: 36577280 rss_rlim: 4294967295
CPU usage: start_time: 1201318490 rtime: 6169 utime: 5294 stime: 875 cutime:0 cstime: 11 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 -1209157920 (LWP 12610)]
[New Thread -1242727536 (LWP 15096)]
(no debugging symbols found)
0x00110402 in __kernel_vsyscall ()

Thread 2 (Thread -1242727536 (LWP 15096))

  • #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 (57 sec old) ---------------------
Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.
Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x2c012c2 (TalkApr01 )
Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.
Window manager warning: Received a _NET_WM_MOVERESIZE message for 0x2200024 (Document p); these messages lack timestamps and therefore suck.
xscreensaver-command: activating and locking.
** Message: Could not connect to power manager: Could not get owner of name 'org.gnome.PowerManager': no such name
** Message: Could not connect to power manager: Could not get owner of name 'org.gnome.PowerManager': no such name
--- Hash table keys for warning below:
--> file:///home/cyberey
(nautilus:15086): Eel-WARNING **: "nautilus-directory.c: directories" hash table still has 1 element at quit time (keys above)
(nautilus:12610): GLib-CRITICAL **: g_utf8_strdown: assertion `str != NULL' failed
--------------------------------------------------
Comment 1 Christian Kirbach 2008-01-30 18:38: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 ***