Quoting: pleasereadthemanual

Quoting: fenglengshunjust general Remote Desktop stuff).

Server RDP or desktop RDP? And what issues?

(as a curious person who runs a GNOME-based RDP server)

Desktop. I mainly used Rustdesk + TeamViewer + AnyDesk, for redundancy in case of connectivity weirdness. Last I tested, unattended access is wonky on KDE and unattended login doesn't work on Wayland at all.

Quoting: EduardoMedina

Quoting: fenglengshunI won't lie, as a Bazzite user who builds my own custom image, I kind of wished that Valve would switch to a an rpm-ostree or similar infrastructure. I would love to have SteamOS images, with my own tools pre-baked in.

IMHO, OSTree is a very bloated software that steps on things that systemd can do. Even GNOME OS tries to replace it with parts of systemd.

I think that SUSE immutable systems are better focused. transactional-update seems smaller than OSTree and Snapper manages the snapshots. Moreover, in SUSE and openSUSE immutable systems you can rollback things the /etc folder, while with OSTree you only can rollback through the system images. In Aeon Desktop the automatic updates are scheduled with a systemd timer.

Finally, with Aeon Desktop you have a rolling release system, while with Fedora you have a point release system if you don't use the rawhide repo, but rawhide is nothing more than an experimental repo.

I like Fedora, but if you try Aeon Desktop, you can see that it's a lighter system than Silverblue, although the presence of x86_64-v3 packages in Aeon Desktop may be influencing.

I don't disagree that it's bloated, but it is bloated in a way that doesn't bother me and for a benefit that I think is worth it.

For me, I just don't like messy packages list. Even in a Distrobox, it bugs me when I have packages that I don't intend to use, that isn't part of the default. The biggest benefit of OSTree for me is their infrastructure- if you take a look at Blue Build system (the now independent image builder aspect of Universal Blue), the effect is that you have a semi-declarative OS image where I can cleanly and clearly put in "Take Bazzite as base, and add these packages." Then Github will build them, and keep 90 days history of them, while my devices has previous image as fallback.

What really made an impression on me was when mainline Kinoite was having an issue once. I just trace each day's image, found when the issue started, test the upstream ublue Kinoitr image of that day, then test the ublue image's upstream in mainline Kinoite... I can just say "Here, this is where the problem started, and it's likely because of this commit." That was a great bug reporting experience, likely both on my and the devs' end. I liked that, and that's why I have a strong feeling towards rpm-ostree.

View this comment - View article - View full comments

I won't lie, as a Bazzite user who builds my own custom image, I kind of wished that Valve would switch to a an rpm-ostree or similar infrastructure. I would love to have SteamOS images, with my own tools pre-baked in.

Then again, I don't need THAT much stuff on host system anymore (vs user-space) so I could settle with SteamOS official desktop installer once my Wayland and Portals woes are settled (currently, mainly usb-portal for gnome-boxes and just general Remote Desktop stuff).

View this comment - View article - View full comments

I hope they succeed. Some of these protocols do take too long and way too many arguments on the correct way to do the same thing. Sometimes I get why, and sometimes I do think they should be more willing to just try things out and iterate.

View this comment - View article - View full comments

Quoting: mrdeathjrbut wmv (with wmapro audio) however still is a problem in my case

Ahh, I'm guessing Yuzusoft still doesn't work by default then. Well, at least it seems like a lot of VNs are getting worked on through ProtonGE, so at least there's that.

View this comment - View article - View full comments

Quoting: reaperx7Many of you are getting this wrong...

Swanstation was a port of the libretro-core that was maintained by RetroArch without Stenzek's permission after he and the head developer of RetroArch had a falling out over Stenzek teying to push code updates to the tree and the RetroArch dev reversing the changes because "he didn't like them".

Duckstation was meant to be distributed as-is either in flatpak, self extracting executables, or the unmodified source code for distributions of Linux/BSD to do their own localized and self-maintained ports with. The exe and flatpak versions would be supported officially by stenzek where as the source code ports would be distribution maintained.

He changed the license because he doesn't want people to clone Duckstation and then steal his work, and have people blaming him for a forked project's faults like Swanstation did.

I don't blame him. The GPL is a very flawed license when it comes to allowing a developer to have absolute control over him/her project. For some projects its fine, but for others it's a total headache.

This is why many developers in the past have used BSDL, MIT, and other more restricive licenses to maintain control and prevent unauthorized forking. This saves Stenzek the time and trouble of dealing with unofficial ports, packages, and projects. He's not saying you can't fork the project, but what he is say is, if you fork, all changes have to be submitted back forst in private, and approved before you publish your changes go public in your fork so the entire project is on the same page.

This is what it means to be FOSS. FOSS is about freedom and openness of the source code. People are free to take your source code and do whatever they want with it. Both good and bad.

If they don't like it, they're free to start a new project, under a new license.

View this comment - View article - View full comments

I personally don't like it. This feels like more FOSS bait-and-switch and erosion of what FOSS meant. FOSS doesn't just mean source available nor does it meant no-commercialization. FOSS means freedom and openness for the source-code, so people can do whatever they want with it.

If he wants to restrict the binary or something, I'm fine with that. Likewise, if he wanted to make a more restricted version of the project, I'm fine with that so long as it's either a new one or a clean-fork of this one.

Add to that, I don't trust a developer this unstable. If it was 100% FOSS instead of being this weird Source Available model, I'd be able to ignore it as I can trust someone will pick up the torch if and when the original dev leaves the project.

So I'd rather just migrate now, and use something else I can trust to be more stable in the long term.

View this comment - View article - View full comments

Quoting: fritzyThe original Redhat 7.1 in 2001 left a bad taste in my mouth, and I never recovered. Is there a reason why we should use this Fedora distro over something like ChimeraOS?

For most users, the Bazzite Launcher app which makes setting up a lot of gaming and non-gaming stuff easy (like setting up virt-manager or sunshine), making it easier to use than other immutable distro. Also, overall there's just a lot of resources that's been accumulated to help people install stuff like Da Vinci Resolve and others. For me, Universal Blue as a whole is what gets me into the immutable train because it's very usable.

On a more power-user side, there is what is now called BlueBuild, which allows you to build your own images. I have a github repo in which I use Bazzite as a base image to build my own image with my own packages list and usr/etc files, allowing me to essentially have my own personal distro after a 6-click short setup process.

View this comment - View article - View full comments

Quoting: mrdeathjr:smile:

I don't know how you have the patience and time to keep doing this, but I appreciate you trying things out, summarizing what you tried, and the actual progress on the bleeding edge cases for Wine.

I don't really get all the details, but it's nice to see progress and it's nice to see users actually testing the experimental stuff.

View this comment - View article - View full comments

I hope they do the first game justice. Aside from the frustrating binary ending, it was a lot of fun with a lot of charm. There's both teenage identity and LGBT identity stuff that's done well. Something that the next games (prequel and such) just didn't capture - granted, I only know about it from the hobbydrama post [External Link], but nothing after the first main game really interested me to pick any of them up.

View this comment - View article - View full comments

Quoting: GuestIsn't it also the case that games running with Proton are automatically and individually sandboxed (to some degree)?

AFAIK by default most proton prefixes still have access to user's system mounted in Z:\ thanks to Wine's defaults.

View this comment - View article - View full comments