Bug 486520 – crash in Home Folder:

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 486520 - crash in Home Folder:


Summary:	crash in Home Folder:


Status:	RESOLVED DUPLICATE of bug 459221

Product:	nautilus
Classification:	Core
Component:	general
Version:	unspecified
Hardware:	Other All

Importance:	High critical
Target Milestone:	---
Assigned To:	Nautilus Maintainers
QA Contact:	Nautilus Maintainers

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2007-10-14 09:31 UTC by sascha
Modified:	2007-10-19 01:46 UTC

See Also:
GNOME target:	---
GNOME version:	2.17/2.18

Description sascha 2007-10-14 09:31:21 UTC

What were you doing when the application crashed?



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

System: Linux 2.6.22-gentoo-r8 #7 PREEMPT Sat Oct 13 01:33:05 Local time zone must be set--see  x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Glory-Simplex
Icon Theme: SnowIsh-1.0_PNG

Memory status: size: 212090880 vsize: 212090880 resident: 31334400 share: 20054016 rss: 31334400 rss_rlim: 18446744073709551615
CPU usage: start_time: 1192355518 rtime: 161 utime: 147 stime: 14 cutime:11 cstime: 2 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 47702720846144 (LWP 6003)]
0x00002b62a6276aef in waitpid () from /lib/libpthread.so.0

+ Trace 170108

Thread 1 (Thread 47702720846144 (LWP 6003))

#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
#0 waitpid
from /lib/libpthread.so.0



----------- .xsession-errors ---------------------
closing
closing
closing
closing
closing
(gnome-terminal:6067): Vte-WARNING **: Kein Handler für Kontrollsequenz »device-control-string« festgelegt.
No running windows found
/home/sascha/.themes/Glory-Simplex/gtk-2.0/gtkrc:540: Bilddatei konnte nicht in pixmap_path gefunden werden: »Menu-Menubar/menuline.png«
/home/sascha/.themes/Glory-Simplex/gtk-2.0/gtkrc:543: Background image options specified without filename
** 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...
/home/sascha/.themes/Glory-Simplex/gtk-2.0/gtkrc:540: Bilddatei konnte nicht in pixmap_path gefunden werden: »Menu-Menubar/menuline.png«
/home/sascha/.themes/Glory-Simplex/gtk-2.0/gtkrc:543: Background image options specified without filename
--------------------------------------------------

Comment 1 André Klapper 2007-10-19 01:46:37 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 459221 ***