Bug 353707 – crash in Computer: trying to re-start compu...

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 353707 - crash in Computer: trying to re-start compu...


Summary:	crash in Computer: trying to re-start compu...


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-08-31 17:13 UTC by JHOLZBAUER
Modified:	2006-08-31 17:26 UTC

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

Description JHOLZBAUER 2006-08-31 17:13:37 UTC

What were you doing when the application crashed?
trying to re-start computer after an update...not a programmer but willing to help if possible..


Distribution: Ubuntu 6.10 (edgy)
Gnome Release: 2.15.92 2006-08-22 (Ubuntu)
BugBuddy Version: 2.15.92

Memory status: size: 116215808 vsize: 0 resident: 116215808 share: 0 rss: 18083840 rss_rlim: 0
CPU usage: start_time: 1157044281 rtime: 0 utime: 103 stime: 0 cutime:97 cstime: 0 timeout: 6 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 -1226983760 (LWP 8827)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 71318

Thread 1 (Thread -1226983760 (LWP 8827))

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

Comment 1 Karsten Bräckelmann 2006-08-31 17:21:47 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 ***

Comment 2 Karsten Bräckelmann 2006-08-31 17:26:55 UTC

JHOLZBAUER, if you could install the relevant debugging packages and reproduce the crash, that really would help. See bug 351713 for details.

When bug-buddy comes up, see the details for the stacktrace. Please add the stacktrace as a comment to the other bug, if you can get one with debugging symbols. Thanks!