Bug 461347 – crash in Open Folder: I clicked a hard disk ic...

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 461347 - crash in Open Folder: I clicked a hard disk ic...


Summary:	crash in Open Folder: I clicked a hard disk ic...


Status:	RESOLVED DUPLICATE of bug 459221

Product:	nautilus
Classification:	Core
Component:	general
Version:	2.19.x
Hardware:	Other All

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

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2007-07-28 23:44 UTC by Robert Ford
Modified:	2007-07-29 15:30 UTC

See Also:
GNOME target:	---
GNOME version:	2.19/2.20

Description Robert Ford 2007-07-28 23:44:18 UTC

Version: 2.19.5

What were you doing when the application crashed?
I clicked a hard disk icon in the leftside filetree


Distribution: Unknown
Gnome Release: 2.19.5 2007-07-28 (GARNOME)
BugBuddy Version: 2.18.1

System: Linux 2.6.22-ARCH #1 SMP PREEMPT Mon Jul 23 21:12:00 CEST 2007 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Enabled
GTK+ Theme: MurrinaGilouche
Icon Theme: gnome

Memory status: size: 390340608 vsize: 390340608 resident: 30388224 share: 20168704 rss: 30388224 rss_rlim: 18446744073709551615
CPU usage: start_time: 1185665884 rtime: 111 utime: 100 stime: 11 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

Backtrace was generated from '/opt/garnome/bin/nautilus'

Using host libthread_db library "/lib/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread 47606400706656 (LWP 24359)]
0x00002b4c3913e79f in waitpid () from /lib/libpthread.so.0

+ Trace 151255

Thread 1 (Thread 47606400706656 (LWP 24359))

#0 waitpid
from /lib/libpthread.so.0
#1 libgnomeui_segv_handle
at gnome-ui-init.c line 865
#2 <signal handler called>
#3 IA__g_logv
#4 IA__g_log
at gmessages.c line 517
#5 IA__g_assert_warning
#6 view_as_menu_switch_views_callback
at nautilus-navigation-window.c line 834
#7 IA__g_closure_invoke
at gclosure.c line 490
#8 signal_emit_unlocked_R
at gsignal.c line 2440
#9 IA__g_signal_emit_valist
at gsignal.c line 2199
#10 IA__g_signal_emit
at gsignal.c line 2243
#11 gtk_combo_box_model_row_deleted
at gtkcombobox.c line 3084
#12 IA__g_closure_invoke
at gclosure.c line 490
#13 signal_emit_unlocked_R
at gsignal.c line 2440
#14 IA__g_signal_emit_valist
at gsignal.c line 2199
#15 IA__g_signal_emit
at gsignal.c line 2243
#16 IA__gtk_list_store_remove
at gtkliststore.c line 969
#17 IA__gtk_list_store_clear
at gtkliststore.c line 1167
#18 load_view_as_menu
at nautilus-navigation-window.c line 884
#19 call_ready_callbacks_at_idle
at nautilus-directory-async.c line 1259
#20 IA__g_main_context_dispatch
at gmain.c line 2061
#21 g_main_context_iterate
at gmain.c line 2694
#22 IA__g_main_loop_run
at gmain.c line 2898
#23 IA__gtk_main
at gtkmain.c line 1144
#24 main
at nautilus-main.c line 548
#0 waitpid
from /lib/libpthread.so.0



----------- .xsession-errors ---------------------
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
** 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...
** (nm-applet:24367): WARNING **: <WARN>  nma_dbus_init(): could not acquire its service.  dbus_bus_acquire_service() says: 'Connection ":1.6" is not allowed to own the service "org.freedesktop.Networ
--------------------------------------------------

Comment 1 Pedro Villavicencio 2007-07-29 15:30:10 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 ***