jami-client-gnome issueshttps://git.jami.net/savoirfairelinux/jami-client-gnome/-/issues2019-04-23T18:26:49Zhttps://git.jami.net/savoirfairelinux/jami-client-gnome/-/issues/817Non-fatal rpm-package's build error on Fedora Linux !2019-04-23T18:26:49ZNokia808Non-fatal rpm-package's build error on Fedora Linux !Hi. There is an error repeatedly occurring every time updating Ring on Fedora Linux. I test it on Fedora 26. Now I'm on Fedora 28 & Ring not available to it.
Take this terminal output for an updating process to see this issue:
```
sudo...Hi. There is an error repeatedly occurring every time updating Ring on Fedora Linux. I test it on Fedora 26. Now I'm on Fedora 28 & Ring not available to it.
Take this terminal output for an updating process to see this issue:
```
sudo dnf upgrade --refresh
Last metadata expiration check: 0:00:00 ago on Sat 10 Feb 2018 09:55:04 AM GMT.
Dependencies resolved.
================================================================================
Package Arch Version Repository
Size
================================================================================
Upgrading:
ring x86_64 20180209.1.830d387-1.fc26 ring 2.0 M
ring-daemon x86_64 20180209.1.830d387-1.fc26 ring 4.6 M
Transaction Summary
================================================================================
Upgrade 2 Packages
Total download size: 6.6 M
Is this ok [y/N]: y
Downloading Packages:
(1/2): ring-20180209.1.830d387-1.fc26.x86_64.rp 393 kB/s | 2.0 MB 00:05
(2/2): ring-daemon-20180209.1.830d387-1.fc26.x8 335 kB/s | 4.6 MB 00:14
--------------------------------------------------------------------------------
Total 474 kB/s | 6.6 MB 00:14
Running transaction check
Transaction check succeeded.
Running transaction test
Transaction test succeeded.
Running transaction
Preparing : 1/1
Upgrading : ring-daemon-20180209.1.830d387-1.fc26.x86_64 1/4
Upgrading : ring-20180209.1.830d387-1.fc26.x86_64 2/4
Running scriptlet: ring-20180209.1.830d387-1.fc26.x86_64 2/4
Cleanup : ring-20180201.1.1c179b2-1.fc26.x86_64 3/4
Running scriptlet: ring-20180201.1.1c179b2-1.fc26.x86_64 3/4
/sbin/ldconfig: relative path `1' used to build cache
warning: %postun(ring-20180201.1.1c179b2-1.fc26.x86_64) scriptlet failed, exit status 1
Non-fatal POSTUN scriptlet failure in rpm package ring
Non-fatal POSTUN scriptlet failure in rpm package ring
Cleanup : ring-daemon-20180201.1.1c179b2-1.fc26.x86_64 4/4
Running scriptlet: ring-20180209.1.830d387-1.fc26.x86_64 4/4
Running scriptlet: ring-daemon-20180201.1.1c179b2-1.fc26.x86_64 4/4
Running as unit: run-r28b48fa5938e4ecf8c8f1727889c7a76.service
Verifying : ring-20180209.1.830d387-1.fc26.x86_64 1/4
Verifying : ring-daemon-20180209.1.830d387-1.fc26.x86_64 2/4
Verifying : ring-20180201.1.1c179b2-1.fc26.x86_64 3/4
Verifying : ring-daemon-20180201.1.1c179b2-1.fc26.x86_64 4/4
Upgraded:
ring.x86_64 20180209.1.830d387-1.fc26
ring-daemon.x86_64 20180209.1.830d387-1.fc26
Complete!
As you see there is a warning say:
"warning: %postun(ring-20180201.1.1c179b2-1.fc26.x86_64) scriptlet failed, exit status 1
Non-fatal POSTUN scriptlet failure in rpm package ring
Non-fatal POSTUN scriptlet failure in rpm package ring"
In fact Ring was working well inspite this error !
What is this exactly ?Sébastien BlinSébastien Blinhttps://git.jami.net/savoirfairelinux/jami-client-gnome/-/issues/809database related crash during exit2020-10-05T20:23:10ZHugo Lefeuvredatabase related crash during exitSometimes the client crashes during exit with following error messages in the debug output:
```
** (gnome-ring:31292): DEBUG: quitting
QSqlQuery::prepare: database not open
** (gnome-ring:31292): WARNING **: Can't get conversation at r...Sometimes the client crashes during exit with following error messages in the debug output:
```
** (gnome-ring:31292): DEBUG: quitting
QSqlQuery::prepare: database not open
** (gnome-ring:31292): WARNING **: Can't get conversation at row 0
QSqlQuery::prepare: database not open
** (gnome-ring:31292): WARNING **: Can't get conversation at row 0
QSqlQuery::prepare: database not open
terminate called after throwing an instance of 'lrc::Database::QueryError'
what(): Driver not loaded Driver not loaded
Aborted (core dumped)
```
I suspect a race condition in the LRC. Something like:
1. DB is closed
2. a signal comes and the callback tries to access the DB's freed data structures
Since this bug is only reproducible on the GNU/Linux GNOME client I'm reporting it here.
**How to reproduce:**
1. open a GNU/Linux GNOME client
2. close it using "quit" button
This crash is pretty rare, and like most race conditions it may not be reproducible on every machine.https://git.jami.net/savoirfairelinux/jami-client-gnome/-/issues/798chatview: Unable to display some emojis2019-11-12T20:18:01ZHugo Lefeuvrechatview: Unable to display some emojisThe chatview fails to display some emojis. It appears that affected emojis are all part of the Emoji 3.0 (Unicode 9.0) spec.
Some examples: 🦊 (U+1F98A), 🦋 (U+1F98B), 🦍 (U+1F98D), 🥜 (U+1F95C), 🥐 (U+1F950).
**How to reproduce:**
1. Open...The chatview fails to display some emojis. It appears that affected emojis are all part of the Emoji 3.0 (Unicode 9.0) spec.
Some examples: 🦊 (U+1F98A), 🦋 (U+1F98B), 🦍 (U+1F98D), 🥜 (U+1F95C), 🥐 (U+1F950).
**How to reproduce:**
1. Open another client (macOS, Android), and send a fox 🦊 (U+1F98A) Emoji to the GNU/Linux GNOME client.
2. The GNU/Linux GNOME client fails to display received Emoji. Only the background is displayed.
This may be a bug in the dependency chain.Full Emoji support 🚩https://git.jami.net/savoirfairelinux/jami-client-gnome/-/issues/743view inconsistency bug2018-06-01T19:53:18ZJami Botview inconsistency bugIssue generated from Tuleap's migration script.
**Originally submitted by: Hugo Lefeuvre (hle)**
\* Environment:
GNU/Linux GNOME client, latest master
\* Reproduce steps:
Create two ring accounts A and B and a conversation betw...Issue generated from Tuleap's migration script.
**Originally submitted by: Hugo Lefeuvre (hle)**
\* Environment:
GNU/Linux GNOME client, latest master
\* Reproduce steps:
Create two ring accounts A and B and a conversation between them. The two accounts should not have any more contacts than the other account, that is A's only contact is B and vice versa. Select the conversation in A's tab and switch to B. The conversation with A stays selected \_but\_ the chat view isn't displayed.
\* Expected result:
The conversation with A should not be selected, or if it is selected then the chat view should be displayed.
\* Fix:
https://gerrit-ring.savoirfairelinux.com/\#/c/9401/https://git.jami.net/savoirfairelinux/jami-client-gnome/-/issues/788"Searching..." displays as a contact2018-07-03T18:53:23ZJami Bot"Searching..." displays as a contactIssue generated from Tuleap's migration script.
**Originally submitted by: Jan (kromka_chleba)**
After typing ring id in the search bar, adding contact with invite button, and clearing search bar with backspace, search icon appears amon...Issue generated from Tuleap's migration script.
**Originally submitted by: Jan (kromka_chleba)**
After typing ring id in the search bar, adding contact with invite button, and clearing search bar with backspace, search icon appears among contacts.
Platform: GNU/Linux Mint 18.3 cinnamon, kernel 4.13.0-41 generic
Ring build: 2018-05-01https://git.jami.net/savoirfairelinux/jami-client-gnome/-/issues/739Wrong path when starting evolution-source-registry2018-11-02T17:57:40ZJami BotWrong path when starting evolution-source-registryIssue generated from Tuleap's migration script.
**Originally submitted by: Baptiste Jonglez (baptiste)**
The Ring daemon tries to run /usr/lib/evolution-data-server/evolution-source-registry, but this does not exist on Arch Linux. The ...Issue generated from Tuleap's migration script.
**Originally submitted by: Baptiste Jonglez (baptiste)**
The Ring daemon tries to run /usr/lib/evolution-data-server/evolution-source-registry, but this does not exist on Arch Linux. The binary is at /usr/lib/evolution-source-registry instead.
\* Environment:
Arch Linux, ring 20180419.1.01da897, evolution-data-server 3.28.1
\* To reproduce
Just start the Gnome client, it will start the daemon which will print the error in journalctl.
\* Actual result:
avril 21 00:01:33 lud dbus-daemon[1637]: Activating via systemd: service name='org.gnome.evolution.dataserver.Sources5' unit='evolution-source-registry.service'
avril 21 00:01:33 lud systemd[1101]: Starting Evolution source registry...
avril 21 00:01:33 lud systemd[488]: evolution-source-registry.service: Failed to execute command: No such file or directory
avril 21 00:01:33 lud systemd[488]: evolution-source-registry.service: Failed at step EXEC spawning /usr/lib/evolution-data-server/evolution-source-registry: No such file or directory
avril 21 00:01:33 lud systemd[1101]: evolution-source-registry.service: Main process exited, code=exited, status=203/EXEC
avril 21 00:01:33 lud systemd[1101]: evolution-source-registry.service: Failed with result 'exit-code'.
avril 21 00:01:33 lud systemd[1101]: Failed to start Evolution source registry.https://git.jami.net/savoirfairelinux/jami-client-gnome/-/issues/735half of viewing window is green2018-07-24T13:49:39ZJami Bothalf of viewing window is greenIssue generated from Tuleap's migration script.
**Originally submitted by: Larson Smith (dodddummy)**
The viewing area on video calls is a little more than halfway filled with solid green. DEs are lxqt and lxde.
\* Environment:
...Issue generated from Tuleap's migration script.
**Originally submitted by: Larson Smith (dodddummy)**
The viewing area on video calls is a little more than halfway filled with solid green. DEs are lxqt and lxde.
\* Environment:
Debian 9 64 bit upgrades current as of 4/14/2018.
"In varietate concordia"
built on 2018-04-14 22:49:42 UTC
\* Reproduce steps:
Place or receive a video call
\* Expected result:
Viewing area should not be partially filled with green.
\* Actual result:
What is the actual result on running the above steps i.e. the bug behavior.
The viewing area of video calls flicker and the top half show the other persons camera but the lower half is solid green.
I don't know if it's related but the two laptops with this issue are debian 9 on 64 bit and the one laptop with no issues is debian 9 on 32 bit.https://git.jami.net/savoirfairelinux/jami-client-gnome/-/issues/786[GNOME] Enable right-click menu when above Device ID with menu item ‘Copy’2018-05-26T23:20:18ZJami Bot[GNOME] Enable right-click menu when above Device ID with menu item ‘Copy’Issue generated from Tuleap's migration script.
**Originally submitted by: Óvári (ovari)**
\* Environment:
Linux Mint 18.3 Cinnamon 64-bit
ring-gnome built on 2018-04-06 22:56:04 UTC
\* Reproduce steps:
1. Settings
2. Accou...Issue generated from Tuleap's migration script.
**Originally submitted by: Óvári (ovari)**
\* Environment:
Linux Mint 18.3 Cinnamon 64-bit
ring-gnome built on 2018-04-06 22:56:04 UTC
\* Reproduce steps:
1. Settings
2. Accounts
3. Select an ‘Account’
4. Devices
5. Please enable right-clicking on a Device ID to show a context menu with ‘Copy’. The attached image shows the areas with a red 1, blue 2, green 3, yellow 4 and light blue 5.
6. This will enable pasting the Device ID into the “Search contacts or enter number” in the main Ring window to call ring users
\* Expected result:
Able to copy Device ID.
\* Actual result:
Unable to copy Device ID.
Thank you
Xref
bug \#1821 - [GNOME] Remove Device, Rename Device and Update Device Name
https://tuleap.ring.cx/plugins/tracker/?aid=1821
bug \#1794 - [GNOME] Unable to place intercom call \*regression\*
https://tuleap.ring.cx/plugins/tracker/?aid=1794
bug \#1700 - [GNOME] Three computers in audio conference call (no video) with 2 unique usernames not working
https://tuleap.ring.cx/plugins/tracker/?aid=1700
![DeviceID](/uploads/265efe9ecd5b7355aa7e09b2c5484fc1/DeviceID.png)https://git.jami.net/savoirfairelinux/jami-client-gnome/-/issues/731[GNOME] SIP TCP protocol support2019-08-27T18:35:16ZJami Bot[GNOME] SIP TCP protocol supportIssue generated from Tuleap's migration script.
**Originally submitted by: Óvári (ovari)**
SIP providers recommended different SIP Transport settings. For example:
\* Transport: Leave UDP for desktop, select TCP if you are using on yo...Issue generated from Tuleap's migration script.
**Originally submitted by: Óvári (ovari)**
SIP providers recommended different SIP Transport settings. For example:
\* Transport: Leave UDP for desktop, select TCP if you are using on your mobile or via mobile connection
1. Would you please enable GNU Ring to allow UDP and TCP transport selection for SIP accounts?
Linphone (http://linphone.org/) provides the following transport options:
\* UDP (User Datagram Protocol)
\* TCP (Transmission Control Protocol)
\* TLS (Transport Layer Security)
\* DTLS (Datagram Transport Layer Security)
2. Can code from Linphone be used in GNU Ring?
3. Does this apply to other platforms, i.e. Android?
4. If so, does the platform for this ticket need to be changed to “Any”?
Thank youSébastien BlinSébastien Blinhttps://git.jami.net/savoirfairelinux/jami-client-gnome/-/issues/727'Download folder' dialog in General Preferences has undefined name and is non...2018-05-22T00:48:18ZJami Bot'Download folder' dialog in General Preferences has undefined name and is non-focusIssue generated from Tuleap's migration script.
**Originally submitted by: Hugo Lefeuvre (hle)**
'Download folder' dialog in General Preferences has undefined name and is non-focus.
\* Reproduce steps:
1) Open General Preferen...Issue generated from Tuleap's migration script.
**Originally submitted by: Hugo Lefeuvre (hle)**
'Download folder' dialog in General Preferences has undefined name and is non-focus.
\* Reproduce steps:
1) Open General Preferences
2) Click on the 'Download folder' file chooser and select 'Other...'
3) This opens a file chooser dialog which is non focus, that is you can interact normally with the main window, e.g. close it or quit preferences.
4) This dialog is also unnamed. If your WM doesn't display dialog names by default, try to put it in fullscreen mode.
A non focus dialog might be confusing for the end user.
The undefined name is a purely aesthetic issue.https://git.jami.net/savoirfairelinux/jami-client-gnome/-/issues/726Preferences remain open when client goes in background2018-05-22T00:48:09ZJami BotPreferences remain open when client goes in backgroundIssue generated from Tuleap's migration script.
**Originally submitted by: Hugo Lefeuvre (hle)**
Whenever the preferences are open and the Ring window is closed (that is the client
enters in background state ?), preferences remain ope...Issue generated from Tuleap's migration script.
**Originally submitted by: Hugo Lefeuvre (hle)**
Whenever the preferences are open and the Ring window is closed (that is the client
enters in background state ?), preferences remain open. This is annoying in the case
where the user was in the Media Preferences with Camera preview: In this case the
daemon continues to record the user, thus letting the web cam led on, potentially
giving the user the impression to be "observed".
\* Reproduce steps:
1) Open Ring
2) Go to Media Preferences
3) If preview is activated (which, I guess, is almost always the case) your web cam led should be on
4) Close the Ring window. The daemon is still recording because the camera led is still on.
Fix: Preferences should be closed when the Ring window is closed.https://git.jami.net/savoirfairelinux/jami-client-gnome/-/issues/725Frame rate field in Media preferences is not sorted / contains duplicates2018-05-22T00:48:00ZJami BotFrame rate field in Media preferences is not sorted / contains duplicatesIssue generated from Tuleap's migration script.
**Originally submitted by: Hugo Lefeuvre (hle)**
The Frame rate field in Media preferences is not sorted and contains duplicates.
This may be confusing for the user.
I expect it ...Issue generated from Tuleap's migration script.
**Originally submitted by: Hugo Lefeuvre (hle)**
The Frame rate field in Media preferences is not sorted and contains duplicates.
This may be confusing for the user.
I expect it to be sorted (increased/decreasing order) and deduplicated.https://git.jami.net/savoirfairelinux/jami-client-gnome/-/issues/785[GNOME] Update Account drop-down2018-07-06T16:00:15ZJami Bot[GNOME] Update Account drop-downIssue generated from Tuleap's migration script.
**Originally submitted by: Óvári (ovari)**
[GNOME] Update Account drop-down
When more than one (RING and/or SIP) account, there is a drop-down to enable selecting the desired account....Issue generated from Tuleap's migration script.
**Originally submitted by: Óvári (ovari)**
[GNOME] Update Account drop-down
When more than one (RING and/or SIP) account, there is a drop-down to enable selecting the desired account.
Steps:
1. Settings → Accounts → Rename ‘Alias’ field
2. Click ‘Settings’ (which looks like a tick)
Please update the Account drop-down to show the updated ‘Alias’ field. The attached imaged shows account “New Account” which has not been updated after a change in the ‘Alias’ field.
Thank you
ring-gnome 2018-03-23 23:25:11 UTC
Linux Mint 18.3 Cinnamon 64-bitGnome 2018.07.15Sébastien BlinSébastien Blinhttps://git.jami.net/savoirfairelinux/jami-client-gnome/-/issues/721client crashes when entering nickname2018-05-22T00:47:18ZJami Botclient crashes when entering nicknameIssue generated from Tuleap's migration script.
**Originally submitted by: Jean-Charles Malahieude (lilyfan)**
A detailed description of the bug.
\* Environment:
Fedora 27, Gnome, ring-20180323.1.cbff567
uname -r : 4.15.10-300....Issue generated from Tuleap's migration script.
**Originally submitted by: Jean-Charles Malahieude (lilyfan)**
A detailed description of the bug.
\* Environment:
Fedora 27, Gnome, ring-20180323.1.cbff567
uname -r : 4.15.10-300.fc27.x86\_64
\* Reproduce steps:
Launch Ring for the first time
Select <Create a Ring account>
Fill in "full name" field
Typing any character in the "Register name publicly" field crashes the window.
\* Expected result:
Let me fill in the field and the next ones
\* Actual result:
Client crashes, deamon still running.
Must kill dring and gnome-ring before running again in order to have the camera active.https://git.jami.net/savoirfairelinux/jami-client-gnome/-/issues/718Bad dark theme handling2019-11-12T14:41:54ZJami BotBad dark theme handlingIssue generated from Tuleap's migration script.
**Originally submitted by: Sébastien Blin (sblin)**
\* Environment:
Gnome client
Arc-Dark or other dark themes
\* Reproduce steps:
Open the client
\* Expected result:
The...Issue generated from Tuleap's migration script.
**Originally submitted by: Sébastien Blin (sblin)**
\* Environment:
Gnome client
Arc-Dark or other dark themes
\* Reproduce steps:
Open the client
\* Expected result:
The theme should be good looking
\* Actual result:
Some icons are dark on dark, some buttons are white. The chatview doesn't look goodhttps://git.jami.net/savoirfairelinux/jami-client-gnome/-/issues/783[GNOME] Repository is not signed2018-05-24T12:12:19ZJami Bot[GNOME] Repository is not signedIssue generated from Tuleap's migration script.
**Originally submitted by: Óvári (ovari)**
OS: Linux Mint 18.3 Cinnamon 64-bit
https://ring.cx/en/download/gnu-linux
Ubuntu 16.04
In the terminal:
$ sudo apt-get update && su...Issue generated from Tuleap's migration script.
**Originally submitted by: Óvári (ovari)**
OS: Linux Mint 18.3 Cinnamon 64-bit
https://ring.cx/en/download/gnu-linux
Ubuntu 16.04
In the terminal:
$ sudo apt-get update && sudo apt-get install ring
Output:
W: GPG error: https://dl.ring.cx/ring-nightly/ubuntu\_16.04 ring InRelease: The following signatures couldn't be verified because the public key is not available: NO\_PUBKEY 64CD5...
W: The repository 'https://dl.ring.cx/ring-nightly/ubuntu\_16.04 ring InRelease' is not signed.
N: Data from such a repository can't be authenticated and is therefore potentially dangerous to use.
N: See apt-secure(8) manpage for repository creation and user configuration details.
Removed, please advise if you need the complete key: 64CD5...
Thank you
![Summary](/uploads/b01cc3ca2dc215377df09baab33a175c/Summary.png)https://git.jami.net/savoirfairelinux/jami-client-gnome/-/issues/782[GNOME] PPA and Flatpak2018-05-23T01:56:21ZJami Bot[GNOME] PPA and FlatpakIssue generated from Tuleap's migration script.
**Originally submitted by: Óvári (ovari)**
A detailed description of the bug. Use following fields for description field:
\* Environment:
Linux Mint 18.3 Cinnamon 64-bit
\* Rep...Issue generated from Tuleap's migration script.
**Originally submitted by: Óvári (ovari)**
A detailed description of the bug. Use following fields for description field:
\* Environment:
Linux Mint 18.3 Cinnamon 64-bit
\* Reproduce steps:
1. ring-gnome via PPA has been installed previously using:
https://ring.cx/en/download/gnu-linux
2. Installed ring-flatpak using Linux Mint's "Software Manager"
3. Ring is shown in the Linux Mint menu twice. One for the PPA version and one for the Flatpak version. The name and description are the same.
4. Tried to open Ring using the menu and Error dialog appears.
\* Expected result:
Ring should open
\* Actual result:
Ring not opening and error dialog show.
The "Error:" is either missing or garbled in the Error dialog box.
![ring-flatpak](/uploads/09b0e99cf127276a38fd135d96613649/ring-flatpak.png)
![ring-gnome](/uploads/2fb53b2ddeb937c664d337455d6e0ba0/ring-gnome.png)https://git.jami.net/savoirfairelinux/jami-client-gnome/-/issues/715[GNOME] Ring Flatpak2018-05-22T00:45:51ZJami Bot[GNOME] Ring FlatpakIssue generated from Tuleap's migration script.
**Originally submitted by: Óvári (ovari)**
Please package the ring-gnome client in Flatpak format and provide them on FlatHub.
https://flathub.org/apps/
For example, LibreOffice is ...Issue generated from Tuleap's migration script.
**Originally submitted by: Óvári (ovari)**
Please package the ring-gnome client in Flatpak format and provide them on FlatHub.
https://flathub.org/apps/
For example, LibreOffice is available in Flatpak format:
https://www.libreoffice.org/download/flatpak/
Please scroll down to the heading "Flatpak" at:
https://blog.linuxmint.com/?p=3418
to read more background information.
It will also give more exposure (advertising, marketing) to your project.
Linux Mint has Flatpak available in the default installation.
Not sure if the Severity for this artifact should be higher than "1 - Ordinary" due to Ubuntu is no longer packaging PPAs, which seems to be the current method of packaging Ring on GNU/Linux.
What do you think?
Thank youhttps://git.jami.net/savoirfairelinux/jami-client-gnome/-/issues/781webview messages clipping2018-05-23T01:55:21ZJami Botwebview messages clippingIssue generated from Tuleap's migration script.
**Originally submitted by: Sébastien Blin (sblin)**
\* Environment:
Fedora 27 only?
\* Reproduce steps:
send messages to the conversations
\* Expected result:
messages shou...Issue generated from Tuleap's migration script.
**Originally submitted by: Sébastien Blin (sblin)**
\* Environment:
Fedora 27 only?
\* Reproduce steps:
send messages to the conversations
\* Expected result:
messages should be correctly shown
\* Actual result:
sometimes we can have some clipping
![clipping](/uploads/8022bef93688a8c3e668b79e55d4a3da/clipping.png)https://git.jami.net/savoirfairelinux/jami-client-gnome/-/issues/708Gnome client UI resets to main screen when account connection is re-established2018-07-17T16:43:36ZJami BotGnome client UI resets to main screen when account connection is re-establishedIssue generated from Tuleap's migration script.
**Originally submitted by: Maxim Cournoyer (mcournoyer)**
A detailed description of the bug. Use following fields for description field:
\* Environment:
Any recent Gnome client (ver...Issue generated from Tuleap's migration script.
**Originally submitted by: Maxim Cournoyer (mcournoyer)**
A detailed description of the bug. Use following fields for description field:
\* Environment:
Any recent Gnome client (version tested: built from sources as of 2018-02-08)
\* Reproduce steps:
1. Open the Gnome client.
2. Enter or create a new chat conversation.
3. Manually disconnect then connect again the network (use the Ethernet cable, the Wi-Fi killswitch, etc.)
4. Notice that when daemon notices about the disconnection, the client redraws its UI to show the main screen and the user is kicked out of its current conversation view.
\* Expected result:
The view should be maintained to the current conversation. If the network problem persists (after a threshold of say, 5 seconds), a visual hint should notify the user that there is currently no connectivity.
\* Actual result:
The user is disoriented/confused since the UI changes under their feet without any action on their part.Next major releaseHugo LefeuvreHugo Lefeuvre