GNOME Bugzilla – Bug 151024
PLEASE DUPE BUG 158904 [ fm_properties_window_get_type ]
Last modified: 2005-05-02 01:56:44 UTC
Distribution: Fedora Core release 2 (Tettnang) Package: nautilus Severity: normal Version: GNOME2.6. unspecified Gnome-Distributor: Red Hat, Inc Synopsis: .pdf files make system go boom Bugzilla-Product: nautilus Bugzilla-Component: File and Folder Operations Bugzilla-Version: unspecified BugBuddy-GnomeVersion: 2.0 (2.6.0) Description: Description of the crash: Everytime I click on a .pdf file with nautillis the system crashes. Steps to reproduce the crash: 1. click on a file with .pdf extension. 2. close nautilis Expected Results: I don't expect anything unusual to happen when I perform such a task but after I click a .pdf file I no longer see items on my desktop and cannot open some files. How often does this happen? Every single time I open a file with a .pdf extension. Additional Information: pdf sucks 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)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...[Thread debugging using libthread_db enabled] [New Thread -151149408 (LWP 3033)] [New Thread 91114416 (LWP 3130)] [Thread debugging using libthread_db enabled] [New Thread -151149408 (LWP 3033)] [New Thread 91114416 (LWP 3130)] [New Thread 59702192 (LWP 3129)] [New Thread 124877744 (LWP 3096)] [New Thread 78109616 (LWP 3075)] [New Thread 10292144 (LWP 3074)] [New Thread 25123760 (LWP 3050)] (no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...[Thread debugging using libthread_db enabled] [New Thread -151149408 (LWP 3033)] [New Thread 91114416 (LWP 3130)] (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)...0x00a287a2 in _dl_sysinfo_int80 () from /lib/ld-linux.so.2
+ Trace 49606
Thread 1 (Thread -151149408 (LWP 3033))
------- Bug moved to this database by unknown@bugzilla.gnome.org 2004-08-25 09:44 ------- 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 snaps@nyc.rr.com. 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.
According to the stack trace, the crash occurred in the function fm_properties_window_get_type. Did you happen to have properties windows opened ?
*** Bug 151325 has been marked as a duplicate of this bug. ***
*** Bug 152374 has been marked as a duplicate of this bug. ***
*** Bug 157798 has been marked as a duplicate of this bug. ***
Reopening and bumping Version based on duplicates.
*** Bug 157703 has been marked as a duplicate of this bug. ***
*** Bug 159927 has been marked as a duplicate of this bug. ***
*** Bug 160553 has been marked as a duplicate of this bug. ***
Fairly nasty crasher, in both FC and Ubuntu. Marking up priority and marking as a tentative blocker for 2.10.
I am not able to replicate this bug in the latest gnome from CVS HEAD with nautilus version 2.9.2. When I click on the pdf file from nautilus it opens fine (i have to specify the viewer when opening for the first time) and when I close nautilus the bug does not appear. Which application is it using for opening the pdf ? My linux distribution is NLD on which I have installed the latest gnome build.
I too am not able to replicate.. I tried with a pdf file and with a file for which the user (owner of file) does not have read, write and execute permission.. i am using nautilus 2.9.3...
Subodh, Venkatesan: exactly what steps did you each try to reproduce with?
1) I tried opening a .pdf file 2) I also tried opening a file for which i had removed rw permissions (chmod u-rw) I could not trigger any crash. I tried on the HEAD..
Steps I followed were: 1. Tried opening a .pdf file from a nautilus window by double-clicking on it and then closed the nautilus window. 2. Tried opening the .pdf file when the properties window for the file is open and then closed the nautilus window. 3. Changed the permissions of the .pdf file and then tried to open it. The pdf viewer throws the proper error. I also tried the various combinations of the above steps with/without closing the nautilus window but didn't see any crash.
*** Bug 165574 has been marked as a duplicate of this bug. ***
Is there any nautilus extension for displaying properties of pdf files? I think I remember seeing that at some time. That might be what is crashing?
This is the non-debug duplicate of bug 158904. A fix is on both branches. *** This bug has been marked as a duplicate of 158904 ***
Reporter has requested an end to the bugzilla spam; since this has already been marked as a duplicate, we should merely need to change the title to handle this, I think.
*** Bug 167236 has been marked as a duplicate of this bug. ***
*** Bug 168294 has been marked as a duplicate of this bug. ***
*** Bug 170572 has been marked as a duplicate of this bug. ***
Reporter has been removed as externalcc, so nobody has to feel guilty when duping to this bug.
*** Bug 170622 has been marked as a duplicate of this bug. ***
*** Bug 171049 has been marked as a duplicate of this bug. ***
*** Bug 172306 has been marked as a duplicate of this bug. ***
*** Bug 172401 has been marked as a duplicate of this bug. ***
*** Bug 300267 has been marked as a duplicate of this bug. ***
*** Bug 302653 has been marked as a duplicate of this bug. ***