Plasma issueshttps://invent.kde.org/groups/plasma/-/issues2023-11-08T12:43:50Zhttps://invent.kde.org/plasma/print-manager/-/issues/4add-printer: Clean up the GUI for 6 release2023-11-08T12:43:50ZMike Noeadd-printer: Clean up the GUI for 6 releasehttps://invent.kde.org/plasma/print-manager/-/issues/3Migrate repo to Plasma namespace/release schedule2023-11-08T12:44:02ZMike NoeMigrate repo to Plasma namespace/release schedulehttps://invent.kde.org/plasma/plasma-desktop/-/issues/105[TBD] Plasma 6 proposal: Fullscreen application launcher based on Kickoff2023-08-31T01:34:07ZFushan Wen[TBD] Plasma 6 proposal: Fullscreen application launcher based on Kickoff# Background
The existing application dashboard (referred as "fullscreen launcher") [has a questionable technical architecture and is completely broken in Plasma 6](https://invent.kde.org/plasma/plasma-workspace/-/issues/88). Most exist...# Background
The existing application dashboard (referred as "fullscreen launcher") [has a questionable technical architecture and is completely broken in Plasma 6](https://invent.kde.org/plasma/plasma-workspace/-/issues/88). Most existing fullscreen launchers on sko are also based on the broken fullscreen launcher, so they are also likely to fail, which means there will be no usable fullscreen launcher in Plasma 6.
# Reasons
It's difficult to quickly completely understand what people really need when they use the fullscreen launcher and its variants. [Some are using it on small-screen devices, and some are using it on full desktops.](https://discuss.kde.org/t/fullscreen-kickoff/4281) If there are still many users using the fullscreen launcher, it might make sense to make a new fullscreen launcher following the design of Kickoff. Reasons given below:
1. The design of the new Kickoff has [gone through multiple rounds of prototyping](https://phabricator.kde.org/T12192), making the final product have good usability, and people seem to be in favor of the current Kickoff as [there are few negative reports](https://bugs.kde.org/buglist.cgi?component=Application%20Launcher%20%28Kickoff%29&list_id=2456024&product=plasmashell&resolution=---).
2. The current Kickoff has already implemented the features available in the fullscreen launcher except for the widget browser, and it's questionable whether it's useful to browse widgets in an application launcher as [many forks of the fullscreen launcher have removed the feature](https://store.kde.org/p/1897990). People using the existing fullscreen launcher will not feel anything incomplete in the new fullscreen launcher.
As I believe users tend to use the fullscreen launcher on touch-capable devices, to adapt Kickoff design to the fullscreen launcher, a few changes will be made:
1. No information overload: A fullscreen view will only serve for a single purpose, which means the home page will no longer be crowded with favorites and application lists, making buttons bigger and more touch-friendly.
2. Less tab, more swipe: Using tabs to navigate is not touch friendly. People are more used to swiping to switch views on mobile platforms.
# Plans
A few fullscreen launcher prototypes will be made to more quickly get feedbacks from the users. A final product will be made after a consensus is reached.6https://invent.kde.org/plasma/plasma-desktop/-/issues/103[Rejected] Plasma 6 proposal: center task manager widget by default2023-08-28T14:32:09ZNatalie Clariusnatalie_clarius@yahoo.de[Rejected] Plasma 6 proposal: center task manager widget by default![task-manager-centered](/uploads/065de75ccbd952f0cb26bdac7a2e314f/task-manager-centered.png)
Advantages:
1. Usability: The less the items are at the screen edges, the easier they are to see and reach with the mouse. I've been daily-...![task-manager-centered](/uploads/065de75ccbd952f0cb26bdac7a2e314f/task-manager-centered.png)
Advantages:
1. Usability: The less the items are at the screen edges, the easier they are to see and reach with the mouse. I've been daily-driving the centered task manager for a long time and whenever I get to a setup with them in the corner I find it a bit of an annoyance, especially on large screens.
2. Visuals: This is of course highly subjective, but
1. I find that the symmetry makes the panel appear more visually balanced,
2. and all modern OSes which have task bars (Mac OS, Windows, Android L) do this so in that regard our current style is somewhat reminiscent of old Windows/Gnome 2 desktops.
Disadvantages:
1. Especially with Windows now apparently also floating their panel in addition to centering the task manager, maybe we don't want to be too similar looking to other OSes.
I would suggest (as seen in the screenshot) to keep the application launcher and pager widgets on the left, to make it visually balanced, and set our own style slightly apart from Windows 11.
Before we do this we should fix https://bugs.kde.org/show_bug.cgi?id=472859 and https://bugs.kde.org/show_bug.cgi?id=424055 and disable filling free space on panel in the task manager widget first.
@teams/vdg CC @niccolove who IIRC wanted this toohttps://invent.kde.org/plasma/breeze-gtk/-/issues/12Gtk warnings when running qemu with the Breeze-dark theme2023-08-27T13:54:07ZMark Veltzermark.veltzer@gmail.comGtk warnings when running qemu with the Breeze-dark theme# I get the following warnings:
(qemu-system-i386:2963505): Gtk-WARNING \*\*: 16:33:20.035: Theme parsing error: gtk.css:1649:16: '-gtk-icon-size' is not a valid property name
(qemu-system-i386:2963505): Gtk-WARNING \*\*: 16:33:20.036:...# I get the following warnings:
(qemu-system-i386:2963505): Gtk-WARNING \*\*: 16:33:20.035: Theme parsing error: gtk.css:1649:16: '-gtk-icon-size' is not a valid property name
(qemu-system-i386:2963505): Gtk-WARNING \*\*: 16:33:20.036: Theme parsing error: gtk.css:1652:16: '-gtk-icon-size' is not a valid property name
==========
This is solved by commenting out some lines from the file:
```plaintext
/usr/share/themes/Breeze-Dark/gtk-3.0/gtk.css
```
which comes from your package.
# The lines are commented are 1647-1653 and they are:
.normal-icons { -gtk-icon-size: 16px; }
# .large-icons { -gtk-icon-size: 32px; }https://invent.kde.org/plasma/ocean-sound-theme/-/issues/9Finishing touches for the Ocean sound theme2023-09-21T15:26:26ZGuilherme Marçal SilvaFinishing touches for the Ocean sound themeAccording to @ngraham in https://invent.kde.org/plasma/ocean-sound-theme/-/issues/7#note_737929 we still need to do a few things, but they should be tracked in a new issue now that https://invent.kde.org/plasma/ocean-sound-theme/-/issues...According to @ngraham in https://invent.kde.org/plasma/ocean-sound-theme/-/issues/7#note_737929 we still need to do a few things, but they should be tracked in a new issue now that https://invent.kde.org/plasma/ocean-sound-theme/-/issues/7 is closed:
- [x] Ask the Plasma release manager (@jriddell) to note it for future release purposes
- [x] Make it part of Neon Unstable https://invent.kde.org/neon/neon/seeds/-/blob/Neon/unstable/desktop (progress: https://invent.kde.org/neon/neon/seeds/-/merge_requests/2)
- [x] Mention in https://community.kde.org/Distributions/Packaging_Recommendations
- [x] Email [distributions@kde.org] about the new packaging recommendationshttps://invent.kde.org/plasma/libplasma/-/issues/19Remove SortFilterModel2023-09-05T13:54:41ZNate GrahamRemove SortFilterModelIt's an unnecessary duplicate of something in KItemModels and is being removed in https://invent.kde.org/frameworks/plasma-framework/-/merge_requests/809. And the KItemModels version's API is being adjusted to be more ergonomic in https:...It's an unnecessary duplicate of something in KItemModels and is being removed in https://invent.kde.org/frameworks/plasma-framework/-/merge_requests/809. And the KItemModels version's API is being adjusted to be more ergonomic in https://invent.kde.org/frameworks/kitemmodels/-/merge_requests/67.
For all MRs related to this work, see the "Related Merge Requests" section belowKF6Marco MartinMarco Martinhttps://invent.kde.org/plasma/plasma-workspace/-/issues/94QT_SCREEN_SCALE_FACTORS causes pixelated rendering of some QT apps (Telegram,...2023-08-20T18:57:26ZPavel ShirshovQT_SCREEN_SCALE_FACTORS causes pixelated rendering of some QT apps (Telegram, MegaSync...)I'm using Plasma with hiDPI displays, so I have fractional scaling turned on.
When fractional scaling is on, plasma-workspace sets environment variable QT_SCREEN_SCALE_FACTORS. For some reason this variable causes strange rendering issu...I'm using Plasma with hiDPI displays, so I have fractional scaling turned on.
When fractional scaling is on, plasma-workspace sets environment variable QT_SCREEN_SCALE_FACTORS. For some reason this variable causes strange rendering issues with Telegram, MegaSync and some other QT applications.
The only way to remove this variable is to patch startplasma-x11.cpp:
```
diff --color -ru a/startkde/startplasma-x11.cpp b/startkde/startplasma-x11.cpp
--- a/startkde/startplasma-x11.cpp 2022-08-23 17:55:27.827687762 +0100
+++ b/startkde/startplasma-x11.cpp 2022-08-23 17:56:11.170498094 +0100
@@ -48,7 +48,7 @@
KConfigGroup kscreenGroup = cfg.group("KScreen");
const auto screenScaleFactors = kscreenGroup.readEntry("ScreenScaleFactors", QByteArray());
if (!screenScaleFactors.isEmpty()) {
- qputenv("QT_SCREEN_SCALE_FACTORS", screenScaleFactors);
+ // qputenv("QT_SCREEN_SCALE_FACTORS", screenScaleFactors);
}
```
I haven't noticed any rendering issues with this variable unset, only improvements.https://invent.kde.org/plasma/latte-dock/-/issues/131Latte Tasks Widget Multimonitor Filtering2023-08-19T12:21:46ZJames MerlinoLatte Tasks Widget Multimonitor FilteringLatte Tasks widget does not respect the "Show only tasks from current screen" option. When selected it shows no application.
Distribution Fedora 38.Latte Tasks widget does not respect the "Show only tasks from current screen" option. When selected it shows no application.
Distribution Fedora 38.https://invent.kde.org/plasma/discover/-/issues/29Discover's PackageKit backend frequently triggers an assert in current packag...2023-08-20T00:22:57ZBernhard RosenkraenzerDiscover's PackageKit backend frequently triggers an assert in current packagekitdWhen using discover with a current PackageKit git snapshot (after PK commit 409ba85b00f02bfd66589b457a148cce82ad2a34), Discover brings up a dialog saying "Connection reset by peer".
This is caused by packagekitd failing with the asserti...When using discover with a current PackageKit git snapshot (after PK commit 409ba85b00f02bfd66589b457a148cce82ad2a34), Discover brings up a dialog saying "Connection reset by peer".
This is caused by packagekitd failing with the assertion introduced in the commit mentioned above.
```
PackageKit:ERROR:../src/pk-transaction.c:5528:pk_transaction_dispose: assertion failed: (transaction->priv->emitted_finished)
Bail out! PackageKit:ERROR:../src/pk-transaction.c:5528:pk_transaction_dispose: assertion failed: (transaction->priv->emitted_finished)
```
Looking at the context in PackageKit, it looks like the assert is intentional and merely exposes a problem that has gone unnoticed before (removing an unfinished transaction from the bus), making it likely that this is a bug in discover rather than PackageKit.https://invent.kde.org/plasma/plasma-workspace/-/issues/93[Approved] Split battery applet into two: "Power Management" and "Brightness"2023-11-18T18:12:23ZNatalie Clariusnatalie_clarius@yahoo.de[Approved] Split battery applet into two: "Power Management" and "Brightness"This was raised here https://bugs.kde.org/show_bug.cgi?id=424283 but I would like to get some more opinions on it from people who are involved in the code. Since we're going to want to dig the applet over to port away from data engines s...This was raised here https://bugs.kde.org/show_bug.cgi?id=424283 but I would like to get some more opinions on it from people who are involved in the code. Since we're going to want to dig the applet over to port away from data engines soon anyway this would be a natural breaking point.
Reasons in favor imo:
1. There is no strong reason the two should be in the same applet to begin with; surely brightness affects power usage, but so does wifi, bluetooth and just about anything you do on your computer, and it's not relevant for external screens either, so it seems a little random to put these two in the same place.
2. The applet is getting full: We now have block inhibiting, screen brightness, keyboard brightness, power profile, battery status for the laptop, battery health for the laptop, battery status for bluetooth devices - this already fills the default applet popup size, and we are planning to include more brightness sliders for both internal and external screens, and potentially backlight color setting for RGB keyboard, so the applet would have to be scrolled or manually resized to access all controls which is not ideal.
Resaons against:
1. More tray icons, which some users don't like
Even as someone who doesn't like many tray icons myself I think a split makes sense.
@teams/usability @teams/vdg @fusionfuture @ratijas @ngrahamhttps://invent.kde.org/plasma/plasma-welcome/-/issues/19CMakeLists BSD licensing2023-10-17T10:19:12ZOliver BeardCMakeLists BSD licensingRaised by @arraybolt3:matrix.org:
https://community.kde.org/Policies/Licensing_Policy indicates that **BSD-2-Clause** should be used for CMakeLists.txt files:
>CMake code must be licenced under the BSD-2-Clause license as listed below ...Raised by @arraybolt3:matrix.org:
https://community.kde.org/Policies/Licensing_Policy indicates that **BSD-2-Clause** should be used for CMakeLists.txt files:
>CMake code must be licenced under the BSD-2-Clause license as listed below or the BSD-3-Clause licence as listed below.
>Note: It is strongly discouraged to use the BSD-3-Clause license.
>Clarified that CMake license requirements apply to all CMake code as discussed in 'CMake source files without license' on kde-devel list.
One such file was authored by me, and I'll of course grant permission for it. Two others have copyright headers for @ngraham and @fhek, who will need to authorise such a change.Oliver BeardOliver Beardhttps://invent.kde.org/plasma/latte-dock/-/issues/130Justify alignment can only, maximum, center 2 widgets when starting the process.2023-08-19T13:09:11ZAngelo CamposJustify alignment can only, maximum, center 2 widgets when starting the process.All widgets left to right are: Application Menu, Global Menu, Color Picker, Currently Playing, Color Picker 2, System Tray, Netspeed Widget & Better inline clock.
![example](/uploads/2f706dcd84f87e64ae9d821d1576e55e/example.png)
Whenev...All widgets left to right are: Application Menu, Global Menu, Color Picker, Currently Playing, Color Picker 2, System Tray, Netspeed Widget & Better inline clock.
![example](/uploads/2f706dcd84f87e64ae9d821d1576e55e/example.png)
Whenever I reboot or kill & restart the process it only holds 2 centered things with justify.
Example using latte spacers to show it clearly can hold more, just doesn't load it initially.
![example2.png](/uploads/423240ccf545a78ac3801a6caa576a3a/example2.png)
It can also pull widgets from the side & center it when it wasn't placed that way.
![example3.png](/uploads/721f63a8cff4bd838a859201d07c03bf/example3.png)https://invent.kde.org/plasma/breeze/-/issues/17Set lighter hover color or white hover text for menubar items2023-08-11T14:31:33ZPiruzzolo PiruzzoloSet lighter hover color or white hover text for menubar itemsSee here, this is the current behavior when hovering on a menu item:
![immagine](/uploads/5e4e91987408ce8f34885bf3c51b6183/immagine.png)
I think it would be nicer to set white color for hover text or a lighter color for hover backgroun...See here, this is the current behavior when hovering on a menu item:
![immagine](/uploads/5e4e91987408ce8f34885bf3c51b6183/immagine.png)
I think it would be nicer to set white color for hover text or a lighter color for hover background (like the hover text color in QListView)https://invent.kde.org/plasma/breeze/-/issues/16Set margin and borders of QListWidget2023-08-11T14:33:12ZPiruzzolo PiruzzoloSet margin and borders of QListWidgetIt would be nice to add some borders and margins for the QListWidget content to like 7 pixels,
basically the equivalent of `listWidget->setStyleSheet("QListWidget {padding: 7px;} QListWidget::item { margin: 7px; }");`
**Before:**
![imm...It would be nice to add some borders and margins for the QListWidget content to like 7 pixels,
basically the equivalent of `listWidget->setStyleSheet("QListWidget {padding: 7px;} QListWidget::item { margin: 7px; }");`
**Before:**
![immagine](/uploads/da3594c03364e549c5c1a12c09b67ad4/immagine.png)
**After:**
![immagine](/uploads/bed94ff54bb1242a2d95321ca9139b6e/immagine.png)
Worth an exception if the items are text-only.
Dunno if it's better to set left margin/border to QListWidgetItem instead.
I'd do it myself but can't figure out how.https://invent.kde.org/plasma/plasma-integration/-/issues/4Tests aren't being run in the CI2023-10-17T07:46:11ZNate GrahamTests aren't being run in the CIAs a result, they're bit-rotting pretty hard:
```
30% tests passed, 7 tests failed out of 10
Total Test time (real) = 9.30 sec
The following tests FAILED:
2 - frameworkintegration-kdeplatformtheme_unittest (Failed)
...As a result, they're bit-rotting pretty hard:
```
30% tests passed, 7 tests failed out of 10
Total Test time (real) = 9.30 sec
The following tests FAILED:
2 - frameworkintegration-kdeplatformtheme_unittest (Failed)
3 - frameworkintegration-kfontsettingsdata_unittest (Failed)
4 - frameworkintegration-kfiledialog_unittest (Failed)
6 - frameworkintegration-kdeplatformsystemtrayicon_unittest (Failed)
8 - frameworkintegration-khintssettings_unittest (Failed)
9 - qmltests (Not Run)
10 - frameworkintegration-kfiledialogqml_unittest (Failed)
```https://invent.kde.org/plasma/xdg-desktop-portal-kde/-/issues/13remote-desktop: add the ability to communicate via an EIS socket2024-03-11T09:14:37Ztheofficial gmanremote-desktop: add the ability to communicate via an EIS socketRemoteDesktop portal spec was updated to include `ConnectToEIS` https://github.com/flatpak/xdg-desktop-portal/pull/762
It has also been implemented and merged into xdg-desktop-portal-gnome https://gitlab.gnome.org/GNOME/xdg-desktop-port...RemoteDesktop portal spec was updated to include `ConnectToEIS` https://github.com/flatpak/xdg-desktop-portal/pull/762
It has also been implemented and merged into xdg-desktop-portal-gnome https://gitlab.gnome.org/GNOME/xdg-desktop-portal-gnome/-/merge_requests/97
This isssue is a request that it be implemented in xdg-desktop-portal-kdehttps://invent.kde.org/plasma/krdp/-/issues/7Cursor is on wrong monitor2023-09-13T05:50:32ZMarek KrausCursor is on wrong monitorArchLinux, latest flatpak image
I have two QHD monitors, the one highlighted is primary one:
![image](/uploads/21c8ae83fd6ec09af252183c6423424d/image.png)
This is my run command:
```
flatpak run org.kde.krdp -u XX -p XX --monitor 0
`...ArchLinux, latest flatpak image
I have two QHD monitors, the one highlighted is primary one:
![image](/uploads/21c8ae83fd6ec09af252183c6423424d/image.png)
This is my run command:
```
flatpak run org.kde.krdp -u XX -p XX --monitor 0
```
On RDP, I saw primary monitor, but the cursor was placed on secondary monitor.https://invent.kde.org/plasma/plasma-workspace/-/issues/92Test media controller more thoroughly2023-08-30T09:55:04ZFushan WenTest media controller more thoroughly- [x] [Touch swipe up/down/left/right to adjust volume/progress](https://invent.kde.org/plasma/plasma-workspace/-/merge_requests/3171)
- [x] Explore the possibility of using the fake input protocol
- [x] Perform some fake touch actio...- [x] [Touch swipe up/down/left/right to adjust volume/progress](https://invent.kde.org/plasma/plasma-workspace/-/merge_requests/3171)
- [x] Explore the possibility of using the fake input protocol
- [x] Perform some fake touch actions
- [x] [Test the multiplexer](https://invent.kde.org/plasma/plasma-workspace/-/merge_requests/3171)
- [x] 1 player, hidden
- 2 players
- [x] A playing, B paused: A
- [x] A paused, B paused: A
- [x] A paused, B playing: B
- [x] A playing, B playing: B
- [x] A playing, B paused: A
- [x] Filter out Firefox instance when p-b-i is installed6Fushan WenFushan Wen2023-12-31https://invent.kde.org/plasma/krdp/-/issues/6Can't install alpha release of krdp2023-08-10T21:05:18ZIbrahim KaikaaCan't install alpha release of krdpI downloaded the latest alpha release of kRDP from this URL: https://download.kde.org/unstable/krdp/krdp-alpha-20230808.flatpak
when I try to install it I get this message:
```console
flatpak install krdp-alpha-20230808.flatpak
error: T...I downloaded the latest alpha release of kRDP from this URL: https://download.kde.org/unstable/krdp/krdp-alpha-20230808.flatpak
when I try to install it I get this message:
```console
flatpak install krdp-alpha-20230808.flatpak
error: The application org.kde.krdp/x86_64/master requires the runtime org.kde.Platform/x86_64/6.5 which was not found
```
I also tried to install org.kde.Platform 6.5 package and I still get the same error message