[quoted lines by Didier Spaier on 2016/06/29 at 08:45 +0200]
>In dmesg's output and /var/log/messages I see:
>
>Jun 29 08:10:03 didier kernel: <27>[6.536711] udevd[581]: invalid
>key/value pair in file /lib/udev/rules.d/40-usb-brltty.rules on line 450,
>starting at character 1 ('R')
Line 45
On 29/06/2016 08:59, Dave Mielke wrote:
> [quoted lines by Didier Spaier on 2016/06/29 at 08:45 +0200]
>
>> In dmesg's output and /var/log/messages I see:
>>
>> Jun 29 08:10:03 didier kernel: <27>[6.536711] udevd[581]: invalid
>> key/value pair in file /lib/udev/rules.d/40-usb-brltty.rules on
On 29/06/2016 09:27, Didier Spaier wrote:
> On 29/06/2016 08:59, Dave Mielke wrote:
>> [quoted lines by Didier Spaier on 2016/06/29 at 08:45 +0200]
>>
>>> In dmesg's output and /var/log/messages I see:
>>>
>>> Jun 29 08:10:03 didier kernel: <27>[6.536711] udevd[581]: invalid
>>> key/value pair
[quoted lines by Didier Spaier on 2016/06/29 at 10:50 +0200]
>Bad news:
>1. I do not have the message from udevd anymore but...
>2. Philippe's Braille display does not work at all after upgrading.
> Unfortunately he can't investigate further right now (no sighted
> person around to help so he
On 29/06/2016 11:51, Dave Mielke wrote:> [quoted lines by Didier Spaier on
2016/06/29 at 10:50 +0200]
>
>> Bad news:
>> 1. I do not have the message from udevd anymore but...
>> 2. Philippe's Braille display does not work at all after upgrading.
>> Unfortunately he can't investigate further r
[quoted lines by Didier Spaier on 2016/06/29 at 11:58 +0200]
After some tracing, I now know what's going on. Even though brltty does put
itself into the background almost immediately, udev is still killing it. All
processes end up in the same cgroup (control group), and what udev is doing is
ki
Hi,
I'm writing some C++ code on ubuntu, trying to connect to a Papenmeier Braillex
EL 40s and just write some characters on it, for a start. However, when taking
control of the tty using the default tty number
(brlapi_enterTtyMode(BRLAPI_TTY_DEFAULT, NULL)), I get an error: "Can't
determine t
[quoted lines by Didier Spaier on 2016/06/29 at 10:50 +0200]
Did you used to use a udev rules file that worked? If so, could you please post
it?
--
Dave Mielke | 2213 Fox Crescent | The Bible is the very Word of God.
Phone: 1-613-726-0014 | Ottawa, Ontario | http://Mielke.cc/bible/
Hi,
I'm trying to install brltty 5.4 on a system with systemd, but the
necesarry startup files like brltty.service dont appear in the right
places. How can I force the make install to put everything where it
should be?
Regards
Adrian
--
Adri P. van Bloois
[quoted lines by adr...@pa0rda.nl on 2016/06/29 at 13:21 +0200]
>I'm trying to install brltty 5.4 on a system with systemd, but the
>necesarry startup files like brltty.service dont appear in the right
>places. How can I force the make install to put everything where it
>should be?
Please be more
Dave Mielke, on Wed 29 Jun 2016 06:30:14 -0400, wrote:
> All processes end up in the same cgroup (control group), and
> what udev is doing is killing off the whole cgroup after a few
> seconds. So, what we need to do is figure out how to put brltty into
> its own cgroup after ud
On 29/06/2016 13:22, Dave Mielke wrote:
> [quoted lines by Didier Spaier on 2016/06/29 at 10:50 +0200]
>
> Did you used to use a udev rules file that worked? If so, could you please
> post
> it?
I just appended a double quote at end of line #450 as you suggested.
Meanwhile I just realized that
Hello all,
I am trying to connect my Braille display, Esytime 32 Standard, to my
Raspberry Pi 3 runninq Raspbian Jessie.
Configuration, compilation and installation do not tell any serious
error, but when running brltty, nothing append on the Braille display.
However it is correctly detected b
[quoted lines by Samuel Thibault on 2016/06/29 at 13:50 +0200]
>I believe that it's on purpose that udev kills the cgroup, and you are
>not supposed to escape from it. AIUI, you need to determine how to tell
>udev that the start was successful, and thus it shouldn't try to clean
>after start failu
[quoted lines by Arthur BREUNEVAL on 2016/06/29 at 14:19 +0200]
>I am trying to connect my Braille display, Esytime 32 Standard, to my
>Raspberry Pi 3 runninq Raspbian Jessie.
>
>Configuration, compilation and installation do not tell any serious
>error, but when running brltty, nothing append on
[quoted lines by Didier Spaier on 2016/06/29 at 10:50 +0200]
>On 29/06/2016 09:27, Didier Spaier wrote:
>> On 29/06/2016 08:59, Dave Mielke wrote:
>>> [quoted lines by Didier Spaier on 2016/06/29 at 08:45 +0200]
>>>
In dmesg's output and /var/log/messages I see:
Jun 29 08:10:03 didi
Dave Mielke writes:
> [quoted lines by Samuel Thibault on 2016/06/29 at 13:50 +0200]
>
>>I believe that it's on purpose that udev kills the cgroup, and you are
>>not supposed to escape from it. AIUI, you need to determine how to tell
>>udev that the start was successful, and thus it shouldn't try
17 matches
Mail list logo