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 464510 - crash in Home Folder: The application was sear...
crash in Home Folder: The application was sear...
Status: RESOLVED DUPLICATE of bug 454799
Product: nautilus
Classification: Core
Component: general
unspecified
Other All
: High critical
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2007-08-07 22:55 UTC by m.koerber
Modified: 2007-08-09 22:04 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18


Description m.koerber 2007-08-07 22:55:54 UTC 
What were you doing when the application crashed?
The application was searching for a file. In the background a rcovery process with tar was been executed.


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: 91795456 vsize: 91795456 resident: 37986304 share: 20213760 rss: 37986304 rss_rlim: 4294967295
CPU usage: start_time: 1186502194 rtime: 1396 utime: 1021 stime: 375 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 -1208658208 (LWP 8515)]
[New Thread -1242743920 (LWP 10216)]
(no debugging symbols found)
0x00128402 in __kernel_vsyscall ()

+ Trace 153579

Thread 2 (Thread -1242743920 (LWP 10216))

  • #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 (14 sec old) ---------------------
kbuildsycoca running...
Fenstermanager-Warnung:Ungültiges WM_TRANSIENT_FOR-Fenster 0x65 festgelegt für 0x3000012 (Basisordne).
Fenstermanager-Warnung:Ungültiges WM_TRANSIENT_FOR-Fenster 0x65 festgelegt für 0x3000012 (digiKam).
Found dcraw version: 8.60
Loading "installonlyn" plugin
/usr/share/system-config-selinux/system-config-selinux.py:72: Warning: IA__g_object_get_valist: object class `GnomeProgram' has no property named `default-icon'
  xml = gtk.glade.XML ("/usr/share/system-config-selinux/system-config-selinux.glade", domain=PROGNAME)
/usr/share/system-config-selinux/system-config-selinux.py:72: Warning: IA__g_object_get_valist: object class `GnomeProgram' has no property named `default-icon'
  xml = gtk.glade.XML ("/usr/share/system-config-selinux/system-config-selinux.glade", domain=PROGNAME)
Fenstermanager-Warnung:Ungültiges WM_TRANSIENT_FOR-Fenster 0x65 festgelegt für 0x1000926 ().
Loading "installonlyn" plugin
Loading "installonlyn" plugin
(nautilus:8515): GLib-CRITICAL **: g_utf8_strdown: assertion `str != NULL' failed
Xlib: unexpected async reply (sequence 0x150d1)!
--------------------------------------------------
Comment 1 Susana 2007-08-09 22:04:20 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 ***