Hi Chime,
In response to the first part of your message, quoted in part below
for context: the default UI output format of apt has indeed changed,
however if you use the apt-get command (note the dash get suffix,
without a space) then it should continue to emit the previous format
that you are fam
wrote:
>
>
> > On Dec 20, 2023, at 13:21, Geoff Shang wrote:
> >
> > On Tue, 28 Nov 2023, James Addison wrote:
> >
> >> To do that, the first step is to enable a sources.list entry for debug
> >> symbol packages, then to install the gdb and espeakup-d
kworm-debug, and
only includes packages from main. More complete instructions are
available at https://wiki.debian.org/HowToGetABacktrace - note that I
don't think we should need to recompile any packages in this case,
because debug symbol packages should be available on arm64.
> -Origina
On Mon, 28 Aug 2023 at 10:46, Geoff Shang wrote:
>
> On Mon, 24 Apr 2023, James Addison wrote:
>
> > Working towards a better backtrace is a good recommendation. I'd also
> > like to mention that there are existing Debian bookworm debug symbol
> > packages availa
On Sun, 30 Apr 2023 at 01:10, James Addison wrote:
>
> I don't have much to (bug)report here yet, but have begun using
> espeakup as a screen reader via Orca in GNOME. CPU usage on the
> machine seemed relatively high, and at times text input became
> unresponsive (both in
On Tue, 25 Apr 2023 at 10:20, James Addison wrote:
>
> On Mon, 24 Apr 2023 at 23:38, James Addison wrote:
> >
> > On Apr 20, 2023, at 08:47:11, Jason White wrote:
> > >
> > > Perhaps the following would also be worth trying:
> > >
> > > R
On Mon, 24 Apr 2023 at 23:38, James Addison wrote:
>
> On Apr 20, 2023, at 08:47:11, Jason White wrote:
> >
> > Perhaps the following would also be worth trying:
> >
> > Rebuild Espeakup with compiler optimizations turned off and with debug
> > symbols ena
On Apr 20, 2023, at 08:47:11, Jason White wrote:
>
> Perhaps the following would also be worth trying:
>
> Rebuild Espeakup with compiler optimizations turned off and with debug
> symbols enabled. This might produce a beter gdb backtrace if you connect to
> the process when it's failing to gener
On Tue, 11 Apr 2023 at 18:27, Frank Carmickle wrote:
>
> On Apr 11, 2023, at 13:19, James Addison wrote:
> > That could be a useful clue. Which of those three systems, if any,
> > are multi-processor?
>
> I suspected such a thing and so today I have been running the qem
On Mon, 10 Apr 2023 at 21:07, Frank Carmickle wrote:
>
> On Mar 30, 2023, at 10:49, James Addison wrote:
> >
> > Yep, bugs with unpredictable timing can be particularly hard to track
> > down. I noticed some references to process threads in one of your
> > previ
On Wed, 29 Mar 2023 at 20:14, Frank Carmickle wrote:
> I guess you missed my followup message that it still does stop speaking. I'm
> trying to notice as much as I can about the environment when it stops
> speaking.
I did read that message - it seemed possible to me that configuring a
language
Ok, that's cautiously promising.
The next suggestion is maybe a bit annoying: try undoing or commenting-out
the language selection and checking whether the previous error-prone
behaviour returns.
I haven't been able to figure out why choosing a language in the config
file would make a difference
s,
>
> Thanks for this. It does not print any information when speaking stops.
> It does print that it received the hangup signal, which is what I sent to
> kill the process.
>
> What shall we add to a build to gain more insight?
>
> Thank you,
> --FC
>
>
>
>
&
On Mon, 20 Mar 2023 16:31:54 -0400, Frank wrote:
> I've reported this before, and I believe we had a fix for it. I just saw it
> happen again. This time it's bookworm arm64 . I can't remember what info was
> needed to track this down. Let me know what I can do please.
Hi Frank,
If you run the e
14 matches
Mail list logo
