savoirfairelinux issueshttps://git.jami.net/groups/savoirfairelinux/-/issues2021-04-19T13:21:34Zhttps://git.jami.net/savoirfairelinux/jami-daemon/-/issues/510Upnp Controller - Create instance only when needed2021-04-19T13:21:34ZMohamed ChibaniUpnp Controller - Create instance only when neededUPNP Cotroller instance used by the Account class (and derived classes) must be created only if needed. Currently, the creation is done in enableUpnp(bool) method which is called when the account data are stored or loaded. The required c...UPNP Cotroller instance used by the Account class (and derived classes) must be created only if needed. Currently, the creation is done in enableUpnp(bool) method which is called when the account data are stored or loaded. The required change is to particularly prevent creating UPNP controller instance when storing the account data.Mohamed ChibaniMohamed Chibanihttps://git.jami.net/savoirfairelinux/jami-daemon/-/issues/509Bump pjproject to version 2.112021-07-23T15:16:28ZSébastien BlinBump pjproject to version 2.11https://git.jami.net/savoirfairelinux/ring-daemon/blob/master/contrib/src/pjproject/rules.mak
We're using pjproject 2.10, and we need to migrate our patches and remove the one already upstreamed.
Cf new features (like trickle ICE for m...https://git.jami.net/savoirfairelinux/ring-daemon/blob/master/contrib/src/pjproject/rules.mak
We're using pjproject 2.10, and we need to migrate our patches and remove the one already upstreamed.
Cf new features (like trickle ICE for medias?)Sébastien BlinSébastien Blinhttps://git.jami.net/savoirfairelinux/jami-project/-/issues/1219Please fix distribution process for Ubuntu2021-05-21T15:26:51ZreubenfirminPlease fix distribution process for UbuntuThe version in 20.04's apt is very old and has bugs. The version in snap is 3 months old, but apparently has issues that have been fixed. Unfortunately, installing the version directly from your site does not pick up the settings from th...The version in 20.04's apt is very old and has bugs. The version in snap is 3 months old, but apparently has issues that have been fixed. Unfortunately, installing the version directly from your site does not pick up the settings from the snap version (I am guessing because snap is sandboxed), so it is not easy to go back and forth from the snap to the downloaded version.
Snap or flatpak are a better solution than distributing your own deb packages. Please consider putting resources into maintaining the latest version in those stores rather than building your own, as it'll result in a more cohesive experience for end users.https://git.jami.net/savoirfairelinux/jami-client-qt/-/issues/364Warning of invalid map<K, T> key (map::at)2021-04-14T14:42:01ZMing Rui ZhangWarning of invalid map<K, T> key (map::at)Ming Rui ZhangMing Rui Zhanghttps://git.jami.net/savoirfairelinux/jami-client-qt/-/issues/363incorrect behavior when copying a jami id from contact profile (text displaye...2023-04-07T18:38:38ZGuillaume Hellerincorrect behavior when copying a jami id from contact profile (text displayed is copied instead of value)Scenario:
- right click on contact
- select profile
- if the id is truncated, when copying it, it only copies the text displayed (instead of the value)
![image](/uploads/f835be7d2ac26bc4f30f8301557fa6db/image.png)Scenario:
- right click on contact
- select profile
- if the id is truncated, when copying it, it only copies the text displayed (instead of the value)
![image](/uploads/f835be7d2ac26bc4f30f8301557fa6db/image.png)https://git.jami.net/savoirfairelinux/jami-client-qt/-/issues/362Linux chatview weird font2021-04-13T19:16:17ZSébastien BlinLinux chatview weird fonthttps://git.jami.net/savoirfairelinux/jami-client-android/-/issues/919Can send text and emoticons, but can't send pictures.2021-08-20T20:00:52ZFrederikSchackCan send text and emoticons, but can't send pictures.I'm new to this app and I'm not a developer.
I'm able to send text, but not pictures. We did occasionally have success with video/voice calling, but sometimes we can't.
We're in what is a big commercial private network, that is fairly...I'm new to this app and I'm not a developer.
I'm able to send text, but not pictures. We did occasionally have success with video/voice calling, but sometimes we can't.
We're in what is a big commercial private network, that is fairly unstable. One issue I have is that we share one public IP, which means we can't redirect a port to more than one subscriber inside the network.
It's the same issue with several phones.
We don't have problems with Bittorrent or any other program accessing the Internet, except for losing Internet connection once in a while.https://git.jami.net/savoirfairelinux/jami-plugins/-/issues/19build: create Jenkins job for Mac2021-04-07T22:42:34ZAline Gondim Santosbuild: create Jenkins job for MacBuild and test plugins
- [x] AutoAnswer
- [x] AudioFilter
- [x] WaterMark
- [x] GreenScreenBuild and test plugins
- [x] AutoAnswer
- [x] AudioFilter
- [x] WaterMark
- [x] GreenScreenAline Gondim SantosAline Gondim Santoshttps://git.jami.net/savoirfairelinux/jami-libclient/-/issues/466Exiting jami-qt segfaults (SIGSEGV) when the LRC is built with -DENABLE_LIBWR...2021-06-08T21:13:09ZMaxim CournoyerExiting jami-qt segfaults (SIGSEGV) when the LRC is built with -DENABLE_LIBWRAP=trueEDIT: This original finding no longer holds for version 20210606.1.e2f9490. The only crash now seems to be upon exiting jami-qt. See the 2nd comment.
I found this issue building with the recently released 20210326.1.cfba013 code.
Add...EDIT: This original finding no longer holds for version 20210606.1.e2f9490. The only crash now seems to be upon exiting jami-qt. See the 2nd comment.
I found this issue building with the recently released 20210326.1.cfba013 code.
Adding `-DENABLE_LIBWRAP=true` as a CMake option would cause the following segfault when attempting to do a video call:
```
[1617377403.268|27762|manager.cpp :2989 ] Did not find conference 7014912808852927
[1617377403.300|28030|accel.cpp :180 ] Device type vaapi successfully created.
[1617377403.300|28030|accel.cpp :213 ] -- Init passed for vaapi with default device.
[1617377403.303|28030|media_decoder.cpp :489 ] Using hardware decoding for h264 with vaapi
[1617377403.303|28030|media_decoder.cpp :496 ] Decoding video using H.264 / AVC / MPEG-4 AVC / MPEG-4 part 10 (h264)
[1617377403.303|28030|sinkclient.cpp :191 ] ShmHolder[Jami Daemon_shm_27762_1]: new sizes: f=0, a=103
[1617377403.303|28030|sinkclient.cpp :158 ] ShmHolder: new holder 'Jami Daemon_shm_27762_1'
[1617377403.303|28030|sinkclient.cpp :429 ] Start sink <7014912808852927 / Jami Daemon_shm_27762_1>, size=1280x720, mixer=0
[1617377403.303|28030|accel.cpp :151 ] Found compatible hardware format for h264 decoder with vaapi
[1617377403.304|28030|accel.cpp :151 ] Found compatible hardware format for h264 decoder with vaapi
[1617377403.304|28030|accel.cpp :151 ] Found compatible hardware format for h264 decoder with vaapi
[1617377403.304|28030|accel.cpp :151 ] Found compatible hardware format for h264 decoder with vaapi
[1617377403.304|28030|accel.cpp :151 ] Found compatible hardware format for h264 decoder with vaapi
[1617377403.304|28030|accel.cpp :151 ] Found compatible hardware format for h264 decoder with vaapi
[1617377403.304|28030|accel.cpp :151 ] Found compatible hardware format for h264 decoder with vaapi
[1617377403.305|28030|accel.cpp :151 ] Found compatible hardware format for h264 decoder with vaapi
[1617377403.305|28030|media_decoder.cpp :568 ] Decoding error falling back to software
[New Thread 0x7fff21283700 (LWP 28061)]
[Thread 0x7fff23c87700 (LWP 28057) exited]
[Thread 0x7fff22c85700 (LWP 28059) exited]
[Thread 0x7fff22484700 (LWP 28060) exited]
[Thread 0x7fff23486700 (LWP 28058) exited]
[1617377403.388|28030|media_decoder.cpp :496 ] Decoding video using H.264 / AVC / MPEG-4 AVC / MPEG-4 part 10 (h264)
[1617377403.388|28030|media_decoder.cpp :506 ] Not using hardware decoding for h264
[New Thread 0x7fff22484700 (LWP 28062)]
[New Thread 0x7fff22c85700 (LWP 28063)]
[1617377403.391|27811|sipcall.cpp :419 ] Sending video keyframe request via SIP INFO
[1617377403.540|28030|sinkclient.cpp :191 ] ShmHolder[Jami Daemon_shm_27762_1]: new sizes: f=3686400, a=7372903
--Type <RET> for more, q to quit, c to continue without paging--c
Thread 1 "..jami-qt-real-" received signal SIGSEGV, Segmentation fault.
0x00007fffeeab4710 in __memmove_ssse3 () from /gnu/store/fa6wj5bxkj5ll1d7292a70knmyl7a0cr-glibc-2.31/lib/libc.so.6
(gdb) bt
#0 0x00007fffeeab4710 in __memmove_ssse3 () from /gnu/store/fa6wj5bxkj5ll1d7292a70knmyl7a0cr-glibc-2.31/lib/libc.so.6
#1 0x0000000000452d3d in FrameWrapper::slotFrameUpdated(QString const&) ()
#2 0x00007fffef105914 in void doActivate<false>(QObject*, int, void**) () from /gnu/store/sbf77k7xzwhkx4ygqjzgkviz9vy4qhf6-qtbase-5.15.2/lib/libQt5Core.so.5
#3 0x00007ffff7d93c55 in lrc::api::AVModel::frameUpdated(QString const&) () from /gnu/store/3scnwm1jlhpxii7261p6zifbj1r9a1ah-libringclient-20210326.1.cfba013/lib/libringclient.so.1.0.0
#4 0x00007fffef0fc763 in QObject::event(QEvent*) () from /gnu/store/sbf77k7xzwhkx4ygqjzgkviz9vy4qhf6-qtbase-5.15.2/lib/libQt5Core.so.5
#5 0x00007ffff7155c3c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /gnu/store/sbf77k7xzwhkx4ygqjzgkviz9vy4qhf6-qtbase-5.15.2/lib/libQt5Widgets.so.5
#6 0x00007ffff715c57f in QApplication::notify(QObject*, QEvent*) () from /gnu/store/sbf77k7xzwhkx4ygqjzgkviz9vy4qhf6-qtbase-5.15.2/lib/libQt5Widgets.so.5
#7 0x00007fffef0ca373 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /gnu/store/sbf77k7xzwhkx4ygqjzgkviz9vy4qhf6-qtbase-5.15.2/lib/libQt5Core.so.5
#8 0x00007fffef0cd521 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /gnu/store/sbf77k7xzwhkx4ygqjzgkviz9vy4qhf6-qtbase-5.15.2/lib/libQt5Core.so.5
#9 0x00007fffef129d53 in postEventSourceDispatch(_GSource*, int (*)(void*), void*) () from /gnu/store/sbf77k7xzwhkx4ygqjzgkviz9vy4qhf6-qtbase-5.15.2/lib/libQt5Core.so.5
#10 0x00007ffff769908a in g_main_context_dispatch () from /gnu/store/1m34rwlhv2pyjbp69n63grlncnkjyi31-glib-2.62.6/lib/libglib-2.0.so.0
#11 0x00007ffff7699288 in g_main_context_iterate.isra () from /gnu/store/1m34rwlhv2pyjbp69n63grlncnkjyi31-glib-2.62.6/lib/libglib-2.0.so.0
#12 0x00007ffff769930c in g_main_context_iteration () from /gnu/store/1m34rwlhv2pyjbp69n63grlncnkjyi31-glib-2.62.6/lib/libglib-2.0.so.0
#13 0x00007fffef12944c in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /gnu/store/sbf77k7xzwhkx4ygqjzgkviz9vy4qhf6-qtbase-5.15.2/lib/libQt5Core.so.5
#14 0x00007fffef0c8d2a in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /gnu/store/sbf77k7xzwhkx4ygqjzgkviz9vy4qhf6-qtbase-5.15.2/lib/libQt5Core.so.5
#15 0x00007fffef0d1e53 in QCoreApplication::exec() () from /gnu/store/sbf77k7xzwhkx4ygqjzgkviz9vy4qhf6-qtbase-5.15.2/lib/libQt5Core.so.5
#16 0x00000000004280a6 in main ()
```
Simply setting this option to false resolves the issue (no longer segfaults and the video call proceeds normally).
Interestingly, audio calls are not affected and the jami-qt client works normally otherwise.Sébastien BlinSébastien Blinhttps://git.jami.net/savoirfairelinux/jami-client-macos/-/issues/280plugins: create base UI2021-05-28T14:40:33ZAline Gondim Santosplugins: create base UI- Add plugin to jami settings: enable/disable, (un)install and (un)load;
- Add a plugin to calls and conversations;
- Add plugins preferences to settings view;- Add plugin to jami settings: enable/disable, (un)install and (un)load;
- Add a plugin to calls and conversations;
- Add plugins preferences to settings view;Kateryna KostiukAline Gondim SantosKateryna Kostiukhttps://git.jami.net/savoirfairelinux/jami-daemon/-/issues/508plugins: add MACOSX ABI to plugin installation options2021-04-08T18:53:40ZAline Gondim Santosplugins: add MACOSX ABI to plugin installation optionsInstallation function needs to know host details to properly extract plugins libraries from the jpl archive.Installation function needs to know host details to properly extract plugins libraries from the jpl archive.Aline Gondim SantosAline Gondim Santoshttps://git.jami.net/savoirfairelinux/jami-client-android/-/issues/918Maybe all settings should be put in one place?2022-08-04T19:29:01ZChris OcelotMaybe all settings should be put in one place?On android clients, settings are located at top right 3 dots as well as the account tab, it seems a bit odd to me.
At first I found the setting located at account tab, then I thought, OK, setting is here, if there is anything I want to...On android clients, settings are located at top right 3 dots as well as the account tab, it seems a bit odd to me.
At first I found the setting located at account tab, then I thought, OK, setting is here, if there is anything I want to change, I need to check here. Then somebody told me there was also setting on top right corner with the 3 dots. It seems very counter-intuitive to put these setting in different places. My suggestion would be add another setting menu under "advanced" section, call it "conversation", and put what was in the top right corner 3 dots in there.https://git.jami.net/savoirfairelinux/jami-client-qt/-/issues/361Add participant: List must be sorted by last interaction2022-12-19T21:22:48ZSébastien BlinAdd participant: List must be sorted by last interactionhttps://git.jami.net/savoirfairelinux/jami-project/-/issues/1218My own dhtproxy node does not work as intended2021-05-07T15:16:04ZChris OcelotMy own dhtproxy node does not work as intendedHello respected devs,
Thanks for this amazing project, I really love the concept of distributed communication service!
I ran into a problem trying to set up my own dhtproxy server, hopefully I can get some hints as to why this happen...Hello respected devs,
Thanks for this amazing project, I really love the concept of distributed communication service!
I ran into a problem trying to set up my own dhtproxy server, hopefully I can get some hints as to why this happens.
I have compiled the latest opendht (on Debian buster) according to the instructions on github wiki, and it was successful. Then I ran the dhtproxy node with the following command:
`dhtnode -b bootstrap.jami.net:4222 --proxyserver 8000`
It connects to the public dht network successfully. My android device is able to use this proxy to connect to the dht network.
(For testing purpose, I disabled bootscrap and proxylist)
Now the problem is that, the notification mechanism of dhtproxy is not working. From my understanding, when someone sends a message to me or calls me, the dhtproxy should notify me something is up, and my device would go fetch it from the dht network. This works for the official dhtproxy.jami.net, but not for my dhtproxy. When someone calls, it would not connect, unless I use to disconnect/connect toggle at the top right corner, forcing my device to fetch data from the dht network, only then will I be able to receive the call. What am I missing?
Thanks in advance for any help!Sébastien BlinSébastien Blinhttps://git.jami.net/savoirfairelinux/jami-client-qt/-/issues/360Change mute/unumte display2021-11-26T21:55:53ZPierre LespagnolChange mute/unumte displayIf a participant is muted and he wants to unmute himeself, there are 2 separate cases:
- The participant is moderator -> he can unmute
- The participant is not moderator -> he can't unmute and a pop-up will be displayed on the unmute but...If a participant is muted and he wants to unmute himeself, there are 2 separate cases:
- The participant is moderator -> he can unmute
- The participant is not moderator -> he can't unmute and a pop-up will be displayed on the unmute button
(like "You have been mute by a moderator")
The mute buttons (in participant overlay and call bar) shoud display the same statehttps://git.jami.net/savoirfairelinux/jami-client-qt/-/issues/359Add missing context menus for text entry fields2021-04-07T19:51:02ZAndreas TraczykAdd missing context menus for text entry fieldsA right click should show a context menu with copy, past, etc.A right click should show a context menu with copy, past, etc.Ming Rui ZhangMing Rui Zhanghttps://git.jami.net/savoirfairelinux/jami-client-qt/-/issues/358plugins: create handlers activation order UI2023-09-15T19:40:39ZAline Gondim Santosplugins: create handlers activation order UIBacklogAline Gondim SantosAline Gondim Santoshttps://git.jami.net/savoirfairelinux/jami-libclient/-/issues/465plugins: set handlers activation order api2023-05-05T19:37:23ZAline Gondim Santosplugins: set handlers activation order apiThere may be API changes allowing UI to change handlers activation order.There may be API changes allowing UI to change handlers activation order.BacklogAline Gondim SantosAline Gondim Santoshttps://git.jami.net/savoirfairelinux/jami-daemon/-/issues/505Update missing at the end of sub- conference2021-04-13T13:37:58ZPierre LespagnolUpdate missing at the end of sub- conference# Scenario
- Bob join Bob-RDV (2 accounts same device)
- Alice join Bob-RDV
- Bob create conference with Bob-RDV and Roger
- Bob ends conference
# Current result
- Alice doesn't receive the update and see remaining layout from Bob and R...# Scenario
- Bob join Bob-RDV (2 accounts same device)
- Alice join Bob-RDV
- Bob create conference with Bob-RDV and Roger
- Bob ends conference
# Current result
- Alice doesn't receive the update and see remaining layout from Bob and RogerPierre LespagnolPierre Lespagnolhttps://git.jami.net/savoirfairelinux/jami-client-qt/-/issues/357Jami current calls set incorrectly2021-07-16T19:57:32ZMing Rui ZhangJami current calls set incorrectlyWhen having a jami call, then switch to another account and then initial another call,
the original call should be on hold, but when hanging up the second call and
switch back, the first call will not be unheld any more.When having a jami call, then switch to another account and then initial another call,
the original call should be on hold, but when hanging up the second call and
switch back, the first call will not be unheld any more.Ming Rui ZhangMing Rui Zhang