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

Bug#782090: xserver-xspice: Xspice broken due to missing spiceqxl driver



Package: xserver-xspice
Version: 0.0.17-2+b1
Severity: grave
Justification: renders package unusable

Dear Maintainer,

Running Xspice fails with an error indicating that the spiceqxl driver is missing.

To test this, do the following:

$ sudo cp /usr/share/doc/xserver-xspice/spiceqxl.xorg.conf.example /etc/X11/spiceqxl.xorg.conf
$ Xspice --disable-ticketing --port 5903 :3.0

In the Xorg.3.0.log file you will find:

[452982.994] (II) LoadModule: "spiceqxl"
[452982.994] (WW) Warning, couldn't open module spiceqxl
[452982.994] (II) UnloadModule: "spiceqxl"
[452982.994] (II) Unloading spiceqxl
[452982.994] (EE) Failed to load module "spiceqxl" (module does not exist, 0)

In Debian 7.0 the spiceqxl driver used to be shipped as part of the xserver-xorg-video-qxl package which was probably wrong as this driver seems to only be needed for Xspice. But in Debian Testing no package ships this file which is worse.

Compiling the driver by hand and placing it in /usr/lib/xorg/modules/drivers/spiceqxl_drv.so fixes this and makes Xspice usable.

It would also be nice if copying spiceqxl.xorg.conf.example into place manually was not necessary. After all no such step is needed to use vncserver.

-- System Information:
Debian Release: 8.0
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.16.0-4-amd64 (SMP w/8 CPU cores)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages xserver-xspice depends on:
ii  libpython2.7-stdlib [python-argparse]  2.7.9-2
ii  python                                 2.7.9-1
ii  xserver-xorg                           1:7.7+7
ii  xserver-xorg-video-qxl                 0.1.1-2+b1

xserver-xspice recommends no packages.

xserver-xspice suggests no packages.

-- no debconf information


Reply to: