Plasma issueshttps://invent.kde.org/groups/plasma/-/issues2023-09-01T15:09:21Zhttps://invent.kde.org/plasma/plasma-desktop/-/issues/106Plasma 6 proposal: Use grid view for all sections of the start menu2023-09-01T15:09:21ZTanbir JishanPlasma 6 proposal: Use grid view for all sections of the start menuIt's rather obvious. The grid view looks modern and organized. The list view is fine, nevertheless the grid view will be better a default. It also will match with the favourites section.
List View:
![list_view](/uploads/c82e8696c95ffe...It's rather obvious. The grid view looks modern and organized. The list view is fine, nevertheless the grid view will be better a default. It also will match with the favourites section.
List View:
![list_view](/uploads/c82e8696c95ffe354c0e09b11d3686bc/list_view.png)
Grid View:
![grid_view](/uploads/5b4e62c7e8d5d3855bf16e29023fbff0/grid_view.png)https://invent.kde.org/plasma/print-manager/-/issues/10printqueue: Port from widget app to QML app2023-08-30T11:56:21ZMike Noeprintqueue: Port from widget app to QML apphttps://invent.kde.org/plasma/print-manager/-/issues/9readme: Update for current status, add long-term notes2024-03-28T00:46:34ZMike Noereadme: Update for current status, add long-term noteshttps://invent.kde.org/plasma/print-manager/-/issues/8kded: Fix warnings other code cruft2023-11-08T12:43:22ZMike Noekded: Fix warnings other code crufthttps://invent.kde.org/plasma/print-manager/-/issues/7kcm/plasmoid: Use printer Description field for printer/queue display2023-09-02T02:59:37ZMike Noekcm/plasmoid: Use printer Description field for printer/queue displayhttps://invent.kde.org/plasma/print-manager/-/issues/6libkcups: Fix warnings, remove some cruft, port ProcessRunner to KIO::CommandJob2023-09-19T01:03:43ZMike Noelibkcups: Fix warnings, remove some cruft, port ProcessRunner to KIO::CommandJobhttps://invent.kde.org/plasma/print-manager/-/issues/5configure-printer: Migrate simple printer/class update into KCM2023-11-08T12:43:36ZMike Noeconfigure-printer: Migrate simple printer/class update into KCM* determine the need for the impl dbus interface: org.kde.ConfigurePrinter* determine the need for the impl dbus interface: org.kde.ConfigurePrinterhttps://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/104Plasma 6 proposal: Make the krunner open at the center by default2024-03-07T19:49:20ZTanbir JishanPlasma 6 proposal: Make the krunner open at the center by defaultOpening the krunner at the center has several benefits:
1. It opens directly in front of the user.
2. It is almost always closer to the mouse.
3. The results are easy to see, and being closer to the mouse, easy to click.
4. Makes it co...Opening the krunner at the center has several benefits:
1. It opens directly in front of the user.
2. It is almost always closer to the mouse.
3. The results are easy to see, and being closer to the mouse, easy to click.
4. Makes it coherent with other runners across DEs and Oses
5. It feels nice.
6. It looks good.
Compare yourself:
top runner:
![top_krunner](/uploads/9d9afbdd4db2d0d891e0d1ea9a6ca6ba/top_krunner.png)
center runner:
![centered_krunner](/uploads/428944ce960fcc5237209b0ae38a88e6/centered_krunner.png)https://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/powerdevil/-/issues/28Duplicate suspend handling code in plasma-workspace and powerdevil2023-09-07T17:38:37ZNicolas FellaDuplicate suspend handling code in plasma-workspace and powerdevilBoth plasma-workspace and powerdevil have code for talking to logind/consolekit for handling suspending.
plasma-workspace code: https://invent.kde.org/plasma/plasma-workspace/-/blob/master/libkworkspace/sessionmanagement.h
powerdevil c...Both plasma-workspace and powerdevil have code for talking to logind/consolekit for handling suspending.
plasma-workspace code: https://invent.kde.org/plasma/plasma-workspace/-/blob/master/libkworkspace/sessionmanagement.h
powerdevil code: https://invent.kde.org/plasma/powerdevil/-/blob/master/daemon/backends/upower/powerdevilupowerbackend.cpp
Conceptually the code does pretty much the same, it checks available suspend modes and suspends.
The implementations diverge however, as can be seen in https://invent.kde.org/plasma/plasma-workspace/-/merge_requests/3219
We should probably unify that.
Options:
1) Make PowerDevil use KWorkspace API
2) Make Plasma DBus-call to Powerdevil to do suspend stuffhttps://invent.kde.org/plasma/breeze/-/issues/18Redesign the tab style2023-11-21T20:08:13ZCarl Schwancarl@carlschwan.euRedesign the tab styleThere are a few mockups published in the vdg chat, posting them here to not loose them
## Mutable tabs
![image](/uploads/e727b981889b6a8bc2a811cfe7e69b8a/image.png)
![image](/uploads/152b0214c1608dd576178b3101c79b77/image.png)
## Unm...There are a few mockups published in the vdg chat, posting them here to not loose them
## Mutable tabs
![image](/uploads/e727b981889b6a8bc2a811cfe7e69b8a/image.png)
![image](/uploads/152b0214c1608dd576178b3101c79b77/image.png)
## Unmutable tabs
![demo-app-configure_1_](/uploads/6943867f79d59927b3cf49e231acc714/demo-app-configure_1_.png)
![demo-app-configure_2_](/uploads/4dc48a08086ac3ab74c6265c3a48cb8e/demo-app-configure_2_.png)
@teams/vdghttps://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/kpipewire/-/issues/7Test programs: Could not find tag for codec vp8 in stream #0, codec not curre...2023-08-26T07:49:08Zandy dspTest programs: Could not find tag for codec vp8 in stream #0, codec not currently supported in containerTrying the test programs, both xdp-recordme and recordme create an empty ~/clementine.mp4 and the console shows
```
[mp4 @ 0x7efc4403b540] Could not find tag for codec vp8 in stream #0, codec not currently supported in container
kpipewir...Trying the test programs, both xdp-recordme and recordme create an empty ~/clementine.mp4 and the console shows
```
[mp4 @ 0x7efc4403b540] Could not find tag for codec vp8 in stream #0, codec not currently supported in container
kpipewire_record_logging: Error occurred when writing header: Invalid argument
```
I built kpipewire from the v5.27.7 tag (couldn't build master since my ECM is 5.108.0 vs requested 5.240.0).
My system info:
- KDE Plasma 5.27.7
- KDE Frameworks 5.109.0
- Qt: 5.15.10
- Kernel: 6.4.9-zen1-1-zen (arch linux)
- Wayland
- laptop with prime graphics, intel and nvidia
Full output of xdp-recordme:
```
kf.kirigami: Failed to find a Kirigami platform plugin
select sources done "/org/freedesktop/portal/desktop/request/1_467/RecordMe3918602276"
params QMap() 0
started! "/org/freedesktop/portal/desktop/request/1_467/RecordMe3918602276"
feeding... 76 25
[libvpx @ 0x7efc4403ba00] v1.13.0
[libvpx @ 0x7efc4403ba00] --prefix=/usr --disable-install-docs --disable-install-srcs --disable-unit-tests --enable-pic --enable-postproc --enable-runtime-cpu-detect --enable-shared --enable-vp8 --enable-vp9 --enable-vp9-highbitdepth --enable-vp9-temporal-denoising
[libvpx @ 0x7efc4403ba00] vpx_codec_enc_cfg
[libvpx @ 0x7efc4403ba00] generic settings
g_usage: 0
g_threads: 0
g_profile: 0
g_w: 320
g_h: 240
g_bit_depth: 8
g_input_bit_depth: 8
g_timebase: {1/30}
g_error_resilient: 0
g_pass: 0
g_lag_in_frames: 0
[libvpx @ 0x7efc4403ba00] rate control settings
rc_dropframe_thresh: 0
rc_resize_allowed: 0
rc_resize_up_thresh: 60
rc_resize_down_thresh: 30
rc_end_usage: 0
rc_twopass_stats_in: (nil)(0)
rc_target_bitrate: 256
[libvpx @ 0x7efc4403ba00] quantizer settings
rc_min_quantizer: 4
rc_max_quantizer: 63
[libvpx @ 0x7efc4403ba00] bitrate tolerance
rc_undershoot_pct: 100
rc_overshoot_pct: 100
[libvpx @ 0x7efc4403ba00] temporal layering settings
ts_number_layers: 1
[libvpx @ 0x7efc4403ba00]
ts_target_bitrate: 0 0 0 0 0
[libvpx @ 0x7efc4403ba00]
ts_rate_decimator: 0 0 0 0 0
[libvpx @ 0x7efc4403ba00]
ts_periodicity: 0
[libvpx @ 0x7efc4403ba00]
ts_layer_id: 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
[libvpx @ 0x7efc4403ba00] decoder buffer model
rc_buf_sz: 6000
rc_buf_initial_sz: 4000
rc_buf_optimal_sz: 5000
[libvpx @ 0x7efc4403ba00] 2 pass rate control settings
rc_2pass_vbr_bias_pct: 50
rc_2pass_vbr_minsection_pct: 0
rc_2pass_vbr_maxsection_pct: 400
[libvpx @ 0x7efc4403ba00] rc_2pass_vbr_corpus_complexity:0
[libvpx @ 0x7efc4403ba00] keyframing settings
kf_mode: 1
kf_min_dist: 0
kf_max_dist: 128
[libvpx @ 0x7efc4403ba00]
[libvpx @ 0x7efc4403ba00] vpx_codec_enc_cfg
[libvpx @ 0x7efc4403ba00] generic settings
g_usage: 0
g_threads: 16
g_profile: 0
g_w: 2560
g_h: 1600
g_bit_depth: 8
g_input_bit_depth: 8
g_timebase: {1/1000}
g_error_resilient: 0
g_pass: 0
g_lag_in_frames: 25
[libvpx @ 0x7efc4403ba00] rate control settings
rc_dropframe_thresh: 0
rc_resize_allowed: 0
rc_resize_up_thresh: 60
rc_resize_down_thresh: 30
rc_end_usage: 0
rc_twopass_stats_in: (nil)(0)
rc_target_bitrate: 8192
[libvpx @ 0x7efc4403ba00] quantizer settings
rc_min_quantizer: 4
rc_max_quantizer: 63
[libvpx @ 0x7efc4403ba00] bitrate tolerance
rc_undershoot_pct: 100
rc_overshoot_pct: 100
[libvpx @ 0x7efc4403ba00] temporal layering settings
ts_number_layers: 1
[libvpx @ 0x7efc4403ba00]
ts_target_bitrate: 0 0 0 0 0
[libvpx @ 0x7efc4403ba00]
ts_rate_decimator: 0 0 0 0 0
[libvpx @ 0x7efc4403ba00]
ts_periodicity: 0
[libvpx @ 0x7efc4403ba00]
ts_layer_id: 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
[libvpx @ 0x7efc4403ba00] decoder buffer model
rc_buf_sz: 6000
rc_buf_initial_sz: 4000
rc_buf_optimal_sz: 5000
[libvpx @ 0x7efc4403ba00] 2 pass rate control settings
rc_2pass_vbr_bias_pct: 50
rc_2pass_vbr_minsection_pct: 0
rc_2pass_vbr_maxsection_pct: 400
[libvpx @ 0x7efc4403ba00] rc_2pass_vbr_corpus_complexity:0
[libvpx @ 0x7efc4403ba00] keyframing settings
kf_mode: 1
kf_min_dist: 0
kf_max_dist: 100
[libvpx @ 0x7efc4403ba00]
[libvpx @ 0x7efc4403ba00] vpx_codec_control
[libvpx @ 0x7efc4403ba00] VP8E_SET_CPUUSED: 6
[libvpx @ 0x7efc4403ba00] VP8E_SET_ARNR_MAXFRAMES: 0
[libvpx @ 0x7efc4403ba00] VP8E_SET_ARNR_STRENGTH: 3
[libvpx @ 0x7efc4403ba00] VP8E_SET_ARNR_TYPE: 3
[libvpx @ 0x7efc4403ba00] VP8E_SET_NOISE_SENSITIVITY: 0
[libvpx @ 0x7efc4403ba00] VP8E_SET_TOKEN_PARTITIONS: 0
[libvpx @ 0x7efc4403ba00] VP8E_SET_STATIC_THRESHOLD: 0
[libvpx @ 0x7efc4403ba00] Using deadline: 40
[file @ 0x7efc440c9d80] Setting default whitelist 'file,crypto,data'
[mp4 @ 0x7efc4403b540] Could not find tag for codec vp8 in stream #0, codec not currently supported in container
kpipewire_record_logging: Error occurred when writing header: Invalid argument
```
I tried this patch to see if I could get it to use libx264
```diff
diff --git a/src/pipewirerecord.cpp b/src/pipewirerecord.cpp
index ac8132e..ff3b51b 100644
--- a/src/pipewirerecord.cpp
+++ b/src/pipewirerecord.cpp
@@ -105,7 +105,7 @@ PipeWireRecord::PipeWireRecord(QObject *parent)
: QObject(parent)
, d(new PipeWireRecordPrivate)
{
- d->m_encoder = "libvpx";
+ d->m_encoder = "libx264";
av_log_set_level(AV_LOG_DEBUG);
qRegisterMetaType<std::optional<int>>();
qRegisterMetaType<std::optional<std::chrono::nanoseconds>>();
@@ -251,7 +251,7 @@ void PipeWireRecordProduce::stateChanged(pw_stream_state state)
QString PipeWireRecord::extension()
{
- return QStringLiteral("webm");
+ return QStringLiteral("mp4");
}
QString PipeWireRecord::currentExtension() const
@@ -260,7 +260,7 @@ QString PipeWireRecord::currentExtension() const
{"libx264", QStringLiteral("mp4")},
{"libvpx", QStringLiteral("webm")},
};
- return s_extensions.value(d->m_encoder, QStringLiteral("mkv"));
+ return s_extensions.value(d->m_encoder, QStringLiteral("mp4"));
}
void PipeWireRecordProduce::setupStream()
@@ -270,7 +270,7 @@ void PipeWireRecordProduce::setupStream()
avformat_alloc_output_context2(&m_avFormatContext, nullptr, nullptr, m_output.toUtf8().constData());
if (!m_avFormatContext) {
qCWarning(PIPEWIRERECORD_LOGGING) << "Could not deduce output format from file: using WebM." << m_output;
- avformat_alloc_output_context2(&m_avFormatContext, nullptr, "webm", m_output.toUtf8().constData());
+ avformat_alloc_output_context2(&m_avFormatContext, nullptr, "mp4", m_output.toUtf8().constData());
}
if (!m_avFormatContext) {
qCDebug(PIPEWIRERECORD_LOGGING) << "could not set stream up";
```
Then I do start to get something. Output of xdp-recordme:
```
kf.kirigami: Failed to find a Kirigami platform plugin
select sources done "/org/freedesktop/portal/desktop/request/1_519/RecordMe3820604744"
params QMap() 0
started! "/org/freedesktop/portal/desktop/request/1_519/RecordMe3820604744"
feeding... 88 25
kpipewire_logging: PipeWire remote error: -2 unknown resource 2 op:2
[libx264 @ 0x7fe50803b9c0] using mv_range_thread = 40
[libx264 @ 0x7fe50803b9c0] using cpu capabilities: MMX2 SSE2Fast SSSE3 SSE4.2 AVX FMA3 BMI2 AVX2
[libx264 @ 0x7fe50803b9c0] profile High, level 6.2, 4:2:0, 8-bit
[file @ 0x7fe509437540] Setting default whitelist 'file,crypto,data'
kpipewire_dmabuf_logging: eglChooseConfig returned this many configs: 1
[libx264 @ 0x7fe50803b9c0] non-strictly-monotonic PTS
[libx264 @ 0x7fe50803b9c0] frame= 0 QP=48.24 NAL=3 Slice:I Poc:0 I:16000 P:0 SKIP:0 size=14321 bytes
[libx264 @ 0x7fe50803b9c0] frame= 1 QP=50.43 NAL=2 Slice:P Poc:4 I:812 P:481 SKIP:14707 size=4285 bytes
[libx264 @ 0x7fe50803b9c0] frame= 2 QP=51.00 NAL=0 Slice:B Poc:2 I:0 P:280 SKIP:15720 size=405 bytes
[libx264 @ 0x7fe50803b9c0] frame= 3 QP=50.66 NAL=2 Slice:P Poc:8 I:397 P:244 SKIP:15359 size=2094 bytes
[libx264 @ 0x7fe50803b9c0] frame= 4 QP=51.00 NAL=0 Slice:B Poc:6 I:1 P:359 SKIP:15640 size=657 bytes
[libx264 @ 0x7fe50803b9c0] frame= 5 QP=50.94 NAL=2 Slice:P Poc:12 I:7 P:13 SKIP:15980 size=173 bytes
[libx264 @ 0x7fe50803b9c0] frame= 6 QP=51.00 NAL=0 Slice:B Poc:10 I:0 P:4 SKIP:15996 size=132 bytes
[libx264 @ 0x7fe50803b9c0] frame= 7 QP=49.48 NAL=2 Slice:P Poc:16 I:9 P:0 SKIP:15991 size=146 bytes
[libx264 @ 0x7fe50803b9c0] frame= 8 QP=51.00 NAL=0 Slice:B Poc:14 I:0 P:4 SKIP:15996 size=132 bytes
```
However, no luck playing with mpv:
```
> mediainfo clementine.mp4
General
Complete name : clementine.mp4
Format : MPEG-4
Format profile : Base Media
Codec ID : isom (isom/iso2/avc1/mp41)
File size : 10.8 MiB
> mpv clementine.mp4
[ffmpeg/demuxer] mov,mp4,m4a,3gp,3g2,mj2: moov atom not found
[lavf] avformat_open_input() failed
[ffmpeg/demuxer] mov,mp4,m4a,3gp,3g2,mj2: moov atom not found
[lavf] avformat_open_input() failed
Failed to recognize file format.
Exiting... (Errors when loading file)
```
In general I was curious finding this project to see how it works and if it could potentially be used as a pipewire to ffmpeg bridge for other use cases (e.g. stream with mpegts instead of saving to file).
Unfortunately I can't use ffmpeg+kmsgrab because of https://trac.ffmpeg.org/ticket/10188https://invent.kde.org/plasma/kwin/-/issues/177Implicit grabs & closed windows2023-08-24T10:45:14ZVlad ZahorodniiImplicit grabs & closed windowsAn implicit grab is started if you press and hold a pointer button or a keyboard key. After that, only the client will receive the subsequent events until the last button or key is released.
It works okay if the window is not closed. Ho...An implicit grab is started if you press and hold a pointer button or a keyboard key. After that, only the client will receive the subsequent events until the last button or key is released.
It works okay if the window is not closed. However, if the window is closed, it's possible to leak release events to the next client. As an example,
- open mpv and firefox(reddit)
- focus mpv and press "q"
- mpv will be closed and the keyboard focus will move to firefox
- however, you'll also see reddit's community search field focused (this should not happen)
Another problem with implicit grabs is that we have to keep it valid even if the associated window or decoration is destroyed. See https://invent.kde.org/plasma/kwin/-/merge_requests/4315#note_746018https://invent.kde.org/plasma/print-manager/-/issues/2Printer Manager - Where to go next?2024-03-09T22:33:55ZMike NoePrinter Manager - Where to go next?**Current Status (pre 6 release)**
* Plasmoid and KCM have been cleaned up and ported to more modern QML.
Components
* The KCM uses a subset of the CUPS library features in it's own implementation.
* Likewise, the plasmoid uses the de...**Current Status (pre 6 release)**
* Plasmoid and KCM have been cleaned up and ported to more modern QML.
Components
* The KCM uses a subset of the CUPS library features in it's own implementation.
* Likewise, the plasmoid uses the declarative plugin (org.kde.plasma.printmanager) which just exposes the models and features from libkcups.
* There are 4 other apps (separate QWidget apps):
* add-printer
* config-printer
* kded (implements a redhat dbus api)
* printqueue
In addition, libkcups is using a handful of deprecated functions.
First look, it might be tempting to combine all of these (except the kded) into a Kirigami app of some sort, with the ability to "do it all" from one place.
OTOH, having separate apps gives flexibility for easy (and lightweight) access to just the feature you may want (configure or add).
At the bare minimum, we should probably:
- Update the deprecated features in libkcups
- Modernize some of the internals to make use of recent KF
- De-duplicate some of the implementation overlap among apps
**Further options:**
- Quick and easy is to then just clean up the GUI of the apps, they're not pretty.
- Longer-term and not-as-easy is to put a fresh new QML face on the apps (not the kded) in some form or another.
- A different tack might look to turning the KCM into a more comprehensive "Printer Control Panel", which might combine all the apps into the KCM itself.
As a side note, the plasmoid might enjoy a little more love with the addition of some basic jobs queues management, but it is very light and clean at this point.https://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.