If you want to maintain this, you can. You likely use it more frequently than I do anyway :p

wait why me

Crashing for me as well, though I don't have any debugging to show from before the May 12 poppler upgrade. Here's what lldb says:

serebit@serebit-sagan ~ $ lldb evince Downloads/TEXTBOOK.pdf 
(lldb) target create "evince"
Current executable set to 'evince' (x86_64).
(lldb) settings set -- target.run-args  "Downloads/TEXTBOOK.pdf"
(lldb) run
Process 29835 launched: '/usr/bin/evince' (x86_64)
Process 29835 stopped
* thread #8, name = 'EvJobScheduler', stop reason = signal SIGSEGV: invalid address (fault address: 0x225)
    frame #0: 0x00007ffff7385bb3 libcairo.so.2`cairo_surface_destroy + 115
libcairo.so.2`cairo_surface_destroy:
->  0x7ffff7385bb3 <+115>: movq   (%rbx), %rbx
    0x7ffff7385bb6 <+118>: callq  0x7ffff7309958            ; ___lldb_unnamed_symbol2$$libcairo.so.2 + 8
    0x7ffff7385bbb <+123>: testq  %rbx, %rbx
    0x7ffff7385bbe <+126>: jne    0x7ffff7385bb0            ; <+112>

For the record, we will as soon as the things that depend on it are compatible with it (kdenlive, for example). We're keeping an eye on it.

2005? Definitely not getting included. Not my decision, though.

Bump

Fix builddeps

We might not want to include this in the repos, as the maintainer is against distributions patching this software, and in their words:

As a heads up. With the next release of NoiseTorch, you will have to either stop applying patches, or rename, as will other distributions.

So we can either distribute it completely unpatched, distribute it under a different name, or just not distribute it at all.

Update to v0.9.2

Update to v1.5.0

Update kotlin-native to v1.5

Unfortunately I have not yet been able to reproduce it. I tried validating on both my laptop (fully AMD) and desktop (AMD CPU + NVIDIA GPU). Could you folks let me know what hardware you're running on?

@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.