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 506886 - crash in Open Folder: searching for a file "*....
crash in Open Folder: searching for a file "*....
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-02 17:28 UTC by ashwin42
Modified: 2008-01-02 20:59 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description ashwin42 2008-01-02 17:28:13 UTC
Version: 2.18.3

What were you doing when the application crashed?
searching for a file "*.iso"


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 #2 SMP Sun Oct 14 22:40:11 EDT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Clearlooks

Memory status: size: 184127488 vsize: 184127488 resident: 42393600 share: 33779712 rss: 42393600 rss_rlim: 4294967295
CPU usage: start_time: 1199294838 rtime: 174 utime: 139 stime: 35 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 -1208158496 (LWP 27072)]
[New Thread -1361998960 (LWP 27101)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

Thread 2 (Thread -1361998960 (LWP 27101))

  • #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 (123034 sec old) ---------------------
ALSA lib pcm_direct.c:1590:(snd_pcm_direct_parse_open_conf) The field ipc_gid must be a valid group (create group audio)
ALSA lib pcm_direct.c:1590:(snd_pcm_direct_parse_open_conf) The field ipc_gid must be a valid group (create group audio)
ALSA lib pcm_direct.c:1590:(snd_pcm_direct_parse_open_conf) The field ipc_gid must be a valid group (create group audio)
ALSA lib pcm_direct.c:1590:(snd_pcm_direct_parse_open_conf) The field ipc_gid must be a valid group (create group audio)
ALSA lib pcm_direct.c:1590:(snd_pcm_direct_parse_open_conf) The field ipc_gid must be a valid group (create group audio)
ALSA lib pcm_direct.c:1590:(snd_pcm_direct_parse_open_conf) The field ipc_gid must be a valid group (create group audio)
ALSA lib pcm_direct.c:1590:(snd_pcm_direct_parse_open_conf) The field ipc_gid must be a valid group (create group audio)
ALSA lib pcm_direct.c:1590:(snd_pcm_direct_parse_open_conf) The field ipc_gid must be a valid group (create group audio)
ALSA lib pcm_direct.c:1590:(snd_pcm_direct_parse_open_conf) The field ipc_gid must be a valid group (create group audio)
ALSA lib pcm_direct.c:1590:(snd_pcm_direct_parse_open_conf) The field ipc_gid must be a valid group (create group audio)
ALSA lib pcm_direct.c:1590:(snd_pcm_direct_parse_open_conf) The field ipc_gid must be a valid group (create group audio)
ALSA lib pcm_direct.c:1590:(snd_pcm_direct_parse_open_conf) The field ipc_gid must be a valid group (create group audio)
ALSA lib pcm_direct.c:1590:(snd_pcm_direct_parse_open_conf) The field ipc_gid must be a valid group (create group audio)
...Too much output, ignoring rest...
--------------------------------------------------
Comment 1 Cosimo Cecchi 2008-01-02 20:59:39 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 ***