blink (blinkd for keyboard LEDs) doesn't work in 8.10

Bug #295095 reported by stinkinrich88
16
This bug affects 2 people
Affects Status Importance Assigned to Milestone
blinkd (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

Binary package hint: blinkd

Hello,

I used to be able to use blink with no problems at all in Hardy. Now I have a clean install of Intrepid and blink (0.4.8-0.1) no longer works. No output is given, even as root, and no LEDs flash. I emailed the dude that made blink and he didn't have much to say but he wanted to know what was in my /var/log/syslog file, so here's an extract:

Nov 7 10:55:39 ubunrich blinkd: Received appropriate blink rate 0x80 (pid 6766)
Nov 7 10:55:39 ubunrich blinkd: current_led: 2 (pid 6766)
Nov 7 10:55:39 ubunrich blinkd: new_rate: 0 (pid 6766)

The above is repeated many times at the end of the log.

Not sure if this is related, but Intrepid did not map my scrolllock key properly by default. I had to configure it manually using the following solution:

http://linuxtechie.wordpress.com/2008/04/07/getting-scroll-lock-to-work-in-ubuntu/

Revision history for this message
billnomates (billygotmail) wrote :

Yeah, this happens to me too, and my scroll-lock key also didn't work on first install.

I get an output though, it say something like "Connection refused". I'll double check later as I am at work right now.

Changed in blinkd:
status: New → Incomplete
Revision history for this message
Kyle Rankin (greenfly-greenfly) wrote :

This bug is also affecting me. Blinkd functioned fine with Hardy and stopped working after the Intrepid upgrade. I notice that when I resume my laptop that the LEDs will blink for a moment up until I see the locked screen login prompt. I haven't had a chance to test yet, but I'm wondering whether it might work if I boot without X altogether.

Revision history for this message
Kyle Rankin (greenfly-greenfly) wrote :

To add extra data points, if I shift to VT1 (Ctrl-Alt-F1) then the blinking works. It only stops the moment I change back to X. I tried starting X by itself to see if that affected it and it didn't. In fact the blinking only stopped once gdm started and continued through the rest of the desktop initialization process.

Revision history for this message
jenom (jenom) wrote :

I stumbled across the same same thing and ended up here but when I configured a second keyboard layout I discovered something. There is an option which lets you feedback the sate of your keyboard (i.e. the current layout) by switching the scroll lock led and this works fine.

Changed in blinkd:
status: Incomplete → Confirmed
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.