Your message dated Mon, 16 Aug 2010 02:29:31 +0200
with message-id <[email protected]>
and subject line Re: Bug#592966: requires xfonts-base to run, but has no
dependancy on it
has caused the Debian Bug report #592966,
regarding xnest - requires xfonts-base to run, but has no
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 this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
592966: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=592966
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: xnest
Version: 2:1.4.2-10.lenny2
Severity: normal
I created a virtual Debian image, during its installation
I unchecked all the "What is this machine to be used as"
boxes in the Debian installer.
I then started Xnest on the host by entering
Xnest -ac :10.0 &
DISPLAY=:10.0 twm &
In the guest machine, I entered
DISPLAY=10.0.0.1:10.0 Xnest -ac :1.0
(10.0.0.1 is the host's virtual network address)
The Xnest process on the guest machine created a window
on the host's Xnest, and after placing with twm,
the guest Xnest crashed with
error opening security policy file /etc/X11/xserver/SecurityPolicy
Could not init font path element /usr/share/fonts/X11/cyrillic, removing from
list!
Could not init font path element /usr/share/fonts/X11/100dpi/:unscaled,
removing from list!
Could not init font path element /usr/share/fonts/X11/75dpi/:unscaled, removing
from list!
Could not init font path element /usr/share/fonts/X11/Type1, removing from list!
Could not init font path element /usr/share/fonts/X11/100dpi, removing from
list!
Could not init font path element /usr/share/fonts/X11/75dpi, removing from list!
Fatal server error:
could not open default font 'fixed'
I'm not sure if this should be a higher priority bug,
but I doubt if many people will try this configuration.
TIA,
Colin S. Miller
-- System Information:
Debian Release: 5.0.3
APT prefers stable
APT policy: (500, 'stable')
Architecture: i386 (i686)
Kernel: Linux 2.6.26-2-686 (SMP w/1 CPU core)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Versions of packages xnest depends on:
ii libc6 2.7-18lenny4 GNU C Library: Shared libraries
ii libdbus-1-3 1.2.1-5+lenny1 simple interprocess messaging syst
ii libfontenc1 1:1.0.4-3 X11 font encoding library
ii libhal1 0.5.11-8 Hardware Abstraction Layer - share
ii libpixman-1-0 0.10.0-2 pixel-manipulation library for X a
ii libx11-6 2:1.1.5-2 X11 client-side library
ii libxau6 1:1.0.3-3 X11 authorisation library
ii libxdmcp6 1:1.0.2-3 X11 Display Manager Control Protoc
ii libxext6 2:1.0.4-1 X11 miscellaneous extension librar
ii libxfont1 1:1.3.3-1 X11 font rasterisation library
ii x11-common 1:7.3+20 X Window System (X.Org) infrastruc
xnest recommends no packages.
xnest suggests no packages.
-- no debconf information
--- End Message ---
--- Begin Message ---
On Sat, Aug 14, 2010 at 16:34:11 +0100, Colin S. Miller wrote:
> Package: xnest
> Version: 2:1.4.2-10.lenny2
> Severity: normal
>
>
> I created a virtual Debian image, during its installation
> I unchecked all the "What is this machine to be used as"
> boxes in the Debian installer.
>
> I then started Xnest on the host by entering
> Xnest -ac :10.0 &
> DISPLAY=:10.0 twm &
>
>
> In the guest machine, I entered
> DISPLAY=10.0.0.1:10.0 Xnest -ac :1.0
>
> (10.0.0.1 is the host's virtual network address)
>
>
> The Xnest process on the guest machine created a window
> on the host's Xnest, and after placing with twm,
> the guest Xnest crashed with
>
>
> error opening security policy file /etc/X11/xserver/SecurityPolicy
> Could not init font path element /usr/share/fonts/X11/cyrillic, removing from
> list!
> Could not init font path element /usr/share/fonts/X11/100dpi/:unscaled,
> removing from list!
> Could not init font path element /usr/share/fonts/X11/75dpi/:unscaled,
> removing from list!
> Could not init font path element /usr/share/fonts/X11/Type1, removing from
> list!
> Could not init font path element /usr/share/fonts/X11/100dpi, removing from
> list!
> Could not init font path element /usr/share/fonts/X11/75dpi, removing from
> list!
>
> Fatal server error:
> could not open default font 'fixed'
>
>
> I'm not sure if this should be a higher priority bug,
> but I doubt if many people will try this configuration.
>
The current version of xnest in testing and unstable has a dependency on
xserver-common, which recommends xfonts-base. That was indeed missing
in lenny. It's not a strict dependency because 1) newer versions of
libXfont have the required fixed and cursor fonts builtin, which lets
the X server start without xfonts-base, and 2) the font path can be set
using the -fp command line switch, to e.g. point at a font server.
Cheers,
Julien
signature.asc
Description: Digital signature
--- End Message ---
