Plasma issueshttps://invent.kde.org/groups/plasma/-/issues2023-08-09T18:53:31Zhttps://invent.kde.org/plasma/plasma-workspace/-/issues/91Fix Flaky systemtraytest2023-08-09T18:53:31ZFushan WenFix Flaky systemtraytest6Fushan WenFushan Wen2023-08-13https://invent.kde.org/plasma/latte-dock/-/issues/129Settings and launchers are reset after readding to autostart2023-08-10T12:35:01Zprashant jainSettings and launchers are reset after readding to autostartOS: Kubuntu 23.04 x86_64
Host: UX310UQK 1.0
Kernel: 6.2.0-26-generic
Packages: 3362 (dpkg), 27 (flatpak), 9 (snap)
Shell: zsh 5.9
Resolution: 1920x1080
DE: Plasma 5.27.4
WM: KWin
WM Theme: WhiteSur-dark
Theme: [Plasma], WhiteSur...OS: Kubuntu 23.04 x86_64
Host: UX310UQK 1.0
Kernel: 6.2.0-26-generic
Packages: 3362 (dpkg), 27 (flatpak), 9 (snap)
Shell: zsh 5.9
Resolution: 1920x1080
DE: Plasma 5.27.4
WM: KWin
WM Theme: WhiteSur-dark
Theme: [Plasma], WhiteSur-Dark [GTK2/3]
Icons: [Plasma], WhiteSur-dark [GTK2/3]
Terminal: konsole
Terminal Font: MesloLGS NF 11
CPU: Intel i5-7200U (4) @ 3.100GHz
GPU: Intel HD Graphics 620
GPU: NVIDIA GeForce 940MX
Memory: 4522MiB / 23900MiB
The settings are gone when you have added latte-dock on autostart items, result on next reboot settings are reset. This is annoying as readding latte does the same.https://invent.kde.org/plasma/plasma-workspace/-/issues/89testrunnermodel & servicerunnertest broken (again?)2023-11-26T13:03:07ZHarald Sittertestrunnermodel & servicerunnertest broken (again?)```
The following tests FAILED:
22 - servicerunnertest (Failed)
25 - testrunnermodel (Failed)
37 - testdesktop (Failed)
```
I'm going to disable them for now so we can switch on test passing requirements.```
The following tests FAILED:
22 - servicerunnertest (Failed)
25 - testrunnermodel (Failed)
37 - testdesktop (Failed)
```
I'm going to disable them for now so we can switch on test passing requirements.Alexander LohnauAlexander Lohnauhttps://invent.kde.org/plasma/latte-dock/-/issues/128Does not Respect "Primary" screen on Wayland2023-08-19T12:23:59ZSteve ChaanineDoes not Respect "Primary" screen on WaylandHello
Running latest Latte-Dock built from source. I have 3 Monitors, 2xHDMI(HDMI-A-1+HDMI-A-2) +1xDP-1, On Wayland although I set it to be shown on Primary display in the center (DP-1) it keeps showing on Right Monitor (HDMI-A-1). If I...Hello
Running latest Latte-Dock built from source. I have 3 Monitors, 2xHDMI(HDMI-A-1+HDMI-A-2) +1xDP-1, On Wayland although I set it to be shown on Primary display in the center (DP-1) it keeps showing on Right Monitor (HDMI-A-1). If I set it to specifically show on DP-1 when I log back into X11 Latte will not show at all until I go to its settings and put it back to "Primary"
Any help would be appreciatedhttps://invent.kde.org/plasma/breeze-gtk/-/issues/11Breeze is Missing the Expand Arrow Icons2023-08-07T14:30:30ZTemmie SidasBreeze is Missing the Expand Arrow IconsIn Adwatia you can see the arrows here:
![image](/uploads/b8fb7bfdae46e05306721a038face5cf/image.png)
However, if you switch to Breeze, the arrows don't render:
![image](/uploads/d925f655e98a7fc37ac783e068331697/image.png)
I'm not real...In Adwatia you can see the arrows here:
![image](/uploads/b8fb7bfdae46e05306721a038face5cf/image.png)
However, if you switch to Breeze, the arrows don't render:
![image](/uploads/d925f655e98a7fc37ac783e068331697/image.png)
I'm not really sure what defines these arrows (I tried looking in the GTK Icon Browser but it wasn't very helpful), but at least it should be a small enough issue to fix.https://invent.kde.org/plasma/systemsettings/-/issues/31Some packages are not installable due to issues with application/gzip associa...2023-08-14T15:38:41ZRuan FormigoniSome packages are not installable due to issues with application/gzip associationThe issue happens when the user tries to install a user-contributed package in the `application/gzip` format, here is the output:
```
Installation of /tmp/kyjVyQ-BeautifulTreeAnimation.tar.gz failed: Could not open package file, unsuppo...The issue happens when the user tries to install a user-contributed package in the `application/gzip` format, here is the output:
```
Installation of /tmp/kyjVyQ-BeautifulTreeAnimation.tar.gz failed: Could not open package file, unsupported archive format: /tmp/kyjVyQ-BeautifulTreeAnimation.tar.gz application/gzip
```
Also:
![Screenshot_20230807_045742](/uploads/eed9750d9cab0bf8aac74f9feb913c70/Screenshot_20230807_045742.png)
Seems to be the same problem the one of this [thread](https://bbs.archlinux.org/viewtopic.php?id=287539)https://invent.kde.org/plasma/plasma-desktop/-/issues/102Task Switcher accessibility issue: no option to keep open?2023-08-07T20:08:37ZStuart DenyerTask Switcher accessibility issue: no option to keep open?As someone raised a number of years ago in https://www.reddit.com/r/kde/comments/6a3ntq/keep_task_switcher_open_after_pressing_alt_tab/ the Plasma task switcher doesn't seem to have the option to stay open until a window is selected, whi...As someone raised a number of years ago in https://www.reddit.com/r/kde/comments/6a3ntq/keep_task_switcher_open_after_pressing_alt_tab/ the Plasma task switcher doesn't seem to have the option to stay open until a window is selected, which is awkward for people with limited dexterity, one hand, etc. And would presumably be helpful for touch input users too.
Standard keyboard shortcuts mirror the Windows Alt+Tab behaviour, but what Windows also provides is a separate keyboard shortcut (Ctrl+Alt+Tab) to open the task switcher and wait for a selection.
It'd be great if this could be considered.https://invent.kde.org/plasma/plasma-desktop/-/issues/101Task Manager idea / feature request: show only tasks that are *not* minimised2023-08-07T19:33:07ZStuart DenyerTask Manager idea / feature request: show only tasks that are *not* minimisedThis may sound like a bit of an odd request at first, but would there be any appetite for adding an option equivalent to "Show only tasks that are minimised" but for tasks that aren't minimised? Is it something that seems like it would b...This may sound like a bit of an odd request at first, but would there be any appetite for adding an option equivalent to "Show only tasks that are minimised" but for tasks that aren't minimised? Is it something that seems like it would be technically straightforward (just applying opposite logic) or are there gotchas that aren't obvious?
The reason for asking is that I'd like to use two task manager widgets, one for showing visible windows and one for showing minimised (or all) windows.
At the moment I normally use tools such as Birdtray and KDocker to keep out of the way things that I want to leave running but not show on the panel, such as an email client, extra file manager or browser windows, etc. and use that extra space to be able to see window/document titles on the main task manager. I've previously looked at virtual desktops and activities, but things like that don't tend to place nicely with multi-monitor setups. Putting things in the notification area / system tray, whilst something a lot of people feel strongly shouldn't be done, is a simple but effective alternative. And having a separate icons-only task manager that only shows minimised windows is close enough, because an option to use taskbar buttons with some applications (or specific windows) and icons with others, which is effectively what KDocker does, would need more UI and be more complex to maintain.
With Wayland on the horizon it's uncertain how well if at all any "add-on" things like Birdtray and KDocker will work, so having more window management options available in the desktop environment itself and in default widgets would be a plus.
If this isn't of much interest to other people, at some point if/when I get chance (timeline probably after Plasma 6 gets a wider release and work's quieter etc) I'll probably have a go at adding an option myself. I'm a mediocre coder but can usually follow other people's stuff and adapt. If that happens is it the sort of merge that's likely to be accepted or would having the option be considered too likely to confuse users? I'm guessing it's the sort of flexibility that would have more appeal to Plasma users than some other DEs anyway.https://invent.kde.org/plasma/kwin/-/issues/176Allow configuring VSync to which screen it locks2023-08-04T12:43:29ZFelix StuppAllow configuring VSync to which screen it locks## What I Want
If VSync is enabled (which now can only be disabled by an Environment variable, see !707), KWin locks its framerate to one screen, which, for one screen, is fine. However, on a multi-monitor setup, it locks on the screen ...## What I Want
If VSync is enabled (which now can only be disabled by an Environment variable, see !707), KWin locks its framerate to one screen, which, for one screen, is fine. However, on a multi-monitor setup, it locks on the screen it likes the most. I couldn’t get, how it decides that, as it seems to be independent of their refresh rates, priority, position is xrandr or even port used. So, to allow users to fix this (in my view broken) auto selection, there should be a setting for that.
## My Setup
Hardware:
- Processor: AMD Ryzen 5 1600X
- Graphics: AMD Radeon RX 6600 XT
Software:
- Debian GNU/Linux trixie/sid
- KDE Plasma Version: 5.27.5
- KDE Frameworks Version: 7.107.0
- Qt Version: 5.15.10
- Kernel Version: 6.4.0-1-amd64
- Graphics Platform: X11
I have three displays, all running at their max configurations, screen priorities configured at that order:
1. 2560x1440, 165 Hz
2. 1920x1080, 60 Hz
3. 1280x1024, 75 Hz, rotated 90° clockwise
These are connected via two DP & one HDMI connector on my graphics card, but how they are connected seems not to matter (see below).
## Expected Result
Without (much) additional configuration, KWin should lock on the 165 Hz screen, either because
- its configured as the primary screen
- it has the highest refresh rate of all screens
## Actual Result
KWin locks on the 60 Hz screen. I know that for sure, because all screens have pairwise different refresh rates and because I checked the framerate with the “Show FPS” tool listed in “Desktop Effects”.
## What I tried so far
Trying all permutations of display -> graphics card port and disconnecting displays temporarily reveals that KWin seems to prefer the screens in that order (numbering from above): 2, 1, 3. Meaning that with all 3 displays, it always locks on 60 fps without me giving a chance to divert from that. If I let display 2 disconnected, KWin locks on 165 fps, independent of connection too.
I searched the web & this issue tracker for debugging configurations I could try: I tried disabling VSync via environment variables written in `~/.config/plasma-workspace/env/kwin.sh` or changing the max fps configuration in `~/.config/kwinrc`, but they did not change anything (disconnecting display 2 to have 165 fps even works too), so I reverted them.
I searched for duplicate issues here, but didn’t found anything.https://invent.kde.org/plasma/plasma-workspace/-/issues/87testrunnermodel broken2023-08-04T14:34:02ZHarald Sittertestrunnermodel brokenCurrently it looks like the test wasn't updated for the refactored model so it is not passing. I've disabled it to unblock requirement of passing tests.Currently it looks like the test wasn't updated for the refactored model so it is not passing. I've disabled it to unblock requirement of passing tests.6Alexander LohnauAlexander Lohnauhttps://invent.kde.org/plasma/plasma-workspace/-/issues/86shelltest broken2023-09-21T14:40:51ZHarald Sittershelltest brokenCurrently shelltest likes to crash alot on failed assertions inside ShellCorona::screenInvariants. I'm disabling it for the time being until someone can find time to fix it (hopefully that isn't never).Currently shelltest likes to crash alot on failed assertions inside ShellCorona::screenInvariants. I'm disabling it for the time being until someone can find time to fix it (hopefully that isn't never).6Marco MartinMarco Martinhttps://invent.kde.org/plasma/kscreen/-/issues/9Missing German keywords2023-07-30T14:36:58ZNicolai WeitkemperMissing German keywords`X-KDE-Keywords[de]` is missing in https://invent.kde.org/plasma/kscreen/-/blob/master/kcm/kcm_kscreen.json.
I'm opening an issue for this because
1. German is one of very few languages without a translation in this file, which seems sus...`X-KDE-Keywords[de]` is missing in https://invent.kde.org/plasma/kscreen/-/blob/master/kcm/kcm_kscreen.json.
I'm opening an issue for this because
1. German is one of very few languages without a translation in this file, which seems suspicious to me,
2. IIRC I'm not supposed to change translations here and
3. getting involved with svn, translation teams etc. seems overkill for thishttps://invent.kde.org/plasma/kwin/-/issues/175Application for Forking UKUI-KWin from KWin2023-10-31T13:08:26ZMouse ZhangApplication for Forking UKUI-KWin from KWinDear KWin Development Team,
I am one of the maintainers of the UKUI desktop environment, and I am writing to apply for the fork of the ukui-kwin code. We hold great admiration for your KWin project and deeply value and respect your insi...Dear KWin Development Team,
I am one of the maintainers of the UKUI desktop environment, and I am writing to apply for the fork of the ukui-kwin code. We hold great admiration for your KWin project and deeply value and respect your insights and suggestions. In our project, we have specific requirements that necessitate some customization to KWin, and we hope to gain your approval.
The modifications we intend to make in the fork include, but are not limited to, the following points:
1. Tablet Mode Support: We have incorporated support for the UKUI tablet mode, which differs from the existing tablet mode mechanism in KWin. Therefore, corresponding modifications are required to adapt to our desktop environment.
2. Virtual Keyboard: We have developed a virtual keyboard, but the current window layering in KWin does not fully meet our needs. Particularly, when using the virtual keyboard for text input, pop-up windows such as QCompleter often obscure the virtual keyboard. To address this issue, we need to add a new window layer to ensure that the virtual keyboard always displays above popup windows.
3. Custom Protocols: To fulfill the application requirements in the UKUI environment, we have added or modified certain protocols, such as the blur effect with gradual intensity changes.
4. Window Snapping Functionality: We have implemented a window snapping feature similar to that in Windows 11, which allows users to manage windows more efficiently.
5. Global Gestures: We have replaced the original edge gestures in KWin with global gestures, such as using a four-finger swipe to invoke search.
6. Dependency Management: We aim to release UKUI without some of the dependencies associated with the Plasma desktop environment, while still using KWin as our window manager and Wayland compositor.
7. X11 Support: We require continued support for X11 and plan to develop new features to ensure flexibility and compatibility of UKUI across various systems.
We genuinely value and respect your collaboration and feedback. If granted permission, we commit to keeping our fork in sync with the upstream KWin and regularly submitting our generic improvements and patches.
We sincerely appreciate you taking the time to review our application. We look forward to working with you to advance the development of Linux desktop environments.
Best regards,
Mouse Zhang
UKUI Desktop Environment Maintainerhttps://invent.kde.org/plasma/plasma-nm/-/issues/5DoT (DNS-over-TLS) or DoH (DNS-over-HTTP) support2023-07-25T12:34:24ZDax PeddaDoT (DNS-over-TLS) or DoH (DNS-over-HTTP) supportI just recently learned that NetworkManager has a per-profile option for DNS-over-TLS.
It would be nice if a toggle for this could be exposed.
I'm not entirely sure if this can be supported without systemd-resolved though.
See https://g...I just recently learned that NetworkManager has a per-profile option for DNS-over-TLS.
It would be nice if a toggle for this could be exposed.
I'm not entirely sure if this can be supported without systemd-resolved though.
See https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/blob/aaaf727b97d8ce1a89a76d9e13808dffa7e3ecf3/src/libnm-core-impl/nm-setting-connection.c#L2539-2573https://invent.kde.org/plasma/plasma-workspace/-/issues/83Port away from direct KActionCollection usage in Plasma2023-07-27T14:09:37ZNate GrahamPort away from direct KActionCollection usage in PlasmaChanges made in https://invent.kde.org/frameworks/plasma-framework/-/merge_requests/826
Merge requests adapting to the changes:
- https://invent.kde.org/plasma/plasma-workspace/-/merge_requests/3069Changes made in https://invent.kde.org/frameworks/plasma-framework/-/merge_requests/826
Merge requests adapting to the changes:
- https://invent.kde.org/plasma/plasma-workspace/-/merge_requests/30696https://invent.kde.org/plasma/plasma-workspace/-/issues/82Port PlasmaCore.IconItem to Kirigami.Icon2023-08-21T15:40:11ZNate GrahamPort PlasmaCore.IconItem to Kirigami.IconWith https://invent.kde.org/frameworks/kirigami/-/merge_requests/1155 and https://invent.kde.org/frameworks/kirigami/-/merge_requests/1189, `Kirigami.Icon` should now be a drop-in replacement as long as we're okay with only using icons f...With https://invent.kde.org/frameworks/kirigami/-/merge_requests/1155 and https://invent.kde.org/frameworks/kirigami/-/merge_requests/1189, `Kirigami.Icon` should now be a drop-in replacement as long as we're okay with only using icons from the icon theme, not the Plasma theme. This comports well with https://invent.kde.org/plasma/plasma-desktop/-/issues/82, which has been agreed to.
So now we need to move Plasma Breeze icons into the Breeze Icon theme. Here's a tool that helps: https://invent.kde.org/frameworks/ksvg/-/merge_requests/14
Merge requests porting to it:
- https://invent.kde.org/documentation/develop-kde-org/-/merge_requests/301
- https://invent.kde.org/frameworks/breeze-icons/-/merge_requests/268
- https://invent.kde.org/frameworks/breeze-icons/-/merge_requests/270
- https://invent.kde.org/frameworks/breeze-icons/-/merge_requests/271
- https://invent.kde.org/frameworks/plasma-framework/-/merge_requests/838
- https://invent.kde.org/frameworks/extra-cmake-modules/-/merge_requests/369
- https://invent.kde.org/plasma/plasma-workspace/-/merge_requests/3044
- https://invent.kde.org/plasma/plasma-desktop/-/merge_requests/1635
- https://invent.kde.org/plasma/kdeplasma-addons/-/merge_requests/438
- https://invent.kde.org/plasma/plasma-pa/-/merge_requests/197
- https://invent.kde.org/plasma/plasma-nm/-/merge_requests/275
- https://invent.kde.org/plasma/bluedevil/-/merge_requests/137
- https://invent.kde.org/plasma/bluedevil/-/commit/269767275ce3f0497b59271091c589d4d56a750b
- https://invent.kde.org/plasma/kscreen/-/merge_requests/227
- https://invent.kde.org/plasma/milou/-/merge_requests/67
- https://invent.kde.org/plasma/kwin/-/merge_requests/4281
- https://invent.kde.org/plasma/plasma-sdk/-/merge_requests/90
- https://invent.kde.org/plasma/plasma-mobile/-/merge_requests/357
---
To test, apply all MRs and apply the Breeze icon theme and the Breeze Light color scheme. Then check with the following Plasma themes:
- Breeze Plasma theme: no visual changes
- Breeze Dark Plasma theme: no visual changes
- 3rd-party Plasma theme that includes icons: most places where icons from the Plasma theme were previously seen now instead display Breeze icons (not all, since there are a few cases where icons were displayed using raw SVG items which need to be ported as well, but that work is outside the scope of this specific Issue)6https://invent.kde.org/plasma/plasma-workspace/-/issues/81Wallpaper API changes2023-07-24T14:27:45ZNate GrahamWallpaper API changesChanges made in https://invent.kde.org/frameworks/plasma-framework/-/merge_requests/824
Merge requests adapting to the changes:
- https://invent.kde.org/plasma/plasma-workspace/-/merge_requests/3061
- https://invent.kde.org/plasma/kdepl...Changes made in https://invent.kde.org/frameworks/plasma-framework/-/merge_requests/824
Merge requests adapting to the changes:
- https://invent.kde.org/plasma/plasma-workspace/-/merge_requests/3061
- https://invent.kde.org/plasma/kdeplasma-addons/-/merge_requests/4316https://invent.kde.org/plasma/plasma-workspace/-/issues/80Porting to the new Actions API2023-07-24T18:18:18ZNate GrahamPorting to the new Actions APIAPI changed in https://invent.kde.org/frameworks/plasma-framework/-/merge_requests/813 and https://invent.kde.org/frameworks/plasma-framework/-/merge_requests/823
Merge requests adapting to those changes:
- https://invent.kde.org/plasma...API changed in https://invent.kde.org/frameworks/plasma-framework/-/merge_requests/813 and https://invent.kde.org/frameworks/plasma-framework/-/merge_requests/823
Merge requests adapting to those changes:
- https://invent.kde.org/plasma/plasma-workspace/-/merge_requests/3057
- https://invent.kde.org/plasma/plasma-desktop/-/merge_requests/1600
- https://invent.kde.org/plasma/kdeplasma-addons/-/merge_requests/425
- https://invent.kde.org/plasma/kdeplasma-addons/-/merge_requests/430
- https://invent.kde.org/plasma/kscreen/-/merge_requests/224
- https://invent.kde.org/plasma/plasma-nm/-/merge_requests/262
- https://invent.kde.org/plasma/plasma-pa/-/merge_requests/193
- https://invent.kde.org/plasma/bluedevil/-/merge_requests/134
- https://invent.kde.org/plasma/plasma-vault/-/merge_requests/326https://invent.kde.org/plasma/systemsettings/-/issues/29Wayland: desired resolutions are unavailable on my laptop as opposed to X112023-07-22T13:16:42Zmuzik naviWayland: desired resolutions are unavailable on my laptop as opposed to X11I have a 14' laptop with hidpi display 2240x1400 (16:10).
For my small screen I would like to set a lower resolution like 1680x1050 (16:10). But only have a few options in Wayland session and there's no desired 1680x1050 (16:10) as I s...I have a 14' laptop with hidpi display 2240x1400 (16:10).
For my small screen I would like to set a lower resolution like 1680x1050 (16:10). But only have a few options in Wayland session and there's no desired 1680x1050 (16:10) as I see in X11 session.
See screenshots for compare.
![2023-07-22_17-31](/uploads/4e2dfb8c61f2b7e028d71e3d2f0058ee/2023-07-22_17-31.png)
![2023-07-22_17-32](/uploads/39827fb9400f501aec3a030fea80bc41/2023-07-22_17-32.png)https://invent.kde.org/plasma/discover/-/issues/28Because the system language is Chinese, Discover cannot connect to the API of...2023-07-19T03:57:02Z阿卡林刘AkarinLiuBecause the system language is Chinese, Discover cannot connect to the API of the OCS server链接来自百度贴吧Arch Linux吧:https://tieba.baidu.com/p/7738474526
访问OCS服务器的时候出现了问题:API出现了未知错误(Code:0),这就导致用户无法下载新的Plasma部件,希望官方能够解决这个问题,这一问题应该得到中文用户的重视。
Link from Baidu Tieba Arch Linux bar: https://tieba.baidu.com/p/7738474526
There was a pr...链接来自百度贴吧Arch Linux吧:https://tieba.baidu.com/p/7738474526
访问OCS服务器的时候出现了问题:API出现了未知错误(Code:0),这就导致用户无法下载新的Plasma部件,希望官方能够解决这个问题,这一问题应该得到中文用户的重视。
Link from Baidu Tieba Arch Linux bar: https://tieba.baidu.com/p/7738474526
There was a problem accessing the OCS server: an unknown error (Code:0) occurred in the API, which prevented users from downloading new Plasma parts, and hopefully the official solution to this problem should be taken seriously by Chinese users.