Bug 2563 - Udev upgrade to udev-173-2.mga2 breaks bluetooth input devices in X
Summary: Udev upgrade to udev-173-2.mga2 breaks bluetooth input devices in X
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: x86_64 Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Colin Guthrie
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-08-29 13:01 CEST by Jari S
Modified: 2011-08-29 15:39 CEST (History)
2 users (show)

See Also:
Source RPM: udev-173-2.mga2.src.rpm
CVE:
Status comment:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Description Jari S 2011-08-29 13:01:22 CEST 
Description of problem:
Udev upgrade to udev-173-2.mga2 breaks bluetooth input devices in X.

Version-Release number of selected component (if applicable):
udev-173-2.mga

How reproducible:
Always.

Steps to Reproduce:
1. Upgrade to udev-173-2
2. Attach bluetooth input device
3. Try to input something with attached device

Fix available at 
* http://www.spinics.net/lists/hotplug/msg05034.html
* also discussed at https://bugs.archlinux.org/task/25356

I tried the fix from Archilinux and it solved the problem.
Manuel Hiebel 2011-08-29 13:15:11 CEST

CC: (none) => mageia, thierry.vignaud

Comment 1 Colin Guthrie 2011-08-29 13:24:56 CEST 
Discussing the issue with Kay upstream now. Will update when I know more.

Status: NEW => ASSIGNED
Assignee: bugsquad => mageia

Comment 2 Colin Guthrie 2011-08-29 13:38:05 CEST 
Can you please test the upstream fix to see if it works (remember to revert the previous fix first (patch -R is your friend!).

http://git.kernel.org/?p=linux/hotplug/udev.git;a=commit;h=617746e09795575c6258dd075ee7f0a44ce61e1e
Comment 3 Colin Guthrie 2011-08-29 15:39:54 CEST 
I've received confirmation the the fix linked above is the one needed and submitted it for build.

Please reopen if there are still problems.

Status: ASSIGNED => RESOLVED
Resolution: (none) => FIXED
Note You need to log in before you can comment on or make changes to this bug.