[-] pretzel6666@c.im 1 points 5 days ago

@mearce You are used to windows being either Maximized or Fullscreen, and these two states being very different things, and changing from one to the other being an hassle, especially exiting from Fullscreen requires touching the keyboard (ESC or f11), or a special button in the interface, hoping the developer made it recognisable. In reality, they are the same thing, with the only difference that Fullscreen hides the menus. If you have the global menu attached to a menu that avoids maximized windows you have unified Fullscreen and Maximized. If on the same panel you also put a widget tonexit from maximized, you also have a universal way to exist from Fullscreen: just take the cursor to the top of the screen and reveal the panel.

14
submitted 1 month ago by pretzel6666@c.im to c/kde@lemmy.kde.social

Hey hey! Looks like @kde Neon has been rebased to 24.04 aka Noble. I started the upgrade right away. The upgrade script crashed halfway because of some problem with apt configuration (probably my fault) but I cleared the error and finished it by hand with "apt dist-upgrade". Reboot, ok.

I only had to purge all that snap+apparmor nonsense that was preventing thunderbird from opening web links and crashing @Vivaldi browser. I really do not understand the point of apparmor outside of server world. How can you be so arrogant to think you'll be able to predict all the possible uses of a consumer software, and decide that it is ok to cause all the other uses to fail with only a cryptic error message buried in the system logs?

[-] pretzel6666@c.im 1 points 5 months ago

@produnis no it isn't ๐Ÿ˜‰

[-] pretzel6666@c.im 1 points 6 months ago* (last edited 6 months ago)

@forrestguid @imecth @cullmann @ohyran @UnityDevice @domi @boredsquirrel @Plopp @soupermkc @minecraftchest1 You have been able to set the icon size for a while, although the interface is a bit minimal (it is in the options of the systray widget) :

[-] pretzel6666@c.im 1 points 8 months ago* (last edited 8 months ago)

@Zamundaaa I don't know if it was a wayland quirks or something esle, but they definitely were not global for me, we're talking two days ago. I would have noticed if desktops kept whizzing around every time I try to maximize a window or pull down the runner, as they do now ;)

[-] pretzel6666@c.im 3 points 8 months ago

@Zamundaaa I did actually mix up three vs four fingers, but what has changed is that the three fingers gestures to change virtual desktop only worked on the bare desktop, while now they are global i.e. they work even if you have an in focus window.

31
submitted 8 months ago by pretzel6666@c.im to c/kde@lemmy.kde.social

@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.

pretzel6666

joined 2 years ago