jami-client-gnome issueshttps://git.jami.net/savoirfairelinux/jami-client-gnome/-/issues2018-07-12T19:55:49Zhttps://git.jami.net/savoirfairelinux/jami-client-gnome/-/issues/864"Account exported!" not switching back to "Export account"2018-07-12T19:55:49ZPhilippe Gorley"Account exported!" not switching back to "Export account"Steps:
1. Create 2 accounts
2. Go to settings and click "Export account"
3. Switch accounts
Expected result: button shows "Export account"
Actual result: button shows "Account exported!"Steps:
1. Create 2 accounts
2. Go to settings and click "Export account"
3. Switch accounts
Expected result: button shows "Export account"
Actual result: button shows "Account exported!"Gnome 2018.07.15Sébastien BlinSébastien Blinhttps://git.jami.net/savoirfairelinux/jami-client-gnome/-/issues/862chatview: duplicate retry entry in dropdown menu2018-07-12T21:03:31ZHugo Lefeuvrechatview: duplicate retry entry in dropdown menu**How to reproduce**:
1. Select a file to transfer and wait until the file transfer object reaches the awaiting peer state
2. Cancel the file transfer before peer accepted it
3. The dropdown menu now contains two retry entries**How to reproduce**:
1. Select a file to transfer and wait until the file transfer object reaches the awaiting peer state
2. Cancel the file transfer before peer accepted it
3. The dropdown menu now contains two retry entriesGnome 2018.07.15Hugo LefeuvreHugo Lefeuvrehttps://git.jami.net/savoirfairelinux/jami-client-gnome/-/issues/861chatview: dropdown menu does not always appear when clicking the ellipsis2018-07-12T21:03:39ZHugo Lefeuvrechatview: dropdown menu does not always appear when clicking the ellipsisSometimes the ellipsis does not trigger the delete dropdown menu when clicked.
**How to reproduce**: Does not always happen, pretty much non-deterministic. Certain images are especially prone to trigger this bug when present in the chat...Sometimes the ellipsis does not trigger the delete dropdown menu when clicked.
**How to reproduce**: Does not always happen, pretty much non-deterministic. Certain images are especially prone to trigger this bug when present in the chatview, but still it's hard to tell what happens exactly.
My best guess is that WebKit can't handle the dropdown menu in all cases because it's a bit hacky, and we'll have to rewrite it with less js.Gnome 2018.07.15Hugo LefeuvreHugo Lefeuvrehttps://git.jami.net/savoirfairelinux/jami-client-gnome/-/issues/860Cannot link new devices - Bad Password2018-07-10T14:22:02Zsteve harrissCannot link new devices - Bad PasswordI have a Linux Mint 4.15.0-24-generic #26~16.04.1-Ubuntu SMP Fri Jun 15 14:35:08 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux. Using "In varietate concordia" built on 2018-07-07 17:49:35 UTC. I cannot link my accounts because I get a 'Bad Pas...I have a Linux Mint 4.15.0-24-generic #26~16.04.1-Ubuntu SMP Fri Jun 15 14:35:08 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux. Using "In varietate concordia" built on 2018-07-07 17:49:35 UTC. I cannot link my accounts because I get a 'Bad Password' error on clicking 'Export on the Ring'. I tried creating a new account in case I had miss-entered my original account password but with the same result.Gnome 2018.07.15Sébastien BlinSébastien Blinhttps://git.jami.net/savoirfairelinux/jami-client-gnome/-/issues/852There is no visual congruence between Settings icons2018-07-13T15:57:10ZannaThere is no visual congruence between Settings iconsIn the main window you can see a gear to enter the settings.
In the settings view you can see a check mark to get back to the main window.
Both buttons are labeled "Settings".
For me this seens to be - visually and logically - a huge ...In the main window you can see a gear to enter the settings.
In the settings view you can see a check mark to get back to the main window.
Both buttons are labeled "Settings".
For me this seens to be - visually and logically - a huge gap for users.
Any ideas to make it more congruent? E.g. an arrow button that indicates back to main window? ...Gnome 2018.07.15https://git.jami.net/savoirfairelinux/jami-client-gnome/-/issues/851Switching accounts when entering and exiting settings2018-07-10T14:21:33ZPhilippe GorleySwitching accounts when entering and exiting settingsSteps:
1. Create 2 accounts
2. Disable the second one (bottom one in account selector in the top right)
3. Select the disable account in the main window
4. Enter settings view
Expected result: entering settings view with the disabled ac...Steps:
1. Create 2 accounts
2. Disable the second one (bottom one in account selector in the top right)
3. Select the disable account in the main window
4. Enter settings view
Expected result: entering settings view with the disabled account selected
Actual result: entering settings view but account is switched to the enabled oneGnome 2018.07.15Sébastien BlinSébastien Blinhttps://git.jami.net/savoirfairelinux/jami-client-gnome/-/issues/849chatview: missing images are badly handled2018-07-12T21:03:46ZHugo Lefeuvrechatview: missing images are badly handled**How to reproduce**:
1. User A sends an image to user B
2. User B receives the image and the chatview displays it successfully
3. For some reason the image is deleted from user B's filesystem
4. Whenever User B tries to display the conv...**How to reproduce**:
1. User A sends an image to user B
2. User B receives the image and the chatview displays it successfully
3. For some reason the image is deleted from user B's filesystem
4. Whenever User B tries to display the conversation, the chatview now displays a white hole and the js logs report various resource access errors
**What should happen**: Instead of trying to display the broken/missing image we should display the usual file transfer canvas. We used to have some code for doing that but it is now broken and should be repared.Gnome 2018.07.15Hugo LefeuvreHugo Lefeuvrehttps://git.jami.net/savoirfairelinux/jami-client-gnome/-/issues/848smartlist: invitation tab disappears when switching account2018-07-09T13:56:17ZHugo Lefeuvresmartlist: invitation tab disappears when switching accountGNU/Linux GNOME client, latest master.
**How to reproduce:**
You need a client with at least two accounts A and B. First account is A.
1. Using a third account C on another device, send an invitation to B.
2. Make sure invitation arri...GNU/Linux GNOME client, latest master.
**How to reproduce:**
You need a client with at least two accounts A and B. First account is A.
1. Using a third account C on another device, send an invitation to B.
2. Make sure invitation arrived.
3. Switch to account A.
4. Switch back to account B. Now the invitation tab does not appear anymore. Instead you will only see a fat, ugly conversations tab.
Note: The invitation tab pops back when using the search bar.Gnome 2018.07.15Sébastien BlinSébastien Blinhttps://git.jami.net/savoirfairelinux/jami-client-gnome/-/issues/845chatview: message bar blocked at bigger size when sending empty messages2018-07-12T21:03:54ZHugo Lefeuvrechatview: message bar blocked at bigger size when sending empty messages**How to reproduce:**
1. Open conversation
2. In the message bar, type SHIFT+ENTER multiple times. This will make the message bar's height bigger and create and empty message
3. Click "send"
4. Message bar is now blocked at bigger size,...**How to reproduce:**
1. Open conversation
2. In the message bar, type SHIFT+ENTER multiple times. This will make the message bar's height bigger and create and empty message
3. Click "send"
4. Message bar is now blocked at bigger size, regardless of the conversation
**Expected:** Size of the message bar is reset-ed after empty message was sent.Gnome 2018.07.15https://git.jami.net/savoirfairelinux/jami-client-gnome/-/issues/843chatview: invitation text is not selectable2018-07-12T21:04:01ZHugo Lefeuvrechatview: invitation text is not selectableThe invitation text in the chatview is not selectable. This is very annoying if one wants to copy and ringID for example.
This is an easy bug. Simply fix the CSS.The invitation text in the chatview is not selectable. This is very annoying if one wants to copy and ringID for example.
This is an easy bug. Simply fix the CSS.Gnome 2018.07.15https://git.jami.net/savoirfairelinux/jami-client-gnome/-/issues/839chatview: navbar glitch during call2018-07-12T21:04:09ZHugo Lefeuvrechatview: navbar glitch during callDuring a call the navbar should not appear, that is it should be `display: none`. Currently it is `visibility: hidden` which means it appears on screen, as a 'hole'. This should be fixed before the next release.During a call the navbar should not appear, that is it should be `display: none`. Currently it is `visibility: hidden` which means it appears on screen, as a 'hole'. This should be fixed before the next release.Gnome 2018.07.15Hugo LefeuvreHugo Lefeuvrehttps://git.jami.net/savoirfairelinux/jami-client-gnome/-/issues/838chatview: navbar present during call if peer sends a message2018-07-12T21:04:38ZHugo Lefeuvrechatview: navbar present during call if peer sends a message**How to reproduce:**
1. User A (any client) calls user B (GNU/Linux GNOME client, latest master)
2. User B accepts the call. User A and B are now able to communicate
3. At some point user A sends a message to user B
4. User B receives t...**How to reproduce:**
1. User A (any client) calls user B (GNU/Linux GNOME client, latest master)
2. User B accepts the call. User A and B are now able to communicate
3. At some point user A sends a message to user B
4. User B receives the message and the chatview pops at the right side of the screen.
* First bug: The chatview has a navbar and it should not.
* Second bug: Received message is not present.
![screenshot-2018-07-03-17-43-44](/uploads/2714c60d103a7b4ca1ac477ac0854bc5/screenshot-2018-07-03-17-43-44.png)Gnome 2018.07.15https://git.jami.net/savoirfairelinux/jami-client-gnome/-/issues/837Migrate Migration view to new LRC models2018-07-10T14:33:04ZSébastien BlinMigrate Migration view to new LRC modelsmigrationview still uses old LRC models. So we need to rewrite related files.migrationview still uses old LRC models. So we need to rewrite related files.Gnome 2018.07.15Sébastien BlinSébastien Blinhttps://git.jami.net/savoirfairelinux/jami-client-gnome/-/issues/836chatview: remove conversation loading animation2018-07-05T15:03:46ZHugo Lefeuvrechatview: remove conversation loading animationThe conversation loading animation doesn't really improve UX, yet it is a perf issue.
Also, it looks ugly. We should get rid of it.The conversation loading animation doesn't really improve UX, yet it is a perf issue.
Also, it looks ugly. We should get rid of it.Gnome 2018.07.15Hugo LefeuvreHugo Lefeuvrehttps://git.jami.net/savoirfairelinux/jami-client-gnome/-/issues/833chatview: major efficiency issues in updateTimestamps2018-07-12T21:04:25ZHugo Lefeuvrechatview: major efficiency issues in updateTimestamps`updateTimestamps()` is affected by several design issues with a large drawbacks on performances:
1. This function goes through all timestamp entries and is called by `addOrUpdateMessage()`. This means that this function is called **eac...`updateTimestamps()` is affected by several design issues with a large drawbacks on performances:
1. This function goes through all timestamp entries and is called by `addOrUpdateMessage()`. This means that this function is called **each and every time a message is displayed** ! This is basically O(n²) algorithm. For instance, displaying 50 messages triggers 1275 timestamp updates.
2. This function handles both text and **position/style updates**. The is probably done in order to simulate some kind of responsive behaviour. This should be done by CSS, not JS.Gnome 2018.07.15Hugo LefeuvreHugo Lefeuvrehttps://git.jami.net/savoirfairelinux/jami-client-gnome/-/issues/805Allow Settings view to be closed without saving2018-07-06T19:47:32ZannaAllow Settings view to be closed without savingand without closing the whole window. For now it's only possible to tick the check mark here.
Closing should bring a user back to the main window.
Another way is to give client the functionality that changes are always saved
e.g. see h...and without closing the whole window. For now it's only possible to tick the check mark here.
Closing should bring a user back to the main window.
Another way is to give client the functionality that changes are always saved
e.g. see https://elementary.io/docs/human-interface-guidelines#always-saved
But then an providing an Undo would make sense as well savoirfairelinux/ring-client-gnome#806
What do you think?Gnome 2018.07.15Sébastien BlinSébastien Blinhttps://git.jami.net/savoirfairelinux/jami-client-gnome/-/issues/802One avatar/display name by account, not general2018-07-06T15:55:29ZSébastien BlinOne avatar/display name by account, not generalDepends on #791Depends on #791Gnome 2018.07.15Sébastien BlinSébastien Blinhttps://git.jami.net/savoirfairelinux/jami-client-gnome/-/issues/796Add repo for Fedora 282018-06-12T21:18:23ZSébastien BlinAdd repo for Fedora 28For now, Ring is not available for Fedora 28.For now, Ring is not available for Fedora 28.Gnome 2018.07.15Sébastien BlinSébastien Blinhttps://git.jami.net/savoirfairelinux/jami-client-gnome/-/issues/791Rework the Accounts settings page2018-10-16T23:00:46ZSébastien BlinRework the Accounts settings pageThe current settings page is bad and miss some functionnalities.
This is the current POC: (https://gerrit-ring.savoirfairelinux.com/#/c/9453/)
![1527364752_1559_26052018_](/uploads/7369beba7740e4db2a21a877d60515d6/1527364752_1559_260520...The current settings page is bad and miss some functionnalities.
This is the current POC: (https://gerrit-ring.savoirfairelinux.com/#/c/9453/)
![1527364752_1559_26052018_](/uploads/7369beba7740e4db2a21a877d60515d6/1527364752_1559_26052018_.png)
![1527364756_1559_26052018_](/uploads/6beed4b84318e1d049711fe35af808b4/1527364756_1559_26052018_.png)Gnome 2018.07.15Sébastien BlinSébastien Blinhttps://git.jami.net/savoirfairelinux/jami-client-gnome/-/issues/733[GNOME] Ring terminates when making an intercom call2018-07-10T13:33:40ZJami Bot[GNOME] Ring terminates when making an intercom callIssue 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. Click “Settings...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. Click “Settings”
2. Click “Accounts” tab
3. Click on Ring “Account”
4. Click “General” tab
5. Right-click on RingID field, select “Select All”
6. Right-click on RingID field, select “Copy”
7. Click “Settings”
8. Right-click on “Search contacts or enter number”, select “Paste”
9. Click on contact/conversation
10. Click on icon in top far right tool-tip “Place call” or “Place audio-only call”. Ring window disappears and Ring icon in the System tray disappears. Has Ring terminated?
\* Expected result:
Ring should try to connect the call.
\* Actual result:
Ring window disappears and Ring icon in the System tray disappears when making an intercom call. Seems like Ring terminated.
Thank you
Xref
bug \#1700 - [GNOME] Three computers in audio conference call (no video) with 2 unique usernames not working
https://tuleap.ring.cx/plugins/tracker/?aid=1700Gnome 2018.07.15Sébastien BlinSébastien Blin