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 468609 - crash in Open Folder: I was changing the permi...
crash in Open Folder: I was changing the permi...
Status: RESOLVED DUPLICATE of bug 485771
Product: nautilus
Classification: Core
Component: general
2.19.x
Other All
: High critical
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2007-08-20 17:50 UTC by fabio.paravento
Modified: 2007-10-19 02:01 UTC
See Also:
GNOME target: ---
GNOME version: 2.19/2.20



Description fabio.paravento 2007-08-20 17:50:11 UTC
Version: 2.19.5

What were you doing when the application crashed?
I was changing the permissions by right-clicking on the folder and then selecting properties but it crashed. I had already changed those permissions in a previous sessions but it did not hold. 


Distribution: Fedora release 7.90 (Rawhide)
Gnome Release: 2.19.5 2007-07-08 (Red Hat, Inc)
BugBuddy Version: 2.18.0

System: Linux 2.6.23-0.61.rc1.git9.fc8 #1 SMP Tue Jul 31 17:14:25 EDT 2007 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: Enforcing
Accessibility: Enabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 473927680 vsize: 473927680 resident: 41742336 share: 23474176 rss: 41742336 rss_rlim: 18446744073709551615
CPU usage: start_time: 1187630806 rtime: 377 utime: 294 stime: 83 cutime:0 cstime: 1 timeout: 0 it_real_value: 0 frequency: 100

Backtrace was generated from '/usr/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 46912700132112 (LWP 3273)]
(no debugging symbols found)
0x00002aaab0b0697f in waitpid () from /lib64/libpthread.so.0

Thread 1 (Thread 46912700132112 (LWP 3273))

  • #0 waitpid
    from /lib64/libpthread.so.0
  • #1 g_cclosure_marshal_VOID__ENUM
    from /usr/lib64/libgnomeui-2.so.0
  • #2 <signal handler called>
  • #3 strcmp
    from /lib64/libc.so.6
  • #4 ??
  • #5 g_closure_invoke
    from /lib64/libgobject-2.0.so.0
  • #6 g_cclosure_marshal_VOID__ENUM
    from /lib64/libgobject-2.0.so.0
  • #7 g_signal_emit_valist
    from /lib64/libgobject-2.0.so.0
  • #8 g_signal_emit
    from /lib64/libgobject-2.0.so.0
  • #9 g_cclosure_marshal_VOID__ENUM
    from /usr/lib64/libgtk-x11-2.0.so.0
  • #10 g_closure_invoke
    from /lib64/libgobject-2.0.so.0
  • #11 g_cclosure_marshal_VOID__ENUM
    from /lib64/libgobject-2.0.so.0
  • #12 g_signal_emit_valist
    from /lib64/libgobject-2.0.so.0
  • #13 g_signal_emit
    from /lib64/libgobject-2.0.so.0
  • #14 gtk_list_store_remove
    from /usr/lib64/libgtk-x11-2.0.so.0
  • #15 gtk_list_store_clear
    from /usr/lib64/libgtk-x11-2.0.so.0
  • #16 ??
  • #17 g_closure_invoke
    from /lib64/libgobject-2.0.so.0
  • #18 g_cclosure_marshal_VOID__ENUM
    from /lib64/libgobject-2.0.so.0
  • #19 g_signal_emit_valist
    from /lib64/libgobject-2.0.so.0
  • #20 g_signal_emit
    from /lib64/libgobject-2.0.so.0
  • #21 nautilus_file_emit_changed
  • #22 nautilus_directory_emit_change_signals
  • #23 nautilus_file_changed
  • #24 ??
  • #25 g_cclosure_marshal_VOID__ENUM
    from /usr/lib64/libgnomevfs-2.so.0
  • #26 g_cclosure_marshal_VOID__ENUM
    from /usr/lib64/libgnomevfs-2.so.0
  • #27 g_main_context_dispatch
    from /lib64/libglib-2.0.so.0
  • #28 g_cclosure_marshal_VOID__ENUM
    from /lib64/libglib-2.0.so.0
  • #29 g_main_loop_run
    from /lib64/libglib-2.0.so.0
  • #30 gtk_main
    from /usr/lib64/libgtk-x11-2.0.so.0
  • #31 main
  • #0 waitpid
    from /lib64/libpthread.so.0


----------- .xsession-errors ---------------------
Window manager warning: Failed to read saved session file /home/fabio/.metacity/sessions/default1.ms: Failed to open file '/home/fabio/.metacity/sessions/default1.ms': No such file or directory
Traceback (most recent call last):
  File "/usr/bin/sealert", line 103, in <module>
    from setroubleshoot.analyze import *
  File "/usr/lib/python2.5/site-packages/setroubleshoot/analyze.py", line 29, in <module>
    from setroubleshoot.avc_audit import *
  File "/usr/lib/python2.5/site-packages/setroubleshoot/avc_audit.py", line 40, in <module>
    from setroubleshoot.signature import AVC, AvcContext
  File "/usr/lib/python2.5/site-packages/setroubleshoot/signature.py", line 74, in <module>
    import libxml2
ImportError: No module named libxml2
** Message: Could not connect to power manager: Could not get owner of name 'org.gnome.PowerManager': no such name
** Message: Could not connect to power manager: Could not get owner of name 'org.gnome.PowerManager': no such name
warning: no loadable sections found in added symbol-file system-supplied DSO at 0x7fff2cdfc000
--------------------------------------------------
Comment 1 André Klapper 2007-09-11 13:59:49 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 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] Please install the following debug packages provided by Fedora: nautilus-debuginfo, glib2-debuginfo, gtk2-debuginfo, pango-debuginfo, gnome-vfs2-debuginfo, libgnome-debuginfo, and libgnomeui-debuginfo.

More details can be found here: http://live.gnome.org/GettingTraces
Comment 2 André Klapper 2007-10-19 02:01:16 UTC
Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but the maintainers need more information to fix the bug. Could you please answer the questions in the other report in order to help the developers?


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