Bug#814327: xserver-xorg-video-intel: No text when export X display from some java applicattions

[Julien Cristau]

On Wed, Feb 10, 2016 at 13:39:17 +0100, Jose Legido wrote:

> Package: xserver-xorg-video-intel
> Version: 2:2.99.917+git20160127-1+b1
> Severity: normal
> 
> Description:
> When export X Display from other machine and run java app, no text in screen. 
> With jessie works fine, with bpo gets strange symbols, with git version no 
> text. I can upload screenshots
> Reproduce:
> ssh -X remote_machine
> java -jar wls1036_generic.jar
> 
Please report this upstream following the instructions at
https://01.org/linuxgraphics/documentation/how-report-bugs and let us
know the bug number for tracking.

Cheers,
Julien

Bug#814394: xserver-xorg-legacy: Fails to start xserver after upgrade to 1.18.1

[Julien Cristau]

Control: tag -1 moreinfo

On Thu, Feb 11, 2016 at 07:58:11 +0100, Robert Luberda wrote:

> Package: xserver-xorg-legacy
> Version: 2:1.18.1-1
> Severity: serious
> Justification: makes the package unusable
> 
> 
> startx does not longer work after upgrade; `grep EE Xorg.log' shows:
> 
>[  1463.840] (EE) systemd-logind: failed to get session: The name 
> org.freedesktop.login1 was not provided by any .service files

X requires logind.  Please provide more details about your setup.

Cheers,
Julien

Processed: Re: Bug#814394: xserver-xorg-legacy: Fails to start xserver after upgrade to 1.18.1

[Debian Bug Tracking System]

Processing control commands:

> tag -1 moreinfo
Bug #814394 [xserver-xorg-legacy] xserver-xorg-legacy: Fails to start xserver 
after upgrade to 1.18.1
Added tag(s) moreinfo.

-- 
814394: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=814394
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#814607: xvfb-run crashes with "Floating point exception" when trying to run qt5 example programs

[Danny Edel]

Package: xvfb
Version: 2:1.18.1-1
Severity: important
Control: fixed -1 2:1.18.0-3

Dear maintainer,

after running the testsuite from my package failed with the xvfb version
currently in sid, I found that the same problem also happens with the qt5
examples, so it may be a bug in the new xvfb version.

I am assuming this affects any application with a Qt5 gui component, so I
believe this qualifies as "important".

I hope I set the pseudo-headers above correctly to "The version in
stretch is not affected, but sid is", please correct it if I did it
wrong.

--- How to reproduce ---

1. install xvfb xauth qtbase5-examples, all from sid
2. run xvfb-run -a 
/usr/lib/x86_64-linux-gnu/qt5/examples/gui/analogclock/analogclock

Result: Immediately outputs "Floating point exception" and dies

--- Known Workaround ---

3. Add stretch to sources.list
4. apt install xvfb/stretch
5. repeat above xvfb-run command

Result:  Lots of warnings about the painter not being active, but no
"floating point exception" like with the sid version.  Program seems to
run, and has to be CTRL-C'd to quit.
(Also, with the xvfb version in stretch, my test suite passes, so it
seems to be operating normally.)


Thank you for maintaining xvfb,

- Danny

Processed: xvfb-run crashes with "Floating point exception" when trying to run qt5 example programs

[Debian Bug Tracking System]

Processing control commands:

> fixed -1 2:1.18.0-3
Bug #814607 [xvfb] xvfb-run crashes with "Floating point exception" when trying 
to run qt5 example programs
Marked as fixed in versions xorg-server/2:1.18.0-3.

-- 
814607: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=814607
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#814631: xserver-xorg-video-siliconmotion: FTBFS: src/smi.h:224:5: error: unknown type name 'IOADDRESS'

[Andreas Beckmann]

Source: xserver-xorg-video-siliconmotion
Version: 1:1.7.8-1
Severity: serious

Hi,

xserver-xorg-video-siliconmotion FTBFS in sid/amd64 (and probably other
architectures as well), might be incompatible with recent Xorg Xserver:

[...]
   dh_auto_build -O--builddirectory=build/
make -j1
make[1]: Entering directory 
'/build/xserver-xorg-video-siliconmotion-1.7.7/build'
make  all-recursive
make[2]: Entering directory 
'/build/xserver-xorg-video-siliconmotion-1.7.7/build'
Making all in src
make[3]: Entering directory 
'/build/xserver-xorg-video-siliconmotion-1.7.7/build/src'
/bin/bash ../libtool  --tag=CC   --mode=compile gcc -DHAVE_CONFIG_H -I. 
-I../../src -I..-fvisibility=hidden -I/usr/include/pixman-1 
-I/usr/include/libdrm -I/usr/include/xorg -I/usr/include/X11/dri -Wall 
-Wpointer-arith -Wmissing-declarations -Wformat=2 -Wstrict-prototypes 
-Wmissing-prototypes -Wnested-externs -Wbad-function-cast 
-Wold-style-definition -Wdeclaration-after-statement -Wunused -Wuninitialized 
-Wshadow -Wmissing-noreturn -Wmissing-format-attribute -Wredundant-decls 
-Wlogical-op -Werror=implicit -Werror=nonnull -Werror=init-self -Werror=main 
-Werror=missing-braces -Werror=sequence-point -Werror=return-type 
-Werror=trigraphs -Werror=array-bounds -Werror=write-strings -Werror=address 
-Werror=int-to-pointer-cast -Werror=pointer-to-int-cast -fno-strict-aliasing  
-g -O2 -c -o smi_501.lo ../../src/smi_501.c
libtool: compile:  gcc -DHAVE_CONFIG_H -I. -I../../src -I.. -fvisibility=hidden 
-I/usr/include/pixman-1 -I/usr/include/libdrm -I/usr/include/xorg 
-I/usr/include/X11/dri -Wall -Wpointer-arith -Wmissing-declarations -Wformat=2 
-Wstrict-prototypes -Wmissing-prototypes -Wnested-externs -Wbad-function-cast 
-Wold-style-definition -Wdeclaration-after-statement -Wunused -Wuninitialized 
-Wshadow -Wmissing-noreturn -Wmissing-format-attribute -Wredundant-decls 
-Wlogical-op -Werror=implicit -Werror=nonnull -Werror=init-self -Werror=main 
-Werror=missing-braces -Werror=sequence-point -Werror=return-type 
-Werror=trigraphs -Werror=array-bounds -Werror=write-strings -Werror=address 
-Werror=int-to-pointer-cast -Werror=pointer-to-int-cast -fno-strict-aliasing -g 
-O2 -c ../../src/smi_501.c  -fPIC -DPIC -o .libs/smi_501.o
In file included from ../../src/smi.h:40:0,
 from ../../src/smi_501.c:33:
/usr/include/xorg/xf86PciInfo.h:50:2: warning: #warning "xf86PciInfo.h is 
deprecated.  For greater compatibility, drivers should include necessary PCI 
IDs locally rather than relying on this file from xorg-server." [-Wcpp]
 #warning "xf86PciInfo.h is deprecated.  For greater compatibility, drivers 
should include necessary PCI IDs locally rather than relying on this file from 
xorg-server."
  ^
In file included from ../../src/smi_501.c:33:0:
../../src/smi.h:224:5: error: unknown type name 'IOADDRESS'
 IOADDRESS  PIOBase; /* Base of I/O ports */
 ^
Makefile:521: recipe for target 'smi_501.lo' failed
make[3]: *** [smi_501.lo] Error 1
make[3]: Leaving directory 
'/build/xserver-xorg-video-siliconmotion-1.7.7/build/src'
Makefile:444: recipe for target 'all-recursive' failed
make[2]: *** [all-recursive] Error 1
make[2]: Leaving directory '/build/xserver-xorg-video-siliconmotion-1.7.7/build'
Makefile:376: recipe for target 'all' failed
make[1]: *** [all] Error 2
make[1]: Leaving directory '/build/xserver-xorg-video-siliconmotion-1.7.7/build'
dh_auto_build: make -j1 returned exit code 2
debian/rules:17: recipe for target 'build' failed
make: *** [build] Error 2
dpkg-buildpackage: error: debian/rules build gave error exit status 2


Andreas

Processed: bug 729337 is forwarded to https://bugs.freedesktop.org/show_bug.cgi?id=92351

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> forwarded 729337 https://bugs.freedesktop.org/show_bug.cgi?id=92351
Bug #729337 [src:xorg-server] xorg-server: FTBFS: preprocessor macro R_SP 
conflict with glibc headers
Set Bug forwarded-to-address to 
'https://bugs.freedesktop.org/show_bug.cgi?id=92351'.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
729337: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=729337
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#754392: weston: segfault on exit when cms-colord.so is loaded

[Hector Oron]

On Tue, Sep 16, 2014 at 01:10:08PM +0200, Laurent Bigonville wrote:
> Package: weston
> Version: 1.5.93-1.1
> Followup-For: Bug #754392

> Still crashing for me with 1.5.93-1.1

Upstream has a commit for this one:
  2611ebd316056cdd85d75e848813d438cffbf507

which should be available since 1.8.91 release.

Do you still experience this issue with 1.9.0 in Debian?

Regards,
-- 
  Hector Oron


signature.asc
Description: PGP signature

Processed (with 1 error): merging 754570 804865

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> merge 754570 804865
Bug #754570 [weston] weston: please add debug symbols package
Unable to merge bugs because:
package of #804865 is 'src:weston' not 'weston'
Failed to merge 754570: Did not alter merged bugs.

> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
754570: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=754570
804865: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=804865
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#814394: xserver-xorg-legacy: Fails to start xserver after upgrade to 1.18.1

[Scott Mcdermott]

Julien Cristau on 2016/02/13 +0100 @11:30:30:
> > startx does not longer work after upgrade; `grep EE
> > Xorg.log' shows:
> > 
> >[  1463.840] (EE) systemd-logind: failed to get
> >session: The name org.freedesktop.login1 was not
> >provided by any .service files
> 
> X requires logind ...

It's not supposed to, when using the X wrapper and
needs_root_rights=yes.  There used to be an upstream patch that
even allowed X to start without this, and skip the ioperm check
(it's not actually needed with KMS), which Debian dropped,
because I guess they want to require everyone to use systemd.

However, even with needs_root_rights, startup broke for me
recently as well, I had to install systemd-logind temporarily
until I can switch to a distro which doesn't force me to run
systemd stuff.

Even with systemd-logind installed, you still have to invoke it
on the same tty you run X on, even with needs_root_rights=yes, it
won't change the perms for you.  This, too, worked fine for me up
until a month or so ago.

I think the solution is to just use a distro which does not
require systemd, such as Gentoo.  Debian's X maintainers do not
appear to be interested in making X work without systemd, as it
has for the last 30 years or so...

Bug#771796: weston: Weston fails with Intel GM45

[Hector Oron]

Hello,

On Tue, Dec 02, 2014 at 09:11:02AM -0500, Anthony Carrico wrote:
> Subject: weston: Weston fails with Intel GM45
> Package: weston
> Version: 1.6.0-2+b1
> Severity: normal
> 
> Dear Maintainer,
> 
> I decided to try Weston. It is just an experiment to see how things are
> coming along. It failed on this
> machine with graphics hardware, but I was able to run it successfully
> with the pixman renderer. I was also able to run successfully with the
> graphics hardware on another machine.
> 
> Here is my graphics card:
> 
> $ glxinfo  | grep 'renderer string'
> OpenGL renderer string: Mesa DRI Mobile Intel® GM45 Express Chipset
> 
> I will paste two runs, the first fails, the second succeeds:

Could you please try latest weston package release from experimental?
Can you reproduce such issue? If so, would you be willing to bring this 
upstream at 
https://bugs.freedesktop.org/enter_bug.cgi?product=Wayland=weston

Best Regards,
-- 
  Hector Oron


signature.asc
Description: PGP signature

Bug#758980: marked as done (With libgl1-mesa-swx11 installed, weston from Debian shows only a black screen)

[Debian Bug Tracking System]

Your message dated Sun, 14 Feb 2016 01:05:05 +0100
with message-id <20160214000505.ga27...@polynomio.collabora.co.uk>
and subject line Re: Bug#758980: With libgl1-mesa-swx11 installed, weston from 
Debian shows only a black screen
has caused the Debian Bug report #758980,
regarding With libgl1-mesa-swx11 installed, weston from Debian shows only a 
black screen
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 ow...@bugs.debian.org
immediately.)


-- 
758980: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=758980
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: weston
Version: 1.5.0-2
Severity: normal

See https://bugs.freedesktop.org/show_bug.cgi?id=82748 for context. I
was trying to debug why Weston only shows a black screen on my machine.
Turns out I had libgl1-mesa-swx11 installed for some reason, and that
breaks all the weston apps because they are compiled with
--with-cairo=gl in Debian — see also especially
https://bugs.freedesktop.org/show_bug.cgi?id=82748#c15

I think it’d be good if we either stop using --with-cairo=gl or add a
dependency to Weston that will ensure that a proper libGL.so is
present on the system.

What do you think?

-- System Information:
Debian Release: jessie/sid
  APT prefers testing
  APT policy: (990, 'testing'), (600, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.14-2-amd64 (SMP w/2 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages weston depends on:
ii  adduser 3.113+nmu3
ii  libc6   2.19-7
ii  libcairo2   1.12.16-2
ii  libcolord2  1.2.1-1
ii  libdbus-1-3 1.8.6-1
ii  libdrm2 2.4.56-1
ii  libegl1-mesa10.2.5-1
ii  libegl1-mesa-drivers10.2.5-1
ii  libgbm1 10.2.5-1
ii  libgl1-mesa-glx [libgl1]10.2.5-1
ii  libgles2-mesa   10.2.5-1
ii  libglib2.0-02.40.0-4
ii  libglu1-mesa [libglu1]  9.0.0-2
ii  libinput0   0.2.0-2
ii  libjpeg88d1-1
ii  liblcms2-2  2.6-3
ii  libmtdev1   1.1.5-1
ii  libpam0g1.1.8-3
ii  libpango-1.0-0  1.36.3-1
ii  libpangocairo-1.0-0 1.36.3-1
ii  libpixman-1-0   0.32.6-1
ii  libpng12-0  1.2.50-2
ii  libsystemd-login0   208-6
ii  libudev1208-6
ii  libwayland-client0  1.5.0-1
ii  libwayland-cursor0  1.5.0-1
ii  libwayland-egl1-mesa [libwayland-egl1]  10.2.5-1
ii  libwayland-server0  1.5.0-1
ii  libx11-62:1.6.2-2
ii  libx11-xcb1 2:1.6.2-2
ii  libxcb-composite0   1.10-3
ii  libxcb-render0  1.10-3
ii  libxcb-shape0   1.10-3
ii  libxcb-shm0 1.10-3
ii  libxcb-xfixes0  1.10-3
ii  libxcb-xkb1 1.10-3
ii  libxcb1 1.10-3
ii  libxcursor1 1:1.1.14-1
ii  libxkbcommon0   0.4.1-2

Versions of packages weston recommends:
ii  libgl1-mesa-dri  10.2.5-1

weston suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Hello,

On Sat, Aug 23, 2014 at 12:16:46AM +0200, Michael Stapelberg wrote:
> Package: weston
> Version: 1.5.0-2
> Severity: normal
> 
> See https://bugs.freedesktop.org/show_bug.cgi?id=82748 for context. I
> was trying to debug why Weston only shows a black screen on my machine.
> Turns out I had libgl1-mesa-swx11 installed for some reason, and that
> breaks all the weston apps because they are compiled with
> --with-cairo=gl in Debian — see also especially
> https://bugs.freedesktop.org/show_bug.cgi?id=82748#c15
> 
> I think it’d be good if we either stop using --with-cairo=gl or add a
> dependency to Weston that will ensure that a proper libGL.so is
> present on the system.
> 
> What do you think?

Weston in Debian has switched the configuration option to:
  --with-cairo=image.

I assume this issue is no longer present, therefore 

Processed: severity of 785339 is normal

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> severity 785339 normal
Bug #785339 [weston] weston: running weston blanks screen, and makes system 
unresponsive when running i386 through vmware player
Severity set to 'normal' from 'important'
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
785339: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=785339
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#785339: weston: running weston blanks screen, and makes system unresponsive when running i386 through vmware player

[Hector Oron]

On Thu, May 14, 2015 at 07:21:51PM -0400, jsmith wrote:
> Package: weston
> Version: 1.6.0-2+b1
> Severity: important
> 
> Dear Maintainer,
> 
> *** Reporter, please consider answering these questions, where appropriate ***
> 
>* What led up to the situation?
>* What exactly did you do (or not do) that was effective (or
>  ineffective)?
>* What was the outcome of this action?
>* What outcome did you expect instead?

Could you please provide more information? 

Regards
-- 
  Hector Oron


signature.asc
Description: PGP signature

Bug#785338: fatal: environment variable XDG_RUNTIME_DIR is not set

[Hector Oron]

On Wed, May 13, 2015 at 12:56:25PM -0400, jsmith wrote:
> Package: weston
> Version: 1.6.0-2+b1

Weston is not responsible to setup XDG_RUNTIME_DIR.
You should be able to set it up in your environment if nothing sets it up for 
you.

Regards,
-- 
  Hector Oron


signature.asc
Description: PGP signature

Processed: tagging 785338

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tags 785338 + wontfix
Bug #785338 [weston] fatal: environment variable XDG_RUNTIME_DIR is not set
Added tag(s) wontfix.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
785338: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=785338
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: severity of 785338 is normal

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> severity 785338 normal
Bug #785338 [weston] fatal: environment variable XDG_RUNTIME_DIR is not set
Severity set to 'normal' from 'important'
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
785338: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=785338
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: tagging 799325

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tags 799325 + confirmed
Bug #799325 [weston] weston: won't start despite having an active logind session
Added tag(s) confirmed.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
799325: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=799325
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: tagging 785339

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tags 785339 + moreinfo
Bug #785339 [weston] weston: running weston blanks screen, and makes system 
unresponsive when running i386 through vmware player
Added tag(s) moreinfo.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
785339: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=785339
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#814682: Updated OpenChrome driver available

[Jeffrey Walton]

Package: xserver-xorg-video-openchrome
Version: 1:0.3.3-2

The current The OpenChrome provided in Debian causes an Xserver crash
on VIA P4M900 chipset. Though its a less popular chipset, its still
used in production for lower end systems, like Netbooks and POS
systems.

The OpenChrome driver is provided in xserver-xorg-video-openchrome. An
updated version of the OpenChrome driver is available from the
freedesktop.org folks, but it is not available in Unstable. The driver
is installed at /usr/lib/xorg/modules/drivers/openchrome_drv.so.

For the freedesktop.org announcement and instruction for obtaining the
updated driver, see "Getting ready to release OpenChrome Version
0.3.4", 
https://lists.freedesktop.org/archives/openchrome-users/2016-February/007234.html.

Related freedesktop.org and downstream bugs due to the driver:

* "Unknown Card-Ids (3371|1019|2125), Chipset: P4M900/VN896/CN896 [and
Xserver crash]", http://bugs.freedesktop.org/show_bug.cgi?id=94130
* "Light Display Manager fails to load [due to Xserver crash]",
http://bugs.launchpad.net/lightdm/+bug/1540774

Also see the following on the debian-x mailing list:

* "Freedesktop and OpenChrome Version 0.3.4",
http://lists.debian.org/debian-x/2016/02/msg00114.html



debian-unstable:/# apt-cache show xserver-xorg-video-openchrome
Package: xserver-xorg-video-openchrome
Version: 1:0.3.3-2
Installed-Size: 546
Maintainer: Debian X Strike Force 
Architecture: amd64
Provides: xorg-driver-video
Depends: libc6 (>= 2.14), libdrm2 (>= 2.3.1), libx11-6 (>=
2:1.4.99.1), libxext6, libxv1, libxvmc1, xorg-video-abi-20,
xserver-xorg-core (>= 2:1.17.99.902)
Description-en: X.Org X server -- VIA display driver
 OpenChrome is a project for the development of free and open-source drivers
 for the VIA UniChrome video chipsets.
 .
 Originally called the 'snapshot' release, since it was a snapshot of an
 experimental branch of the unichrome cvs code, this is a continued development
 of the open source unichrome driver (from http://unichrome.sf.net) which
 also incorporates support for the unichrome-pro chipsets.
 .
 Support for hardware acceleration (XvMC) for all chipsets has subsequently
 been ripped out of the unichrome.sf.net driver. Therefore your only option if
 you wish to make use of the acceleration features of your VIA chip with free
 and open-source drivers is to use this version of the driver.
Description-md5: 11d4a7275218ad33ccc6479463963d83
Homepage: https://www.freedesktop.org/wiki/Openchrome/
Tag: hardware::video, implemented-in::c, role::plugin, use::driver
Section: x11
Priority: optional
Filename: 
pool/main/x/xserver-xorg-video-openchrome/xserver-xorg-video-openchrome_0.3.3-2_amd64.deb
Size: 199654
MD5sum: ff4710469045b8e878164c3f204557fe
SHA1: d142e843e64059da6581c1c0615eba5046c31cb8
SHA256: 96a60c621021a2f3924e371c7be395eb274bb9725362cd5539fe74b61d3be0cf

Bug#814313: xorg-server: Using systemd and startx, input does not work anymore

[Kei Hibino]

Package: src:xorg-server
Followup-For: Bug #814313

Dear Maintainer,

I was affected with this bug, the same version 2:1.18.1-1.
Input did not work anymore too.

To recover this, I installed downgraded binary packages of xserver (provided in 
jessie, 2:1.16.4-1) which works fine.

I'm not using systemd-sysv, but using sysvinit-core.
I'm not using X login manager, but using startx with xserver-xorg-legacy (when 
using sid xserver binary).

-- System Information:
Debian Release: stretch/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.3.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=ja_JP.UTF-8, LC_CTYPE=ja_JP.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

Bug#715505: Updated OpenChrome driver available

[Jeffrey Walton]

Also see "Updated OpenChrome driver available",
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=814682. It does not
appear to be available in Debian Unstable yet.

Fir the VIA and Unknown Card-Ids (3371|1019|2125), Chipset:
P4M900/VN896/CN896, and Xserver crash, also see
http://bugs.freedesktop.org/show_bug.cgi?id=94130.