Bug 415475 – crash in Home Folder: presuvaô mp.3 subor ..po...

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 415475 - crash in Home Folder: presuvaô mp.3 subor ..po...


Summary:	crash in Home Folder: presuvaô mp.3 subor ..po...


Status:	RESOLVED DUPLICATE of bug 320020

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-03-06 21:53 UTC by voxar
Modified:	2007-03-10 22:12 UTC

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

Description voxar 2007-03-06 21:53:21 UTC

What were you doing when the application crashed?
presuvaô mp.3 subor ..pocuval stream v aac -vlc player a presuval z win disku 


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

Memory status: size: 121729024 vsize: 0 resident: 121729024 share: 0 rss: 47927296 rss_rlim: 0
CPU usage: start_time: 1173207550 rtime: 0 utime: 34570 stime: 0 cutime:17905 cstime: 0 timeout: 16665 it_real_value: 0 frequency: 5028

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

(no debugging symbols found)
Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1227196752 (LWP 4461)]
[New Thread -1237533792 (LWP 13097)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 116427

Thread 1 (Thread -1227196752 (LWP 4461))

#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 nautilus_clipboard_monitor_emit_changed
#5 nautilus_clipboard_monitor_emit_changed
#6 nautilus_directory_async_state_changed
#7 nautilus_directory_async_state_changed
#8 nautilus_undo_transaction_unregister_object
#9 nautilus_file_get_uri
#10 POA_Nautilus_MetafileMonitor__init
#11 fm_directory_view_pop_up_location_context_menu
#12 fm_directory_view_pop_up_location_context_menu
#13 fm_directory_view_bump_zoom_level
#14 g_cclosure_marshal_VOID__POINTER
from /usr/lib/libgobject-2.0.so.0
#15 g_closure_invoke
from /usr/lib/libgobject-2.0.so.0
#16 g_signal_chain_from_overridden
from /usr/lib/libgobject-2.0.so.0
#17 g_signal_emit_valist
from /usr/lib/libgobject-2.0.so.0
#18 g_signal_emit
from /usr/lib/libgobject-2.0.so.0
#19 nautilus_icon_container_request_update_all
#20 eel_marshal_BOOLEAN__BOXED
from /usr/lib/libeel-2.so.2
#21 g_closure_invoke
from /usr/lib/libgobject-2.0.so.0
#22 g_signal_chain_from_overridden
from /usr/lib/libgobject-2.0.so.0
#23 g_signal_emit_valist
from /usr/lib/libgobject-2.0.so.0
#24 g_signal_emit
from /usr/lib/libgobject-2.0.so.0
#25 eel_canvas_window_to_world
from /usr/lib/libeel-2.so.2
#26 nautilus_icon_container_request_update_all
#27 _gtk_marshal_BOOLEAN__BOXED
from /usr/lib/libgtk-x11-2.0.so.0
#28 g_value_set_boxed
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_get_default_style
from /usr/lib/libgtk-x11-2.0.so.0
#34 gtk_propagate_event
from /usr/lib/libgtk-x11-2.0.so.0
#35 gtk_main_do_event
from /usr/lib/libgtk-x11-2.0.so.0
#36 _gdk_events_init
from /usr/lib/libgdk-x11-2.0.so.0
#37 g_main_context_dispatch
from /usr/lib/libglib-2.0.so.0
#38 g_main_context_check
from /usr/lib/libglib-2.0.so.0
#39 g_main_loop_run
from /usr/lib/libglib-2.0.so.0
#40 gtk_main
from /usr/lib/libgtk-x11-2.0.so.0
#41 POA_Nautilus_MetafileMonitor__init
#42 __libc_start_main
from /lib/tls/i686/cmov/libc.so.6
#43 ??
#0 __kernel_vsyscall

Comment 1 André Klapper 2007-03-10 22:12:29 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 320020 ***