Bug 366680 – crash in CD/DVD Creator: je fermais un fichier lo...

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 366680 - crash in CD/DVD Creator: je fermais un fichier lo...


Summary:	crash in CD/DVD Creator: je fermais un fichier lo...


Status:	RESOLVED DUPLICATE of bug 367701

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:	2006-10-29 06:40 UTC by stasnova
Modified:	2007-06-29 01:26 UTC

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

Description stasnova 2006-10-29 06:40:45 UTC

What were you doing when the application crashed?
je fermais un fichier lorsque cette fenêtre et aparue.


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

Memory status: size: 107229184 vsize: 0 resident: 107229184 share: 0 rss: 29192192 rss_rlim: 0
CPU usage: start_time: 1162103639 rtime: 0 utime: 346 stime: 0 cutime:326 cstime: 0 timeout: 20 it_real_value: 0 frequency: 0

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 -1226856784 (LWP 4948)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 79594

Thread 1 (Thread -1226856784 (LWP 4948))

#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 _IO_sgetn
from /lib/tls/i686/cmov/libc.so.6
#5 g_vasprintf
from /usr/lib/libglib-2.0.so.0
#6 g_strdup_vprintf
from /usr/lib/libglib-2.0.so.0
#7 g_strdup_printf
from /usr/lib/libglib-2.0.so.0
#8 nautilus_file_is_directory
#9 nautilus_file_get_string_attribute
#10 nautilus_file_get_string_attribute
#11 fm_directory_view_bump_zoom_level
#12 gtk_tree_model_get_value
from /usr/lib/libgtk-x11-2.0.so.0
#13 gtk_tree_view_column_cell_set_cell_data
from /usr/lib/libgtk-x11-2.0.so.0
#14 _gtk_tree_view_column_autosize
from /usr/lib/libgtk-x11-2.0.so.0
#15 _gtk_marshal_BOOLEAN__BOXED
from /usr/lib/libgtk-x11-2.0.so.0
#16 g_value_set_boxed
from /usr/lib/libgobject-2.0.so.0
#17 g_closure_invoke
from /usr/lib/libgobject-2.0.so.0
#18 g_signal_chain_from_overridden
from /usr/lib/libgobject-2.0.so.0
#19 g_signal_emit_valist
from /usr/lib/libgobject-2.0.so.0
#20 g_signal_emit
from /usr/lib/libgobject-2.0.so.0
#21 gtk_widget_get_default_style
from /usr/lib/libgtk-x11-2.0.so.0
#22 gtk_main_do_event
from /usr/lib/libgtk-x11-2.0.so.0
#23 gdk_window_is_viewable
from /usr/lib/libgdk-x11-2.0.so.0
#24 gdk_window_process_all_updates
from /usr/lib/libgdk-x11-2.0.so.0
#25 gdk_window_process_all_updates
from /usr/lib/libgdk-x11-2.0.so.0
#26 g_source_is_destroyed
from /usr/lib/libglib-2.0.so.0
#27 g_main_context_dispatch
from /usr/lib/libglib-2.0.so.0
#28 g_main_context_check
from /usr/lib/libglib-2.0.so.0
#29 g_main_loop_run
from /usr/lib/libglib-2.0.so.0
#30 gtk_main
from /usr/lib/libgtk-x11-2.0.so.0
#31 POA_Nautilus_MetafileMonitor__init
#32 __libc_start_main
from /lib/tls/i686/cmov/libc.so.6
#33 ??
#0 __kernel_vsyscall

Comment 1 Behdad Esfahbod 2006-10-31 17:48:56 UTC

Thanks for taking the time to report this bug.
Unfortunately, that stack trace is missing some elements that will help a lot to solve the problem, so it will be hard for the developers to fix that crash. Can you get us a stack trace with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so. Thanks in advance!
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.


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

Comment 2 Pedro Villavicencio 2007-06-29 01:26:03 UTC

Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.


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