@Staudey 10901 is also evenly divisible by 11, and both the version and diff start and end with 1.

Notes on the new Budgie sync for those testing this upgrade:

• If you notice the Budgie panel crashing at any point (which can be either restarting or vanishing entirely), report it with any journalctl logs from budgie-panel from the time of the crash.
• If you use the existing "Disable Night Light mode when windows are fullscreen" or the new "Pause notifications when windows are fullscreen" settings, please report if you find an application that does not properly trigger either of these.

If you encounter these issues, report them on the Budgie issue tracker. They are unlikely to be Solus-specific.

It can install VMM? Well, it's got my vote!

@akrenz It actually broke with commit https://dev.getsol.us/R4992:9a0facf8e6aa47f6b7fb61f8ce388afbbd9bfa0a, not the most recent one. Anyway, D10859 fixes it on my system, so just waiting for it to be accepted and committed.

Seems like this is a known issue with JavaFX 11. I'm not sure why it only manifested with the mentioned commit, but in any case, I'm working on a fix. It should also resolve the issues people are having with bisq.

Build with Gradle wrapper

No daemon

Use Gradle wrapper and update to v1.4.32

LGTM, but still up to core team review. Also, if you're up for maintaining Maven, be my guest—I don't actively use it myself.

My understanding of the situation follows. I may have gotten some bits wrong, so feel free to correct me.

Done. Awaiting review.

Replaces beignet

Fix icd path

I don't think this is really accurate. I do think the change is correct, but the commit message suggests that you might have made the right change for the wrong reasons.

Fix description

Now working on this. @joebonrichie and I will co-maintain Neo, as he's more experienced than I am but lacks the ability to test the software. To do, in order:

In T9406#182842, @Staudey wrote:

@serebit Could it be that bubblewrap is/was not installed on your machine, but flatpak is? In that case the Steam runtime will use flatpak-bwrap instead, which isn't setuid and therefore works (as I saw in testing when replacing bwrap by a script and forgetting to set chmod +x)

Hey, just chiming in, I've mentioned myself in the thread that I wasn't having the issue when this was created. I still haven't had this issue. Given the activity from smcv and Staudey over the last few days, both here and on the steam-runtime GitHub, it's safe to assume that a workaround would've been pushed by next stable sync even if your article hadn't been published. In addition, you probably shouldn't take too much credit, given that the only reason any of us even saw your article was because someone with far more reach to Linux users than you (who doesn't even *use* Solus) pointed it out to me in another forum, calling it out for how ridiculous and childish it was.

Any update on this, @egee-irl / @Staudey / @ekianjo? There have been a few iterations on pressure-vessel and Proton since this issue was created. If the Flatpak version of Steam can't launch Proton 5.13, then that's an upstream issue according to @smcv (who is apparently from Collabora! Neat), but if our native Steam package can't launch Proton 5.13 on some systems then this warrants further investigation. Like smcv said, a backtrace would be helpful.

Use our Gradle and enable teamcity build

Those are some very strange terms...

Tarballs now being published as of December.

Enable compiler2 and tiered compilation, increase code cache size

@DataDrake Done. Still doesn't seem to match P14, but it's much closer.

Rebuild with updated system libraries