KDE

This week in KDE: real modifier-only shortcuts and cropping in Spectacle

https://pointieststick.com/2024/04/05/this-week-in-kde-real-modifier-only-shortcuts-and-cropping-in-spectacle/

@kde@floss.social @kde@lemmy.kde.social
#KDE #Plasma #KDEPlasma #Linux #FOSS #OpenSource

Hi,

Maliit is selected in virtual keyboard settings, it shows up when using a KDE app like Dolphin or Konsole, but it doesn't show up when using a non-KDE app like VLC or Discord.

How to fix this ?

Thanks

On one of my machines, I am completely unable to log out. The behavior is slightly different depending on whether I am in Wayland or X11.

Wayland

1. Clicking log out and then OK in the log out window brings me back to the desktop.
2. Doing this again does the same thing
3. Clicking log out for a third time does nothing

X11

1. Clicking log out will lead me to a black screen with just my mouse cursor.

In my journalctl logs, I see:

Apr 03 21:52:46 arch-nas systemd[1]: Stopping User Runtime Directory /run/user/972...
Apr 03 21:52:46 arch-nas systemd[1]: run-user-972.mount: Deactivated successfully.
Apr 03 21:52:46 arch-nas systemd[1]: user-runtime-dir@972.service: Deactivated successfully.
Apr 03 21:52:46 arch-nas systemd[1]: Stopped User Runtime Directory /run/user/972.
Apr 03 21:52:46 arch-nas systemd[1]: Removed slice User Slice of UID 972.
Apr 03 21:52:46 arch-nas systemd[1]: user-972.slice: Consumed 1.564s CPU time.
Apr 03 21:52:47 arch-nas systemd[1]: dbus-:1.2-org.kde.kded.smart@0.service: Deactivated successfully.
Apr 03 21:52:47 arch-nas systemd[1]: dbus-:1.2-org.kde.powerdevil.discretegpuhelper@0.service: Deactivated successfully.
Apr 03 21:52:47 arch-nas systemd[1]: dbus-:1.2-org.kde.powerdevil.backlighthelper@0.service: Deactivated successfully.
Apr 03 21:52:48 arch-nas systemd[1]: dbus-:1.2-org.kde.powerdevil.chargethresholdhelper@0.service: Deactivated successfully.
Apr 03 21:52:54 arch-nas systemd[4500]: Created slice Slice /app/dbus-:1.2-org.kde.LogoutPrompt.
Apr 03 21:52:54 arch-nas systemd[4500]: Started dbus-:1.2-org.kde.LogoutPrompt@0.service.
Apr 03 21:52:54 arch-nas ksmserver-logout-greeter[5553]: qt.gui.imageio: libpng warning: iCCP: known incorrect sRGB profile
Apr 03 21:52:54 arch-nas ksmserver-logout-greeter[5553]: kf.windowsystem: static bool KX11Extras::compositingActive() may only be used on X11
Apr 03 21:52:54 arch-nas plasmashell[5079]: qt.qpa.wayland: eglSwapBuffers failed with 0x300d, surface: 0x0
Apr 03 21:52:55 arch-nas systemd[4500]: Created slice Slice /app/dbus-:1.2-org.kde.Shutdown.
Apr 03 21:52:55 arch-nas systemd[4500]: Started dbus-:1.2-org.kde.Shutdown@0.service.
Apr 03 21:52:55 arch-nas systemd[4500]: Stopped target plasma-workspace-wayland.target.
Apr 03 21:52:55 arch-nas systemd[4500]: Stopped target KDE Plasma Workspace.
Apr 03 21:52:55 arch-nas systemd[4500]: Requested transaction contradicts existing jobs: Transaction for  is destructive (drkonqi-coredump-pickup.service has 'start' job queued, but 'stop' is included in transaction).
Apr 03 21:52:55 arch-nas systemd[4500]: graphical-session.target: Failed to enqueue stop job, ignoring: Transaction for graphical-session.target/stop is destructive (drkonqi-coredump-pickup.service has 'start' job queued, but 'stop' is included in transaction).
Apr 03 21:52:55 arch-nas systemd[4500]: Stopped target KDE Plasma Workspace Core.
Apr 03 21:52:55 arch-nas systemd[4500]: Stopped target Startup of XDG autostart applications.
Apr 03 21:52:55 arch-nas systemd[4500]: Stopped target Session services which should run early before the graphical session is brought up.
Apr 03 21:52:55 arch-nas systemd[4500]: dbus-:1.2-org.kde.LogoutPrompt@0.service: Main process exited, code=exited, status=1/FAILURE
Apr 03 21:52:55 arch-nas systemd[4500]: dbus-:1.2-org.kde.LogoutPrompt@0.service: Failed with result 'exit-code'.graphical-session.target/stop

I've filed an upstream bug for this but I was wondering if anyone else here was also experiencing the same issue.

Hey, I've been daily driving wayland since plasma 6 released. The improvements are stunning, and it's actually responsive on my multi monitor setup.

Main problem I've been having is with my drawing tablet. It works fine, but the touch/scroll wheel doesn't register. I can't find anything in the settings about it, so my first assumption is it's just not implemented yet. But no matter how many searches I do I can't find anyone with the same problem.

I only have this problem in wayland, in X11 it functions just as intended. It's not a huge issue, it just really screws with my muscle memory. I'd just love to be able to use my tablet properly with wayland so I don't have to switch back to the laggy mess that is X11.

Tablet: Wacom Intuos Pro
Distro: Garuda Linux (arch-based)
GPU: Nvidia RTX 3060
Plasma version: 6.0.3-1
libinput version: 1.25.0-1

If this is the wrong community or if any other info is required just let me know. I originally posted on !kde@lemmy.ml but then realized that community was mostly dead.

Edit: formatting

Edit 2: HW Probe

Using dices in elementary school to play mathematical games allows to train logic and strategy. Before that, dice patterns need to be learned. "Number with dice" helps pupils in preschool to quickly count the dots present on a dice and offers practice to train dice patterns recognition, preparing children for the elementary school.

I got an update today for qt5 webengine and I was wondering if I should update it or just remove it since we are on qt6/plasma 6?

⚠️ BEWARE ⚠️ Scammers are targeting Kdenlive users

Scammers are still circulating fake emails targeting #Kdenlive users and content creators.

Remain vigilant and be cautious of any unsolicited communications claiming to be affiliated with us. We DO NOT send any emails offering promotional opportunities, advertising integrations or any promotional collaboration.

Our communications are done through Mastodon, Twitter and through emails from kde.org and kdenlive.org domains.

@kde

What's going on here? What's that smell? Smells like... empanadas...

@kde@lemmy.kde.social

We write all recipes for our juiciest empanadas in our #Marknote notebooks. Version 1.1.0 available now!

https://carlschwan.eu/2024/04/01/marknote-1.1.0/

Flatpak coming today!

@kde@lemmy.kde.social

You like tasty? Cos KDE got tasty!

https://tube.kockatoo.org/videos/watch/c71ac1ee-f29b-47d3-a067-78b5ea232ae2

@kde@lemmy.kde.social

Just felt like lemmy users might like reading this post too about my development work for Plasma 6 (and beyond!). It's a bit all over the place because I am bad at writing but anyway, hope you find it interesting nonetheless.

Visit our new brick and mortar store at Entre Ríos 1485 in Rosario, Santa Fe!

https://maps.app.goo.gl/fTxksYfywcDmLLZs9

@kde@lemmy.kde.social

Amarok was KDE's flagship music player during the KDE3 and Plasma 4 days. For Plasma 5, a new music player called Elisa was created with Kirigami which is the current KDE flagship music player. The last full release of Amarok was 2.9.0 in 2018, still targeting Qt4. A Plasma 5 port was started with the intention of being released as Amarok 3.0, but despite a usable alpha 2.9.71 release in 2021, the full 3.0 release was never completed. Outside of the occasional odd pull request, the project was essentially dead and was listed as unmaintained by apps.kde.org.

Two weeks ago, occasional contributor Tuomas Nurmi, author of over a third of these pull requests, made a push to become an Amarok maintainer, starting this thread in the mailing list: https://mail.kde.org/pipermail/amarok-devel/2024-March/014748.html

In the thread, Tuomas expresses his desire to revive Amarok. He believes a second alpha for 3.0 can be released in mid-April and a full Plasma 6 port could be completed within 2024 after the release of 3.0. Tuomas has since created a fair amount of merges and fixes in preparation for 3.0 and has shown no sign of stopping.

This is very exciting news. For many, Elisa isn't a satisfying replacement for Amarok. It simply doesn't come close to matching Amarok's power and features. It also has the drawback of being a convergent application, meaning compromises have to be made to make the interface work well on smartphones.

It's also victim to the many drawbacks of Kirigami. Theming is worse since Plasma has to convert QtWidget themes to QtQuick themes, which works great for Breeze, but meh for everything else. There is no good equivalent for KStandardAction/QAction, KHamburgerMenu or KStandardShortcut. Any Kirigami app that wants customizable toolbars and shortcuts need to go out of their way to implement them, while QtWidgets apps just get them for free. You also don't have a good QDockWidget equivalent that I know of. Apps that do bother to reimplement some of these features (Haruna is the only one I know of) still don't have toolbar customization to nearly the same extent QtWidgets apps do. Most Kirigami apps don't bother with this at all and lose a lot of customizability in the process. Elisa is not Haruna, tho. There is no shortcut customization, there is no toolbar to customize and that hamburger menu can't be turned into a menubar.

For years, the solution was Strawberry, a fork of Amarok still under active development. Thing is, Strawberry is a fork of Clementine, itself a fork of Amarok 1.4. That's old. That's 2008 Amarok, not 2018 Amarok. Clementine had its first release in 2010, when Amarok was still going strong. It was for good reason, Amarok 2.0 introduced a very divisive redesign of the interface, which prompted a fork. But this means 2.0+ Amarok and Strawberry are actually very different beasts. For those who were using Amarok 2.9, switching to Strawberry meant switching to a new music player, making it far from an ideal successor. So I'm very much excited for the return of Amarok, the best music player KDE has had.

KDE Neon users please note: Neon is NOT affected by the xz security issue. You do not have to take any precautions.

@kde@lemmy.kde.social

Thx to all devs ;)

This week in KDE: looking forward towards Plasma 6.1

https://pointieststick.com/2024/03/29/this-week-in-kde-looking-forward-towards-plasma-6-1/

@kde@floss.social @kde@lemmy.kde.social
#KDE #Plasma #KDEPlasma #Linux #FOSS #OpenSource

Hi, Arch Linux KDE 6.0.2 here, looks like Elisa can't sort album by "originalyear" but only by "year"; this mean album in the same year appears in a random order.

I have been searching with no luck, where can I find documentation for the system tray icons?

I am aware that now in Plasma 6 they come from the Icon theme, but how are they mapped? How do I know which file each tray entry is looking for on my Icon theme? What about cases like volume, Bluetooth, network... we use to have a single file for each that contained the different -states- they could be.

I tried just dropping my plasma theme icons on my Icon theme and got some weird results, for instance Bluetooth now shows the network icon, some other icons did not change at all.