Bug 420622 – crash in Open Folder: accedere alla memory-car...

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 420622 - crash in Open Folder: accedere alla memory-car...


Summary:	crash in Open Folder: accedere alla memory-car...


Status:	RESOLVED DUPLICATE of bug 353836

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

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

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2007-03-20 17:32 UTC by cata.rocco
Modified:	2007-03-21 19:07 UTC

See Also:
GNOME target:	---
GNOME version:	2.15/2.16

Description cata.rocco 2007-03-20 17:32:12 UTC

What were you doing when the application crashed?
accedere alla memory-card tramite lettore integrato nella stampante hp-psc 1355


Distribution: Ubuntu 6.10 (edgy)
Gnome Release: 2.16.1 2006-10-02 (Ubuntu)
BugBuddy Version: 2.16.0

Memory status: size: 124010496 vsize: 0 resident: 124010496 share: 0 rss: 32915456 rss_rlim: 0
CPU usage: start_time: 1174405665 rtime: 0 utime: 1316 stime: 0 cutime:924 cstime: 0 timeout: 392 it_real_value: 0 frequency: 277

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

Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread -1226873168 (LWP 4997)]
0xffffe410 in __kernel_vsyscall ()

+ Trace 120424

Thread 1 (Thread -1226873168 (LWP 4997))

#0 __kernel_vsyscall
#1 __waitpid_nocancel
from /lib/tls/i686/cmov/libpthread.so.0
#2 gnome_gtk_module_info_get
from /usr/lib/libgnomeui-2.so.0
#3 <signal handler called>
#4 strchr
from /lib/tls/i686/cmov/libc.so.6
#5 nautilus_module_initialize
from /usr/lib/nautilus/extensions-1.0/libnautilus-gksu.so
#6 g_cclosure_marshal_VOID__VOID
from /usr/lib/libgobject-2.0.so.0
#7 g_closure_invoke
from /usr/lib/libgobject-2.0.so.0
#8 g_signal_chain_from_overridden
from /usr/lib/libgobject-2.0.so.0
#9 g_signal_emit_valist
from /usr/lib/libgobject-2.0.so.0
#10 g_signal_emit
from /usr/lib/libgobject-2.0.so.0
#11 nautilus_menu_item_activate
at nautilus-menu-item.c line 85
#12 extension_action_slow_mime_types_ready_callback
at fm-directory-view.c line 4827
#13 file_list_file_ready_callback
at nautilus-file.c line 5949
#14 ready_callback_call
at nautilus-directory-async.c line 1237
#15 nautilus_directory_async_state_changed
at nautilus-directory-async.c line 1849
#16 nautilus_directory_call_when_ready_internal
at nautilus-directory-async.c line 1319
#17 vfs_file_call_when_ready
at nautilus-vfs-file.c line 66
#18 nautilus_file_call_when_ready
at nautilus-file.c line 5548
#19 nautilus_file_list_call_when_ready
at nautilus-file.c line 5982
#20 extension_action_callback
at fm-directory-view.c line 4843
#21 g_cclosure_marshal_VOID__VOID
from /usr/lib/libgobject-2.0.so.0
#22 g_closure_invoke
from /usr/lib/libgobject-2.0.so.0
#23 g_signal_chain_from_overridden
from /usr/lib/libgobject-2.0.so.0
#24 g_signal_emit_valist
from /usr/lib/libgobject-2.0.so.0
#25 g_signal_emit
from /usr/lib/libgobject-2.0.so.0
#26 _gtk_action_emit_activate
from /usr/lib/libgtk-x11-2.0.so.0
#27 gtk_action_activate
from /usr/lib/libgtk-x11-2.0.so.0
#28 g_cclosure_marshal_VOID__VOID
from /usr/lib/libgobject-2.0.so.0
#29 g_closure_invoke
from /usr/lib/libgobject-2.0.so.0
#30 g_signal_chain_from_overridden
from /usr/lib/libgobject-2.0.so.0
#31 g_signal_emit_valist
from /usr/lib/libgobject-2.0.so.0
#32 g_signal_emit
from /usr/lib/libgobject-2.0.so.0
#33 gtk_widget_activate
from /usr/lib/libgtk-x11-2.0.so.0
#34 gtk_menu_shell_activate_item
from /usr/lib/libgtk-x11-2.0.so.0
#35 gtk_menu_shell_append
from /usr/lib/libgtk-x11-2.0.so.0
#36 gtk_menu_reorder_child
from /usr/lib/libgtk-x11-2.0.so.0
#37 _gtk_marshal_BOOLEAN__BOXED
from /usr/lib/libgtk-x11-2.0.so.0
#38 g_value_set_boxed
from /usr/lib/libgobject-2.0.so.0
#39 g_closure_invoke
from /usr/lib/libgobject-2.0.so.0
#40 g_signal_chain_from_overridden
from /usr/lib/libgobject-2.0.so.0
#41 g_signal_emit_valist
from /usr/lib/libgobject-2.0.so.0
#42 g_signal_emit
from /usr/lib/libgobject-2.0.so.0
#43 gtk_widget_get_default_style
from /usr/lib/libgtk-x11-2.0.so.0
#44 gtk_propagate_event
from /usr/lib/libgtk-x11-2.0.so.0
#45 gtk_main_do_event
from /usr/lib/libgtk-x11-2.0.so.0
#46 _gdk_events_init
from /usr/lib/libgdk-x11-2.0.so.0
#47 g_main_context_dispatch
from /usr/lib/libglib-2.0.so.0
#48 g_main_context_check
from /usr/lib/libglib-2.0.so.0
#49 g_main_loop_run
from /usr/lib/libglib-2.0.so.0
#50 gtk_main
from /usr/lib/libgtk-x11-2.0.so.0
#51 main
at nautilus-main.c line 372
#52 __libc_start_main
from /lib/tls/i686/cmov/libc.so.6
#53 _start
#0 __kernel_vsyscall

Comment 1 Christian Kirbach 2007-03-21 19:05:04 UTC

trace is not bad, but can you please isntall the glib and nautilusdebugging packages? Please see
http://live.gnome.org/GettingTraces for more information on how to do so.
Thanks in advance!


Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but the maintainers need more information to fix the bug. Could you please answer the questions in the other report in order to help the developers?


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

Comment 2 Christian Kirbach 2007-03-21 19:06:37 UTC

sorry that was wrong

Comment 3 Christian Kirbach 2007-03-21 19:07:53 UTC

Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but the maintainers need more information to fix the bug. Could you please answer the questions in the other report in order to help the developers?


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