[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#386377: marked as done (xvfb: Unrecognized option: -fbdir)

Your message dated Fri, 16 Feb 2007 23:04:28 +0100
with message-id <45D62A6C.1030300@ens-lyon.org>
and subject line #374862: xvfb: Xvfb option -fbdir disappear
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 --- 
Package: xvfb
Version: 1:1.0.2-9
Severity: normal


-fbdir is a documented option in the xvfb manpage. It happened to work with earlier versions of the package, but with the cirrent version
my scripts break with:

Unrecognized option: -fbdir


-- System Information:
Debian Release: testing/unstable
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Shell:  /bin/sh linked to /bin/dash
Kernel: Linux 2.6.16.11
Locale: LANG=en_US.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)

Versions of packages xvfb depends on:
ii  libc6                     2.3.5-13       GNU C Library: Shared libraries an
ii  libfontenc1               1:1.0.1-6      X11 font encoding library
ii  libxau6                   6.9.0.dfsg.1-4 X Authentication library
ii  libxdmcp6                 6.9.0.dfsg.1-4 X Display Manager Control Protocol
ii  libxfont1                 1:1.2.0-2      X11 font rasterisation library
ii  zlib1g                    1:1.2.3-11     compression library - runtime

Versions of packages xvfb recommends:
ii  xbase-clients             6.9.0.dfsg.1-4 miscellaneous X clients

-- no debconf information

--- End Message ---
--- Begin Message --- 
Version: 1.1.1-17

I have been able to reproduce with 1.0.2-9, but not with 1.1.1-17. So I
guess it's fixed now, and probably since the first upload of upstream
1.1. Closing.

Brice

--- End Message ---
Reply to: