savoirfairelinux issueshttps://git.jami.net/groups/savoirfairelinux/-/issues2023-12-21T14:52:59Zhttps://git.jami.net/savoirfairelinux/jami-plugins/-/issues/61Cleanup: remove useless ffmpeg contrib2023-12-21T14:52:59ZSébastien BlinCleanup: remove useless ffmpeg contribAlready all symbols are in the daemonAlready all symbols are in the daemonhttps://git.jami.net/savoirfairelinux/jami-client-android/-/issues/1505Return to ongoing call banner does not display itself immediately2023-12-20T19:31:51ZEmma FalkiewitzReturn to ongoing call banner does not display itself immediately## Steps to reproduce
![Screen_recording_20231220_142439.mp4](/uploads/6428474aeb1111970749465b9dc2f507/Screen_recording_20231220_142439.mp4)
- Expected result: have the return to ongoing call banner in the conversation immediately (we...## Steps to reproduce
![Screen_recording_20231220_142439.mp4](/uploads/6428474aeb1111970749465b9dc2f507/Screen_recording_20231220_142439.mp4)
- Expected result: have the return to ongoing call banner in the conversation immediately (we don't need to change conversation to have it displayed).https://git.jami.net/savoirfairelinux/dhtnet/-/issues/15Peer Discovery: Validate design in dhtnet2024-03-28T00:05:08ZSébastien BlinPeer Discovery: Validate design in dhtnet# TODO
+ add tests
+ Manually test on all distribution# TODO
+ add tests
+ Manually test on all distributionAmna SneneAmna Snenehttps://git.jami.net/savoirfairelinux/jami-daemon/-/issues/930POC: new linking account mechanism2024-03-28T00:05:08ZSébastien BlinPOC: new linking account mechanism# Goal
Do not use the DHT to transfer the account archive while linking a new device, but rather use a p2p link between the new and old device
# TODO
+ Define architecture
+ POC (client)
+ add docs to docs.jami.net
+ Finalize daemon c...# Goal
Do not use the DHT to transfer the account archive while linking a new device, but rather use a p2p link between the new and old device
# TODO
+ Define architecture
+ POC (client)
+ add docs to docs.jami.net
+ Finalize daemon code
+ Ping design & clients to implement the featureKessler DuPont-TeevinAdrien BéraudKessler DuPont-Teevin2024-01-31https://git.jami.net/savoirfairelinux/jami-client-ios/-/issues/312Performance analysis: Provide report with profiler/flamegraph/perf2024-03-28T00:05:08ZSébastien BlinPerformance analysis: Provide report with profiler/flamegraph/perf# Problem
Lot of users report an abnormal battery drain
# Todo
+ Get metrics for performance analysis
+ This will provide bottlenecks and information about where the CPU is used (and if there is CPU loop)
# Next
Mitigate detected is...# Problem
Lot of users report an abnormal battery drain
# Todo
+ Get metrics for performance analysis
+ This will provide bottlenecks and information about where the CPU is used (and if there is CPU loop)
# Next
Mitigate detected issues by priorityKateryna KostiukKateryna Kostiukhttps://git.jami.net/savoirfairelinux/jami-client-android/-/issues/1495The recycling highlight when clicking on a replied message doesn't work.2023-12-20T15:36:02ZEmma FalkiewitzThe recycling highlight when clicking on a replied message doesn't work.
![Screen_recording_20231220_103451](/uploads/e65249f56a2b025fa459acb483e03a3f/Screen_recording_20231220_103451.mp4)
![Screen_recording_20231220_103451](/uploads/e65249f56a2b025fa459acb483e03a3f/Screen_recording_20231220_103451.mp4)https://git.jami.net/savoirfairelinux/jami-client-android/-/issues/1493Jami plugins2023-12-21T20:20:17ZPierre NicolasJami plugins* [ ] greenscreen is not functional, to check for others plugins
* [ ] it looks like plugins are loaded in UI thread which cause application not responding
* [ ] UX weird on plugin disabled/enabled on call (see 1)
* [ ] should not try to...* [ ] greenscreen is not functional, to check for others plugins
* [ ] it looks like plugins are loaded in UI thread which cause application not responding
* [ ] UX weird on plugin disabled/enabled on call (see 1)
* [ ] should not try to install a plugin if already installed
* [ ] install a plugin should show a loading UX
* [ ] install a plugin should not send user back on advanced setting page (should stay on plugin list page)
* [ ] remove a plugin should not send user back on homeactivity (should stay on plugin list page)
* [ ] reset plugin settings should not send user back on homeactivity (should stay on the plugin page)
* [ ] "automatically activate plugin" feature doesn't seem to be taken into account
(1) ![image.png](/uploads/6eb612b73a06c2743a931d04babb70ec/image.png){width="252" height="181"} ![image.png](/uploads/bf9479a7bce2bf9d5c1a65b526c3f633/image.png){width="253" height="181"}https://git.jami.net/savoirfairelinux/jami-client-android/-/issues/1492Plugin installed but not working/enabled (GreenScreen & Whisper)2024-03-28T00:05:08ZSébastien BlinPlugin installed but not working/enabled (GreenScreen & Whisper)# Scenario
+ Install GreenScreen or Whisper (settings by default are correct, also plugins is enabled by default)
+ Start a call
# Current result
+ GreenScreen or Whisper is not working & seems disabled (from the checkbox) in the plug...# Scenario
+ Install GreenScreen or Whisper (settings by default are correct, also plugins is enabled by default)
+ Start a call
# Current result
+ GreenScreen or Whisper is not working & seems disabled (from the checkbox) in the plugin list
# Expected
Greenscreen or Whisper must workhttps://git.jami.net/savoirfairelinux/jami-packaging/-/issues/155Flatpak Application2023-12-20T07:06:02Zex3mptedFlatpak ApplicationIt would be great to see flatpak distribution to support more distros. While there seems to be a flatpak app on flathub, it doesn't seem to be verified with the developers of Jami & has not been listed on the site. Creating a flathub app...It would be great to see flatpak distribution to support more distros. While there seems to be a flatpak app on flathub, it doesn't seem to be verified with the developers of Jami & has not been listed on the site. Creating a flathub app would ensure reach in linux.https://git.jami.net/savoirfairelinux/jami-daemon/-/issues/927Android: Same contact multiple times (multi device related?)2023-12-16T18:01:12ZElysAndroid: Same contact multiple times (multi device related?)Desktop (Beta): 202312142117
Android (20231213-01)
Steps to reproduce:
- You are using the same Jami account ("Jamiaccount1") on different devices - and you always have your own Jami account in the contact list (so you can make calls /...Desktop (Beta): 202312142117
Android (20231213-01)
Steps to reproduce:
- You are using the same Jami account ("Jamiaccount1") on different devices - and you always have your own Jami account in the contact list (so you can make calls / send messages "Jamiaccount1" device 1 <-> "Jamiaccount1" device 2)
- - only the desktop device 1 also has another own account "Jamiaccount2": "Jamiaccount1" is in the contact list of "Jamiaccount2" (and the other direction); however "Jamiaccount2" account does NOT have it's own account in the contact list?
- BUT you always use the same two devices (desktop and android phone) for weeks
- Now you are using a different desktop device (3) that only uses "Jamiaccount2" (device 3)contact ("Jamiaccount1") is already in the contact list of "Jamiaccount2" (device 1,2) because you've added "Jamiaccount2" on another device
- Once you open Jami on desktop - Jami on Android will create another same contact of "Jamiaccount1" and if you tap the duplicated contact the chatview will stuck at "Downloading conversation from peer" (even if you restart Jami on Android)
Screenshot (of the Android device)
![Jamitwice1](/uploads/32a667c3f81374effdc83094bcd1c85c/Jamitwice1.png)
Detail:
![Jamitwice2](/uploads/456f273bf0080e14b7b569cdb820656e/Jamitwice2.png)https://git.jami.net/savoirfairelinux/jami-client-qt/-/issues/1454Allow users to supply postmortem reports2024-03-28T00:05:08ZAndreas TraczykAllow users to supply postmortem reports**Objective**:
* Implement a feature allowing users to submit postmortem reports.
**Purpose**:
* To collect data for improving application stability.
**User Story**:
* As a user, I want to be able to submit postmortem reports so tha...**Objective**:
* Implement a feature allowing users to submit postmortem reports.
**Purpose**:
* To collect data for improving application stability.
**User Story**:
* As a user, I want to be able to submit postmortem reports so that I can contribute to the improvement of the application.
**Requirements**:
* [ ] A flag in system settings should detect a postmortem run.
* [ ] A submission interface in the application for postmortem reports.
* [ ] Option for users to opt-in for automatic submission of postmortem reports.
* [ ] A server-side implementation (POST) and an alternate, manual client-side submission mechanism.
* [ ] Postmorem report must include platform/version info.
**User Interface**:
* Easy-to-use submission form for postmortem reports.
* Clear options for opting in or out of automatic reports.
**Server-Side Implementation**:
* Storage solution for incoming reports.Andreas TraczykAndreas Traczykhttps://git.jami.net/savoirfairelinux/jami-client-qt/-/issues/1453MSI: allow single user installs2024-02-22T20:40:29ZAndreas TraczykMSI: allow single user installsUsers without admin access should be able to install Jami.Users without admin access should be able to install Jami.Andreas TraczykAndreas Traczykhttps://git.jami.net/savoirfairelinux/jami-client-qt/-/issues/1452[Windows 11] Jami is shown twice after update(s)2024-02-01T17:22:36ZElys[Windows 11] Jami is shown twice after update(s)using Windows 11 Pro 23H2
newest version of Jami
Steps to reproduce?
1. (In the past) Install an older version of Jami
1. Now update
1. After the update you'll view Jami twice in the windows 11 settings "Installed apps" https://www.ele...using Windows 11 Pro 23H2
newest version of Jami
Steps to reproduce?
1. (In the past) Install an older version of Jami
1. Now update
1. After the update you'll view Jami twice in the windows 11 settings "Installed apps" https://www.elevenforum.com/t/find-storage-space-usage-size-of-apps-in-windows-11.14129/
Screenshot:
![Screenshot-double](/uploads/40dcd79be56917b9dd5502fab00ca64a/Screenshot-double.png)https://git.jami.net/savoirfairelinux/jami-project/-/issues/1622Please allow https://jami.biz/ to be translated2024-01-26T12:36:39ZovariPlease allow https://jami.biz/ to be translatedPlease add [JAMS Website](https://jami.biz/) as a project to [Transifex](https://explore.transifex.com/savoirfairelinux/) to enable translation.
![Transifex projects](/uploads/a4396f62b6beddc872d5410af6e8f6a4/image.png)
What do you thi...Please add [JAMS Website](https://jami.biz/) as a project to [Transifex](https://explore.transifex.com/savoirfairelinux/) to enable translation.
![Transifex projects](/uploads/a4396f62b6beddc872d5410af6e8f6a4/image.png)
What do you think?
Thank you
Cc: @plarosehttps://git.jami.net/savoirfairelinux/jami-client-qt/-/issues/1449Add a donate button in "About Jami" popup2024-02-14T20:26:56ZCharlotte HoffmannAdd a donate button in "About Jami" popupAdd a donate button after "feedback"Add a donate button after "feedback"Andreas TraczykAndreas Traczykhttps://git.jami.net/savoirfairelinux/jami-daemon/-/issues/926Crash in OpenSSL (JAMS deletion) - heap use after free2023-12-05T21:03:14ZSébastien BlinCrash in OpenSSL (JAMS deletion) - heap use after free```
#0 0x7f00b503a396 in __interceptor_memcpy ../../../../src/libsanitizer/sanitizer_common/sanitizer_common_interceptors.inc:827
#1 0x7f00a10e1361 (/lib/x86_64-linux-gnu/libcrypto.so.3+0xe1361)
#2 0x7f00a10d234a (/lib/x86_...```
#0 0x7f00b503a396 in __interceptor_memcpy ../../../../src/libsanitizer/sanitizer_common/sanitizer_common_interceptors.inc:827
#1 0x7f00a10e1361 (/lib/x86_64-linux-gnu/libcrypto.so.3+0xe1361)
#2 0x7f00a10d234a (/lib/x86_64-linux-gnu/libcrypto.so.3+0xd234a)
#3 0x7f00a10d5344 (/lib/x86_64-linux-gnu/libcrypto.so.3+0xd5344)
#4 0x7f00a10d5b3c in BIO_read_ex (/lib/x86_64-linux-gnu/libcrypto.so.3+0xd5b3c)
#5 0x7f00a10d5344 (/lib/x86_64-linux-gnu/libcrypto.so.3+0xd5344)
#6 0x7f00a10d54c6 in BIO_read (/lib/x86_64-linux-gnu/libcrypto.so.3+0xd54c6)
#7 0x7f00a10bc059 in asn1_d2i_read_bio (/lib/x86_64-linux-gnu/libcrypto.so.3+0xbc059)
#8 0x7f00a1268716 (/lib/x86_64-linux-gnu/libcrypto.so.3+0x268716)
#9 0x7f00a125aa62 (/lib/x86_64-linux-gnu/libcrypto.so.3+0x25aa62)
#10 0x7f00a11697ba (/lib/x86_64-linux-gnu/libcrypto.so.3+0x1697ba)
#11 0x7f00a1169a90 in OSSL_DECODER_from_bio (/lib/x86_64-linux-gnu/libcrypto.so.3+0x169a90)
#12 0x7f00a1169dbd in OSSL_DECODER_from_data (/lib/x86_64-linux-gnu/libcrypto.so.3+0x169dbd)
#13 0x7f00a123fae3 (/lib/x86_64-linux-gnu/libcrypto.so.3+0x23fae3)
#14 0x7f00a10ceb9a (/lib/x86_64-linux-gnu/libcrypto.so.3+0xceb9a)
#15 0x7f00a10d03e7 (/lib/x86_64-linux-gnu/libcrypto.so.3+0xd03e7)
#16 0x7f00a10ced18 (/lib/x86_64-linux-gnu/libcrypto.so.3+0xced18)
#17 0x7f00a10d03e7 (/lib/x86_64-linux-gnu/libcrypto.so.3+0xd03e7)
#18 0x7f00a10ced18 (/lib/x86_64-linux-gnu/libcrypto.so.3+0xced18)
#19 0x7f00a10cf492 in ASN1_item_d2i_ex (/lib/x86_64-linux-gnu/libcrypto.so.3+0xcf492)
#20 0x7f00a15e8132 (/lib/x86_64-linux-gnu/libssl.so.3+0x67132)
#21 0x7f00a15e4a04 (/lib/x86_64-linux-gnu/libssl.so.3+0x63a04)
#22 0x7f00a15e6607 (/lib/x86_64-linux-gnu/libssl.so.3+0x65607)
#23 0x7f00a5176230 in asio::ssl::detail::engine::perform(int (asio::ssl::detail::engine::*)(void*, unsigned long), void*, unsigned long, std::error_code&, unsigned long*) (/home/sblin/Projects/jami-project/client-qt/daemon/src/.libs/libjami.so.0+0x1d76230)
#24 0x7f00a5135430 in asio::ssl::detail::io_op<asio::basic_stream_socket<asio::ip::tcp, asio::any_io_executor>, asio::ssl::detail::handshake_op, dht::http::Connection::async_handshake(std::function<void (std::error_code const&)>)::{lambda(std::error_code const&)#1}>::operator()(std::error_code, unsigned long, int) (/home/sblin/Projects/jami-project/client-qt/daemon/src/.libs/libjami.so.0+0x1d35430)
#25 0x7f00a514062b in asio::detail::reactive_socket_recv_op<asio::mutable_buffers_1, asio::ssl::detail::io_op<asio::basic_stream_socket<asio::ip::tcp, asio::any_io_executor>, asio::ssl::detail::handshake_op, dht::http::Connection::async_handshake(std::function<void (std::error_code const&)>)::{lambda(std::error_code const&)#1}>, asio::any_io_executor>::do_complete(void*, asio::detail::scheduler_operation*, std::error_code const&, unsigned long) (/home/sblin/Projects/jami-project/client-qt/daemon/src/.libs/libjami.so.0+0x1d4062b)
#26 0x7f00a501e62b in asio::detail::epoll_reactor::descriptor_state::do_complete(void*, asio::detail::scheduler_operation*, std::error_code const&, unsigned long) (/home/sblin/Projects/jami-project/client-qt/daemon/src/.libs/libjami.so.0+0x1c1e62b)
#27 0x7f00a3e7ebb8 in asio::detail::scheduler_operation::complete(void*, std::error_code const&, unsigned long) /home/sblin/Projects/jami-project/client-qt/daemon/contrib/x86_64-linux-gnu/include/asio/detail/scheduler_operation.hpp:39
#28 0x7f00a3e85aa6 in asio::detail::scheduler::do_run_one(asio::detail::conditionally_enabled_mutex::scoped_lock&, asio::detail::scheduler_thread_info&, std::error_code const&) /home/sblin/Projects/jami-project/client-qt/daemon/contrib/x86_64-linux-gnu/include/asio/detail/impl/scheduler.ipp:492
#29 0x7f00a3e84ed9 in asio::detail::scheduler::run(std::error_code&) /home/sblin/Projects/jami-project/client-qt/daemon/contrib/x86_64-linux-gnu/include/asio/detail/impl/scheduler.ipp:209
#30 0x7f00a3e86298 in asio::io_context::run() (/home/sblin/Projects/jami-project/client-qt/daemon/src/.libs/libjami.so.0+0xa86298)
#31 0x7f00a3e3aaef in operator() /home/sblin/Projects/jami-project/client-qt/daemon/src/manager.cpp:464
#32 0x7f00a3e73fb3 in __invoke_impl<void, jami::Manager::ManagerPimpl::ManagerPimpl(jami::Manager&)::<lambda()> > /usr/include/c++/11/bits/invoke.h:61
#33 0x7f00a3e73f76 in __invoke<jami::Manager::ManagerPimpl::ManagerPimpl(jami::Manager&)::<lambda()> > /usr/include/c++/11/bits/invoke.h:96
#34 0x7f00a3e73f23 in _M_invoke<0> /usr/include/c++/11/bits/std_thread.h:259
#35 0x7f00a3e73ef7 in operator() /usr/include/c++/11/bits/std_thread.h:266
#36 0x7f00a3e73edb in _M_run /usr/include/c++/11/bits/std_thread.h:211
#37 0x7f00a30dc252 (/lib/x86_64-linux-gnu/libstdc++.so.6+0xdc252)
#38 0x7f00a2c94ac2 in start_thread nptl/pthread_create.c:442
#39 0x7f00a2d26a3f (/lib/x86_64-linux-gnu/libc.so.6+0x126a3f)
0x62a0001c90e7 is located 3815 bytes inside of 21848-byte region [0x62a0001c8200,0x62a0001cd758)
freed by thread T0 here:
#0 0x7f00b50b4537 in __interceptor_free ../../../../src/libsanitizer/asan/asan_malloc_linux.cpp:127
#1 0x7f00a10f5174 in BUF_MEM_free (/lib/x86_64-linux-gnu/libcrypto.so.3+0xf5174)
previously allocated by thread T24 here:
#0 0x7f00b50b4887 in __interceptor_malloc ../../../../src/libsanitizer/asan/asan_malloc_linux.cpp:145
#1 0x7f00a10f6ca5 in BUF_MEM_grow (/lib/x86_64-linux-gnu/libcrypto.so.3+0xf6ca5)
Thread T24 created by T0 here:
#0 0x7f00b5058685 in __interceptor_pthread_create ../../../../src/libsanitizer/asan/asan_interceptors.cpp:216
#1 0x7f00a30dc328 in std::thread::_M_start_thread(std::unique_ptr<std::thread::_State, std::default_delete<std::thread::_State> >, void (*)()) (/lib/x86_64-linux-gnu/libstdc++.so.6+0xdc328)
#2 0x7f00a3e3b424 in jami::Manager::ManagerPimpl::ManagerPimpl(jami::Manager&) /home/sblin/Projects/jami-project/client-qt/daemon/src/manager.cpp:461
#3 0x7f00a3e90a5e in std::_MakeUniq<jami::Manager::ManagerPimpl>::__single_object std::make_unique<jami::Manager::ManagerPimpl, jami::Manager&>(jami::Manager&) /usr/include/c++/11/bits/unique_ptr.h:962
#4 0x7f00a3e3fbfe in jami::Manager::Manager() /home/sblin/Projects/jami-project/client-qt/daemon/src/manager.cpp:755
#5 0x7f00a3e3f94b in jami::Manager::instance() /home/sblin/Projects/jami-project/client-qt/daemon/src/manager.cpp:728
#6 0x7f00a3f83bee in libjami::init(libjami::InitFlag) /home/sblin/Projects/jami-project/client-qt/daemon/src/ring_api.cpp:69
#7 0x5637e3d41766 in InstanceManagerInterface::InstanceManagerInterface(bool) /home/sblin/Projects/jami-project/client-qt/src/libclient/qtwrapper/instancemanager.cpp:54
#8 0x5637e4e588c7 (/home/sblin/Projects/jami-project/client-qt/build/jami+0x1d568c7)
SUMMARY: AddressSanitizer: heap-use-after-free ../../../../src/libsanitizer/sanitizer_common/sanitizer_common_interceptors.inc:827 in __interceptor_memcpy
Shadow bytes around the buggy address:
0x0c54800311c0: fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd
0x0c54800311d0: fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd
0x0c54800311e0: fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd
0x0c54800311f0: fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd
0x0c5480031200: fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd
=>0x0c5480031210: fd fd fd fd fd fd fd fd fd fd fd fd[fd]fd fd fd
0x0c5480031220: fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd
0x0c5480031230: fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd
0x0c5480031240: fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd
0x0c5480031250: fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd
0x0c5480031260: fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd
Shadow byte legend (one shadow byte represents 8 application bytes):
Addressable: 00
Partially addressable: 01 02 03 04 05 06 07
Heap left redzone: fa
Freed heap region: fd
Stack left redzone: f1
Stack mid redzone: f2
Stack right redzone: f3
Stack after return: f5
Stack use after scope: f8
Global redzone: f9
Global init order: f6
Poisoned by user: f7
Container overflow: fc
Array cookie: ac
Intra object redzone: bb
ASan internal: fe
Left alloca redzone: ca
Right alloca redzone: cb
Shadow gap: cc
==596032==ABORTING
```https://git.jami.net/savoirfairelinux/jami-client-qt/-/issues/1447emoji picker out of window2023-12-05T14:48:26ZPierre Nicolasemoji picker out of window## Describe your environment
- OS: Ubuntu 22.04
- Jami version: 202311212345
- What build you are using: ubuntu software store
## Additional information
![Kazam_screencast_00008](/uploads/af81df16f402adebcb713e00d04f933e/Kazam_screenc...## Describe your environment
- OS: Ubuntu 22.04
- Jami version: 202311212345
- What build you are using: ubuntu software store
## Additional information
![Kazam_screencast_00008](/uploads/af81df16f402adebcb713e00d04f933e/Kazam_screencast_00008.webm)https://git.jami.net/savoirfairelinux/dhtnet/-/issues/12"undefined reference to" For "uuid_unparse" And "uuid_generate"2024-03-09T00:41:19Zvindicatorr"undefined reference to" For "uuid_unparse" And "uuid_generate"It's been like over a year since I've looked at this project and am noticing changes in the build process, this being one of them...
Using:
opendht: 297e182576f962e9bca6343110f9dcb5c72d2c05 (built/installed/running successfully)
pjp...It's been like over a year since I've looked at this project and am noticing changes in the build process, this being one of them...
Using:
opendht: 297e182576f962e9bca6343110f9dcb5c72d2c05 (built/installed/running successfully)
pjproject: 311bd018fc07aaf62d4c2d2494e08b5ee97e6846 (built/installed/questionable?)
dhtnet: b1bcdecbac2a41de3941ef5a34faa6fbe4472535 (trying to build)
I even copied the pjproject files over to the associated dependencies folder and edit the `build.py`to only build that (already had restinio installed), since this is where I narrowed down the issue to.
```
$ cmake .. -DCMAKE_INSTALL_PREFIX=/usr/local -DCMAKE_BUILD_TYPE=Release -DBUILD_DEPENDENCIES=OFF -DBUILD_TESTING=OFF -DCMAKE_PREFIX_PATH=/usr/local
...
dependencies path: /<pathTo>/dhtnet/dependencies/install/
...
-- Checking for one of the modules 'opendht'
-- Checking for one of the modules 'libpjproject'
-- Checking for one of the modules 'upnp;libupnp'
-- Checking for one of the modules 'natpmp'
...
```
Building failed with the error above:
```
[ 74%] Linking CXX executable dnc
/usr/bin/ld: /usr/lib/libasan.so.8: warning: the use of `tempnam' is dangerous, better use `mkstemp'
/usr/bin/ld: /usr/lib/libasan.so.8: warning: the use of `tmpnam_r' is dangerous, better use `mkstemp'
/usr/bin/ld: /usr/lib/libasan.so.8: warning: the use of `tmpnam' is dangerous, better use `mkstemp'
/usr/bin/ld: /<pathTo>/dhtnet/dependencies/install/lib/libpj-x86_64-unknown-linux-gnu.a(guid_uuid.o): in function `pj_generate_unique_string':
guid_uuid.c:(.text+0x3e): undefined reference to `uuid_generate'
/usr/bin/ld: guid_uuid.c:(.text+0x4b): undefined reference to `uuid_unparse'
collect2: error: ld returned 1 exit status
```
`nm` shows:
```
guid_uuid.o:
U __assert_fail
0000000000000000 r .LC0
0000000000000016 r .LC1
0000000000000010 T pj_generate_unique_string
0000000000000000 T pj_GUID_STRING_LENGTH
000000000000001c R PJ_GUID_STRING_LENGTH
0000000000000000 r __PRETTY_FUNCTION__.0
U __stack_chk_fail
U uuid_generate
U uuid_unparse
```
util-linux-libs 2.39.2
/usr/lib/libuuid.so.1.3.0
/usr/include/uuid/uuid.h: `extern void uuid_unparse(const uuid_t uu, char *out);`
EDIT0: As an aside, perhaps authenticate the emails you're sending (they're being sent to spam because they aren't passing checks):
```
spf=neutral (google.com: 208.88.110.44 is neither permitted nor denied by best guess record for domain of gitlab@git.jami.net) smtp.mailfrom=gitlab@git.jami.net;
dmarc=fail (p=QUARANTINE sp=QUARANTINE dis=QUARANTINE) header.from=jami.net
```https://git.jami.net/savoirfairelinux/jami-client-android/-/issues/1472Crash when returning to conversation after closing menu option2023-11-30T21:53:53ZEmma FalkiewitzCrash when returning to conversation after closing menu option![Screen_recording_20231130_165209](/uploads/97c530f82e42c8ee9d46339184c76fa2/Screen_recording_20231130_165209.mp4)![Screen_recording_20231130_165209](/uploads/97c530f82e42c8ee9d46339184c76fa2/Screen_recording_20231130_165209.mp4)https://git.jami.net/savoirfairelinux/jami-client-qt/-/issues/1442Errors that cause session exceptions2023-12-06T15:41:20Zsession 21Errors that cause session exceptionsWin10, version: 202311221353
I have 25 actual sessions, but in the directory "C: \\ Users \\ -- \\ AppData \\ Local \\ jami \\ -- \\ conversions", there are only 18 corresponding files for the sessions, so the remaining seven sessions a...Win10, version: 202311221353
I have 25 actual sessions, but in the directory "C: \\ Users \\ -- \\ AppData \\ Local \\ jami \\ -- \\ conversions", there are only 18 corresponding files for the sessions, so the remaining seven sessions are abnormal.
My confusion lies in why Jami did not create corresponding files for these sessions.
![image.png](/uploads/aaa95871dc6851e4808a535b36995825/image.png)