savoirfairelinux issueshttps://git.jami.net/groups/savoirfairelinux/-/issues2021-09-24T16:17:26Zhttps://git.jami.net/savoirfairelinux/jami-daemon/-/issues/587ice_transport: Ice default remote address is not IPv4 nor IPv62021-09-24T16:17:26ZOlivier Dionice_transport: Ice default remote address is not IPv4 nor IPv6RTCP address set by `VideoRtpSession::start` is not an IPv4 nor and IPv6.
See
- [report.txt](/uploads/0c305b28c4737641802f05ec5f13787a/gdb.txt)
- [report2.txt](/uploads/96f2af2d4bda88119c42bf56bd35e7cd/gdb.txt)RTCP address set by `VideoRtpSession::start` is not an IPv4 nor and IPv6.
See
- [report.txt](/uploads/0c305b28c4737641802f05ec5f13787a/gdb.txt)
- [report2.txt](/uploads/96f2af2d4bda88119c42bf56bd35e7cd/gdb.txt)Mohamed ChibaniOlivier DionMohamed Chibanihttps://git.jami.net/savoirfairelinux/jami-client-qt/-/issues/521Chatview: vertical scroll bar should be present if the chatview has more info...2021-09-22T14:17:12ZovariChatview: vertical scroll bar should be present if the chatview has more information that the height of the screenWhen the chatview has more entries than the height of the screen, you can use the mouse wheel to scroll; however, there doesn't seem to be a vertical scroll bar.
Can you please implement a vertical scroll bar in the chatview?
Thank you...When the chatview has more entries than the height of the screen, you can use the mouse wheel to scroll; however, there doesn't seem to be a vertical scroll bar.
Can you please implement a vertical scroll bar in the chatview?
Thank you
Linux Mint 20.2 Cinnamon<br>
Jami client-qt Verzió: 202108261858Andreas TraczykAndreas Traczykhttps://git.jami.net/savoirfairelinux/jami-client-qt/-/issues/533chat window not available2021-09-21T19:55:16ZJavierchat window not available- OS: Artix GNU + Linux (AUR package)
- Jami version: built from head of master (3f27289)
- What build you are using: AUR - https://aur.archlinux.org/packages/jami-client-qt-git (head of master, currently, 3f27289)
- Can you reprodu...- OS: Artix GNU + Linux (AUR package)
- Jami version: built from head of master (3f27289)
- What build you are using: AUR - https://aur.archlinux.org/packages/jami-client-qt-git (head of master, currently, 3f27289)
- Can you reproduce the bug: at will (always)
- Steps:
1. Just start jami, and I get the image
![image](/uploads/201b6bb49cc17160d108aba60c8143c8/image.png)
2. No matter how many times I click on the contacts' at the left, the chat window on the right never shows, up, only the jami advertising window remains. Even if a contact writes to me, or myself (from the phone), I can't get to the chat window to reply...
...
- Actual result: No way to access any contact chat window.
- Expected result: When clicking on a contact, the chat window should be visible, instead of the jami advertising one.https://git.jami.net/savoirfairelinux/jami-daemon/-/issues/629Jami (Windows 10): Crash if another person displays own [Android]screen in la...2021-09-21T17:29:49ZElysJami (Windows 10): Crash if another person displays own [Android]screen in landscape (horizontal) modePerson A: Windows 10: Jami version 202109171743
Person B: Android: using newest beta version of Jami (Mate 20 Pro, EMUI 11):
Steps to reproduce:
Start Jami (windows 10 AND Android), wait until both persons are online (bug android: ht...Person A: Windows 10: Jami version 202109171743
Person B: Android: using newest beta version of Jami (Mate 20 Pro, EMUI 11):
Steps to reproduce:
Start Jami (windows 10 AND Android), wait until both persons are online (bug android: https://git.jami.net/savoirfairelinux/jami-client-android/-/issues/994)
(Steps Person B:) Rotate your phone: change the screen mode to landscape. You make a video call. Now Person A can see Person B. Then Person B shares the screen.
Result: Jami (Windows 10, Person A) crashes, the version of android keeps going on.https://git.jami.net/savoirfairelinux/jami-client-qt/-/issues/532Jami (Windows 10): Crash if another person displays own [Android]screen in la...2021-09-21T17:26:04ZElysJami (Windows 10): Crash if another person displays own [Android]screen in landscape (horizontal) modePerson A: Windows 10: Jami version 202109171743
Person B: Android: using newest beta version of Jami (Mate 20 Pro, EMUI 11):
Steps to reproduce:
Start Jami (windows 10 AND Android), wait until both persons are online (bug android: ht...Person A: Windows 10: Jami version 202109171743
Person B: Android: using newest beta version of Jami (Mate 20 Pro, EMUI 11):
Steps to reproduce:
Start Jami (windows 10 AND Android), wait until both persons are online (bug android: https://git.jami.net/savoirfairelinux/jami-client-android/-/issues/994)
(Steps Person B:) Rotate your phone: change the screen mode to landscape. You make a video call. Now Person A can see Person B. Then Person B shares the screen.
Result: Jami (Windows 10, Person A) crashes, the version of android keeps going on.https://git.jami.net/savoirfairelinux/jami-client-qt/-/issues/529empty conversation2021-09-21T07:08:03Zcarross-tlhuillierempty conversation## Describe your environment
- OS:xubuntu 21.04
- Jami version:202109142121
- repo: https://dl.jami.net/nightly/ubuntu_20.04/ jami main
## Steps to reproduce
- Can you reproduce the bug: at will
- Steps:
1. Open Jami
2. Write...## Describe your environment
- OS:xubuntu 21.04
- Jami version:202109142121
- repo: https://dl.jami.net/nightly/ubuntu_20.04/ jami main
## Steps to reproduce
- Can you reproduce the bug: at will
- Steps:
1. Open Jami
2. Write a message containing "%0" (ex. <td><?=sprintf('%01.2f', $Price->sellPrice)?> <?=_("€ HT")?></td>) to someone
3. Close Jami
4. Open Jami
5. Go to the conversation
- Actual result: there is no messages in the conversation and no new messages can appear in the conversation
- Expected result: there should be the full history in the conversation and new messages should be added to the conversation
## Additional information
logs:
`"notify server name: Xfce Notify Daemon, vendor: Xfce, version: 0.4.4, spec: 1.2"
No migration required
could not update message status for not existing conversation
could not update message status for not existing conversation
could not update message status for not existing conversation
could not update message status for not existing conversation
could not update message status for not existing conversation
could not update message status for not existing conversation
could not update message status for not existing conversation
Can't open file: "/home/xxxxx/.local/share/jami/xxxxxxxxxxxx/profile.vcf"
Cannot find dbus interface for screen saver
Syncing lrc accounts list with the daemon
NetworkManager client initialized, version: 1.22.10 , daemon running: yes , networking enabled: yes
primary network connection: xxxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxx default: yes
qrc:/src/mainview/MainView.qml:471:5: QML AboutPopUp: Binding loop detected for property "height"
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() ?)
NewAccountModel::getAccountInfo, can't find dummy ; Using default avatar
NewAccountModel::getAccountInfo, can't find dummy ; Using default avatar
js: Uncaught SyntaxError: Unexpected token '%'`
The last line appear when I open the conversation.Sébastien BlinSébastien Blinhttps://git.jami.net/savoirfairelinux/jami-client-qt/-/issues/527Device link PIN characters cut off2021-09-20T20:26:29ZAlexander Lussier-CullenDevice link PIN characters cut off## Describe your environment
Please specify the following:
- OS: Ubuntu 20.04
- Jami version: 202109142155
- What build you are using: jami.net
## Steps to reproduce
- Can you reproduce the bug: at will
- Steps:
1. Go to account set...## Describe your environment
Please specify the following:
- OS: Ubuntu 20.04
- Jami version: 202109142155
- What build you are using: jami.net
## Steps to reproduce
- Can you reproduce the bug: at will
- Steps:
1. Go to account settings
2. Click Link another device
- Actual result: Characters of the PIN have their tops cut off
- Expected result: Characters of the PIN without their tops cut off
## Additional information
![Screenshot_from_2021-09-15_13-23-12](/uploads/a5190a6cc3a013636a05d8684fb5a8a7/Screenshot_from_2021-09-15_13-23-12.png)https://git.jami.net/savoirfairelinux/jami-client-qt/-/issues/522Settings: crash when changing between media and other tabs2021-09-20T20:24:37ZAndreas TraczykSettings: crash when changing between media and other tabsAlso may occur when entering and exiting the settings page. This seems to be caused by unprotected access provoked by the async start/stop calls to the audio input stream when enabling and disabling the audiometer.Also may occur when entering and exiting the settings page. This seems to be caused by unprotected access provoked by the async start/stop calls to the audio input stream when enabling and disabling the audiometer.Andreas TraczykAndreas Traczykhttps://git.jami.net/savoirfairelinux/jami-client-qt/-/issues/535Should there be only 1 jami folder in /.local/share/ ?2021-09-20T13:29:06ZovariShould there be only 1 jami folder in /.local/share/ ?There are 2 folders, i.e. `Jami` and `jami`, in `/.local/share/`.
![image](/uploads/edeb08b8a9b5b3766a5221ccb0ff986c/image.png)
Should there be only 1 `jami` folder `/.local/share/`?
It is understood that Windows is case-insensitive s...There are 2 folders, i.e. `Jami` and `jami`, in `/.local/share/`.
![image](/uploads/edeb08b8a9b5b3766a5221ccb0ff986c/image.png)
Should there be only 1 `jami` folder `/.local/share/`?
It is understood that Windows is case-insensitive so these folders might be the same location with a Windows operating system; however, GNU/Linux operating systems are case-sensitive.
Should the name be in all lowercase, i.e. `jami`?
What do you think?
Thank youhttps://git.jami.net/savoirfairelinux/jami-client-qt/-/issues/534Revoked device blank screen startup2021-09-19T21:57:50ZovariRevoked device blank screen startup1. Revoke a device (client-qt on Linux Mint 20.2 Cinnamon) from another device.
2. Open Jami on the device (client-qt on Linux Mint 20.2 Cinnamon) which has Jami revoked.<br>
Unable to do anything.<br>
Question 1: Should the screen be th...1. Revoke a device (client-qt on Linux Mint 20.2 Cinnamon) from another device.
2. Open Jami on the device (client-qt on Linux Mint 20.2 Cinnamon) which has Jami revoked.<br>
Unable to do anything.<br>
Question 1: Should the screen be the start screen?<br>
Question 2: Does all the data files get deleted on the revoked device?
Screenshot of Jami on the revoked device.
![Revoked_Device](/uploads/0130865256905851a5d3cd88a9afeed5/Revoked_Device.png)
Is this critical as we can't set up the device again until a fix is provided?
Thank you
client-qt Verzió: 202109142121 deb edition<br>
Linux Mint 20.2 Cinnamonhttps://git.jami.net/savoirfairelinux/jami-project/-/issues/1290Daemon submodule Update Fails2021-09-17T17:22:57ZBrightson JupiriDaemon submodule Update Failshi Jami,
I'm compiling for the client-qt for Windows
was trying to update submodule "git submodule update --init daemon lrc client-qt"
but got error,
**error: no such remote ref d1aa79d02af606861b1bf9029cb31645e059b079
Fetched in sub...hi Jami,
I'm compiling for the client-qt for Windows
was trying to update submodule "git submodule update --init daemon lrc client-qt"
but got error,
**error: no such remote ref d1aa79d02af606861b1bf9029cb31645e059b079
Fetched in submodule path 'daemon', but it did not contain d1aa79d02af606861b1bf9029cb31645e059b079. Direct fetching of that commit failed.**
Tried this on Android/release_316 and the Master, both produce the same problem
kindly Assist on this, Thank you :smile:https://git.jami.net/savoirfairelinux/jami-project/-/issues/1301Please allow `Share this` to be translatable2021-09-16T21:13:15ZovariPlease allow `Share this` to be translatablePlease allow `Share this` to be translatable.
![Share this](/uploads/040b3fffc9435d37aa8e11fc55d779f9/image.png)
Thank you
P.S. Congratulations on release of the [First Jami beta with Swarm support](https://jami.net/first-jami-beta-wi...Please allow `Share this` to be translatable.
![Share this](/uploads/040b3fffc9435d37aa8e11fc55d779f9/image.png)
Thank you
P.S. Congratulations on release of the [First Jami beta with Swarm support](https://jami.net/first-jami-beta-with-swarm-support/). Looking forward this article being translatable too and reading the future blog about `The introduction of the new file transfer system`. Thank you once again.https://git.jami.net/savoirfairelinux/jami-client-qt/-/issues/524Account migration: dialog doesn't work2021-09-16T18:32:49ZAndreas TraczykAccount migration: dialog doesn't workOutput:
`qrc:/src/commoncomponents/AccountMigrationDialog.qml:91: TypeError: Property 'updateImage' of object Avatar_QMLTYPE_49(0x1dbcf3b0ee0) is not a function`Output:
`qrc:/src/commoncomponents/AccountMigrationDialog.qml:91: TypeError: Property 'updateImage' of object Avatar_QMLTYPE_49(0x1dbcf3b0ee0) is not a function`Andreas TraczykAndreas Traczykhttps://git.jami.net/savoirfairelinux/jami-client-qt/-/issues/439Bug on GNU/Linux gnome with the icon and multiple instances2021-09-15T21:11:09ZAltonsBug on GNU/Linux gnome with the icon and multiple instances## Describe your environment
Please specify the following:
- OS: Fedora 34 with Gnome desktop
- Jami version:202105282159
- What build you are using: jami.net
## Steps to reproduce
Note: Better the scenario is, better we will be able...## Describe your environment
Please specify the following:
- OS: Fedora 34 with Gnome desktop
- Jami version:202105282159
- What build you are using: jami.net
## Steps to reproduce
Note: Better the scenario is, better we will be able to reproduce and debug.
- Can you reproduce the bug: at will
- Steps:
1. Open jami
2. (You can reopen another Jami)
- Actual result:
When I start Jami, it launches well, but the icon is a generic one (not the icon of Jami) and it is written net.jami.jami-qt
When lauching from the command line I get:
```
QSocketNotifier: Can only be used with threads started with QThread
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() ?)
```
I am also able to lauch several instances of Jami, which is weird.
- Expected result:
## Additional information
![image](/uploads/fcce3bdfca819a2ebaea73c4d45cca18/image.png)
Several instances
![image](/uploads/9d684133d22662dee82ec6f0dc3c0a07/image.png)
Several instances, view of the icon tray (appindicator extension for gnome)
![image](/uploads/c9352a943d38be2bbdd1caeac6a17d49/image.png)https://git.jami.net/savoirfairelinux/jami-client-android/-/issues/992Jami Beta on Fdroid (or just outside Google Play)2021-09-15T18:08:00ZxliivJami Beta on Fdroid (or just outside Google Play)I heard, that Beta with Swarm feature is available on Google Play: https://git.jami.net/savoirfairelinux/ring-client-android/-/issues/501#note_30472
Users (without Google Play access) could help testing it if it was available via Fdroid...I heard, that Beta with Swarm feature is available on Google Play: https://git.jami.net/savoirfairelinux/ring-client-android/-/issues/501#note_30472
Users (without Google Play access) could help testing it if it was available via Fdroid (or any other channel, is it?).
Regular Jami is released on Fdroid, see https://f-droid.org/en/packages/cx.ring/https://git.jami.net/savoirfairelinux/jami-client-android/-/issues/501Message sent but not received2021-09-15T17:51:49ZbeletteMessage sent but not received## Describe your environment
- Ring version: 20180501 (latest from F-Droid)
- Device model: Samsung-S3
- Android version: Replicant (Android 6.0)
- What build you are using: F-droid (latest availalbe on date)
## Steps to reprodu...## Describe your environment
- Ring version: 20180501 (latest from F-Droid)
- Device model: Samsung-S3
- Android version: Replicant (Android 6.0)
- What build you are using: F-droid (latest availalbe on date)
## Steps to reproduce
- Can you reproduce the bug: yes
- Steps:
1. sending a message
2. not received on the other end
## Additional information
Message take time to be sent (about 30sec for a single word on 3G+ network)
Image are not sent at all (Unjoinable Peer)
I am able to receive some messages. (about 1/5)
My correspondant never received any message..Sébastien BlinSébastien Blinhttps://git.jami.net/savoirfairelinux/jami-client-qt/-/issues/508Unable to `Edit device name` on Linux Mint 20.2 client-qt deb version2021-09-15T17:51:34ZovariUnable to `Edit device name` on Linux Mint 20.2 client-qt deb version1. Click `Open settings`
2. Click `Account`
3. In `Linked Devices`, click on the pencil to the right `Edit device name` (perhaps this should always be the first in the list?)
4. Change the name to `Linux Mint`
5. Click on the button to t...1. Click `Open settings`
2. Click `Account`
3. In `Linked Devices`, click on the pencil to the right `Edit device name` (perhaps this should always be the first in the list?)
4. Change the name to `Linux Mint`
5. Click on the button to the right `Save new device name`<br>
Looks like it is saved
6. Click `Close settings`
7. Click `Open settings`<br>
The device name is now what it was before being changed to `Linux Mint`
Also tried `LinuxMint`, i.e. without a space and that didn't work either.
Are you able to reproduce and please fix?
Thank you
Linux Mint 20.2 Cinnamon<br>
client-qt Version: 202108261858https://git.jami.net/savoirfairelinux/jami-daemon/-/issues/610ICE/SIPCall - possible race condition in ICE initialization2021-09-15T14:23:37ZMohamed ChibaniICE/SIPCall - possible race condition in ICE initializationPossible race condition between JamiAccount::SIPStartCall() and SIPCall::initIceMediaTransport(). SIPCall::addLocalIceAttributes() is called by SIPStartCall() before the ice session is fully setup.
```
[1628703709.408|52540|ice_transpor...Possible race condition between JamiAccount::SIPStartCall() and SIPCall::initIceMediaTransport(). SIPCall::addLocalIceAttributes() is called by SIPStartCall() before the ice session is fully setup.
```
[1628703709.408|52540|ice_transport.cpp :791 ] [ice:0x7fff99480f00] added host stun config for UDP transport
[1628703709.422|52540|ice_transport.cpp :566 ] [ice:0x7fff99480f00] UDP initialization success
[1628703709.422|52540|ice_transport.cpp :630 ] [ice:0x7fff99480f00] as master
[1628703709.426|52540|ice_transport.cpp :766 ] [ice:0x7fff99480f00] (local) ufrag=132de820, pwd=057ba91211155276119d9083
[1628703709.430|52686|sipcall.cpp :1642 ] [call:438314284593258] no media ICE transport, SDP not changed
[1628703709.432|52686|sipcall.cpp :686 ] [call:438314284593258] Set new invite session [0x7fff94133328]
[1628703709.436|52540|sipcall.cpp :2935 ] [call:438314284593258] Successfully created media ICE transport
```Mohamed ChibaniSébastien BlinMohamed Chibanihttps://git.jami.net/savoirfairelinux/jami-project/-/issues/1303Disable video call button when video is disabled in account settings2021-09-15T12:26:19ZChristian WeiskeDisable video call button when video is disabled in account settingsI use Jami as SIP phone only, and thus only have a SIP account. I don't do video calls via SIP, so I disabled "activate video" in the account settings.
It would be nice if the "Start video call" and "send video message" (no idea how it'...I use Jami as SIP phone only, and thus only have a SIP account. I don't do video calls via SIP, so I disabled "activate video" in the account settings.
It would be nice if the "Start video call" and "send video message" (no idea how it's called in english, I only see the German interface) would be hidden in the contact details/message view.https://git.jami.net/savoirfairelinux/jami-daemon/-/issues/624Unable to revoke a device/remove a device from the list of linked devices2021-09-14T20:08:47ZovariUnable to revoke a device/remove a device from the list of linked devicesUnable to revoke a device.
client-android shows a message with title `Can't revoke device` with message `Unknown device.`
If the device is unknown, how can the device be removed from the list?
client-qt does not revoke the device and ...Unable to revoke a device.
client-android shows a message with title `Can't revoke device` with message `Unknown device.`
If the device is unknown, how can the device be removed from the list?
client-qt does not revoke the device and provides no feedback.
Can client-qt please show a message if it was unable to revoke a device like Android does?
Please advise if you need a screenshot from the Android device.
Thank you
client-andriod 20210812-01
Linux Mint 20.2 Cinnamon<br>
client-qt 202108172029Sébastien BlinSébastien Blin