FEDORA-2018-3cc91ce983

bugfix update in Fedora 27 for libinput

Status: stable 6 months ago

Fix crasher due to missing devnode after resume (#1536633)


libinput 1.10, fixes a crash with tablets, better hysteresis handling, better palm detection

Comments 19

This update has been submitted for testing by whot.

This update has obsoleted libinput-1.10.0-1.fc27, and has inherited its bugs and notes.

This update has been pushed to testing.

works for me

karma: +1

no regressions noted

karma: +1

works for me

karma: +1

This update has been submitted for batched by bodhi.

After upgrading, I cannot use the keyboard's media keys nor the laptop's power button to suspend.

karma: -1 critpath: -1

Bodhi is disabling automatic push to stable due to negative karma. The maintainer may push manually if they determine that the issue is not severe.

@yajo, do you have a bug number for me? also test with sudo libinput debug-events to see if the events are still being delivered

Sorry, I have no bug number... I was just testing this package to fix #1536633 and noticed that started happening.

That command seems to say it's working fine though... Weird 😕:

-event7   KEYBOARD_KEY      +3.49s  KEY_PLAYPAUSE (164) pressed
 event7   KEYBOARD_KEY      +3.61s  KEY_PLAYPAUSE (164) released
 event7   KEYBOARD_KEY      +4.03s  KEY_PLAYPAUSE (164) pressed
 event7   KEYBOARD_KEY      +4.09s  KEY_PLAYPAUSE (164) released
-event3   KEYBOARD_KEY     +10.11s  KEY_POWER (116) pressed
 event3   KEYBOARD_KEY     +10.11s  KEY_POWER (116) released

I just tested on gnome-settings trying to rebind some keys, and the key presses get detected; however they have no effect while on the session. I guess that can be a problem of another component in the stack? Gnome shell maybe?

Yep, it seems to be gnome shell. I used alt+f2, r, enter and those keys started working again.

karma: +1 critpath: +1

It works fine.

karma: +1 critpath: +1

@yajo: yeah, if you can see the keys in debug-events then gnome will receive them (as a general rule: we don't really do anything with key events, so that's the thing in libinput to least likely get buggy :)

This update has been submitted for stable by whot.

pushing to stable based on +6 karma and the bug reported by @yajo is an issue with another component

This update has been pushed to stable.


Add Comment & Feedback
Toggle Preview

Comment fields support Fedora-Flavored Markdown. Comments are governed under this privacy policy.

-1 0 +1 Feedback Guidelines
#1536633 [abrt] xorg-x11-server-Xorg: OsLookupColor(): Segmentation fault at address 0x0
Does the system's basic functionality continue to work after this update?
Is the update generally functional?
Content Type
RPM
Status
stable
Test Gating Status
Tests Passed
Submitted by
Update Type
bugfix
Karma
+6
stable threshold: 3
unstable threshold: -3
Autopush
Disabled
Dates
submitted 6 months ago
in testing 6 months ago
in stable 6 months ago

Related Bugs 1

00 #1536633 [abrt] xorg-x11-server-Xorg: OsLookupColor(): Segmentation fault at address 0x0

Automated Test Results

Test results and gating status may sometimes conflict as the gating status is retrieved periodically by Bodhi's backend server, while the test results presented here are retrieved upon page load. If your update is marked as gated while all the tests show green/passed, the next check of gating status should open the gate.