Re: [orca] Re: (solved) orca's strange behavior in a crowded terminal
On Sun, Sep 03, 2023 at 11:18:49PM +0200, Samuel Thibault wrote: > Alexander Epaneshnikov, le lun. 04 sept. 2023 00:08:42 +0300, a ecrit: > > in order to return this fix, where the correction of the diff algorithm > > should occur in libvte or in orca? > > In vte. Diff algorithms should be done as early as possible to avoid > overflowing the rest. OK. thanks for the answer. if there is any news please keep me posted. for now, I'll just keep this patch locally. > Samuel -- Sincerely, Alexander
Re: [orca] Re: (solved) orca's strange behavior in a crowded terminal
Alexander Epaneshnikov, le lun. 04 sept. 2023 00:08:42 +0300, a ecrit: > in order to return this fix, where the correction of the diff algorithm > should occur in libvte or in orca? In vte. Diff algorithms should be done as early as possible to avoid overflowing the rest. Samuel
Re: [orca] Re: (solved) orca's strange behavior in a crowded terminal
On Sun, Sep 03, 2023 at 09:39:56PM +0200, Jérémy Prego wrote: > hello, hello Jérémy. > I've just found the library that's causing the problem. > > it's the libvte-2.91-0 library in version 0.73.93-1 currently in debian > testing. downgrading to version 0.72.2-3 solves the problem. that happened because bug [1] was fixed in libvte. in fact I think this fix improved more than it got worse, so I'm sad that it was rolled back. > i'm relieved! :) > > I was thinking of making a bug report in debian against the package, but I > confess I don't know what to put in it. A question for Samuel. in order to return this fix, where the correction of the diff algorithm should occur in libvte or in orca? because as a vte-based terminal every day user, I can't imagine life without this patch. ps Well, this patch has a difficult fate. > Jerem [1]: https://gitlab.gnome.org/GNOME/vte/-/issues/88 -- Sincerely, Alexander
Re: [orca] Re: (solved) orca's strange behavior in a crowded terminal
I've just seen that version 0.73.99-1, which will soon be available in sid and then in testing, solves the problem for me with this version as well. so for me the problem is closed, as it will soon be corrected in debian. Jerem Le 03/09/2023 à 23:08, Alexander Epaneshnikov a écrit : On Sun, Sep 03, 2023 at 09:39:56PM +0200, Jérémy Prego wrote: hello, hello Jérémy. I've just found the library that's causing the problem. it's the libvte-2.91-0 library in version 0.73.93-1 currently in debian testing. downgrading to version 0.72.2-3 solves the problem. that happened because bug [1] was fixed in libvte. in fact I think this fix improved more than it got worse, so I'm sad that it was rolled back. i'm relieved! :) I was thinking of making a bug report in debian against the package, but I confess I don't know what to put in it. A question for Samuel. in order to return this fix, where the correction of the diff algorithm should occur in libvte or in orca? because as a vte-based terminal every day user, I can't imagine life without this patch. ps Well, this patch has a difficult fate. Jerem [1]: https://gitlab.gnome.org/GNOME/vte/-/issues/88
Re: [orca] (solved) orca's strange behavior in a crowded terminal
hello, I've just found the library that's causing the problem. it's the libvte-2.91-0 library in version 0.73.93-1 currently in debian testing. downgrading to version 0.72.2-3 solves the problem. i'm relieved! :) I was thinking of making a bug report in debian against the package, but I confess I don't know what to put in it. Jerem Le 02/09/2023 à 02:55, Jérémy Prego (jeremy) a écrit : Hello, since this evening, I've been experiencing a strange bug with orca, but I don't think he's the direct culprit. if I fill my terminal and then issue a command, e.g. "echo foo", Orca will read out the entire terminal window, not just the text that has just been added to the terminal. as long as the terminal isn't full, everything's fine, it works as expected. I've tried downgrading at-spi with all the right debian packages, but the problem is still there. I'm attaching a debug, if it helps to understand what's going on :) thanks, Jerem
