Bug 509573 – crash in Computer: I was searching a file c...

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 509573 - crash in Computer: I was searching a file c...


Summary:	crash in Computer: I was searching a file c...


Status:	RESOLVED DUPLICATE of bug 454799

Product:	nautilus
Classification:	Core
Component:	general
Version:	2.18.x
Hardware:	Other All

Importance:	High critical
Target Milestone:	---
Assigned To:	Nautilus Maintainers
QA Contact:	Nautilus Maintainers

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2008-01-15 08:56 UTC by colasmaillard
Modified:	2008-01-15 22:09 UTC

See Also:
GNOME target:	---
GNOME version:	2.17/2.18

Description colasmaillard 2008-01-15 08:56:14 UTC

Version: 2.18.3

What were you doing when the application crashed?
I was searching a file called "lotus" in my home file


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: Permissive
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 99897344 vsize: 99897344 resident: 42921984 share: 21987328 rss: 42921984 rss_rlim: 4294967295
CPU usage: start_time: 1200386989 rtime: 465 utime: 397 stime: 68 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 -1209043232 (LWP 2734)]
[New Thread -1232639088 (LWP 2865)]
(no debugging symbols found)
0x00110402 in __kernel_vsyscall ()

+ Trace 185402

Thread 2 (Thread -1232639088 (LWP 2865))

#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 (10 sec old) ---------------------
localuser:colas being added to access control list
SESSION_MANAGER=local/unix:/tmp/.ICE-unix/2607
Impossible d'ouvrir le fichier de bureau /home/colas/Bureau/fedora-realplay.desktop pour le lanceur du tableau de bord: Aucun fichier ou répertoire de ce type
Impossible d'ouvrir le fichier de bureau /home/colas/Bureau/kaffeine.desktop pour le lanceur du tableau de bord: Aucun fichier ou répertoire de ce type
Impossible d'ouvrir le fichier de bureau /home/colas/Bureau/kile.desktop pour le lanceur du tableau de bord: Aucun fichier ou répertoire de ce type
Impossible d'ouvrir le fichier de bureau /home/colas/Bureau/k3b.desktop pour le lanceur du tableau de bord: Aucun fichier ou répertoire de ce type
Impossible d'ouvrir le fichier de bureau /home/colas/Bureau/Xmoto.desktop pour le lanceur du tableau de bord: Aucun fichier ou répertoire de ce type
Avertissement du gestionnaire de fenêtres : Fenêtre WM_TRANSIENT_FOR 0x4d non valide indiquée pour 0x1400186 ().
(nautilus:2734): GLib-CRITICAL **: g_utf8_strdown: assertion `str != NULL' failed
Xlib: unexpected async reply (sequence 0x1acd)!
--------------------------------------------------

Comment 1 Bruno Boaventura 2008-01-15 22:09:42 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 ***