Bug 392435 – crash in Open Folder: Tasto destro -> propriet...

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 392435 - crash in Open Folder: Tasto destro -> propriet...


Summary:	crash in Open Folder: Tasto destro -> propriet...


Status:	RESOLVED DUPLICATE of bug 377052

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-03 19:17 UTC by gittimail
Modified:	2007-01-24 00:57 UTC

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

Description gittimail 2007-01-03 19:17:02 UTC

What were you doing when the application crashed?
Tasto destro -> proprietà


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

Memory status: size: 155455488 vsize: 0 resident: 155455488 share: 0 rss: 31428608 rss_rlim: 0
CPU usage: start_time: 1167407835 rtime: 0 utime: 2795 stime: 0 cutime:2453 cstime: 0 timeout: 342 it_real_value: 0 frequency: 1816

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 -1226832208 (LWP 4443)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 99100

Thread 1 (Thread -1226832208 (LWP 4443))

#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 __kernel_vsyscall
#5 raise
from /lib/tls/i686/cmov/libc.so.6
#6 abort
from /lib/tls/i686/cmov/libc.so.6
#7 g_logv
from /usr/lib/libglib-2.0.so.0
#8 g_log
from /usr/lib/libglib-2.0.so.0
#9 g_assert_warning
from /usr/lib/libglib-2.0.so.0
#10 fm_directory_view_bump_zoom_level
#11 nautilus_file_ref
#12 nautilus_file_ref
#13 nautilus_icon_container_request_update_all
#14 g_source_is_destroyed
from /usr/lib/libglib-2.0.so.0
#15 g_main_context_dispatch
from /usr/lib/libglib-2.0.so.0
#16 g_main_context_check
from /usr/lib/libglib-2.0.so.0
#17 g_main_loop_run
from /usr/lib/libglib-2.0.so.0
#18 gtk_main
from /usr/lib/libgtk-x11-2.0.so.0
#19 POA_Nautilus_MetafileMonitor__init
#20 __libc_start_main
from /lib/tls/i686/cmov/libc.so.6
#21 ??
#0 __kernel_vsyscall

Comment 1 André Klapper 2007-01-03 21:24:13 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 Ubuntu 6.10: nautilus-dbg, libglib2.0-0-dbg, libgtk2.0-0-dbg, libpango1.0-0-dbg, libgnomevfs2-0-dbg, and libgnomeui-0-dbg.

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

Comment 2 Bruno Boaventura 2007-01-24 00:57: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 377052 ***