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 497010 - crash in Open Folder: logged in as root, tried...
crash in Open Folder: logged in as root, tried...
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-11-15 10:28 UTC by cmtunc
Modified: 2007-11-15 15:02 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description cmtunc 2007-11-15 10:28:28 UTC
Version: 2.18.3

What were you doing when the application crashed?
logged in as root, tried to perform a search of /root via nautilus. As soon as I pressed enter I was welcome by Bug Buddy : )


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.9-91.fc7 #1 SMP Thu Sep 27 20:47:39 EDT 2007 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 481349632 vsize: 481349632 resident: 42745856 share: 21811200 rss: 42745856 rss_rlim: 18446744073709551615
CPU usage: start_time: 1195122332 rtime: 183 utime: 160 stime: 23 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 "/lib64/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 46912496393264 (LWP 29591)]
[New Thread 1094719824 (LWP 29601)]
(no debugging symbols found)
0x00000033450c82e6 in poll () from /lib64/libc.so.6

Thread 2 (Thread 1094719824 (LWP 29601))

  • #0 waitpid
    from /lib64/libpthread.so.0
  • #1 g_cclosure_marshal_VOID__ENUM
    from /usr/lib64/libgnomeui-2.so.0
  • #2 <signal handler called>
  • #3 strstr
    from /lib64/libc.so.6
  • #4 ??
  • #5 g_cclosure_marshal_VOID__ENUM
    from /usr/lib64/libgnomevfs-2.so.0
  • #6 g_cclosure_marshal_VOID__ENUM
    from /usr/lib64/libgnomevfs-2.so.0
  • #7 g_cclosure_marshal_VOID__ENUM
    from /usr/lib64/libgnomevfs-2.so.0
  • #8 g_cclosure_marshal_VOID__ENUM
    from /usr/lib64/libgnomevfs-2.so.0
  • #9 g_cclosure_marshal_VOID__ENUM
    from /usr/lib64/libgnomevfs-2.so.0
  • #10 g_cclosure_marshal_VOID__ENUM
    from /usr/lib64/libgnomevfs-2.so.0
  • #11 gnome_vfs_directory_visit_uri
    from /usr/lib64/libgnomevfs-2.so.0
  • #12 ??
  • #13 g_cclosure_marshal_VOID__ENUM
    from /lib64/libglib-2.0.so.0
  • #14 start_thread
    from /lib64/libpthread.so.0
  • #15 clone
    from /lib64/libc.so.6


----------- .xsession-errors ---------------------
(termit:27717): Vte-WARNING **: No handler for control sequence `device-control-string' defined.
ALSA lib confmisc.c:769:(parse_card) cannot find card ''
ALSA lib conf.c:3510:(_snd_config_evaluate) function snd_func_card_driver returned error: No such device
ALSA lib confmisc.c:392:(snd_func_concat) error evaluating strings
ALSA lib conf.c:3510:(_snd_config_evaluate) function snd_func_concat returned error: No such device
ALSA lib confmisc.c:1251:(snd_func_refer) error evaluating name
ALSA lib conf.c:3510:(_snd_config_evaluate) function snd_func_refer returned error: No such device
ALSA lib conf.c:3982:(snd_config_expand) Evaluate error: No such device
ALSA lib pcm.c:2144:(snd_pcm_open_noupdate) Unknown PCM default
JACK tmpdir identified as [/dev/shm]
[00000428] jack audio output error: failed to connect to JACK server
(nautilus:27579): GLib-CRITICAL **: g_utf8_strdown: assertion `str != NULL' failed
(nautilus:29591): GLib-CRITICAL **: g_utf8_strdown: assertion `str != NULL' failed
--------------------------------------------------
Comment 1 palfrey 2007-11-15 15:02:03 UTC
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find

*** This bug has been marked as a duplicate of 454799 ***