KDE

cross-posted from: https://lemmy.ml/post/7492459

"Chill your Champagne bottles – it’s official: the KDE Plasma 6.0 + KDE Frameworks 6.0 + KDE Gear 24.02 Mega Release™ that will take KDE software to the next level is going to happen on 28th February 2024! Let’s have a look at what I’ve been up to in the past two months, again working mostly on either Qt itself or dealing with its behavior changes on the application side."

Cool KDE Plasma Tip: Quickly access task manager apps with [Meta] + [number]

@kde@floss.social's task manager usually lives in the panel located by default at the bottom of your desktop (see attached image).

Quickly open or display apps shown in the task manager by holding down the [Meta] (aka "Windows") key and hitting one of the number keys at the top of your keyboard.

Reach the first app on the left with [Meta] + [1], the second from the left with [Meta] + [2], etc.

#Plasma #KDE #tip

@kde@lemmy.kde.social

We are nearing the halfway mark on our Plasma 6 drive to get 500 Supporting Members

Will you push us over that line?

https://kde.org/fundraisers/plasma6member/

#Plasma6 #fundraiser

@kde@lemmy.kde.social

Ever since the renaming Mercuro starts and immediately crashes. Has anyone else experienced that?

The new KDE PIM report is out, bringing news of improved email, calendaring, contacts, and travel apps.

Your favorite email, calendaring, contacts, and travel utilities gained offline AI capabilities, PGP encryption and signing for calendar invitations, an improved look for Merkuro and much more.

https://kontact.kde.org/blog/2023/2023-11-01-kde-pim-september-october-2023/

@kde@lemmy.kde.social

THE KUBE IS BACK!

https://invent.kde.org/plasma/kdeplasma-addons/-/merge_requests/188

@kde@lemmy.kde.social

#Plasma6

To show the panel above a game window, without Firefox, Dolphin windows, the start menu etc popping up alongside it?

I'm using the 'Move keyboard focus between panels' keybind as a non-reliable workaround right now.

Hello!

I'm still using X11, and one of the things that's keeping me there is that I make heavy use of a launch-or-focus script, so that I hit a certain hotkey and no matter what a browser/chat/editor/terminal/file-manager/etc. shows up focused on my current desktop.

In the world of Wayland, this isn't so easy. If this can be recreated at all, I think it'll have to be made to rely on some sort of interface to Kwin.

I don't think it's possible now, but might it be in the future?

Here's my script, let's see if the lemmy interface mangles it (EDIT: yes, the last character should be an ampersand, not &):

#!/bin/zsh -ex

# -- Usage --
# ./toggle_window.zsh LAUNCH_CMD [ WM_CLASS [ CHECK_CMD ] ]

# -- Defaults --
# WM_CLASS and CHECK_CMD each default to the value of LAUNCH_CMD

# -- Examples --
# ./toggle_window.zsh dolphin
# ./toggle_window.zsh wezterm-gui org.wezfurlong.wezterm
# ./toggle_window.zsh firefox firefox firefox-bin
# ./toggle_window.zsh \
#   'flatpak run --branch=stable --arch=x86_64 --command=telegram-desktop --file-forwarding org.telegram.desktop' \
#   telegram-desktop telegram-deskto
# Yes, "telegram-deskto" without a final p. Hmm.

# -- Dependencies --
# - procps (pgrep)
# - wmctrl
# - x11-utils (xprop)
# - xdotool

# -- TODO --
# - wayland

launch_cmd=(${(z)1})
wm_class=${2:-$1}
check_cmd=${3:-$1}

if [[ $(xprop -id $(xdotool getactivewindow) WM_CLASS) =~ \"$wm_class\" ]] {
  xdotool getactivewindow windowminimize
} else {
  wmctrl -xR $wm_class || true
}

pgrep -u $USER -x $check_cmd || exec $launch_cmd &

Check out Off-Theme, a series that showcases creative global themes to spice up the look and feel of your Plasma desktop.

In this intro, we guide you through the process of preparing your system for the eye-popping #themes of upcoming episodes.

https://quickfix.es/2023/10/going-off-theme-the-prologue/

@kde@lemmy.kde.social

#plasma #customization #desktop #Linux

Every time I try to create a new post in this community I notice that the post is never created, it keeps on loading forever.

Getting a little more technical, when I use the browser's developer tools analyze the request, I notice that I get a "language not supported" error message with a 400 status code on the response.

Is this intentional or is this a bug?

I use Endeavour OS (Arch based btw) and I've noticed that when I select to choose a new image as my wallpaper, it doesn't support the .webp format.

Does plasma desktop not support .webp images as wallpaper? Am I doing something wrong?

Can one post app-making requests here?

I don't have app inquiries - just asking 😄

I want to start Konsole in Split View which is possible using the --layout command but then also run a command like htop in one of the sessions. How do I do that?

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 UI elements are blurry, too regardless of the scaling. Although those elements aren't defaults, but still blurry and look out of place. For example, the oxygen window decoration buttons are very blurry. Hovering over those buttons shows a big blurry and empty box.

Anywho, I'm pretty sure the whole KDE team is aware of this, but my question is, is this being addressed in plasma 6? This is literally the only thing holding me back from Wayland. I love how snappy it is. Things are way quicker than x11. I want to use it. Thank you

Hello! I'm trying to do this:

but I can't seem to find a "good" way to do it:

if I just place it in the Kirigami.Page it is displayed, well, in the page, as in the image above.

Kirigami.ApplicationWindow {
   pageStack.initialPage: Kirigami.ScrollablePage {
      Kirigami.SearchField { // TODO move in the page header
         id: searchField
         Layout.fillWidth: true
      }
   }
}

if I place it in the header of the window it is displayed before the actual header even:

Kirigami.ApplicationWindow {
    header: Kirigami.SearchField { // TODO move in the page header
         id: searchField
         Layout.fillWidth: true
      }
   pageStack.initialPage: Kirigami.ScrollablePage {
     
   }
}

if I place it just before the Page it goes inside the header, but all aligned to the top instead of nicely in the center:

Kirigami.ApplicationWindow {
    Kirigami.SearchField { // TODO move in the page header
         id: searchField
         Layout.fillWidth: true
      }
   pageStack.initialPage: Kirigami.ScrollablePage {
     
   }
}

what is the correct way of doing this?

thanks in advance!

Krita artist and contributor, David Revoy, gets massive exhibition in mall

@davidrevoy, creator of the popular Pepper and Carrot webcomic (https://www.peppercarrot.com/), has been honored with an exhibition of his work in a French mall. Massive murals with images from his comics are displayed all over the shopping center at Plérin, Brittany.

David is an active @Krita contributor, and will be signing copies of his work at the mall on Saturday, the 4th of November.

https://www.davidrevoy.com/article992/large-exhibition-in-plerin-france

@kde@lemmy.kde.social

I have been curious for some time now if there is any difference between them besides one being located in "Display Configuration" and the other in "Power Management". They seem a bit redundant to me so as if the folks from the Plasma team weren't sure where to put and how to name it, lol. >.<

Where is the source code for #KDE Klipper hosted? The link in the handbook was broken. @kde

Hello folks! I’ve been having this issue seen in the screenshot. I get this Wayland window and krunner and other things run in there. After a time I even get the login screen inside the wayland window. If I close it I lose krunner, alt-tab, and other keyboard shortcuts.

Not sure how this is happening or how to make it go away. I did try Wayland at one point but it wasn’t quite working out for me and since I reverted back to X11 I get this issue.

If anyone’s wondering, my main issue with Wayland was that it wasn’t setting the DISPLAY and WAYLAND_DISPLAY environment variables for some reason, and this would cause all kinds of software like Steam and Firefox to not even launch. I tried setting them manually but that didn’t go do well either.

Edit: Thank you all! With your help I managed to find and fix it - it was my fault due to a systemd override launching a service after kwin_wayland.

[Unit]
Requires=plasma-kwin_wayland.service
After=plasma-kwin_wayland.service
[Install]
WantedBy=graphical-session.target

That was the issue. Remved the override and everything works!
I even tried Wayland again and now the display variables are defined correctly from the get go and everything works - although this has been on again off again so it might stop working at one point.