Known issue, reported on the old solus-sc tracker (we have a new repo at https://github.com/getsolus/solus-sc). Issues should be filed there, not here, until I've fully moved the project over to Phabricator and we have the tooling in place to facilitate its development.

NodeJS is a dependency of VSCODE when installing it, as far as why I don’t really know.

Should be filed at https://github.com/getsolus/3rd-party as this is simply an issue witha new Chrome being available and 3rd-party not being updated yet. Maybe @Staudey can take a look.

Yea, I'll kill it.

@DataDrake We should probably nuke R2602 python-ipaddr as well. No reverse dependencies and last item was R3132:2fc577ab5f1368f8a04be47cabf341c5dffb8259

Closing due to lack of response.

In case you want to land this yourself, might want to amend the commit message. Also be sure to rebuild qtox against this.

Abandoning due to lack of action.

Upstream didn't provide any changelog, but I did quickly notice that the ugly artifacts and flickers were gone from the boot of my KDE Plasma computer.

I'm having no issues building Budgie against newer meson. I'd recommend checking your meson.build instead.

Can confirm it works as expected. @kyrios123 Let's get this added to the Desktop Actions in files/firefox.desktop for your 64.0 patch.

Why is Debian being referenced, especially when they haven't updated theirs since 2012 and it is not really relevant? Is the one provided by fesch a fork?

We have gnome-pomodoro in the repo, which isn't a GNOME extension, but rather an application. What does tomate-gtk do that GNOME Pomodoro doesn't?

Issue report stated 1.4.8 should resolve the issue, 1.5.0 is now in unstable. Frankly, if it continues to be an issue, prod upstream, nothing I can do about it.

I'll get the langpacks on the server when I wake up.

Unfortunately it does not appear that --new-tab in fact opens up a new tab, at least in 63.0.3-145, whether it's using --new-window to open up the instance or not.

Lightzone was dropped a long while ago from our repos (T5629) but not entirely sure the reasoning. Maybe @Justin would know seeing as he was the maintainer of it.