Bug 355023 – crash in Open Folder: i was searching somethin...

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 355023 - crash in Open Folder: i was searching somethin...


Summary:	crash in Open Folder: i was searching somethin...


Status:	RESOLVED DUPLICATE of bug 351713

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-09-08 22:01 UTC by quasarfreak
Modified:	2006-10-09 15:01 UTC

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

Description quasarfreak 2006-09-08 22:01:51 UTC

What were you doing when the application crashed?
i was searching something in google, and just finish of install prelink


Distribution: Ubuntu 6.10 (edgy)
Gnome Release: 2.16.0 2006-09-04 (Ubuntu)
BugBuddy Version: 2.16.0

Memory status: size: 75788288 vsize: 0 resident: 75788288 share: 0 rss: 22929408 rss_rlim: 0
CPU usage: start_time: 1157752795 rtime: 0 utime: 138 stime: 0 cutime:127 cstime: 0 timeout: 11 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 -1208256848 (LWP 20108)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 71916

Thread 1 (Thread -1208256848 (LWP 20108))

#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_directory_async_state_changed
#5 nautilus_file_get_uri
#6 nautilus_file_get_uri
#7 nautilus_file_has_volume
#8 nautilus_icon_container_request_update_all
#9 fm_directory_view_bump_zoom_level
#10 nautilus_file_ref
#11 nautilus_file_ref
#12 fm_directory_view_bump_zoom_level
#13 nautilus_marshal_VOID__OBJECT_OBJECT
#14 g_value_set_boxed
from /usr/lib/libgobject-2.0.so.0
#15 g_closure_invoke
from /usr/lib/libgobject-2.0.so.0
#16 g_signal_chain_from_overridden
from /usr/lib/libgobject-2.0.so.0
#17 g_signal_emit_valist
from /usr/lib/libgobject-2.0.so.0
#18 g_signal_emit
from /usr/lib/libgobject-2.0.so.0
#19 fm_directory_view_bump_zoom_level
#20 g_source_get_current_time
from /usr/lib/libglib-2.0.so.0
#21 g_main_context_dispatch
from /usr/lib/libglib-2.0.so.0
#22 g_main_context_check
from /usr/lib/libglib-2.0.so.0
#23 g_main_loop_run
from /usr/lib/libglib-2.0.so.0
#24 gtk_main
from /usr/lib/libgtk-x11-2.0.so.0
#25 POA_Nautilus_MetafileMonitor__init
#26 __libc_start_main
from /lib/tls/i686/cmov/libc.so.6
#27 ??
#0 __kernel_vsyscall

Comment 1 Christian Kirbach 2006-09-09 16:20:43 UTC

unique trace

Thanks for the bug report. Unfortunately, that stack trace is not very useful in determining the cause of the crash. Can you get us one with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so.

Comment 2 André Klapper 2006-10-09 15:01:59 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 351713 ***