Quoting: finaldestI am done with this crap.

I am fed up of this complete utter greed. First we lost physical releases along with publishers destroying games preservation. Now they want even more money by charging £100+ for a broken PC game and now I am required to give yet more money to play the game on release day (AKA On time)

I am done. After 20 years I am now going back to the high seas.

Visual novels are still very much physical. Tens of thousands of them are only available physically.

Big pain to ship them internationally and sometimes they're encumbered by DRM, but they are physical...I wonder if these Japanese games will ever make the shift to digital-only.

View this comment - View article - View full comments

Quoting: Purple Library GuySo, I've never really used flatpaks, except maybe one or two that were actually in my distro's repository. So I'm wondering--If you install stuff from Flathub, how do you keep it up to date? Is there some mechanism or do you just have to sort of remember that you ought to, application by application? Do you update, or do you just reinstall a newer version?

You just click the Update All button in GNOME Software or KDE Discover to update your system + Flatpak packages. They're all managed via PackageKit. It informs you if there have been any permission changes between versions. I assume the Linux Mint software GUI would have a similar screen. It updates like any other system package, replacing the older version.

You can also run:

flatpak update

in the terminal if you like.

Incidentally, rolling back to a previous version of a Flatpak requires the terminal and is a little obscure, but it's easily possible. For instance, let's say you want to downgrade GIMP. First we need to know the Parent commit:

flatpak remote-info flathub org.gimp.GIMP

Then update to the Parent commit:

flatpak update --commit=02da1cc51c2b5f9fe03487ff6024e95be68f22e1f10c73ca6a10f8de84e8d321 org.gimp.GIMP

To see all of the previous versions, run:

flatpak remote-info --log flathub org.gimp.GIMP

View this comment - View article - View full comments

Quoting: Pyrate

Quoting: pleasereadthemanualNo official Signal Desktop package. Where do you get it? From the unverified Flatpak? From openSUSE's OBS, which is maintained by a Fedora packager? From the COPR? Do you compile it yourself?

So the flatpak is not verified? I never realised that! is this worthy of concern? I don't know how this works, can one like check how the flatpak is built or whatever so one can be sure there were no modifications? What do you use to get Signal then if not the flatpak?

You'll almost certainly be getting your Flatpaks from Flathub. This is the way Flathub works:

• A user creates a manifest file (which is just a text file) with a bunch of instructions.


• Flathub builds a Flatpak package based on that manifest.


• The Flatpak package appears for download on Flathub's repositories.

Flathub is responsible for building the packages, so it always matches the manifest.* However, the manifest might be malicious. Flathub does manually review all initial Flatpak submissions and permissions changes, so that's some assurance.

Now, about Verification. Take a look at the Signal Flathub page: https://flathub.org/apps/org.signal.Signal

You'll see it says "Unverified". All this really means is that Signal Foundation (the original developer) is not responsible for the manifest or the package. The Flatpak is built by the community, which may or may not be trustworthy. It's a risk you need to take into account. Signal only provides a .deb package officially and nothing else.

Compare this to a "Verified" package, like Thunderbird. It's a package by the original developer, so you can trust it as long as you trust the original developer.

*: Mozilla provides the Flatpak package for Firefox, rather than Flathub building it. It's a very unique case.

And now...Signal

I apologize in advance for sending you down the garden path: https://github.com/signalapp/Signal-Desktop/issues/1630

To save you a lot of reading, a trustworthy option might be the Open Build Service RPM package provided by cryptomilk, who is a Fedora Proven Packager and contributor to Signal.

[1]: March 2018, cryptomilk expresses interest in creating an OBS package when Signal signs their git tags and OBS supports GPG sigs: https://github.com/signalapp/Signal-Desktop/issues/1630#issuecomment-373272490
[2]: October 2019, cryptomilk starts working on the OBS package: https://github.com/signalapp/Signal-Desktop/issues/1630#issuecomment-545581829
[3]: April 2020, cryptomilk gets the package working on OBS: https://github.com/signalapp/Signal-Desktop/issues/1630#issuecomment-611564892
[4]: July 2020, cryptomilk moves the OBS package to a new URL: https://github.com/signalapp/Signal-Desktop/issues/1630#issuecomment-664135377

Or maybe you decide "the Flatpak is probably trustworthy enough" and like the idea of auto-updates, so you just use the Flatpak package.

Or you decide that you only trust Signal and just build it from source: https://github.com/signalapp/Signal-Desktop/blob/main/CONTRIBUTING.md#linux

I never managed to settle on a decision. When I come back to Fedora, I might investigate container options like Podman/toolbx...

View this comment - View article - View full comments

Quoting: Phlebiac

Quoting: pleasereadthemanualI managed to compile Gamescope on Fedora

I haven't messed with it myself, but gamescope is in the default repositories, so very easy to install. Same for mangohud, goverlay, lutris, wine, and "almost" anything that is open source.

So it is.

I forget why exactly I compiled Gamescope from source on Fedora...there might have been a regression. Or I just didn't realise it was in the repositories!

One program I was surprised to find in Fedora's repositories was Cinelerra-GG.

Quoting: Phlebiac

Quoting: pleasereadthemanualinstalling patent-encumbered encoders/decoders, like the ones for H.264/H.265. You need to get those from RPM Fusion

I prefer the "fedora-multimedia" negativo17 repository myself.

Thanks for the tip!

Quoting: Phlebiac

Quoting: pleasereadthemanualAudacity is really out of date!

Current version in the repo is 3.3.3; that is indeed out of date, but it's less than a year old, going by the official Audacity website. Oh, but 3.4.2 is there for Fedora 40 (I think 3.5 just released a few days ago?):
https://packages.fedoraproject.org/pkgs/audacity/audacity/

Fedora 38 had Audacity 3.1, which was missing several major improvements from recent versions (I forget what exactly, I didn't use it for long). This is really a program that should be kept up-to-date throughout the Fedora release rather than pinned to a certain version. I don't know if it's possible to import newer project files in older versions of audacity, but I collaborate with users from other operating systems on various projects, so that would be a requirement. Yes, 3.5 just came out this week.

I noticed a few other programs on Fedora weren't kept up-to-date, like QBitTorrent, but that didn't matter as much to me as Audacity. Audacity 4.0 will be Qt-based, so hopefully that will make building it easier for Fedora in the future.

Quoting: Phlebiac

Quoting: pleasereadthemanualWhen I tried to watch videos with mpv, they would crash suddenly a few minutes in.

I assume that's from rpmfusion; you could try the negativo17 version.

Will do, when I get around to trying out the new Fedora release.

View this comment - View article - View full comments

Quoting: tuubiI suppose one might want to play around with gamescope, but no game actually requires that stuff as far as I know.

Visual novels are a chore to play without Gamescope. Almost all of them have broken fullscreen, or you can't move the window at all, or... other stuff.

Localization teams tend to do some engine hacking to fix that stuff, but if you want to play the Japanese version, it's usually like that.

Quoting: WoodlandorWayland graphics flickering under Nvidia drivers seems to be fixed with the final release.

Considering NVIDIA's new driver that fixes this isn't due to be out until halfway through May (and that's just their Beta driver, their production release won't be out for probably another month after that), explicit sync is very much still an issue on Wayland and will likely be until June sometime.

Quoting: legluondunetWhat distribution you will advice for gaming?

Most of those dependencies can be installed via Flatpak, but Arch by far makes installing all of this stuff natively the easiest.

A friend tried to install Gamescope on Mint and openSUSE, but they had a lot of trouble compiling it. I managed to compile Gamescope on Fedora while cross-referencing the AUR package for the right dependencies, and after about half an hour, I got there.

Best way to install Gamescope is to install the Lutris/Bottles + Gamescope Flatpaks. Any distribution would work then, but you would need to use the Steam flatpak if you wanted to use Gamescope on Steam.

It isn't hard to install NVIDIA's proprietary graphics drivers on Fedora. What is difficult, in my experience, is installing patent-encumbered encoders/decoders, like the ones for H.264/H.265. You need to get those from RPM Fusion, and while I followed the commands exactly, they didn't work the first two times. I have no idea why they worked the third time. Although I think Fedora provides AAC in its own repositories? Anyway, OpenH264 was flat out broken for me (lots of fun artifacts), so I needed the FFmpeg decoder for H.264, which I could only get from RPM Fusion.

In case anyone was curious, here's the list of remaining patents for H.264. About three-quarters of them are expired now, and by the end of April, around 11/58 pages of patents will be left. Do note that quite a few of them can be disregarded, as the most widely used version of the H.264 standard is the High Profile, patents for which would need to have been filed in 2007 or before. A number of patents apply to later standard revisions which are not in nearly as wide use.

Further sources about patent expiration dates for H.264.[1][2] Also, maybe Unified Patents will invalidate a few more before they expire naturally! But probably not.

Other things that were annoying on Fedora (my experience was Fedora 38):

• No official Signal Desktop package. Where do you get it? From the unverified Flatpak? From openSUSE's OBS, which is maintained by a Fedora packager? From the COPR? Do you compile it yourself?


• Audacity is really out of date! You need to get the AppImage or the Flatpak, which in my experience are both broken in different ways.


• There's also no desktop package for Bitwarden...same reason as Signal: Fedora does not package Electron currently because it's hard.


• For some reason, fcitx5 was broken due to a Fedora-specific reason. I know this because I needed to run im-chooser, a Fedora-specific program, to fix the issue. I have no idea what the issue was, but at least I can write in Japanese now.


• When I tried to watch videos with mpv, they would crash suddenly a few minutes in. This happened reliably. You might be wondering why I didn't report it—well, the error reporting program also crashed and wouldn't produce a backtrace. GNOME-Abrt never successfully generated an error report for me.

That being said, I'm going to try Fedora 40/41 again on a computer I don't care about. And I'm going to try Fedora Workstation this time instead of the KDE Spin. I hope Fedora is the kind of distribution you can leave alone for a few weeks and not come back expecting breakage.

I'll probably replace it with Pop!_OS, eventually...

[1]: https://forum.doom9.org/showthread.php?t=184869
[2]: https://meta.wikimedia.org/wiki/Have_the_patents_for_H.264_MPEG-4_AVC_expired_yet%3F

View this comment - View article - View full comments

I don't play LoL, but I appreciate that the developers went to the effort of understanding how Linux players play their game, and explaining in detail from their perspective, why they will now prevent Linux players from playing their game.

It's more than some publishers will do. They could have just pretended Linux players don't exist, or pretend that Valve is the only party responsible for making sure the game works.

View this comment - View article - View full comments

Quoting: Purple Library Guy

Quoting: pleasereadthemanual

Quoting: Purple Library GuyOn Mac, I suspect open source software is quite hard to run.

In general, it's a lot easier than Windows because it has a lot of the same libraries as Linux due to its *BSD heritage.

I was thinking more along the lines of just a bit of a pain to install because of Apple walled garden stuff, not so much not working or anything.

Oh, well in that case, not really! Installing open source software (or any kind of software, really) is pretty easy on macOS. Even installing homebrew is possible with a click (and a drag, and an OK prompt, and a right-click to Open it) or a one-line command. Same deal with, say, Krita. Just download the .DMG and go through a wizard. Most people don't use the App Store because it sucks for getting software anyway.

I actually think macOS is a pretty decent OS (with major caveats) and isn't much more locked down than Windows. In some ways, I think it's less limiting. It's all of Apple's other devices where that reputation is rightly deserved.

View this comment - View article - View full comments

Quoting: elmapul

Quoting: pleasereadthemanualO

Quoting: pleasereadthemanual. GIMP 3.0 will be out with so many improvements.

im not sure if that will be enough to counter photoshop AI stuff...

No way, but it has basic NDE (absolutely huge difference and necessary for so many people's workflows), multi-layer select, decent CMYK support, Wayland support, GTK3 support ... those are the things I noticed in 5 minutes of using the dev branch. The GSoC projects this year have me even more excited.

I don't expect GIMP to ever replace Photoshop for the simple reason that Photoshop is the only program that has perfect compatibility with .PSD files (with the exception of maybe Photopea?). That is what it would need for it to replace Photoshop for me and for a lot of other people. Same goes for Scribus, Inkscape, Natron, and Kdenlive/DaVinci Resolve for Adobe's respective formats, to a lesser extent. What's important is that GIMP is more pleasant to use and has more professional features for the odd things. Those that aren't locked to Photoshop then have a good option on Linux, and a good open source option on Windows and macOS.

Quoting: Purple Library GuyOn Mac, I suspect open source software is quite hard to run.

In general, it's a lot easier than Windows because it has a lot of the same libraries as Linux due to its *BSD heritage. Homebrew makes it so. It's why so many developers use macOS (Unix without the hassle, as they used to say). However, both GIMP and Krita have significant performance issues on macOS due to OpenGL, but mpv works fine for example. Kdenlive (and Lightworks, interestingly) can't handle scrolling inertia at all, but DaVinci Resolve is a fantastic experience on macOS. And Wine is more of a hassle. Open source software is quite easily installed on macOS compared to Windows, but the actual experience can be hit-or-miss.

I agree that there is a tendency to pay for stuff. Somehow I ended up paying for Magnet instead of installing Rectangle.

That being said, you can pry my Intel Mac from my cold dead hands before I shell out money for Apple Silicon (famous last words).

View this comment - View article - View full comments

QuoteTechnically, ChromeOS is also Linux, and while people like to debate that if you do include Linux and ChromeOS together it would actually be 6.32%. A number that is getting steadily harder for developers of all kinds to ignore.

If I remember correctly from last time we had a market share thread, more knowledgeable users than me pointed out that ChromeOS does not run Linux binaries (without installing Linux containers); it only runs webapps. That adds pressure for developers like Adobe to release webapps and hopefully make them good substitutes for native programs, but it doesn't mean anything for making Native Linux programs.

Wine still can't run Adobe Creative Cloud, but hey, at least you have a few more options today...

Quoting: rustigsmedwith win10 support ending for home users late next year combined with win11 high system requirements we could see a continued or slight jump. anyone want to predict Jan 2026? will 6% or higher be possible? It will be interesting and fun to watch.

I'm curious how many people will pay for extended support. For business users, it starts at $60 per year, then $120 for the next year, and $240 for the last year. Extended support for home users will likely be cheaper...

By 2025, I think Wayland will be a good experience for everyone. STF's funding for GNOME runs out at the end of 2024, and hopefully the accessibility stack will be up to snuff. v1 of the Color Management/HDR protocol will hopefully be finalized this year. Wine 10.0 will probably have the Wayland driver exposed by default. Noveau + Zink + NVK will have had more time to mature. GIMP 3.0 will be out with so many improvements. So it'll probably be a good time to switch!

In some ways, I'm glad Fedora 40 is forcibly cutting ties with X11 next week (although a KDE developer maintains X11 packages for Fedora, they aren't installed by default) as it will give more users more time to live on Wayland, which gives user-facing programs like Steam, Discord, and Krita (after CM...) more time to switch to Wayland. I just worry about Linux Mint's Wayland project.

View this comment - View article - View full comments

Quoting: F.Ultra

Quoting: pleasereadthemanual

Quoting: TheRiddickBe a great day once NVIDIA gets [..] properly balanced HDR (is desaturated and wrong exposure atm).

Is HDR even available at all? As far as I know, KDE only offers a partially-implemented version of HDR on their Wayland session.

gamescope

Ah, that's true.

View this comment - View article - View full comments