Bug 435089 – crash in Open Folder: intentando activar beryl...

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 435089 - crash in Open Folder: intentando activar beryl...


Summary:	crash in Open Folder: intentando activar beryl...


Status:	RESOLVED DUPLICATE of bug 363856

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-02 04:35 UTC by jose_power1
Modified:	2007-05-02 11:30 UTC

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

Description jose_power1 2007-05-02 04:35:47 UTC

What were you doing when the application crashed?
intentando activar beryl,,,keno me sale el cubo ,,,,mi grafica es ....ati radeon xpress1100    ayuda   xfa


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

Memory status: size: 111058944 vsize: 0 resident: 111058944 share: 0 rss: 25817088 rss_rlim: 0
CPU usage: start_time: 1178068297 rtime: 0 utime: 1656 stime: 0 cutime:1338 cstime: 0 timeout: 318 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 -1214654800 (LWP 4709)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 131817

Thread 1 (Thread -1214654800 (LWP 4709))

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

Comment 1 palfrey 2007-05-02 11:30:56 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 363856 ***