KDE

I have a very cool Core 2 Duo laptop here that runs Linux Mint.

And it is pretty aweful. Would love to put Fedora Kinoite (Atomic KDE) on there, manual upgrades on shutdown, minimal set of apps.

But I dont know how well Plasma works on such old hardware. It is pretty bloated and messy sometimes, Dolphin and plasmashell are my biggest worries (the whole panel and widget stuff is sooo complex).

Has anyone tried Plasma?

An alternative would be LXQt with KWin once 6.1 comes out and it has full Wayland support.

I'm using task switcher with Recently used sort order, but I still feel unsure if it's the same behavior

Great to see that krfb-virtualmonitor is usable with wayland! So, kde is compatible with the wireless pc-on-tv feature on samsung tv.

My secondary head for my couch-office!

I was working on some stuff on my PC and stepped away for a bit, and on returning noticed notifications on it that some files had been downloaded via KDE Connect from my phone. I was using my phone at the time, and didn't send the files.

I know that you can quietly download files from a phone with its paired device (i.e. no notification on the phone, nor prompting permission) from allowed directories, but these files weren't from those directories, so...What may have happened here?

Glitched notifications, or something else?

Also, the downloaded files weren't anywhere on my PC, so... 😕

edit:
I found an issue report I think may be what I was seeing: KDE Connect spams the desktop with a torrent of old notifications.

This is an issue that I know for a fact that is not specific to plasma, but I came here to ask for help since I run Plasma and I'm hoping that there is something I can change on the DE to fix it. Caps-lock is very slow and causes THis ISsue, and it is driving me crazy. I'm the person who can never learn how to use the shift to capitalize my letters and use caps-lock religiously. I have been using this fix on xorg, but it doesn't work on wayland, and I'm now back to square one. Any kind soul here knows how I can fix this issue? Thank you

Does that exist ?

Thanks

MBition, the company that designs and implements infotainment systems for Mercedes-Benz, has become a KDE patron.

MBition uses KDE technologies and developers' know-how to create attractive and responsive interfaces that make Mercedes vehicles easier to drive and safer for their occupants.

@[email protected]

https://ev.kde.org/2024/05/07/mbition-becomes-kde-patron/

I've seen a lot of conflicting information on the topic, so I'm curious if there is an updated official policy that I haven't been able to find.

I wrote a blog post about my experiences on daily driving Plasma Mobile

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 particular activity and off on any other. Is it possible?

I'm moving from ChromeOS to Manjaro. I want to put the Task Manager on the right edge of the screen, but don't see how to do this. I'm pretty sure this was possible a long time ago.

Running KDE Plasma 5.27.11 and Wayland.

The Adwaita Icon Theme no longer follows the FDO icon naming spec breaking KDE applications on Fedora 40 Workstation and Co. See the concrete state of the issue in the linked article.

I have a wacom graphics tablet that I want to use, but the builtin drivers of plasma 6 do not have enough customizability for me/don't do what I want them to, so I wanted to use the opentabletdriver package, which worked well for me on plasma 5, but the builtin driver is still active even when opentabletdriver is and I then have 2 cursors (the one from the plasma 6 drivers is invisible tho) at different positions and am effectively unable to use the tablet. So I was wondering how to disable the builtin driver, I looked it up but all I found was the same question on reddit, so I thought I'd try asking here.

Another problem is that I also just don't have the settings tab for the tablet on X11, only on the Wayland session, the driver is still active in X11 but with default settings, giving me effectively 1/4 of the tablet for my primary monitor.

I can't really use Wayland, as of now my nvidia card still causes a lot of flickering in games.

UPDATE: I did a fully system update today and there are some changes now, plasma's driver does not interfere with opentabletdriver driver on the X11 Session anymore.

The Wayland Session does not detect my tablet on it's own at all anymore, however when I start the opentabletdriver daemon with the tablet in artist mode, plasma detects this and hijacks it, making any settings in the opentabletdriver ineffective (-> the Settings in the kde Settings also don't seem to do anything). However by Setting the driver to absolute mode (which I believe to just move the mouse to the right position) it works like it normally does in absolute mode.

conclusion: After an update everything works on X11 and artist mode is broken on Wayland (at least for me), still an option to disable the builtin driver would be nice

edit: waylands builtin driver got layered on top of the opentabletdriver, setting it to all screens solves this issue since it does not further transform opentabletdrivers input, however I could not get my buttons to work. My guess is that opentabletdriver takes the input and converts it, but wayland tries to do so again, resulting in invalid input, but I don't know for sure.

This week in KDE: megabytes and gigabytes for all

https://pointieststick.com/2024/04/26/this-week-in-kde-megabytes-and-gigabytes-for-all/

@[email protected] @[email protected]
#KDE #Plasma #KDEPlasma #Linux #FOSS #OpenSource

Look! No ads!

Take back control. Choose Plasma.

https://kde.org/plasma-desktop/

(Microsoft starts testing ads in the Windows 11 Start menu: https://www.theverge.com/2024/4/12/24128640/microsoft-windows-11-start-menu-ads-app-recommendations)

#Windows #Windows11 #Plasma6 #Microsoft

@[email protected]

cross-posted from: https://floss.social/users/akademy/statuses/112246259874693015

The #Akademy2024 Call for Participation (CfP) is now open!

Don't miss the opportunity to talk about your project and present your ideas to the community! The CfP will close on 24 May 2024.

Find more information and submit your talk at https://akademy.kde.org/2024/cfp/

@[email protected]

We have now reached (and surpassed) 1000 Supporting Members! 🎉

But as KDE grows and takes on more and more ambitious projects, the effort to raise funds also increases.

If you would like to help, please consider becoming a supporting member and get your name inscribed in Plasma's Hall of Fame:

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

Or, if you prefer, you can make a one time donation:

https://kde.org/community/donations/
https://kde.org/fundraisers/yearend2022/

@[email protected]
#donations #charity

cross-posted from: https://floss.social/users/LabPlot/statuses/112229009522045503 - [email protected]

Support for #MCAP format is coming to #LabPlot 🚀🙂

@[email protected]

#MCAP is a standardized container file format for storing heterogeneous robotics data.

See how to read and plot #Robotics (#Sensor) data with #LabPlot.

➡️ https://www.youtube.com/watch?v=kK5QbFi90wA

#DataAnalysis #DataScience #Data #DataViz #Science #Statistics #FOSS #FLOSS #OpenSource

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.

@[email protected]

Or is it just buggy?