Hi
Samuel Thibault schrieb am 28.02.2017, 23:28 +0100:
>Sebastian Humenda, on lun. 27 févr. 2017 14:30:19 +0100, wrote:
>> Sebastian Humenda schrieb am 20.02.2017, 11:13 +0100:
>> Ok, seems hard to reproduce. Here's another bt.
>Does the change at least reduce the frequency of happening?
That is r
Sebastian Humenda, on lun. 27 févr. 2017 14:30:19 +0100, wrote:
> Sebastian Humenda schrieb am 20.02.2017, 11:13 +0100:
> >>Ok, we can wait more, no pb :)
> >No crashes, I think it's safe.
> Ok, seems hard to reproduce. Here's another bt.
Does the change at least reduce the frequency of happening?
Hi
Sebastian Humenda schrieb am 20.02.2017, 11:13 +0100:
>>Ok, we can wait more, no pb :)
>No crashes, I think it's safe.
Ok, seems hard to reproduce. Here's another bt.
Thanks
Sebastian
===
Thread 8 (Thread 0x7f6285632700 (LWP 16207)):
#0 0x7f629273e536 in futex_abstimed_wait_cancelable (
Samuel Thibault schrieb am 13.02.2017, 10:52 +0100:
>Sebastian Humenda, on Mon 13 Feb 2017 10:47:33 +0100, wrote:
>> I haven't encountered any issues yet. It is rather hard to say whether it is
>> fixed, because the bug is hard to reproduce. However, there have been no
>> further crashes so far.
Sebastian Humenda, on Mon 13 Feb 2017 10:47:33 +0100, wrote:
> Samuel Thibault schrieb am 12.02.2017, 12:15 +0100:
> […]0
> >> > >Sebastian Humenda, on Sun 05 Feb 2017 21:02:37 +0100, wrote:
> >> > >> I'm not sure whether the issue is actually in BRLTTY or espeak-ng, but
> >> > >> I couldn't encoun
Hello
Samuel Thibault schrieb am 12.02.2017, 12:15 +0100:
[…]0
>> > >Sebastian Humenda, on Sun 05 Feb 2017 21:02:37 +0100, wrote:
>> > >> I'm not sure whether the issue is actually in BRLTTY or espeak-ng, but
>> > >> I couldn't encounter any issues while using speech-dispatcher with
>> > >> espeak
Hello,
Samuel Thibault, on Thu 09 Feb 2017 10:37:17 +0100, wrote:
> Sebastian Humenda, on Thu 09 Feb 2017 10:23:36 +0100, wrote:
> > Samuel Thibault schrieb am 08.02.2017, 23:49 +0100:
> > >Sebastian Humenda, on Sun 05 Feb 2017 21:02:37 +0100, wrote:
> > >> I'm not sure whether the issue is actual
Sebastian Humenda, on Thu 09 Feb 2017 10:23:36 +0100, wrote:
> Samuel Thibault schrieb am 08.02.2017, 23:49 +0100:
> >Sebastian Humenda, on Sun 05 Feb 2017 21:02:37 +0100, wrote:
> >> I'm not sure whether the issue is actually in BRLTTY or espeak-ng, but
> >> I couldn't encounter any issues while u
Hi
Samuel Thibault schrieb am 08.02.2017, 23:49 +0100:
>Sebastian Humenda, on Sun 05 Feb 2017 21:02:37 +0100, wrote:
>> I'm not sure whether the issue is actually in BRLTTY or espeak-ng, but
>> I couldn't encounter any issues while using speech-dispatcher with
>> espeak-ng yet.
>
>Ok. I'm afraid
Hello,
Sebastian Humenda, on Sun 05 Feb 2017 21:02:37 +0100, wrote:
> I'm not sure whether the issue is actually in BRLTTY or espeak-ng, but
> I couldn't encounter any issues while using speech-dispatcher with
> espeak-ng yet.
Ok. I'm afraid that might be an issue with the way BRLTTY uses espeak
Hi
Samuel Thibault schrieb am 06.02.2017, 0:21 +0100:
>Could you install:
[...]
>brltty-dbgsym
>
>> #0 0x7f3fec3c7540 in () at /usr/lib/x86_64-linux-gnu/libasound.so.2
>
>and libasound2-dbgsym
libasound2 was already installed, do you have any idea why the symbols don't
show up?
The full BT
Hello,
Could you install:
Sebastian Humenda, on Sun 05 Feb 2017 21:02:37 +0100, wrote:
> #1 0x5653f0d0437c in asyncExecuteIoCallback ()
brltty-dbgsym
> #0 0x7f3fec3c7540 in () at /usr/lib/x86_64-linux-gnu/libasound.so.2
and libasound2-dbgsym
Samuel
Package: brltty-espeak
Version: 5.4-6
Severity: important
Hi
Every now and then, BRLTTY crashes. It looks as if there is an issue while
emitting speech using espeak-ng. I'm not sure whether the issue is actually in
BRLTTY or espeak-ng, but I couldn't encounter any issues while using
speech-dispat
13 matches
Mail list logo
