Distribution: Fedora Core release 3 (Heidelberg)
Package: nautilus
Severity: normal
Version: GNOME2.8.0 unspecified
Gnome-Distributor: Red Hat, Inc
Synopsis: Crash when opening link to a pdf from desktop
Bugzilla-Product: nautilus
Bugzilla-Component: Desktop
Bugzilla-Version: unspecified
BugBuddy-GnomeVersion: 2.0 (2.8.0)
Description:
Description of the crash:
Opened a spatial folder and created a link to a document in this folder.
copied it and pasted it on the desktop and clicked on it there. GGV
popped up and nautilus crashed. This is the same crash in gnome_theme_*
code that has been seen in capplets and other apps earlier. Not sure
what the bugnumber it should be duplicated against is, but there are
duplicates in bugzilla at least.

Steps to reproduce the crash:
1. 
2. 
3. 

Expected Results:


How often does this happen?


Additional Information:



Debugging Information:

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

Using host libthread_db library "/lib/tls/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread -1208129856 (LWP 20366)]
[New Thread 25959344 (LWP 20378)]
[Thread debugging using libthread_db enabled]
[New Thread -1208129856 (LWP 20366)]
[New Thread 25959344 (LWP 20378)]
[New Thread 140774320 (LWP 20377)]
[New Thread 15092656 (LWP 20374)]
[New Thread 3845040 (LWP 20373)]
[New Thread 25693104 (LWP 20367)]
[Thread debugging using libthread_db enabled]
[New Thread -1208129856 (LWP 20366)]
[New Thread 25959344 (LWP 20378)]
0x00b827a2 in ?? () at rtld.c:577 from /lib/ld-linux.so.2
577	relocate_doit (void *a)

+ Trace 54408

    argDescrip = 0x0}, {longName = 0x0, shortName = 0 '\0', argInfo = 0,

    arg = 0x0, val = 0, descrip = 0x0, argDescrip = 0x0}}




------- Bug moved to this database by unknown@bugzilla.gnome.org 2005-01-11 18:23 -------


Unknown platform unknown. Setting to default platform "Other".
Unknown milestone "unknown" in product "nautilus".
   Setting to default milestone for this product, '---'
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.