jami-project issueshttps://git.jami.net/savoirfairelinux/jami-project/-/issues2024-01-29T21:44:29Zhttps://git.jami.net/savoirfairelinux/jami-project/-/issues/1449Blocking contact does not work, removed/blocked contact can be called? [Andro...2024-01-29T21:44:29ZElysBlocking contact does not work, removed/blocked contact can be called? [Android-> Windows 10]newest beta version of Jami (Windows 10 and Android); 1:1 swarm, using different Jami accounts
Windows 10= username1; Android=username2; group chat disabled;
EDIT: Just the Windows 10 user enabled "Allow incoming calls from unknown cont...newest beta version of Jami (Windows 10 and Android); 1:1 swarm, using different Jami accounts
Windows 10= username1; Android=username2; group chat disabled;
EDIT: Just the Windows 10 user enabled "Allow incoming calls from unknown contacts"
steps to reproduce
1. both contacts (Windows 10 user and Android user) are each showing up in their contact list
1. Windows 10 user removes the Android contact in contact list (However the Android user does not)
1. Android user writes message (Android -> Windows 10)
1. Windows 10 user does not receive the message
1. Now the android makes a phone call
1. Windows 10 receives the phone call; He can hear the ringtone but won't get the options to decline or answer in audio/video
1. Now the Windows 10 user exits and restarts jami (The Android user keeps Jami running)
1. Now the Android user tries to make a phone call (android -> windows 10)
1. Windows 10 user does not get any notification
Android user exit and start Jami again
Android user still sees green dot of Windows 10 user
Windows 10 user does not get any notification (same issue again)
Next issue:
1. Now the Windows 10 user unblocks the Android
1. The android user sends text message
1. The Windows 10 user gets an invitation and accepts
1. The Windows 10 user still sees the notification "invitations 1"
1. Jami Windows 10 still shows invitations but the user does not receive any message
However you can make a video call Android -> Windows 10 but Jami (Windows 10) does not show up chat history
Next issue: (after the previous issue)
1. Restart Jami (just the user of Windows 10)
1. You can view **the same (Android) user twice (Both: Swarm: Is true)**; It is still not possible that the Windows 10 user receives any text message (Android -> Windows 10) and it is also not possible to receive text messages Windows 10 -> Android
However video call Windows 10 <-> Android are possible
If you restart Jami (windows 10) same issue again
(And you still won't receive any messages anymore although windows 10 contact is unblocked)
---------
Now remove the contacts (Windows 10 AND Android; exit all Jami apps)
Windows 10 user: As soon as you remove the (unblocked) Android - you just want to delete the contact - the Android user will be listed in "blocked contacts" (although you did not block the user (again)).
You won't be able to delete the Android user anymore - the user will always be moved to "blocked contacts".
----
Now Android -> Windows 10 (all contacts (windows 10 and Android) were removed)
Android: Add the Windows 10 user by searching the user name and add the Windows 10 user
Sending text messages Android <-> Windows 10 now works
Now:
1. The Android user blocks the Windows 10 user (If the Android user tabs the Windows 10 user (from the conversation list) block contact does not work)
1. So the Android user needs to go to contact details and block the Windows 10 contact and confirms
1. However the Windows 10 user DOES NOT remove the android user from his contact list
1. Android: even if you stay (conversation - tap the contact) you won't receive any new messages (from the Windows 10 user)
1. Now return to conversations: the blocked user is gone
However: As soon as the Windows 10 user makes a video call your blocked contact will be shown again (conversations) and you get a notification how you want to answer the call (although both contacts disabled "Allow calls from unknown contacts")
After you finished the call you are asked if you accept the invetation of the blocked Windows 10 user.
If the Android user accepts:
The Android user can send messages but the windows 10 user will not receive them
However - the android user will still receive messages (windows 10 -> Android)
If the android user taps "blocked contact" Windows 10 user is still shown and you can't change anything.Sébastien BlinSébastien Blinhttps://git.jami.net/savoirfairelinux/jami-project/-/issues/665[JAMS] Revoke device on manager should inform clients2023-09-07T19:23:24ZSébastien Blin[JAMS] Revoke device on manager should inform clientsNew release 1Adrien BéraudAdrien Béraudhttps://git.jami.net/savoirfairelinux/jami-project/-/issues/1566Remove linked device fails2023-04-28T19:08:52ZJames BealeRemove linked device fails@sblin
Hi Sébastien
Világfa Version: 202304121407
jami-all.deb install on Kubuntu 22.04LTS
I am unable to remove two linked devices within my Jami.
I ran `/usr/bin/jami -d > output.log`.
The log file itself didn't have much inf...@sblin
Hi Sébastien
Világfa Version: 202304121407
jami-all.deb install on Kubuntu 22.04LTS
I am unable to remove two linked devices within my Jami.
I ran `/usr/bin/jami -d > output.log`.
The log file itself didn't have much information:
> 18:27:11.261 os_core_unix.c !pjlib 2.12.1 for POSIX initialized
> Daemon is running
However, the terminal session produced the information in the attached file, "jami term output 24 april 2023 1834h.txt". The output states "this is a bug, please report".
So, I'm reporting it as a bug. Being unable to remove the linked devices would surely qualify anyway!
James
[jami_term_output_24_april_2023_1834h.txt](/uploads/571698cb71c9610de3547b7e5a51e9e0/jami_term_output_24_april_2023_1834h.txt)Sébastien BlinSébastien Blinhttps://git.jami.net/savoirfairelinux/jami-project/-/issues/1388Outgoing call fails if you immediately start a video call after you see the g...2023-04-14T12:59:34ZElysOutgoing call fails if you immediately start a video call after you see the green dot / or after screen timeout (Android)Related to https://git.jami.net/savoirfairelinux/jami-client-android/-/issues/846
>If you start Jami (Windows 10; you wait until the green dot of Person B is visible) and you immediately start a video call you get connected but it takes...Related to https://git.jami.net/savoirfairelinux/jami-client-android/-/issues/846
>If you start Jami (Windows 10; you wait until the green dot of Person B is visible) and you immediately start a video call you get connected but it takes some time and then the outgoing call fails.
>(turn enabled both sides)
So you start a video call as soon as both apps are opened and you can see both persons are shown online.
(This test: same user account -> same user account)
> Windows 10: After you see the green dot of the account of the person you want to call and you NOT immediately call the other person but wait for 30 seconds there's hardly any connection problem.
both situations:
Call:
Windows 10 -> Android
Android -> Windows 10https://git.jami.net/savoirfairelinux/jami-project/-/issues/1558Multi-device, avatar changes in a weird way2023-04-12T14:14:43ZSébastien BlinMulti-device, avatar changes in a weird way# Scenario
Got a multi-device account. Launch them several times
# Expected result
The profile should not change
# Current result
Avatar changes randomly# Scenario
Got a multi-device account. Launch them several times
# Expected result
The profile should not change
# Current result
Avatar changes randomlySébastien BlinSébastien Blinhttps://git.jami.net/savoirfairelinux/jami-project/-/issues/1093notification message on non-Google phones2023-04-07T20:07:41ZRiknotification message on non-Google phonesHi,
i use Jami both on a Google-Android phone and on a non-Google-Android phone (https://e.foundation). On the latter, there is a persistent notification message that Jami is syncing. I think this may be necessary (it sometimes is for o...Hi,
i use Jami both on a Google-Android phone and on a non-Google-Android phone (https://e.foundation). On the latter, there is a persistent notification message that Jami is syncing. I think this may be necessary (it sometimes is for other messaging services as well), but my advice would be to change the notification message, and say something like "Jami is connected" or something. I'd also advice to delete the time ("20h" in the image below). Now it looks like something is wrong and Jami is not syncing well, while it is syncing just fine.
![image](/uploads/58ba78395a8040a4a84f61b58dc38896/image.png)BacklogAdrien BéraudAdrien Béraudhttps://git.jami.net/savoirfairelinux/jami-project/-/issues/1512First call: "Searching" remains if the Android contact is called after JUST t...2023-03-31T15:54:47ZElysFirst call: "Searching" remains if the Android contact is called after JUST the Android contact disables and enables (again) his own account (only useraccount1 -> useraccount2?)using Jami (Windows 10 -> Android; useraccount1 -> useraccount2), different network
EDIT: I think I didn't reproduce if I make a call **sameuseraccount -> sameuseraccount** if the Android user enables his account very quickly again - ho...using Jami (Windows 10 -> Android; useraccount1 -> useraccount2), different network
EDIT: I think I didn't reproduce if I make a call **sameuseraccount -> sameuseraccount** if the Android user enables his account very quickly again - however if the **Android user waits** one **minute or even longer** and THEN **enables** his account again I get the **"Connecting"** issue https://git.jami.net/savoirfairelinux/jami-project/-/issues/1513 (at least after I repeat these steps the second time: Open Jami (Windows 10 and Android); Wait a few seconds; Now just the Android user disables his own account and waits two minutes or even longer; Now the Android user enables his own account; Same steps: The Android user disables his own account and waits two minutes; Now the Android user enables his own account: This time a call sameuseraccount(windows 10) -> sameuseraccount(android) will stuck in "Connecting")
You have to make a call **useraccount1 -> useraccount2** if the Android user **immediately** enables his account
Mixed:
- If I first make a call sameuseraccount(windows 10) -> sameuseraccount(android) everything works
- Now I disable (Windows 10) sameuseraccount(windows 10) and enable the other account (useraccount1 (windows 10)) so I can make a call useraccount1 (Windows 10) -> useraccount2 (Android)
- Still same issue (although sameuseraccount(windows 10) -> sameuseraccount(android) does not have any issues?)
Maybe also related: https://git.jami.net/savoirfairelinux/jami-project/-/issues/1513
ALWAYS DISABLE "run in background"
Steps to reproduce:
1. Windows 10: (=useraccount1) You've already opened Jami and keep Jami running
1. Android (=useraccount2) Open Jami
1. Now the Windows 10 user will view the green dot of the Android user in the contact list
1. Now just the Android user disables his own account
1. Now just the Android user enables his own account
1. BEFORE the Android user views the green dot of (all) his contacts in the contact list the Windows 10 user tries to make a call (Windows 10 -> Android)
1. Windows 10: The call will be stuck at "Searching" (it won't fail? - it won't work?; even after a minute; even if the Android user now views the green dot of all contacts)
Sometimes after some time you'll get missed outgoing call (in that case Windows 10).
Same issue if you immediately make a **first call** (Windows 10 -> Android) if the Android user views the green dot of the Windows 10 user in the contact list
However - the **next calls will work**?
EDIT: I think this is not (only) a timing issue but an issue because **(just) the Android user disabled** (and now enables) his own account.
**No issues** if you make a call **Android -> Windows 10**. (Remember you never disabled the Windows 10 Jami account)
EDIT 2: If the Windows 10 user also disables his own account and enables his account again I think this issue does NOT happen? (Not sure - I also had this issue if the Windows 10 user disables and enables his account?)https://git.jami.net/savoirfairelinux/jami-project/-/issues/1549Jami - Linux : Crashes when adding new account2023-03-20T13:48:40ZJames BealeJami - Linux : Crashes when adding new accountI'd rate this a severe bug, if it is one. :smile:
When clicking "Add account+", Jami crashes. I've replicated this on two machines.
Ubuntu Linux 22.04LTS - & - Kubuntu Linux 20.04LTS
Jami Világfa
Version: 202303131454
Here's the lo...I'd rate this a severe bug, if it is one. :smile:
When clicking "Add account+", Jami crashes. I've replicated this on two machines.
Ubuntu Linux 22.04LTS - & - Kubuntu Linux 20.04LTS
Jami Világfa
Version: 202303131454
Here's the log, but the application crashed, so it may not be much use:
[1678987417.668|29355|manager.cpp :940 ] ############## START MONITORING ##############
[1678987417.668|29355|manager.cpp :941 ] Using PJSIP version 2.12.1 for x86_64-pc-linux-gnu
[1678987417.668|29355|manager.cpp :942 ] Using GnuTLS version 3.6.13
[1678987417.668|29355|manager.cpp :943 ] Using OpenDHT version 2.4.11
[1678987417.669|29355|manager.cpp :949 ] Opened files: 181
[1678987417.669|29355|connectionmanager.cpp :1196] ConnectionManager for account [redacted2] (jami:wts), current status:
[1678987417.669|29355|peer_connection.cpp :426 ] - Ice connection: [2] 92.222.89.217:22333 [relay] <-> 217.155.15.207:52332 [prflx]
[1678987417.669|29355|peer_connection.cpp :426 ] - Ice connection: [2] 82.69.100.117:51968 [prflx] <-> 92.222.89.217:26142 [relay]
[1678987417.669|29355|peer_connection.cpp :426 ] - Ice connection: [2] 0.0.0.218:40311 [host] <-> 0.0.0.207:41086 [prflx]
[1678987417.669|29355|peer_connection.cpp :426 ] - Ice connection: [2] 82.69.100.117:14356 [prflx] <-> 51.254.39.157:19475 [relay]
[1678987417.669|29355|peer_connection.cpp :426 ] - Ice connection: [2] 82.69.100.117:13660 [prflx] <-> 51.254.39.157:22538 [relay]
[1678987417.669|29355|peer_connection.cpp :426 ] - Ice connection: [2] 82.69.100.117:25930 [prflx] <-> 51.254.39.157:18930 [relay]
[1678987417.669|29355|peer_connection.cpp :426 ] - Ice connection: [2] 0.0.0.218:55877 [host] <-> 0.0.0.7:40634 [prflx]
[1678987417.669|29355|connectionmanager.cpp :1203] ConnectionManager for account [redacted2] (jami:wts), end status.
[1678987417.669|29355|connectionmanager.cpp :1196] ConnectionManager for account [redacted] (jami:tt), current status:
[1678987417.669|29355|peer_connection.cpp :426 ] - Ice connection: [2] 0.0.0.142:54949 [prflx] <-> 0.0.0.207:49750 [prflx]
[1678987417.669|29355|peer_connection.cpp :426 ] - Ice connection: [2] 0.0.0.218:41065 [host] <-> 0.0.0.7:58480 [prflx]
[1678987417.669|29355|connectionmanager.cpp :1203] ConnectionManager for account [redacted] (jami:tt), end status.
[1678987417.669|29355|manager.cpp :958 ] ############## END MONITORING ##############
[1678987423.354|29503|jamiaccount.cpp :1888] [Account [redacted]] Dht status: IPv4 connected; IPv6 disconnectedSébastien BlinSébastien Blinhttps://git.jami.net/savoirfairelinux/jami-project/-/issues/1224re-register to late2023-03-13T13:31:51ZLukas Wallischre-register to lateAs the logs suggests the re-register timer is to long... as far as i know the reregister should come before the old register expires, not 10s after...
```
[1618330072.037|43625|sipaccount.cpp :958 ] Start keep alive timer for accoun...As the logs suggests the re-register timer is to long... as far as i know the reregister should come before the old register expires, not 10s after...
```
[1618330072.037|43625|sipaccount.cpp :958 ] Start keep alive timer for account 7e9411aaf521bc4b
[1618330072.037|43625|sipaccount.cpp :977 ] Registration Expire: 119
[1618330072.037|43625|sipvoiplink.cpp :776 ] Register new keep alive timer 2099486383 with delay 129
```
OS : Ubuntu 20.04
Version: snap ( downloaded today)
`jami -v` gives:
```
Testing for explicit PulseAudio choice...
Testing for ALSA permissions...
...and using ALSA.
Jami Daemon 9.8.0-a6d5ad32d7-dirty, by Savoir-faire Linux 2004-2019
https://jami.net/
[Video support enabled]
[Plugins support enabled]
```
i can only find the settings for the expire-timer, but the not the reregister-timer. am I missing something?
I'm using this client behind a Hardware-PBX, because of the late reregister my calls keep getting abortedSébastien BlinSébastien Blinhttps://git.jami.net/savoirfairelinux/jami-project/-/issues/1391Jami shows the same user account twice (after deletion of old account?), wron...2022-08-19T14:16:59ZElysJami shows the same user account twice (after deletion of old account?), wrong date; No more NEW (!) call history:(Maybe similar: https://git.jami.net/savoirfairelinux/jami-daemon/-/issues/714 )
Steps to reproduce:
Mate 20 Pro: You have to delete your own account that is displayed in the contact list (so you have Swarm: Is true)
Same process using...(Maybe similar: https://git.jami.net/savoirfairelinux/jami-daemon/-/issues/714 )
Steps to reproduce:
Mate 20 Pro: You have to delete your own account that is displayed in the contact list (so you have Swarm: Is true)
Same process using Windows 10. As soon as you click on your own user account it suddenly moves up.
using Bluestacks 5:
After I delete the old user account and I made a call you suddenly have your user account twice.https://git.jami.net/savoirfairelinux/jami-project/-/issues/1439Add contact: Contact is shown twice if you remove the contact2022-06-20T18:43:34ZElysAdd contact: Contact is shown twice if you remove the contactusing newest beta version (both) Android and Windows 10 (different user accounts "account 1" -> "account 2")
(group chat (experimental) disabled)
Steps to reproduce
1. (Windows 10 user ="account 1") Search for a new user name /contact
...using newest beta version (both) Android and Windows 10 (different user accounts "account 1" -> "account 2")
(group chat (experimental) disabled)
Steps to reproduce
1. (Windows 10 user ="account 1") Search for a new user name /contact
2. (Windows 10 user ="account 1") Select the username "account 2" and click "Add to conversation"
3. [Android user ="account 2"] Accept contact and go to "Conversations"
4. (Windows 10 user ="account 1") Remove user "account 2"
5. "account 2" (Swarm: Is true) is gone **but "account 2" (Swarm: Is false) appears**
Now you have 2 possibilities (Windows 10 user ="account 1"):
a) If you right click on the contact ("account 2") you can view all options and remove the contact
- The contact is now completely gone
b) The Windows 10 user ="account 1" did **NOT** select "Add to conversation" but immediately makes a video call (step 2) and already ended the video call. - So the windows 10 user only views the chat view anymore.
A little bit different:
> 4. (Windows 10 user ="account 1") Remove user "account 2"
> 5. "account 2" (Swarm: Is true) is gone **but "account 2" (Swarm: Is false) appears**
However if you (windows 10 user) right click on the contact you can only view "Stop call" (although you don't have any call anymore) and contact details
(Windows 10:) You have to exit Jami and open Jami again: Now you can still view the "account 2" (Swarm: Is false) but you right click on the contact ("account 2") you can view all options and remove the contact
- The contact is now completely gone
However - [Android user ="account 2"] still has contact 1 in his contact list (not sure if this is a bug?)
If the android user ("account 2") does not remove "account 1" from his device and the windows 10 user (="account 1") start from step 1 mentioned above, Jami (Windows 10) will show the contact "account 2" Swarm: is falsehttps://git.jami.net/savoirfairelinux/jami-project/-/issues/1415jami-qt cannot be upgraded from debian 11 nightly2022-04-02T08:50:53ZRobert Alessijami-qt cannot be upgraded from debian 11 nightlyTrying to upgrade to the latest nightly built package of Jami-qt failed this morning with the following error message:
```
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are...Trying to upgrade to the latest nightly built package of Jami-qt failed this morning with the following error message:
```
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:
The following packages have unmet dependencies:
jami : Depends: jami-libclient (= 20220320.0836.fdd4c45~dfsg1-1) but it is not installable
E: Unable to correct problems, you have held broken packages.
```
For information, even if this `jami-libclient 20220320.0836.fdd4c45~dfsg1-1` can be installed separately, the upgrade of `jami` still fails with the same error message.
As a workaround, I tried to install `jami-gnome` and it worked.Amin BandaliAmin Bandalihttps://git.jami.net/savoirfairelinux/jami-project/-/issues/1384Jami uses the GPU when idle2022-04-01T21:46:21ZA. SpennerJami uses the GPU when idleJami is using about 7-8 percentage in an idle/passive state when GUI is open.
"Enable hardware acceleration" is disabled inside Audio/Video settings.
The result above can also be seen as an overlay if running Jami together with "MSI Af...Jami is using about 7-8 percentage in an idle/passive state when GUI is open.
"Enable hardware acceleration" is disabled inside Audio/Video settings.
The result above can also be seen as an overlay if running Jami together with "MSI Afterburner" / "RivaTuner Statistics Server".
OS: Windows 10 Pro (20H2 19042.1466)
Version: 202112221635 TaranisAndreas TraczykAndreas Traczykhttps://git.jami.net/savoirfairelinux/jami-project/-/issues/1043Unable to stop Sharing Location2021-11-19T16:54:18ZAndy HiscockUnable to stop Sharing LocationI can share my location from one android client to another android client but there doesnt seemed to be wa way of turning off. ven when the "1 hour" has passed the location is still displayed on the screen of the destination client. ...I can share my location from one android client to another android client but there doesnt seemed to be wa way of turning off. ven when the "1 hour" has passed the location is still displayed on the screen of the destination client. I tried flicking, looking for a contex menu to stop the location. The only way I can see is killing Jami and reopening it.Amirhossein NaghshzanAmirhossein Naghshzanhttps://git.jami.net/savoirfairelinux/jami-project/-/issues/914Video call in the Windows client triggers Assertion: mtuProbe_ >= MIN_MTU2021-08-20T19:01:08ZEnno RehlingVideo call in the Windows client triggers Assertion: mtuProbe_ >= MIN_MTUWhenever somebody calls me (video call), the Windows client crashes before I even get any notification:
![image](/uploads/32ca39858178edf9203bb3eecc0d9730/image.png)
The same thing happens when I try to initiate the call myself.Whenever somebody calls me (video call), the Windows client crashes before I even get any notification:
![image](/uploads/32ca39858178edf9203bb3eecc0d9730/image.png)
The same thing happens when I try to initiate the call myself.https://git.jami.net/savoirfairelinux/jami-project/-/issues/892Retrieving/Creating an account is impossible2021-07-02T15:57:53ZJerrynickiRetrieving/Creating an account is impossibleI've installed the latest nightly build of Jami on Debian Testing and whenever I try to create an account, import one from an archive or import it from a pin, the client gets stuck at "Retrieving your Jami account..." and the dring proce...I've installed the latest nightly build of Jami on Debian Testing and whenever I try to create an account, import one from an archive or import it from a pin, the client gets stuck at "Retrieving your Jami account..." and the dring process jumps to 8% cpu usage (one thread on my cpu).
I've also tried the official package from testing and compiled jami myself, all had the same issue.
This did not happen with the flatpak package.
Program output:
```** Message: 11:50:04.050: Jami GNOME client version: 1b618a6dac9fbf4891f8c842fae7a1a030a96c88
** Message: 11:50:04.050: git ref: unknown
No accounts to migrate
QDBusMarshaller: type `VectorString' attempts to redefine basic D-BUS type 'as' (QStringList) (Did you forget to call beginStructure() ?)
QDBusMarshaller: type `MapStringVectorString' produces invalid D-BUS signature `a{s}' (Did you forget to call beginStructure() ?)
QDBusMarshaller: type `QMap<QString,MapStringVectorString>' produces invalid D-BUS signature `a{s}' (Did you forget to call beginStructure() ?)
(jami-gnome:84290): Gtk-CRITICAL **: 11:50:04.319: gtk_scrolled_window_add: assertion 'child_widget == NULL' failed
(jami-gnome:84290): Gtk-WARNING **: 11:50:04.382: Theme parsing error: <data>:1:273: not a number
(jami-gnome:84290): Gtk-CRITICAL **: 11:50:12.802: gtk_file_chooser_select_filename: assertion 'filename != NULL' failed
(jami-gnome:84290): Gtk-CRITICAL **: 11:50:22.798: gtk_file_chooser_select_filename: assertion 'filename != NULL' failed
** (jami-gnome:84290): CRITICAL **: 11:50:23.804: gchar* avatar_manipulation_get_temporary(AvatarManipulation*): assertion 'IS_AVATAR_MANIPULATION(view)' failed
Syncing lrc accounts list with the daemon
"detected new account bf28824fa9abe8d2"
Can't open file: "/home/niklas/.local/share/jami/bf28824fa9abe8d2/profile.vcf"```https://git.jami.net/savoirfairelinux/jami-project/-/issues/540Jami client gnome starts and throws an error, then closes2021-05-19T13:58:13ZJan WielkiewiczJami client gnome starts and throws an error, then closesI can't start gnome client using GUI, no window shows. When run it in terminal emulator, the program throws an error:
``
** Message: Jami GNOME client version: development
** Message: git ref: unknown
QDBusMarshaller: type `VectorString'...I can't start gnome client using GUI, no window shows. When run it in terminal emulator, the program throws an error:
``
** Message: Jami GNOME client version: development
** Message: git ref: unknown
QDBusMarshaller: type `VectorString' attempts to redefine basic D-BUS type 'as' (QStringList) (Did you forget to call beginStructure() ?)
QDBusMarshaller: type `MapStringVectorString' produces invalid D-BUS signature `a{s}' (Did you forget to call beginStructure() ?)
QDBusMarshaller: type `QMap<QString,MapStringVectorString>' produces invalid D-BUS signature `a{s}' (Did you forget to call beginStructure() ?)
terminate called after throwing an instance of 'std::out_of_range'
what(): map::at
``
The daemon ran with -pcd options, doesn't seem to see the client(does nothing, when the client is started). I have compiled daemon, lrc, and client myself, the same way as in my previous issue https://git.ring.cx/savoirfairelinux/ring-project/issues/522
Jami versions(tarballs):
2018-12-14
2018-12-15
2018-12-16
Operating system: Devuan ASCII GNU/Linux
Is my setup or distribution, I'm using a ruin? Is it systemd related? If so, please don't make Jami systemd dependent, because it is badly designed.Sébastien BlinSébastien Blinhttps://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-project/-/issues/1088Jami deleting myself-chat issues2020-12-13T08:28:59ZJami deleting myself-chat issues(I am using jami on android but wandering contact request might affect every client)
1. I added myself to the contacts with one click after search, just 'contact added' appears
2. I sent a message to myself and it came back
3. I delete ...(I am using jami on android but wandering contact request might affect every client)
1. I added myself to the contacts with one click after search, just 'contact added' appears
2. I sent a message to myself and it came back
3. I delete chat with myself by holding longer and pressing 'delete contact' (that step pulls that chat to the bottom and clears its history)
4. Now i can't send any message to any chat
5. Fully restart jami
6. Everything works, chat disappeared from the chat list, and after few secs i get a contact request from myself
(I tried all that again thinking this is the real way contacts are added, result was the same)
Summary: can't check if jami really works without creating a chat with myself, contact request for myself seems to travel while no one needed it as i already succeeded sending and receiving data, myself-chat deletion (doesn't fully delete a chat before app restart) breaks sending messages to any chat (message bubble doesn't appear)Iteration 25https://git.jami.net/savoirfairelinux/jami-project/-/issues/1048./make-ring.py should detect qmake 5.152020-12-12T21:12:11ZSébastien Blin./make-ring.py should detect qmake 5.15Itération 21Sébastien BlinSébastien Blin