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 467655 - crash in Open Folder: An USB hdd is attached a...
crash in Open Folder: An USB hdd is attached a...
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-08-17 13:35 UTC by robert.dady
Modified: 2007-08-21 20:23 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description robert.dady 2007-08-17 13:35:14 UTC
Version: 2.18.3

What were you doing when the application crashed?
An USB hdd is attached at /media/disk and I called Ctrl+F in Nautilus 2.18.3 for this directory. After typing the word to be find in files I pressed ENTER and Bug Buddy started.


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

System: Linux 2.6.22.1-41.fc7 #1 SMP Fri Jul 27 18:10:34 EDT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: Enforcing
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 88375296 vsize: 88375296 resident: 32993280 share: 19611648 rss: 32993280 rss_rlim: 4294967295
CPU usage: start_time: 1187357512 rtime: 164 utime: 149 stime: 15 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/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1208437024 (LWP 7807)]
[New Thread -1252496496 (LWP 7826)]
(no debugging symbols found)
0x00110402 in __kernel_vsyscall ()

Thread 2 (Thread -1252496496 (LWP 7826))

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


----------- .xsession-errors ---------------------
Unable to connect to yum-updatesd.  Please ensure that the yum-updatesd 
package is installed and that the service is running.
Unable to connect to yum-updatesd.  Please ensure that the yum-updatesd 
package is installed and that the service is running.
Unable to connect to yum-updatesd.  Please ensure that the yum-updatesd 
package is installed and that the service is running.
Unable to connect to yum-updatesd.  Please ensure that the yum-updatesd 
package is installed and that the service is running.
Max failures exceeded, exiting now
(nautilus:3221): GLib-CRITICAL **: g_filename_display_basename: assertion `filename != NULL' failed
(nautilus:3221): GLib-CRITICAL **: g_filename_display_basename: assertion `filename != NULL' failed
(nautilus:7807): GLib-CRITICAL **: g_utf8_strdown: assertion `str != NULL' failed
--------------------------------------------------
Comment 1 Susana 2007-08-21 20:23:11 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 ***