GNOME Bugzilla – Bug 80083
Crash on startup in xft
Last modified: 2004-12-22 21:47:04 UTC
Package: nautilus Severity: normal Version: 1.1.13 Synopsis: Crash on startup Bugzilla-Product: nautilus Bugzilla-Component: general BugBuddy-GnomeVersion: 2.0 (1.115.0) Description: Description of Problem: Nautilus crashes after showing the home-dir window, but before showing any files. Steps to reproduce the problem: 1. Start nautilus Actual Results: Crash Expected Results: No crash How often does this happen? Every time 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)... (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)...[New Thread 1024 (LWP 19455)] [New Thread 2049 (LWP 19458)] [New Thread 1026 (LWP 19459)] [New Thread 2051 (LWP 19460)] [New Thread 3076 (LWP 19463)] (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)...0x40a4ea69 in wait4 () from /lib/libc.so.6
+ Trace 21390
Thread 5 (Thread 3076 (LWP 19463))
Thread 4 (Thread 2051 (LWP 19460))
Thread 3 (Thread 1026 (LWP 19459))
Thread 1 (Thread 1024 (LWP 19455))
------- Bug moved to this database by unknown@bugzilla.gnome.org 2002-04-27 19:13 ------- Unknown version 1.1.x in product nautilus. Setting version to the default, "unspecified". Reassigning to the default owner of the component, nautilus-maint@bugzilla.gnome.org.
Looks like something is busted with the Xft configuration.
This may be related: for whatever reason, after a recent apt-get dist-upgrade, loging in with the Gnome-AA session stopped working---it would send me back to the login screen basically instantly. Also, I managed to get nautilus to work for some things: If I run it with --no-desktop and with a directory other than my home dir, it will work fine for a while... I can also sometimes hit stop fast enough for it not to load my home dir, after which I can go on and use it for a while. There are other non-home-directory locations that will crash it, though.
alex: should owen be cc'd on this, then? It looks like it is dying in pango, right? [FWIW this isn't the first report of this- see also bug 78766.] Ben: do you have an XftConfig file installed correctly? Is it possible the dist-upgrade horked your X and/or Xft installs?
This is a crash in PangoFT2. It uses the same configuration as the AA mode, and it seems to crash while reading the config file. I think the configuration file contains something strange. Maybe it shouldn't crash though. Could you attach you XftConfig?
Created attachment 8035 [details] My XftConfig file. I modified it from the dist. version, but not since this bug showed up.
Reopening, then. Owen, is this xftconfig useful to you?
More interesting question is whether it is useful to Alex. (I've cc'ed him directly in case he's still way behind on nautilus-maint mail.)
The crash is repeatable with this XftConfig file at least.
Looks bad. With that config file even gtk-demo crashes when i run it in Xft mode:
+ Trace 21619
Seems we should pass this on to keithp.
I just tried some things: First, I tried incramentally commenting out my XftConfig file. Even after commenting it out entirely, Nautilus would crash. Then I downloaded http://www.keithp.com/~keithp/fonts/XftConfig, which worked perfectly. What's weird is, I just commented out all of *that* file, and it still works. I suspect it has something to do with Xft not re-parsing it's file every time I run Nautilus... If anyone knows how to force Xft to re-read the file, I'd be happy to try to narrow down what's breaking it.
Well, the good news is that there's no way it will crash in XftConfiglex with current XFree86 CVS, or in MinXftConfiglex once Pango has migrated to Xft 2. Neither of those functions exist anymore. This (oddly) leaves me less motivated to find the actual source of the problem, but I'll see about getting a fix applied to the 4.2 branch of XFree86 sometime soonish. Of course, if someone else had a suitable patch it would get done faster ...
That sounds an awful lot like WONTFIX, which I guess is fine with me...
So is this won't fix than???
Owen: I'm reassigning to gtk since this also crashes gtk-demo; based on keith's comment I'm guessing this is wontfix but it is up to you.
*** Bug 100894 has been marked as a duplicate of this bug. ***