brltty starts twice on boot

Bug #83939 reported by Henrik Nilsen Omma
6
Affects Status Importance Assigned to Milestone
brltty (Ubuntu)
Fix Released
Medium
Unassigned

Bug Description

Binary package hint: brltty

Quote from Mike Pedersen:
(originally from bug 80892)

An interesting new development here. Within the past half hour a new version of brltty was uploaded and added to udev to support the auto detection of braille displays on boot up. Braille now starts successfully for me. A couple small problems remain though:
1. brltty attempted to start twice which made an error appear on the braille display. A press of any key on the braille display dismissed the error.
2. Orca is not currently communicating with brltty so I am currently only able to read text consoles with brltty. This problem could however be a configuration error on my part so I'll give more info when I have it.

Revision history for this message
Luke Yelavich (themuso) wrote :

Mike, I'll likely bet that your display is USB, and you have Brltty configured to start via the init script etc. Brltty now ships with udev rules to automatically start brltty if a usb Braille device is found, so thats probably the second occurrance of brltty accounted for.

To be sure of this, try re-adding the exit line that used to be in /etc/init.d/brltty and see if that makes a difference.

As for Orca, I'll give that a test shortly, and see if I get the same behavior.

Revision history for this message
Henrik Nilsen Omma (henrik) wrote :

When updating I got this error:

cp: cannot stat '/etc/udev/rules.d/85-brltty.rules'

So a missing udev rules file likely causes brltty to start in a way not compatible with Orca (?)

Revision history for this message
Mike Pedersen (michael-pedersen) wrote :

Well, re-adding the exit line certainly changes the behavior. Now when I boot the laptop with the USB display attached brltty continually tries to initialize the display never with any success. This is the exact behavior I reported in the original bug. It almost seems like something that starts up late in the boot process is continually poling the usb ports thus not allowing brltty to start after a certain point. What is strange is that before the recent changes brltty never loaded via the brltty in init.d either which makes me wonder why does it alter the behavior at all?

Changed in brltty:
importance: Undecided → Medium
status: Unconfirmed → Confirmed
Revision history for this message
Henrik Nilsen Omma (henrik) wrote :

Mike, are you still having this problem?

Revision history for this message
Mike Pedersen (michael-pedersen) wrote : Re: [Bug 83939] Re: brltty starts twice on boot
Download full text (60.9 KiB)

> Mike, are you still having this problem?
>
Yes until I remove brltty from /etc/init.d. Even after doing this I
still have the problem of brltty trying to start over and over again if
I have my display connected on boot. The only way on any of my machines
with usb that I can get braille to start is to connect the display after
login. Attached to this message is another syslog.
Mike

Apr 6 07:36:49 desktop syslogd 1.4.1#20ubuntu4: restart.
Apr 6 07:36:49 desktop anacron[2451]: Job `cron.daily' terminated
Apr 6 07:36:49 desktop anacron[2451]: Normal exit (1 job run)
Apr 6 07:37:04 desktop dhclient: DHCPREQUEST on eth1 to 192.168.1.1 port 67
Apr 6 07:37:35 desktop last message repeated 3 times
Apr 6 07:38:35 desktop last message repeated 5 times
Apr 6 07:39:37 desktop last message repeated 5 times
Apr 6 07:40:30 desktop last message repeated 5 times
Apr 6 07:41:41 desktop last message repeated 5 times
Apr 6 07:42:37 desktop last message repeated 5 times
Apr 6 07:43:34 desktop last message repeated 4 times
Apr 6 07:44:38 desktop last message repeated 4 times
Apr 6 07:45:44 desktop last message repeated 5 times
Apr 6 07:46:35 desktop last message repeated 5 times
Apr 6 07:47:35 desktop last message repeated 5 times
Apr 6 07:48:32 desktop last message repeated 3 times
Apr 6 07:49:31 desktop last message repeated 4 times
Apr 6 07:50:32 desktop last message repeated 4 times
Apr 6 07:51:36 desktop last message repeated 5 times
Apr 6 07:52:45 desktop last message repeated 6 times
Apr 6 07:53:38 desktop last message repeated 4 times
Apr 6 07:54:29 desktop last message repeated 3 times
Apr 6 07:55:33 desktop last message repeated 6 times
Apr 6 07:56:45 desktop last message repeated 5 times
Apr 6 07:57:39 desktop last message repeated 3 times
Apr 6 07:58:39 desktop last message repeated 6 times
Apr 6 07:59:45 desktop last message repeated 5 times
Apr 6 08:00:45 desktop last message repeated 3 times
Apr 6 08:01:30 desktop last message repeated 3 times
Apr 6 08:02:45 desktop last message repeated 5 times
Apr 6 08:03:42 desktop last message repeated 4 times
Apr 6 08:04:34 desktop last message repeated 4 times
Apr 6 08:05:31 desktop last message repeated 4 times
Apr 6 08:06:42 desktop last message repeated 6 times
Apr 6 08:07:38 desktop last message repeated 3 times
Apr 6 08:08:39 desktop last message repeated 4 times
Apr 6 08:09:40 desktop last message repeated 4 times
Apr 6 08:10:31 desktop last message repeated 3 times
Apr 6 08:11:34 desktop last message repeated 4 times
Apr 6 08:12:36 desktop last message repeated 4 times
Apr 6 08:13:34 desktop last message repeated 4 times
Apr 6 08:14:33 desktop last message repeated 4 times
Apr 6 08:15:38 desktop last message repeated 5 times
Apr 6 08:16:26 desktop last message repeated 3 times
Apr 6 08:16:59 desktop last message repeated 2 times
Apr 6 08:17:01 desktop /USR/SBIN/CRON[11295]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly)
Apr 6 08:17:15 desktop dhclient: DHCPREQUEST on eth1 to 192.168.1.1 port 67
Apr 6 08:17:29 desktop dhclient: DHCPREQUEST on eth1 to 192.168.1.1 port 67
Apr 6 08:18:27 desktop last message repeated 4 times
Apr 6 08:19:...

Revision history for this message
Mesar Hameed (mhameed) wrote :

I wonder if the solution presented at
http://live.gnome.org/Orca/Braille under the heading "/etc/brltty.conf is overwritten" will also remove this multiple brltty start problem.
It certainly doesnt load twice anymore for me, and neither does it overwrite the config file.

Revision history for this message
Henrik Nilsen Omma (henrik) wrote :

The fix described on the gnome wiki does not seem to have been implemented in Hardy. Is this still a problem or has it been fixed in some other way?

Changed in brltty:
status: Confirmed → Incomplete
Revision history for this message
Luke Yelavich (themuso) wrote :

The problem has been fixed another wy. I'm making packages available for gutsy users to be sure that it is fixed.

Mike, are you still having this issue in hardy?

Revision history for this message
Henrik Nilsen Omma (henrik) wrote :

Thanks Luke :)

Changed in brltty:
status: Incomplete → Fix Released
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.