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 520425 - crash in Open Folder:
crash in Open Folder:
Status: RESOLVED INCOMPLETE
Product: nautilus
Classification: Core
Component: general
2.21.x
Other Solaris
: High critical
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2008-03-05 00:34 UTC by agregson
Modified: 2009-03-31 17:42 UTC
See Also:
GNOME target: ---
GNOME version: 2.21/2.22



Description agregson 2008-03-05 00:34:28 UTC
Version: 2.21.91

What were you doing when the application crashed?



Distribution:                   Solaris Express Community Edition snv_83a X86
Gnome Release: 2.21.91 2008-02-27 (Sun Microsystems, Inc.)
BugBuddy Version: 2.21.90

X Vendor: Sun Microsystems, Inc.
X Vendor Release: 10300000
Selinux: No
Accessibility: Enabled
GTK+ Theme: Clearlooks
Icon Theme: Tango

Memory status: size: 144838656 vsize: 144838656 resident: 64856064 share: 851968 rss: 64856064 rss_rlim: 0
CPU usage: start_time: 0 rtime: 276 utime: 2377386 stime: 384851 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)]

Thread 1 (LWP 1)

  • #0 __waitid
    from /lib/libc.so.1
  • #1 waitid
    from /lib/libc.so.1
  • #2 waitpid
    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 __sighndlr
    from /lib/libc.so.1
  • #9 call_user_handler
    from /lib/libc.so.1
  • #10 <signal handler called>
  • #11 g_hash_table_remove_internal
    from /usr/lib/libglib-2.0.so.0
  • #12 g_hash_table_remove
    from /usr/lib/libglib-2.0.so.0
  • #13 nautilus_directory_finalize
  • #14 g_object_unref
    from /usr/lib/libgobject-2.0.so.0
  • #15 nautilus_directory_unref
  • #16 finalize
  • #17 g_object_unref
    from /usr/lib/libgobject-2.0.so.0
  • #18 nautilus_file_unref
  • #19 free_xdg_dir_cache
  • #20 destroy_xdg_dir_cache
  • #21 eel_debug_shut_down
    from /usr/lib/libeel-2.so.2
  • #22 main

Thread 4 (Thread 1384        ):
#-1 0xfef00c6b in __lwp_park () from /lib/libc.so.1
No symbol table info available.

Thread 3 (LWP    1384        ):
#-1 0xfef00c6b in __lwp_park () from /lib/libc.so.1
No symbol table info available.

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

Thread 1 (LWP    1        ):
#-1 0xfef04c07 in __waitid () from /lib/libc.so.1
No symbol table info available.
#-1 0xfef04c07 in __waitid () from /lib/libc.so.1
Comment 1 Cosimo Cecchi 2008-03-06 16:56:43 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 ***
Comment 2 Cosimo Cecchi 2008-03-06 16:58:38 UTC
Wrongly marked as a dup, sorry for the spam.
Comment 3 André Klapper 2008-10-18 22:36:22 UTC
Still, it's not a useful trace. :-(
Thanks for taking the time to report this bug.
Unfortunately, the stack trace is missing some elements that will help a lot to solve the problem, so it will be hard for the developers to fix that crash.

Could you please help fixing this by installing some debugging packages [1], start the application as normal, and try to reproduce the crash, if possible?

Once bug-buddy pops up, you can find the stacktrace in the 'Details', now containing way more information. Please copy that stacktrace and paste it as a comment here. Thanks in advance!

[1] Please install debug packages for nautilus, glib2, gtk2, pango, gnome-vfs2, libgnome, and libgnomeui.

More details can be found here: http://live.gnome.org/GettingTraces
Comment 4 André Klapper 2009-03-31 17:42:14 UTC
Closing this bug report as no further information has been provided. Please feel free to reopen this bug if you can provide the information asked for.
Thanks!