Thank you
Inspiration from Thunderbird/Betterbird:
Thank you
For some reason I am also unable to select the message above the
jami-gnome --version
765e320f
For some reason I am also unable to select the message above the
jami-gnome --version
765e320f
@sblin Oh, I start jami as admin again. Now, it works! Thank you so much!
With the few details you given (and no log) I can't say. I have no issue (but I have only one disk) and I don't need any admin right
@sblin Hi, thank you for the link. I realized that I post in the wrong place. But anyway, is this problem solved or not? I tried to launch jami as admin. But that does not give any difference. What is more, why can't jami on windows directly paste and show images?
Dear developers,
I just started using jami. I installed jami on windows and Android with different accounts respectively. I did some tests on sending messages. I found that it is fine sending text, images, files from Android to windows. But when sending images or files from windows to Android, the message always tagged as "incoming transfer". For example, I paste an image into the sending box, it is like below before sending
After click sending, It looks like this
at the same time, on android side, I do receive a message with a "download" sign. But no matter how I click that, it does not give any respond.
There are 4 issues here:
best regards
Hi and thank you for the report, however I close this as a duplicate of jami-client-qt#908 (closed)
Dear developers,
I just started using jami. I installed jami on windows and Android with different accounts respectively. I did some tests on sending messages. I found that it is fine sending text, images, files from Android to windows. But when sending images or files from windows to Android, the message always tagged as "incoming transfer". For example, I paste an image into the sending box, it is like below before sending
After click sending, It looks like this
at the same time, on android side, I do receive a message with a "download" sign. But no matter how I click that, it does not give any respond.
There are 4 issues here:
best regards
The situation: I have a Bose qc35 II, and for some reason, the microphone deosn't work on linux over bluetooth, it's a well known issue not related to Jami.
The solution is to setup my laptop microphone as default, so I can hear people from my headphone andthe can hear me from my laptop microphone. (see attached screeshot)
This setup works well on telegram app, whereby and nextcloud talk (using firefox or chrome) but on Jami it's lookalike the app try to use my headset microphone, so nobody can hear me.
I made a video call from Android client version 20191208 to Gnome client version 20191217 or 20191224, turned on and off screen sharing on Android a few times and then closed the screen sharing. This made the gnome client to close and throw "31452 Bus error", Android client was fine though. I tested this only on Guix System with with the package I made. Patches for pjproject and ffmpeg were applied correctly, we use the 3.6.9 version instead of 3.6.10 though, don't know if it's a problem, but I can test it soon.
-> "Open chat". That would be the minimal variant of this issue.
At the same time I wonder why the search bar is called "Find or start a conversation" and if it needs some more changes.
My idea: Simply rename the search bar to "Find conversation" and declare the + button as "Start conversation". Because the search field never starts a conversation.
Irritating would be the back button within the conversation view, which currently has the tooltip "Hide chat view". Is it actually spelled "chat view" or "chatview"? And shouldn't it be called "Conversation(s) view" and therefore "Hide conversation"?
While typing a message in the typing bar and switching to a different conversation, the unready message is still displayed there. This should be unique for all contacts and accounts (because it happens after switching to another account too) to avoid sending a message to a different person, the message was for and to let users type long messages to different people at the same time.
After switching:
Currently: Accounts can be imported an unrestricted number of times. They are all considered to be independent devices, so it is expected to work fine.
This is confusing. 99% of users just don't want to have the same account twice on the same machine. For them, it will juste be a bug and bad UX.
What we should probably do: Print an explicit warning when one tries to import an account which is already present.
Issue generated from Tuleap's migration script. Originally submitted by: Isak Rubin (isakrubin)
username and avatar seems to not be synced across devices.
* Environment:
Android 7.1
Debian Stretch
* Reproduce steps:
Install on android, register account, setup avatar and username.
Install on debian using deb package, connect account using pincode.
* Expected result:
Expect my username and avatar to be available on my debian setup.
* Actual result:
Avatar and username not synced, not even able to set my username in the settings as it says it's not available.
Once i made the choice to replace the default avatar picture, there seems to be no way to get back. I could change it again and again, but i am still stuck to the decision that i have to choose one manually.
btw. most of my contacts have still their generic id avatars. Until i choose a new picture on my own, my contatcs should see such an generic avatar as well, right? But why don't i see my own generic avatar until i choose a profile picture manually? At the moment this looks more logical to me. Instead of the avatar placeholder that i can see at the moment.
The client uses several deprecated features which could eventually be an issue. Attached is a grep of the make logs listing the deprecated functions.