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 170622 - nautilus crashes on permission settings
nautilus crashes on permission settings
Status: RESOLVED DUPLICATE of bug 151024
Product: gnome-utils
Classification: Deprecated
Component: gdict
2.8.x
Other other
: Normal normal
: ---
Assigned To: gnome-utils Maintainers
gnome-utils Maintainers
Depends on:
Blocks:
 
 
Reported: 2005-03-17 00:24 UTC by a.t.cook
Modified: 2005-03-17 01:03 UTC
See Also:
GNOME target: ---
GNOME version: 2.7/2.8



Description a.t.cook 2005-03-17 00:24:27 UTC
Distribution: Fedora Core release 3 (Heidelberg)
Package: gnome-utils
Severity: normal
Version: GNOME2.8.0 2.8.1
Gnome-Distributor: Red Hat, Inc
Synopsis: nautilus crashes on permission settings
Bugzilla-Product: gnome-utils
Bugzilla-Component: gdict
Bugzilla-Version: 2.8.1
BugBuddy-GnomeVersion: 2.0 (2.8.0)
Description:
Description of the crash:
nautilus crashes if the files inside the current folder are not set to
current user

Steps to reproduce the crash:
1. open folder again
2. 
3. 

Expected Results:
crash

How often does this happen?
every time

Additional Information:



Debugging Information:

Backtrace was generated from '/usr/bin/nautilus'

(no debugging symbols found)...Using host libthread_db library
"/lib/tls/libthread_db.so.1".
(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)...[Thread debugging using libthread_db enabled]
[New Thread -151161152 (LWP 8569)]
[New Thread -166724688 (LWP 8575)]
[Thread debugging using libthread_db enabled]
[New Thread -151161152 (LWP 8569)]
[New Thread -166724688 (LWP 8575)]
[Thread debugging using libthread_db enabled]
[New Thread -151161152 (LWP 8569)]
[New Thread -166724688 (LWP 8575)]
[New Thread -164787280 (LWP 8572)]
[New Thread -164521040 (LWP 8571)]
[New Thread -154018896 (LWP 8570)]
(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)...0x0085c7a2 in _dl_sysinfo_int80 () from /lib/ld-linux.so.2

Thread 5 (Thread -154018896 (LWP 8570))

  • #0 _dl_sysinfo_int80
    from /lib/ld-linux.so.2
  • #1 poll
    from /lib/tls/libc.so.6
  • #2 g_main_context_acquire
    from /usr/lib/libglib-2.0.so.0
  • #3 g_main_loop_run
    from /usr/lib/libglib-2.0.so.0
  • #4 link_thread_io_context
    from /usr/lib/libORBit-2.so.0
  • #5 ??
    from /usr/lib/libglib-2.0.so.0
  • #6 ??
  • #7 g_static_private_free
    from /usr/lib/libglib-2.0.so.0



------- Bug moved to this database by unknown@bugzilla.gnome.org 2005-03-16 19:24 -------


Unknown version 2.8.1 in product gnome-utils.  Setting version to "2.8.x".
Unknown platform unknown. Setting to default platform "Other".
Unknown milestone "unknown" in product "gnome-utils".
   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 a.t.cook@herts.ac.uk.
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 Elijah Newren 2005-03-17 01:03:30 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.

Matches the stack trace in bug 168294, which has been marked as a duplicate of
151024.

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