Bug 394971 – crash in Open Folder: Apaguei alguns arquivos ...

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 394971 - crash in Open Folder: Apaguei alguns arquivos ...


Summary:	crash in Open Folder: Apaguei alguns arquivos ...


Status:	RESOLVED INCOMPLETE

Product:	nautilus
Classification:	Core
Component:	general
Version:	2.16.x
Hardware:	Other All

Importance:	High critical
Target Milestone:	---
Assigned To:	Nautilus Maintainers
QA Contact:	Nautilus Maintainers

URL:
Whiteboard:

Duplicates:	404899 423212 453116 (view as bug list)
Depends on:
Blocks:

Reported:	2007-01-10 10:24 UTC by t.nogueira
Modified:	2007-12-07 16:33 UTC

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

Description t.nogueira 2007-01-10 10:24:58 UTC

What were you doing when the application crashed?
Apaguei alguns arquivos com o comando shit+delete.


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

Memory status: size: 85712896 vsize: 0 resident: 85712896 share: 0 rss: 29495296 rss_rlim: 0
CPU usage: start_time: 1168423737 rtime: 0 utime: 713 stime: 0 cutime:660 cstime: 0 timeout: 53 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 -1227315536 (LWP 4210)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 100944

Thread 1 (Thread -1227315536 (LWP 4210))

#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 g_type_check_is_value_type
from /usr/lib/libgobject-2.0.so.0
#5 g_value_type_compatible
from /usr/lib/libgobject-2.0.so.0
#6 g_object_class_override_property
from /usr/lib/libgobject-2.0.so.0
#7 g_signal_emit_valist
from /usr/lib/libgobject-2.0.so.0
#8 g_signal_emit
from /usr/lib/libgobject-2.0.so.0
#9 fm_directory_view_bump_zoom_level
#10 g_source_get_current_time
from /usr/lib/libglib-2.0.so.0
#11 g_main_context_dispatch
from /usr/lib/libglib-2.0.so.0
#12 g_main_context_check
from /usr/lib/libglib-2.0.so.0
#13 g_main_loop_run
from /usr/lib/libglib-2.0.so.0
#14 gtk_main
from /usr/lib/libgtk-x11-2.0.so.0
#15 POA_Nautilus_MetafileMonitor__init
#16 __libc_start_main
from /lib/tls/i686/cmov/libc.so.6
#17 ??
#0 __kernel_vsyscall

Comment 1 André Klapper 2007-01-12 00:46:59 UTC

Thanks for taking the time to report this bug.
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: 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

Comment 2 palfrey 2007-01-12 01:22:43 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 348979 ***

Comment 3 Mariano Suárez-Alvarez 2007-02-07 04:18:04 UTC

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

Comment 4 André Klapper 2007-03-31 13:17:40 UTC

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

Comment 5 Christian Kirbach 2007-07-02 20:50:41 UTC

uhm Tom are you sure this is a dup??

Comment 6 Christian Kirbach 2007-07-02 20:52:31 UTC

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

Comment 7 Christian Kirbach 2007-07-02 21:04:34 UTC

<lunacymaze> yes I agree
<andre> uhm yes, wrong

Comment 8 Christian Kirbach 2007-07-02 21:05:05 UTC

this is not a dup

please see Comment #1

Comment 9 André Klapper 2007-12-07 16:33:22 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!