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 491733 - crash in Computer:
crash in Computer:
Status: RESOLVED DUPLICATE of bug 459221
Product: nautilus
Classification: Core
Component: general
2.18.x
Other All
: High critical
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2007-10-30 14:22 UTC by brankob
Modified: 2007-10-31 02:03 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18


Description brankob 2007-10-30 14:22:46 UTC 
Version: 2.18.3

What were you doing when the application crashed?



Distribution: Gentoo Base System release 1.12.9
Gnome Release: 2.18.3 2007-10-15 (Gentoo)
BugBuddy Version: 2.18.1

System: Linux 2.6.23-gentoo #3 SMP Fri Oct 26 23:16:21 CEST 2007 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: gnome

Memory status: size: 316903424 vsize: 316903424 resident: 35069952 share: 22544384 rss: 35069952 rss_rlim: 18446744073709551615
CPU usage: start_time: 1193747961 rtime: 165 utime: 156 stime: 9 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)
0x00002b0c8822393f in waitpid () from /lib/libpthread.so.0

+ Trace 173920

  • #0 waitpid
    from /lib/libpthread.so.0
  • #1 ??
    from /usr/lib/libgnomeui-2.so.0
  • #2 <signal handler called>
  • #3 raise
    from /lib/libc.so.6
  • #4 abort
    from /lib/libc.so.6
  • #5 g_logv
    from /usr/lib/libglib-2.0.so.0
  • #6 g_log
    from /usr/lib/libglib-2.0.so.0
  • #7 g_assert_warning
    from /usr/lib/libglib-2.0.so.0
  • #8 ??
  • #9 g_closure_invoke
    from /usr/lib/libgobject-2.0.so.0
  • #10 ??
    from /usr/lib/libgobject-2.0.so.0
  • #11 g_signal_emit_valist
    from /usr/lib/libgobject-2.0.so.0
  • #12 g_signal_emit
    from /usr/lib/libgobject-2.0.so.0
  • #13 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #14 g_closure_invoke
    from /usr/lib/libgobject-2.0.so.0
  • #15 ??
    from /usr/lib/libgobject-2.0.so.0
  • #16 g_signal_emit_valist
    from /usr/lib/libgobject-2.0.so.0
  • #17 g_signal_emit
    from /usr/lib/libgobject-2.0.so.0
  • #18 gtk_list_store_remove
    from /usr/lib/libgtk-x11-2.0.so.0
  • #19 gtk_list_store_clear
    from /usr/lib/libgtk-x11-2.0.so.0
  • #20 ??
  • #21 ??
  • #22 g_main_context_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #23 ??
    from /usr/lib/libglib-2.0.so.0
  • #24 g_main_loop_run
    from /usr/lib/libglib-2.0.so.0
  • #25 gtk_main
    from /usr/lib/libgtk-x11-2.0.so.0
  • #26 main 


----------- .xsession-errors ---------------------
** Message: drive = 0
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
** ERROR **: file nautilus-navigation-window.c: line 834 (activate_nth_short_list_item): assertion failed: (index < g_list_length (window->details->short_list_viewers))
aborting...
Error while mapping shared library sections:
/usr/lib64/nautilus/extensions-1.0/libnautilus-burn-extension.so: No such file or directory.
Error while mapping shared library sections:
/usr/lib64/gnome-vfs-2.0/modules/libmapping.so: No such file or directory.
warning: no loadable sections found in added symbol-file system-supplied DSO at 0x7fff281fd000
--------------------------------------------------
Comment 1 Christoph Wolk 2007-10-31 02:03:01 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 is cause by running nauilus 2.18 with current gtk. Using a current version of nautilus (or gtk 2.10) should fix this. Furthermore, while we appreciate it a lot when people inform us about bugs, in general it is not neccessary to report it everytime an application crashes in quick succession, as these crashes are likely to have the same cause. Thank you for your interest in improving GNOME.

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