[plasmashell] [Bug 488956] New: Icons-only-task manager panel unusable (on wayland) until entering edit mode since upgrade to plasma 6
https://bugs.kde.org/show_bug.cgi?id=488956 Bug ID: 488956 Summary: Icons-only-task manager panel unusable (on wayland) until entering edit mode since upgrade to plasma 6 Classification: Plasma Product: plasmashell Version: 6.1.0 Platform: Other OS: Other Status: REPORTED Severity: normal Priority: NOR Component: Panel Assignee: plasma-b...@kde.org Reporter: fake.n...@posteo.net CC: niccolo.venera...@gmail.com Target Milestone: 1.0 SUMMARY Since the upgrade to 6.0.1, and persisting til 6.1.0, unless one enters edit mode, a panel with nothing but icons only task manager -- which is to say, a dock -- appears as a panel of minimum width containing absolutely no icons. Entering edit mode causes the panel to begin to behave as expected; crashes to kwin reset to the useless state also. In said useless state, clicking on the (visually devoid of icons) panel will open apps meant to be in the task manager, in some vague correlate to their left-to-right, though again, the icons are gone and the panel is at minimum length. STEPS TO REPRODUCE The problem is visible upon login in the absence of any user action. It happens in the absence of any user behavior. It is strictly limited to wayland. entering edit mode "fixes" the problem. EXPECTED RESULT When turning on the system, panels should... exist, I guess. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Arch zen 6.9.5 KDE Plasma Version: 6.any KDE Frameworks Version: 6.3 Qt Version: 6.7.1 ADDITIONAL INFORMATION This started somewhere around plasma 6.0.2, but reversion doesn't help. changing to 6.1 does not fix the bug, but has the *added bug* that the panel, until edit mode is entered, is now on the left of the screen instead of centered. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 488957] New: column width in keyboard kcm is too small and resizeable
https://bugs.kde.org/show_bug.cgi?id=488957 Bug ID: 488957 Summary: column width in keyboard kcm is too small and resizeable Classification: Applications Product: systemsettings Version: 6.1.0 Platform: Arch Linux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: kcm_keyboard Assignee: plasma-b...@kde.org Reporter: g311571...@gmail.com CC: butir...@gmail.com, natalie_clar...@yahoo.de Target Milestone: --- Created attachment 170801 --> https://bugs.kde.org/attachment.cgi?id=170801&action=edit kcm_keyboard SUMMARY The problem is simple, using "width: 60" and "resizable: false" is too small https://invent.kde.org/plasma/plasma-desktop/-/blob/master/kcms/keyboard/ui/Layouts.qml?ref_type=heads#L314 OBSERVED RESULT Text label is cutting off as my screenshot -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 488958] New: "Wi-Fi & Networking" KCM not available
https://bugs.kde.org/show_bug.cgi?id=488958 Bug ID: 488958 Summary: "Wi-Fi & Networking" KCM not available Classification: KDE Neon Product: neon Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Live/Install images Assignee: neon-b...@kde.org Reporter: popov...@ukr.net CC: j...@jriddell.org, neon-b...@kde.org Target Milestone: --- SUMMARY "Wi-Fi & Networking" KCM not available in KDE neon Developer Edition 20240617-1605 live iso image. SOFTWARE/OS VERSIONS Operating System: KDE neon Developer Edition 20240617-1605 -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 488958] "Wi-Fi & Networking" KCM not available
https://bugs.kde.org/show_bug.cgi?id=488958 popov895 changed: What|Removed |Added CC||popov...@ukr.net -- You are receiving this mail because: You are watching all bug changes.
[frameworks-qqc2-desktop-style] [Bug 488743] `AbstractButton.TextUnderIcon` display mode stopped working
https://bugs.kde.org/show_bug.cgi?id=488743 --- Comment #4 from ratijas --- I'm not at my laptop right now, but I'm almost sure those are ToolButton instances -- You are receiving this mail because: You are watching all bug changes.
[frameworks-qqc2-desktop-style] [Bug 488743] `AbstractButton.TextUnderIcon` display mode stopped working
https://bugs.kde.org/show_bug.cgi?id=488743 --- Comment #5 from ratijas --- Indeed, that is a regular ActionToolBar without any custom display component in it's actions, meaning what you are showing are ToolButtons. https://github.com/KDE/kirigami-gallery/blob/11761e467bd78291063fce77c20127e4215a1f62/src/data/contents/ui/gallery/MiscGallery.qml#L66 -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 488480] Auto Reconcile not working
https://bugs.kde.org/show_bug.cgi?id=488480 Thomas Baumgart changed: What|Removed |Added Status|REPORTED|NEEDSINFO Resolution|--- |WAITINGFORINFO --- Comment #1 from Thomas Baumgart --- Imported transactions are marked as such. Once they are accepted (one can select all such transactions and do that in one shot) they will be marked as cleared. The setting you are talking about is meant for manually entered transactions only. Does that help? -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 487591] Global Scaling is messed up after Kubuntu Upgrade from 23.10 to 24.04
https://bugs.kde.org/show_bug.cgi?id=487591 --- Comment #4 from thomasvondere...@gmx.de --- Created attachment 170802 --> https://bugs.kde.org/attachment.cgi?id=170802&action=edit Screenshot of Scaling-Problem "Does the distortion with that scale factor also affect other GTK apps in the same way in the new user account?" For instance with Firefox and Thunderbird: The functionality is good, but they are scaled too large too. And I found out, that Cairo-Dock functions in fallback-mode fine too, but is also scaled too large. Here is a screenshot of the 3 with the software-manager in comparison. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-bluez-qt] [Bug 480621] Bluetooth applet: disabling bluetooth using rfkill takes a while and blocks the UI
https://bugs.kde.org/show_bug.cgi?id=480621 ratijas changed: What|Removed |Added Product|Bluedevil |frameworks-bluez-qt Component|system tray |general Assignee|plasma-b...@kde.org |kdelibs-b...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 488959] New: Google Pixel 7 KDE Connect randomly disconnects/reconnects
https://bugs.kde.org/show_bug.cgi?id=488959 Bug ID: 488959 Summary: Google Pixel 7 KDE Connect randomly disconnects/reconnects Classification: Applications Product: kdeconnect Version: 1.3.1 Platform: Android OS: Android 13.x Status: REPORTED Severity: minor Priority: NOR Component: android-application Assignee: albertv...@gmail.com Reporter: dai...@gmail.com CC: andrew.g.r.hol...@gmail.com Target Milestone: --- SUMMARY I have a Google Pixel 7 phone (Android version 14) which connects to a Gentoo Linux KDE (Plasma 5.27.11) KDE Connect version 23.08.5-r1. The phone will connect & disconnect randomly when at home on the same wifi. I also have a Google Pixel 7 phone (Android version 14) which connects & stays connected reliably. STEPS TO REPRODUCE 1. Install KDE Connect on a Pixel 7 2. Monitor the connection status 3. OBSERVED RESULT The connection drops out, with both sides declaring neither is on the same network, then will randomly reconnect without intervention. EXPECTED RESULT They should stay connected while on the same WiFi. SOFTWARE/OS VERSIONS Linux/KDE Plasma: 5.27.11 KDE Plasma Version: 5.27.11-r1 KDE Frameworks Version: 5.116.0 Qt Version: 5.15.14 ADDITIONAL INFORMATION Leaving the house so that the phone is outside the WiFi range will sometimes cause a reconnect when returning. Turning the WiFi off/on on the phone has no effect. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 485769] Autologin settings for SDDM not read from kde_settings.conf correctly
https://bugs.kde.org/show_bug.cgi?id=485769
--- Comment #11 from Li Jiajun ---
Created attachment 170803
--> https://bugs.kde.org/attachment.cgi?id=170803&action=edit
Screenshot_shows_fixing_the_issue_by_reverting_the_commit_of_kirigami
Flozza is right.
I fixed the issue by comment out the commit of kirigami
458003901cfcdbea2e3789e320d44725f5a18428
Perhaps SDDM-KCM requires modifications to accommodate the changes implemented
in Kirigami.
Here is my patch to comment out that commit as temporal fix.
>From ccc65a2a206de614acb13154d40516fe5082c45a Mon Sep 17 00:00:00 2001
From: wlmqljj
Date: Sat, 22 Jun 2024 16:51:12 +0800
Subject: [PATCH] revert
https://invent.kde.org/frameworks/kirigami/-/merge_requests/1480
---
src/layouts/columnview.cpp | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/src/layouts/columnview.cpp b/src/layouts/columnview.cpp
index 583a8885..bb729271 100644
--- a/src/layouts/columnview.cpp
+++ b/src/layouts/columnview.cpp
@@ -709,10 +709,10 @@ void ContentItem::updateVisibleItems()
m_visibleItems.removeAll(item);
});
attached->setInViewport(true);
-item->setEnabled(true);
+// item->setEnabled(true);
} else {
attached->setInViewport(false);
-item->setEnabled(false);
+// item->setEnabled(false);
}
}
--
2.45.2
--
You are receiving this mail because:
You are watching all bug changes.
[kwin] [Bug 476567] With some authentication methods (e.g. fingerprint and smartcard), moving the cursor during the screen lock grace period breaks the locker
https://bugs.kde.org/show_bug.cgi?id=476567 aux...@gmail.com changed: What|Removed |Added CC||aux...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[Elisa] [Bug 488960] New: Elisa crashed while browsing playlist
https://bugs.kde.org/show_bug.cgi?id=488960 Bug ID: 488960 Summary: Elisa crashed while browsing playlist Classification: Applications Product: Elisa Version: 24.05.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: matthieu_gall...@yahoo.fr Reporter: germano.massu...@gmail.com Target Milestone: --- Created attachment 170804 --> https://bugs.kde.org/attachment.cgi?id=170804&action=edit gdb Elisa crashed while browsing playlist Qt 6.7.1 See attached gdb -- You are receiving this mail because: You are watching all bug changes.
[KRdp] [Bug 488961] New: Unable to connect or use
https://bugs.kde.org/show_bug.cgi?id=488961
Bug ID: 488961
Summary: Unable to connect or use
Classification: Plasma
Product: KRdp
Version: 6.1.0
Platform: Other
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: general
Assignee: unassigned-b...@kde.org
Reporter: tts...@outlook.com
CC: ahiems...@heimr.nl
Target Milestone: ---
SUMMARY
I'm using KRdp on Arch Linux, however it does not work properly and I have no
idea about its logs. Only got a black screen on
[aFreeRDP](https://f-droid.org/en/packages/com.freerdp.afreerdp/), or
immediately disconnect with [another RDP
client](https://play.google.com/store/apps/details?id=com.devolutions.remotedesktopmanager).
STEPS TO REPRODUCE
1. Install package `krdp` via pacman.
2. Run `krdpserver -u test -p test` in the terminal, and press "Share" in the
prompt.
3. Observe the output. The program will periodically output errors.
4. Connect the RDP server with aFreeRDP.
OBSERVED RESULT
Client got a blacks screen with nothing can be controlled, or disconnect
immediately.
EXPECTED RESULT
The screen appears on the client and can be controlled.
SOFTWARE/OS VERSIONS
Linux: Arch Linux
KDE Plasma Version: 6.1.0
KDE Frameworks Version: 6.3.0
Qt Version: 6.7.1
ADDITIONAL INFORMATION
When the client starts the connection, a same prompt as when the program starts
pops out and immediately disappears.
Here's a complete log with steps described above:
```
org.kde.krdp: Initializing Freedesktop Portal Session
org.kde.krdp: Listening for connections on QHostAddress("0.0.0.0") 3389
org.kde.krdp: Started Freedesktop Portal session
kpipewire_vaapi_logging: VAAPI: Failed to initialize display
kpipewire_vaapi_logging: VAAPI: Failed to initialize display
kpipewire_vaapi_logging: DRM device not found
org.kde.krdp: Closing Freedesktop Portal Session
org.kde.krdp: Initializing Freedesktop Portal Session
org.kde.krdp: Session setup completed, start processing...
[16:53:50:238] [36378:36418] [ERROR][com.freerdp.core.transport] - BIO_read
returned a system error 0: 成功
[16:53:50:239] [36378:36418] [ERROR][com.freerdp.core] -
transport_read_layer:freerdp_set_last_error_ex
ERRCONNECT_CONNECT_TRANSPORT_FAILED [0x0002000D]
org.kde.krdp: Unable to check file descriptor
org.kde.krdp: Closing session
org.kde.krdp: Closing Freedesktop Portal Session
org.kde.krdp: Initializing Freedesktop Portal Session
org.kde.krdp: Session setup completed, start processing...
[16:54:00:238] [36378:36431] [ERROR][com.freerdp.core.transport] - BIO_read
returned a system error 0: 成功
[16:54:00:238] [36378:36431] [ERROR][com.freerdp.core] -
transport_read_layer:freerdp_set_last_error_ex
ERRCONNECT_CONNECT_TRANSPORT_FAILED [0x0002000D]
org.kde.krdp: Unable to check file descriptor
org.kde.krdp: Closing session
org.kde.krdp: Closing Freedesktop Portal Session
org.kde.krdp: Initializing Freedesktop Portal Session
org.kde.krdp: Session setup completed, start processing...
[16:54:10:239] [36378:36434] [ERROR][com.freerdp.core.transport] - BIO_read
returned a system error 0: 成功
[16:54:10:239] [36378:36434] [ERROR][com.freerdp.core] -
transport_read_layer:freerdp_set_last_error_ex
ERRCONNECT_CONNECT_TRANSPORT_FAILED [0x0002000D]
org.kde.krdp: Unable to check file descriptor
org.kde.krdp: Closing session
org.kde.krdp: Closing Freedesktop Portal Session
org.kde.krdp: Initializing Freedesktop Portal Session
org.kde.krdp: Session setup completed, start processing...
[16:54:20:240] [36378:36437] [ERROR][com.freerdp.core.transport] - BIO_read
returned a system error 0: 成功
[16:54:20:240] [36378:36437] [ERROR][com.freerdp.core] -
transport_read_layer:freerdp_set_last_error_ex
ERRCONNECT_CONNECT_TRANSPORT_FAILED [0x0002000D]
org.kde.krdp: Unable to check file descriptor
org.kde.krdp: Closing session
org.kde.krdp: Closing Freedesktop Portal Session
org.kde.krdp: Initializing Freedesktop Portal Session
org.kde.krdp: Session setup completed, start processing...
[16:54:22:033] [36378:36440] [INFO][com.freerdp.core.connection] - Client
Security: NLA:1 TLS:1 RDP:0
[16:54:22:033] [36378:36440] [INFO][com.freerdp.core.connection] - Server
Security: NLA:1 TLS:0 RDP:0
[16:54:22:033] [36378:36440] [INFO][com.freerdp.core.connection] - Negotiated
Security: NLA:1 TLS:0 RDP:0
[16:54:22:039] [36378:36440] [WARN][com.winpr.negotiate] -
AcceptSecurityContext status SEC_I_CONTINUE_NEEDED [0x00090312]
[16:54:22:041] [36378:36440] [WARN][com.winpr.negotiate] -
AcceptSecurityContext status SEC_I_COMPLETE_NEEDED [0x00090313]
[16:54:22:045] [36378:36440] [INFO][com.freerdp.core.connection] - Accepted
client: aFreeRDP-1694a1
[16:54:22:045] [36378:36440] [INFO][com.freerdp.core.connection] - Accepted
channels:
[16:54:22:045] [36378:36440] [INFO][com.freerdp.core.connection] - rdpdr
[16:54:22:045] [36378:36440] [INFO][com.freerdp.core.connection] - rdpsnd
[16:54:22:045] [36378:36440] [INFO][
[Elisa] [Bug 488960] Elisa crashed while browsing playlist
https://bugs.kde.org/show_bug.cgi?id=488960 Bug Janitor Service changed: What|Removed |Added Severity|normal |crash -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 488944] Down scaling makes widget controls hard to click
https://bugs.kde.org/show_bug.cgi?id=488944 --- Comment #2 from medin --- (In reply to cwo from comment #1) > You can close the "Panel Configuration" dialog to increase the size of the > desktop view, and if you need an even larger view, the "Add Widget" dialog > as well. If we need to close panel and widget sidebar, then the whole idea of this new edit mode has no meaning and solves nothing at all. I don't know how it got accepted as a feature. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 488944] Down scaling makes widget controls hard to click
https://bugs.kde.org/show_bug.cgi?id=488944 --- Comment #3 from cwo --- You use the Panel Configuration dialog if you want to edit the panel. It's not necessary if you want to edit the widgets on the desktop, and if you enter edit mode through the desktop context menu, it's not shown until the user explicitly opens it. This is why they are separate dialogs. I'm not sure what kind of solution you expect. If the additional dialogs are open, either the view on the desktop has to be made smaller (as it is now), or the dialogs would have to overlap the desktop, and then you couldn't interact with widgets that are in the overlapping areas. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 469440] The Media Control Applet crashes Plasma at QOpenGLContext::functions()
https://bugs.kde.org/show_bug.cgi?id=469440 Alex changed: What|Removed |Added Status|NEEDSINFO |REPORTED Resolution|WAITINGFORINFO |--- -- You are receiving this mail because: You are watching all bug changes.
[kactivitymanagerd] [Bug 482892] Switching activities also switches active virtual desktop
https://bugs.kde.org/show_bug.cgi?id=482892 Kevin Krammer changed: What|Removed |Added Version|6.0.2 |6.1.0 -- You are receiving this mail because: You are watching all bug changes.
[kdeplasma-addons] [Bug 488574] Sidebar task switch doesn't show correctly
https://bugs.kde.org/show_bug.cgi?id=488574 --- Comment #4 from Alireza Rashidi --- Created attachment 170805 --> https://bugs.kde.org/attachment.cgi?id=170805&action=edit "Add widget" popup -- You are receiving this mail because: You are watching all bug changes.
[kdeplasma-addons] [Bug 488574] Sidebar task switch doesn't show correctly
https://bugs.kde.org/show_bug.cgi?id=488574 --- Comment #5 from Alireza Rashidi --- The "Add widget" popup on KDE v6.1.0 is causing me the same issue, and I've added it to the attachments. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 484323] High CPU load of kwin_x11 when locking or turning off the screen
https://bugs.kde.org/show_bug.cgi?id=484323 --- Comment #34 from Kevin Krammer --- After upgrade to Plasma 6.1 the behavior is still present but not as bad as before. Xorg still goes up to ~50% of one CPU, but kwin_x11 only to 30% and ksmserver only to 15% -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 484323] High CPU load of kwin_x11 when locking or turning off the screen
https://bugs.kde.org/show_bug.cgi?id=484323 Kevin Krammer changed: What|Removed |Added Version|6.0.3 |6.1.0 -- You are receiving this mail because: You are watching all bug changes.
[calligraplan] [Bug 488926] The application named "Plan" is listed twice on the website apps.kde.org
https://bugs.kde.org/show_bug.cgi?id=488926 Ben Cooksley changed: What|Removed |Added Component|apps.kde.org|general Product|www.kde.org |calligraplan Assignee|kde-...@kde.org |dag.ander...@kdemail.net --- Comment #1 from Ben Cooksley --- This is caused by Calligra Plan providing multiple Appstream metainfo files - reassigning to Calligra Plan as the fix should be done there. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 484327] Bad initial window sizes
https://bugs.kde.org/show_bug.cgi?id=484327 Kevin Krammer changed: What|Removed |Added Version|6.0.1 |6.1.0 --- Comment #3 from Kevin Krammer --- (In reply to Tobias Leupold from comment #2) > It seems like one of the problems has been resolved meanwhile: The main > window restores its size (not its position) when restarting. Just had this one again after the upgrade to 6.1 and also verified that I also still see the other two issues. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 488944] Down scaling makes widget controls hard to click
https://bugs.kde.org/show_bug.cgi?id=488944 --- Comment #4 from medin --- (In reply to cwo from comment #3) > You use the Panel Configuration dialog if you want to edit the panel. It's > not necessary if you want to edit the widgets on the desktop, and if you > enter edit mode through the desktop context menu, it's not shown until the > user explicitly opens it. This is why they are separate dialogs. > > I'm not sure what kind of solution you expect. If the additional dialogs are > open, either the view on the desktop has to be made smaller (as it is now), > or the dialogs would have to overlap the desktop, and then you couldn't > interact with widgets that are in the overlapping areas. The only advanage I found is moving the added widgets in that small scaled view. -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 482891] Kolab resource gone after upgrade to 6.0.0 mega release and not migrated to IMAP either
https://bugs.kde.org/show_bug.cgi?id=482891 --- Comment #1 from Kevin Krammer --- Kolab Resource still missing from kpim6-kdepim-runtime package after upgrade to 6.1 -- You are receiving this mail because: You are watching all bug changes.
[kcalc] [Bug 488962] New: Changing display font resets display field to 0
https://bugs.kde.org/show_bug.cgi?id=488962 Bug ID: 488962 Summary: Changing display font resets display field to 0 Classification: Applications Product: kcalc Version: 24.05.1 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: evan.te...@gmail.com Reporter: popov...@ukr.net CC: gabriel.barrantes@outlook.com Target Milestone: --- SUMMARY Changing display font resets display field to 0. STEPS TO REPRODUCE 1. Do some calculation 2. Open Settings > Font 3. Change "Display font" OBSERVED RESULT The display field resets to 0. EXPECTED RESULT The display field keeps its value unchanged. SOFTWARE/OS VERSIONS Operating System: openSUSE Tumbleweed 20240609 KDE Plasma Version: 6.0.5 KDE Frameworks Version: 6.3.0 KDE Gear Version: 24.05.1 Qt Version: 6.7.1 -- You are receiving this mail because: You are watching all bug changes.
[kcalc] [Bug 488962] Changing display font resets display field to 0
https://bugs.kde.org/show_bug.cgi?id=488962 popov895 changed: What|Removed |Added CC||popov...@ukr.net -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 488871] `kwin_x11` hogs CPU
https://bugs.kde.org/show_bug.cgi?id=488871 Thorolf E.R. Weißhuhn changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED --- Comment #1 from Thorolf E.R. Weißhuhn --- I cannot reproduce now. Went back to a system snapshot about 2 weeks old, then a summary update (Discover) of all ~1.6k updates, now kwin_x11 stays in the lower 1-digit cpu usage percent. Changing to resolved. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 488963] New: wl_output order doesn't respect KScreen priority settings
https://bugs.kde.org/show_bug.cgi?id=488963 Bug ID: 488963 Summary: wl_output order doesn't respect KScreen priority settings Classification: Plasma Product: kwin Version: 6.1.0 Platform: Arch Linux OS: Linux Status: REPORTED Severity: major Priority: NOR Component: multi-screen Assignee: kwin-bugs-n...@kde.org Reporter: o...@np880.ru Target Milestone: --- Created attachment 170806 --> https://bugs.kde.org/attachment.cgi?id=170806&action=edit Screen Priorities SUMMARY I have 3 monitors, with my primary monitor in the middle. I've set screen priorities with the middle monitor as a primary monitor. But KWin doesn't respect this setting and place wl_outputs in arbitrary order (probably how monitors were initialized during boot). This is very annoying since a there's no concept of primary monitor in Wayland and most fullscreen apps (mostly SDL ones) are putting themselves on a first reported wl_output. STEPS TO REPRODUCE 1. Log into system (either with autologin or SDDM) 2. Look at the KScreen priority settings (attachment) 3. Compare them to wl_outputs order in System Info Wayland section (additional info) OBSERVED RESULT wl_outputs order MUST match KScreen's display order (kscreen-console outputs or kscreen-doctor -o) EXPECTED RESULT wl_outputs order differs from KScreen's one, most importantly primary display isn't the first reported wl_output SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 6.1.0 KDE Frameworks Version: 6.3.0 Qt Version: 6.7.1 Kernel Version: 6.9.5-2-cachyos (64-bit) Graphics Platform: Wayland Processors: 8 × Intel® Core™ i7-7700K CPU @ 4.20GHz Memory: 15.6 ГиБ of RAM Graphics Processor: AMD Radeon RX 6700 XT ADDITIONAL INFORMATION interface: 'kde_output_device_v2', version: 8, name: 59 interface: 'kde_output_device_v2', version: 8, name: 60 interface: 'kde_output_device_v2', version: 8, name: 61 interface: 'wl_output', version: 4, name: 62 name: HDMI-A-1 description: Philips Consumer Electronics Company Philips 235PL/DL41103143133 x: 3840, y: 0, scale: 1, physical_width: 510 mm, physical_height: 287 mm, make: 'Philips Consumer Electronics Company', model: 'Philips 235PL/DL41103143133', subpixel_orientation: unknown, output_transform: 90°, mode: width: 1920 px, height: 1080 px, refresh: 60.000 Hz, flags: current interface: 'wl_output', version: 4, name: 63 name: DP-2 description: Philips Consumer Electronics Company Philips 226V4/UK81443014262 x: 0, y: 0, scale: 1, physical_width: 477 mm, physical_height: 268 mm, make: 'Philips Consumer Electronics Company', model: 'Philips 226V4/UK81443014262', subpixel_orientation: unknown, output_transform: normal, mode: width: 1920 px, height: 1080 px, refresh: 60.000 Hz, flags: current interface: 'wl_output', version: 4, name: 64 name: DP-1 description: ASR PG27FF1A/0x0D42 x: 1920, y: 0, scale: 1, physical_width: 598 mm, physical_height: 336 mm, make: 'ASR', model: 'PG27FF1A/0x0D42', subpixel_orientation: unknown, output_transform: normal, mode: width: 1920 px, height: 1080 px, refresh: 165.003 Hz, flags: current -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 487904] Stuff using Kirigami InlineMessage and PlaceholderMessage fail to load with error `Cannot assign object of type \"Action\" to property of type \"Action_QMLTYPE_72*\" as the
https://bugs.kde.org/show_bug.cgi?id=487904 ezh changed: What|Removed |Added CC||eugene.savit...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 488963] wl_output order doesn't respect KScreen priority settings
https://bugs.kde.org/show_bug.cgi?id=488963 --- Comment #1 from Oleg --- Created attachment 170807 --> https://bugs.kde.org/attachment.cgi?id=170807&action=edit kscreen-console outputs log Here is also "kscreen-console outputs" log. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 340982] No way to change just the date format but not its actual translated text
https://bugs.kde.org/show_bug.cgi?id=340982 Anton changed: What|Removed |Added Status|RESOLVED|REOPENED Resolution|UPSTREAM|--- CC||anton.mel...@outlook.com --- Comment #266 from Anton --- I'm not sure what the situation is but I have just installed kde-full on Ubuntu 24.04 and it appears there is no way to not have the unbelievably stupid American date format, almost 10 years after this bug was created. I must be missing something, and it must be possible. When you click on "Set time format" it takes me to the "Region & Language" settings. There are no US/North American values configured, only British English. The British do not format their dates MM/DD/. So there is at least that bug. What QT does is obviously irrelevant... -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 488963] wl_output order doesn't respect KScreen priority settings
https://bugs.kde.org/show_bug.cgi?id=488963 --- Comment #2 from Oleg --- I've mixed up expected and observed results sections, sorry. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 487904] Stuff using Kirigami InlineMessage and PlaceholderMessage fail to load with error `Cannot assign object of type \"Action\" to property of type \"Action_QMLTYPE_72*\" as the
https://bugs.kde.org/show_bug.cgi?id=487904 postix changed: What|Removed |Added CC||pos...@posteo.eu -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 488225] After waking from a sleep of a few hours, the desktop session shows a black screen with a cursor
https://bugs.kde.org/show_bug.cgi?id=488225 postix changed: What|Removed |Added CC||pos...@posteo.eu -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 488225] After waking from a sleep of a few hours, the desktop session shows a black screen with a cursor
https://bugs.kde.org/show_bug.cgi?id=488225 postix changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=477738 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 477738] [AMD, NVIDIA] kwin on Wayland black screen with cursor after most resume-from-RAM
https://bugs.kde.org/show_bug.cgi?id=477738 postix changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=488225 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 488964] New: Slide animation broken since 6.1.0 when switching activities
https://bugs.kde.org/show_bug.cgi?id=488964 Bug ID: 488964 Summary: Slide animation broken since 6.1.0 when switching activities Classification: Plasma Product: kwin Version: 6.1.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: activities Assignee: kwin-bugs-n...@kde.org Reporter: bastimeyer...@gmail.com Target Milestone: --- Created attachment 170808 --> https://bugs.kde.org/attachment.cgi?id=170808&action=edit Missing slide animation when switching activities (same virtual desktop) SUMMARY This started after the 6.1.0 upgrade. I have 2 activities set up with 9 virtual desktops, aligned in a 3x3 grid. I can't find the config option right now, but I know that I had kwin configured to remember the current virtual desktop on each separate activity, which is relevant here. Not sure if this config has been removed and now defaults to always being true. Anyway, now to the issue... Previously, when switching activities, regardless whether this also involved switching to a different virtual desktop due to the other activity being on a different one, the slide switching animation was shown, similar to when switching virtual desktops on the same activity. Now, since 6.1.0, no slide animation is shown when switching activities unless there's also a switch to a different virtual desktop involved. Please see the attached video. The activity with the tree wallpaper is the first one, while the hexagon wallpaper is on the second activity. A quick note though, before toggling the slide animation in the virtual desktop settings menu for the purpose of reproducing the bug in the recorded video, a slide animation was shown when switching from the first to the second activity, but not when switching from the second to the first one. But now even after restoring all settings, no animation is played at all, just like shown in the video. STEPS TO REPRODUCE 1. Set up more than one activity and have the slide animation enabled when switching virtual desktops 2. Have activities on the same virtual desktop, switch activities, no animation at all 3. Have activities use different virtual desktops, switch activities, see the slide animation EXPECTED BEHAVIOR The slide animation should always be played, not just when also switching virtual desktops. For example, if the same wallpaper was used and no applications/windows were on the desktops of both activities, then the user would not be aware that the activities were indeed switched, because no animation was shown, which is confusing and bad. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Arch Linux KDE Plasma Version: 6.1.0 KDE Frameworks Version: 6.3.0 Qt Version: 6.7.1 -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 478975] Missing V360 and 3D Effects
https://bugs.kde.org/show_bug.cgi?id=478975 Proteus Four changed: What|Removed |Added CC||proteu...@infomaniak.ch --- Comment #1 from Proteus Four --- Hi fellas, I've the same problem on linux, No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 22.04.2 LTS Release:22.04 Codename: jammy The app used is the appimage 24.5.0 x86_64. the version of kdenlive is : 23.08.04. In the effect window, the item menu VR360 and 3D, only the effect Stereoscopic 3D is visible. I've tried to find an issue, but nothing found. Thank you for your help, I can't use my VR360 images without this tool. I'm blocked. If you have other options to transform this kind of videos, I'm your guy. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 488965] New: Most KCMs are unreadable via System Settings, but readable via KCMShell6.
https://bugs.kde.org/show_bug.cgi?id=488965 Bug ID: 488965 Summary: Most KCMs are unreadable via System Settings, but readable via KCMShell6. Classification: Applications Product: systemsettings Version: 6.0.4 Platform: Fedora RPMs URL: https://www.mediafire.com/file/2pvn6adh2tgh0te/Screenc ast_20240622_115500.webm/file OS: Linux Status: REPORTED Severity: major Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: 4wy78...@rokejulianlockhart.addy.io Target Milestone: --- Created attachment 170809 --> https://bugs.kde.org/attachment.cgi?id=170809&action=edit Reproduction screencast. STEPS TO REPRODUCE 1. Updated OS using `plasma-discover`. 2. `systemctl reboot`. 3. `systemsettings`. 4. Select any of the KCMs depicted at https://www.mediafire.com/file/2pvn6adh2tgh0te/Screencast_20240622_115500.webm/file - the "Colour & Theme" ones are all broken. OBSERVED RESULT > **Error loading QML file.** > > ```log > qrc:/kcm/kcm_sddm/main.qml:38 Type NewStuff.Action unavailable > qrc:/qt/qml/org/kde/newstuff/Action.qml:167 Type NewStuff.Page unavailable > qrc:/qt/qml/org/kde/newstuff/Page.qml:133 Type Kirigami.InlineMessage > unavailable > file:///usr/lib64/qt6/qml/org/kde/kirigami/InlineMessage.qml:63 Type > KT.InlineMessage unavailable > qrc:/qt/qml/org/kde/kirigami/templates/InlineMessage.qml:123 Cannot assign > object of type "TP.IconPropertiesGroup" to property of type > "IconPropertiesGroup_QMLTYPE_81*" as the former is neither the same as the > latter nor a sub-class of it. > ``` EXPECTED RESULT All KCMs listed should be visible via `systemsettings`. SOFTWARE/OS VERSIONS Operating System: Fedora Linux 40 KDE Plasma Version: 6.1.0 KDE Frameworks Version: 6.3.0 Qt Version: 6.7.1 Kernel Version: 6.9.5-200.fc40.x86_64 (64-bit) Graphics Platform: Wayland Processors: 12 × AMD Ryzen 5 7600X 6-Core Processor Memory: 30.5 GiB of RAM Graphics Processor: AMD Radeon RX 5700 Manufacturer: ASRock Product Name: X670E Taichi -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 340982] No way to change just the date format but not its actual translated text
https://bugs.kde.org/show_bug.cgi?id=340982 dmatteo...@gmail.com changed: What|Removed |Added CC||dmatteo...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 488966] New: Uncontrolled windows and unusable desktop environment after upgrading to KDE 6.1.0
https://bugs.kde.org/show_bug.cgi?id=488966 Bug ID: 488966 Summary: Uncontrolled windows and unusable desktop environment after upgrading to KDE 6.1.0 Classification: Plasma Product: kwin Version: 6.1.0 Platform: Arch Linux OS: Linux Status: REPORTED Severity: critical Priority: NOR Component: generic-crash Assignee: kwin-bugs-n...@kde.org Reporter: jsha...@qq.com Target Milestone: --- Created attachment 170810 --> https://bugs.kde.org/attachment.cgi?id=170810&action=edit bug overview *** If you're not sure this is actually a bug, instead post about it at https://discuss.kde.org If you're reporting a crash, attach a backtrace with debug symbols; see https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** SUMMARY After upgrading to KDE 6.1.0, my desktop environment became totally unusable. The opened windows have no frame (title bar, maximize/minimize/close buttons), so I can't control them. Some actions like "Alt + Tab" doesn't work as well. Meanwhile, the opened windows are not shown on my task bar. In the system settings - Virtual Desktops, an error shown up says "There was an error requesting information from the compositor". So I guess something happened that led to the broken of the compositor. I use KDE under X11 environment. I have tried to switch to Wayland, but I cannot log in Wayland through SDDM (After successful login, the screen turns black and soon return back to the login screen.) STEPS TO REPRODUCE 1. Upgrade KDE to 6.1.0 OBSERVED RESULT Opened windows are not controllable. EXPECTED RESULT They can be controlled as normal. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Arch Linux x86_64 / KDE 6.1.0 (available in About System) KDE Plasma Version: 6.1.0 KDE Frameworks Version: 6.1.0 Qt Version: 6.7.1 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 488966] Uncontrolled windows and unusable desktop environment after upgrading to KDE 6.1.0
https://bugs.kde.org/show_bug.cgi?id=488966 Znshje changed: What|Removed |Added CC||jsha...@qq.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 488967] New: Visual bell invert screen flashes the app window white instead of inverting
https://bugs.kde.org/show_bug.cgi?id=488967 Bug ID: 488967 Summary: Visual bell invert screen flashes the app window white instead of inverting Classification: Plasma Product: kwin Version: 6.1.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: compositing Assignee: kwin-bugs-n...@kde.org Reporter: brodierobertson54...@gmail.com Target Milestone: --- Created attachment 170811 --> https://bugs.kde.org/attachment.cgi?id=170811&action=edit Application window flashing white *** If you're not sure this is actually a bug, instead post about it at https://discuss.kde.org If you're reporting a crash, attach a backtrace with debug symbols; see https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** SUMMARY When the visual bell invert screen is enabled, the application window does not invert, instead it flashes white. STEPS TO REPRODUCE 1. Enable invert screen under visual bell 2. Try an application that causes the bell (GIMP for example) 3. App does not invert, instead flashes white OBSERVED RESULT Application instead of inverting flashes white EXPECTED RESULT Application window should invert SOFTWARE/OS VERSIONS Linux/KDE Plasma: (available in About System) KDE Plasma Version: 6.1.0 KDE Frameworks Version: 6.3.0 Qt Version: 6.7.1 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 488968] New: Audible Bell (probably more components) don't respect system sounds theme
https://bugs.kde.org/show_bug.cgi?id=488968 Bug ID: 488968 Summary: Audible Bell (probably more components) don't respect system sounds theme Classification: Plasma Product: kwin Version: 6.1.0 Platform: Arch Linux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: core Assignee: kwin-bugs-n...@kde.org Reporter: skylyn.bilen...@gmail.com Target Milestone: --- SUMMARY STEPS TO REPRODUCE 1. Set system audio theme to (for example) Oxygen 2. Do something that triggers the audible bell. (Like pressing Escape in GIMP) OBSERVED RESULT it plays the sound provided by freedesktop instead of the bell sound from Oxygen EXPECTED RESULT it plays sounds selected in the theme. SOFTWARE/OS VERSIONS Linux/KDE Plasma: ArchLinux (available in About System) KDE Plasma Version: 6.1 KDE Frameworks Version: 6.3.0 Qt Version: 6.7.1 ADDITIONAL INFORMATION Either the audio themes need to stop shipping formats that're unsupported, or more audio formats need to be allowed by more parts of kwin and system settings and whatnot -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 488893] Floating panel leads to graphical glitches caused by maximizing windows
https://bugs.kde.org/show_bug.cgi?id=488893 --- Comment #4 from Max --- I can confirm that disabling the "Maximize" animation fixes the issue. Moreover, I could reproduce the bug on the latest KDE neon Developer Edition on two different computers. A laptop: SOFTWARE/OS VERSIONS Operating System: KDE neon Unstable Edition KDE Plasma Version: 6.1.80 KDE Frameworks Version: 6.4.0 Qt Version: 6.7.0 Kernel Version: 6.5.0-35-generic (64-bit) Graphics Platform: Wayland Processors: 6 × AMD Ryzen 5 4500U with Radeon Graphics Memory: 7.2 GiB of RAM Graphics Processor: AMD Radeon Graphics Manufacturer: ASUSTeK COMPUTER INC. Product Name: VivoBook_ASUSLaptop TP420IA_TM420IA System Version: 1.0 And a PC: SOFTWARE/OS VERSIONS Operating System: KDE neon Unstable Edition KDE Plasma Version: 6.1.80 KDE Frameworks Version: 6.4.0 Qt Version: 6.7.0 Kernel Version: 6.5.0-35-generic (64-bit) Graphics Platform: Wayland Processors: 4 × Intel® Core™ i5-2300 CPU @ 2.80GHz Memory: 7.7 GiB of RAM Graphics Processor: NV137 Manufacturer: MEDIONPC Product Name: MS-7707 System Version: 1.1 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 488968] Audible Bell (probably more components) don't respect system sounds theme or can't use themes' provided formats
https://bugs.kde.org/show_bug.cgi?id=488968 Skylyn Bilen changed: What|Removed |Added Summary|Audible Bell (probably more |Audible Bell (probably more |components) don't respect |components) don't respect |system sounds theme |system sounds theme or ||can't use themes' provided ||formats -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 488068] Custom bottom panel width leads to wrong position of panel on Plasma 6 X11
https://bugs.kde.org/show_bug.cgi?id=488068 Maximilian Böhm changed: What|Removed |Added Resolution|WAITINGFORINFO |FIXED Status|NEEDSINFO |RESOLVED --- Comment #6 from Maximilian Böhm --- Seems to be fixed in Plasma 6.1! Nice! -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 488969] New: After performing a clean install of Tuxedo OS 3, Dolphin keeps crashing when trying to open. Only the flatpak version works, but that is not as full featured.
https://bugs.kde.org/show_bug.cgi?id=488969 Bug ID: 488969 Summary: After performing a clean install of Tuxedo OS 3, Dolphin keeps crashing when trying to open. Only the flatpak version works, but that is not as full featured. Classification: Applications Product: dolphin Version: 24.02.2 Platform: Other OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: wazsal...@proton.me CC: kfm-de...@kde.org Target Milestone: --- *** If you're not sure this is actually a bug, instead post about it at https://discuss.kde.org If you're reporting a crash, attach a backtrace with debug symbols; see https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** SUMMARY After performing a clean install of Tuxedo OS 3, Dolphin keeps crashing when trying to open. Only the flatpak version works, but that is not as full featured. STEPS TO REPRODUCE 1. Install Tuxedo OS 3 from ISO. 2. Uninstall dolphin flatpak if installed. 3. Install dolphin jammy release. OBSERVED RESULT Dolphin doesn't load and instead there's a pop up saying the crash has been reported. EXPECTED RESULT Dolphin loads. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: TUXEDO OS 3 (available in About System) KDE Plasma Version: 6.0.5 KDE Frameworks Version: 6.2.0 Qt Version: 6.7.0 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 470369] Add "Pin Screenshot" Functionality to Spectacle
https://bugs.kde.org/show_bug.cgi?id=470369 seaswimmerthe...@gmail.com changed: What|Removed |Added CC||seaswimmerthe...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[Elisa] [Bug 488970] New: Wrong song is playing after pause
https://bugs.kde.org/show_bug.cgi?id=488970 Bug ID: 488970 Summary: Wrong song is playing after pause Classification: Applications Product: Elisa Version: 24.05.0 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: matthieu_gall...@yahoo.fr Reporter: mosa...@posteo.de Target Milestone: --- SUMMARY After a new song has been added to the playlist, it shows the playing indicator but another song of the playlist can be heard. The "Pause" and "Play" symbols don't match what can be heard. You can trigger that weird behaviour this way: STEPS TO REPRODUCE 1. Put one song into the empty playlist and play it. 2. Pause the playout by pressing the pause button. 3. Put another song into the playlist. 4. Play the new song by clicking it. OBSERVED RESULT The first song is playing again, but the "play"-symbol is on the new song. For the first song there still is the "pause"-symbol showing. EXPECTED RESULT The new song should be playing and the "pause"-symbol should disappear from the other song which had been paused previously. SOFTWARE/OS VERSIONS Operating System: Fedora Linux 40 KDE Plasma Version: 6.1.0 KDE Frameworks Version: 6.3.0 Qt Version: 6.7.1 Kernel Version: 6.9.4-200.fc40.x86_64 (64-bit) Graphics Platform: Wayland -- You are receiving this mail because: You are watching all bug changes.
[kstars] [Bug 488382] 3.7.1 DMG not readable
https://bugs.kde.org/show_bug.cgi?id=488382 --- Comment #18 from Jean-Claude --- (In reply to Rob from comment #16) > Do all of your devices use drivers from the 3rd Party Repo? > https://github.com/indilib/indi-3rdparty I noticed today that the 3rd Party > recipe dependency was missing from the craft KStars build recipe, so it > would make sense that those drivers don't work since they were not built. > But do you have any devices that use drivers from the main INDI repo? > https://github.com/indilib/indi. I would expect those drivers to still work > properly. Rob, Did you notice that the size of kstars 3.7.1 dmg has strongly diminished compared to the previous versions ? kstars 3.7.1 dmg = 172.2 MB kstars 3.6.8 dmg = 291.7 MB This could be the reason why the drivers can't be loaded. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 487750] Kwin never notifies the systemd watchdog and gets killed
https://bugs.kde.org/show_bug.cgi?id=487750 Jonas Rakebrandt changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |REPORTED --- Comment #9 from Jonas Rakebrandt --- (In reply to Vlad Zahorodnii from comment #8) > We disabled the watchdog in 6.1 release. Is kwin still getting killed in > 6.1.0? No, with watchdog disabled in 6.1.0 kwin doesn't get killed -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 481003] display brightness applet laggy and sometimes does not react to input
https://bugs.kde.org/show_bug.cgi?id=481003 Jakob Petsovits changed: What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|--- |FIXED Latest Commit||https://invent.kde.org/plas ||ma/powerdevil/-/commit/0338 ||25d2217ec3c91af5af1fc0a6fbb ||66f91fdbd --- Comment #5 from Jakob Petsovits --- Git commit 033825d2217ec3c91af5af1fc0a6fbb66f91fdbd by Jakob Petsovits. Committed on 22/06/2024 at 11:46. Pushed by jpetso into branch 'master'. daemon: Limit KAuth backlighthelper calls to only one at a time KAuth invocations are slower than users can move a slider. So we get many brightness change requests, and KAuth can't keep up. As a result, high-frequency brightness change requests for BacklightBrightness (i.e. laptop displays) would feel very laggy and get worse over time if not given a break to catch up. This commit fixes the lagginess. Conceptually it's easy: Don't start a new KAuth helper job until the current one has reported a result. At that point, check if a different brightness level was requested in the meantime, and start another job only then. BacklightHelper can deal fine with interrupting a running animation and starting a new one from the current brightness level. Hence, there is no need to wait until the end of the brightness animation to start a new KAuth job - this would only increase latency. Starting the new job right after receiving a result is perfectly fine. In the same go, we make two related improvements. Firstly, the udev-powered brightness observer will not only ignore events when the animation timer is running, but also in between setBrightness() and the KAuth result handler where the timer is started. Secondly, the condition involving m_brightnessAnimationThreshold is changed to something sensible. It makes no sense to simply check the current brightness against a constant number (100) to determine whether the brightness change should be animated. What I think this meant to do is to ensure that there are enough brightness steps available to animate. So following this commit, we will now animate when the difference between the current and the requested brightness is 100 or more integer steps. Taken together, laptop brightness slider UX now seems decent. Related: bug 470106 M +38 -13 daemon/controllers/backlightbrightness.cpp M +3-0daemon/controllers/backlightbrightness.h https://invent.kde.org/plasma/powerdevil/-/commit/033825d2217ec3c91af5af1fc0a6fbb66f91fdbd -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 470106] brightness-control slider shows different percentage than OSD
https://bugs.kde.org/show_bug.cgi?id=470106 --- Comment #6 from Jakob Petsovits --- Git commit 033825d2217ec3c91af5af1fc0a6fbb66f91fdbd by Jakob Petsovits. Committed on 22/06/2024 at 11:46. Pushed by jpetso into branch 'master'. daemon: Limit KAuth backlighthelper calls to only one at a time KAuth invocations are slower than users can move a slider. So we get many brightness change requests, and KAuth can't keep up. As a result, high-frequency brightness change requests for BacklightBrightness (i.e. laptop displays) would feel very laggy and get worse over time if not given a break to catch up. This commit fixes the lagginess. Conceptually it's easy: Don't start a new KAuth helper job until the current one has reported a result. At that point, check if a different brightness level was requested in the meantime, and start another job only then. BacklightHelper can deal fine with interrupting a running animation and starting a new one from the current brightness level. Hence, there is no need to wait until the end of the brightness animation to start a new KAuth job - this would only increase latency. Starting the new job right after receiving a result is perfectly fine. In the same go, we make two related improvements. Firstly, the udev-powered brightness observer will not only ignore events when the animation timer is running, but also in between setBrightness() and the KAuth result handler where the timer is started. Secondly, the condition involving m_brightnessAnimationThreshold is changed to something sensible. It makes no sense to simply check the current brightness against a constant number (100) to determine whether the brightness change should be animated. What I think this meant to do is to ensure that there are enough brightness steps available to animate. So following this commit, we will now animate when the difference between the current and the requested brightness is 100 or more integer steps. Taken together, laptop brightness slider UX now seems decent. Related: bug 481003 M +38 -13 daemon/controllers/backlightbrightness.cpp M +3-0daemon/controllers/backlightbrightness.h https://invent.kde.org/plasma/powerdevil/-/commit/033825d2217ec3c91af5af1fc0a6fbb66f91fdbd -- You are receiving this mail because: You are watching all bug changes.
[kompare] [Bug 472088] Unable to scroll horizontally
https://bugs.kde.org/show_bug.cgi?id=472088 --- Comment #2 from Bug Janitor Service --- A possibly relevant merge request was started @ https://invent.kde.org/sdk/kompare/-/merge_requests/27 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 488149] Doesn't always paste the latest copy
https://bugs.kde.org/show_bug.cgi?id=488149 --- Comment #3 from Marcos Dione --- I just tried. To start with, the UI is quite different, but that must be related to the system wide changes I made (style,. colors, etc). Behaviorly, the applet seems to work fine, but as I mentioned, sometimes it feels like it's time related. The only thing I can tell is that, even if pasting with the keyboard works fine, when I invoke the Items Menu, the topmost item IS the text I just C&P'ed, but it's not 'selected' (no checked checkbox at it left). Is this as intended? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 488149] Doesn't always paste the latest copy
https://bugs.kde.org/show_bug.cgi?id=488149 --- Comment #4 from Marcos Dione --- BTW, could you tell me where the config for the applet is? I would like to save a copy before playing with the options. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 488915] Certain widgets break after reboot
https://bugs.kde.org/show_bug.cgi?id=488915 edwloef changed: What|Removed |Added CC||edwin.frank.loeffler@gmail. ||com --- Comment #1 from edwloef --- I have the same issue, on a Lenovo IdeaPad Pro 5i. It seems you can also make the widgets work again by running `plasmashell --replace` -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 340982] No way to change just the date format but not its actual translated text
https://bugs.kde.org/show_bug.cgi?id=340982 --- Comment #267 from Enrico Tagliavini --- (In reply to Anton from comment #266) > I'm not sure what the situation is but I have just installed kde-full on > Ubuntu 24.04 and it appears there is no way to not have the unbelievably > stupid American date format, almost 10 years after this bug was created. > > I must be missing something, and it must be possible. When you click on "Set > time format" it takes me to the "Region & Language" settings. There are no > US/North American values configured, only British English. The British do > not format their dates MM/DD/. So there is at least that bug. What QT > does is obviously irrelevant... I use American English as the system language, but I've set (via the KDE GUI, not from command line) the date format to be English Irish. This shows the dates in DD/MM/YY format and sets the environment variable LC_TIME=en_IE.UTF-8 . The Plasma digital clock shows the date of today as 22/06/2024. I hope this helps you. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 488915] Certain widgets break after reboot
https://bugs.kde.org/show_bug.cgi?id=488915 edwloef changed: What|Removed |Added Ever confirmed|0 |1 Status|REPORTED|CONFIRMED -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 488971] New: Option to disable the inactivity duration on Hide Cursor and only hide cursor when typing
https://bugs.kde.org/show_bug.cgi?id=488971 Bug ID: 488971 Summary: Option to disable the inactivity duration on Hide Cursor and only hide cursor when typing Classification: Plasma Product: kwin Version: 6.1.0 Platform: Other OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: compositing Assignee: kwin-bugs-n...@kde.org Reporter: brodierobertson54...@gmail.com Target Milestone: --- SUMMARY It would be nice with the Hide Cursor desktop effect to be able to disable the hide on inactivity and instead only hide when typing STEPS TO REPRODUCE 1. Enable the Hide Cursor desktop effect OBSERVED RESULT You can set the inactivity duration to 99 seconds but there is no way to disable it EXPECTED RESULT Disable the inactivity duration SOFTWARE/OS VERSIONS Linux/KDE Plasma: (available in About System) KDE Plasma Version: 6.1.0 KDE Frameworks Version: 6.3.0 Qt Version: 6.7.0 -- You are receiving this mail because: You are watching all bug changes.
[kcalc] [Bug 488972] New: Backspace not working
https://bugs.kde.org/show_bug.cgi?id=488972
Bug ID: 488972
Summary: Backspace not working
Classification: Applications
Product: kcalc
Version: 24.05.0
Platform: Fedora RPMs
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: general
Assignee: evan.te...@gmail.com
Reporter: dom.ji...@gmail.com
CC: gabriel.barrantes@outlook.com
Target Milestone: ---
***
If you're not sure this is actually a bug, instead post about it at
https://discuss.kde.org
If you're reporting a crash, attach a backtrace with debug symbols; see
https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports
***
SUMMARY
When typing something wrong in the formula you want to remove the last typed
number with backspace. This does remove the result but not the just typed
formula. You need to go with the mouse to the input field and use delete or
backspace there.
STEPS TO REPRODUCE
1. Type formula with keyboard
2. Press backspace
3. Last typed number is not removed
OBSERVED RESULT
Type 5+1+6{backspace} the 6 is not removed
EXPECTED RESULT
Type 5+1+6{backspace} the 6 is removed
SOFTWARE/OS VERSIONS
Windows:
macOS:
Linux/KDE Plasma: 6.1.0
(available in About System)
KDE Plasma Version:
KDE Frameworks Version: 6.3.0
Qt Version: 6.7.1
ADDITIONAL INFORMATION
Worked in older versions
--
You are receiving this mail because:
You are watching all bug changes.
[kcalc] [Bug 488973] New: .5 is not handled like before and give errors
https://bugs.kde.org/show_bug.cgi?id=488973 Bug ID: 488973 Summary: .5 is not handled like before and give errors Classification: Applications Product: kcalc Version: 24.05.0 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: evan.te...@gmail.com Reporter: dom.ji...@gmail.com CC: gabriel.barrantes@outlook.com Target Milestone: --- *** If you're not sure this is actually a bug, instead post about it at https://discuss.kde.org If you're reporting a crash, attach a backtrace with debug symbols; see https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** SUMMARY When typing your formula and you need to type 0.5 in it. Previously you can type .5 for it. But when typing now .5 it gives errors in the formula STEPS TO REPRODUCE 1. Type formula with keyboard and place .5 in it 2. Press enter 3. Gives UI.tvoerfout OBSERVED RESULT Type 1+.5 enter it gives UI.tvoerfout EXPECTED RESULT Type 1+.5 enter and the result should be 1.5 SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: 6.1.0 (available in About System) KDE Plasma Version: KDE Frameworks Version: 6.3.0 Qt Version: 6.7.1 ADDITIONAL INFORMATION Worked in older versions -- You are receiving this mail because: You are watching all bug changes.
[kompare] [Bug 463315] Allow to choose a diff file from welcome window / Rework welcome window
https://bugs.kde.org/show_bug.cgi?id=463315 --- Comment #2 from Bug Janitor Service --- A possibly relevant merge request was started @ https://invent.kde.org/sdk/kompare/-/merge_requests/28 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 488974] New: Combination of digital clock and media player causes freeze if panel is too thick
https://bugs.kde.org/show_bug.cgi?id=488974 Bug ID: 488974 Summary: Combination of digital clock and media player causes freeze if panel is too thick Classification: Plasma Product: plasmashell Version: 6.0.5 Platform: Manjaro OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Panel Assignee: plasma-b...@kde.org Reporter: kde-b...@nicoweio.33mail.com CC: niccolo.venera...@gmail.com Target Milestone: 1.0 Created attachment 170812 --> https://bugs.kde.org/attachment.cgi?id=170812&action=edit stderr of `plasmashell --replace` *** If you're not sure this is actually a bug, instead post about it at https://discuss.kde.org If you're reporting a crash, attach a backtrace with debug symbols; see https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** SUMMARY A specific combination of widgets within a particularly thick panel makes plasmashell freeze with 100% utilization of one CPU core. This started with a Manjaro update, but notably not the 5→6 one but the one to 6.0.5. STEPS TO REPRODUCE / OBSERVED RESULT 1. You might want to start fresh with a new user account. 2. Create another panel on the left-hand side. 3. Increase its width to 400 (not sure if those are pixels, so YMMV) 4. In the newly created panel, add the digital clock widget and the media player widget below. You might catch a freeze right then. If not, try the following: 5. Kill and restart plasmashell. (I like to do this quickly with Yakuake.) 6. Now you should definitely have a freeze. 7. You can reduce the thickness again by editing ~/.config/plasmashellrc and changing to something like thickness=200 and verify that plasmashell once again starts normally. SOFTWARE/OS VERSIONS KDE Plasma Version: 6.0.5 KDE Frameworks Version: 6.2.0 Qt Version: 6.7.1 Wayland (but seems to equally affect X11) ADDITIONAL INFORMATION HiDPI monitor, but scaling options left to default I wrote a bit more in a Manjaro forum thread: https://forum.manjaro.org/t/kde-plasmashell-freezes-loading-aborted-after-latest-stable-update-only-mouse-and-yakuake-working/163023/8 -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 488975] New: The jitter mouse will continue to get bigger.
https://bugs.kde.org/show_bug.cgi?id=488975 Bug ID: 488975 Summary: The jitter mouse will continue to get bigger. Classification: I don't know Product: kde Version: unspecified Platform: Arch Linux OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: gz18870140...@outlook.com Target Milestone: --- ARRAY(0x555c9397fa40) -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 470106] brightness-control slider shows different percentage than OSD
https://bugs.kde.org/show_bug.cgi?id=470106 --- Comment #7 from Bug Janitor Service --- A possibly relevant merge request was started @ https://invent.kde.org/plasma/powerdevil/-/merge_requests/383 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 481003] display brightness applet laggy and sometimes does not react to input
https://bugs.kde.org/show_bug.cgi?id=481003 Jakob Petsovits changed: What|Removed |Added Latest Commit|https://invent.kde.org/plas |https://invent.kde.org/plas |ma/powerdevil/-/commit/0338 |ma/powerdevil/-/commit/1017 |25d2217ec3c91af5af1fc0a6fbb |585fe5ef2263e02e6dc6f5227de |66f91fdbd |15fb3ba5d --- Comment #6 from Jakob Petsovits --- Git commit 1017585fe5ef2263e02e6dc6f5227de15fb3ba5d by Jakob Petsovits. Committed on 22/06/2024 at 12:16. Pushed by jpetso into branch 'Plasma/6.1'. daemon: Limit KAuth backlighthelper calls to only one at a time KAuth invocations are slower than users can move a slider. So we get many brightness change requests, and KAuth can't keep up. As a result, high-frequency brightness change requests for BacklightBrightness (i.e. laptop displays) would feel very laggy and get worse over time if not given a break to catch up. This commit fixes the lagginess. Conceptually it's easy: Don't start a new KAuth helper job until the current one has reported a result. At that point, check if a different brightness level was requested in the meantime, and start another job only then. BacklightHelper can deal fine with interrupting a running animation and starting a new one from the current brightness level. Hence, there is no need to wait until the end of the brightness animation to start a new KAuth job - this would only increase latency. Starting the new job right after receiving a result is perfectly fine. In the same go, we make two related improvements. Firstly, the udev-powered brightness observer will not only ignore events when the animation timer is running, but also in between setBrightness() and the KAuth result handler where the timer is started. Secondly, the condition involving m_brightnessAnimationThreshold is changed to something sensible. It makes no sense to simply check the current brightness against a constant number (100) to determine whether the brightness change should be animated. What I think this meant to do is to ensure that there are enough brightness steps available to animate. So following this commit, we will now animate when the difference between the current and the requested brightness is 100 or more integer steps. Taken together, laptop brightness slider UX now seems decent. Related: bug 470106 (cherry picked from commit 033825d2217ec3c91af5af1fc0a6fbb66f91fdbd) M +38 -13 daemon/controllers/backlightbrightness.cpp M +3-0daemon/controllers/backlightbrightness.h https://invent.kde.org/plasma/powerdevil/-/commit/1017585fe5ef2263e02e6dc6f5227de15fb3ba5d -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 470106] brightness-control slider shows different percentage than OSD
https://bugs.kde.org/show_bug.cgi?id=470106 --- Comment #8 from Jakob Petsovits --- Git commit 1017585fe5ef2263e02e6dc6f5227de15fb3ba5d by Jakob Petsovits. Committed on 22/06/2024 at 12:16. Pushed by jpetso into branch 'Plasma/6.1'. daemon: Limit KAuth backlighthelper calls to only one at a time KAuth invocations are slower than users can move a slider. So we get many brightness change requests, and KAuth can't keep up. As a result, high-frequency brightness change requests for BacklightBrightness (i.e. laptop displays) would feel very laggy and get worse over time if not given a break to catch up. This commit fixes the lagginess. Conceptually it's easy: Don't start a new KAuth helper job until the current one has reported a result. At that point, check if a different brightness level was requested in the meantime, and start another job only then. BacklightHelper can deal fine with interrupting a running animation and starting a new one from the current brightness level. Hence, there is no need to wait until the end of the brightness animation to start a new KAuth job - this would only increase latency. Starting the new job right after receiving a result is perfectly fine. In the same go, we make two related improvements. Firstly, the udev-powered brightness observer will not only ignore events when the animation timer is running, but also in between setBrightness() and the KAuth result handler where the timer is started. Secondly, the condition involving m_brightnessAnimationThreshold is changed to something sensible. It makes no sense to simply check the current brightness against a constant number (100) to determine whether the brightness change should be animated. What I think this meant to do is to ensure that there are enough brightness steps available to animate. So following this commit, we will now animate when the difference between the current and the requested brightness is 100 or more integer steps. Taken together, laptop brightness slider UX now seems decent. Related: bug 481003 (cherry picked from commit 033825d2217ec3c91af5af1fc0a6fbb66f91fdbd) M +38 -13 daemon/controllers/backlightbrightness.cpp M +3-0daemon/controllers/backlightbrightness.h https://invent.kde.org/plasma/powerdevil/-/commit/1017585fe5ef2263e02e6dc6f5227de15fb3ba5d -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 480693] Major memory leak when changing wallpapers
https://bugs.kde.org/show_bug.cgi?id=480693 --- Comment #15 from vinkmr <0vinoth0kum...@gmail.com> --- I upgraded to plasma 6.1 yesterday, so far the issue seems to be gone. -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 488975] The jitter mouse will continue to get bigger.
https://bugs.kde.org/show_bug.cgi?id=488975 --- Comment #1 from lc --- Because after updating the KDE 6.1.0 version, I found that the mouse turns on by default after setting the jitter, so I wanted to try this feature and fixed the size in the settings, but found that the mouse jitter keeps getting bigger. I don't know if anyone else has filed this bug, but I don't think it will affect anything. This passage is translated by a web page and may be incorrect. SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 6.1.0 KDE Frameworks Version: 6.3.0 Qt Version: 6.7.1 Kernel Version: 6.9.5-arch1-1 (64-bit) Graphics Platform: Wayland Processors: 16 × AMD Ryzen 7 7735H with Radeon Graphics Memory: 11.4 GiB of RAM Graphics Processor: AMD Radeon 680M Manufacturer: MECHREVO Product Name: WUJIE 14 System Version: Version 1.0 -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 488975] The jitter mouse will continue to get bigger.
https://bugs.kde.org/show_bug.cgi?id=488975 --- Comment #2 from lc --- Created attachment 170813 --> https://bugs.kde.org/attachment.cgi?id=170813&action=edit The size in the settings is fixed, but the mouse is still getting bigger. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kirigami] [Bug 488326] After update to KF 6.3, many systemsettings pages of Plasma 6.0.90 show an error message
https://bugs.kde.org/show_bug.cgi?id=488326 Antonio Rojas changed: What|Removed |Added CC||4wy78uwh@rokejulianlockhart ||.addy.io --- Comment #15 from Antonio Rojas --- *** Bug 488965 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 488965] Most KCMs are unreadable via System Settings, but readable via KCMShell6.
https://bugs.kde.org/show_bug.cgi?id=488965 Antonio Rojas changed: What|Removed |Added Resolution|--- |DUPLICATE Status|REPORTED|RESOLVED --- Comment #1 from Antonio Rojas --- *** This bug has been marked as a duplicate of bug 488326 *** -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 488969] After performing a clean install of Tuxedo OS 3, Dolphin keeps crashing when trying to open. Only the flatpak version works, but that is not as full featured.
https://bugs.kde.org/show_bug.cgi?id=488969 Antonio Rojas changed: What|Removed |Added Status|REPORTED|NEEDSINFO Resolution|--- |BACKTRACE --- Comment #1 from Antonio Rojas --- Crash reports require a backtrace to be actionable. -- You are receiving this mail because: You are watching all bug changes.
[kcalc] [Bug 488973] .5 is not handled like before and give errors
https://bugs.kde.org/show_bug.cgi?id=488973 Antonio Rojas changed: What|Removed |Added Resolution|--- |DUPLICATE Status|REPORTED|RESOLVED --- Comment #1 from Antonio Rojas --- *** This bug has been marked as a duplicate of bug 487659 *** -- You are receiving this mail because: You are watching all bug changes.
[kcalc] [Bug 487659] can't input decimals without the leading 0
https://bugs.kde.org/show_bug.cgi?id=487659 Antonio Rojas changed: What|Removed |Added CC||dom.ji...@gmail.com --- Comment #10 from Antonio Rojas --- *** Bug 488973 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 488860] Massive frame drops with intel iris xe graphics and triple buffering
https://bugs.kde.org/show_bug.cgi?id=488860 g...@marcais.net changed: What|Removed |Added CC||g...@marcais.net --- Comment #8 from g...@marcais.net --- I can confirm this as well. Animation is extremely choppy when going from one desktop to another. Windows are not updated for 1 second or so (very noticeable in Zoom calls). Log filled with this error: Jun 22 08:26:25 gus-cachyos kwin_wayland[967]: OpenGL vendor string: Intel Jun 22 08:26:25 gus-cachyos kwin_wayland[967]: OpenGL renderer string: Mesa Intel(R) Xe Graphics (TGL GT2) Jun 22 08:26:25 gus-cachyos kwin_wayland[967]: OpenGL version string: 4.6 (Core Profile) Mesa 24.1.2-arch1.2 Jun 22 08:26:25 gus-cachyos kwin_wayland[967]: OpenGL shading language version string: 4.60 Jun 22 08:26:25 gus-cachyos kwin_wayland[967]: Driver: Intel Jun 22 08:26:25 gus-cachyos kwin_wayland[967]: GPU class: Tiger Lake Jun 22 08:26:25 gus-cachyos kwin_wayland[967]: OpenGL version: 4.6 Jun 22 08:26:25 gus-cachyos kwin_wayland[967]: GLSL version: 4.60 Jun 22 08:26:25 gus-cachyos kwin_wayland[967]: Mesa version: 24.1.2 Jun 22 08:26:25 gus-cachyos kwin_wayland[967]: Requires strict binding: no Jun 22 08:26:25 gus-cachyos kwin_wayland[967]: Virtual Machine: no Jun 22 08:26:25 gus-cachyos kwin_wayland[967]: kwin_scene_opengl: 0x3: GL_INVALID_OPERATION in glDrawBuffers(unsupported buffer GL_BACK_LEFT) inux/KDE Plasma: CachyOS Linux KDE Plasma Version: 6.1.0 KDE Frameworks Version: 6.3.0 Qt Version: 6.7.1 -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 487005] When renaming in icon view, the cursor and the text is not centered but goes to the very left
https://bugs.kde.org/show_bug.cgi?id=487005 accou...@kricket.cc changed: What|Removed |Added CC||accou...@kricket.cc --- Comment #3 from accou...@kricket.cc --- SUMMARY This bug is causing me frustration as well, after updating my Manjaro system yesterday. The text is centered when I hit F2 to rename the file, but as soon as I paste in the new file name, the text jumps left, rather than staying centered. SCREEN RECORDING: Here is a screen recording example: https://ibb.co/ZNGjxFm SOFTWARE/OS VERSIONS Operating System: Manjaro Linux 24 KDE Plasma Version: 6.0.5 KDE Frameworks Version: 6.2.0 Qt Version: 6.7.1 Kernel Version: 6.6.32-1-MANJARO (64-bit) Graphics Platform: X11 Processors: 32 × 13th Gen Intel® Core™ i9-13900HX Memory: 31.1 GiB of RAM Graphics Processor: Mesa Intel® Graphics Manufacturer: LENOVO -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 479695] In icons view mode, file name moves left during rename
https://bugs.kde.org/show_bug.cgi?id=479695 L5Pro changed: What|Removed |Added CC||accou...@kricket.cc --- Comment #12 from L5Pro --- I have this problem too. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 488882] "Shake Cursor" can enlarge cursor multiple times
https://bugs.kde.org/show_bug.cgi?id=42 filip.kend...@gmail.com changed: What|Removed |Added CC||gz18870140...@outlook.com --- Comment #2 from filip.kend...@gmail.com --- *** Bug 488975 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 488975] The jitter mouse will continue to get bigger.
https://bugs.kde.org/show_bug.cgi?id=488975 filip.kend...@gmail.com changed: What|Removed |Added CC||filip.kend...@gmail.com Resolution|--- |DUPLICATE Status|REPORTED|RESOLVED --- Comment #3 from filip.kend...@gmail.com --- *** This bug has been marked as a duplicate of bug 42 *** -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 488976] New: Share dialogue on app details page shows nonsense
https://bugs.kde.org/show_bug.cgi?id=488976 Bug ID: 488976 Summary: Share dialogue on app details page shows nonsense Classification: Applications Product: Discover Version: 6.1.0 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: discover Assignee: plasma-b...@kde.org Reporter: gregorpla...@unity-mail.de CC: aleix...@kde.org Target Milestone: --- Created attachment 170814 --> https://bugs.kde.org/attachment.cgi?id=170814&action=edit Nonsense sharing popup SUMMARY The share popup on any app details page in Discover just shows five buttons, without any indication what they do STEPS TO REPRODUCE 1. Open Discover 2. Search an app and open its details page 3. Click the share button at the bottom OBSERVED RESULT See attached screenshot EXPECTED RESULT Showing options like "Generate QR Code", just like in Plasma 6.0 SOFTWARE/OS VERSIONS Operating System: Fedora Linux 40 KDE Plasma Version: 6.1.0 KDE Frameworks Version: 6.3.0 Qt Version: 6.7.1 Kernel Version: 6.9.5-200.fc40.x86_64 (64-bit) Graphics Platform: X11 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 488977] New: Deleted panel is stuck in edit mode when restored from notification
https://bugs.kde.org/show_bug.cgi?id=488977 Bug ID: 488977 Summary: Deleted panel is stuck in edit mode when restored from notification Classification: Plasma Product: plasmashell Version: 6.1.0 Platform: Arch Linux OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: Panel Assignee: plasma-b...@kde.org Reporter: rkolbas...@tutanota.com CC: niccolo.venera...@gmail.com Target Milestone: 1.0 SUMMARY Deleted panel, when restored by clicking "Undo" on "Panel Removed" notification, will get stuck in edit mode. STEPS TO REPRODUCE 1. Enter edit mode 2. Create a Default Panel 3. Delete new panel 4. On "Panel Removed" notification click "Undo" 5. Exit edit mode 6. Try to use panel OBSERVED RESULT Panel behaves as if it is in edit mode. Widgets can't be moved, but show context menus and overlays from edit mode. EXPECTED RESULT Panel behaves normally SOFTWARE/OS VERSIONS Linux/KDE Plasma: (available in About System) KDE Plasma Version: 6.1.0 KDE Frameworks Version: 6.3.0 Qt Version: 6.7.1 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 485927] Animations in KDE Plasma 6.0.4 seem to be capped at 60hz
https://bugs.kde.org/show_bug.cgi?id=485927 1...@mailbox.org changed: What|Removed |Added CC||1...@mailbox.org --- Comment #2 from 1...@mailbox.org --- Can still reproduce on 6.1. So far, I've found the overview, desktop grid, cube and new edit mode to be affected. With a 165hz monitor and a 60hz one right beside it and spamming the overview, it is very obviously running at 60hz. Even if I boot with only the 165hz one physically connected, the problem persists. I have verified with the 'Show FPS' effect that the desktop barely drops frames when activating any of these effects. Couple notes for the overview: - Switching to another workspace (clicking, arrow keys, shortcut) in the overview also runs at 60hz. In comparison, the 'slide' effect when switching virtual desktops outside the overview is significantly smoother. - When dragging a window here, the window moves at the correct framerate. The new edit mode is also interesting, because the animations for entering and exiting it are visibly choppy (seemingly below 60fps even), while the animation that plays when opening a panel configuration (desktop being pushed away to make space) is hilariously smooth in comparison. The animation for opening the 'Add widgets' sidebar for example also runs at the correct framerate. Regarding the scrolling, I've tested a couple applications that have smooth scrolling. Not scrolling at the correct framerate: - System Monitor/Info Center - Dolphin (the F3 sidebar sliding animations is also running at 60hz) - Okular Scrolling at the correct framerate (extra notes for these below): - System Monitor (process tables) - Discover - Emoji selector - Filelight (sidebar) - Clipboard applet (needs a plasmashell restart as well after applying below fixes) If I boot with a secondary 60hz monitor enabled, these applications also have the 60hz scrolling. If I turn that monitor off and then on again, they seem to be fixed until next reboot (this fix seems to persist even through logging out). If I boot only with the 165hz one connected, they are fine. Operating System: Fedora Linux 40 KDE Plasma Version: 6.1.0 KDE Frameworks Version: 6.3.0 Qt Version: 6.7.1 Kernel Version: 6.9.4-200.fc40.x86_64 (64-bit) Graphics Platform: Wayland Graphics Processor: AMD Radeon RX 7600 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 488978] New: Right click menu only closes when clicking on a search field
https://bugs.kde.org/show_bug.cgi?id=488978 Bug ID: 488978 Summary: Right click menu only closes when clicking on a search field Classification: Applications Product: systemsettings Version: 6.1.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: brodierobertson54...@gmail.com Target Milestone: --- Created attachment 170815 --> https://bugs.kde.org/attachment.cgi?id=170815&action=edit Right-click menu will never give you up, let you down, run around, and desert you SUMMARY If you open a right click menu on the search field it can only be closed by clicking on another search field, clicking anywhere else in the window will not close it. If you click on other menu options in the list of sections the right click menu appears on top of them STEPS TO REPRODUCE 1. Open a right click menu on the search field 2. Click elsewhere 3. It ain't no closen OBSERVED RESULT Right click menu only closes when clicking on another search field EXPECTED RESULT Right click menu not closing SOFTWARE/OS VERSIONS Linux/KDE Plasma: (available in About System) KDE Plasma Version: 6.1.0 KDE Frameworks Version: 6.3.0 Qt Version: 6.7.1 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 488977] Deleted panel is stuck in edit mode when restored from notification
https://bugs.kde.org/show_bug.cgi?id=488977 filip.kend...@gmail.com changed: What|Removed |Added Ever confirmed|0 |1 Status|REPORTED|CONFIRMED CC||filip.kend...@gmail.com --- Comment #1 from filip.kend...@gmail.com --- I can confirm this bug. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 488978] Right click menu only closes when clicking on a search field
https://bugs.kde.org/show_bug.cgi?id=488978 Oliver Beard changed: What|Removed |Added Ever confirmed|0 |1 Status|REPORTED|CONFIRMED CC||notm...@gmail.com, ||olib...@outlook.com Component|general |sidebarview --- Comment #1 from Oliver Beard --- Other uses of Kirigami's search fields, in KCMs or in other applications, work fine, so this is a unique issue with the sidebar. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kirigami] [Bug 488326] After update to KF 6.3, many systemsettings pages of Plasma 6.0.90 show an error message
https://bugs.kde.org/show_bug.cgi?id=488326 Adi Efendic changed: What|Removed |Added CC||efendic...@gmail.com --- Comment #16 from Adi Efendic --- Can confirm the same happens for me. What I did notice is that it usually happens if I visit any settings page after opening System Settings. After that, if I open a settings page directly from the Application launcher (without first opening System Settings) it goes away. System details: Operating System: Fedora Linux 40 KDE Plasma Version: 6.1.0 KDE Frameworks Version: 6.3.0 Qt Version: 6.7.1 Kernel Version: 6.9.5-200.fc40.x86_64 (64-bit) Graphics Platform: Wayland Processors: 12 × AMD Ryzen 5 5600 6-Core Processor Memory: 31.3 GiB of RAM Graphics Processor: AMD Radeon RX 6600 -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 488979] New: Disappearing files in Dolphin smb
https://bugs.kde.org/show_bug.cgi?id=488979 Bug ID: 488979 Summary: Disappearing files in Dolphin smb Classification: Applications Product: dolphin Version: 24.05.0 Platform: Other OS: Linux Status: REPORTED Severity: major Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: squi...@o2.pl CC: kfm-de...@kde.org Target Milestone: --- Created attachment 170816 --> https://bugs.kde.org/attachment.cgi?id=170816&action=edit Issue video When I open any directory on my NAS via Dolphin smb://... the files starts to disappear from the files list one by one when I hover mouse above any of the file in the list. SOFTWARE/OS VERSIONS System: KDE Neon User Edition KDE Plasma Version: 6.1.0 KDE Frameworks Version: 6.3.0 Qt Version: 6.7.0 -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 487005] When renaming in icon view, the cursor and the text is not centered but goes to the very left
https://bugs.kde.org/show_bug.cgi?id=487005 --- Comment #4 from mozo --- It's the same on Plasma 6.1. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 448866] [NVIDIA] Graphical glitches and unresponsive after waking from sleep
https://bugs.kde.org/show_bug.cgi?id=448866 tess changed: What|Removed |Added CC||tburger...@gmail.com --- Comment #28 from tess --- Still experiencing this on 555.52.04 with plasma 6.1 Operating System: Arch Linux KDE Plasma Version: 6.1.0 KDE Frameworks Version: 6.3.0 Qt Version: 6.7.1 Kernel Version: 6.9.5-zen1-1-zen (64-bit) Graphics Platform: Wayland Processors: 24 × AMD Ryzen 9 5900X 12-Core Processor Memory: 31.3 GiB of RAM Graphics Processor: NVIDIA GeForce RTX 3060 Ti/PCIe/SSE2 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 481003] display brightness applet laggy and sometimes does not react to input
https://bugs.kde.org/show_bug.cgi?id=481003 Jakob Petsovits changed: What|Removed |Added CC||jpe...@petsovits.com Version Fixed In||6.1.1 -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 481308] screen locker black with cursor on X11
https://bugs.kde.org/show_bug.cgi?id=481308 j...@raby.sh changed: What|Removed |Added CC||j...@raby.sh --- Comment #68 from j...@raby.sh --- (In reply to Gabriel Barros from comment #65) > backlight do turn off when screen locks. > > moving the mouse turn it on but only show mouse cursor. pressing ESC moves > back to screen off. pressing ESC again turns backlight with only mouse > cursor again. > > Sometimes moving to another tty and back shows the image, sometimes it does > not. (it seems that changing tty first thing and back, works. but if you > cycle ESC then it won't work. but reproduction is not 100%) > > unlocking by typing password blind or using fingerprint touch do resume > image fine on unlocked desktop. Did you ever find a solution for this? I've been having this issue for weeks (months?), I'm running a similar configuration: - Arch x86_64 - X11 - libplasma 6.1.0-1 (upgraded on a weekly basis for like 3 years) When locking the screen, it goes black. cursor is visible and movable but screen stays black. going to a tty and back makes the "unlock prompt" show up. blindly typing the password into the black screen unlocks it. However I just realized that if I choose another theme, either Breeze Twilight or Oxygen, it works as it should. Also, going back to the theme I use (Breeze dark), breaks it again. If I choose Breeze Twilight, then switch back to Breeze Dark, but do not select "Plasma Style" in the "Choose what to apply..." menu, the screenlocker works. I'm not sure how to investigate what is up with that, any pointer would be appreciated. It seems like any themes I used before upgrading to plasma 6 (breeze and breeze dark) exhibit the same broken behavior while locking the screen. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 488964] Add an animation for switching between Activities
https://bugs.kde.org/show_bug.cgi?id=488964 Zamundaaa changed: What|Removed |Added Status|REPORTED|CONFIRMED Summary|Slide animation broken |Add an animation for |since 6.1.0 when switching |switching between |activities |Activities Severity|normal |wishlist Ever confirmed|0 |1 CC||xaver.h...@gmail.com --- Comment #1 from Zamundaaa --- The slide animation was never supposed to play when switching between Activities... but we should definitely have *some* animation -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 486149] Option to set FreeSync (VRR) mode has disappeared
https://bugs.kde.org/show_bug.cgi?id=486149 --- Comment #23 from JLV --- (In reply to Mufeed Ali from comment #22) > After a good amount of time, I can confirm that making SDDM use Wayland did > in fact fix the issue for me and I haven't faced it since my last comment > here. I can confirm too. I followed the instructions and now I have access to VRR all of the time. I don't know if this changes will be included in the future by default installations. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 488971] Option to disable the inactivity duration on Hide Cursor and only hide cursor when typing
https://bugs.kde.org/show_bug.cgi?id=488971 Oliver Beard changed: What|Removed |Added CC||olib...@outlook.com Status|REPORTED|CONFIRMED Ever confirmed|0 |1 Assignee|kwin-bugs-n...@kde.org |olib...@outlook.com -- You are receiving this mail because: You are watching all bug changes.
