|
Bugzilla – Full Text Bug Listing |
| Summary: | udev-173 kills bluetooth HID devices | ||
|---|---|---|---|
| Product: | [openSUSE] openSUSE 12.1 | Reporter: | Stefan Seyfried <seife> |
| Component: | Basesystem | Assignee: | Greg Kroah-Hartman <gregkh> |
| Status: | RESOLVED FIXED | QA Contact: | E-mail List <qa-bugs> |
| Severity: | Critical | ||
| Priority: | P5 - None | CC: | fcrozat, kasievers, rwooninck |
| Version: | Factory | ||
| Target Milestone: | --- | ||
| Hardware: | Other | ||
| OS: | Other | ||
| Whiteboard: | |||
| Found By: | Third Party Developer/Partner | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
| Attachments: |
working udev-172
non-working udev-173 |
||
Created attachment 449972 [details]
non-working udev-173
Removing the new (in 173) line SUBSYSTEMS=="bluetooth", GOTO="persistent_input_end" from 60-persistent-input.rules fixes the issue. the above comment does not fix the issue completely: after reconnecting the mouse, i still need to switch away from X and back again, so something else is missing. On the latest factory (running kernel rc6), it seems sufficient to remove this line from the file /lib/udev/rules.d/60-persistent-input.rules. My bluetooth mouse (After connecting) is working directly in a KDE session. Searching the internet (as that the kernel.org website was down), I found a patch from upstream that was applied to the Fedora udev-173 package. I have build the udev package successfully and can confirm that it resolves this issue. The updated packages I have submitted back to Base:System with SR #82821. Regards Raymond patch accepted, thanks. This is an autogenerated message for OBS integration: This bug (716892) was mentioned in https://build.opensuse.org/request/show/83689 Factory / udev |
Created attachment 449971 [details] working udev-172 After update to udev-173, bluetooth HID devices (mice, for example) no longer get signaled to x.org, resulting in a non-working device. Downgrading to udev-172 from factory-tested instantly fixes the issue. Attached are the results from udevadm monitor --property with both versions and then switching on the mouse.