| Summary: | kde 4.11.2 blouetooth mouse does not work correctly with bluez5 | ||
|---|---|---|---|
| Product: | Mageia | Reporter: | Denis Robel <denis.robel> |
| Component: | RPM Packages | Assignee: | Nicolas Lécureuil <mageia> |
| Status: | RESOLVED OLD | QA Contact: | |
| Severity: | major | ||
| Priority: | Normal | CC: | balcaen.john, lmenut, mageia |
| Version: | 4 | ||
| Target Milestone: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Source RPM: | bluedevil | CVE: | |
| Status comment: | |||
|
Description
Denis Robel
2014-01-27 10:22:26 CET
Hallo, I compiled bluedevil from source (Bluedevil RC1 of december 2013) and all things are ok now. The reason was the broken bluedevil code in cauldron (segfaulting of bluedevil-input). For MGA4 final release you should create a new package of bluedevil from lates bludevil code. with best regards Denis
Sander Lepik
2014-01-27 12:24:28 CET
CC:
(none) =>
mageia
Sander Lepik
2014-01-27 12:28:24 CET
CC:
sysadmin-bugs =>
(none)
Manuel Hiebel
2014-01-28 18:23:19 CET
CC:
(none) =>
balcaen.john, lmenut I've just submitted libbluedevil-2.0-0.git20140107 and bluedevil-2.0.0-0.git20140216 (bluedevil RC1 + some more fixes and updated translations) in cauldron and Mga 4 core/updates_testing. Please, could you test them? regards, Luc Version:
Cauldron =>
4 Hallo Luc, I downloaded all src RPM's fom Cauldron (bluez, obexd and bludevil) and I compiled and installed all the stuff. Result I can connect my ThnikPad bluetooth mouse correctly but afete a suspend or after a reboot it does not reconnect. But this is a known bug in bluedevil: https://bugs.kde.org/show_bug.cgi?id=295349 regards, Denis Mageia 4 changed to end-of-life (EOL) status on 2015-09-19. It is is no longer maintained, which means that it will not receive any further security or bug fix updates. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Mageia version. Bug Reporter: Thank you for reporting this issue and we are sorry that we weren't able to fix it before Mageia 4's end of life. If you are able to reproduce it against a later version of Mageia, you are encouraged to click on "Version" and change it against that version of Mageia. If it's valid in several versions, select the highest and add MGAxTOO in whiteboard for each other valid release. Example: it's valid in cauldron and Mageia 5, set to cauldron and add MGA5TOO. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Mageia release includes newer upstream software that fixes bugs or makes them obsolete. If you would like to help fixing bugs in the future, don't hesitate to join the packager team via our mentoring program [1] or join the teams that fit you most [2]. [1] https://wiki.mageia.org/en/Becoming_a_Mageia_Packager [2] http://www.mageia.org/contribute/ As announced over a month ago, Mageia 4 changed to end-of-life (EOL) status on 2015-09-19. It is is no longer maintained, which means that it will not receive any further security or bug fix updates. This issue may have been fixed in a later Mageia release, so, if you still see it and didn't already do so: please upgrade to Mageia 5 (or, if you read this much later than this is written: make sure you run a currently maintained Mageia version) If you are able to reproduce it against a maintained version of Mageia, you are encouraged to 1. reopen this bug report, by changing the "Status" from "RESOLVED - OLD" to "REOPENED" 2. click on "Version" and change it against that version of Mageia. If you know it's valid in several versions, select the highest and add MGAxTOO in whiteboard for each other valid release. Example: it's valid in cauldron and Mageia 5, set to cauldron and add MGA5TOO. 3. give as much relevant information as possible. If you're not an experienced bug reporter and have some time: please read this page: https://wiki.mageia.org/en/How_to_report_a_bug_properly If you see a similar issue, but are _not_sure_ it is the same, with the same cause, then please file a new bug report and mention this one in it (please include the bug number, too). If you would like to help fixing bugs in the future, don't hesitate to join the packager team via our mentoring program [1] or join the teams that fit you most [2]. [1] https://wiki.mageia.org/en/Becoming_a_Mageia_Packager [2] http://www.mageia.org/contribute/ Status:
NEW =>
RESOLVED |