savoirfairelinux issueshttps://git.jami.net/groups/savoirfairelinux/-/issues2024-03-28T00:05:08Zhttps://git.jami.net/savoirfairelinux/jami-client-ios/-/issues/355User can receive requests for already accepted invites2024-03-28T00:05:08ZAndreas TraczykUser can receive requests for already accepted invites - possibly related to #354
- STEPS TO REPRODUCE (not 100% reproducible):
- get invite and accept it
- put app in background
- get invite again - possibly related to #354
- STEPS TO REPRODUCE (not 100% reproducible):
- get invite and accept it
- put app in background
- get invite againKateryna KostiukKateryna Kostiukhttps://git.jami.net/savoirfairelinux/jami-client-ios/-/issues/354Phantom invites that lead to several UX bugs2024-03-11T17:13:13ZAndreas TraczykPhantom invites that lead to several UX bugs - user sees conversation filter that shows invites
but when the user taps the invites tab, the user sees no invites
and can not leave the invites tab because the tab disappears
- the invites are likely regular conversations t... - user sees conversation filter that shows invites
but when the user taps the invites tab, the user sees no invites
and can not leave the invites tab because the tab disappears
- the invites are likely regular conversations that are not being
filtered correctly
- STEPS TO REPRODUCE:
- get invites
- the user will see the conversation in the invites filter
- the user will tap the invites filter
- the user will see no invites or phantom invites
- if there are no invites, the user will not be able to leave the invites tab
- if there are phantom invites, the user can accept an and this will remove all phantom invites
and return the user to the conversations tab (the invites tab will disappear)https://git.jami.net/savoirfairelinux/jami-daemon/-/issues/971"jamid" received signal SIGABRT, Aborted.2024-03-08T19:26:08ZCyrille Béraud"jamid" received signal SIGABRT, Aborted.`1709906012.321|57318|conversation.cpp :1675] Sync e43a7778189cc4adc94185c8db7e96c8d1097ed7 with 9138aa43a57c4cb0c77409837637d62e2c8731f176699e38c8c892a8f884f151
Thread 2 "jamid" received signal SIGABRT, Aborted.
[Switching to Th...`1709906012.321|57318|conversation.cpp :1675] Sync e43a7778189cc4adc94185c8db7e96c8d1097ed7 with 9138aa43a57c4cb0c77409837637d62e2c8731f176699e38c8c892a8f884f151
Thread 2 "jamid" received signal SIGABRT, Aborted.
[Switching to Thread 0x7ffff39ff6c0 (LWP 319436)]
__pthread_kill_implementation (no_tid=0, signo=6, threadid=<optimized out>) at ./nptl/pthread_kill.c:44
44 ./nptl/pthread_kill.c: Aucun fichier ou dossier de ce type.
(gdb) bt
#0 __pthread_kill_implementation (no_tid=0, signo=6, threadid=<optimized out>) at ./nptl/pthread_kill.c:44
#1 __pthread_kill_internal (signo=6, threadid=<optimized out>) at ./nptl/pthread_kill.c:78
#2 __GI___pthread_kill (threadid=<optimized out>, signo=signo@entry=6) at ./nptl/pthread_kill.c:89
#3 0x00007ffff66428e6 in __GI_raise (sig=sig@entry=6) at ../sysdeps/posix/raise.c:26
#4 0x00007ffff66268b7 in __GI_abort () at ./stdlib/abort.c:79
#5 0x00007ffff6627750 in __libc_message (fmt=fmt@entry=0x7ffff67c38d3 "*** %s ***: terminated\n") at ../sysdeps/posix/libc_fatal.c:150
#6 0x00007ffff6737c9b in __GI___fortify_fail (msg=msg@entry=0x7ffff67c8a98 "bit out of range 0 - FD_SETSIZE on fd_set") at ./debug/fortify_fail.c:24
#7 0x00007ffff6737792 in __GI___fdelt_chk (d=<optimized out>) at ./debug/fdelt_chk.c:26
#8 0x0000555555f41224 in dhtnet::upnp::NatPmp::readResponse(natpmp_t&, natpmpresp_t&) ()
#9 0x0000555555f42790 in dhtnet::upnp::NatPmp::getIgdPublicAddress() ()
#10 0x0000555555f430e3 in dhtnet::upnp::NatPmp::initNatPmp() ()
#11 0x0000555555f47075 in dhtnet::upnp::NatPmp::searchForIgd() ()
#12 0x0000555555f43b99 in asio::detail::wait_handler<dhtnet::upnp::NatPmp::searchForIgd()::{lambda(std::error_code const&)#1}, asio::any_io_executor>::do_complete(void*, asio::detail::scheduler_operation*, std::error_code const&, unsigned long) ()
#13 0x0000555555f2115e in asio::detail::scheduler::run(std::error_code&) [clone .isra.0] ()
#14 0x0000555555f214bf in std::thread::_State_impl<std::thread::_Invoker<std::tuple<dhtnet::upnp::UPnPContext::createIoContext(std::shared_ptr<asio::io_context> const&, std::shared_ptr<dht::log::Logger> const&)::{lambda()#1}> > >::_M_run() ()
#15 0x00007ffff6ae6333 in ?? () from /lib/x86_64-linux-gnu/libstdc++.so.6
#16 0x00007ffff6697b5a in start_thread (arg=<optimized out>) at ./nptl/pthread_create.c:444
#17 0x00007ffff67285fc in clone3 () at ../sysdeps/unix/sysv/linux/x86_64/clone3.S:78
(gdb)
#0 __pthread_kill_implementation (no_tid=0, signo=6, threadid=<optimized out>) at ./nptl/pthread_kill.c:44
#1 __pthread_kill_internal (signo=6, threadid=<optimized out>) at ./nptl/pthread_kill.c:78
#2 __GI___pthread_kill (threadid=<optimized out>, signo=signo@entry=6) at ./nptl/pthread_kill.c:89
#3 0x00007ffff66428e6 in __GI_raise (sig=sig@entry=6) at ../sysdeps/posix/raise.c:26
#4 0x00007ffff66268b7 in __GI_abort () at ./stdlib/abort.c:79
#5 0x00007ffff6627750 in __libc_message (fmt=fmt@entry=0x7ffff67c38d3 "*** %s ***: terminated\n") at ../sysdeps/posix/libc_fatal.c:150
#6 0x00007ffff6737c9b in __GI___fortify_fail (msg=msg@entry=0x7ffff67c8a98 "bit out of range 0 - FD_SETSIZE on fd_set") at ./debug/fortify_fail.c:24
#7 0x00007ffff6737792 in __GI___fdelt_chk (d=<optimized out>) at ./debug/fdelt_chk.c:26
#8 0x0000555555f41224 in dhtnet::upnp::NatPmp::readResponse(natpmp_t&, natpmpresp_t&) ()
#9 0x0000555555f42790 in dhtnet::upnp::NatPmp::getIgdPublicAddress() ()
#10 0x0000555555f430e3 in dhtnet::upnp::NatPmp::initNatPmp() ()
#11 0x0000555555f47075 in dhtnet::upnp::NatPmp::searchForIgd() ()
#12 0x0000555555f43b99 in asio::detail::wait_handler<dhtnet::upnp::NatPmp::searchForIgd()::{lambda(std::error_code const&)#1}, asio::any_io_executor>::do_complete(void*, asio::detail::scheduler_operation*, std::error_code const&, unsigned long) ()
#13 0x0000555555f2115e in asio::detail::scheduler::run(std::error_code&) [clone .isra.0] ()
#14 0x0000555555f214bf in std::thread::_State_impl<std::thread::_Invoker<std::tuple<dhtnet::upnp::UPnPContext::createIoContext(std::shared_ptr<asio::io_context> const&, std::shared_ptr<dht::log::Logger> const&)::{lambda()#1}> > >::_M_run() ()
#15 0x00007ffff6ae6333 in ?? () from /lib/x86_64-linux-gnu/libstdc++.so.6
#16 0x00007ffff6697b5a in start_thread (arg=<optimized out>) at ./nptl/pthread_create.c:444
#17 0x00007ffff67285fc in clone3 () at ../sysdeps/unix/sysv/linux/x86_64/clone3.S:78
(gdb)
#0 __pthread_kill_implementation (no_tid=0, signo=6, threadid=<optimized out>) at ./nptl/pthread_kill.c:44
#1 __pthread_kill_internal (signo=6, threadid=<optimized out>) at ./nptl/pthread_kill.c:78
#2 __GI___pthread_kill (threadid=<optimized out>, signo=signo@entry=6) at ./nptl/pthread_kill.c:89
#3 0x00007ffff66428e6 in __GI_raise (sig=sig@entry=6) at ../sysdeps/posix/raise.c:26
#4 0x00007ffff66268b7 in __GI_abort () at ./stdlib/abort.c:79
#5 0x00007ffff6627750 in __libc_message (fmt=fmt@entry=0x7ffff67c38d3 "*** %s ***: terminated\n") at ../sysdeps/posix/libc_fatal.c:150
#6 0x00007ffff6737c9b in __GI___fortify_fail (msg=msg@entry=0x7ffff67c8a98 "bit out of range 0 - FD_SETSIZE on fd_set") at ./debug/fortify_fail.c:24
#7 0x00007ffff6737792 in __GI___fdelt_chk (d=<optimized out>) at ./debug/fdelt_chk.c:26
#8 0x0000555555f41224 in dhtnet::upnp::NatPmp::readResponse(natpmp_t&, natpmpresp_t&) ()
#9 0x0000555555f42790 in dhtnet::upnp::NatPmp::getIgdPublicAddress() ()
#10 0x0000555555f430e3 in dhtnet::upnp::NatPmp::initNatPmp() ()
#11 0x0000555555f47075 in dhtnet::upnp::NatPmp::searchForIgd() ()
#12 0x0000555555f43b99 in asio::detail::wait_handler<dhtnet::upnp::NatPmp::searchForIgd()::{lambda(std::error_code const&)#1}, asio::any_io_executor>::do_complete(void*, asio::detail::scheduler_operation*, std::error_code const&, unsigned long) ()
#13 0x0000555555f2115e in asio::detail::scheduler::run(std::error_code&) [clone .isra.0] ()
#14 0x0000555555f214bf in std::thread::_State_impl<std::thread::_Invoker<std::tuple<dhtnet::upnp::UPnPContext::createIoContext(std::shared_ptr<asio::io_context> const&, std::shared_ptr<dht::log::Logger> const&)::{lambda()#1}> > >::_M_run() ()
#15 0x00007ffff6ae6333 in ?? () from /lib/x86_64-linux-gnu/libstdc++.so.6
#16 0x00007ffff6697b5a in start_thread (arg=<optimized out>) at ./nptl/pthread_create.c:444
#17 0x00007ffff67285fc in clone3 () at ../sysdeps/unix/sysv/linux/x86_64/clone3.S:78
(gdb)
`Adrien BéraudSébastien BlinAdrien Béraudhttps://git.jami.net/savoirfairelinux/jami-daemon/-/issues/970Video camera stream is black when hardware acceleration is enabled2024-03-08T13:26:13ZPaul Le Guen de KerneizonVideo camera stream is black when hardware acceleration is enabled## How to report a bug
## One bug = one bug report
If you have multiple issues, please file separate bug reports. It will be much easier to track bugs that way.
## Avoid duplicates
Search for similar problem - update existing issue i...## How to report a bug
## One bug = one bug report
If you have multiple issues, please file separate bug reports. It will be much easier to track bugs that way.
## Avoid duplicates
Search for similar problem - update existing issue instead of creating new one.
## Bug report form
## Describe your environment
Please specify the following:
- OS: Ubuntu 22.04.4 LTS
- Jami version: 202402141827
- What build you are using: jami.net
## Steps to reproduce
1. Enable hardware acceleration in parameters with 960x540 resolution
2. Start a video call
- Actual result: My video camera stream is black on the Jami screen of other contacts in the meeting. However, I can see myself on my Jami screen. Must disable hardware acceleration to solve the problem or change the video resolution to 1280x720
- Expected result: Other people can see my camera video stream instead of a black screen.
## Additional information
- With Jami enable with `--debug`, this log appeared:
```
[1709890977.592|52761|accel.cpp :298 ] Failed to push frame to GPU: Invalid argument
[1709890977.593|52761|media_encoder.cpp :438 ] Fail to get frame
[1709890977.593|52761|video_sender.cpp :87 ] encoding failed
```
- The issue appears whatever camera I use
- My laptop is a Lenovo P14S with AMD GPU and same hardware
- We achieve to reproduce the same bug with Fedora 39
On contact side:
![Screenshot_from_2024-03-08_11-29-49](/uploads/f93d51095c449899708f64255c9f4850/Screenshot_from_2024-03-08_11-29-49.png)
On my side:
![Screenshot_from_2024-03-08_11-29-48](/uploads/f5672232032c2ce2a9671ebf44825c2e/Screenshot_from_2024-03-08_11-29-48.png)
For retrieving logs, cf [this page](https://git.jami.net/savoirfairelinux/ring-project/wikis/tutorials/Bug-report-guide#logs).https://git.jami.net/savoirfairelinux/jami-client-qt/-/issues/1596Video camera stream is black when hardware acceleration is enabled2024-03-08T12:40:48ZPaul Le Guen de KerneizonVideo camera stream is black when hardware acceleration is enabled## How to report a bug
## One bug = one bug report
If you have multiple issues, please file separate bug reports. It will be much easier to track bugs that way.
## Avoid duplicates
Search for similar problem - update existing issue i...## How to report a bug
## One bug = one bug report
If you have multiple issues, please file separate bug reports. It will be much easier to track bugs that way.
## Avoid duplicates
Search for similar problem - update existing issue instead of creating new one.
## Bug report form
## Describe your environment
Please specify the following:
- OS: Ubuntu 22.04.4 LTS
- Jami version: 202402141827
- What build you are using: jami.net
## Steps to reproduce
1. Enable hardware acceleration in parameters with 960x540 resolution
2. Start a video call
- Actual result: My video camera stream is black on the Jami screen of other contacts in the meeting. However, I can see myself on my Jami screen. Must disable hardware acceleration to solve the problem or change the video resolution to 1280x720
- Expected result: Other people can see my camera video stream instead of a black screen.
## Additional information
- With Jami enable with `--debug`, this log appeared:
```
[1709890977.592|52761|accel.cpp :298 ] Failed to push frame to GPU: Invalid argument
[1709890977.593|52761|media_encoder.cpp :438 ] Fail to get frame
[1709890977.593|52761|video_sender.cpp :87 ] encoding failed
```
- The issue appears whatever camera I use
- My laptop is a Lenovo P14S with AMD GPU and same hardware
- We achieve to reproduce the same bug with Fedora 39
On contact side:
![Screenshot from 2024-03-08 11-29-49.png](/uploads/45412327f2128bb956b1baa47fd6086d/Screenshot_from_2024-03-08_11-29-49.png)
On my side:
![Screenshot from 2024-03-08 11-29-48.png](/uploads/85782dfb436546d53ce5b0f2b47f857d/Screenshot_from_2024-03-08_11-29-48.png)
For retrieving logs, cf [this page](https://git.jami.net/savoirfairelinux/ring-project/wikis/tutorials/Bug-report-guide#logs).https://git.jami.net/savoirfairelinux/jami-client-android/-/issues/1625Share debug.keystore among developers2024-03-05T16:28:01ZPierre NicolasShare debug.keystore among developersWould enable launching code on various Android devices without the need to delete the app beforehand.Would enable launching code on various Android devices without the need to delete the app beforehand.https://git.jami.net/savoirfairelinux/jami-daemon/-/issues/968Fix sporadic failures2024-03-05T17:58:43ZSébastien BlinFix sporadic failures```
1) test: jami::test::ConversationTest::testIsComposing (F) line: 986 conversation/conversation.cpp
assertion failed
- Expression: cv.wait_for(lk, 30s, [&]() { return bobData.composing; })
```
```
1) test: jami::test::ConversationM...```
1) test: jami::test::ConversationTest::testIsComposing (F) line: 986 conversation/conversation.cpp
assertion failed
- Expression: cv.wait_for(lk, 30s, [&]() { return bobData.composing; })
```
```
1) test: jami::test::ConversationMembersEventTest::testAddAcceptOfflineThenConnects (F) line: 613 conversation/conversationMembersEvent.cpp
assertion failed
- Expression: cv.wait_for(lk, 60s, [&]() { return !bobData.conversationId.empty(); })
```
```
!!!FAILURES!!!
Test Results:
Run: 4 Failures: 3 Errors: 0
1) test: jami::test::TypersTest::testSetIsComposing (F) line: 203 conversation/typers.cpp
assertion failed
- Expression: cv.wait_for(lk, 5s, [&]() { return bobData.composing[aliceUri]; })
2) test: jami::test::TypersTest::testTimeout (F) line: 229 conversation/typers.cpp
assertion failed
- Expression: cv.wait_for(lk, 5s, [&]() { return bobData.composing[aliceUri]; })
3) test: jami::test::TypersTest::testTypingRemovedOnMemberRemoved (F) line: 254 conversation/typers.cpp
assertion failed
- Expression: cv.wait_for(lk, 5s, [&]() { return aliceData.composing[bobUri]; })
```Sébastien BlinSébastien Blinhttps://git.jami.net/savoirfairelinux/jami-project/-/issues/1631Call Notifications: Re-design call swarm layout2024-03-28T00:05:08ZSébastien BlinCall Notifications: Re-design call swarm layoutOrdre du jour:Ordre du jour:Sébastien BlinCharlotte HoffmannAdrien BéraudAndreas TraczykCyrille BéraudSébastien Blin2024-03-11https://git.jami.net/savoirfairelinux/jami-client-qt/-/issues/1595The input box still has issues2024-03-05T12:50:54Zsession 21The input box still has issuesWindows, version: 202402091720
The logic of the input box still seems to have significant issues, and the copied long text cannot be edited well in the input box. In the picture, it can be seen that the cursor is already outside the dis...Windows, version: 202402091720
The logic of the input box still seems to have significant issues, and the copied long text cannot be edited well in the input box. In the picture, it can be seen that the cursor is already outside the display range, which poses certain obstacles for us to edit the text.
![image.png](/uploads/441a4fda42b82ad6aa4e69098611e2cf/image.png)
Copying long text almost always reproduces this problem.
In addition, after copying long text, the input box still cannot be restored to its original state in a timely manner, but it is better than before. At least now, it will be restored to its original state after we send a new message.
![image.png](/uploads/975ffe381151e8f2489ae2fd07949aeb/image.png)https://git.jami.net/savoirfairelinux/jami-client-qt/-/issues/1594Field for password and archive doesnt disappear on OK2024-03-04T18:17:07ZShalokShalomField for password and archive doesnt disappear on OKI can set a password, or backup the archive and the functionality is flawless.
Although, when I press on OK, the small window that provides the interaction, does not disappear.
I assume this might be the case for 'Delete account' as we...I can set a password, or backup the archive and the functionality is flawless.
Although, when I press on OK, the small window that provides the interaction, does not disappear.
I assume this might be the case for 'Delete account' as well.
Jami 20231201.0 on NixOShttps://git.jami.net/savoirfairelinux/jami-client-qt/-/issues/1593Add JAMS (Jami Account Management Server) tip2024-03-04T18:19:36ZovariAdd JAMS (Jami Account Management Server) tip![image](/uploads/1cd3b0208dc4c8e19153ace9ad4093bb/image.png)
Please add a JAMS (Jami Account Management Server) tip.
This can help people discover and visit https://jami.biz/
What do you think?
Thank you![image](/uploads/1cd3b0208dc4c8e19153ace9ad4093bb/image.png)
Please add a JAMS (Jami Account Management Server) tip.
This can help people discover and visit https://jami.biz/
What do you think?
Thank youhttps://git.jami.net/savoirfairelinux/jami-client-qt/-/issues/1592Easy way to report Jami version when opeing new issue2024-03-04T18:12:50ZPierre MétrasEasy way to report Jami version when opeing new issuePlease add an easy way to capture Jami version and platform information, for instance a button to copy this information to the clipboard. Presently, you have to do 2 copy/paste to get this information (1 for release name and 1 for versio...Please add an easy way to capture Jami version and platform information, for instance a button to copy this information to the clipboard. Presently, you have to do 2 copy/paste to get this information (1 for release name and 1 for version) while it could be done, with more information, in 1 click.
![Screenshot_20240301_201404](/uploads/aa85a0aaa6e0b5eaa669533b0604df09/Screenshot_20240301_201404.png)https://git.jami.net/savoirfairelinux/jami-client-qt/-/issues/1591Question regarding presence and message delivery2024-03-05T11:49:41ZannaQuestion regarding presence and message deliveryMy account shows a green dot.
My Swarm contact's account does too.
However, my last message still has a white circle.
As I have learnt, this means that the message is being sent.
What puzzles me, however: If I assume by seeing the col...My account shows a green dot.
My Swarm contact's account does too.
However, my last message still has a white circle.
As I have learnt, this means that the message is being sent.
What puzzles me, however: If I assume by seeing the coloured dots that my contact and I are both online: Then why is the message transfer not completed?
Observed with version: 202402141739 on Linux.
My swarm contact is using iOS.https://git.jami.net/savoirfairelinux/jami-client-android/-/issues/1623If the message is a file, the "Delete message" button from the menu (long pre...2024-03-01T10:42:18ZannaIf the message is a file, the "Delete message" button from the menu (long press) does not workObserved with Jami Android version 20240223-1.Observed with Jami Android version 20240223-1.https://git.jami.net/savoirfairelinux/jami-client-qt/-/issues/1590presence: different shape for different presence2024-03-11T08:46:24Zovaripresence: different shape for different presence![image](/uploads/bedc8c098ce3e82bfd632336638b910d/image.png)
Should the orange presence also have a different shape to the green presence, say a semicircle?
This may help improve the UX for vision impaired people.
1. Active = green, ...![image](/uploads/bedc8c098ce3e82bfd632336638b910d/image.png)
Should the orange presence also have a different shape to the green presence, say a semicircle?
This may help improve the UX for vision impaired people.
1. Active = green, solid circle
2. Away = orange, solid semicircle
3. Do not disturb = red, solid octagon (like a stop sign). If the size is too small, perhaps a red, solid square
Thank you
Linux Mint 21.3 Cinnamon<br>
Jami Version: 202402291646https://git.jami.net/savoirfairelinux/jami-client-qt/-/issues/1589presence: account green and swarm member orange. Should they both be green as...2024-03-04T18:10:53Zovaripresence: account green and swarm member orange. Should they both be green as they are the same account?presence: account green and swarm member orange. Should they both be green as they are the same account?
![image](/uploads/5e140381484714f2150285dfa36385dc/image.png)
Thank you
Linux Mint 21.3 Cinnamon<br>
Jami Version: 202402291646presence: account green and swarm member orange. Should they both be green as they are the same account?
![image](/uploads/5e140381484714f2150285dfa36385dc/image.png)
Thank you
Linux Mint 21.3 Cinnamon<br>
Jami Version: 202402291646https://git.jami.net/savoirfairelinux/jami-client-qt/-/issues/1588Removing the only linked device does not work2024-03-05T11:28:05ZannaRemoving the only linked device does not work![Screencast](/uploads/6218a65b0de10621e3a04618b9222c92/Screencast.webm)
The "Cancel" button closes the window.
However, when I click on "Remove", nothing happens.
Observed with version: 202402141739 on Linux.![Screencast](/uploads/6218a65b0de10621e3a04618b9222c92/Screencast.webm)
The "Cancel" button closes the window.
However, when I click on "Remove", nothing happens.
Observed with version: 202402141739 on Linux.https://git.jami.net/savoirfairelinux/jami-client-qt/-/issues/1587Add a way to preview voice and video messages2024-03-04T18:17:21ZannaAdd a way to preview voice and video messagesIt should be possible to preview voice or video messages before I send them.
At the moment, I only have the options: "Discard and restart" and "Send".
Observed with version: 202402141739 on Linux.It should be possible to preview voice or video messages before I send them.
At the moment, I only have the options: "Discard and restart" and "Send".
Observed with version: 202402141739 on Linux.https://git.jami.net/savoirfairelinux/jami-client-qt/-/issues/1586Jami constantly crashes when I open a conversation and the content is being l...2024-03-13T11:20:54ZannaJami constantly crashes when I open a conversation and the content is being loadedThe issue has only appeared recently.
How can I access the logs if the graphical user interface keeps crashing?
Observed with version: 202402141739 on Linux.The issue has only appeared recently.
How can I access the logs if the graphical user interface keeps crashing?
Observed with version: 202402141739 on Linux.https://git.jami.net/savoirfairelinux/jami-client-qt/-/issues/1585Various cut-off dialogues when removing or linking a device2024-03-04T18:17:42ZannaVarious cut-off dialogues when removing or linking a device![01](/uploads/c353402ace9c7ac9e7a44dbe98d3e1f6/01.png)
![02](/uploads/814191ec1d984ed24dd57b5fea6d1efc/02.png)
![03](/uploads/ce2f595b742ba426dff1d483a92dad2d/03.png)
The text zoom level is set to 100.
Observed with version: 2024021...![01](/uploads/c353402ace9c7ac9e7a44dbe98d3e1f6/01.png)
![02](/uploads/814191ec1d984ed24dd57b5fea6d1efc/02.png)
![03](/uploads/ce2f595b742ba426dff1d483a92dad2d/03.png)
The text zoom level is set to 100.
Observed with version: 202402141739 on Linux.