Bug 442369 – crash in Computer: explorando la carpeta [e...

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 442369 - crash in Computer: explorando la carpeta [e...


Summary:	crash in Computer: explorando la carpeta [e...


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:

Depends on:
Blocks:

Reported:	2007-05-30 17:17 UTC by miguel.ty
Modified:	2007-05-31 15:42 UTC

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

Description miguel.ty 2007-05-30 17:17:50 UTC

What were you doing when the application crashed?
explorando la carpeta [etc]  se colgo 


Distribution: openSUSE 10.2 (X86-64)
Gnome Release: 2.16.1 2006-11-28 (SUSE)
BugBuddy Version: 2.16.0

Memory status: size: 400637952 vsize: 400637952 resident: 13053952 share: 22593536 rss: 35647488 rss_rlim: 1793633280
CPU usage: start_time: 1180545349 rtime: 652 utime: 594 stime: 58 cutime:10 cstime: 2 timeout: 0 it_real_value: 0 frequency: 100

Backtrace was generated from '/opt/gnome/bin/nautilus'

(no debugging symbols found)
Using host libthread_db library "/lib64/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 47856489157248 (LWP 5765)]
(no debugging symbols found)
0x00002b8672872c5f in waitpid () from /lib64/libpthread.so.0

+ Trace 136849

Thread 1 (Thread 47856489157248 (LWP 5765))

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

Comment 1 palfrey 2007-05-31 15:42:10 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 362346 ***