Bug 363993 – crash in Open Folder: Instalando Beryl y el dr...

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 363993 - crash in Open Folder: Instalando Beryl y el dr...


Summary:	crash in Open Folder: Instalando Beryl y el dr...


Status:	RESOLVED DUPLICATE of bug 355216

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-21 18:44 UTC by VPablo
Modified:	2006-10-21 20:27 UTC

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

Description VPablo 2006-10-21 18:44:30 UTC

What were you doing when the application crashed?
Instalando Beryl y el driver de NVidia tal y como dice en:
http://wiki.beryl-project.org/index.php/Install/Ubuntu/Edgy/nVIDIA


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

Memory status: size: 84729856 vsize: 0 resident: 84729856 share: 0 rss: 29298688 rss_rlim: 0
CPU usage: start_time: 1161462122 rtime: 0 utime: 634 stime: 0 cutime:517 cstime: 0 timeout: 117 it_real_value: 0 frequency: 1208

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

+ Trace 77546

Thread 1 (Thread -1227045200 (LWP 6251))

#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 fm_directory_view_bump_zoom_level
#11 nautilus_file_ref
#12 nautilus_icon_container_request_update_all
#13 fm_directory_view_bump_zoom_level
#14 fm_directory_view_supports_zooming
#15 g_cclosure_marshal_VOID__VOID
from /usr/lib/libgobject-2.0.so.0
#16 g_closure_invoke
from /usr/lib/libgobject-2.0.so.0
#17 g_signal_chain_from_overridden
from /usr/lib/libgobject-2.0.so.0
#18 g_signal_emit_valist
from /usr/lib/libgobject-2.0.so.0
#19 g_signal_emit
from /usr/lib/libgobject-2.0.so.0
#20 nautilus_file_get_uri
#21 nautilus_file_get_uri
#22 nautilus_directory_async_state_changed
#23 gnome_vfs_job_get_count
from /usr/lib/libgnomevfs-2.so.0
#24 ??
#25 ??
#26 ??
#27 ??
from /usr/lib/libgthread-2.0.so.0
#28 ??
#29 ??
from /usr/lib/libglib-2.0.so.0
#30 ??
#31 g_slice_alloc
from /usr/lib/libglib-2.0.so.0
#32 g_source_is_destroyed
from /usr/lib/libglib-2.0.so.0
#33 g_main_context_dispatch
from /usr/lib/libglib-2.0.so.0
#34 g_main_context_check
from /usr/lib/libglib-2.0.so.0
#35 g_main_loop_run
from /usr/lib/libglib-2.0.so.0
#36 gtk_main
from /usr/lib/libgtk-x11-2.0.so.0
#37 POA_Nautilus_MetafileMonitor__init
#38 __libc_start_main
from /lib/tls/i686/cmov/libc.so.6
#39 ??
#0 __kernel_vsyscall

Comment 1 Karsten Bräckelmann 2006-10-21 18:56:20 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 355216 ***

Comment 2 VPablo 2006-10-21 20:27:05 UTC

EL problema ha sido actualizar el beryl sin haber actualizado antes el restod e paquetes. Ademas estoy con un Live-CD y la RC1, por lo que supongo que el fallo no sera el mismo si estuviera instalado en el disco.