[Bug 2066] Re: Unable to load any usable fontset

2007-02-13 Thread Simon Martin
OK. My results. 1.- When I logout/login then ~/.gnome2/share/fonts/fonts.dir is regenerated and contains 0 as before. Behaviour is as before. 2.- xset fp rehash cures the xdvi problem. -- Unable to load any usable fontset https://launchpad.net/bugs/2066 -- ubuntu-bugs mailing list

[Bug 2066] Re: Unable to load any usable fontset

2007-02-13 Thread Sebastien Bacher
That upload fixes the problem: control-center (1:2.17.91-0ubuntu1) feisty; urgency=low . * New upstream version: common: - Compilation fixes - Fixed localedir defines - Use standard installation paths - Use capplet name for G_LOG_DOMAIN - Require GTK+ = 2.10

[Bug 2066] Re: Unable to load any usable fontset

2007-02-13 Thread Sebastien Bacher
** Also affects: libxfont (Ubuntu) Importance: Undecided Status: Unconfirmed -- Unable to load any usable fontset https://launchpad.net/bugs/2066 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2066] Re: Unable to load any usable fontset

2007-02-13 Thread Sebastien Bacher
The libxfont problem is fixed with that upload: libxfont (1:1.2.2-1ubuntu1) feisty; urgency=low . * debian/patches/from_git_accept_empty_font_path.patch: - patch from git,fontfile: accept empty (but valid) font paths (bug #3091) If a path has a valid fonts.dir or fonts.alias, but

[Bug 2066] Re: Unable to load any usable fontset

2007-02-12 Thread Simon Martin
I can confirm this behaviour. I modified /etc/environment to LANG=C, LANGUAGE=C, and things came back to life. I then set it to LANG=en_GB and LANGUAGE=en_GB and it still worked. Now with the default of LANG=en_GB.UTF-8 and LANGUAGE=en_GB:en then I get the font problems. Definitely looks like a

[Bug 2066] Re: Unable to load any usable fontset

2007-02-12 Thread Torsten Spindler
Try the following: When a file ~/.gnome2/share/fonts/fonts.dir exists, move it out of the way (e.g. mv ~/.gnome2/share/fonts/fonts.dir ~/.gnome2-share-fonts-fonts.dir-gone) and see if xdvi works. -- Unable to load any usable fontset https://launchpad.net/bugs/2066 -- ubuntu-bugs mailing list

[Bug 2066] Re: Unable to load any usable fontset

2007-02-12 Thread Simon Martin
Worked for me. I checked the contents of the ~/.gnome2/share/fonts/fonts.dir file and it has a single line consisting of a single 0 in it. -- Unable to load any usable fontset https://launchpad.net/bugs/2066 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com

Re: [Bug 2066] Re: Unable to load any usable fontset

2007-02-12 Thread mattaw
On Mon, 2007-02-12 at 15:31 +, Torsten Spindler wrote: Try the following: When a file ~/.gnome2/share/fonts/fonts.dir exists, move it out of the way (e.g. mv ~/.gnome2/share/fonts/fonts.dir ~/.gnome2-share-fonts-fonts.dir-gone) and see if xdvi works. I get: [EMAIL PROTECTED]:~$ mv

[Bug 2066] Re: Unable to load any usable fontset

2007-02-12 Thread Simon Martin
Ooops. Just checked again. I was using an X-Win session on a remote box, not at the console. I have just checked on the console and it failed. Something to do with XOrg? -- Unable to load any usable fontset https://launchpad.net/bugs/2066 -- ubuntu-bugs mailing list

[Bug 2066] Re: Unable to load any usable fontset

2007-02-12 Thread Torsten Spindler
Forgot to add the following: Please end your session and start a new one. If this does not work, does 'xset fp rehash' work? -- Unable to load any usable fontset https://launchpad.net/bugs/2066 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com

[Bug 2066] Re: Unable to load any usable fontset

2007-02-07 Thread lemming
I experienced similar problems when running sawfish as my window manager. It seems that changing my locale to C fixes the problem. Thus, adding: LANG=C to my .xinitrc allowed sawfish to run just fine. I also changed this in my .bashrc so that other apps such as xdvi, etc. don't run into

[Bug 2066] Re: Unable to load any usable fontset

2007-01-16 Thread Simon Law
This is not xfig's problem, but rather a problem with the xorg package. ** Changed in: xfig (Ubuntu) Sourcepackagename: xfig = xorg Assignee: MOTU = (unassigned) -- Unable to load any usable fontset https://launchpad.net/bugs/2066 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com

[Bug 2066] Re: Unable to load any usable fontset

2007-01-16 Thread Simon Law
Nope, I lied. Here are reproduction steps for Ubuntu Edgy: 1. Install tetex-bin. 2. Log out. 3. At the login screen, go to Options Select Session... Then, select the Failsafe Terminal session and login. 4. Run `xdvi` and click Cancel 5. Note down xdvi's output 6. Run `dbus-launch` and export

[Bug 2066] Re: Unable to load any usable fontset

2007-01-11 Thread Torsten Spindler
The command xset fp rehash seems to fix this problem. -- Unable to load any usable fontset https://launchpad.net/bugs/2066 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2066] Re: Unable to load any usable fontset

2007-01-10 Thread X-Bert
It seems that the bug still isn't fixed. Is it possible to reopen it with the same number? -- Unable to load any usable fontset https://launchpad.net/bugs/2066 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2066] Re: Unable to load any usable fontset

2007-01-10 Thread Adriaan Peeters
reopened ** Changed in: xfig (Ubuntu) Status: Fix Released = Confirmed -- Unable to load any usable fontset https://launchpad.net/bugs/2066 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2066] Re: Unable to load any usable fontset

2007-01-05 Thread Patrick Goetz
I'm still having all the problems described above with Edgy (6.10). -- Unable to load any usable fontset https://launchpad.net/bugs/2066 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs