Bug 420750 – crash in Open Folder: browsing old xp partitio...

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 420750 - crash in Open Folder: browsing old xp partitio...


Summary:	crash in Open Folder: browsing old xp partitio...


Status:	RESOLVED INCOMPLETE

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:

Duplicates:	443041 (view as bug list)
Depends on:
Blocks:

Reported:	2007-03-20 21:54 UTC by gruffudd
Modified:	2007-07-30 03:14 UTC

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

Description gruffudd 2007-03-20 21:54:40 UTC

What were you doing when the application crashed?
browsing old xp partition


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

Memory status: size: 109068288 vsize: 0 resident: 109068288 share: 0 rss: 14622720 rss_rlim: 0
CPU usage: start_time: 1174427622 rtime: 0 utime: 0 stime: 0 cutime:0 cstime: 0 timeout: 0 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 -1227041104 (LWP 25553)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 120534

Thread 1 (Thread -1227041104 (LWP 25553))

#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 gnome_vfs_find_directory
from /usr/lib/libgnomevfs-2.so.0
#5 gnome_vfs_close_cancellable
from /usr/lib/libgnomevfs-2.so.0
#6 gnome_vfs_create_uri
from /usr/lib/libgnomevfs-2.so.0
#7 fm_directory_view_bump_zoom_level
#8 g_source_get_current_time
from /usr/lib/libglib-2.0.so.0
#9 g_main_context_dispatch
from /usr/lib/libglib-2.0.so.0
#10 g_main_context_check
from /usr/lib/libglib-2.0.so.0
#11 g_main_loop_run
from /usr/lib/libglib-2.0.so.0
#12 gtk_main
from /usr/lib/libgtk-x11-2.0.so.0
#13 POA_Nautilus_MetafileMonitor__init
#14 __libc_start_main
from /lib/tls/i686/cmov/libc.so.6
#15 ??
#0 __kernel_vsyscall

Comment 1 Susana 2007-03-23 15:08:47 UTC

Thanks for taking the time to report this bug.
Unfortunately, that 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 the application 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] debugging packages for nautilus, glib, gtk+, pango, gnome-vfs, libgnome, and libgnomeui.

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

Comment 2 gruffudd 2007-03-27 22:28:25 UTC

Unfortunately it looks as if there is a fault in the nautilus-dbgsym package which results in unmet dependencies when using apt-get. The same problem has been reported here:

https://lists.ubuntu.com/archives/ubuntu-users/2007-February/106031.html

Comment 3 Susana 2007-03-27 23:10:13 UTC

Hi,

Thank you for your feedback. Could you please try the *-dbg packages?

sudo apt-get install nautilus-dbg libglib2.0-0-dbg libgtk2.0-0-dbg libpango1.0-0-dbg libgnomevfs2-0-dbg libgnomeui-0-dbg

Thanks in advance.

Comment 4 Pedro Villavicencio 2007-06-02 00:59:01 UTC

*** Bug 443041 has been marked as a duplicate of this bug. ***

Comment 5 Pedro Villavicencio 2007-07-30 03:14:53 UTC

Closing this bug report as no further information has been provided. Please feel free to reopen this bug if you can provide the information asked for.
Thanks!