the Fedora repos (i.e. not main or gnome-46 branch). The
issue persists.
So, once again, can someone help me solve this issue?
Thanks,
Frans-Willem
On 05-03-2024 15:07, Frans-Willem Post wrote:
Hello all,
Sorry for the noise. After updating the display's firmware version to
5.82-26 inside a
Hello all,
Sorry for the noise. After updating the display's firmware version to
5.82-26 inside a Windows virtual machine, the display is back in working
order.
Issue solved, kind regards,
Frans-Willem
On 05-03-2024 10:51, Frans-Willem Post wrote:
Dear list,
Running BRLTTY 6.6 (and Orca
Dear list,
Running BRLTTY 6.6 (and Orca main) under Fedora 39 with X11.
Since today, my Focus 40 Blue braille display no longer works. Fedora
received an update to kernel 6.7.7, but the issue is present with kernel
6.7.6, too.
I have checked the USB-cable and the connections; they are all
/02/24 10:04, Frans-Willem Post wrote:
Hello Brandt,
I found the same thing; that Fedora doesn't enable some services by
default. That can be fixed, though.
sudo systemctl enable --now brltty.service;
should enable the BrlTTY service permanently.
Good luck and kind regards,
Frans-Willem
Hello Brandt,
I found the same thing; that Fedora doesn't enable some services by
default. That can be fixed, though.
sudo systemctl enable --now brltty.service;
should enable the BrlTTY service permanently.
Good luck and kind regards,
Frans-Willem
On 24-02-2022 08:43, Brandt Steenkamp
Thanks for the quick response. I'll be patient and consider my options.
Kind regards,
Frans-Willem Post
On 29-01-2022 22:11, Samuel Thibault wrote:
Hello,
Frans-Willem Post, le sam. 29 janv. 2022 22:08:49 +0100, a ecrit:
Is there a possibility to use the Braille input keys of my Freedom
and applications has been no problem.
Orca and BrlTTY both work very well. Braille input, however, does not
because of the absence of an X-server.
Is there a possibility to use the Braille input keys of my Freedom
Scientific Focus 40 Blue under Wayland?
Thanks and kind regards,
Frans-Willem
On 22-12-2020 23:55, Samuel Thibault wrote:
we'd thus need a brltty log with -l server to see what
it is doing.
Samuel
See attached log file. I had to Alt-Tab into another window and back, to
get xbrlapi going in the terminal where I started it.
This time, I typed 'a', 'b', 'c', three
On 22-12-2020 23:25, Samuel Thibault wrote:
Frans-WIllem Post, le mar. 22 déc. 2020 23:20:27 +0100, a ecrit:
I ran the strace command (see attached log).
Did you not get anything on stderr? In the log I see
write(2, "grabbed 0x02406b78\n", 19)= 19
write(2, "win 0x024
On 22-12-2020 23:11, Samuel Thibault wrote:
Frans-WIllem Post, le mar. 22 déc. 2020 22:59:17 +0100, a ecrit:
Now I'm trying to get xbrlapi up and running - but it does nothing. When I
start it like this: "xbrlapi -n -v", watch that terminal and proceed to type
in another termi
Hello Samuel,
On 22-12-2020 21:13, Samuel Thibault wrote:
Hello,
Frans-WIllem Post, le mar. 22 déc. 2020 18:14:49 +0100, a ecrit:
The physical input keys are OK; they work when I'm in BrlTTY's preferences
menu and need to return (dot8). They work as expected (backspace and enter
Hello Alexander,
On 21-12-2020 17:09, Alexander Epaneshnikov wrote:
21.12.2020 18:24, Frans-WIllem Post пишет:
Hello,
On 21-12-2020 15:10, Alexander Epaneshnikov wrote:
21.12.2020 9:56, Frans-WIllem Post пишет:
Hello all,
Would someone be able to help me with getting BrlTTY running
Hello,
On 21-12-2020 15:10, Alexander Epaneshnikov wrote:
21.12.2020 9:56, Frans-WIllem Post пишет:
Hello all,
Would someone be able to help me with getting BrlTTY running on Fedora
33, see below? My braille display says "Not in text mode" while in
GUI. On the TTY-console
Hello all,
Would someone be able to help me with getting BrlTTY running on Fedora
33, see below? My braille display says "Not in text mode" while in GUI.
On the TTY-consoles, however, it works perfectly.
Thank you very much.
Frans-Willem Post
On 15-12-2020 21:41, Frans-WIllem
entific Focus 3" by lsusb.
Thanks for your help!
Kind regards,
Frans-Willem Post
--
Met de .ASC-bijlage(n) kan uw e-mailprogramma garanderen dat bovenstaand
bericht van mij afkomstig is, en onderweg niet door derden is aangepast.
OpenPGP_0xC0932DFE211E9A9D.asc
Description:
Hello again, success!
On 08-08-2020 18:06, Dave Mielke wrote:
> Did you try rebooting, just in case that matters? All you should need to do is
> switch to a different table and back again, but it wouldn't hurt to test
> rebooting.
Yes, I rebooted in between tries. It didn't matter.
>> Does the
Hello again,
On 08-08-2020 16:34, Dave Mielke wrote:
> I just checked that code. It wasn't working properly, and has now been fixed.
Thank you.
> Please update to the latest apk.The update mechanism through the app's
> interface is very convenient. It
works very well.
> The right place to put
Hello again,
On 07-08-2020 16:41, Dave Mielke wrote:
> Not easily because the list is hard-coded. This is so that a proper name for
> each tale, rather than its file name, can be displayed.OK, I understand.
> In theory (though I haven't tested this recently), you can use the same file
> name as
Dear all,
Recently, I received a question about using a custom text table on
BRLTTY for Android. I therefore installed the brltty-latest.apk,
configured it and found it working as expected.
There is a (quite extensive) list of predefined text tables to use - but
is there a possibility to use
Have tested the brltty package in bionic-proposed as instructed in
comment #12: v5.5-4ubuntu2.0.1
It works as expected.
After commenting out the "api-parameters Auth=keyfile" line in
brltty.conf and restarting the machine (just to be sure), my braille
display works completely in both text
Have tested the brltty package in bionic-proposed as instructed in
comment #12: v5.5-4ubuntu2.0.1
It works as expected.
After commenting out the "api-parameters Auth=keyfile" line in
brltty.conf and restarting the machine (just to be sure), my braille
display works completely in both text
Thanks to a member of the BrlTTY mailing list, my problem is solved. It
seems that the default authorization of BrltTTY under Ubuntu was no
longer working. Providing it with a dummy key-file was enough to get it
back to work - instantly.
The display came back to life immediately after these
Thanks to a member of the BrlTTY mailing list, my problem is solved. It
seems that the default authorization of BrltTTY under Ubuntu was no
longer working. Providing it with a dummy key-file was enough to get it
back to work - instantly.
The display came back to life immediately after these
Dear John,
Thank you very very very much! Your instructions worked perfectly.
The display came back to life immediately after editing the conf-file, a
simple "sudo touch /etc/brlapi.key" and "sudo chmod 0644 /etc/brlapi.key".
Kind regards,
Frans-Willem Post
On 23-07-18 10:3
don't
know).
Can someone help me get the display back up under GNOME (i.e. under X)?
Thank you very much,
Frans-Willem Post
signature.asc
Description: OpenPGP digital signature
___
This message was sent via the BRLTTY mailing list.
To post a mes
.
This is continuous, while the display reads "Screen not in text mode".
Ultimately, the display turns itself off (or BrlTTY does this, I don't
know).
Can someone help me get the display back up under GNOME (i.e. under X)?
Thank you very much,
Frans-Willem Post
signature.asc
Descriptio
Have just replayed the upgrade in a VirtualBox VM using a clean install
of Ubuntu 18.04.
Before the upgrade (of policy-kit), the braille display works (both
output and input).
After the upgrade and reboot, the same errors appear in /var/log/syslog:
Jul 18 11:49:43 test-VirtualBox brltty[409]:
Have just replayed the upgrade in a VirtualBox VM using a clean install
of Ubuntu 18.04.
Before the upgrade (of policy-kit), the braille display works (both
output and input).
After the upgrade and reboot, the same errors appear in /var/log/syslog:
Jul 18 11:49:43 test-VirtualBox brltty[409]:
Public bug reported:
$ lsb_release -rd
Description:Ubuntu 18.04 LTS
Release:18.04
$ apt-cache policy brltty
brltty:
Installed: 5.5-4ubuntu2
Candidate: 5.5-4ubuntu2
Version table:
*** 5.5-4ubuntu2 500
500 http://nl.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
Public bug reported:
$ lsb_release -rd
Description:Ubuntu 18.04 LTS
Release:18.04
$ apt-cache policy brltty
brltty:
Installed: 5.5-4ubuntu2
Candidate: 5.5-4ubuntu2
Version table:
*** 5.5-4ubuntu2 500
500 http://nl.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
I'm sorry, but I no longer have the crash-report.
I performed a clean install of Ubuntu (now 18.04) and the bug is gone.
Next to the release difference (17.10 to 18.04), I did not install the
nVidia proprietary driver.
For me, this problem's solved.
--
You received this bug notification
I'm sorry, but I no longer have the crash-report.
I performed a clean install of Ubuntu (now 18.04) and the bug is gone.
Next to the release difference (17.10 to 18.04), I did not install the
nVidia proprietary driver.
For me, this problem's solved.
--
You received this bug notification
Finally making some headway, I tried the following:
1. boot the system.
2. at the graphical login prompt, switch to another console (Ctrl+Alt+F2)
3. login
4. logout
The screen displays the GUI login prompt but hangs. I can still login on
this console using the braille display.
5. Log in from
Finally making some headway, I tried the following:
1. boot the system.
2. at the graphical login prompt, switch to another console (Ctrl+Alt+F2)
3. login
4. logout
The screen displays the GUI login prompt but hangs. I can still login on
this console using the braille display.
5. Log in from
Trying to reproduce on different system (laptop).
Same Ubuntu release and GNOME/my desktop system, GDM packages.
$ lsb_release -rd
Description:Ubuntu 17.10
Release:17.10
$ apt-cache policy gdm3
gdm3:
Installed: 3.26.1-3ubuntu3
Candidate: 3.26.1-3ubuntu3
Version table:
***
Trying to reproduce on different system (laptop).
Same Ubuntu release and GNOME/my desktop system, GDM packages.
$ lsb_release -rd
Description:Ubuntu 17.10
Release:17.10
$ apt-cache policy gdm3
gdm3:
Installed: 3.26.1-3ubuntu3
Candidate: 3.26.1-3ubuntu3
Version table:
***
Trying to pin this bug down, I deactivated nVIDIA's driver, reactivated
nouveau and rebooted.
Sadly, the problem still persists.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1764643
Title:
Logout
Trying to pin this bug down, I deactivated nVIDIA's driver, reactivated
nouveau and rebooted.
Sadly, the problem still persists.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm3 in Ubuntu.
https://bugs.launchpad.net/bugs/1764643
Thanks.
I uninstalled LIRC, just to be on the safe side.
Orca is necessary for my using the computer.
I uncommented the line #WaylandEnable=false and rebooted.
The problem still persists.
Then, without logging in graphically, I switched to tty3 (Ctrl+Alt+F3).
Logged in, executed a single command
Thanks.
I uninstalled LIRC, just to be on the safe side.
Orca is necessary for my using the computer.
I uncommented the line #WaylandEnable=false and rebooted.
The problem still persists.
Then, without logging in graphically, I switched to tty3 (Ctrl+Alt+F3).
Logged in, executed a single command
As requested, I killed both gdm3 and gnome-shell.
The bug-ids are #1764672 and #1764674 respectively.
Thanks.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm3 in Ubuntu.
https://bugs.launchpad.net/bugs/1764643
Title:
Logout
As requested, I killed both gdm3 and gnome-shell.
The bug-ids are #1764672 and #1764674 respectively.
Thanks.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1764643
Title:
Logout after console use
I followed your instructions; commented out the line in
/etc/apport/crashdb.conf, reproduced the problem, but there are no
crash-files in /var/crash.
Sorry.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm3 in Ubuntu.
I followed your instructions; commented out the line in
/etc/apport/crashdb.conf, reproduced the problem, but there are no
crash-files in /var/crash.
Sorry.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
Hello,
Ubuntu 17.10 64 bit
GNOME 3.26.2
nVIDIA GeForce GT620 driver 384.111
X-server 11.0, v1.19.5
Orca + braille enabled
$ lsb_release -rd
Description:Ubuntu 17.10
Release:17.10
$ apt-cache policy gdm3
gdm3:
Installed: 3.26.1-3ubuntu3
Candidate:
Public bug reported:
Hello,
Ubuntu 17.10 64 bit
GNOME 3.26.2
nVIDIA GeForce GT620 driver 384.111
X-server 11.0, v1.19.5
Orca + braille enabled
$ lsb_release -rd
Description:Ubuntu 17.10
Release:17.10
$ apt-cache policy gdm3
gdm3:
Installed: 3.26.1-3ubuntu3
Candidate:
Public bug reported:
Hello,
Ubuntu 17.10 64 bit
GNOME 3.26.2
nVIDIA GeForce GT620 driver 384.111
X-server 11.0, v1.19.5
Orca + braille enabled
$ lsb_release -rd
Description:Ubuntu 17.10
Release:17.10
$ apt-cache policy gdm3
gdm3:
Installed: 3.26.1-3ubuntu3
Candidate:
would tell
This was indeed the case. In my X-environment, I can not type the
characters not listed in the keymap, but on a real TTY-console, I can.
Thank you for helping me understand,
Frans-Willem Post
The Netherlands
On 18-08-17 20:40, Frans-Willem Post wrote:
Hello,
Using BRLTTY 5.3.1 on
en braille?
Alvast bedankt voor jullie hulp,
Frans-Willem Post
--
BLXF - BLinuXForum MailingList
Voor hulp of in- en uitschrijven, stuur het woord help naar:
blxf-request at lists.tuxfamily.org
Archief raadplegen:
http://listengine.tuxfamily.org/lists.tuxfamily.org/blxf
of
http://www.mail
49 matches
Mail list logo
