savoirfairelinux issueshttps://git.jami.net/groups/savoirfairelinux/-/issues2024-03-19T13:20:57Zhttps://git.jami.net/savoirfairelinux/jami-client-android/-/issues/1632Buttons are missing in CallView when Android interface scaling and font scali...2024-03-19T13:20:57ZPreston LeppanenButtons are missing in CallView when Android interface scaling and font scaling are set to too large## Environment
- Jami version: 20240308-01
- Device model: Xiaomi Mi 10T Lite
- Android version: 12
- What build you are using: F-Droid
## Description
Android has scaling options for interface/font in display settings. When yo...## Environment
- Jami version: 20240308-01
- Device model: Xiaomi Mi 10T Lite
- Android version: 12
- What build you are using: F-Droid
## Description
Android has scaling options for interface/font in display settings. When you change the scaling to the largest, buttons in CallView are no longer visible.
<img src="/uploads/f7b16d478c43666770f03231f58ba0b1/c92cb1f3-fcb3-499d-afb5-ea1f8c33ede0.png" width="200"/>
This can be partially considered an accessibility issue, as users with difficulty reading small texts are more likely to change Android interface/font scaling option.
## Steps to reproduce
How often can you reproduce the bug: always
#### Steps:
1. Open Android Settings app -> Display (Some vendors might have different locations, for example in Accessibility -> Vision -> Display)
2. Find Display scale settings, change it to the largest
3. Find Font scale settings, change it to the largest
4. Open Jami, make a voice/video call
#### Expected result:
Buttons in CallView are visible. I can hang-up the call without using Android notification center.
#### Actual result:
Buttons are missing in CallView, including the hang-up button. I have to resort to notification center to hang-up the call.
## Additional information
Jami has multiple similar issues when display scale is too large (logical size is too small), like https://git.jami.net/savoirfairelinux/jami-client-android/-/issues/1226 to name one.https://git.jami.net/savoirfairelinux/jami-project/-/issues/1637Show translated article title in the web browser window title2024-03-16T22:01:55ZovariShow translated article title in the web browser window titlePlease show the translated article title in the web browser window title
https://jami.net/improved-reliability-presence-and-message-status/?lang=hu
![image](/uploads/538d1bca53735f8538ac534254484264/image.png)
Thank you
Cc: @plarosePlease show the translated article title in the web browser window title
https://jami.net/improved-reliability-presence-and-message-status/?lang=hu
![image](/uploads/538d1bca53735f8538ac534254484264/image.png)
Thank you
Cc: @plarosehttps://git.jami.net/savoirfairelinux/jami-project/-/issues/1636Newsletter Privacy Policy2024-03-16T21:57:00ZovariNewsletter Privacy PolicyPlease enable `Newsletter Privacy Policy` to be translatable
https://jami.net/newsletter-privacy-policy/?lang=hu
Thank you
Cc: @plarosePlease enable `Newsletter Privacy Policy` to be translatable
https://jami.net/newsletter-privacy-policy/?lang=hu
Thank you
Cc: @plarosehttps://git.jami.net/savoirfairelinux/jami-project/-/issues/1635Overlap of text and images2024-03-27T10:38:45ZovariOverlap of text and imageshttps://jami.net/?lang=hu
![image](/uploads/73727ddaebdba6cfcb5eb6a3e20327bb/image.png)
Thank you
Cc: @plarosehttps://jami.net/?lang=hu
![image](/uploads/73727ddaebdba6cfcb5eb6a3e20327bb/image.png)
Thank you
Cc: @plarosehttps://git.jami.net/savoirfairelinux/jami-client-qt/-/issues/1600Swarm conversation does no load after restoring account backup2024-03-25T15:21:11Zring userSwarm conversation does no load after restoring account backupBug report form
---------------
## Describe your environment
Please specify the following:
Device 0. is not available anymore and had account A and had a connection to account B as well ad device 2.
1.
- OS: Ubuntu 22.04
- Jami versi...Bug report form
---------------
## Describe your environment
Please specify the following:
Device 0. is not available anymore and had account A and had a connection to account B as well ad device 2.
1.
- OS: Ubuntu 22.04
- Jami version: Current Snap: Eleutheria Version: 202402141827
- What build you are using: Snap
- EDIT: Account A.
2.
- OS: Android
- Jami version: Current F-Droid: Eleutheria 20240308-01
- What build you are using: Snap
- EDIT: Account B.
## Steps to reproduce
Note: Better the scenario is, better we will be able to reproduce and debug.
- Can you reproduce the bug: at will
- Steps:
1. Import a backup of a Jami account A. in Jami 1.
2. Both Jami 1 and Jami 2 are online
3. I open a conversation between Jami 1. and 2.
4. I send a messages from 2. to 1.
- Actual result:
1. If I open the conversation on device 1., I see the following message:
- `Sie haben die Unterhaltungsanfrage angenommen`
- `Warten bis ## eine Verbindung herstellt, um die Unterhaltung zu synchronisieren.`
2. I cannot read any messages or chat because neither the messages nor the chat text field is shown.
3. Calls are working.
4. There is no possibility to continue the conversation.
- Expected result:
1. The conversation is synchronizing or is synchronized and I can use it.
2. The messages send are shown in Jami 1.
3. Calls are working.
4. I can continue the conversation.
## Additional information
```
[1710587184.680|43502|manager.cpp :957 ] ############## START MONITORING ##############
[1710587184.680|43502|manager.cpp :958 ] Using PJSIP version 2.13.1 for x86_64-pc-linux-gnu
[1710587184.680|43502|manager.cpp :959 ] Using GnuTLS version 3.8.2
[1710587184.680|43502|manager.cpp :960 ] Using OpenDHT version 3.1.7
[1710587184.680|43502|manager.cpp :967 ] Opened files: 106
[1710587184.680|43502] ConnectionManager current status:
[1710587184.680|43502] ConnectionManager end status.
[1710587184.680|43502|manager.cpp :976 ] ############## END MONITORING ##############
[1710587196.589|43915] [device ###] Received request answer
[1710587196.589|43915] [device ###] Respond received, but cannot find request
```
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-project/-/issues/1634Add `Subscribe to newsletter` to `Join the Jami community` on https://jami.ne...2024-03-16T10:53:34ZovariAdd `Subscribe to newsletter` to `Join the Jami community` on https://jami.net/contribute/@plarose should `Subscribe to the Jami newsletter` be added to https://jami.net/contribute/ under the section `Join the Jami community`?
![image](/uploads/3614ba3db7ea7192c2095e4f3bb7c18d/image.png)
What do you think?
Thank you@plarose should `Subscribe to the Jami newsletter` be added to https://jami.net/contribute/ under the section `Join the Jami community`?
![image](/uploads/3614ba3db7ea7192c2095e4f3bb7c18d/image.png)
What do you think?
Thank youhttps://git.jami.net/savoirfairelinux/jami-project/-/issues/1633`Mailling` typo? Should it be `Mailing`, i.e. only 1 "l"?2024-03-16T10:43:57Zovari`Mailling` typo? Should it be `Mailing`, i.e. only 1 "l"?1. Visit https://jami.net/contribute/
2. Under the `Join the Jami community` heading
3. `Mailling` typo? Should it be `Mailing`, i.e. only 1 "l"?<br>
![image](/uploads/07245250bff2357eaf9ce60688ccf32d/image.png)
What do you think?
Than...1. Visit https://jami.net/contribute/
2. Under the `Join the Jami community` heading
3. `Mailling` typo? Should it be `Mailing`, i.e. only 1 "l"?<br>
![image](/uploads/07245250bff2357eaf9ce60688ccf32d/image.png)
What do you think?
Thank you
Cc: @plarosehttps://git.jami.net/savoirfairelinux/jami-project/-/issues/1632Add `MUO` article to `Mentioned In` on https://jami.net/2024-03-16T10:25:38ZovariAdd `MUO` article to `Mentioned In` on https://jami.net/@plarose should a link to the `MUO: Make Use Of_` article below be added to https://jami.net/ under the section `Mentioned In`?
![image](/uploads/cf97b795007a0e4a5bd2835799a29ca3/image.png)
`MUO: Make Use Of_` article by Danny Maiorca ...@plarose should a link to the `MUO: Make Use Of_` article below be added to https://jami.net/ under the section `Mentioned In`?
![image](/uploads/cf97b795007a0e4a5bd2835799a29ca3/image.png)
`MUO: Make Use Of_` article by Danny Maiorca and Hilda Munjuri Updated Mar 8, 2024
### The 4 Best Open-Source Video Conferencing Software
https://www.makeuseof.com/open-source-video-conferencing-software/
![image](/uploads/df746224a25bd87821b05939e5e18dbd/image.png)
What do you think?
Thank youhttps://git.jami.net/savoirfairelinux/jami-client-ios/-/issues/360update UI for swarm creation2024-03-14T19:42:04ZKateryna Kostiukupdate UI for swarm creationKateryna KostiukKateryna Kostiukhttps://git.jami.net/savoirfairelinux/jami-client-android/-/issues/1628Layout bugs on settings pages2024-03-13T14:58:49ZVitalii NikitchynLayout bugs on settings pages- Jami version: 20240308-01
- Device model: all (landscape view mode)
- What build you are using: my own -> 86f9804af37b06df6b46a2992c55810782415a80
1. Scrollview cut bottom content on settings pages. Check all settings fragment, ...- Jami version: 20240308-01
- Device model: all (landscape view mode)
- What build you are using: my own -> 86f9804af37b06df6b46a2992c55810782415a80
1. Scrollview cut bottom content on settings pages. Check all settings fragment, including "Account Settings", "Advanced Settings" and "About Jami"
![menu](/uploads/e44094c8558b7b2bd9e12629a0319efd/menu.png)
![Screenshot_1710268084](/uploads/c3ca4443c764d0f320869cb1f8e01d7e/Screenshot_1710268084.png)
2. Settings fragments: Appbar blink on navigation. Check all settings fragment, including "Account Settings", "Advanced Settings" and "About Jami"
![Screen_recording_20240313_101323](/uploads/95dab11c98a7233bfde1a4096952938c/Screen_recording_20240313_101323.mp4)Vitalii NikitchynVitalii Nikitchynhttps://git.jami.net/savoirfairelinux/jami-client-qt/-/issues/1598Call ownaccount 1 -> ownaccount 2: Ownaccount 2 does not show the incoming ca...2024-03-12T17:09:11ZElysCall ownaccount 1 -> ownaccount 2: Ownaccount 2 does not show the incoming call unless you click on the account in the contact listusing Jami Version (Beta): 202403061444
Steps to reproduce:
* You are using two own Jami accounts at the same time (desktop; Windows 10)
* Make a call own ownaccount 1 -\> ownaccount 2 (while you are viewing the contact list of "ownacc...using Jami Version (Beta): 202403061444
Steps to reproduce:
* You are using two own Jami accounts at the same time (desktop; Windows 10)
* Make a call own ownaccount 1 -\> ownaccount 2 (while you are viewing the contact list of "ownaccount1")
* You view the ongoing call (like "Connecting", "Calling")
* Now go to ownaccount 2: You just view the contact list (and "ongoing call" within the contact list) but you actually don't view the "incoming call banner" - You have to click on the contact in the contact list to view the call banner
---
Not sure if it should be possible -but system notifications also won't be shownhttps://git.jami.net/savoirfairelinux/jami-client-android/-/issues/1627Missing conversation info for swarm group2024-03-28T00:05:08ZPierre NicolasMissing conversation info for swarm group## Describe your environment
Please specify the following:
- Jami version: 410
## Steps to reproduce
- Can you reproduce the bug: at will
## Additional information
Missing conversation info for swarm group when last event is a call...## Describe your environment
Please specify the following:
- Jami version: 410
## Steps to reproduce
- Can you reproduce the bug: at will
## Additional information
Missing conversation info for swarm group when last event is a call.
![image.png](/uploads/3bedaabdea35e819f7afedd020106c69/image.png){width=306 height=680}
![image.png](/uploads/de3813cef463866ba3e83170b74fe34f/image.png){width=311 height=691}Pierre NicolasPierre Nicolashttps://git.jami.net/savoirfairelinux/jami-client-android/-/issues/1626Message separation not respected2024-03-28T00:05:08ZPierre NicolasMessage separation not respected## Describe your environment
Please specify the following:
- Jami version: 410
## Steps to reproduce
- Can you reproduce the bug: at will
## Additional information
![image.png](/uploads/ffeb638f1d63eb27162635ff6e17f35d/image.png){w...## Describe your environment
Please specify the following:
- Jami version: 410
## Steps to reproduce
- Can you reproduce the bug: at will
## Additional information
![image.png](/uploads/ffeb638f1d63eb27162635ff6e17f35d/image.png){width=383 height=851}Pierre NicolasPierre Nicolashttps://git.jami.net/savoirfairelinux/jami-client-qt/-/issues/1597Jami's storage is too large2024-03-11T16:40:34Zsession 21Jami's storage is too largeI still have a lot of space on my C drive, but Jami's usage still surprises me. Can Jami move chat records to another disk.
![6b364783444bdc4352b0a7e64460542945d09f2d_848593296952902.png](/uploads/522bb49d21836c7a6b4ed3b029c15b38/6b3647...I still have a lot of space on my C drive, but Jami's usage still surprises me. Can Jami move chat records to another disk.
![6b364783444bdc4352b0a7e64460542945d09f2d_848593296952902.png](/uploads/522bb49d21836c7a6b4ed3b029c15b38/6b364783444bdc4352b0a7e64460542945d09f2d_848593296952902.png)
This is just a chat record of a conversation, of course, the files, pictures, and videos downloaded by Jami are also on the C drive.https://git.jami.net/savoirfairelinux/dhtnet/-/issues/24Another Upnp crash - on conversation change2024-03-09T14:34:16ZCyrille BéraudAnother Upnp crash - on conversation change`Thread 22998 "jamid" received signal SIGABRT, Aborted.
[Switching to Thread 0x7ffac57fa6c0 (LWP 130363)]
__pthread_kill_implementation (no_tid=0, signo=6, threadid=<optimized out>)
at ./nptl/pthread_kill.c:44
44 ./nptl/pthread_kill....`Thread 22998 "jamid" received signal SIGABRT, Aborted.
[Switching to Thread 0x7ffac57fa6c0 (LWP 130363)]
__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 0x00007ffff64428e6 in __GI_raise (sig=sig@entry=6)
at ../sysdeps/posix/raise.c:26
#4 0x00007ffff64268b7 in __GI_abort () at ./stdlib/abort.c:79
#5 0x00007ffff6427750 in __libc_message (
fmt=fmt@entry=0x7ffff65c38d3 "*** %s ***: terminated\n")
at ../sysdeps/posix/libc_fatal.c:150
#6 0x00007ffff6537c9b in __GI___fortify_fail (
msg=msg@entry=0x7ffff65c8a98 "bit out of range 0 - FD_SETSIZE on fd_set")
at ./debug/fortify_fail.c:24
#7 0x00007ffff6537792 in __GI___fdelt_chk (d=<optimized out>)
at ./debug/fdelt_chk.c:26
#8 0x000055555611633d in sock_read_write ()
#9 0x00005555561184b8 in http_SendMessage ()
#10 0x00005555561185c5 in http_RequestAndResponse ()
#11 0x0000555556119686 in http_Download ()
#12 0x000055555610e3cd in UpnpDownloadUrlItem ()
#13 0x000055555610e432 in UpnpDownloadXmlDoc ()
--Type <RET> for more, q to quit, c to continue without paging--
#14 0x0000555555f335d1 in dhtnet::upnp::PUPnP::downLoadIgdDescription(std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&)
()
#15 0x0000555555f33932 in std::_Function_handler<void (), dhtnet::upnp::PUPnP::processDiscoverySearchResult(std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&, std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&, dhtnet::IpAddr const&)::{lambda()#1}>::_M_invoke(std::_Any_data const&) ()
#16 0x000055555600ee9e in std::thread::_State_impl<std::thread::_Invoker<std::tuple<dht::ThreadPool::run(std::function<void ()>&&)::{lambda()#1}> > >::_M_run()
()
#17 0x00007ffff68e6333 in ?? () from /lib/x86_64-linux-gnu/libstdc++.so.6
#18 0x00007ffff6497b5a in start_thread (arg=<optimized out>)
at ./nptl/pthread_create.c:444
#19 0x00007ffff65285fc in clone3 ()
at ../sysdeps/unix/sysv/linux/x86_64/clone3.S:78
(gdb)
`Adrien BéraudSébastien BlinAdrien Béraudhttps://git.jami.net/savoirfairelinux/dhtnet/-/issues/23"jamid" received signal SIGABRT, Aborted.2024-03-22T14:34:23ZCyrille 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
jami-daemon#1 __pthread_kill_internal (signo=6, threadid=<optimized out>) at ./nptl/pthread_kill.c:78
jami-daemon#2 __GI___pthread_kill (threadid=<optimized out>, signo=signo@entry=6) at ./nptl/pthread_kill.c:89
jami-daemon#3 0x00007ffff66428e6 in __GI_raise (sig=sig@entry=6) at ../sysdeps/posix/raise.c:26
jami-daemon#4 0x00007ffff66268b7 in __GI_abort () at ./stdlib/abort.c:79
jami-daemon#5 0x00007ffff6627750 in __libc_message (fmt=fmt@entry=0x7ffff67c38d3 "*** %s ***: terminated\n") at ../sysdeps/posix/libc_fatal.c:150
jami-daemon#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
jami-daemon#7 0x00007ffff6737792 in __GI___fdelt_chk (d=<optimized out>) at ./debug/fdelt_chk.c:26
jami-daemon#8 0x0000555555f41224 in dhtnet::upnp::NatPmp::readResponse(natpmp_t&, natpmpresp_t&) ()
jami-daemon#9 0x0000555555f42790 in dhtnet::upnp::NatPmp::getIgdPublicAddress() ()
jami-daemon#10 0x0000555555f430e3 in dhtnet::upnp::NatPmp::initNatPmp() ()
jami-daemon#11 0x0000555555f47075 in dhtnet::upnp::NatPmp::searchForIgd() ()
jami-daemon#12 0x0000555555f43b99 in asio::detail::wait_handler<dhtnet::upnp::NatPmp::searchForIgd()::{lambda(std::error_code const&)jami-daemon#1}, asio::any_io_executor>::do_complete(void*, asio::detail::scheduler_operation*, std::error_code const&, unsigned long) ()
jami-daemon#13 0x0000555555f2115e in asio::detail::scheduler::run(std::error_code&) [clone .isra.0] ()
jami-daemon#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()jami-daemon#1}> > >::_M_run() ()
jami-daemon#15 0x00007ffff6ae6333 in ?? () from /lib/x86_64-linux-gnu/libstdc++.so.6
jami-daemon#16 0x00007ffff6697b5a in start_thread (arg=<optimized out>) at ./nptl/pthread_create.c:444
jami-daemon#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
jami-daemon#1 __pthread_kill_internal (signo=6, threadid=<optimized out>) at ./nptl/pthread_kill.c:78
jami-daemon#2 __GI___pthread_kill (threadid=<optimized out>, signo=signo@entry=6) at ./nptl/pthread_kill.c:89
jami-daemon#3 0x00007ffff66428e6 in __GI_raise (sig=sig@entry=6) at ../sysdeps/posix/raise.c:26
jami-daemon#4 0x00007ffff66268b7 in __GI_abort () at ./stdlib/abort.c:79
jami-daemon#5 0x00007ffff6627750 in __libc_message (fmt=fmt@entry=0x7ffff67c38d3 "*** %s ***: terminated\n") at ../sysdeps/posix/libc_fatal.c:150
jami-daemon#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
jami-daemon#7 0x00007ffff6737792 in __GI___fdelt_chk (d=<optimized out>) at ./debug/fdelt_chk.c:26
jami-daemon#8 0x0000555555f41224 in dhtnet::upnp::NatPmp::readResponse(natpmp_t&, natpmpresp_t&) ()
jami-daemon#9 0x0000555555f42790 in dhtnet::upnp::NatPmp::getIgdPublicAddress() ()
jami-daemon#10 0x0000555555f430e3 in dhtnet::upnp::NatPmp::initNatPmp() ()
jami-daemon#11 0x0000555555f47075 in dhtnet::upnp::NatPmp::searchForIgd() ()
jami-daemon#12 0x0000555555f43b99 in asio::detail::wait_handler<dhtnet::upnp::NatPmp::searchForIgd()::{lambda(std::error_code const&)jami-daemon#1}, asio::any_io_executor>::do_complete(void*, asio::detail::scheduler_operation*, std::error_code const&, unsigned long) ()
jami-daemon#13 0x0000555555f2115e in asio::detail::scheduler::run(std::error_code&) [clone .isra.0] ()
jami-daemon#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()jami-daemon#1}> > >::_M_run() ()
jami-daemon#15 0x00007ffff6ae6333 in ?? () from /lib/x86_64-linux-gnu/libstdc++.so.6
jami-daemon#16 0x00007ffff6697b5a in start_thread (arg=<optimized out>) at ./nptl/pthread_create.c:444
jami-daemon#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
jami-daemon#1 __pthread_kill_internal (signo=6, threadid=<optimized out>) at ./nptl/pthread_kill.c:78
jami-daemon#2 __GI___pthread_kill (threadid=<optimized out>, signo=signo@entry=6) at ./nptl/pthread_kill.c:89
jami-daemon#3 0x00007ffff66428e6 in __GI_raise (sig=sig@entry=6) at ../sysdeps/posix/raise.c:26
jami-daemon#4 0x00007ffff66268b7 in __GI_abort () at ./stdlib/abort.c:79
jami-daemon#5 0x00007ffff6627750 in __libc_message (fmt=fmt@entry=0x7ffff67c38d3 "*** %s ***: terminated\n") at ../sysdeps/posix/libc_fatal.c:150
jami-daemon#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
jami-daemon#7 0x00007ffff6737792 in __GI___fdelt_chk (d=<optimized out>) at ./debug/fdelt_chk.c:26
jami-daemon#8 0x0000555555f41224 in dhtnet::upnp::NatPmp::readResponse(natpmp_t&, natpmpresp_t&) ()
jami-daemon#9 0x0000555555f42790 in dhtnet::upnp::NatPmp::getIgdPublicAddress() ()
jami-daemon#10 0x0000555555f430e3 in dhtnet::upnp::NatPmp::initNatPmp() ()
jami-daemon#11 0x0000555555f47075 in dhtnet::upnp::NatPmp::searchForIgd() ()
jami-daemon#12 0x0000555555f43b99 in asio::detail::wait_handler<dhtnet::upnp::NatPmp::searchForIgd()::{lambda(std::error_code const&)jami-daemon#1}, asio::any_io_executor>::do_complete(void*, asio::detail::scheduler_operation*, std::error_code const&, unsigned long) ()
jami-daemon#13 0x0000555555f2115e in asio::detail::scheduler::run(std::error_code&) [clone .isra.0] ()
jami-daemon#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()jami-daemon#1}> > >::_M_run() ()
jami-daemon#15 0x00007ffff6ae6333 in ?? () from /lib/x86_64-linux-gnu/libstdc++.so.6
jami-daemon#16 0x00007ffff6697b5a in start_thread (arg=<optimized out>) at ./nptl/pthread_create.c:444
jami-daemon#17 0x00007ffff67285fc in clone3 () at ../sysdeps/unix/sysv/linux/x86_64/clone3.S:78
(gdb)
`Sébastien BlinAdrien BéraudSébastien Blinhttps://git.jami.net/savoirfairelinux/jami-client-ios/-/issues/359User not receiving notifications #22024-03-08T16:31:01ZAndreas TraczykUser not receiving notifications #2 - at first, the user receives notifications from the desktop app
- then, the user stops receiving notifications for no apparent reason
- after peer restart, the cycle repeats
- ~100% reproducible - at first, the user receives notifications from the desktop app
- then, the user stops receiving notifications for no apparent reason
- after peer restart, the cycle repeats
- ~100% reproduciblehttps://git.jami.net/savoirfairelinux/jami-client-ios/-/issues/358User not receiving notifications #12024-03-08T16:26:31ZAndreas TraczykUser not receiving notifications #1 - STEPS TO REPRODUCE (not 100% reproducible):
- send a message to the user when the app is in the background
- the user will not receive a notification
- HYPOTHESIS:
- dht::shutdown is deadlocked
- any pending o... - STEPS TO REPRODUCE (not 100% reproducible):
- send a message to the user when the app is in the background
- the user will not receive a notification
- HYPOTHESIS:
- dht::shutdown is deadlocked
- any pending opendht patches?https://git.jami.net/savoirfairelinux/jami-client-ios/-/issues/357Presence for group-swarms not shown2024-03-08T16:10:25ZAndreas TraczykPresence for group-swarms not shownIf at least one member of the swarm has presence, this should be used in the smart-list for the item presence.If at least one member of the swarm has presence, this should be used in the smart-list for the item presence.https://git.jami.net/savoirfairelinux/jami-client-ios/-/issues/356Toggling enable-notifications setting not persistent2024-03-08T16:03:28ZAndreas TraczykToggling enable-notifications setting not persistent - STEPS TO REPRODUCE (not 100% reproducible):
- toggle enable-notifications setting
- put app in background
- put app in foreground
- maybe restart the app
- other actions TBD (do some actions in the app, etc.)
... - STEPS TO REPRODUCE (not 100% reproducible):
- toggle enable-notifications setting
- put app in background
- put app in foreground
- maybe restart the app
- other actions TBD (do some actions in the app, etc.)
- the setting will be reset to the previous value