:: [devuan-dev] bug#232: marked as don…
トップ ページ
このメッセージを削除
このメッセージに返信
著者: Devuan bug Tracking System
日付:  
To: Arne Wichmann
題目: [devuan-dev] bug#232: marked as done (xserver-xorg-input-wacom: starting X session results in permanent black screen)
Your message dated Mon, 28 Oct 2024 15:58:26 +0100
with message-id <Zx-mlLJeIkWt2jKn@???>
and subject line No information - closing bug
has caused the Devuan bug report #232,
regarding xserver-xorg-input-wacom: starting X session results in permanent 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 owner@???
immediately.)


--
232: https://bugs.devuan.org/cgi/bugreport.cgi?bug=232
Devuan Bug Tracking System
Contact owner@??? with problems
Package: xserver-xorg-input-wacom
Version: 0.34.0-1

I own a Lenovo Thinkpad X201 Tablet laptop. When initializing an X session with this package, the video goes black and the keyboard is no longer functional. The only way to safely shutdown/reboot is via Magic Sysrq commands (ex: Raising Elephants Is So Utterly Boring).

On this same laptop, if the specified package is absent, the X session starts normally without tablet functionality.

Having encountered this issue on previous non-systemd distros, the solution is this command:
$ isdv4-serial-inputattach /dev/ttyS0

This command should be incorporated via a custom init script, by editing the Xsession/display manager init script, or something else as long as it's executed before X. To hide the output of this command and background, I modify the above command to:
$ isdv4-serial-inputattach /dev/ttyS0 > /dev/null 2>&1 &

Afterward running the above command, the X session launches successfully with tablet functionality.Hi.

There has not be an answer to this bug for 18 months, so I am closing it.
If there is an update to the bug, you can reopen it.

cu

YPl
--
[...] If you don't want to be restricted, don't agree to it. If you are
coerced, comply as much as you must to protect yourself, just don't support
it. Noone can free you but yourself. (crag, on Debian Planet)
Y Plentyn (aw@???)