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 160510 - Nautilus crashes while trying to open a folder current user don't have right to open
Nautilus crashes while trying to open a folder current user don't have right ...
Status: RESOLVED DUPLICATE of bug 165938
Product: nautilus
Classification: Core
Component: general
2.9.x
Other other
: Normal normal
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2004-12-05 14:19 UTC by jerome
Modified: 2005-02-02 21:01 UTC
See Also:
GNOME target: ---
GNOME version: 2.9/2.10


Attachments
Screenshot showing the Error dialog when non-accessible folder is clicked in the nautilus window (71.17 KB, image/png)
2004-12-07 06:07 UTC, Subodh Soni
Details

Description jerome 2004-12-05 14:20:13 UTC
Distribution: Debian 3.1
Package: nautilus
Severity: normal
Version: GNOME2.9.2 2.9.1
Gnome-Distributor: Ubuntu
Synopsis: Nautilus crashes while trying to open a folder current user don't have right to open
Bugzilla-Product: nautilus
Bugzilla-Component: general
Bugzilla-Version: 2.9.1
BugBuddy-GnomeVersion: 2.0 (2.8.0)
Description:
Description of the crash:
Nautilus crashes while trying to open a folder current user don't own
and don't have right to open it (for exemple : /root in 700 mode)

Steps to reproduce the crash:
1. chmod 700 /root
2. chown root.root /root
3. open Nautilus as non root user
4. open the left panel (F9)
4. click on /root

Expected Results:
Application crashes

How often does this happen?
every time

Additional Information:
none


Debugging Information:

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)
`system-supplied DSO at 0xffffe000' has disappeared; keeping its
symbols.
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 1091282016 (LWP 8812)]
[New Thread 1102355376 (LWP 8816)]
[Thread debugging using libthread_db enabled]
[New Thread 1091282016 (LWP 8812)]
[New Thread 1102355376 (LWP 8816)]
[New Thread 1102089136 (LWP 8815)]
[New Thread 1101429680 (LWP 8814)]
[New Thread 1101130672 (LWP 8813)]
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()
  • #0 __kernel_vsyscall
  • #1 __waitpid_nocancel
    from /lib/tls/i686/cmov/libpthread.so.0
  • #2 libgnomeui_module_info_get
    from /usr/lib/libgnomeui-2.so.0
  • #3 <signal handler called>
  • #4 nautilus_navigation_window_allow_forward
  • #5 nautilus_navigation_window_allow_forward
  • #6 nautilus_window_close
  • #7 nautilus_directory_add_file_monitors
    from /usr/lib/libnautilus-private.so.2
  • #8 nautilus_async_destroying_file
    from /usr/lib/libnautilus-private.so.2
  • #9 nautilus_directory_async_state_changed
    from /usr/lib/libnautilus-private.so.2
  • #10 nautilus_directory_monitor_add_internal
    from /usr/lib/libnautilus-private.so.2
  • #11 nautilus_directory_stop_monitoring_file_list
    from /usr/lib/libnautilus-private.so.2
  • #12 nautilus_directory_stop_monitoring_file_list
    from /usr/lib/libnautilus-private.so.2
  • #13 nautilus_directory_force_reload_internal
    from /usr/lib/libnautilus-private.so.2
  • #14 nautilus_directory_async_state_changed
    from /usr/lib/libnautilus-private.so.2
  • #15 nautilus_directory_monitor_remove_internal
    from /usr/lib/libnautilus-private.so.2
  • #16 nautilus_vfs_directory_get_type
    from /usr/lib/libnautilus-private.so.2
  • #17 nautilus_directory_file_monitor_remove
    from /usr/lib/libnautilus-private.so.2
  • #18 fm_directory_view_get_emblem_names_to_exclude
  • #19 fm_directory_view_init_view_iface
  • #20 g_cclosure_marshal_VOID__VOID
    from /usr/lib/libgobject-2.0.so.0
  • #21 g_cclosure_new_swap
    from /usr/lib/libgobject-2.0.so.0
  • #22 g_closure_invoke
    from /usr/lib/libgobject-2.0.so.0
  • #23 g_signal_emit_by_name
    from /usr/lib/libgobject-2.0.so.0
  • #24 g_signal_emit_valist
    from /usr/lib/libgobject-2.0.so.0
  • #25 g_signal_emit
    from /usr/lib/libgobject-2.0.so.0
  • #26 gtk_object_destroy
    from /usr/lib/libgtk-x11-2.0.so.0
  • #27 gtk_widget_get_default_direction
    from /usr/lib/libgtk-x11-2.0.so.0
  • #28 ??
  • #29 gtk_widget_get_default_direction
    from /usr/lib/libgtk-x11-2.0.so.0
  • #30 ??
  • #31 ??
  • #32 ??
  • #33 fm_list_view_get_type




------- Bug moved to this database by unknown@bugzilla.gnome.org 2004-12-05 09:20 -------


Unknown version 2.9.1 in product nautilus.  Setting version to "2.9.x".
Unknown platform unknown. Setting to default platform "Other".
Unknown milestone "unknown" in product "nautilus".
   Setting to default milestone for this product, '---'
The original reporter of this bug does not have
   an account here. Reassigning to the person who moved
   it here, unknown@bugzilla.gnome.org.
   Previous reporter was jerome@no-log.org.
Setting to default status "UNCONFIRMED".
Setting qa contact to the default for this product.
   This bug either had no qa contact or an invalid one.

Comment 1 Subodh Soni 2004-12-07 06:05:32 UTC
I am not able to replicate it on nautilus 2.9.2 from CVS HEAD. Attached is the
screenshot that shows the error message I get when I click on the root/ folder
as specified in the steps to reproduce the bug.
Comment 2 Subodh Soni 2004-12-07 06:07:20 UTC
Created attachment 34570 [details]
Screenshot showing the Error dialog when non-accessible folder is clicked in the nautilus window
Comment 3 Sebastien Bacher 2005-02-02 21:01:23 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 165938 ***