Bug 391451 – crash in Computer:

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 391451 - crash in Computer:


Summary:	crash in Computer:


Status:	RESOLVED DUPLICATE of bug 391452

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-01-01 01:25 UTC by dvn805
Modified:	2007-01-03 20:51 UTC

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

Description dvn805 2007-01-01 01:25:04 UTC

What were you doing when the application crashed?



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

Memory status: size: 452595712 vsize: 452595712 resident: 17514496 share: 22392832 rss: 39907328 rss_rlim: 894858240
CPU usage: start_time: 1167614681 rtime: 776 utime: 702 stime: 74 cutime:6 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 47566915338880 (LWP 29163)]
(no debugging symbols found)
0x00002b4306955c5f in waitpid () from /lib64/libpthread.so.0

+ Trace 98390

Thread 1 (Thread 47566915338880 (LWP 29163))

#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 nautilus_file_get_uri
#4 nautilus_file_get_parent_uri
#5 g_list_foreach
from /opt/gnome/lib64/libglib-2.0.so.0
#6 g_list_foreach
from /opt/gnome/lib64/libglib-2.0.so.0
#7 g_list_foreach
from /opt/gnome/lib64/libglib-2.0.so.0
#8 g_list_foreach
from /opt/gnome/lib64/libglib-2.0.so.0
#9 g_list_foreach
from /opt/gnome/lib64/libglib-2.0.so.0
#10 g_list_foreach
from /opt/gnome/lib64/libglib-2.0.so.0
#11 g_list_foreach
from /opt/gnome/lib64/libglib-2.0.so.0
#12 POA_Nautilus_MetafileMonitor__init
#13 fm_directory_view_bump_zoom_level
#14 fm_directory_view_bump_zoom_level
#15 g_source_get_current_time
from /opt/gnome/lib64/libglib-2.0.so.0
#16 g_main_context_dispatch
from /opt/gnome/lib64/libglib-2.0.so.0
#17 g_main_context_prepare
from /opt/gnome/lib64/libglib-2.0.so.0
#18 g_main_loop_run
from /opt/gnome/lib64/libglib-2.0.so.0
#19 gtk_main
from /opt/gnome/lib64/libgtk-x11-2.0.so.0
#20 POA_Nautilus_MetafileMonitor__init
#21 __libc_start_main
from /lib64/libc.so.6
#22 g_cclosure_marshal_VOID__ENUM
#23 ??
#24 ??
#0 waitpid
from /lib64/libpthread.so.0

Comment 1 André Klapper 2007-01-03 20:49:33 UTC

Thanks for taking the time to report this.

Unfortunately, the stack trace is missing some elements that will help a lot
to solve the problem, so it will be hard for the developers to fix that crash.

Could you please help fixing this by installing some debugging packages [1], start Nautilus as normal, and try to reproduce the crash, if possible?
Once bug-buddy pops up, you can find the stacktrace in the "Details", now
containing way more information. Please copy that stacktrace and paste it as a
comment here. Thanks in advance!

[1] Please install the following debug packages provided by SuSE 10.2: nautilus-debuginfo, glib2-debuginfo, gtk2-debuginfo, pango-debuginfo, gnome-vfs2-debuginfo, libgnome-debuginfo, and libgnomeui-debuginfo.

SuSE 10.2 provides a debuginfo package repository, that users can add to their installation and installation sources, under http://download.opensuse.org/distribution/10.2/repo/debug/suse/ .

More details can be found here:
http://live.gnome.org/GettingTraces/DistroSpecificInstructions


Also, this bug report isn't very useful because it doesn't describe the bug well. If you have time and can still reproduce the bug, please read http://bugzilla.gnome.org/bug-HOWTO.html and add a more useful description to this bug.

Comment 2 André Klapper 2007-01-03 20:51:07 UTC

okay... obviously a duplicate of bug 391452, but we're still missing information what you did when this crash happened. please add that piecce of info to bug 391452. thanks a lot in advance for helping!

*** This bug has been marked as a duplicate of 391452 ***