debian testing iso install in franch: mate desktop is in English

2023-12-15 Thread Jérémy Prego

Hello,

a friend and I installed a debian testing from the iso available here:
https://cdimage.debian.org/cdimage/daily-builds/daily/arch-latest/amd64/iso-cd/

When you choose French, and install the mate desktop, the graphical 
interface is in English, while the rest of the system is in French.

however, the keyboard is in azerty as I requested during installation

If it's any help, I'd like to point out that the first test was carried 
out on December 9 and my test on December 15, and the bug is still present.


thanks,

Jerem



Re: [orca] Re: (solved) orca's strange behavior in a crowded terminal

2023-09-11 Thread Jérémy Prego




Le 11/09/2023 à 20:49, Samuel Thibault a écrit :

Jérémy Prego, le lun. 11 sept. 2023 09:21:38 +0200, a ecrit:

Le 11/09/2023 à 09:01, Samuel Thibault a écrit :

Jérémy Prego, le lun. 11 sept. 2023 03:35:15 +0200, a ecrit:

I noticed a small problem

1. when you open a large file using cat file.txt |less and press enter to go
down in the file, orca almost always pronounces the first 2 letters of the
line before reading the whole line.

Is this a regression over the previous versions or not?

yes, it's a regression. i don't have this behavior with the version in debian 
testing

Ok, I see the issue. I have updated the patches and package to merge the
additions, could you please re-test?

I can confirm that it's much better!

after a quick test, I don't have any more problems, I'll test it in use, 
but for me, everything looks good compared to the version in debian testing


thanks !


Samuel

Jerem

libt.tld_type is 1, lib_t.tld_source_file is 
'/usr/local/lib/aarch64-linux-gnu/perl/5.30.0/auto/share/dist/Mail-DMARC-opendmarc/effective_tld_names.dat'
___
orca mailing list
o...@freelists.org
https://www.freelists.org/list/orca
Orca wiki: https://wiki.gnome.org/Projects/Orca
Orca documentation: https://help.gnome.org/users/orca/stable/
GNOME Universal Access guide: 
https://help.gnome.org/users/gnome-help/stable/a11y.html




Re: [orca] Re: (solved) orca's strange behavior in a crowded terminal

2023-09-11 Thread Jérémy Prego




Le 11/09/2023 à 09:01, Samuel Thibault a écrit :

Jérémy Prego, le lun. 11 sept. 2023 03:35:15 +0200, a ecrit:

I noticed a small problem

1. when you open a large file using cat file.txt |less and press enter to go
down in the file, orca almost always pronounces the first 2 letters of the
line before reading the whole line.

Is this a regression over the previous versions or not?



yes, it's a regression. i don't have this behavior with the version in debian 
testing
Samuel




Re: [orca] Re: (solved) orca's strange behavior in a crowded terminal

2023-09-10 Thread Jérémy Prego

hello,

I've just tested this version out of curiosity.

I noticed a small problem

1. when you open a large file using cat file.txt |less and press enter 
to go down in the file, orca almost always pronounces the first 2 
letters of the line before reading the whole line.


Jerem
Le 11/09/2023 à 02:27, Samuel Thibault a écrit :

Hello,

I have updated https://gitlab.gnome.org/GNOME/vte/-/issues/88 with an
improved patch. Could people try it? I have also uploaded patched Debian
packages on https://people.debian.org/~sthibault/tmp/trixie-tmp/

Please test so we can at last get this fixed!

Samuel
___
orca mailing list
o...@freelists.org
https://www.freelists.org/list/orca
Orca wiki: https://wiki.gnome.org/Projects/Orca
Orca documentation: https://help.gnome.org/users/orca/stable/
GNOME Universal Access guide: 
https://help.gnome.org/users/gnome-help/stable/a11y.html




Re: [orca] Re: (solved) orca's strange behavior in a crowded terminal

2023-09-03 Thread Jérémy Prego
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

2023-09-03 Thread Jérémy Prego

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




Re: ifconfig

2023-07-07 Thread Jérémy Prego

hello,

apt install net-tools

Jerem
Le 07/07/2023 à 23:53, K0LNY a écrit :
Anyone know why the ifconfig command does not work on my Debian 32 bit 
on my Asus?

I've tried it as root and not as root, it just says
command not found.
Thanks.




Re: Running A nano VNA file

2023-02-08 Thread Jérémy Prego

hello,

in folder, type:
./nanovna-saver

Is it better?

Jerem
Le 08/02/2023 à 20:24, K0LNY_Glenn a écrit :

Hi All,
I downloaded NanoVNA-Saver for Linux at:
https://github.com/NanoVNA-Saver/nanovna-saver/releases/tag/v0.5.4
and I'm using Ubuntu with Orca.
I unzipped the file:
NanoVNASaver.linux.zip
and got a single file
nanovna-saver
The page says to chmod -x it because the executable flags get lost with the
unzipping.
So I did that with no errors.
But the file does not execute.
I just get command not found
I tried sudo bash nanovna-saver
and it says it's not an executable file
The NanoVNA is a device to test antennas for SWR and resonant frequency.
Thanks for any assistance.

Glenn





Re: how to stop Marco from locking up on Bullseye/Mate?

2022-06-29 Thread Jérémy Prego

hello,

I confirm this bug under debian with a version of marco higher than 
1.24.0-1.


I had already mentioned this problem earlier without a solution so far. 
I don't know how to reproduce the problem every time.


to unlock marco and orca, just call the orca preferences with the 
shortcut orca + space. once an orca window appears everything 
unlocks...until next time...


    Jerem
Le 29/06/2022 à 20:48, Chevelle a écrit :
If I start VLC to play an audio file and press control-q to quit the 
file Marco gets locked up.  This renders ORCA useless because it can't 
read things properly.  The system is useless at that point.  A similar 
thing happens with MPV.  It was happening with Chromium until version 
103 came out last week.  If I switch to a console window and kill 
Marco the problem goes away temporarily.


Does anybody have a solution for this or know how to track it down or 
file a bug report on it?


I sent the ORCA developer a debug file demonstrating the problem with 
Chromium, but she never answered me.




On 6/29/2022 9:59 AM, Didier Spaier wrote:

Hello Roberto

Le 29/06/2022 à 15:27, Roberto Burceni a écrit :

Thank you for your response. Which distribution are you using for xlqt?
Slint, but running the pre-version 15.0 not yet released (I am its 
maintainer).


Cheers,
Didier







RE: [solved but ...] accessibility bug after quitting a qt application

2021-03-05 Thread Jérémy Prego
hello,

i just found the culprit ... i am using mate desktop and there has been
an update from marco to 1.24.1-2.

I went back to marco 1.24.0 and I found the happiness of being able to
quit qt applications without any problem! :)

I also had bugs with marco 1.24.1-1 several months ago. I blocked the
installation of version 1.24.1-1 but it looks like version 1.24.1-2
still has the same issues with qt apps ...

hoping it can help other people

Jerem
Le 23/02/2021 à 17:34, Devin Prater a écrit :
> Yeah, it's been here for a while in Arch. If you go to the desktop
> immediately after quitting the program, you're good. You can also call
> an Orca dialog, like Insert + H, then F2 to show keyboard commands.
>
> On 2/22/21 7:10 PM, Jérémy Prego via orca-list wrote:
>> Hello,
>>
>> Since the last update of qt on my debian testing a week ago, I am
>> experiencing a bug when I quit a qt application with alt + f4.
>>
>> i don't think orca is frozen because if i get a notification it will
>> read it, but i can't do anything on the keyboard anymore
>>
>> To get out of this freeze, I just need to call orca preferences with
>> orca + space and there I find the interaction with my keyboard.
>>
>> I specify that I have not yet tried to install a debian testing on a vm
>> in order to reproduce the behavior.
>>
>> Have you heard of this bug?
>>
>> thanks,
>>
>> Jerem
>> ___
>> orca-list mailing list
>> orca-l...@gnome.org
>> https://mail.gnome.org/mailman/listinfo/orca-list
>> Orca wiki: https://wiki.gnome.org/Projects/Orca
>> Orca documentation: https://help.gnome.org/users/orca/stable/
>> GNOME Universal Access guide: 
>> https://help.gnome.org/users/gnome-help/stable/a11y.html



accessibility bug after quitting a qt application

2021-02-22 Thread Jérémy Prego
Hello,

Since the last update of qt on my debian testing a week ago, I am
experiencing a bug when I quit a qt application with alt + f4.

i don't think orca is frozen because if i get a notification it will
read it, but i can't do anything on the keyboard anymore

To get out of this freeze, I just need to call orca preferences with
orca + space and there I find the interaction with my keyboard.

I specify that I have not yet tried to install a debian testing on a vm
in order to reproduce the behavior.

Have you heard of this bug?

thanks,

Jerem



Re: at-spi 2.33 stack in experimental

2019-09-07 Thread Jérémy Prego



Le 07/09/2019 à 20:40, Samuel Thibault a écrit :
> Jérémy Prego, le ven. 06 sept. 2019 15:36:31 +0200, a ecrit:
>> as long as I do not press at least one letter, f10, or alt + tab and
>> then alt + tab to return in pluma, nothing happens if I use the arrow.
> I can't reproduce the issue. What I am doing is:
>
> - install bullseye
> - upgrade at-spi packages as mentioned in my previous mail

> reboot ? or no. here, if I don't restart, I got the impression that still use 
> the old version

Jerem
> - put some text in test.txt
> - run mate-terminal
> - type pluma test.txt there
>
> Pluma opens, and orca's braille monitor shows the first line of
> test.txt
>
> If I type the down arrow, orca's braille monitor shows the next line of
> test.txt
>
> Samuel
>



Re: at-spi 2.33 stack in experimental

2019-09-06 Thread Jérémy Prego
Le 06/09/2019 à 15:12, Samuel Thibault a écrit :
> Hello,
>
> Jérémy Prego, le ven. 06 sept. 2019 15:05:34 +0200, a ecrit:
>> if I open a program from a terminal, pluma /tmp/fichier.txt for example,
>> I have not the access to the entire suite if I use the up and down
>> arrows. there is a small lag.
> I'm not sure of the details here: do mention both not having access, and
> having a lag. Do you mean that you do not have _immediate_ access, i.e.
> operations take a lot of time before you get results?

I thought it was a lag, but eventually, it is nothing.

as long as I do not press at least one letter, f10, or alt + tab and
then alt + tab to return in pluma, nothing happens if I use the arrow.

> I have the impression that he expects that the window of pluma, either modify 
> it to be able to capture it

> Samuel
Jerem



Re: at-spi 2.33 stack in experimental

2019-09-06 Thread Jérémy Prego
hello,

the bug of su is fixed in 2.33.92-2. thanks ! However, I have another
bug that is not related, but I relate it as there is still time.

if I open a program from a terminal, pluma /tmp/fichier.txt for example,
I have not the access to the entire suite if I use the up and down
arrows. there is a small lag. after I don't know if the bug comes from
orca or at-spi. I do not know since when it no longer works exactly.

to solve the problem I do a alt + tab and then a second alt + tab to
return in pluma.

Jerem
Le 06/09/2019 à 03:54, Samuel Thibault a écrit :
> Hello,
>
> I managed to reproduce the issue.  I believe this should be fixed by
> version 2.33.92-2 of at-spi2-core.
>
>
> Some people have asked how to install these versions.  You should be
> able to just add
>
> deb http://deb.debian.org/debian/ experimental main 
>
> to your sources.list, run apt-get update, and then use
>
> apt-get install at-spi2-core/experimental gir1.2-atspi-2.0/experimental 
> libatk-adaptor/experimental libatk-bridge2.0-0/experimental 
> libatspi2.0-0/experimental python3-pyatspi/experimental 
> libatk1.0-0/experimental
>
> to upgrade the whole at-spi stack to the experimental version. And use
>
> apt-get install at-spi2-core/unstable gir1.2-atspi-2.0/unstable 
> libatk-adaptor/unstable libatk-bridge2.0-0/unstable libatspi2.0-0/unstable 
> python3-pyatspi/unstable libatk1.0-0/unstable
>
> to downgrade back to unstable.
>
> Samuel
>



Re: at-spi 2.33 stack in experimental

2019-09-04 Thread Jérémy Prego
hello,

result check-a11y

jeremy@jerem-debian:~/check-a11y$ ./troubleshoot
Info
INFO: session type 'x11'
INFO: VT '7'
INFO: session desktop 'lightdm-xsession'
INFO: current desktop 'MATE'
INFO: DISPLAY ':0.0'
INFO: WAYLAND_DISPLAY ''

Packages
PASS: at-spi2-core installed
PASS: libgail-common installed
PASS: libatk-adaptor installed
PASS: qt-at-spi installed
FAIL: libatk-wrapper-java not installed, Java Swing applications will
not be accessible

Running environment
PASS: at-spi-bus-launcher is running as user jeremy
PASS: at-spi2-registryd is running as user jeremy
FAIL: mismatch between $DBUS_SESSION_BUS_ADDRESS
(unix:path=/run/user/1000/bus) and well-known path
/home/jeremy/.dbus/session-bus/1795160871d64fc086911b59fabb7ca4-0 ()
PASS: got accessibility bus
unix:abstract=/tmp/dbus-7hjZBYOBc7,guid=61bf95d55461303e5116c7b45d6eb779
from session dbus
PASS: got accessibility bus
unix:abstract=/tmp/dbus-7hjZBYOBc7,guid=61bf95d55461303e5116c7b45d6eb779
from root window
PASS: accessibility buses from session dbus and from root window match
PASS: org.a11y.Status IsEnabled is true

Layer enabling
PASS: screen-reader-enabled is set in gsettings
PASS: MATE accessibility is set in gsettings
PASS: GTK_MODULES contains gail
PASS: GTK_MODULES contains atk-bridge
PASS: QT_ACCESSIBILITY is set to 1
WARN: GNOME_ACCESSIBILITY is set to '', mozilla applications will not be
accessible unless IsEnabled is set to true (as typically set by starting
orca, but not accerciser etc.)
jeremy@jerem-debian:~/check-a11y$ su -l
Mot de passe :
02:21:~# cd /home/jeremy/che
02:21:~# cd /home/jeremy/check-a11y/
02:21:/home/jeremy/check-a11y# ./troubleshoot
Info
INFO: session type ''
INFO: VT ''
INFO: session desktop ''
INFO: current desktop ''
INFO: DISPLAY ':0.0'
INFO: WAYLAND_DISPLAY ''

Packages
PASS: at-spi2-core installed
PASS: libgail-common installed
PASS: libatk-adaptor installed
PASS: qt-at-spi installed
FAIL: libatk-wrapper-java not installed, Java Swing applications will
not be accessible

Running environment
FAIL: at-spi-bus-launcher is not running as user root
but another at-spi-bus-launcher is running as another user (though
perhaps on another DISPLAY)
FAIL: at-spi2-registryd is not running as user root
but another at-spi2-registryd is running as another user (though perhaps
on another DISPLAY)
FAIL: no session bus address in $DBUS_SESSION_BUS_ADDRESS
  well-known path
/root/.dbus/session-bus/1795160871d64fc086911b59fabb7ca4-0 says
unix:abstract=/tmp/dbus-EulxEYmzKS,guid=7ebe74b5480801ba4fff4b955d6e29c2
Error org.freedesktop.DBus.Error.NoReply: Did not receive a reply.
Possible causes include: the remote application did not send a reply,
the message bus security policy blocked the reply, the reply timeout
expired, or the network connection was broken.
FAIL: can't get accessibility bus from session dbus
PASS: got accessibility bus
unix:abstract=/tmp/dbus-7hjZBYOBc7,guid=61bf95d55461303e5116c7b45d6eb779
from root window
^[[DError org.freedesktop.DBus.Error.NoReply: Did not receive a reply.
Possible causes include: the remote application did not send a reply,
the message bus security policy blocked the reply, the reply timeout
expired, or the network connection was broken.
WARN: org.a11y.Status IsEnabled is '', mozilla applications will not be
accessible unless GNOME_ACCESSIBILITY is set to 1

Layer enabling
PASS: screen-reader-enabled is set in gsettings
PASS: MATE accessibility is set in gsettings
WARN: GTK_MODULES does not contain gail, GTK2 applications may not be
accessible
WARN: GTK_MODULES does not contain atk-bridge, GTK2 applications may not
be accessible
WARN: QT_ACCESSIBILITY is not set to 1, Qt4 applications may not be
accessible
WARN: GNOME_ACCESSIBILITY is set to '', mozilla applications will not be
accessible unless IsEnabled is set to true (as typically set by starting
orca, but not accerciser etc.)
02:22:/home/jeremy/check-a11y#

I precise that I do the test with at-spi2-core version 2.32. should I do
the same thing with the 2.33 ?

I also explained that in my /root I have a file .gtkrc-2.0 which
contains this:
gtk-modules = "gail:atk-bridge"

please tell me if I forgot to answer something

Jerem
Le 05/09/2019 à 00:21, Samuel Thibault a écrit :
> Jérémy Prego, le mar. 03 sept. 2019 11:07:26 +0200, a ecrit:
>> I have a regression when I want to read a document in su mode. the 
>> downgrader at-spi2-core has the old version (2.32.1-4) solves the problem. 
>> step to reproduce:
>> 1. open a terminal
>> 2. su-l and then password
>> 3. pluma file
>>
>> here, orca does not read anything 
> Mmm, there are several things:
>
> - su -l resets the environment, so it is expected that things won't
>   work. Actually I wonder why you are not getting
>
>   Cannot open display:
>   Run 'pluma --help' to see a full list of available command line options.
>
>   because DISPLAY would be unset. Are you perhaps setting DISPLAY to :0
&g

Re: at-spi 2.33 stack in experimental

2019-09-03 Thread Jérémy Prego
Le 03/09/2019 à 01:26, Samuel Thibault a écrit :
> Hello,
>
> Samuel Thibault, le sam. 24 août 2019 19:20:46 +0200, a ecrit:
>> The at-spi 2.33 stack is available for testing from the experimental
>> repository.
>>
>> testing can be welcome to avoid surprises when it will enter
>> unstable then testing.
> There was indeed a regression on orca startup, this is now fixed in the
> 2.33.92 series now available in experimental, up for more testing!


> hello,
>
> I just try to upgrade the battery accessibility in 2.33 in my debian testing.
>
> Start-Date: 2019-09-03  07:39:48
> Upgrade: gir1.2-atk-1.0:amd64 (2.33.3+really2.32.0-4, 2.33.3+really2.33.3-1), 
> at-spi2-core:amd64 (2.32.1-4, 2.33.92-1), python3-pyatspi:amd64 
> (2.33.90+really2.32.1+dfsg-4, 2.33.92-1), libatk-adaptor:amd64 (2.32.0-7, 
> 2.33.92-1), libatk1.0-0:amd64 (2.33.3+really2.32.0-4, 2.33.3+really2.33.3-1), 
> libatspi2.0-0:amd64 (2.32.1-4, 2.33.92-1), gir1.2-atspi-2.0:amd64 (2.32.1-4, 
> 2.33.92-1), libatk-bridge2.0-0:amd64 (2.32.0-7, 2.33.92-1), 
> libatk1.0-data:amd64 (2.33.3+really2.32.0-4, 2.33.3+really2.33.3-1)
> End-Date: 2019-09-03  07:39:50
>
> I have a regression when I want to read a document in su mode. the downgrader 
> at-spi2-core has the old version (2.32.1-4) solves the problem. 
>
> step to reproduce:
> 1. open a terminal
> 2. su-l and then password
> 3. pluma file
>
> here, orca does not read anything 

I don't know if this is a bug or I have forgot to update something.

thanks,

> Samuel
Jerem