--- Begin Message ---
Package: xvfb
Version: 2:1.1.1-21etch1
xvfb in etch simply doesn't work for me. Whatever X-client I start with
xvfb-run, it cannot connect to the DISPLAY. E.g.
gis-w@trend-cc:~ $ xvfb-run xterm
xterm Xt error: Can't open display: :99
/usr/bin/xvfb-run: line 158: kill: (4889) - Kein passender Prozess gefunden
This happens not only with the default display 99, but also when I explicitly
specify e.g. a lower display number.
xvfb from testing works perfectly, though.
Cheers,
Carsten
--- End Message ---
--- Begin Message ---
On Wed, Feb 6, 2008 at 00:45:38 +0100, Carsten Pfeiffer wrote:
> Am Mittwoch, 6. Februar 2008 schrieb Julien Cristau:
>
> > [pid 31171] write(2, "Could not init font path element"..., 103) = 103
> > [pid 31171] write(2, "\nFatal server error:\n", 21) = 21
> > [pid 31171] write(2, "could not open default font \'fix"..., 35) = 35
> > [pid 31171] write(2, "\n", 1) = 1
> > [pid 31171] unlink("/tmp/.X99-lock") = 0
> > [pid 31171] munmap(0xb7cbd000, 311296) = 0
> > [pid 31171] exit_group(1) = ?
> >
> > There's the likely explanation. Is xfonts-base installed?
>
> Aha, good catch! No, it's not installed. Works perfectly now. Should that
> become a dependency for xvfb, perhaps?
>
Not IMO. As all other X servers, Xvfb should be able to get fonts from
a fontserver instead of the local filesystem, so having fonts installed
isn't a hard dependency. xfonts-base is already Recommended by the xvfb
package in lenny and sid.
Closing this bug, thanks for following up!
Cheers,
Julien
--- End Message ---