There have been multiple accounts created with the sole purpose of posting advertisement posts or replies containing unsolicited advertising.

Accounts which solely post advertisements, or persistently post them may be terminated.

Zamundaaa

@[email protected]

This profile is from a federated server and may be incomplete. Browse more on the original instance.

Zamundaaa , (edited )

That has pretty much nothing to do with the color profile, when colors look very desaturated on HDR screens, that’s the driver messing up the colorspace signaling.

What GPU do you have? Both Intel and NVidia still have major problems with this.

Many displays (but not all, which is why it’s not exposed in the GUI) also support doing HDR without additional colorspace signaling, you could try enabling only hdr and disabling wcg with kscreen-doctor. IMO the color part is the more noticeable benefit of HDR, but you could at least have functional HDR until your GPU driver is fixed.

Zamundaaa ,

Of course apps can and do restore their window sizes. Don’t spread misinformation

Zamundaaa ,

There have been incidents involving malicious code downloaded through Plasma global themes.

No malicious code was involved, just buggy code.

Found a security bug in LMDE6, need some help (i.imgur.com)

I have an older Intel laptop that has a 1600x900 display, and I find that if I put the machine to sleep, connect an external monitor with a higher resolution, and then turn it back on, the login screen doesn’t adjust to the new resolution and it reveals what I had open (see photo)....

Zamundaaa ,

KDE did bother, this does neither happen with KScreenlocker, nor do non-screenlocker windows show in another way, because the screen locker is integrated with the compositor.

If the compositor crashes or gets disabled somehow ofc though, that integration doesn’t help either and you have to rely on a mountain of bad hacks as well as the hope that the screen locker doesn’t also crash for nothing to happen in that case, but it’s as close to secure screen locking as you get on Xorg… in the end the solution for secure screen locking is still Wayland.

Intel revealed more Lunar Lake processor details with their new Xe2 graphics (www.gamingonlinux.com)

From what details Intel provided they’re claiming “60%” better battery life for these mobile processors in “real-life usages”. Impressive if true, but just as exciting is the huge advancement of the graphics side with Xe2 which they claim will bring improved “gaming and graphics performance by 1.5x over the previous...

Zamundaaa ,

Writing graphics code in a unified model is quite a bit different from the conventional x86 model.

It isn’t. The difference is pretty small, and it’s just optimizations for when copies can be skipped and not a radical change in the approach of how rendering is done.

Intel would need their own equivalent to Metal if they wanted to do a similar move.

Not at all. If big-ish changes were required, they could be exposed as Vulkan extensions.

I don’t know enough about Vulkan to say if it’s compatible with this kind of approach

Of course Vulkan, the graphics API used on all modern phones except Apple’s, supports using integrated graphics efficiently.

State of S3 - Your Laptop is no Laptop anymore (blog.jeujeus.de)

In this article, I aim to take a different approach. We will begin by defining a laptop according to my understanding. The I will share my personal history and journey to this point, as well as my current situation with my home and work laptops. Using this perspective, we will explore the current dysfunctionality of the standby...

Zamundaaa ,

the fact that 1.8 was working tells me that it is possible for a window manager to work well for nvidia

Nope, it’s a race condition for which the visible effects can appear or disappear for plenty of reasons. The only fix is explicit sync, which is being worked on for wlroots

Zamundaaa ,

It’s been possible for a long time, but yes, now you can do it intuitively in the shortcuts GUI

Zamundaaa ,

Just use Wayland, then you don’t have to care about this

Zamundaaa ,

Most displays provide settings to modify the colors of your screen; mine has like 10 different “picture modes” that strongly modify gamma curves, colors and the whitepoint. The EDID only describes colors of one of them, so if you change display settings, the data no longer applies.

More generally, the information isn’t used by Windows or other popular video sources by default, so manufacturers don’t have much of an incentive to put correct information in there. If it doesn’t make a difference for the user, why would they care? Some displays even go so far as to intentionally report wrong physical size information, to make Windows select the default scale the manufacturer wants to have on that display (or at least that’s what I think is the case with my cheap AliExpress portable monitor)…

That’s not to say that the information is actually often completely wrong or unusable, but if one in tenthousand displays gets really messed up colors because we toggle this setting on by default, it’s not worth it. We might add some heuristics for detecting at least usable color information and change this decision at some point though

Zamundaaa ,

it falls to each and every individual app to (re)implement everything: accessibility, clipboard, keyboard, mouse, compositing etc. etc.

I haven’t read so much nonsense packed in a single sentence in a while. No, apps don’t implement any of these things themselves. How the fuck would apps simultaneously “implement compositing themselves” and also neither have access to the “framebuffer” (which isn’t even the case on Xorg!) nor information about other windows on the screen?

Please, don’t rant about things you clearly don’t know anything about.

Zamundaaa ,

Only thing not working for me is HDR (should be fixed in Plasma 6.1)

What’s supposed to not work, and what am I supposed to have fixed in 6.1? There haven’t been any major changes to HDR since 6.0

Zamundaaa ,

And you cannot invoke it by yourself to type in XWayland applications

Yes you can

Zamundaaa ,

When you have a Xwayland app focused, the Plasma panel will have an upward facing arrow in the system tray. If you tap it, the virtual keyboard will pop up

Zamundaaa ,

I am talking about the desktop. Mobile doesn’t have a system tray.

Zamundaaa ,

Fedora. Though I just tested it again and the input method icon is now hidden by default, and does not automatically show up when appropriate :|

You can make it always be shown in the system tray configuration, but this should really work out of the box…

Rectangle for Linux?

To preface this, I’ve used Linux from the CLI for the better part of 15 years. I’m a software engineer and my personal projects are almost always something that runs in a Linux VM or a Docker container somewhere, but I’ve always used a Mac to work on personal and professional projects. I have a Windows desktop that I use...

Zamundaaa ,

You’ll need to specify what DE you’re using. This comes built in with KDE Plasma: Meta+left and then quickly also up for top left corner, Meta+right and then quickly also down for bottom right corner etc.

I don’t knowt what exact shortcuts other DEs use, but I think most that aren’t Gnome support quarter tiling too

Zamundaaa , (edited )

Debian still ships version 5

Debian ships 5.27.5 - it’s not just not updating often, but it’s not shipping bugfix releases (latest 5.27 version is 5.27.11!). I recommend to avoid it and maybe look at KUbuntu LTS instead

Zamundaaa ,

That’s about running on 32 bit hardware, not about running 32 bit applications

Zamundaaa ,

4k is literally a resolution, usually 3840x2160 or something around that. 1080p is another resolution, usually 1920x1080. These are never comparable.

You would be right if lossy compression wasn’t a thing. But it is, and it’s getting used a lot.

“4k” can very much be worse than 1080p if it’s compressed in a way that erases more details. That’s what people are complaining about with streaming services and YouTube - the resolution numbers don’t mean shit, and quality at a given “resolution” has been degraded more and more over time.

Zamundaaa ,

Widgets aren’t themes. They’re things on your desktop that people are using for example for showing a folder - and if that can’t interact with the system, that widget’s functionality is broken.

Of course, that should not apply to install scripts or the like, which shouldn’t be a thing at all really. And it should be made a lot more obvious which downloadable things can execute code / which ones are “guaranteed” safe and which ones may not be.

Zamundaaa ,

It is not related to Wayland or the compositor in any way. This is a plasmashell extension.

Similar caveats do apply to KWin scripts and effects though

Zamundaaa ,

No, it’s just a (long fixed!) bug. In the case of the Deck, the next version of SteamOS comes with the fix soon… in the case of Debian, they don’t ship our bugfix releases, so it’ll be stuck with this until Debian 13 :/

Zamundaaa ,

Fedora KDE 40 does not have an X11 session by default

Zamundaaa ,

Why would it be odd? This post is about the exact same thing happening with Gnome

Zamundaaa ,

Your quote describes literally the exact same thing that Fedora KDE 40 does. Yes, they wanted to go further and remove the Xorg bits already, but that got rolled back.

Zamundaaa ,

Gnome defaulted to Wayland when it was still very much unusable to be frank, it doesn’t really have any relevance for removing the Xorg session.

I think Fedora 38 is when they defaulted to wayland in the Plasma edition

34, not 38.

Zamundaaa ,

Is that on Xorg, or on Wayland? On Xorg, a bunch of different processes can try to take control over the gamma_lut of a screen (like night light in KWin vs the gamma settings page vs some games like CS2 vs colord), so if you’re on Xorg I’d be surprised if you didn’t have issues with it sooner…

Issue with Valve Index

I got myself a valve index, as I’ve heard that it works well on GNU/Linux (I use Debain 12 with GNOME). Turns out, there were a bunch of hurtles. At first, my cable was just broken, so I needed to get that relaced. Later on when I got the cable, Everything worked fine, but nothinig is being displayed in the headset. The screen...

Zamundaaa ,

The warnings you see are caused by github.com/ValveSoftware/SteamVR-for-Linux/…/616. Maybe disabling async reprojection will help you too

Zamundaaa ,

They are afaik not allowed to exist with USB C. And except for some very few very sketchy manufacturers, it’s also luckily not a thing in practice.

Zamundaaa ,

It is closed in the sense that all the ISO specs are closed - you have to pay a decent sum of money to see the specs, and you’re not allowed to just copy them and show them to people that haven’t bought access.

They are not closed like HDMI though - if you implement them, copy constants from the specs into the Linux kernel for example, that’s fine. Having actually open standards like Wayland would be a lot better though ofc…

Zamundaaa ,

That shortcut does nothing on Wayland. What you’re experiencing is either placebo, or you’re not using Wayland

Zamundaaa ,

Yes, it is a KDE shortcut, a kwin_x11 shortcut to be more specific. It’s not a thing with kwin_wayland, and so it most certainly did not help or do anything for you - unless you’re not actually using the Wayland session of course.

I dislike wayland

Quite the unpopular opinion, but I just wanted to post this to show the silent majority that we still exist. We have reached a point where voicing criticism against wayland is treated like the worst thing ever and leads you to being censored and what not. The red hat funded multi year long shill campaign has proven to be quite...

Zamundaaa ,

wasn’t it thought for kiosk applications, then extended to login screens

No, that’s a really pervasive myth, spread by trolls.

Wayland - or rather, Weston - first came into use in the embedded scene because things are a lot simpler to change there and the limitations of Xorg even more unforgiving… But it was never designed for that purpose alone, it was always meant to replace Xorg everywhere.

Zamundaaa ,

Yes, though it’s not exactly relevant to your wishes… KWin has supported VRR for almost three years now, and HDR for 9 months too (not released yet ofc). I’ve been playing all my HDR capable games in HDR mode for the past few months.

For me, this is more about making it more efficient and make it work better by default.

Zamundaaa ,

The best part is that instead of doing what Flatpak does (just blocking things and leaving the user unable to to anything) the system will prompt you for a decision.

No, Flatpak isn’t the problem here, portals for these things exist. The problem is that apps would have to use them, and unlike Apple, there’s noone restricting the old / unrestricted ways of doing things… So apps usually don’t port over to the portals.

Even where the unrestricted APIs stop working, like with screen capture and Wayland, apps are excruciatingly slow to port over, because they don’t get kicked from app stores for it, and because many users can still fall back to using the old system.

Zamundaaa ,

Instead of bluntly blocking things why can’t Flatpak just simulate a full environment and just prompt the user whenever some application wants to read/write to file / unix socket at some path?

Because the user getting a hundred popups on app start for various files the app needs isn’t exactly a usable experience. Also, blocking the app’s main thread (which is the only way you could do this) is likely to break it and cause tons of user complaints too.

Aside from apps using the APIs meant for the purpose of permission systems, there’s no good way to make it work.

Zamundaaa ,

until apps can declare on a simple config file what paths they require

They can, and always could. Apps aren’t doing it, most Flatpaks have just blanket “allow ~/Downloads” or “allow all of home” permissions by default - or no file permissions, and you have to go grant them manually yourself.

Again, unless apps actually support it, no matter how good the security system is, it won’t work out.

Zamundaaa ,

FreeBSD isn’t working on a Wayland port, that’s already happened. The Plasma Wayland session has supported it for quite a while… KDE even runs a CI job on FreeBSD for every merge request, where kwin_wayland autotests are run.

Considering the amount of complaints we got when something broke recently though (which is to say, none), it doesn’t look like it has a lot of users

Zamundaaa ,

Plasma never had this issue in any release, VRR has worked exactly the same since it was introduced until Plasma 6 (where there’s some improvements for the “always” mode)

GNOME Sees Progress On Variable Refresh Rate Setting, Adding Battery Charge Control (www.phoronix.com)

As pointed out in This Week in GNOME, there’s been some continued work on Variable Rate Refresh for the GNOME desktop. The VRR setting within GNOME Settings continues to be iterated on as the developers iron out how they’d like to present the Variable Rate Refresh setting for users. The developers have been discussing how to...

Zamundaaa ,

via the Wayland protocol

There’s no Wayland protocol involved, Mutter directly talks to the kernel

Zamundaaa ,

Does Wayland only encompass communication between clients and the server?

Yes

Is requesting VRR a part of Kernel Mode Setting, then?

Also yes

Zamundaaa ,

Unfortunately Debian stable doesn’t ship our bugfix releases after the major Debian version gets tagged - KDE Plasma in Debian is currently at 5.27.5, and 5.27.10 was released upstream two months ago.

In other words, you’ll be experiencing bugs that have long been fixed… I’d advise to stay away from Debian for KDE Plasma because of that. If you want a Debian based distro with a good KDE Plasma experience, KUbuntu is likely a better choice, even with forced snaps. If you don’t need Debian though I’d recommend taking a look at Fedora KDE or Arch (derivatives).

Zamundaaa ,

It’s a driver bug, it doesn’t reject buffers that the GPU can’t actually handle correctly.

We’ve switched to a different way of doing multi-gpu in Plasma 6 that hits at least fewer such bugs.

Zamundaaa ,

Sorry, but Debian stable is a terrible recommendation! They don’t even ship bugfix releases of KDE Plasma… It’s stuck with a months old version that has lots of known and long fixed bugs in it

Zamundaaa ,

The 1 second present timeout still only works for XWayland

Oof, I thought the corresponding MR for Wayland was merged… But it was from Sebastian and after he got into a heated discussion again and started cursing, the MR got closed by someone else :|

realistically unless SDL2, GLFW or whatever engine a gamedev is using handles it for them they just don’t have the time to worry about what GTK, Qt, or XDG shell does

SDL does handle it, but only for OpenGL; it can’t do anything about Vulkan. GLFW doesn’t do anything about it either, so that is pretty annoying.

I believe in the glorious Wayland future… I just wish it would get here a bit faster

Don’t we all. Let’s hope the current upstream approach to fix this issue gets somewhere sooner than later…

  • All
  • Subscribed
  • Moderated
  • Favorites
  • random
  • lifeLocal
  • goranko
  • All magazines