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 512906 - crash in Open Folder:
crash in Open Folder:
Status: RESOLVED DUPLICATE of bug 483884
Product: nautilus
Classification: Core
Component: general
2.20.x
Other All
: High critical
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2008-01-29 21:18 UTC by drew
Modified: 2008-01-29 23:39 UTC
See Also:
GNOME target: ---
GNOME version: 2.19/2.20


Description drew 2008-01-29 21:18:23 UTC 
Version: 2.20.0

What were you doing when the application crashed?



Distribution:                    Solaris Express Community Edition snv_77 X86
Gnome Release: 2.20.1 2007-10-22 (Sun Microsystems, Inc.)
BugBuddy Version: 2.20.1

X Vendor: Sun Microsystems, Inc.
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: nimbus
Icon Theme: nimbus

Memory status: size: 184926208 vsize: 184926208 resident: 67334144 share: 0 rss: 67334144 rss_rlim: 0
CPU usage: start_time: 0 rtime: 3660 utime: 33487205 stime: 3117609 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 0

Backtrace was generated from '/usr/bin/nautilus'

(no debugging symbols found)
sol-thread active.
Retry #1:
Retry #2:
Retry #3:
Retry #4:
[New LWP    1        ]
[New Thread 1 (LWP 1)]

+ Trace 187254

Thread 1 (LWP 1)

  • #0 _waitid
    from /lib/libc.so.1
  • #1 _waitpid
    from /lib/libc.so.1
  • #2 waitpid_cancel
    from /lib/libc.so.1
  • #3 g_spawn_sync
    from /usr/lib/libglib-2.0.so.0
  • #4 g_spawn_command_line_sync
    from /usr/lib/libglib-2.0.so.0
  • #5 __1cNrun_bug_buddy6Fpkclp0_b_
    from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
  • #6 __1cMcheck_if_gdb6Fpv_b_
    from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
  • #7 _ex_text0
    from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
  • #8 sigfatal_handler
  • #9 __sighndlr
    from /lib/libc.so.1
  • #10 call_user_handler
    from /lib/libc.so.1
  • #11 <signal handler called>
  • #12 nautilus_icon_factory_possibly_free_cached_icon
  • #13 g_hash_table_foreach_remove_or_steal
    from /usr/lib/libglib-2.0.so.0
  • #14 g_hash_table_foreach_remove
    from /usr/lib/libglib-2.0.so.0
  • #15 nautilus_icon_factory_sweep
  • #16 g_timeout_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #17 g_main_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #18 g_main_context_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #19 g_main_context_iterate
    from /usr/lib/libglib-2.0.so.0
  • #20 g_main_loop_run
    from /usr/lib/libglib-2.0.so.0
  • #21 gtk_main
    from /usr/lib/libgtk-x11-2.0.so.0
  • #22 main 

Thread 4 (Thread 351 (LWP 351)):
#-1 0xfeef30d7 in _read () from /lib/libc.so.1
No symbol table info available.

Thread 3 (LWP    351        ):
#-1 0xfeef30d7 in _read () from /lib/libc.so.1
No symbol table info available.

Thread 2 (Thread 1 (LWP 1)):
#-1 0xfeef35b7 in _waitid () from /lib/libc.so.1
No symbol table info available.

Thread 1 (LWP    1        ):
#-1 0xfeef35b7 in _waitid () from /lib/libc.so.1
No symbol table info available.
#-1 0xfeef35b7 in _waitid () from /lib/libc.so.1


----------- .xsession-errors (3658202 sec old) ---------------------
/etc/X11/gdm/PreSession/Default: Registering your session with wtmp and utmp
/etc/X11/gdm/PreSession/Default: running: /usr/openwin/bin/sessreg -a -w /var/log/wtmp -u /var/run/utmp -x "/var/lib/gdm/:0.Xservers" -h "" -l ":0" "drew"
/etc/X11/gdm/Xsession: Beginning session setup...
/etc/X11/gdm/Xsession: Setup done, will execute: /usr/bin/ssh-agent -- /usr/dt/config/Xsession.jds
--------------------------------------------------
Comment 1 Cosimo Cecchi 2008-01-29 23:39:02 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 483884 ***