Bug 429914 – crash in Open Folder: Estaba explorando una ca...

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 429914 - crash in Open Folder: Estaba explorando una ca...


Summary:	crash in Open Folder: Estaba explorando una ca...


Status:	RESOLVED DUPLICATE of bug 362346

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:

Duplicates:	431424 431708 431728 432052 432495 433659 (view as bug list)
Depends on:
Blocks:

Reported:	2007-04-15 10:19 UTC by dlomaxd
Modified:	2007-06-22 18:21 UTC

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

Description dlomaxd 2007-04-15 10:19:10 UTC

What were you doing when the application crashed?
Estaba explorando una carpeta que habia incluido en el grabador de dc/dvd


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

Memory status: size: 88973312 vsize: 0 resident: 88973312 share: 0 rss: 32735232 rss_rlim: 0
CPU usage: start_time: 1176626022 rtime: 0 utime: 5230 stime: 0 cutime:4463 cstime: 0 timeout: 767 it_real_value: 0 frequency: 552

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

+ Trace 127912

Thread 1 (Thread -1226389840 (LWP 4538))

#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 __kernel_vsyscall
#5 raise
from /lib/tls/i686/cmov/libc.so.6
#6 abort
from /lib/tls/i686/cmov/libc.so.6
#7 g_logv
from /usr/lib/libglib-2.0.so.0
#8 g_log
from /usr/lib/libglib-2.0.so.0
#9 g_assert_warning
from /usr/lib/libglib-2.0.so.0
#10 nautilus_directory_async_state_changed
#11 fm_directory_view_bump_zoom_level
#12 g_cclosure_marshal_VOID__VOID
from /usr/lib/libgobject-2.0.so.0
#13 g_value_set_boxed
from /usr/lib/libgobject-2.0.so.0
#14 g_closure_invoke
from /usr/lib/libgobject-2.0.so.0
#15 g_signal_chain_from_overridden
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 fm_directory_view_bump_zoom_level
#19 fm_directory_view_bump_zoom_level
#20 nautilus_clipboard_monitor_emit_changed
#21 nautilus_directory_async_state_changed
#22 nautilus_icon_container_request_update_all
#23 g_source_is_destroyed
from /usr/lib/libglib-2.0.so.0
#24 g_main_context_dispatch
from /usr/lib/libglib-2.0.so.0
#25 g_main_context_check
from /usr/lib/libglib-2.0.so.0
#26 g_main_loop_run
from /usr/lib/libglib-2.0.so.0
#27 gtk_main
from /usr/lib/libgtk-x11-2.0.so.0
#28 POA_Nautilus_MetafileMonitor__init
#29 __libc_start_main
from /lib/tls/i686/cmov/libc.so.6
#30 ??
#0 __kernel_vsyscall

Comment 1 palfrey 2007-04-16 18:11:16 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!

Comment 2 palfrey 2007-04-26 11:13:20 UTC

*** Bug 431424 has been marked as a duplicate of this bug. ***

Comment 3 palfrey 2007-04-27 10:41:41 UTC

*** Bug 433659 has been marked as a duplicate of this bug. ***

Comment 4 palfrey 2007-04-27 14:44:40 UTC

*** Bug 431708 has been marked as a duplicate of this bug. ***

Comment 5 palfrey 2007-04-27 14:44:45 UTC

*** Bug 431728 has been marked as a duplicate of this bug. ***

Comment 6 palfrey 2007-04-27 14:55:08 UTC

*** Bug 432052 has been marked as a duplicate of this bug. ***

Comment 7 palfrey 2007-04-27 15:02:44 UTC

*** Bug 432495 has been marked as a duplicate of this bug. ***

Comment 8 enenl.desyncer 2007-04-27 20:28:22 UTC

I wouldn't mind getting traces, I don't think I'll be able to reproduce the crash though, since I've been using it for awhile since and nothing happened.

Comment 9 André Klapper 2007-06-22 18:21:00 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 362346 ***