Mailinglist Archive: opensuse-bugs (3354 mails)

< Previous Next >
[Bug 981750] [synaptics] TW20160524: driver pulled in automatically but it should not
  • From: bugzilla_noreply@xxxxxxxxxx
  • Date: Sun, 29 May 2016 06:33:24 +0000
  • Message-id: <bug-981750-21960-eIHyGxaLcy@http.bugzilla.opensuse.org/>
http://bugzilla.opensuse.org/show_bug.cgi?id=981750
http://bugzilla.opensuse.org/show_bug.cgi?id=981750#c8

Egbert Eich <eich@xxxxxxxx> changed:

What |Removed |Added
----------------------------------------------------------------------------
Summary|TW20160524: |[synaptics] TW20160524:
|xf86-input-synaptics is |driver pulled in
|pulled in automatically but |automatically but it should
|it should not |not

--- Comment #8 from Egbert Eich <eich@xxxxxxxx> ---
(In reply to Stefan Dirsch from comment #7)

I don't see a MatchIsTablet for libinput but for evdev config. So this is
still useful.

The tablet is indeed missing.

I even don't know, whether xorg-x11-input-driver package is installed on
this system.

We can find out. Robby, was your TW installation an upgrade and can you check
if you have 'xorg-x11-driver-input' installed on your system?

But to be sure we can ask Coolo.

We definitely need to ask him!

On upgrades of systems that had the synaptics driver installed we will always
have the problem that the synaptics driver will take precedence over libinput.
This will however only affect TW. On Leap 42.1 we never installed libinput by
default. According to the old precedence rules, the synaptics driver had
precedence over evdev for anything that matched on a 'touchpad' device.
After an update this will remain the same: synaptics will have precedence over
evdev and libinput for anything 'touchpad'.
Only on TW systems that still had xorg-x11-input-driver installed by default
but also pulled in xf86-input-libinput an issue as described here may occur.

Removing synaptics from xorg-x11-driver-input will not deinstall synaptics on
update but it allows to uninstall it without breaking dependencies.

--
You are receiving this mail because:
You are on the CC list for the bug.
< Previous Next >