Re: [orca-list] Problem with brltty
- From: Michael Whapples <mwhapples aim com>
- To: orca-list gnome org
- Subject: Re: [orca-list] Problem with brltty
- Date: Wed, 05 Dec 2007 17:46:15 +0000
Hello,
If the problem is what I had once before when I used ubuntu, it is that
brltty gets started twice, once when the display is detected, and once
when the start-up scripts starts it.
I think I solved it (I am going from memory as it was some time ago I
used ubuntu (and that was feisty)) I removed the brltty udev rule
(probably removing it from the start-up scripts would work as well).
To explain the two above ways brltty is started:
udev is a system which detects new hardware and performs a task
accordingly, so can start brltty when a braille display is plugged in
(but this requires the connection to allow automatic detection of
devices, serial ports don't, I think, so if a braille display is
connected by serial brltty won't be started this way).
The start-up scripts will always start brltty (regardless of connection
type) when the system starts.
Hope this helps you with working something out.
From
Michael Whapples
On Wed, 2007-12-05 at 17:51 +0100, Ollie wrote:
Hello list,
since I installed Ubuntu 7.10, I've experienced a strange problem with brltty.
When I boot, brltty seems to start regularly (I get brltty 3.72 on my
display), then a message appears that says:
startup problem
When I log in and Orca starts, I disconnect the braille display for a
second or so and then reconnect it, and the display shows "screen not
in text mode", instead of the "Welcome to Orca" message.
If I press Alt+f1, the menu shows regularly, and after that brltty
seems to work perfectly well.
Can it be avoided?
Thanks and cheers,
Ollie
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]