Your message dated Sat, 12 Aug 2006 21:00:40 +0300 with message-id <20060812180040.GO5396@fooishbar.org> and subject line Now fixed? has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database)
--- Begin Message ---
- To: <submit@bugs.debian.org>
- Subject: xnest requires fonts unless you specify fontpath
- From: "Oskar Liljeblad" <osk@hem.passagen.se>
- Date: Thu, 11 Mar 1999 13:21:44 +0100
- Message-id: <002601be6bb9$dab6fde0$647af482@oskar>
Package: xnest Version: 3.3.2.3a-11 (probably all other versions as well) Xnest has a built-in fontpath which specifies the following places to look for fonts in: /usr/X11R6/lib/X11/fonts/misc/ /usr/X11R6/lib/X11/fonts/Speedo/ /usr/X11R6/lib/X11/fonts/Type1/ /usr/X11R6/lib/X11/fonts/75dpi/ /usr/X11R6/lib/X11/fonts/100dpi/ If one of these directories doesn't exist, or is missing fonts.dir and (probably) fonts.scale files, Xnest won't start. An error is displayed saying that Xnest failed to set the font path and that the 'fixed' font was not found. You can, however, override the default font path by using the -fp option. I don't know how to tackle this problem; but at least the the following packages should be listed as 'recommended' by xnest: xfonts-scalable (Speedo, Type1 directories) xfonts-base (misc directory) xfonts-75dpi (75dpi directory) xfonts-100dpi (100dpi directory) Oskar Liljeblad (osk@hem.passagen.se)
--- End Message ---
--- Begin Message ---
- To: 13417-done@bugs.debian.org
- Subject: Now fixed?
- From: Daniel Stone <daniel@fooishbar.org>
- Date: Sat, 12 Aug 2006 21:00:40 +0300
- Message-id: <20060812180040.GO5396@fooishbar.org>
Hi, The code to deal with this is all in the DIX, which allows initialisation of single font paths to fail on startup. So I claim this bug is now fixed. Cheers, DanielAttachment: signature.asc
Description: Digital signature
--- End Message ---