Bug 450081
| Summary: | Can't connect bluetooth mouse (MS Wireless Notebook Presenter Mouse 8000) | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Miroslav Pragl <miroslav> | ||||
| Component: | bluez-gnome | Assignee: | Bastien Nocera <bnocera> | ||||
| Status: | CLOSED RAWHIDE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||
| Severity: | low | Docs Contact: | |||||
| Priority: | low | ||||||
| Version: | 9 | CC: | bdm, bnocera | ||||
| Target Milestone: | --- | Keywords: | i18n | ||||
| Target Release: | --- | ||||||
| Hardware: | All | ||||||
| OS: | Linux | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2009-03-05 18:53:07 UTC | Type: | --- | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Embargoed: | |||||||
| Attachments: |
|
||||||
|
Description
Miroslav Pragl
2008-06-05 07:55:38 UTC
Hi, I yum-updated bluez stuff today: Jun 26 14:25:55 mirek-nb yum: Updated: bluez-utils-alsa-3.32-1.fc9.x86_64 Jun 26 14:25:57 mirek-nb yum: Updated: bluez-utils-3.32-1.fc9.x86_64 Jun 26 14:25:57 mirek-nb yum: Updated: bluez-utils-cups-3.32-1.fc9.x86_64 and the problem is 99% SOLVED. The -1% is fact that I can use the mouse but it's name is truncated to "Microsoft" from "Microsoft (tm) Wireless ... mouse". Seems that "TM" character is bad guy. Is there a way how to dump the name "as is"? hcitool scan finds "00:12:5A:67:A3:C1 Microsoft" hcitool name 00:12:5A:67:A3:C1 finds "Microsoft� Wireless Notebook Presenter Mouse 8000" - see attached txt file MP Created attachment 310326 [details]
this is dump from hcitool name 00:12:5A:67:A3:C1 >name.txt
the name actually contains (R) sign (0xAE) - Microsoft(R) Wireless Notebook
Presenter Mouse 8000
MP
It's most likely the string being in the wrong encoding, or hcid not setting its default encoding to UTF-8 (if it is actually UTF-8). The name of the mouse not being the right one in F9 isn't something I would really spend time on, but let us know whether the naming problem still exists with F10 when you get to installing it. We could more easily work towards fixing the problem with the latest versions. Note that the mouse is broken, as the device name is supposed to be in UTF-8. So MS are breaking the spec. Even then, I've implemented a work-around, and posted the patch at: http://thread.gmane.org/gmane.linux.bluez.kernel/1687 Work-around is in bluez-4.32-4 in rawhide. Is there any chance of getting updated packages for bluez released for Fedora 10 please? I have an MS mouse of the same type and it worked in Fedora 8 I think, but no longer now. Something equal to or later than 4.32-4 would be really useful. Tried a local package rebuild but even after adding --enable-alsa to the configure step the alsa .so files still don't get built. Thanks! (In reply to comment #5) > Is there any chance of getting updated packages for bluez released for Fedora > 10 please? I have an MS mouse of the same type and it worked in Fedora 8 I > think, but no longer now. Something equal to or later than 4.32-4 would be > really useful. You probably need to update your system, Miroslav's mouse works fine, the only fix was for the mouse name, which really isn't something I'm going to spend time on for F10. My F10 system is fully updated, so when you say update, what did you have in mind? I can pair the mouse with the laptop, but it has done nothing after that, so I was wondering if it could be down to udev etc not recognising it as a mouse and failing to set things up correctly. I suppose F11 will be out soon, so I'll upgrade then but I would like to understand what's gone wrong since F8. File a separate bug with the debug output of bluetoothd. This bug is closed, and there's no point in adding more comments to it. |