You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Upon enabling this extension I noticed the moving text is stale, i.e. the marquee in the top pane. It shows the correct text, but it does not move. And yes, “display mode” is set to “marquee”.
I run Gnome 44.2, on Ubuntu 23.10, with X11.
Note that your code says it should be version 21, yet the installed extension reports version 22.
From journalctl I got
Spotify appeared on DBus.
ncspot vanished from DBus.
meta_window_set_stack_position_no_sync: assertion 'window->stack_position >= 0' failed
The last entry is probably something else, it pops up even if the extension isn't enabled.
Seems like the code does what it is supposed to do, but on smaller screens the label widget will be truncated, thus the marquee text will not move because the actual text is shorter than the given marquee length. Still the width of the label widget is to short to accommodate the full text, so it becomes visually truncated and does not scroll.
Let me see if I've understood it correctly. When the marquee length is set to a value larger than the max possible width of the label, and the label text is too short to trigger a marquee but still long enough to get automatically truncated by the panel, you end up with a truncated static text. Does that sound about right?
Upon enabling this extension I noticed the moving text is stale, i.e. the marquee in the top pane. It shows the correct text, but it does not move. And yes, “display mode” is set to “marquee”.
I run Gnome 44.2, on Ubuntu 23.10, with X11.
Note that your code says it should be version 21, yet the installed extension reports version 22.
From journalctl I got
The last entry is probably something else, it pops up even if the extension isn't enabled.
I use the ordinary client from Spotify.
This bug has been previously reported at Gnome Extensions
The text was updated successfully, but these errors were encountered: