Zamundaaa

@[email protected]

This profile is from a federated server and may be incomplete. View on remote instance

alavi , to KDE Persian
@alavi@techhub.social avatar

This sddm bug is driving me insane
(No, I don't want to clean my desk)
@kde

video/mp4

Zamundaaa ,

That's just a law of computers, the default arrangement of monitors must always be wrong.

You can just sync your Plasma settings to SDDM though, and it'll use the same output settings as your session

Zamundaaa ,

Just click the button in the sddm settings page

Zamundaaa ,

Yes, and many distros have a polkit rule set up to allow installing or updating without a password. You can likely just copy it from Fedora or sth

Zamundaaa ,

Fedora just has

polkit.addRule(function(action, subject) {
    if ((action.id == "org.freedesktop.packagekit.package-install" ||
         action.id == "org.freedesktop.packagekit.package-remove") &&
        subject.active == true && subject.local == true &&
        subject.isInGroup("wheel")) {
            return polkit.Result.YES;
    }
});

in /usr/share/polkit-1/rules.d/org.freedesktop.packagekit.rules. If you put the same file in there, it should work.

Zamundaaa ,

The only effects relevant for performance are blur and background contrast. Turn those off if you feel the system is slow, maybe increase the animation speed and you're done

Zamundaaa ,

Setting the speed to the max does turn them off

Enable/Disable KWin Scripts depending on current activity?

So, I like working with tiled WMs sometimes though not always. And Polonium is working great for that in Plasma 6. But as I said, I don't want it enabled 24/7. And rather than open settings and toggling it on and off every time, it'd be wonderful if I could harness the power of KDE activities and automatically toggle it on in a...

Zamundaaa ,

You can probably implement it in the script itself, but there's no external functionality to do it

Zamundaaa ,

Many monitors allow you to turn off HDR, they just claim they don't support it to the computer when you do that

Zamundaaa , (edited )

Changing the output config file should work, as long as KWin isn't running while you make the change (in which case the change will just be overridden)

Edit: Also, please make a bug report about this for KWin. It's probably not a KWin issue, but we can usually figure out where it's coming from

Zamundaaa ,

Almost every output setting "may seriously break things" in my experience. Display drivers are sadly quite fragile

pretzel6666 , to KDE
@pretzel6666@c.im avatar

@kde I'm quite happy with the Plasma6 release, but I have number of regression with respect to Plasma5.

The worst, by far, is that lockscreen seems to be broken. I use password or fingerprint, with pam configured to ask for fingerprint after password failure. When I unlock after sleep, the greeter only displays an "unlock" button with an open lock icon. Clicking it does nothing. If I manually trigger the screen locker, I can unlock once, but on the second try it usually hangs.

Second problem: touchpad gestures in wayland. It was already a pain that one could not personalize these actions, but at least the defaults were ok for me (3 finger up/down for desktop grid/present windows). And I could use fusuma for more.
The new defaults hijacks all 3-finger gestures to scroll one virtual desktop up/down left/right which I find useless.

And all those widgets which have not been ported yet, and probably never will. I tried to give a quick look at the two I used most, but it is too far away from my kind of programming.

Zamundaaa ,

It was already a pain that one could not personalize these actions, but at least the defaults were ok for me (3 finger up/down for desktop grid/present windows). And I could use fusuma for more.
The new defaults hijacks all 3-finger gestures to scroll one virtual desktop up/down left/right which I find useless.

You don’t remember the gestures on Plasma 5 correctly. They already used both 3 and 4 finger gestures like they do now, and 3 finger gestures were for virtual desktop switching too.

Zamundaaa ,

No, they were always global. Scrolling on the desktop to change virtual desktops was disabled by default, nothing changed about the three finger gestures

Zamundaaa ,

I’m one of the KWin maintainers, I can tell you with absolute certainty that this hasn’t changed. Maybe you were on Xorg then?

Zamundaaa ,

That’s something apps have to implement, we unfortunately can’t do it globally

Zamundaaa ,

There is no gesture, only horizontal scroll. The app has to scroll when there is content to scroll, and interpret the horizontal scroll as a gesture thing when you can’t scroll anymore. Firefox has that implemented, and every app that wants this to work needs to implement it for itself.

Zamundaaa ,

What you want is now a built in option, you can set the screen saver timeout for when the screen is locked separately from the normal timeout

Zamundaaa ,

I don’t know tbh, I see neither any MR that removed it, nor the option you’re talking about.

kde , to KDE
@kde@floss.social avatar

The Plasma 6 Megarelease is just 2 weeks away! Have you signed up for your local party yet 🥳?

KDE is organizing parties around the globe to celebrate the megarelease. Join us in the celebration with a party in your city or town!

https://community.kde.org/Promo/Events/Parties/KDE_6th_Megarelease

@kde

Zamundaaa ,

Debian stable doesn’t ship our bugfix releases. It is not “stable” in the meaning that normal people use

Zamundaaa ,

Debian ships the latest thing that’s available at the time of tagging, and that is not bug free in any way or form. In the case of Debian 12 that’s Plasma 5.27.5… There were 5 bugfix versions after that. People are experiencing known bugs on Debian stable, not no bugs.

Zamundaaa ,

Virtual desktops are strictly worse for the purpose of separating things like work and gaming

AUA: We are the Plasma dev team. Ask Us Anything about Plasma 6, gear 24.02, Frameworks 6 and everything else in the upcoming Megarelease.

David, Nate, Josh, Marco, Carl, and Niccolò are here ready to answer all your questions on Plasma (all versions), Gear, Frameworks, Wayland (and how it affects KDE’s software), and everything in between....

Zamundaaa ,

A near term plan is to make it so you don’t have to use any Vulkan layer to make it work, by having gamescope use the protocol directly. After that, add support to all the other clients - Mesa, SDL, glfw, mpv, Krita, Chromium and so on

will there be an easy way to get HDR working with the Steam flatpak for the Plasma 6 launch?

You can run Steam in gamescope, doesn’t matter if it’s sandboxed or not.

Zamundaaa ,

Yes

Zamundaaa , (edited )

How is Xorg ready when critical things like all apps crashing when the compositor display server crashes are completely ignored?

Zamundaaa ,

Ugh, I’ve been working on Wayland too much… I meant to write display server. Thanks

Wayland: Font is blurry with fractional scaling

This is now the only thing standing between me and using Wayland as my daily driver. I have an all AMD PC running on two 27" 4k monitors. Setting them up to 200% is good, but too big. Setting them to 175% causes the font to be blurry. Not too blurry, but I can tell and it’s not comfortable to look at for too long. Also, other...

Zamundaaa ,

Yes, that should be fixed in Plasma 6 - at least for Qt apps. For other apps it depends on the toolkit to have support for fractional scaling

question about gitlab merge request (invent.kde.org)

Hello! Yesterday I submitted my first merge request to a KDE software! I forked the repo, applied the edits, committed them and pushed to my fork, and then from gitlab created a merge request. after a few hours, the author pushed something into the master, making my merge request 1 commit behind the master. On the merge request...

Zamundaaa ,

Presumably, your merge request is about merging your fork master branch into the upstream master branch, right?

In that case, you have two options:

  1. Go into the Gitlab settings of your fork, find the setting where branches are protected and disable the protection for your master branch
  2. (the recommended way, at least for future merge requests) always create a feature branch, never work on master in the first place. You can create a branch from what you have right now on the command line with git checkout -b featurename. Then push that branch and create a new merge request for it
Zamundaaa ,

around 1080p resolution

What do you mean by that? Is the biggest resolution you can select in the display settings 1080p, or do things look as big as you’d expect from a 1080p monitor?

Zamundaaa ,

Okay, sounds like a bandwidth related issue. Could you try putting KWIN_DRM_PREFER_COLOR_DEPTH=24 into /etc/environment and rebooting?

Zamundaaa , (edited )

The default is 30. Drivers are supposed to limit the bit depth automatically to make the display work, but DisplayLink is quite shitty so I guess I should not be too surprised. I think I’ll just make KWin force it to 24 for DisplayLink by default to get rid of the problem for everyone

Edit: heh, I already effectively did. It should not happen in Plasma 6 anymore

[Thread, post or comment was deleted by the author]

    •
    Zamundaaa ,

    In a Plasma 6 Wayland session, Qt apps can make that behave as you’d expect, and we implemented it for plasmashell. I don’t know if GTK has any support for that though

    Zamundaaa ,

    SteamOS currently still uses X11 for the desktop mode, so afaik it’s not really possible

  • All
  • Subscribed
  • Moderated
  • Favorites
  • •
  • random
  • All magazines
    •