Cool, while a lot of people are complaining. For those of us that still keep a chromium based browser around for the those few times where you need compatibility. These small improvements are very much welcome.

Cool. Always nice to see the whole document signing situation improving across all the different linux desktops.

Glad you brought up the software point. Back when I tried I had the same issue, but no one mentioned it when I was hearing about why I should try out a BSD system. Seems that even open source software often doesn’t have any of the BSD’s in mind and you end up needing to use that linux compat thing I remember seeing. If that even works for whatever you are trying to use.

I tried the flatpak for Zen, but it seem to crash quite a bit. How has your experience been?

No, not really. I believe it is because a lot of us linux users have more understanding of our systems, so we know why a certain outcome happened vs “it just works ^tm”.

Also I would like to point out something that I have been telling people for years whenever a post like this comes up. Windows and Mac users do the same thing. They constantly overlook bugs, bad design, artificial limitations, and just the overall lack of care when it comes to various details that more community oriented projects cater to. The reason is because of familiarity. Just like many of us will often not see issues with new comers struggles because we have already worked around all of the issues. These users do the same.

I found this in the forum that was linked on the planettwatt.com site. https://planetwatt.com/newforum/index.php?topic=1016.msg3100#msg3100

Didn’t find any source code though.

deleted by creator

I rarely see any comments on any Gnome posts here actually.

As someone who tries to look under the hood for a lot of the open source software I run, one thing that I have noticed is that there are a lot of cases where the general sentiment seems to be port to what. Wayland still doesn’t support a number of things that some applications require. A lot of developers that I have interacted with would rather have the app run through XWayland rather than have a wayland version of the app with less features or certain features grayed out.

In the case of one project in paticular, that being the Sunshine game streaming project. I have personally witnessed. Them implementing a solution for wlroots based compositor. Having that solution eventually break as wlroots based projects deprecate the protocol they were using in favor of a new one and now that protocol is looking like it too is old news and is going to be deprecated in favor of a newer and better protocol. What I am getting at here is that protocols not existing isn’t the only problem, but things are still very much in development. Even applications that implemented wayland support are being put in positions where they need yet another rewrite because things are far from finalized and still moving pretty fast.

Good for them. Hope more follow suit.

The whole samba filenames thing is configurable. I only use linux systems and I ran into that same issue.

By default samba seems to mangle file names. Not to mention that Windows systems don’t tend to support naming your files whatever you want the same way they do on linux so we need to map those characters to something else. To solve this I include a few different entries in my samba config file to fix the issue.

mangled names = no
vfs objects = catia
catia:mappings = 0x22:0xa8,0x2a:0xa4,0x2f:0xf8,0x3a:0xf7,0x3c:0xab,0x3e:0xbb,0x3f:0xbf,0x5c:0xff,0x7c:0xa6

That’s just if you choose to go with samba. I only use it cause it was easier to setup than NFS when I tried.

There are real issues with Mozilla, but most of these people are complaining about nothing. Constantly whining about every little thing to the point you would think they are saying they are worse than Google.

I read the words hybrid cpu 5 times and still thought this was something about hybrid graphics.

I usually do distro repos, followed by aur, then flatpak if the aur version is too cumbersome (e.g. obs, game emulators). Funnily enough I use steam native because when I was using the flatpak. I had trouble with mods and things of that nature. A lot of that stuff either needs to be moved to different locations, straight up doesn’t work, or requires a bit of permission fiddling and I just didn’t wanna go through that. On the other hand. I believe there was a glibc issue on Arch that broke all games on steam native for a couple of days which the flatpak didn’t suffer from. Just goes to show nothing is perfect either way.

Maybe you should have considered the stuff he wanted to do before convincing him to use linux. I could have told you he’d have problems with that stuff. If he said he mainly plays steam games then sure, but not literally the most finicky, cumbersome games to get going in existence. Also out of curiosity because I haven’t even thought about Roblox in like 8 years. I thought that was a browser game?

I feel like that may be true nowadays, but I remember back when I used to use ubuntu that the upgrade from 16.04 to 18.04 was pretty bad. Fedora has always worked great for me, but these days I only use rolling release distros in which case there aren’t any major version updates in the first place, so the problem largely doesn’t exist in the same context.

While the actual install process is super easy especially if you managed to install windows 10 on your own, I’m actually more curious as to what laptop you went and bought. Whether or not your hardware even works well with linux is the much more common problem that people have when using it. It’s what leads to the vast majority of something works on my hardware, but not yours posts. Plenty of people have already given instructions on installing, so I won’t go into that, but maybe try to research linux on [insert whatever laptop you bought] first.

I’m still struggling with remote desktop software and other alternatives such as sunshine. KDE connect input sharing is inconsistent on wayland, but they will probably fix that eventually. xwaylandvideobridge is great when it works, but currently has an issue with eating input invisibly. Also, some things just seem to be kinda wonky. For example screen sharing portal when sharing my screen in a browser seems to open twice. Same with obs. Still no good virtual keyboard. If onboard worked on wayland that would be perfect.

Sounds like a case where machine learning would actually be useful.

Been using it since plasma 6