savoirfairelinux issueshttps://git.jami.net/groups/savoirfairelinux/-/issues2018-11-27T20:17:22Zhttps://git.jami.net/savoirfairelinux/jami-client-gnome/-/issues/935Ubuntu 16.04 dbus blocked2018-11-27T20:17:22ZSébastien BlinUbuntu 16.04 dbus blockedWhen running ring on Ubuntu 16.04, the client seems to block on getting a dbus result from the daemon.When running ring on Ubuntu 16.04, the client seems to block on getting a dbus result from the daemon.Sébastien BlinSébastien Blin2018-12-01https://git.jami.net/savoirfairelinux/jami-project/-/issues/529Release for ubuntu 18.102018-11-30T19:55:24ZSébastien BlinRelease for ubuntu 18.10The release for ubuntu 18.10 is not generated for now cause LRC is not finding dbus files from daemon.The release for ubuntu 18.10 is not generated for now cause LRC is not finding dbus files from daemon.Sébastien BlinSébastien Blin2018-12-01https://git.jami.net/savoirfairelinux/jami-client-gnome/-/issues/931Add support for Fedora 292018-11-30T19:53:23ZannaAdd support for Fedora 29Hej there!
Yesterday the release of Fedora 29 has been announced.
https://fedoramagazine.org/announcing-fedora-29/
Please provide new Ring packages to support it!Hej there!
Yesterday the release of Fedora 29 has been announced.
https://fedoramagazine.org/announcing-fedora-29/
Please provide new Ring packages to support it!Sébastien BlinSébastien Blin2018-12-01https://git.jami.net/savoirfairelinux/jami-project/-/issues/1638Feature: Send notification that you've been blocked (opt-in per contact and a...2024-03-25T13:29:33ZElysFeature: Send notification that you've been blocked (opt-in per contact and account)all supported OS and all Jami clients
I think it would be useful that if you (person A) block another peer (person B) you should have a dialog with a checkbox "Inform the peer about the block" which will send a message to the blocked pe...all supported OS and all Jami clients
I think it would be useful that if you (person A) block another peer (person B) you should have a dialog with a checkbox "Inform the peer about the block" which will send a message to the blocked person (B) that the person is now blocked.
So the blocked person gets a standard message like "You've been blocked. Note that within Jami communication is not possible anymore and the other peer won't receive any new messages, video / voice messages and/or attachments/files and you won't be able to call the peer unless you get unblocked."
You should have also the possibility to to generally disable or enable such a notification in the settings per own Jami account. So you won't get a dialog with a checkbox and no other peer will ever receive any notification that he has been blocked. He might just knows it because nothing works anymore.
And it should be possible using Jami account 1 for example contact A gets a notification but contact B and C won't get any notification (opt-in per contact unless you generally disable this notifications in the settings (per Jami accounts)).
* Maybe something similiar should be possible when it comes to kick a peer (NO block) https://git.jami.net/savoirfairelinux/jami-project/-/issues/1493
* Also if you remove a peer from the contact list
* I guess using SIP-Accounts this would not make sense because sending SMS might not be free of charge?https://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/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-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-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-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-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/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-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/1581Migrate to Qt6.6.2 and QWindowKit will work fine2024-03-04T20:40:28ZSineStrikerMigrate to Qt6.6.2 and QWindowKit will work fineCheck https://github.com/stdware/qwindowkit/issues/23Check https://github.com/stdware/qwindowkit/issues/23Andreas TraczykAndreas Traczykhttps://git.jami.net/savoirfairelinux/jami-daemon/-/issues/961newOutgoingCall => no call for host (make newOutgoingCall Asyng and change ca...2024-02-28T20:04:42ZSébastien BlinnewOutgoingCall => no call for host (make newOutgoingCall Asyng and change call creation)https://git.jami.net/savoirfairelinux/jami-client-android/-/issues/1622Delay when enabling Screenshare Android142024-02-28T21:41:47ZPierre NicolasDelay when enabling Screenshare Android14Bug report form
---------------
## Describe your environment
Please specify the following:
- Jami version: 407
- Device model: Google Pixel Tablet
- Android version: 14
## Steps to reproduce
- Can you reproduce the bug: at w...Bug report form
---------------
## Describe your environment
Please specify the following:
- Jami version: 407
- Device model: Google Pixel Tablet
- Android version: 14
## Steps to reproduce
- Can you reproduce the bug: at will
- Steps:
1. Make a phone call with a contact
2. Enable screenshare
- Actual result: It takes forever to see the screenshare on contact device (15s by spamming the screen and more than 2min30 if just waiting)
- Expected result: Instant screenshare