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 doesn't work properly
- From: "Anthony C. Zboralski" <frantic@sct.fr>
- Date: Mon, 27 Jul 1998 12:36:52 +0200 (CET)
- Message-id: <Pine.LNX.3.96.980727123409.4473A-100000@red.blood.int>
Package: Xnest Version: 3.3.2.2-4 well xnest doesn't work the way i expect. bash-2.01$ Xnest -ac :2 PEXExtensionInit: Couldn't open default PEX font file Roman_Mfailed to set default font path '/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/' Fatal server error: could not open default font 'fixed' bash-2.01$
--- 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 ---