After update keyboard bluenot working

Bug #423568 reported by Onno Timmerman
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
bluez (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Binary package hint: bluetooth

keyboard: Logitec diNivo Edge
laptop: E4300 Dell (has bluetooth onboard)

Since this morning keyboaurd can't connect (3 sept 2009)
Normaly the keybaord get auto connected and I don't need to perform steps but today no connection
Also checked with Mobile Nokia, no connection
Bluetooth is on in the laptop. (checked)

steps:
a: click on the bluetooth icon
b: setup new device
c: find the keyboard and select it
d: ask for pin and type in the pin in the keyboard
Z : Nothing happens where normaly you get connected

Keyboard bluetooth light keeps blinking

Revision history for this message
Mario Limonciello (superm1) wrote :

Hi, thanks for the bug report.

Couple of things:

Please provide these:
1) lsusb output
2) hciconfig output
3) rfkill list output

Was this a fresh boot, or suspend/resume cycle of right after updates?

Changed in bluez (Ubuntu):
status: New → Incomplete
Revision history for this message
Onno Timmerman (onno-filosofie) wrote : Re: [Bug 423568] Re: After update keyboard bluenot working

Hi,

This was after a fresh boot, Ubuntu did do a disk check so I'm sure.
Atlhough yesterday I used all of my battery.

In attach the files you asked. However rfkill is a command that neither
I or command line or apt-get knows!

I'm now using my keyboard via a bluthoot usb dongle.

Onno

Mario Limonciello schreef:
> Hi, thanks for the bug report.
>
> Couple of things:
>
> Please provide these:
> 1) lsusb output
> 2) hciconfig output
> 3) rfkill list output
>
> Was this a fresh boot, or suspend/resume cycle of right after updates?
>
> ** Changed in: bluez (Ubuntu)
> Status: New => Incomplete
>

Revision history for this message
Leo Arias (elopio) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. We are sorry that we do not always have the capacity to look at all reported bugs in a timely manner. There have been many changes in Ubuntu since that time you reported the bug and your problem may have been fixed with some of the updates. It would help us a lot if you could test a current, supported, Ubuntu version. If you can test it, and it is still an issue, we would appreciate if you could upload updated logs by running apport-collect 423568, and any other logs that are relevant for this particular issue.

Revision history for this message
Leo Arias (elopio) wrote :

We'd like to figure out what's causing this bug for you, but we haven't heard back from you in a while. Could you please provide the requested information? Thanks!

Revision history for this message
Leo Arias (elopio) wrote :

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!

Changed in bluez (Ubuntu):
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.