This KDE Bug Breaks The COSMIC Desktop??

Summary

The video script discusses an issue with KDE Plasma's shortcut system, which incorrectly generates local desktop entries that can override global ones, causing the app tray in the COSMIC desktop to malfunction. The creator suggests a simple fix, such as renaming local commands to avoid conflicts, but questions the reliance on desktop files for shortcuts. They also highlight that other window managers manage shortcuts without this issue, implying a design flaw in Plasma. The video ends with a call for feedback and support through Patreon and other platforms.

Takeaways

• 😕 The speaker criticizes the KDE Plasma desktop environment for having accumulated 'cruft' over 30 years, leading to design decisions that are hard to understand or fix.
• 💻 A specific issue is highlighted where a design flaw in Plasma's shortcut system is causing problems for the COSMIC desktop environment.
• 🔗 The Plasma shortcut system allows for the creation of arbitrary commands, which can lead to conflicts with existing desktop entries (.desktop files).
• 🛠️ The problem arises when a local desktop entry is created that overrides a global one, causing applications to launch with incorrect commands.
• 📁 The speaker demonstrates that desktop entries are generated in a shared location, which can lead to conflicts between different desktop environments.
• 🔑 A potential quick fix is suggested: ensuring that local shortcuts are named uniquely to avoid conflicts with global shortcuts.
• 🤔 A deeper question is raised about why Plasma relies on desktop files for its shortcut system when other window managers do not.
• 🔍 The speaker has reported the issue to the KDE Plasma developers and suggests that a better long-term solution would be to redesign the shortcut system.
• 👀 The script also points out that the issue is not consistent across all applications within COSMIC, indicating that there might be workarounds within the COSMIC environment itself.
• 📢 The speaker invites viewers to share their thoughts on the issue and whether they can see any logic behind Plasma's design that the speaker has missed.

Q & A

What is the main issue discussed in the script related to KDE Plasma and COSMIC desktops?

The main issue is that a design decision in KDE Plasma is causing the app tray to malfunction in the COSMIC desktop environment. This is due to Plasma's shortcut system generating local desktop entries that can override global ones, leading to incorrect applications launching when pinned to the app tray.

How does the KDE Plasma shortcut system work with arbitrary commands?

In KDE Plasma, users can bind arbitrary commands to keyboard shortcuts. These commands are saved as desktop entries in a specific directory, which are then used to launch applications or execute scripts when the shortcut is activated.

What is a 'desktop entry' or 'desktop file' as mentioned in the script?

A desktop entry or desktop file is a file that contains metadata and launch information for applications in a graphical environment. These files are used by application launchers to display and start applications.

Why does the script mention that the problem with the app tray in COSMIC is 'annoying but easy to work around'?

The problem is considered 'annoying but easy to work around' because while it causes inconvenience, it does not prevent the user from launching applications through other means, such as using the application launcher directly.

What is the proposed quick fix for the issue of local overrides in the KDE Plasma shortcut system?

The quick fix proposed is to avoid generating local overrides by ensuring that the first command is named with a suffix like 'command-name-1.desktop' instead of 'command-name.desktop', preventing conflicts with global desktop entries.

What is the long-term solution suggested in the script to address the reliance on desktop files in the Plasma shortcut system?

The long-term solution suggested is a redesign of the Plasma shortcut system to not rely on desktop files, which would prevent issues with local overrides and make the system more robust and consistent with other window managers.

Why does the script mention that other window managers do not have this issue with shortcut systems?

The script mentions that other window managers do not have this issue because they have designed their shortcut systems without relying on desktop files, thus avoiding the conflicts and overrides that Plasma is experiencing.

What is the significance of the 'x-kde-globalexcel-command shortcut equals true' line mentioned in the script?

The 'x-kde-globalexcel-command shortcut equals true' line suggests a method to differentiate global shortcuts from local ones. KDE uses this to determine whether to use the global or local desktop entry, which COSMIC could also implement to avoid the issue.

How does the script describe the behavior of the shortcut system when multiple commands are bound?

The script describes that when multiple commands are bound, the first command generates a desktop entry without a suffix, which can override global entries. Subsequent commands are given suffixes like '-2', '-3', etc., which can lead to the wrong application launching when pinned to the app tray.

What is the user's call to action at the end of the script regarding the issue with KDE Plasma and COSMIC?

The user encourages viewers to share their thoughts on the issue, especially if they believe there is a sensible reason behind Plasma's design choice. The user also invites feedback and suggestions for alternative solutions.