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 304283 - right-clicking for desktop file properties causes nautilus to crash
right-clicking for desktop file properties causes nautilus to crash
Status: RESOLVED DUPLICATE of bug 158904
Product: nautilus
Classification: Core
Component: general
2.8.x
Other other
: Normal normal
: ---
Assigned To: gnome-utils Maintainers
gnome-utils Maintainers
Depends on:
Blocks:
 
 
Reported: 2005-05-15 20:19 UTC by apayan
Modified: 2005-05-15 20:26 UTC
See Also:
GNOME target: ---
GNOME version: 2.7/2.8



Description apayan 2005-05-15 20:19:36 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: right-clicking for desktop file properties causes nautilus to crash
Bugzilla-Product: gnome-utils
Bugzilla-Component: gdict
Bugzilla-Version: 2.8.1
BugBuddy-GnomeVersion: 2.0 (2.8.0)
Description:
Description of the crash:
right-clicking for desktop file properties causes nautilus to crash

Steps to reproduce the crash:
1. Right-click file on desktop
2. Select properties
3. Nautilus crashes

Expected Results:
I should get the properties dialog


How often does this happen?
Everytime

Additional Information:
The file is a .cdr (a type of disc image from OS X). I just wanted to
see the file size. The properties dialog box does pop open, but
immediately after Nautilus crashes. If I can be of anymore help and
you'd like me to try any other configurations, settings, or files you
can email me at apayan!_N_O_SP_@M! @ usc.edu


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 -1209066880 (LWP 23803)]
[New Thread -1223148624 (LWP 23809)]
[Thread debugging using libthread_db enabled]
[New Thread -1209066880 (LWP 23803)]
[New Thread -1223148624 (LWP 23809)]
[Thread debugging using libthread_db enabled]
[New Thread -1209066880 (LWP 23803)]
[New Thread -1223148624 (LWP 23809)]
[New Thread -1222882384 (LWP 23808)]
[New Thread -1222616144 (LWP 23807)]
[New Thread -1221948496 (LWP 23806)]
[New Thread -1221682256 (LWP 23805)]
[New Thread -1211192400 (LWP 23804)]
(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)...0x00c217a2 in _dl_sysinfo_int80 () from /lib/ld-linux.so.2

Thread 7 (Thread -1211192400 (LWP 23804))

  • #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-05-15 20:19 UTC -------


Unknown version 2.8.1 in product gnome-utils.  Setting version to "2.8.x".
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 apayan@usc.edu.

Comment 1 Christian Kirbach 2005-05-15 20:26:55 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 158904 ***