It turned out that those FPS drops I was talking about, were a known memory leak that was fixed in one of the patches. Just FYI

View this comment - View article - View full comments

I noticed a bug in Proton. In my configuration, whenever I save the game in a very tasking areas, FPS drops to 4-6 and GPU is used 100%. It never goes away, until I change the resolution (no matter if up or down). This immediately raises FPS to normal levels, the same with GPU. The issue doesn't happen on Vulkan, however, because Vulkan is unstable (crashes on every dialog), Proton's layer (DXVK) is needed.

Playing on lowest requirement hardware, this becomes very tedious.

Any idea where to submit that proton bug?

View this comment - View article - View full comments

Flatpack Zoom didn't work with it, but Zoom from AUR works great in Plasma. The annoying notification about its working only in Gnome is gone, and it simply opens the usual sharing option window.

View this comment - View article - View full comments

Quoting: voxWhen KDE team will fix their major bugs then I'll consider switching permanently. Otherwise I don't see the appeal.[...] I don't want to have a risk of losing all of my opened programs in case of a crash.

This is not a KDE issue. It's a Wayland issue, so all Wayland sessions on all possible DEs are affected.
I'm running Wayland on Plasma 5.27 a second week, and it's very stable, although I have a hybrid GPU with Nvidia. The only crashes I observed were when I tinkered with Kwin settings, or with system tray. So basically, two situations where it crashed spontaneously. Those situations are not everyday actions, so stability wise, Wayland became pretty good nowadays, comparable with X11. However, if you work with graphics, video programs, it's too big risk. I can set LO to save my documents every minute and for the most part, I will be fine, but most work situations won't be so forgiving.

View this comment - View article - View full comments

Quoting: lejimsterI keep trying to switch over to Wayland, but there is always a few quirks on gnome that wind me up and put me off using it full time, I really should test KDE as it's probably just gnome issues. Anyway, I wonder if this will have any benefits over gamescope? Even less latency? I was planning to do some testing with gamescope as it works so well on the steam deck but I haven't got around to it yet. Does anyone here run gamescope on their PC?

Plasma 5.27 has a nearly perfect Wayland experience. For a long time Wayland was no-go for me, because I use a hybrid GPU laptop with Nvidia so even when for many PCs it worked well, it was horrible at my end. With Plasma 5.27 I decided to switch to Wayland and... the experience is almost on pair with X11 and in some areas better. I run Steam with prime-run and Divinity Original Sin had about the same performance as on X11, so this has to mean, that Nvidia is correctly used. I couldn't tell it before looking on system data on Steam, because it always crashes on Wayaland, but that's a problem with Steam, not getting the correct data and going haywire because of that. I suspect not all games will work well, but so far so good.

The perk of Wayland is the real-time touch gestures on a pad. They work so much better than on X11. It is as if I got a new pad, as accurate and smooth as on MacBooks. The con is, that there is a set of pre-defined gestures and no UI to configure them, so we are stuck with what is given to us. However, Overview and grid are absolutely awesome. The gestures' configuration is planned, but the person responsible for it went gone. Eventually it will be implemented (if not by the original developer, by someone else), but not soon I'm afraid.

My main issue now is with shutdown, which takes a long time, or it freezes. I'm not sure if it has something to do with Wayland, but prior to Plasma 5.27 update on X11, all was fine. However, it may be some issue on my computer.

Unfortunately, there is one absolutely MAJOR CON OF WAYLAND that nobody is talking about: when Wayland crashes, all opened windows have no way of returning, so they are force-closed, so when Wayland is automatically restarted, all opened apps are gone, including latte-dock. This is currently the problem of Wayland, so also Gnome and other Wayland implementations suffer from this. Because of that, Wayland is not ready to be the default and those who set it as a default for their distros, are probably not aware of this huge concern. So as you can imagine, tinkering with Plasma settings increase a risk of Kwin crashing, and if Kwin crashes, Wayland does also, because they are the same in Wayland session (so to speak). On a daily basis, risk is minimal thou.

Luckily, there is work already started to fix this, but it won't come soon, maybe in a couple of months, a year, or longer? Hard to tell.

View this comment - View article - View full comments

Quoting: JarmerThe current stable release of Mesa as listed on their site (https://mesa3d.org/) is 22.3.6 which is in unstable branch on Manjaro ... so it needs to get into testing, then stable. THEN Mesa 23 can enter into unstable and start testing.

I'm moreso waiting on plasma 5.27!

The nice thing about Manjaro is that you can easily switch the branches (one command). Most of the time I'm on testing branch, but when I can't wait, I check out the unstable. That is why I already have Plasma 5.27.1. Of course, backup before every update is a must, just to be on the safe side.

sudo pacman-mirrors --api --set-branch unstable

and if you want to revert to for example testing branch:

sudo pacman-mirrors --api --set-branch testing

And of course "sudo pacman -Syyu" after the switch.

View this comment - View article - View full comments

Quoting: EikeMaybe this?
prime-run "steam -newbigpicture"

No, also doesn't do anything. From what I heard, this doesn't work on nvidia cards and that is the reason.

View this comment - View article - View full comments

I'm confused. It doesn't work. I already use:

prime-run steam

in a launcher. So where do I put those arguments? I thought that the proper place would be at the end, but it doesn't make any difference (I am running Steam beta). So I tried it before steam, also no change. Before prime-run? That would make no sense, or maybe? I checked and... again no change...

View this comment - View article - View full comments

Quoting: mphuZIt's a shame that Valve hasn't released the SteamOS desktop distribution yet.
And even the new Big Picture is missing in the beta version of Steam.

The SteamOS is suited to SteamDeck's hardware. This makes the whole thing easier and cleaner. Desktop OSes must be ready for all kind of hardware, and not all combinations will work well. Although I would love to see the Steam OS on PCs, I don't think it would be a good thing after all:

- the SteamOS development team would have to deal with probably 1000% increase of bugs, issues and bad press, which is not going to help anyone
- users would be frustrated by various issues that don't exist on SteamDeck, so the experience hadn't been so smooth
- the bad press, experiences, would likely distract from the process of marketing SteamDeck, they already have their hands full, they should stay focused, they are already doing a lot

We already have community OSes like Chimera OS that is doing a similar thing, but is more open that SteamOS and suitable for PCs. Any issues with the system won't be credited back to Valve.

Said that, I don't think that releasing SteamOS for PCs will happen or if it happens, it may not be a good thing, unless Valve makes this an unofficial spin-off, run by and for the community - without any guaranties or official ties to Valve. If there would be some hidden, unofficial support of some Valve employees, it would be a nice touch thou.

View this comment - View article - View full comments

Quoting: sudoer

Quoting: michaldybczakManjaro unstable aka Arch stable, this was a whole another thing. The OS can break pretty fast and hard. There were quite damaging updates along the way. Fixes came in matter of hours, but I was too late, I updated to packages that were broken and that were crutial for the OS to function.

That's plain wrong, I've tested Manjaro in the past and its "unstable" is not Arch stable, Manjaro unstable contains Manjaro's own in-house developed unstable packages, their own kernels, modules, overlay packages there, so if things break for you in Manjaro unstable, this does not mean that the same is happening in Arch stable, nor that they are comparable.

Sure, Manjaro has some own packages, but every time I got breakages on Manjaro unstable, it was directly because of Arch packages. As said before, those were fixed incredibly fast, but I had the poor luck to update with the broken packages. Few hours later and I would be fine.

What I wrote comes from my own experience. Besides, you are uncessarily nitpicking on details. We are not discussing here the structure of Manajro and Arch packages, but in general, the stability of a distro, and based on my examples, I was proving a point, that Manjaro has more flexibility and stability than Arch. Manjaro has its overlays so Manjaro unstable isn't 1 to 1 Arch unstable, agreed, but that's beside the point. Manjaro unstable is the closest to Arch stable as possible and there is a VAST DIFFERENCE between Manjaro unstable and Manjaro testing. So if someone wants to be on Arch based distro, Manjaro is a good option. No need to go to Fedora.

I personally had only bad experiences with all RPM distros, so I keep away from them. I always thought that expression "dependency hell" is only a historical one, till I tried RPM distros. It was pure chaos and the distros were breaking almost right away during installing normal program packages that I'm used to use. Pacman feels more robust to such craziness. Maybe Fedora is different and better then Open Suse in that front, but I prefer Arch simplicity: only newest packages + AUR. No versions, added repos, no repo complications. Sure, Arch has its issues as well, but those are easy to manage if one is familiar with them.

View this comment - View article - View full comments