On Tue, March 25, 2008 06:58, Zoltan wrote:
> My logitech cordless elite bluetooth hub connects with USB.
> When you get the first login prompt, just pull out the USB plug, wait a
> second or two and plug it back in. Both your keyboard and mouse will then
> wake up. Tadaaa!
Nada tadaaa!
When you
My logitech cordless elite bluetooth hub connects with USB.
When you get the first login prompt, just pull out the USB plug, wait a second
or two and plug it back in. Both your keyboard and mouse will then wake up.
Tadaaa!
I fully agree that this is the most pathetically tedious bug I have ever
On Sun, March 23, 2008 01:42, ChaseNeveu wrote:
> After searching the internet for solutions to my particular bluetooth
> problem, I've come across dozens of these bug reports. It's the same for
> each one:
>
> "My keyboard/mouse won't reconnect after reboot/suspend/idle."
>
> And the response has
After searching the internet for solutions to my particular bluetooth
problem, I've come across dozens of these bug reports. It's the same for
each one:
"My keyboard/mouse won't reconnect after reboot/suspend/idle."
And the response has been the same too:
"Try entering this into your configs and
This is still a problem in Gutsy. My Logitech mouse stops working if I
leave the computer too long. The only workaround I've found is to turn
the physical bluetooth switch on the laptop off and on again.
--
Bluetooth Mouse and Keyboard Broken in Dapper/Edgy/Feisty
https://bugs.launchpad.net/bug
@Ron Adams,
Might it be you're indeed seeing Bug #123920 ?
--
Bluetooth Mouse and Keyboard Broken in Dapper/Edgy/Feisty
https://bugs.launchpad.net/bugs/32415
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
--
ubuntu-bugs mailing list
ub
I can confirm a variation on Gusty Beta, fully patched as of 9/29. I
have an MX Revolution mouse, which works fine throughout (as expected;
it's not bluetooth and has its own dongle), but my MX 5000 bluetooth
keyboard does not work until it is replugged.
AMD 64-FX running x86 Gusty Beta.
If you n
Hi All,
I am new to this discussion, just tripped over it while looking for something
totally different.
If I say something silly, please let me know. Just trying to help, but I may be
totally wrong here :-)
My understanding of the symptoms:
- a bluetooth mouse or keyboard, regardless of the bra
On Fri, August 3, 2007 10:02, neskweek wrote:
> Sorry :P
> Depited I forgot to post my reults :
> When I tryed patching the kernel with bluez patch, the patch process
> reports that almost all modifications have already been done to the kernel
> (which is weird... maybe that's due to some modifica
Sorry :P
Depited I forgot to post my reults :
When I tryed patching the kernel with bluez patch, the patch process reports
that almost all modifications have already been done to the kernel (which is
weird... maybe that's due to some modification made by the ubuntu team but not
exactly the same
Any results yet, neskweek?
--
Bluetooth Mouse and Keyboard Broken in Dapper/Edgy/Feisty
https://bugs.launchpad.net/bugs/32415
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https:
(:P Send the last report as I didn't finished it. Sorry Off course the
attached file is to read after my thread )
Then in the kernel bug report we can see that the bug you're hunting is
located on the hidp kernel module.
I'm currently searching if this patch was installed in the ubuntus
kernel :
Hi
I've got a Dinovo Keyboard set (First Generation) installed on a PC (Intel
Pentium III Prescot E)
After some times on Gentoo I have installed a Kubuntu feisty with the alternate
CD.
My box is running the 2.6.20-16-generic #2 SMP kernel.
I have this problem too. Having spend some times fugur
On Tue, May 22, 2007 16:53, alex_mayorga wrote:
> @amedee, Zoltan
> Can you see if this helps
> http://ubuntuforums.org/showpost.php?p=2334318&postcount=17 I have a fully
> functional Logitech diNovo Laser now, at least one fellow ubuntero has
> reported success with that guide.
I'll try it toni
@amedee, Zoltan
Can you see if this helps
http://ubuntuforums.org/showpost.php?p=2334318&postcount=17 I have a fully
functional Logitech diNovo Laser now, at least one fellow ubuntero has reported
success with that guide.
My 2ยข,
Alex
--
Bluetooth Mouse and Keyboard Broken in Dapper/Edgy/Feist
amedee wrote:
> Op dinsdag 15-05-2007 om 15:04 uur [tijdzone +], schreef Zoltan:
>
>> amedee wrote:
>>
>>> On Tue, May 15, 2007 15:40, Zoltan wrote:
>>>
>>>
amedee wrote:
> On Tue, May 15, 2007 07:58, Zoltan wrote:
>
>
>
Op dinsdag 15-05-2007 om 15:04 uur [tijdzone +], schreef Zoltan:
> amedee wrote:
> > On Tue, May 15, 2007 15:40, Zoltan wrote:
> >
> >> amedee wrote:
> >>
> >>> On Tue, May 15, 2007 07:58, Zoltan wrote:
> >>>
> >>>
> Hi,
> Just want to add my name to the list of peeps a
amedee wrote:
> On Tue, May 15, 2007 15:40, Zoltan wrote:
>
>> amedee wrote:
>>
>>> On Tue, May 15, 2007 07:58, Zoltan wrote:
>>>
>>>
Hi,
Just want to add my name to the list of peeps affected by this bug :-)
I have the Logitech MX Bluetooth Kyb/Mouse, which was fine u
On Tue, May 15, 2007 15:40, Zoltan wrote:
> amedee wrote:
>> On Tue, May 15, 2007 07:58, Zoltan wrote:
>>
>>> Hi,
>>> Just want to add my name to the list of peeps affected by this bug :-)
>>> I have the Logitech MX Bluetooth Kyb/Mouse, which was fine until 5.10,
>>> and
>>> after having shelved t
amedee wrote:
> On Tue, May 15, 2007 07:58, Zoltan wrote:
>
>> Hi,
>> Just want to add my name to the list of peeps affected by this bug :-)
>> I have the Logitech MX Bluetooth Kyb/Mouse, which was fine until 5.10, and
>> after having shelved this expensive monster for a year, I see it's still
>
On Tue, May 15, 2007 07:58, Zoltan wrote:
> Hi,
> Just want to add my name to the list of peeps affected by this bug :-)
> I have the Logitech MX Bluetooth Kyb/Mouse, which was fine until 5.10, and
> after having shelved this expensive monster for a year, I see it's still
> not fine in 7.04 - but
Hi,
Just want to add my name to the list of peeps affected by this bug :-)
I have the Logitech MX Bluetooth Kyb/Mouse, which was fine until 5.10, and
after having shelved this expensive monster for a year, I see it's still not
fine in 7.04 - but at least re-plugging it seems to re-awaken it.
I'll
On Sat, May 5, 2007 09:06, Eugene Lazutkin wrote:
>>> BTW, it is not Logitech specific --- I have this problem with
>>> Miscrosoft
>>> Bluetooth mouse.
>>>
>>Does it have a broadcomm-based usb receiver?
>
> It uses the built-in Bluetooth module in my notebook.
Yes, and which chipset does your bui
>> BTW, it is not Logitech specific --- I have this problem with Miscrosoft
>> Bluetooth mouse.
>>
>Does it have a broadcomm-based usb receiver?
It uses the built-in Bluetooth module in my notebook.
--
Bluetooth Mouse and Keyboard Broken in Dapper/Edgy/Feisty
https://bugs.launchpad.net/bugs/3241
Op zaterdag 05-05-2007 om 05:23 uur [tijdzone +], schreef Eugene
Lazutkin:
> BTW, it is not Logitech specific --- I have this problem with Miscrosoft
> Bluetooth mouse.
>
Does it have a broadcomm-based usb receiver?
--
Amedee Van Gasse <[EMAIL PROTECTED]>
--
Bluetooth Mouse and Keyboard Br
BTW, it is not Logitech specific --- I have this problem with Miscrosoft
Bluetooth mouse.
--
Bluetooth Mouse and Keyboard Broken in Dapper/Edgy/Feisty
https://bugs.launchpad.net/bugs/32415
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
-
Bluetooth failure still present.
iMac G5 rev B Apple bluetooth k/b & bluetooth mouse.
Feisty final powerpc alternate install CD.
Installation goes through fine (install-powerpc64).
Reboot works fine up to GDM login screen.
This becomes a lockout screen; no mouse, no k/b functionality.
--
Bluetoot
I have the exact same problem as aliubi mentioned above
(https://bugs.launchpad.net/ubuntu/+source/bluez-
utils/+bug/32415/comments/97). My Logitech MX5000 keyboard and mouse
work fine for a while, but the connection gets dropped if either device
is idle for too long. I'm not sure what the exact id
This looks like the same or a similar bug:
http://groups.google.com/group/ubuntu-
bluetooth/browse_frm/thread/eda5d4dfefe905db ?
--
Bluetooth Mouse and Keyboard Broken in Dapper/Edgy/Feisty
https://bugs.launchpad.net/bugs/32415
You received this bug notification because you are a member of Ubuntu
The status of this more than a year old bug is still needs info.
Who do we have to bribe / give beer to / let our sister sleep with / sacrifice
our firstborn for to get some attention to this bug?
A few posts and weeks back I wrote a functional workaround, but there still is
no confirmation that
I guess there is more than enough info for the developers to have a look
at this now...
** Changed in: bluez-utils (Ubuntu)
Status: Needs Info => Confirmed
--
Bluetooth Mouse and Keyboard Broken in Dapper/Edgy/Feisty
https://bugs.launchpad.net/bugs/32415
You received this bug notification
Maybe this is Logitech specific. However I only have the old diNovo
desktop and that one works perfectly fine for me. Even the re-connect
has no problems.
--
Bluetooth Mouse and Keyboard Broken in Dapper/Edgy/Feisty
https://bugs.launchpad.net/bugs/32415
You received this bug notification because
Same problem here. I have the latest feisty, and I have to "sudo hidd
--search" after rebooting, and periodically after that to re-attach the
mouse. I cannot unplug/re-plug the dongle because my notebook has the
internal Bluetooth module.
This bug thread goes for so long! How come it was never fix
I just updated my Feisty install's kernel from 2.6.20-13-generic to
2.6.20-14-generic, with all other packages up-to-date, too. The problem
wasn't fixed by -13, nor by -14.
I have a Logitech MX5000 keyboard / MX1000 mouse combo. The unplug
(wait...) plug back in workaround works for me. Output fro
The latest kernel (2.6.20-13) fixes the problem for me.
--
Bluetooth Mouse and Keyboard Broken in Dapper/Edgy/Feisty
https://launchpad.net/bugs/32415
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
It's (almost) solved!
I have added the following to /etc/default/bluetooth:
HIDD_OPTIONS="-i hci0 --connect 00:07:61:3F:DA:41 --connect
00:07:61:48:71:DE --master --server"
00:07:61 is Logitech, 3F:DA:41 is the keyboard; 48:71:DE is the mouse.
I rebooted. It's my impression that the keyboard do
I now have a working keyboard+mouse+phone!
Wat I did:
* update to the latest bluetooth version in feisty
* in this version, the mouse and the phone work, but not the keyboard
* I attached a spare ps2 keyboard
* I pressed the connection button on the keyboard and the dongle, while typing
(on the o
Op donderdag 15-03-2007 om 18:03 uur [tijdzone +], schreef T.
Koehler:
> What other information do you seek? Please specify.
>
> I propose to change the urgency to high, since it disables people with
> bluetooth-based input devices from using their computer at all.
>
I agree with the urgency
Op donderdag 15-03-2007 om 18:09 uur [tijdzone +], schreef T.
Koehler:
> Since this seems in part to be a kernel issue, the bug should also be
> filed against the kernel package, correct?
I agree.
I have also sent an email to the linux kernel mailing list (you can't go
any more upstream than
Since this seems in part to be a kernel issue, the bug should also be
filed against the kernel package, correct?
--
Bluetooth Mouse and Keyboard Broken in Dapper/Edgy/Feisty
https://launchpad.net/bugs/32415
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailma
What other information do you seek? Please specify.
I propose to change the urgency to high, since it disables people with
bluetooth-based input devices from using their computer at all.
--
Bluetooth Mouse and Keyboard Broken in Dapper/Edgy/Feisty
https://launchpad.net/bugs/32415
--
ubuntu-bug
Confirmed on feisty (up-to-date as of posting) on i386:
I can only use my bluetooth keyboard and mouse (Microsoft Office Desktop
Elite) in HIDP-mode.
Patching the kernel (2.6.20-10-lowlatency) with the latest patch from
www.bluez.org (-mh1) resolves the issue.
I had the same problem in several o
I just installed Edgy on a couple of machines last week. (Let me
preface this by saying I'm already an Ubuntu convert...however...) I
have a Logitech DiNovo keyboard and mouse, with dongle.
The behaviour I see seems slightly different than what is described
herein. I use sudo hidd --connect, an
No attachments, I see.
Second try...
I should also mention that the keyboard is found, but that kbluetoothd
is unable to pair with the keyboard.
** Attachment added: "several logfiles"
http://librarian.launchpad.net/6615244/log.tar.gz
--
Bluetooth Mouse and Keyboard Broken in Dapper/Edgy/Fei
Ok, tried it again.
When I type hcitool scan, it find my mouse and keyboard (Piotr, you have to put
your keyboard/mouse into discoverable mode by pressing the button on they
keyboard/mouse). When I try to connect my mouse using "hidd --connect
MACADDRESS" I get this error.
Can't get device info
On 3/1/07, amedee <[EMAIL PROTECTED]> wrote:
>
> That is exactly what I expected would happen, and this is an excellent
> description of the problem.
Hey Amedee,
sorry for not coming back for so long.
I did:
[EMAIL PROTECTED]:~$ sudo hid2hci and the result is:
Switching device 046d:c70a to HCI m
On do, 2007-03-01 at 19:21 +, SickFinga wrote:
> OK, new findings.
>
> I plugged in regular keyboard/mouse with bluetooth ones still plug in. As
> usual bluetooth ones didnt work.
> I tried using my cellphone and it found my bluetooth dongle. I also tried
> hcitool scan and it found my mouse
OK, new findings.
I plugged in regular keyboard/mouse with bluetooth ones still plug in. As usual
bluetooth ones didnt work.
I tried using my cellphone and it found my bluetooth dongle. I also tried
hcitool scan and it found my mouse/keyboard.
If I do unplug/plug back in routine, and I try to u
I can also comfirm this bug on Ubuntu 6.10 with Logitech Elite keyboard
and MX900 combo (both USB)
Here is how it works for me.
When I boot into Ubuntu with bluetooth dongle pluged in, mouse and
keyboard stops working.
When I unplug USB from the bluetooth dongle Ubuntu loads fine, keyboard works
On di, 2007-02-20 at 15:34 +, Piotr Szczepanik wrote:
> I must admit that setting in /etc/default/bluetooth:
>
> HIDD_OPTIONS="--master --connect 00:07:61:34:xx:xx--connect
> 00:07:61:37:xx:xx --server"
>
> makes my MX5000 set working in HCI mode on Edgy x86.
> I loose it only after I boot to
I must admit that setting in /etc/default/bluetooth:
HIDD_OPTIONS="--master --connect 00:07:61:34:xx:xx--connect
00:07:61:37:xx:xx --server"
makes my MX5000 set working in HCI mode on Edgy x86.
I loose it only after I boot to Windows and back to Edgy but then replugging
the dongle makes it worki
> Don't put --connect in HIDD_OPTIONS. This will fully mess with your system and
> whoever proposed this strange settings is wrong.
Marcel,
putting the following in my /etc/default/bluez-utils is the only thing
that ever made my keyboard, mediapad and mouse (all 3 are bluetooth
devices) work with
Perhaps it's not important, but I think I should mention it.
On the forums someone mentioned it's not possible to get a bluetooth mouse
working in Ubuntu when it's working in Windows. You have to disable it in
Windows too.
http://www.ubuntuforums.org/showthread.php?t=87919&page=9
I have a multibo
Attached is the output of
sudo watch hcidump -X -V >> ~/hcidump.log
If anyone knows a better way of logging, please tell me.
** Attachment added: "hcidump.log"
http://librarian.launchpad.net/6480285/hcidump.log
--
Bluetooth Mouse and Keyboard Broken in Dapper/Edgy/Feisty
https://launchpa
One reboot later...
The problem remains identical.
I can use the bluetooth keyboard&mouse in legacy HID mode, OR I can use the
bluetooth dongle in HCI mode to connect to my phone, but not both at the same
time.
--
Bluetooth Mouse and Keyboard Broken in Dapper/Edgy/Feisty
https://launchpad.net/b
Thank you for your reply. Attached you will find my /etc/default/bluetooth
The most relevant section is:
HIDD_ENABLED=1
HIDD_OPTIONS="--master --server"
I will see what happens when I remove --master.
One question though. You write that --search or --connect only needs to
be issued once. When an
Don't put --connect in HIDD_OPTIONS. This will fully mess with your
system and whoever proposed this strange settings is wrong. In general
the option --server is fully enough and HIDD_ENABLE must be on.
The --search or --connect needs only to be issued once. After that the
mouse or keyboard will r
Today Ubuntu Feisty pulled in bluez-utils version 3.9.
The situation remains identical: I either have connection with keyboard+mouse,
or with the phone, but never both.
--
Bluetooth Mouse and Keyboard Broken in Dapper/Edgy/Feisty
https://launchpad.net/bugs/32415
--
ubuntu-bugs mailing list
ubu
This bug is marked as "needs info".
Please, what info do you need? I will give all information you need, and even
more.
Is this bug really going to celebrate its first anniversary in a couple of days?
--
Bluetooth Mouse and Keyboard Broken in Dapper/Edgy/Feisty
https://launchpad.net/bugs/32415
i run ubuntu 6.10 at the current update level (30.1.2007) on a fujitsu
tablett (386)
i followed the instructions in the wiki to install bluetooth such that
it works from login - and it worked for a few times, but then stopped
(nothing done with bluetooth in the meantime). i can install bluetooth
d
"fixed with...bluez-utils-3.9...for Feisty...sync with...upstream
source."
Sure, and put more frequent updates in the repos. The bug title
includes Dapper/Edgy/Feisty.
>From a Dapper x86-32 machine we checked bluez status. Bluez sits at
2.24 versus the current 3.9 source. That's quite a lag.
> I disagree, the problem is not only on Apples!
I concur. I can reproduce the problem on x86 and x86_64.
AJ
--
Bluetooth Mouse and Keyboard Broken in Dapper/Edgy/Feisty
https://launchpad.net/bugs/32415
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/
On Tue, January 30, 2007 11:20, Marcel Holtmann said:
> I think all these problems on Apple based system are caused by a race
> condition in the startup and init routines for the Bluetooth adapter. I
> am pretty sure that I finally fixed this. At least my Quad G5 running
> Edgy now has no problems
I think all these problems on Apple based system are caused by a race
condition in the startup and init routines for the Bluetooth adapter. I
am pretty sure that I finally fixed this. At least my Quad G5 running
Edgy now has no problems anymore.
The main problem was that the command for setting th
> I now have full Bluetooth functionality and can finally access to my mobile
> phone
> via bluetooth !
PS: That's because I previously had to disable Bluetooth altogether to
use my Logitech set.
Regards,
Patrick.
--
Bluetooth Mouse and Keyboard Broken in Dapper/Edgy/Feisty
https://launchpad.n
Bug remains unsolved in latest Feisty PPC build. We tested
iMac G5 rev B
Apple bluetooth keyboard A1016
Apple bluetooth mouse A1015
Feisty daily build 29 Jan 2007
Alt-powerpc disc : "install-powerpc64"
(kernel 2.6.20-5-powerpc64-smp)
So kernel >= 2.6.19 evidently does not solve the problem(s).
Cheers for that will give it a go.
alex108 <[EMAIL PROTECTED]> wrote: Finally, I made two of my computers work
with my Logitech diNovo BT
keyboard/mouse/num pad work in 6.10. I was fallowing several guides like
this https://help.ubuntu.com/community/BluetoothSetup and perhaps some
other posts
The kernel patch applies to all platforms (it changes arch-independent
sources).
But the bug doesn't occur on the other platforms:
- x86 is 32bit userspace on a 32bit kernel
- amd64 is 64bit userspace on a 64bit kernel.
The bug only appears when a 32bit userspace is used on a 64bit kernel -
this
Does this kernel bugfix also apply for x86 and/or amd64? Or is it only
for powerpc?
--
Bluetooth Mouse and Keyboard Broken in Dapper/Edgy/Feisty
https://launchpad.net/bugs/32415
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Thanks, Marcel!
You're right, that's a fix for this problem.
For everyone to verify, here's the commit entry:
http://www.kernel.org/git/?p=linux/kernel/git/stable/linux-2.6.19.y.git;a=commit;h=e9c5702e3c5558dade169949abd730173e87ef9c
Marcel has fixed the issue entirely in the kernel, leaving the
The kernel should have been fixed to handle that properly. It is part of
the 2.6.19-rc3 kernel and later. It fixes similar issues in BNEP and
CMTP support.
--
Bluetooth Mouse and Keyboard Broken in Dapper/Edgy/Feisty
https://launchpad.net/bugs/32415
--
ubuntu-bugs mailing list
ubuntu-bugs@lists
@Lothar (2006-10-14/15):
thanks for you strace log.
It proves that there are actually two diffent bugs, both related to hidd and/or
the hidp kernel module.
A/ you observe a "connect timeout" from "hidd --connect ..."
B/ Zhares sees a "HID create error 14" from "hidd --connect ..."
Bug A seems to
Finally, I made two of my computers work with my Logitech diNovo BT
keyboard/mouse/num pad work in 6.10. I was fallowing several guides like
this https://help.ubuntu.com/community/BluetoothSetup and perhaps some
other posts in Ubuntu forums. It was not easy when I started but it
looks very easy
I confirm my suspicion about the bug subtype B (occuring on ppc64
machines only).
The problem can be worked around by building a 64bit version of bluez-
utils and bluez-libs.
Currently, I've got 32bit and 64bit variants installed in parallel.
hidd --connect xx:yy:zz:
ALWAYS prints "HID create
Here comes the patch.
It applies to bluez-utils 2.25 and 3.7 (and all versions inbetween,
presumably).
The patch can safely be applied to the source tree for all platforms.
It checks at compile time that it's being build for PowerPC 32bit, otherwise it
doesn't change the implementation.
Then it
Oh, I agree. :)
I just went back to the old wired stuff. I'd like to experiment with a
USB Bluetooth adapter and my Nokia phone here in the near future.
amedee wrote:
> Op maandag 25-12-2006 om 21:12 uur [tijdzone +], schreef wls:
>> I've since sold the Logitech MX 900 Bluetooth mouse with c
Op maandag 25-12-2006 om 21:12 uur [tijdzone +], schreef wls:
> I've since sold the Logitech MX 900 Bluetooth mouse with corresponding
> BT hub / base charger.
That's not an option for me.
It was a gift from my wife, after my previous keyboard broke.
Anyway, Ubuntu should work with this hardw
I've since sold the Logitech MX 900 Bluetooth mouse with corresponding
BT hub / base charger.
amedee wrote:
> To help the developers a bit, to clean up some mess, and hopefully to
> raise the priority of this bug a bit, I dug up all bugs that seemed
> obvious duplicates of this one. I'm sure there
To help the developers a bit, to clean up some mess, and hopefully to
raise the priority of this bug a bit, I dug up all bugs that seemed
obvious duplicates of this one. I'm sure there might be more dupes...
Anyway, a bug with 8 obvious duplicates certainly confirms that there is
a serious problem
79 matches
Mail list logo