Bug 415719 – crash in Open Folder: Estaba moviendo el conte...

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 415719 - crash in Open Folder: Estaba moviendo el conte...


Summary:	crash in Open Folder: Estaba moviendo el conte...


Status:	RESOLVED DUPLICATE of bug 352592

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-07 14:33 UTC by Víctor
Modified:	2007-03-08 14:24 UTC

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

Description Víctor 2007-03-07 14:33:46 UTC

What were you doing when the application crashed?
Estaba moviendo el contenido de una carpeta, a una de sus subcarpetas. Luego he apretado la tecla "subir" y el programa ha dejado de responder.


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

Memory status: size: 246657024 vsize: 246657024 resident: 42090496 share: 24395776 rss: 42090496 rss_rlim: -1
CPU usage: start_time: 1173270231 rtime: 4207 utime: 3787 stime: 420 cutime:88 cstime: 148 timeout: 0 it_real_value: 0 frequency: 100

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

(no debugging symbols found)
Using host libthread_db library "/lib/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 46915028752976 (LWP 4640)]
[New Thread 1124096336 (LWP 5109)]
(no debugging symbols found)
0x00002aab3da24eef in waitpid () from /lib/libpthread.so.0

+ Trace 116610

Thread 1 (Thread 46915028752976 (LWP 4640))

#0 waitpid
from /lib/libpthread.so.0
#1 gnome_gtk_module_info_get
from /usr/lib/libgnomeui-2.so.0
#2 <signal handler called>
#3 raise
from /lib/libc.so.6
#4 abort
from /lib/libc.so.6
#5 g_logv
from /usr/lib/libglib-2.0.so.0
#6 g_log
from /usr/lib/libglib-2.0.so.0
#7 g_assert_warning
from /usr/lib/libglib-2.0.so.0
#8 fm_directory_view_bump_zoom_level
#9 g_closure_invoke
from /usr/lib/libgobject-2.0.so.0
#10 g_signal_chain_from_overridden
from /usr/lib/libgobject-2.0.so.0
#11 g_signal_emit_valist
from /usr/lib/libgobject-2.0.so.0
#12 g_signal_emit
from /usr/lib/libgobject-2.0.so.0
#13 fm_directory_view_bump_zoom_level
#14 g_source_get_current_time
from /usr/lib/libglib-2.0.so.0
#15 g_main_context_dispatch
from /usr/lib/libglib-2.0.so.0
#16 g_main_context_check
from /usr/lib/libglib-2.0.so.0
#17 g_main_loop_run
from /usr/lib/libglib-2.0.so.0
#18 gtk_main
from /usr/lib/libgtk-x11-2.0.so.0
#19 POA_Nautilus_MetafileMonitor__init
#20 __libc_start_main
from /lib/libc.so.6
#21 ??
#22 ??
#23 ??
#0 waitpid
from /lib/libpthread.so.0

Comment 1 Pedro Villavicencio 2007-03-08 14:24: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 352592 ***