This is reported against an old version of Ubuntu and many things has
changed since then. Because of that we won't fix this issue however if
this behavior repeats on a modern version please fill a bug report
against it and we will take it from there.
** Changed in: bluez (Ubuntu)
Status:
** Tags added: bluez-classic
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/61413
Title:
Logitech DiNovo MediaPad should not toggle Numlock
To manage notifications about this bug go to:
Thank you for taking the time to report this bug and helping to make
Ubuntu better. You reported this bug a while ago and there hasn't been
any activity in it recently. We were wondering is this still an issue
for you? Thanks in advance.
--
Logitech DiNovo MediaPad should not toggle Numlock
No change has been made that affects this.
Please don't post canned messages without reading the description and
discussion just to get your 5-a-day. It's much too common. Thanks.
--
Logitech DiNovo MediaPad should not toggle Numlock
https://bugs.launchpad.net/bugs/61413
You received this bug
Sorry if it looks like that but that wasn't my intention. I saw that
Mario set the bug to Incomplete and asked you a question that you
weren't able to answer back then, so I thought I would ping you to check
if you can answer his question now, since the bug has been lying around
incomplete for
** Changed in: bluez (Ubuntu)
Sourcepackagename: bluez-utils = bluez
Importance: Undecided = Wishlist
--
Logitech DiNovo MediaPad should not toggle Numlock
https://bugs.launchpad.net/bugs/61413
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
As a useful data point, can someoen see if this is still the situation
on Intrepid (2.6.27 kernel and 4.x bluez packages)
** Changed in: bluez (Ubuntu)
Status: Confirmed = Incomplete
--
Logitech DiNovo MediaPad should not toggle Numlock
https://bugs.launchpad.net/bugs/61413
You received
Robert, I doubt that this is ever what the user wanted. If the user
wanted to use numlock-mode on *another* keyboard, why press this button
on the mediapad? Why not press the numlock button that is exactly where
the numlock should be? This setup with two separate keyboards is
explicitly designed
To throw my hat in the ring, I think that the default behavior of the
Mediapad *should* be to toggle numlock-mode. On any standard keyboard
configuration, this should pose no problem and is probably what the user
wanted.
That said, I think this is a valid bug for laptop computer users, but
the
We are closing this bug report as it lacks the information, described in
the previous comments, we need to investigate the problem further.
However, please reopen it if you can give us the missing information and
don't hesitate to submit bug reports in the future.
** Changed in: bluez-utils
Ummm Paul, aren't you confusing the two issues here? There's nothing
fixed about this in tribe 2 or later, so I assumed you were answering
Alex how to get things working at all. Why would you close a bug as
invalid because it hasn't been fixed?
--
Logitech DiNovo MediaPad should not toggle
Sorry, I may have close this one too fast.
We do close bug waiting for more than 1 month without having got an answer.
I have taken my previous comment as a request to try if Tribe-2 would have fix
this issue.
Now that I see you tried with Tribe-2, and that you are there to answer
further
Sorry
Well I would suggest you try with http://www.ubuntu.com/testing/tribe2 BUT
watchout! according to https://bugs.launchpad.net/ubuntu/+bug/123920 and
https://bugs.launchpad.net/ubuntu/+source/bluez-utils/+bug/32415
device may not work anymore.
** Changed in: bluez-utils (Ubuntu)
: Logitech DiNovo MediaPad should not toggle Numlock
Alex, see bug #66884 for the Logitech dongle + Bluez - should be fixed
in Feisty though I haven't tried it yet.
--
Logitech DiNovo MediaPad should not toggle Numlock
https://launchpad.net/bugs/61413
--
Logitech DiNovo MediaPad should not toggle
Alex, see bug #66884 for the Logitech dongle + Bluez - should be fixed
in Feisty though I haven't tried it yet.
--
Logitech DiNovo MediaPad should not toggle Numlock
https://launchpad.net/bugs/61413
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
I can confirm this happens in my Dell Latitude CPxJ as well.
I concur it would be an advantageous feature, given that the exact same
behavior described happens in Windows.
Kristoffer,
I have to ask, have you managed to make the dongle of this set to play
nicely with Ubuntu/Bluez? If so I'd
16 matches
Mail list logo
