Le mercredi 29 juin à 14:00, Didier Spaier a écrit :
> 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
On 7/20/2016 11:59 AM, Dave Mielke wrote:
[quoted lines by Chevelle on 2016/06/28 at 23:05 -0400]
I downloaded brltty-win-5.4-1-libusb-1.0.exe. Microsoft Security
Essentials flags Win32/Maltule.c!cl; as a threat. Not sure if it is,
but I let it remove it.
I've asked others to look at the fi
[quoted lines by Chevelle on 2016/06/28 at 23:05 -0400]
>I downloaded brltty-win-5.4-1-libusb-1.0.exe. Microsoft Security
>Essentials flags Win32/Maltule.c!cl; as a threat. Not sure if it is,
>but I let it remove it.
I've asked others to look at the file, and they aren't finding anything. We
fi
Dave Mielke writes:
> [quoted lines by Samuel Thibault on 2016/07/04 at 21:54 +0200]
>
>>in Debian we do use a udev rule for 0403/6001 because there are popular
>>devices which use this generic ID.
>
> Do you, then, allow all generic adapter rules in?
No. I should probably explain that what S
[quoted lines by Samuel Thibault on 2016/07/04 at 21:54 +0200]
>in Debian we do use a udev rule for 0403/6001 because there are popular
>devices which use this generic ID.
Do you, then, allow all generic adapter rules in? If you only allow this one,
how do you filter the others out? Does the u
Dave Mielke, on Mon 04 Jul 2016 09:27:38 -0400, wrote:
> [quoted lines by Samuel Thibault on 2016/07/04 at 07:26 +0200]
>
> >> >I see that the md driver was added to the 0403/6001 USB ID autodetection
> >> >udev rule. Is it really safe to add it? (we used to have issues with at,
> >> >ce, and mm,
[quoted lines by Samuel Thibault on 2016/07/04 at 07:26 +0200]
>> >I see that the md driver was added to the 0403/6001 USB ID autodetection
>> >udev rule. Is it really safe to add it? (we used to have issues with at,
>> >ce, and mm, which we disabled in the Debian packaging)
>>
>> As long as only
Samuel Thibault writes:
> Dave Mielke, on Sun 03 Jul 2016 22:16:58 -0400, wrote:
>> [quoted lines by Samuel Thibault on 2016/07/03 at 20:51 +0200]
>> >I see that the md driver was added to the 0403/6001 USB ID autodetection
>> >udev rule. Is it really safe to add it? (we used to have issues with
Dave Mielke, on Sun 03 Jul 2016 22:16:58 -0400, wrote:
> [quoted lines by Samuel Thibault on 2016/07/03 at 20:51 +0200]
> >I see that the md driver was added to the 0403/6001 USB ID autodetection
> >udev rule. Is it really safe to add it? (we used to have issues with at,
> >ce, and mm, which we dis
[quoted lines by Samuel Thibault on 2016/07/03 at 20:51 +0200]
>I see that the md driver was added to the 0403/6001 USB ID autodetection
>udev rule. Is it really safe to add it? (we used to have issues with at,
>ce, and mm, which we disabled in the Debian packaging)
As long as only non-generic ru
Hello,
I see that the md driver was added to the 0403/6001 USB ID autodetection
udev rule. Is it really safe to add it? (we used to have issues with at,
ce, and mm, which we disabled in the Debian packaging)
Samuel
___
This message was sent via the BRLT
[quoted lines by Didier Spaier on 2016/06/30 at 14:38 +0200]
>(and sorry to have bothered you with this issue in two voicemail messages).
Why would you be sorry? I didn't realize the server was having problems until
you made me aware of it. Thank you.
>To clarify, in the source tarball I sent t
On 29/06/2016 16:27, Dave Mielke wrote:
> [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/
(message initially sent on 29/06/2016 13:49 UTC with in CC
Philippe DELAVALADE and Patrick J. VOLKERDING)
On 29/06/2016 14:00 (12:00 UTC), Didier Spaier wrote:
> Meanwhile I just realized that I sent to Philippe a package built on
> Slint64-14.2 but he has 14.1 as that (triggered a version misma
Le mercredi 29 juin à 14:00, Didier Spaier a écrit :
> 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
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
[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
[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
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
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
[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/
[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
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 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 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
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
[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 03:46, Dave Mielke wrote:
> BRLTTY-5.4 has been released. As always, it can be downloaded from:
I made a package for Slint64-14.2 including a startup script and
the udev rules.
In dmesg's output and /var/log/messages I see:
Jun 29 08:10:03 didier kernel: <27>[6
maybe time to virus scan the vm?
Den 2016-06-29 kl. 05:41, skrev Dave Mielke:
[quoted lines by mattias on 2016/06/29 at 05:35 +0200]
hm dave do you have viruses in your own software??
Not that I know of. The Windows system on which the build is done is a virtual
machine only used by me, and,
[quoted lines by mattias on 2016/06/29 at 05:35 +0200]
>hm dave do you have viruses in your own software??
Not that I know of. The Windows system on which the build is done is a virtual
machine only used by me, and, really, only for brltty testing ande builds. I'll
gladly accept any advice on h
hm dave do you have viruses in your own software??
sounds not serious
Den 2016-06-29 kl. 05:29, skrev Dave Mielke:
[quoted lines by Chevelle on 2016/06/28 at 23:05 -0400]
I downloaded brltty-win-5.4-1-libusb-1.0.exe. Microsoft Security
Essentials flags Win32/Maltule.c!cl; as a threat. Not s
[quoted lines by Chevelle on 2016/06/28 at 23:05 -0400]
>I downloaded brltty-win-5.4-1-libusb-1.0.exe. Microsoft Security
>Essentials flags Win32/Maltule.c!cl; as a threat. Not sure if it is,
>but I let it remove it.
Googling it says that it's a Trojan that can do ransomware. Doesn't look good.
FYI
I downloaded brltty-win-5.4-1-libusb-1.0.exe. Microsoft Security
Essentials flags Win32/Maltule.c!cl; as a threat. Not sure if it is,
but I let it remove it.
On 6/28/2016 9:46 PM, Dave Mielke wrote:
BRLTTY-5.4 has been released. As always, it can be downloaded from:
http
BRLTTY-5.4 has been released. As always, it can be downloaded from:
http://brltty.com/
Here's a summary of the significant things that've changed since 5.3.1:
Core changes:
The Delayed Cursor Tracking feature (and preference) has been added.
Stuck keys are now automaticall
34 matches
Mail list logo
