polari issueshttps://gitlab.gnome.org/GNOME/polari/-/issues2022-09-20T08:26:07Zhttps://gitlab.gnome.org/GNOME/polari/-/issues/168polari drops certain chat messages2022-09-20T08:26:07ZMichael Catanzaropolari drops certain chat messagesI don't know of any way to reproduce this, but sometimes polari drops chat messages sent to me. The unlucky dropped message appears only in the GNOME Shell notification but not polari's chat window. This makes it impossible to see the me...I don't know of any way to reproduce this, but sometimes polari drops chat messages sent to me. The unlucky dropped message appears only in the GNOME Shell notification but not polari's chat window. This makes it impossible to see the message after the GNOME Shell notification disappears. It's frustrating because notifications are nowadays only visible for a few seconds.
When this happens, the messages sent before and after appear normally in polari. Only one particular seemingly-random dropped message will be missing from the conversation.https://gitlab.gnome.org/GNOME/polari/-/issues/148Attempting to run a JS callback during garbage collection. This is most likel...2023-02-03T00:13:37ZMichael CatanzaroAttempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), , dispose(), or remove() vfuncs.Earlier today, polari spammed my system journal with approximately 2 million lines of:
> Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy si...Earlier today, polari spammed my system journal with approximately 2 million lines of:
> Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked.
> The offending callback was SourceFunc().
I'm not sure how to reproduce this. I only noticed it in my journal after the spam had already finished.https://gitlab.gnome.org/GNOME/polari/-/issues/106Difficult to bypass polari setup wizard when network is already configured2019-09-01T17:11:38ZMichael CatanzaroDifficult to bypass polari setup wizard when network is already configuredWhenever I reinstall my travel laptop, I notice the same difficulty when starting polari for the first time on the new computer. Here is what I saw a couple weeks ago when preparing for GUADEC:
![polari-first-run-broken](/uploads/a8291d...Whenever I reinstall my travel laptop, I notice the same difficulty when starting polari for the first time on the new computer. Here is what I saw a couple weeks ago when preparing for GUADEC:
![polari-first-run-broken](/uploads/a8291d72038a72c541b3be22edcdad84/polari-first-run-broken.png)
To get past this screen, I have to select a network to add. The only network that I want to add is GNOME. But GNOME is already added (because I have copied my homedir to the travel laptop from my main workstation). So I have to add another network that I don't actually want in order to bypass this initial setup wizard.
It'd be good to skip this page entirely if I already have a network added.https://gitlab.gnome.org/GNOME/polari/-/issues/59Support for irc.gitter.im2019-04-14T13:51:14ZJan Niklas HasseSupport for irc.gitter.imI've tried to use Polari to connect to Gitter via https://irc.gitter.im/. When connecting I'm asked for a server password where I entered the token. After that I can connect to my channels, but not talk in them (input field is grayed out...I've tried to use Polari to connect to Gitter via https://irc.gitter.im/. When connecting I'm asked for a server password where I entered the token. After that I can connect to my channels, but not talk in them (input field is grayed out).
It works in HexChat. Is there any setting I've missed?https://gitlab.gnome.org/GNOME/polari/-/issues/51Trying to join an unlisted room is a PITA with a slow-loading room list2023-10-26T21:46:19ZGNTrying to join an unlisted room is a PITA with a slow-loading room listIf a room's unlisted on a server (e.g. "someroom"), Polari adds an entry for it at the bottom of the room list.
However, if the room list is slowly loading and adding items, if the user scrolls to the bottom of the list to tick the "som...If a room's unlisted on a server (e.g. "someroom"), Polari adds an entry for it at the bottom of the room list.
However, if the room list is slowly loading and adding items, if the user scrolls to the bottom of the list to tick the "someroom" item, it can get repeatedly and almost immediately pushed down below the visible area by additional discovered rooms as they're added.
And this will happen repeatedly until the list is fully populated.
This is especially annoying on a trackpad, since scrolling and moving the cursor are mutually exclusive actions, and so it's not possible to reliably scroll+position+tick fast enough to work around this.
Three options for fixing this would be:
* Move the automatic item to the top
* "Stick" the scroll to the bottom is scrolled all the way down (so new items would push up the items above it, rather than push down those below it
* Separate the automatic item entirely from the scrolling list (could be at the bottom, without any grey space between it and the list, but with a thicker version of the list item dividing line, for example)https://gitlab.gnome.org/GNOME/polari/-/issues/26Selecting rooms in join dialog needs double click while loading2020-12-08T11:23:07ZFlorian Müllnerfmuellner@gnome.orgSelecting rooms in join dialog needs double click while loadingThe TreeView in the join dialog is set to activate rows on single-click, however for whatever reason that only works once loading has finished. As long as we are still inserting pending room infos, activating a row requires a double-clic...The TreeView in the join dialog is set to activate rows on single-click, however for whatever reason that only works once loading has finished. As long as we are still inserting pending room infos, activating a row requires a double-click.
According to `log()`, it's the ::row-activated signal itself that only gets emitted after a double-click, not our handler that somehow mixes up state, so this could actually be a GTK+ issue.
Selecting rows via the keyboard is not affected.https://gitlab.gnome.org/GNOME/polari/-/issues/19Polari does not ask to unlock keyring, it just will not login accounts at all2021-05-25T11:56:14ZFlorian Müllnerfmuellner@gnome.orgPolari does not ask to unlock keyring, it just will not login accounts at allF. [wrote](https://bugzilla.gnome.org/show_bug.cgi?id=776566):
> Polari seems to not ask to unlock the keyring in which passwords are stored like for example Evolution does.
>
> This will result in no remember nickserv identifications to...F. [wrote](https://bugzilla.gnome.org/show_bug.cgi?id=776566):
> Polari seems to not ask to unlock the keyring in which passwords are stored like for example Evolution does.
>
> This will result in no remember nickserv identifications to be performed which is a bother.
>
> Right now I just open something else like Evolution to unlock it, and then I open Polari.https://gitlab.gnome.org/GNOME/polari/-/issues/10The timestamps without dates are useless2023-03-17T16:43:19ZGhost UserThe timestamps without dates are uselessOn the following SS, there are times:
![Snímek_z_2017-10-18_11-07-48](/uploads/8dde33e740dbcfef26b40367b60caa71/Snímek_z_2017-10-18_11-07-48.png)
But without any possibility to display date alongside the time, they are pretty useless. ...On the following SS, there are times:
![Snímek_z_2017-10-18_11-07-48](/uploads/8dde33e740dbcfef26b40367b60caa71/Snímek_z_2017-10-18_11-07-48.png)
But without any possibility to display date alongside the time, they are pretty useless. Please display the date along the time or in tooltip or something along the lines.