GNOME Bugzilla – Bug 128067
Crashing when trying to open window
Last modified: 2005-08-19 22:36:48 UTC
Distribution: Slackware Slackware 9.1.0 Package: nautilus Severity: normal Version: GNOME2.4.0 2.4.0 Gnome-Distributor: GNOME.Org Synopsis: Crashing when trying to open window Bugzilla-Product: nautilus Bugzilla-Component: general Bugzilla-Version: 2.4.0 BugBuddy-GnomeVersion: 2.0 (2.4.0.1) Description: Description of the crash: When click on the home desktop icon Nautilus crashes 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' (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)...[New Thread 16384 (LWP 774)] [New Thread 32769 (LWP 777)] [New Thread 16386 (LWP 778)] [New Thread 32771 (LWP 779)] [New Thread 49156 (LWP 780)] [New Thread 65541 (LWP 781)] [New Thread 81926 (LWP 782)] 0x40b6960c in waitpid () from /lib/libpthread.so.0
+ Trace 42127
Thread 1 (Thread 16384 (LWP 774))
------- Bug moved to this database by unknown@bugzilla.gnome.org 2003-11-27 12:01 ------- Unknown version 2.4.0 in product nautilus. Setting version to the default, "unspecified". The original reporter (fandonov@iinf.bas.bg) of this bug does not have an account here. Reassigning to the exporter, unknown@bugzilla.gnome.org. Reassigning to the default owner of the component, nautilus-maint@bugzilla.gnome.org.
*** Bug 127122 has been marked as a duplicate of this bug. ***
Marking as new, setting version->2.4.x, priority->high, severity->critical. Adding GNOMEVER2.4, STACKTRACE keywords.
*** Bug 128092 has been marked as a duplicate of this bug. ***
*** Bug 128224 has been marked as a duplicate of this bug. ***
bug 129217 might be a duplicate of this.
*** Bug 129217 has been marked as a duplicate of this bug. ***
*** Bug 129914 has been marked as a duplicate of this bug. ***
*** Bug 129993 has been marked as a duplicate of this bug. ***
*** Bug 129992 has been marked as a duplicate of this bug. ***
Yowzas. Adding some keywords.
*** Bug 130394 has been marked as a duplicate of this bug. ***
*** Bug 131723 has been marked as a duplicate of this bug. ***
*** Bug 132651 has been marked as a duplicate of this bug. ***
*** Bug 132733 has been marked as a duplicate of this bug. ***
*** Bug 133083 has been marked as a duplicate of this bug. ***
I can't reproduce this on nautilus 2.4.1 or 2.5.X, if anybody has a set of reproduceable steps for this bug (or any extra information as to what may be causing it) please post them here. According to some of the reports it happens most frequently when viewing a pic (.jpg) inside nautilus and hitting the "Up" button to go up a directory. Louis: why'd you add GNOMEVER2.5 to the keywords? All of the reports so far have been from 2.4. I'm bumping the Version Details up to -> 2.4.1 which is the highest version that's been reported on so far.
The steps to reproduce listed in bug 120911 might be helpful, as that is probably related to this bug according to Martin.
In my case, I get an endless loop of this when I click on a desktop icon (my home folder in RedHat 9): Nautilus begins to open; I get a crash dialog including "Segmentation fault"; I dismiss the error dialog; my desktop disappears (icons, Gnome panel); desktop reappears; a new nautilus window appears; I get a creash dialog including "Segmentation fault"; .... I have to exit XFree and then dismiss the error dialog to regain control of the PC (a laptop starting at initlevel 3). One thing I have noticed: I have no sound after this happens. I'd be glad to provide any additional information I can that you'd like. Please be specific as to what you want - I am good, but not an expert.
Bill: could you open a new bug report (unless you already did and it was marked a duplicate of this bug - if that's the case then say so and tell us the bug number)? We can't be sure your problem is related to this bug unless we see a stacktrace. If you follow the "report this bug" wizard in the "application crash" dialog which results when the application crashes, the stacktrace is automatically included with the rest of the report.
Its possible that this eel patch (in 2.5.6) fixed this: 2004-01-27 Alexander Larsson <alexl@redhat.com> * eel/eel-canvas-util.c: (eel_canvas_get_miter_points): * eel/eel-canvas.c: (emit_event): Update from foocanvas. May fix nautilus event crash.
To gatto: I have submitted a bug report. It's been assigned the number 134079. If you'd like anything else, let me know. One thought occurred to me: does Nautilus require any special files in /dev/? I ask because at some point recently while using a new external USB floppy drive/digital media reader, my symbolic link /dev/cdrom was erased. My Nautilus problems started shortly after this. This got me wondering. Thanks! for your help and time.
Given that Alex thinks that this is fixed, and we have no 2.5 reports, I'm tentatively closing; if we see new reports in 2.5/2.6 we should definitely reopen.
*** Bug 134379 has been marked as a duplicate of this bug. ***
*** Bug 135749 has been marked as a duplicate of this bug. ***
*** Bug 136504 has been marked as a duplicate of this bug. ***
*** Bug 136824 has been marked as a duplicate of this bug. ***
*** Bug 137205 has been marked as a duplicate of this bug. ***
*** Bug 138879 has been marked as a duplicate of this bug. ***
I know this bug number is closed, but I am posting this in case you want to see if you can reproduce my crash, and since people are still reporting this, maybe this will work for them. The method described here reliably reproduces the crash for me on my laptop. I am not requesting that the bug be reopened - I've fixed my problem. I'm sending this just in case anyone wants to know. I'm enclosing two files, local.conf.000: <?xml version="1.0"?> <!DOCTYPE fontconfig SYSTEM "fonts.dtd"> <!-- /etc/fonts.conf file to configure system font access --> <fontconfig> <!-- Enable sub-pixel rendering --> <match target="font"> <test qual="all" name="rgba"> <const>unknown</const> </test> <edit name="rgba" mode="assign"><const>rgb</const></edit> </match> </fontconfig> and local.conf.001: <?xml version="1.0"?> <!DOCTYPE fontconfig SYSTEM "fonts.dtd"> <!-- /etc/fonts.conf file to configure system font access --> <fontconfig> <!-- Enable sub-pixel rendering --> <match target="font"> <edit name="rgba" mode="assign"> <const>rgb</const></edit> </match> </fontconfig> They are sample local.conf files meant to be used with the Xft font system. My system (stock RedHat 9, updated with all official RedHat errata) puts its Xft configuration files in /etc/fonts/. At the suggestion of a magazine article (Linux Magazine, February 2004, "Guru Guidance," Roderick W. Smith, pp 38-40.), I tried enabling an Xft feature called sub-pixel rendering. In doing so, I looked in my RH stock fonts.conf file and found the snippet which I copied into local.conf.000. When I rename it to local.conf, place it in the Xft configuration directory, and restart Xft, my Nautilus crashes, as described earlier, but only when A) trying to see the contents of a folder, and B) when "Show text in icons" is enabled under Edit | Preferences | Preview. The specific part of local.conf.000 that causes the problem is the <test...> ... </test> part. If I remove it from local.conf, as I've done in local.conf.001, Nautilus does not crash at all even with the "Show text in icons" enabled. Some related discoveries: if local.conf.000 is my local.conf, Nautilus will show a directory's contents as long as "Show text in icons" is disabled. However, if an item in the directory is right-clicked, and Properties is chosen, then a crash results. But I can dismiss the crash dialog, and Nautilus will restart just fine. The crash occurs only when I try to look at the properties of the item. As a result, I have left local.conf.001 as my local.conf, have enabled "Show text in icons," and have not upgraded my Nautilus, and Nautilus works fine for me. [Update since originally posted: Apparently, stock RH 9 ignores the local.conf file completely. Sib-pixel rendering is controlled via the "Font Preferences" application found in the Preferences menu (or by running "gnome-font-properties" from a terminal).]
*** Bug 139508 has been marked as a duplicate of this bug. ***
*** Bug 139568 has been marked as a duplicate of this bug. ***
*** Bug 140170 has been marked as a duplicate of this bug. ***
*** Bug 140197 has been marked as a duplicate of this bug. ***
*** Bug 140480 has been marked as a duplicate of this bug. ***
*** Bug 142083 has been marked as a duplicate of this bug. ***
*** Bug 145913 has been marked as a duplicate of this bug. ***
*** Bug 146404 has been marked as a duplicate of this bug. ***
*** Bug 146599 has been marked as a duplicate of this bug. ***
*** Bug 157063 has been marked as a duplicate of this bug. ***
*** Bug 302647 has been marked as a duplicate of this bug. ***
*** Bug 311236 has been marked as a duplicate of this bug. ***
*** Bug 313858 has been marked as a duplicate of this bug. ***