KDE

I'm working on a project to create an LED ring that lights up based on my active notifications in KDE Plasma. I'm wondering if there's a way to access the current list of active notifications without having to dive into the KDE source code.

Is there an existing API or method for grabbing this info? Any tips would be greatly appreciated!

How does it work? I mean I have several Containments numbers like: [Containments][8] ... [Containments][23] ... I get that some are for the background of plasma where the wallpaper goes, some are for panels

But overtime it seems it gets messy, with repeated background ones and panels.

I guess I want to know how plasma interprets it, whats the logic for these IDs and why as I change my plasma settings the amount of containers increase even if I don't add more panels, screens etc.

Fedora on Apple Silicon, with Plasma and Wayland?

That's an impressive feat! Congrats to all the team!!! 🎉 😍

https://social.treehouse.systems/@AsahiLinux/111607682159825520

@kde@lemmy.kde.social

When we go to Konsole main menu » Settings » Toolbars Shown and check or uncheck any option, where does it get stored?

I checked ~/.config/konsolerc and it was not stored there.

I actually toggled them and checked all files in my system that were changed at the same time I toggled them and I still could not find.

My ~/.local/share/kxmlgui5/konsole/ has no files in it, both on Arch and Void Linux. I also tried creating a partui.rc file as well as konsoleui.rc to see if it would get populated when changing which toolbars are shown and which aren't but it did not work. My KDE Version is 5.27.10 on both distros.

I create a new KDE style called Brise.

This style contains some tweaks to the default Breeze style like larger and configurable border radius, a new tab style, and more.

https://carlschwan.eu/2023/12/19/announcing-brise-theme/

@kde

Brise theme is yet another fork of Breeze. The name comes having both the French and German translations of Breeze, being Brise.

I can't imagine there is but I'm wondering if I am missing something. I use GeForce Now and unfortunately it does not work in Plasma Wayland (issues with input redirection). Is there any problem with logging into an X11 session whenever I want to use that but using Wayland generally?

Mark your calendars! conf.kde.in 2024 coorganized with CoFSUG is happening from 2-4 February at COEP Technological University, Pune.

The Call for Proposals is now open! Submit your ideas for talks and workshops.

https://kde.org/announcements/conf-kde-in-2024/

#confkdein2024 #CfP #India #conference

@kde@lemmy.kde.social

Thanks to the help of our contributors the current state of Kate for the upcoming first Qt & KF 6 release looks very promising. For more information read this post.

Plasma and apps for mobile also getting overhauled for 6.

It's not only Plasma on the desktop that is getting a new version, as Devin Lin explains in his blog post,

https://espi.dev/posts/2023/12/plasma-mobile-towards-6/

developers are working hard on getting #PlasmaMobile 6 ready for the #megarelease scheduled for February.

#Plasma6

@kde@lemmy.kde.social

Calling all KDE users and new contributors: Season of KDE has started!

Work on kool KDE projects, contribute to Free Software, learn new technologies, become part of a team.

Participating is easy: Check out the #SOK24 ideas page

https://community.kde.org/SoK/Ideas/2024

Pick a project, and send a proposal. You have until Monday 8 January 2024!

For more details and links you need, please read this very carefully:

https://discuss.kde.org/t/call-for-proposals-want-to-start-contributing-to-kde-its-time-to-submit-proposals-for-our-mentorship-program-sok24-deadline-8-jan

#SOK #SOK2024 #mentorship #freesoftware #opensource

@kde@lemmy.kde.social

While cutting edge testing distribution such as Fedora are going Wayland only and the proponents of such move say that this push is required to shake things out. I would like to highlight some of the things which are not there yet on the graphic tablet configuration front on plasma wayland. Although the basic support for the tablet is provided through libinput and those who are content with the default will have no issues, those who rely on configuring the tablet will have hard time on wayland.

I was told that fedora making this move will help us get up to speed and it will pressurize developers to fix broken and non implemented things in plasma wayland soon. But sadly I do not see this happening in the graphic tablet configuration side of things. Hope this post gets the attention from the developers and they pay some attention towards the needs of us less lucky people who do not know to code it ourselves.

I am not sure if these deficiencies will be fixed in plasma 6 release as most of them are marked as wish list or extra things. Thus making the transition from plasma 5 to plasma 6 a regression for people depending on these things. If you compare the current graphic tablet configuration section on X11 to that of plasma wayland you will understand what I am saying.

Graphic tablet support bugs

• No way to map a portion of the tablet are to the screen - Some people have large tablet and sometime they want to map a portion of the tablet to the monitor - bug report - https://bugs.kde.org/show_bug.cgi?id=457703. Moreover the UI for mapping tablet area and its buttons is slightly inferior to the UI of the same functionality in X11 KCM. - Bug report - https://bugs.kde.org/show_bug.cgi?id=477750

• No way to create multiple profile of the tablet configuration, so that artist can choose different configuration like shortcuts , pen pressure etc for different workflow like inking a comic or doing vector art - Bug report - https://bugs.kde.org/show_bug.cgi?id=477671

• No way to fine tune pressure curve of the tablet, various people draw with varying pressure some people draw with heavy hand some use light touch, configuring pressure curve helps artist to get nice lines. - bug report - https://bugs.kde.org/show_bug.cgi?id=457705

• Often graphic tablets have a touch strip or ring but on plasma wayland there is no way to assign shortcut to touch rings - bug report - https://bugs.kde.org/show_bug.cgi?id=477752

• Related to the above some tablets allow users to switch the modes of the touch ring for example you can click a button and change the mode from one set of shortcuts like scrolling to another set of shortcut like changing hue or zooming in and out. but this is not available in plasma wayland - https://bugs.kde.org/show_bug.cgi?id=477787

• Creative applications often have use of single modifier shortcuts, artists map this to their pen buttons for example holding ctrl to colour pick while painting but this is not possible on plasma wayland - https://bugs.kde.org/show_bug.cgi?id=461259

• There is no way to calibrate a display tablet so that there is no wierd offset - https://bugs.kde.org/show_bug.cgi?id=476982 this is in the works and there is an open MR by an awesome KDE contributor but it will probably be in 6.1

• There is no way to switch between absolute and relative mode of the graphic tablet - bug report - https://bugs.kde.org/show_bug.cgi?id=477898

• There is no way to assign mouse click presses to pen button as shortcuts, For example you want to change the default and assign a different button on a pen to do middle mouse click to pan the canvas in krita it won't accept middle mouse click as a shortcut- https://bugs.kde.org/show_bug.cgi?id=457636

• The pointer for the graphic tablet is a cross in plasma wayland, it doesn't even change to resize handle cursor or any other things depending on the context. So if you want to resize a window with your pen it will be troublesome to use this pointer. - https://bugs.kde.org/show_bug.cgi?id=477570 I am not sure how this was gone unnoticed until now.

I hope some kind volunteer developer notices these shortcomings which were possible earlier on X11 and are not possible on plasma Wayland and help us artists types who rely on these features to use and enjoy wayland like it is intended without worry. Some of these things were possible on X11 for a decade and yet wayland takes us back to square 1.

Wow, World of Goo 2 is happening!

Check out the official trailer made with #Kdenlive.

https://www.youtube.com/watch?v=6rGroEFNEpI

Congrats TomorrowCorp and 2D Boy.

@kde

@kde @kde nostalgia

Pay your own tribute to a desktop that once ruled the 90s Unix world with Commonality, the fourth and final (for now) entry in Off-Theme:

https://quickfix.es/2023/12/off-theme-presents-commonality/

#Plasma #theming #desktop #Linux

@kde@lemmy.kde.social

digiKam, KDE's powerful photo management application, releases version 8.2.0.

This version brings better support for more languages (up to 61 in the works), and an improved version on Windows.

Look forward to automatic tagging based on content analysis and deep-learning. This feature is currently in pre-production.

https://www.digikam.org/news/2023-12-03-8.2.0_release_announcement/

@kde@lemmy.kde.social

#photo #management

Hello! I want to change keyboard layout from command line, but online I only found this, but unfortunately qdbus org.kde.keyboard /Layouts setLayout "xyz" does no longer work, and looking for "keyboard" or "layout" in keyboard viewer gave 0 results... any tips?
thanks in advance!

I've been wanting to use the Falkon browser as my daily driver because I like the integration with the Plasma desktop and it works quite well for most things, but I've been hesitant to do so because there are so few extensions and the only privacy-focused one is the AdBlock. I've tried using GreaseMonkey scripts, but half of the few privacy-focused scripts I've found just don't work and I'm not good enough with scripting to really figure out why. I've set what I could in the Preferences menu for privacy, but I'm wondering if there is any way to access other settings to do things like disable WebGL and/or otherwise block trackers and prevent fingerprinting? If I can set it up to be reasonably close to Brave or LibreWolf privacy-wise, I'd be happy to use it more.

Hello!

Do you hate the watermark preview banner?

Add the text HideDesktopPreviewBanner=true just after [General] in the file ~/.config/kdeglobals. You will have something as the following:

[General]
HideDesktopPreviewBanner=true

Better for OLEDs displays, stylish, auto-suspend all-blacks displays, etc.

Src: https://invent.kde.org/plasma/plasma-workspace/-/commit/b15d9f41f7f41210b1dd5a78dc1b1894bd40c3dd#16f843a94440a858a2387e36472454ab5685e179_193_196

I'm not sure if this is normal, but it seems that Plasma 6 (Wayland) feels overall slow on my laptop with Intel i5-6200U.

Operating System: KDE neon Unstable Edition
KDE Plasma Version: 5.90.0
KDE Frameworks Version: 5.246.0
Qt Version: 6.6.0
Kernel Version: 6.2.0-37-generic (64-bit)
Graphics Platform: Wayland
Processors: 4 × Intel® Core™ i5-6200U CPU @ 2.30GHz
Memory: 15.5 GiB of RAM
Graphics Processor: Mesa Intel® HD Graphics 520
Manufacturer: Dell Inc.
Product Name: Inspiron 5559

I only got this laptop recently from a friend so I have yet to test on X11 session. The only other time I've spent using Plasma was on a RTX 3060 Ti in a VM so it didn't feel as slow.

Is that normal?

Created bug report 477959.