[kwin] [Bug 466454] New: Vulkan and OpenGL windows not being created properly with fraction scale factors
https://bugs.kde.org/show_bug.cgi?id=466454 Bug ID: 466454 Summary: Vulkan and OpenGL windows not being created properly with fraction scale factors Classification: Plasma Product: kwin Version: 5.27.1 Platform: openSUSE OS: Linux Status: REPORTED Severity: major Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: oldkentuckym...@gmail.com Target Milestone: --- Created attachment 156749 --> https://bugs.kde.org/attachment.cgi?id=156749=edit example image Trying to create a window of a given size(ex. 1280x720) results in being given a surface one exaclty 1 pixel too tall (1280x721). Happens only on wayland with amdgpu, on the radeon mesa opengl driver, and both RADV and lavapipe drivers, with fractional scaling factors such as 150%. Does not happen on kwin_x11 nor on wayland with integer scale factors. Was happening on plasma 5.26 before the new fractional scaling protocol merge. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 466336] Unable to load VPN configuration
https://bugs.kde.org/show_bug.cgi?id=466336 --- Comment #6 from el...@seznam.cz --- > Does "nmcli connection import type vpnc file /home/elman/Temp/syd-006.ovpn" > work? Same error: > nmcli connection import type openvpn file /home/elman/Temp/syd-006.ovpn Error: failed to import '/home/elman/Temp/syd-006.ovpn': configuration error: unsupported 3th argument vpn_gateway to “route” (line 18). -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 466453] Dolphin and Discover icons are all white in Latte Dock and Discover also all white in the new Welcome dialogue
https://bugs.kde.org/show_bug.cgi?id=466453 --- Comment #1 from DozyDolphin --- Created attachment 156748 --> https://bugs.kde.org/attachment.cgi?id=156748=edit How the Discover icon looks in the Welcome dialogue -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 466453] New: Dolphin and Discover icons are all white in Latte Dock and Discover also all white in the new Welcome dialogue
https://bugs.kde.org/show_bug.cgi?id=466453 Bug ID: 466453 Summary: Dolphin and Discover icons are all white in Latte Dock and Discover also all white in the new Welcome dialogue Classification: Plasma Product: Breeze Version: 5.27.1 Platform: Neon OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Icons Assignee: visual-des...@kde.org Reporter: anderslg...@gmail.com CC: kain...@gmail.com, m...@nueljl.in Target Milestone: --- Created attachment 156747 --> https://bugs.kde.org/attachment.cgi?id=156747=edit How the Dolphin Icon looks on my Latte Dock SUMMARY * If I open Dolphin or Discover so they are visible on my Latte Dock, the icons are all white. * I have only observed the problem with these two icons - The Discover icon will sometimes look normal until I hover over it - then it becomes all white - The Dolphin icon will sometimes look all white until I hover over - then I can see the normal icon. Most of the time it is all white however * None of the icons are all white in the Application Dashboard * The Discover icon displayed in the new welcome dialogue is also all white I have attached images. It started after upgrading to 5.27 and is still a problem in 5.27.1 STEPS TO REPRODUCE Not sure how to reproduce SOFTWARE/OS VERSIONS Linux/KDE Plasma: KDE neon 5.27 (available in About System) KDE Plasma Version: 5.27.1 KDE Frameworks Version: 5.103.0 Qt Version: 5.15.8 I'm using X11 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 466452] New: Ability to copy image to clipboard
https://bugs.kde.org/show_bug.cgi?id=466452 Bug ID: 466452 Summary: Ability to copy image to clipboard Classification: Applications Product: digikam Version: 7.9.0 Platform: Ubuntu OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: Preview-Image Assignee: digikam-bugs-n...@kde.org Reporter: avmaksi...@yandex.ru Target Milestone: --- SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** It is very needed possibility. Sometimes when I recognize faces and manage my albums I need to ask about it from my relatives and need to send the photo. So the usual way it would be by pressing Ctrl+C but it doesn't work. Even I open in pressing F4 I can't copy to clipboard (I mean the whole image). Please add this ability in Preview Image at least. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 466451] New: Chromium/Chrome with client-side decorations (CSD) lose tiling when header is clicked
https://bugs.kde.org/show_bug.cgi?id=466451
Bug ID: 466451
Summary: Chromium/Chrome with client-side decorations (CSD)
lose tiling when header is clicked
Classification: Plasma
Product: kwin
Version: 5.27.1
Platform: Archlinux
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: Custom Tiling
Assignee: kwin-bugs-n...@kde.org
Reporter: breakingsp...@gmail.com
CC: notm...@gmail.com
Target Milestone: ---
Created attachment 156746
--> https://bugs.kde.org/attachment.cgi?id=156746=edit
readds "if (interactiveMoveResizeGravity() != Gravity::None)"
SUMMARY
When Chromium windows with client-side decorations are when snapped to a tile,
focusing the browser window by single-clicking on the tab header will cause the
window to lose it's tiling and return to it's previous size.
This occurs with both the new Shift+drag Custom Tiling, and legacy Quick Tiling
(after the commit where the new tiling was introduced). Tiling functions
normally with client-side decorations off, but this is less than ideal.
So far I can only identify Chromium+Chrome as affected, Firefox behaves like
normal with similar client-side decorations to Chromium. Of course, Chromium's
decorations are outside of Kwin scope, but I may have found a fix, below.
STEPS TO REPRODUCE
1. Open Chromium with "Use system title bar and borders" disabled, note the
window size before snapping.
2. Snap the window to a tile using either the new Shift modifier, or the old
quick corners/keys.
3. Click the blank space in the title bar once, the window will lose it's
snapping and return to original size.
OBSERVED RESULT
Window leaves tile and jumps back to original size, keeps position
EXPECTED RESULT
Window should focus/activate and remain static in the tile unless dragged or
double-clicked (maximize)
SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Arch / Plasma 5.27.1 (and master)
ADDITIONAL INFORMATION
The issue was introduced when the new Custom Tiling system was integrated, I
found this particular block affects the windows in question:
https://invent.kde.org/plasma/kwin/-/commit/e4507861f7b5ba563ae7cd5ce036a42a09f9edf8?page=2#4901cf4a1e41ceabcf8333e2929683619d4f0698_1664_1663
Adding the extra if check back in seems to resolve the issue for me, the
Chromium windows behave as expected and stay snapped to the new and old tiles
when focusing.
if (m_tile && !m_tile->supportsResizeGravity(interactiveMoveResizeGravity())) {
if (interactiveMoveResizeGravity() != Gravity::None) {
setQuickTileMode(QuickTileFlag::None);
}
}
Attached the patch i'm testing with. I'm still tinkering so I can understand
the particulars and find out if there are adverse effects.
--
You are receiving this mail because:
You are watching all bug changes.
[frameworks-knotifications] [Bug 452627] The notification system can become corrupted - notifications fail to update
https://bugs.kde.org/show_bug.cgi?id=452627 Michael Hamilton changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED --- Comment #4 from Michael Hamilton --- This could be closed as fixed. The notification system has been working well since the later part of 2022, I presume improvements unrelated to this bug report have resolved the issue. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 459543] Feature request: Zoom to width
https://bugs.kde.org/show_bug.cgi?id=459543 Andrei changed: What|Removed |Added CC||avmaksi...@yandex.ru --- Comment #3 from Andrei --- Hello! If it would be fit only by width the some parts of image will be not shown. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 466438] Some of Krita Layer and Brush Effect are not working properly Like Lumminosity, Multiply, Linear Bun, and some other
https://bugs.kde.org/show_bug.cgi?id=466438 Brandon changed: What|Removed |Added Keywords||accessibility -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 466450] In System Settings' Window Rules page, window property dialog jitters when scrolling with scroll bar
https://bugs.kde.org/show_bug.cgi?id=466450 Rocket Aaron changed: What|Removed |Added CC||i...@rocka.me -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 466450] New: In System Settings' Window Rules page, window property dialog jitters when scrolling with scroll bar
https://bugs.kde.org/show_bug.cgi?id=466450 Bug ID: 466450 Summary: In System Settings' Window Rules page, window property dialog jitters when scrolling with scroll bar Classification: Applications Product: systemsettings Version: 5.27.1 Platform: Archlinux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: kcm_kwinrules Assignee: kwin-bugs-n...@kde.org Reporter: i...@rocka.me CC: isma...@gmail.com, plasma-b...@kde.org Target Milestone: --- Created attachment 156745 --> https://bugs.kde.org/attachment.cgi?id=156745=edit scroll bar and dialog content jitters up and down SUMMARY In "System Settings - Workspace - Window Management - Window Rules" page, when editing or creating rules, "Add property to the rule" dialog would jitter when scrolling using mouse to drag the scroll bar. STEPS TO REPRODUCE 1. Open "System Settings - Workspace - Window Management - Window Rules", and click "Add New..." button 2. In the newly opened "New window settings" page, click "Add Property..." button 3. Try scrolling down the "Add property to the rule" dialog using mouse to drag the scroll bar OBSERVED RESULT The scroll bar and dialog content jitters up and down EXPECTED RESULT The scroll bar and dialog content scrolls down smoothly SOFTWARE/OS VERSIONS Linux/KDE Plasma: KDE Plasma Version: 5.27.1 KDE Frameworks Version: 5.103.0 Qt Version: 5.15.8+kde+r181-1 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 466326] Multi-screen crash when unplugging/plugging in multiple monitors or enabling/disabling displays in settings
https://bugs.kde.org/show_bug.cgi?id=466326 --- Comment #4 from Brian Tipton --- Created attachment 156744 --> https://bugs.kde.org/attachment.cgi?id=156744=edit Diagnosis Info -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 466326] Multi-screen crash when unplugging/plugging in multiple monitors or enabling/disabling displays in settings
https://bugs.kde.org/show_bug.cgi?id=466326 --- Comment #3 from Brian Tipton --- Created attachment 156743 --> https://bugs.kde.org/attachment.cgi?id=156743=edit GDB -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 466326] Multi-screen crash when unplugging/plugging in multiple monitors or enabling/disabling displays in settings
https://bugs.kde.org/show_bug.cgi?id=466326 --- Comment #2 from Brian Tipton --- (In reply to Nate Graham from comment #1) > If something crashed, we need a backtrace of it so we can figure out what's > going on. See > https://community.kde.org/Guidelines_and_HOWTOs/Debugging/ > How_to_create_useful_crash_reports. > > Can you please attach one? Thanks! Yea sorry, I meant to post one the other night. Another couple thing to note, I have 2 GPU's attached to my machine with VFIO setup. Whenever I swap the monitors via KVM I am swapping to the output of the 2nd GPU. The swapping seems to be okay when removing monitors, but when I am attempting to reconnect the monitors via KVM the system gets very laggy on the running monitor (mouse/windows visually jumping around). Then when I go inside the system settings to disable/enable to attempt to get them to work it crashes. Also tested on 5.27.1 with same results. I will also attach diagnosis info. Thanks -- You are receiving this mail because: You are watching all bug changes.
[skrooge] [Bug 437933] Confirm before dismissing changed operation
https://bugs.kde.org/show_bug.cgi?id=437933 pa...@web.de changed: What|Removed |Added Status|NEEDSINFO |REPORTED Resolution|WAITINGFORINFO |--- --- Comment #3 from pa...@web.de --- (In reply to Stephane MANKOWSKI from comment #1) > Hi, > > Just some questions to well understand your scenario and propose the better > solution. > > In step 3, why did you click on another operation ? What is your intention ? > > If you want do modify this operation, this is normal to update the form with > the new selection. Yes, correct, step 3 is an error on my side. Typically in this situation I was sidetracked by some other issue and forget, but sometimes it's just that the click did not work for whatever reason (window wasn't active, cursor didn't match button position, clicking was not recognized, ...) I think it's pretty much the same as when you write a text in a text editor and (most often accidentally) click on close before saving. Then it's usual to have the text editor let the user confirm, that their text (modified state) would be deleted by presenting some options to go forward. I think it's always the same pattern with unsaved modified state, be it an HTML form or in a configuration dialog. Similarly when modifying an entry and forgetting to either create a new entry or overwrite the existing on, the user would again lose modified state and therefore Skrooge should be presenting some options to go forward (ideally disactivable for the future). I think this makes sense from a user friendliness point of view and would have saved some frustration on my side (like an e-mail you have to rewrite because it gone lost somehow during editing – it's not the sheer amount of additional work which is frustrating, but doing the very same thing again). -- You are receiving this mail because: You are watching all bug changes.
[skrooge] [Bug 454965] Stats plugin should use XDG_STATE_HOME rather than the hardcoded .skrooge path to store files
https://bugs.kde.org/show_bug.cgi?id=454965 --- Comment #2 from cont...@etage.io --- Hi, yes, that is exactly what I mean. QDir::homePath() % "/." % appname % is equivalent to $HOME/skrooge. Rather CacheLocation should be used (see https://doc.qt.io/qt-5/qstandardpaths.html; $XDG_STATE_HOME doesn't seem to be added yet). -- You are receiving this mail because: You are watching all bug changes.
[Tokodon] [Bug 466440] Duplicate copies of the same account in the "Switch User" menu
https://bugs.kde.org/show_bug.cgi?id=466440 --- Comment #2 from Spry --- (In reply to Joshua Goins from comment #1) > I can confirm this happens, and I'm building in stronger safeguards in the > next release to prevent this from happening. Can you confirm that the > accounts show up normally after logging back in? Yes, they are normal again after logging back in. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 457726] kscreen_backend_launcher block entering Screen Energy saving
https://bugs.kde.org/show_bug.cgi?id=457726 --- Comment #4 from Josh Medeiros --- I have a similar issue, but it happens after the monitors are off for a couple hours. One monitor wakes, the backlight comes on, the OSD says "DisplayPort: No Input", and the monitor goes back to sleep. Then the other wakes and does the exact same thing, then back to the first in an infinite loop. This continues until I wake the system. On logs I see massive spam from kscreen_backend_launcher every 5 seconds, which is the same interval as the monitors waking. When I wake screen kscreenlocker is broken - the background is there but no greeter, impossible to log in. I can open a TTY but loginctl unlock-session does nothing, nor does killing kscreenlocker. The best solution I've found is to kill sddm, but this starts a new session I lose everything I had open. Probably a second bug, but it happens 100% of the time after kscreen_backend_launcher starts waking the screens, so likely related in some way. I can also reproduce windows moving by running xset dpms force off and then waking monitors immediately after they power off. For me everything goes to my second screen but I think this is just GPU port order (plasma defaults to my second screen on a fresh install too). Software: Kubuntu 22.04.2 Kernel 5.15.0-60 Plasma 5.24.7 Hardware: i5 3570k Radeon RX 6600 (non-XT) Monitors are both Asus PB278Q on displayport at 1440p Second monitor in portrait orientation -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 466172] SIGTRAP crash whenever getaddrinfo call is issued by valgrind
https://bugs.kde.org/show_bug.cgi?id=466172 b_be...@yahoo.com changed: What|Removed |Added CC||b_be...@yahoo.com -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 466436] S22 DNG thumbnails are not well oriented
https://bugs.kde.org/show_bug.cgi?id=466436 caulier.gil...@gmail.com changed: What|Removed |Added CC||caulier.gil...@gmail.com Component|Albums-MainView |Albums-IconView --- Comment #1 from caulier.gil...@gmail.com --- This must be fixed in next 7.10 release. Please test with Linux AppImage bundle per-release available here : https://files.kde.org/digikam/ Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 466449] New: Discover crashes when manually installing RPM.
https://bugs.kde.org/show_bug.cgi?id=466449 Bug ID: 466449 Summary: Discover crashes when manually installing RPM. Classification: Applications Product: Discover Version: 5.27.0 Platform: unspecified OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: discover Assignee: plasma-b...@kde.org Reporter: erik.nie...@outlook.com CC: aleix...@kde.org Target Milestone: --- Application: plasma-discover (5.27.0) Qt Version: 5.15.2 Frameworks Version: 5.103.0 Operating System: Linux 6.1.12-1271.native x86_64 Windowing System: X11 Distribution: Clear Linux OS DrKonqi: 5.27.0 [KCrashBackend] -- Information about the crash: When installing a third party RPM, like Google Chrome, Discover immediately crashes. The crash can be reproduced every time. -- Backtrace: Application: Discover (plasma-discover), signal: Segmentation fault [KCrash Handler] #6 doActivate () at kernel/qobject.cpp:3803 #7 0x55a62211c152 in ResultsStream::resourcesFound () at /builddir/build/BUILD/discover-5.27.0/clr-build/libdiscover/DiscoverCommon_autogen/3YJK5W5UP7/moc_AbstractResourcesBackend.cpp:159 #8 0x55a5f4fc7137 in operator() () at /builddir/build/BUILD/discover-5.27.0/libdiscover/backends/FlatpakBackend/FlatpakBackend.cpp:1586 #9 call () at /usr/include/qt5/QtCore/qobjectdefs_impl.h:146 #10 call, void> () at /usr/include/qt5/QtCore/qobjectdefs_impl.h:256 #11 impl () at /usr/include/qt5/QtCore/qobjectdefs_impl.h:443 #12 0x55a61f7eda85 in QObject::event () at kernel/qobject.cpp:1347 #13 0x55a621640543 in QApplicationPrivate::notify_helper () at kernel/qapplication.cpp:3637 #14 0x55a61f7c2778 in QCoreApplication::notifyInternal2 () at kernel/qcoreapplication.cpp:1064 #15 0x55a61f7c2a06 in QCoreApplication::sendEvent () at kernel/qcoreapplication.cpp:1462 #16 QCoreApplicationPrivate::sendPostedEvents () at kernel/qcoreapplication.cpp:1821 #17 0x55a61f81ad40 in QCoreApplication::sendPostedEvents () at kernel/qcoreapplication.cpp:1680 #18 postEventSourceDispatch () at kernel/qeventdispatcher_glib.cpp:277 #19 0x55a61ebdc141 in g_main_dispatch () at ../glib/gmain.c:3454 #20 g_main_context_dispatch () at ../glib/gmain.c:4172 #21 0x55a61ec6955b in g_main_context_iterate.constprop.0 () at ../glib/gmain.c:4248 #22 0x55a61ebda0d5 in g_main_context_iteration () at ../glib/gmain.c:4313 #23 0x55a61f819bfe in QEventDispatcherGlib::processEvents () at kernel/qeventdispatcher_glib.cpp:423 #24 0x55a61f7bfda6 in QEventLoop::processEvents () at kernel/qeventloop.cpp:139 #25 QEventLoop::exec () at kernel/qeventloop.cpp:232 #26 0x55a61f7c2f83 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1375 #27 0x55a6222c2278 in main () at /builddir/build/BUILD/discover-5.27.0/discover/main.cpp:224 [Inferior 1 (process 11767) detached] Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 457726] kscreen_backend_launcher block entering Screen Energy saving
https://bugs.kde.org/show_bug.cgi?id=457726 Josh Medeiros changed: What|Removed |Added CC||josh.a.medei...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 310123] Make it possible to enable/disable all preview plugins
https://bugs.kde.org/show_bug.cgi?id=310123 BL changed: What|Removed |Added CC||baby-l...@earthling.net --- Comment #2 from BL --- Can confirm that the 'feature wish' is not yet present on my Dolphin 21.12.3. My list contains 20 items. Operating System: Kubuntu 22.04, KDE Plasma Version: 5.24.7, KDE Frameworks Version: 5.92.0, Qt Version: 5.15.3 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 466448] New: Xwayland - Legacy X11 App Support does not forward mouse button events to X11 apps
https://bugs.kde.org/show_bug.cgi?id=466448 Bug ID: 466448 Summary: Xwayland - Legacy X11 App Support does not forward mouse button events to X11 apps Classification: Plasma Product: kwin Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: toadk...@toadking.com Target Milestone: --- SUMMARY The new "Legacy X11 App Support" feature works by forwarding keyboard keys to X11 apps, but it does not work for mouse buttons. STEPS TO REPRODUCE 1. Open an X11 app that you can bind mouse buttons with (I'm using Discord as an example) 2. Bind an action (ex. Push-to-talk) to that mouse button 3. Focus a native Wayland app and push the bound mouse button OBSERVED RESULT Push-to-talk does not work EXPECTED RESULT Push-to-talk works SOFTWARE/OS VERSIONS Linux: 6.1.12-arch1-1 (64-bit) KDE Plasma Version: 5.27.1 KDE Frameworks Version: 5.103.0 Qt Version: 5.15.8 ADDITIONAL INFORMATION Joystick button events also don't get passed to X11 apps but I'm not sure if that's something that should be handled here as well. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 358231] desktop locks up when moving lots of files
https://bugs.kde.org/show_bug.cgi?id=358231 Evgeny changed: What|Removed |Added Ever confirmed|1 |0 Status|NEEDSINFO |REPORTED Resolution|WAITINGFORINFO |--- --- Comment #43 from Evgeny --- I can't confirm when dragging a directory with lots of files (740 pictures) from dolphin to desktop, BUT can confirm when dragging a single big file (1.7 GB) from dolphin to desktop. Plasmashell freezes for about 10 seconds, then context menu appears. File is on HDD, system & desktop on NVME SSD. Just like in the attached video by Zhora Zmeikin https://bugs.kde.org/attachment.cgi?id=151631 dolphin/lunar,now 4:22.12.2-0ubuntu1 amd64 Operating System: Kubuntu 23.04 KDE Plasma Version: 5.27.0 (there are some 5.26.5 and 5.26.90 packages) KDE Frameworks Version: 5.103.0 (there are some 5.102 and even 5.101 packages, Kubuntu Lunar is a mess) Qt Version: 5.15.8 Kernel Version: 5.19.0-21-generic (64-bit) Graphics Platform: X11 Processors: 16 × AMD Ryzen 7 5800X 8-Core Processor Memory: 31.3 ГиБ of RAM Graphics Processor: AMD Radeon RX 590 Series Manufacturer: ASUS -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 466447] In plasma wayland session, Spectacle's Rectangular Region Selection magnifier zooms in wrong position when display scaling is enabled
https://bugs.kde.org/show_bug.cgi?id=466447 Rocket Aaron changed: What|Removed |Added CC||i...@rocka.me -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 466447] New: In plasma wayland session, Spectacle's Rectangular Region Selection magnifier zooms in wrong position when display scaling is enabled
https://bugs.kde.org/show_bug.cgi?id=466447 Bug ID: 466447 Summary: In plasma wayland session, Spectacle's Rectangular Region Selection magnifier zooms in wrong position when display scaling is enabled Classification: Applications Product: Spectacle Version: 22.12.2 Platform: Archlinux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: General Assignee: m...@baloneygeek.com Reporter: i...@rocka.me CC: k...@david-redondo.de Target Milestone: --- Created attachment 156742 --> https://bugs.kde.org/attachment.cgi?id=156742=edit The magnifier zooms in wrong position, likely 50% of the actual coordinate SUMMARY In plasma wayland session, Spectacle's Rectangular Region Selection magnifier zooms in wrong position when display scaling is enabled. In my case, I've set the display sacle to 200%. STEPS TO REPRODUCE 1. In plasma wayland session, enable display scaling via "System Settings - Display and Monitor - Display Configuration - Scale", set Scale to 200% 2. Open Spectacle, click "Configure...", in "General" section, make sure "Rectangular Region Selection - Show magnifier" is enabled 3. Click "Take a New Screenshot" with Area set to "Rectangular Region" 4. Click and drag to draw a selection rectangle OBSERVED RESULT The magnifier zooms in wrong position, likely 50% of the actual coordinate EXPECTED RESULT The magnifier zooms in under cursor SOFTWARE/OS VERSIONS Linux/KDE Plasma: KDE Plasma Version: 5.27.1 KDE Frameworks Version: 5.103.0 Qt Version: 5.15.8+kde+r181-1 ADDITIONAL INFORMATION The magnifier zooms in under cursor in Xorg -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 461023] Top-left hotcorner doesn't work anymore on X11 (works on Wayland)
https://bugs.kde.org/show_bug.cgi?id=461023 Bug Janitor Service changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |WORKSFORME --- Comment #15 from Bug Janitor Service --- This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 464849] Discover crashes when trying to view installed applications.
https://bugs.kde.org/show_bug.cgi?id=464849 Bug Janitor Service changed: What|Removed |Added Resolution|BACKTRACE |WORKSFORME Status|NEEDSINFO |RESOLVED --- Comment #3 from Bug Janitor Service --- This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 358231] desktop locks up when moving lots of files
https://bugs.kde.org/show_bug.cgi?id=358231 --- Comment #42 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 342999] Finance:Quote online source for South African Unit Trusts not available
https://bugs.kde.org/show_bug.cgi?id=342999 --- Comment #3 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 466424] System settings crash after applying global theme
https://bugs.kde.org/show_bug.cgi?id=466424 --- Comment #1 from andrew.lou...@gmail.com --- I replicated it! I more or less randomly selected from the "Global Theme" presets selecting "Apply" and after doing this a few times, switching back to "VGUI2 Classic" caused another crash -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 466446] New: Day is repeated in the tool tip when "Show seconds: Only in the tooltip" is enabled
https://bugs.kde.org/show_bug.cgi?id=466446 Bug ID: 466446 Summary: Day is repeated in the tool tip when "Show seconds: Only in the tooltip" is enabled Classification: Plasma Product: plasmashell Version: master Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Digital Clock Assignee: plasma-b...@kde.org Reporter: guimarcalsi...@gmail.com Target Milestone: 1.0 Created attachment 156741 --> https://bugs.kde.org/attachment.cgi?id=156741=edit Day is repeated multiple times when the seconds are shown on the tooltip. The letter e is also added in front of it. SUMMARY I'm seeing the day being repeated multiple times on the tooltip when "Show seconds: Only in the tooltip" is enabled, with the addition of "e" in front of it. This is on Neon Unstable. Check the attached screenshot. Important: The system was originally in Brazilian Portuguese, then I changed it to American English, but the dates are still shown in Portuguese for some reason. I went to the Region and Language KCM and changed the date format to the American one, but even after a restart, it still shows the name in Portuguese. If this bug cannot be reproduced in normal conditions, this could be the reason. Try changing your date format and restarting to see if the bug can be reproduced. This was possibly caused by https://invent.kde.org/plasma/plasma-workspace/-/merge_requests/2232 STEPS TO REPRODUCE 1. Hover over the tooltip 2. If you cannot reproduce, try changing the date locale and restarting OBSERVED RESULT The day is repeated multiple times and an "e" is added. For instance, today is Feb. 25th, and here it says "25 25e Fevereiro 25e 2023". EXPECTED RESULT The day should be shown as normal, the same way it is shown when the seconds in the tooltip are disabled. SOFTWARE/OS VERSIONS Operating System: KDE neon Unstable Edition KDE Plasma Version: 5.27.80 KDE Frameworks Version: 5.104.0 Qt Version: 5.15.8 Kernel Version: 5.19.0-32-generic (64-bit) Graphics Platform: Wayland Processors: 6 × Intel® Core™ i5-9400F CPU @ 2.90GHz Memory: 15,6 GiB of RAM Graphics Processor: AMD Radeon RX 570 Series -- You are receiving this mail because: You are watching all bug changes.
[Tokodon] [Bug 466439] Feature request: Provide custom emoji picker in toot composer
https://bugs.kde.org/show_bug.cgi?id=466439 Joshua Goins changed: What|Removed |Added Status|REPORTED|CONFIRMED Ever confirmed|0 |1 --- Comment #1 from Joshua Goins --- Yeah I plan on implementing something soon, similar to what NeoChat has (emoji picker and autocomplete) :) -- You are receiving this mail because: You are watching all bug changes.
[Tokodon] [Bug 466440] Duplicate copies of the same account in the "Switch User" menu
https://bugs.kde.org/show_bug.cgi?id=466440 Joshua Goins changed: What|Removed |Added Status|REPORTED|CONFIRMED Ever confirmed|0 |1 --- Comment #1 from Joshua Goins --- I can confirm this happens, and I'm building in stronger safeguards in the next release to prevent this from happening. Can you confirm that the accounts show up normally after logging back in? -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 466445] New: Dolphin crashes after close 2 tabs, and then switching folders
https://bugs.kde.org/show_bug.cgi?id=466445 Bug ID: 466445 Summary: Dolphin crashes after close 2 tabs, and then switching folders Classification: Applications Product: dolphin Version: 22.12.2 Platform: Archlinux OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: ethan1472...@gmail.com CC: kfm-de...@kde.org Target Milestone: --- Application: dolphin (22.12.2) Qt Version: 5.15.8 Frameworks Version: 5.103.0 Operating System: Linux 6.1.1-arch1-1 x86_64 Windowing System: X11 Distribution: "Arch Linux" DrKonqi: 5.27.1 [KCrashBackend] -- Information about the crash: I open Dolphin and it restores the last session (3 open tabs). I close 2 tabs and attempt to switch folders in the last tab, then it crashes. The crash can be reproduced every time. -- Backtrace: Application: Dolphin (dolphin), signal: Segmentation fault [KCrash Handler] #4 0x7fc17f313500 in typeinfo for QObject () from /usr/lib/libQt5Core.so.5 #5 0x7fc1812e261a in UpdateItemStatesThread::run() () from /usr/lib/libdolphinprivate.so.5 #6 0x7fc17eee432a in ?? () from /usr/lib/libQt5Core.so.5 #7 0x7fc17e89ebb5 in ?? () from /usr/lib/libc.so.6 #8 0x7fc17e920d90 in ?? () from /usr/lib/libc.so.6 Thread 4 (Thread 0x7fc168d6c6c0 (LWP 2194) "QThread"): #1 0x7fc17d2c5c2f in ?? () from /usr/lib/libglib-2.0.so.0 #2 0x7fc17d26d0e2 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #3 0x7fc17f0d8c8f in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/libQt5Core.so.5 #4 0x7fc17f0866ec in QEventLoop::exec(QFlags) () from /usr/lib/libQt5Core.so.5 #5 0x7fc17eee725f in QThread::exec() () from /usr/lib/libQt5Core.so.5 #6 0x7fc17eee432a in ?? () from /usr/lib/libQt5Core.so.5 #7 0x7fc17e89ebb5 in ?? () from /usr/lib/libc.so.6 #8 0x7fc17e920d90 in ?? () from /usr/lib/libc.so.6 Thread 3 (Thread 0x7fc170ac26c0 (LWP 2187) "dolphin"): #1 0x7fc17c357524 in ?? () from /usr/lib/libusbmuxd-2.0.so.6 #2 0x7fc17c3588a9 in ?? () from /usr/lib/libusbmuxd-2.0.so.6 #3 0x7fc17e89ebb5 in ?? () from /usr/lib/libc.so.6 #4 0x7fc17e920d90 in ?? () from /usr/lib/libc.so.6 Thread 2 (Thread 0x7fc1791fb6c0 (LWP 2181) "QDBusConnection"): #1 0x7fc17d2c5c2f in ?? () from /usr/lib/libglib-2.0.so.0 #2 0x7fc17d26d0e2 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #3 0x7fc17f0d8c6c in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/libQt5Core.so.5 #4 0x7fc17f0866ec in QEventLoop::exec(QFlags) () from /usr/lib/libQt5Core.so.5 #5 0x7fc17eee725f in QThread::exec() () from /usr/lib/libQt5Core.so.5 #6 0x7fc1803eccba in ?? () from /usr/lib/libQt5DBus.so.5 #7 0x7fc17eee432a in ?? () from /usr/lib/libQt5Core.so.5 #8 0x7fc17e89ebb5 in ?? () from /usr/lib/libc.so.6 #9 0x7fc17e920d90 in ?? () from /usr/lib/libc.so.6 Thread 1 (Thread 0x7fc179760ac0 (LWP 2177) "dolphin"): #1 0x7fc17eee056c in QSemaphore::acquire(int) () from /usr/lib/libQt5Core.so.5 #2 0x7fc17f0beb74 in ?? () from /usr/lib/libQt5Core.so.5 #3 0x7fc17f0bee14 in QObject::destroyed(QObject*) () from /usr/lib/libQt5Core.so.5 #4 0x7fc17f0b537c in QObject::~QObject() () from /usr/lib/libQt5Core.so.5 #5 0x7fc1810e9026 in ?? () from /usr/lib/libKF5Bookmarks.so.5 #6 0x7fc17e854445 in ?? () from /usr/lib/libc.so.6 #7 0x7fc17e8545b0 in exit () from /usr/lib/libc.so.6 #8 0x7fc1792ae069 in ?? () from /usr/lib/libQt5XcbQpa.so.5 #9 0x7fc1792dd8c8 in ?? () from /usr/lib/libQt5XcbQpa.so.5 #10 0x7fc17d26e82b in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0 #11 0x7fc17d2c5cc9 in ?? () from /usr/lib/libglib-2.0.so.0 #12 0x7fc17d26d0e2 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #13 0x7fc17f0d8c6c in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/libQt5Core.so.5 #14 0x7fc17f0866ec in QEventLoop::exec(QFlags) () from /usr/lib/libQt5Core.so.5 #15 0x7fc17f091219 in QCoreApplication::exec() () from /usr/lib/libQt5Core.so.5 #16 0x559838e90f53 in ?? () #17 0x7fc17e83c790 in ?? () from /usr/lib/libc.so.6 #18 0x7fc17e83c84a in __libc_start_main () from /usr/lib/libc.so.6 #19 0x559838e91695 in ?? () [Inferior 1 (process 2177) detached] Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 466444] New: Rectangle selection blanks out monitors.
https://bugs.kde.org/show_bug.cgi?id=466444 Bug ID: 466444 Summary: Rectangle selection blanks out monitors. Classification: Applications Product: Spectacle Version: 22.08.3 Platform: Ubuntu OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: General Assignee: m...@baloneygeek.com Reporter: frank.so...@gmail.com CC: k...@david-redondo.de Target Milestone: --- SUMMARY When in multi-monitor if scale set to 125% or if one monitor is scaled differntly than the others when using rectangular region all sceens will blank out. You can select an image you just cannot see what you are doing. If all set to any scale other than 125% it works as normal. *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** STEPS TO REPRODUCE 1. There are two ways to reproduce this bug either set all monitors to 125% scale or have one of three monitors set to a different scale than the rest of the monitors. 2. When you press the shorcut for rectange selection all thre monitors blank out. 3. This only happens at 125% or if all screens are not set to the same scale OBSERVED RESULT All screens blank out, you can select an image but you cannot see what you are doing. EXPECTED RESULT Normal screen grab selection operation SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Kubuntu 22.10 x86_64 / Plasma 5.27.0 (available in About System) KDE Plasma Version: Plasma 5.27.0 KDE Frameworks Version: 5.102.0 Qt Version: 5.15.6 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 463225] Akonadi server crashed when switching user
https://bugs.kde.org/show_bug.cgi?id=463225 --- Comment #4 from Steven Danderson --- Created attachment 156740 --> https://bugs.kde.org/attachment.cgi?id=156740=edit New crash information added by DrKonqi akonadiserver (5.22.2 (22.12.2)) using Qt 5.15.8 I was closing KPatience. The screen went totally black. The the desktop returned; first the wallpaper, then the taskbar. -- Backtrace (Reduced): #4 0x55a901bac29b in Akonadi::Server::AkonadiServer::connectionDisconnected() () #5 0x7f32594c8134 in QObject::event(QEvent*) () from /lib64/libQt5Core.so.5 #6 0x7f325949d4cb in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib64/libQt5Core.so.5 #7 0x7f32594a0854 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /lib64/libQt5Core.so.5 #8 0x7f32594eeb07 in postEventSourceDispatch(_GSource*, int (*)(void*), void*) () from /lib64/libQt5Core.so.5 -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 463225] Akonadi server crashed when switching user
https://bugs.kde.org/show_bug.cgi?id=463225 Steven Danderson changed: What|Removed |Added CC||danderson.ste...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 466443] New: The "Configure..." entry in the new Wide Gamut Color Selector docker's hamburger menu is not translatable
https://bugs.kde.org/show_bug.cgi?id=466443 Bug ID: 466443 Summary: The "Configure..." entry in the new Wide Gamut Color Selector docker's hamburger menu is not translatable Classification: Applications Product: krita Version: nightly build (please specify the git hash!) Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Dockers Assignee: krita-bugs-n...@kde.org Reporter: tyson...@tysontan.com Target Milestone: --- Created attachment 156739 --> https://bugs.kde.org/attachment.cgi?id=156739=edit Untranslatable "Configure..." entry in Wide Gamut Color Selector's hamburger menu The "Configure..." entry in the new Wide Gamut Color Selector docker's hamburger menu is not translatable. There is no string in krita.pot that matches this entry. It can be accessed by: Wide Gamut Color Selector docker -> Hamburger menu botton (top-right) -> Configure... -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 466442] New: Searching terms like "video", "audio", "game", "torrent", etc crashes discover.
https://bugs.kde.org/show_bug.cgi?id=466442 Bug ID: 466442 Summary: Searching terms like "video", "audio", "game", "torrent", etc crashes discover. Classification: Applications Product: Discover Version: 5.27.1 Platform: Other OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: discover Assignee: plasma-b...@kde.org Reporter: rosh206...@gmail.com CC: aleix...@kde.org Target Milestone: --- SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** Searching for certain application name doesn't crash discover. I tired by searching "firefox", "telegram", "ktorrent" and "video downloader" and these don't crash discover. And same goes for when searching some random words, searching random words doesn't crash discover either. So, I guess when using search terms that have many related applications, Discover crashes. STEPS TO REPRODUCE 1. Open discover. 2. Search using terms like "video", "audio", "game", "torrent", "download" etc 3. OBSERVED RESULT Discover closes, and I get a notification that says "Discover closed unexpectedly". EXPECTED RESULT Show apps related to those search terms. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Fedora Linux 37 (available in About System) KDE Plasma Version: 5.27.1 KDE Frameworks Version: 5.103.0 Qt Version: 5.15.8 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kmenuedit] [Bug 466242] kmenuedit crash
https://bugs.kde.org/show_bug.cgi?id=466242 Bug Janitor Service changed: What|Removed |Added Status|CONFIRMED |ASSIGNED --- Comment #2 from Bug Janitor Service --- A possibly relevant merge request was started @ https://invent.kde.org/plasma/kmenuedit/-/merge_requests/13 -- You are receiving this mail because: You are watching all bug changes.
[Tokodon] [Bug 466439] Feature request: Provide custom emoji picker in toot composer
https://bugs.kde.org/show_bug.cgi?id=466439 Bug Janitor Service changed: What|Removed |Added Severity|normal |wishlist -- You are receiving this mail because: You are watching all bug changes.
[Tokodon] [Bug 466441] New: No way to control notifications in Tokodon Flatpak version
https://bugs.kde.org/show_bug.cgi?id=466441 Bug ID: 466441 Summary: No way to control notifications in Tokodon Flatpak version Classification: Applications Product: Tokodon Version: 23.02.0 Platform: Flatpak OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: spry.bed7...@fastmail.com CC: c...@carlschwan.eu, j...@redstrate.com Target Milestone: --- SUMMARY In the Flatpak version there is currently no way to limit which Mastodon notifications generate system-level notifications (i.e. disabling the noise from faves, boosts, etc). In the non-Flatpak version, there is integration in the KDE System Settings -> Notifications -> Applications pane. In my view this specificity should either be moved to the in-application Settings or the Flatpak should be updated to integrate properly with the KDE System Settings. STEPS TO REPRODUCE 1. Install the Flatpak version of Tokodon. 2. Open System Settings. 3. Navigate to Notifications -> Applications. OBSERVED RESULT Tokodon is not in the application list. EXPECTED RESULT Tokodon is in the application list and allows users to edit granular notification settings. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Kubuntu 22.04 KDE Plasma Version: 5.24.7 KDE Frameworks Version: 5.92.0 Qt Version: 5.15.3 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 466269] Allow configuring the modifier key that must be held down to trigger Custom Tiling
https://bugs.kde.org/show_bug.cgi?id=466269 --- Comment #3 from a...@triptech.net --- Thanks Nate: not sure if the direction to add separate bug reports was directed at my original report, or Sidney's comment, or both? If you could clarify I'm happy to comply to help? >From my original, would the split be a/ default behaviour with alt-drag, then b/configurable modifier keys as a separate request? On a first read of Sidney's comment I thought it was tangential, but now I think that it is actually much the same as the (b) part of mine about configuring modifier keys. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kconfig] [Bug 460260] On a multi screen setup on Wayland, KDE app windows do not remember the size they had if the primary monitor is not the leftmost one.
https://bugs.kde.org/show_bug.cgi?id=460260 --- Comment #24 from Nate Graham --- Git commit 239bb9c4be1b49116a45e708135dec85b526966c by Nate Graham. Committed on 26/02/2023 at 01:02. Pushed by ngraham into branch 'kf5'. Don't include screen connector names in screen position/size data We have code that saves window positions (on X11) and sizes. It saves this data independently for single screens, different resolutions, and multi-screen arrangements. Identifying these in a way that's reliable has proved to be a challenge and multiple approaches have been taken over time. Currently we do the following: - For single screens, save data on a per-primary-screen-name and per-resolution basis - For multi-screen, save data on a per-screen-arrangement basis (with "screen arrangement" being defined as "an alphabetically-sorted string list of all connector names) Unfortunately, we know that under various circumstances connector names are volatile and change their text. For example: - When switching GPUs - When plugging a screen into a different type of port in the same GPU (e.g. HDMI -> DP or vice versa) - When using an external screen with a laptop and switching between the external screen being connected to a dock vs connected directly to the laptop - When switching between the X11 and wayland sessions - Due to kernel bugs like https://bugzilla.kernel.org/show_bug.cgi?id=206387 We've done our best to minimize the impact of this volatility by sorting the list alphabetically and no longer including the name of the "current" screen in the config file key. But the whole approach of using screen connectors in the first place is inherently flawed due to the above-mentioned volatility and cannot be made to work perfectly reliably. For this reason, as of Plasma 5.27, Plasma and KScreen no longer use screen names to try to identify specific screens. We can do the same here to significantly increase the robustness of the size and position restoration code. Instead of using screen names anywhere, now we do the following: * Single screen* Only save data on a per-resolution basis. Example config file contents: [MainWindow] 1920x1080 screen: Height=770 1920x1080 screen: Width=1122 1920x1080 screen: XPosition=588 1920x1080 screen: YPosition=216 *Multi-screen arrangements* Only save data on a "number of connected screens" basis. Example config file contents: [MainWindow] 2 screens: Height=770 2 screens: Width=1122 2 screens: XPosition=1865 2 screens: YPosition=1274 This commit implements that change in the most minimal and backportable-to-kf5 manner. Further refactoring to remove now-unnecessary code will be done later only for KF6, to minimize risk. Test Plan: X11, single screen: 1. Open Info Center 2. Move it to another location on screen and resize it 3. Close Info Center 4. Re-open Info Center -> position and size are remembered Wayland, single screen as well as 2 screens 1. Open Info Center 2. Move it to another location on screen and resize it 3. Close Info Center 4. Re-open Info Center -> size is remembered; position is not wnd it instead opens on the screen with the cursor on it according to the active window positioning mode, which is intentional at this point in time on Wayland X11, 2 screens: 1. Pin Info Center to Task Manager on Panel 1. Open Info Center using Task Manager, and, if it doesn't open on the screen with the Panel, move it there, close it, and open it again 2. Move it to the other screen that does not have the Panel on it 3. Close Info Center 4. Re-open Info Center from Task manager pinned icon -> position and size are remembered, including opening on the screen that doesn't have the Panel on it (cherry picked from commit 9d4418b3b9521514298c8aca1191617eb4be9985) M +11 -8src/gui/kwindowconfig.cpp https://invent.kde.org/frameworks/kconfig/commit/239bb9c4be1b49116a45e708135dec85b526966c -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kconfig] [Bug 460260] On a multi screen setup on Wayland, KDE app windows do not remember the size they had if the primary monitor is not the leftmost one.
https://bugs.kde.org/show_bug.cgi?id=460260 --- Comment #23 from Nate Graham --- Git commit 9d4418b3b9521514298c8aca1191617eb4be9985 by Nate Graham. Committed on 24/02/2023 at 16:10. Pushed by ngraham into branch 'master'. Don't include screen connector names in screen position/size data We have code that saves window positions (on X11) and sizes. It saves this data independently for single screens, different resolutions, and multi-screen arrangements. Identifying these in a way that's reliable has proved to be a challenge and multiple approaches have been taken over time. Currently we do the following: - For single screens, save data on a per-primary-screen-name and per-resolution basis - For multi-screen, save data on a per-screen-arrangement basis (with "screen arrangement" being defined as "an alphabetically-sorted string list of all connector names) Unfortunately, we know that under various circumstances connector names are volatile and change their text. For example: - When switching GPUs - When plugging a screen into a different type of port in the same GPU (e.g. HDMI -> DP or vice versa) - When using an external screen with a laptop and switching between the external screen being connected to a dock vs connected directly to the laptop - When switching between the X11 and wayland sessions - Due to kernel bugs like https://bugzilla.kernel.org/show_bug.cgi?id=206387 We've done our best to minimize the impact of this volatility by sorting the list alphabetically and no longer including the name of the "current" screen in the config file key. But the whole approach of using screen connectors in the first place is inherently flawed due to the above-mentioned volatility and cannot be made to work perfectly reliably. For this reason, as of Plasma 5.27, Plasma and KScreen no longer use screen names to try to identify specific screens. We can do the same here to significantly increase the robustness of the size and position restoration code. Instead of using screen names anywhere, now we do the following: * Single screen* Only save data on a per-resolution basis. Example config file contents: [MainWindow] 1920x1080 screen: Height=770 1920x1080 screen: Width=1122 1920x1080 screen: XPosition=588 1920x1080 screen: YPosition=216 *Multi-screen arrangements* Only save data on a "number of connected screens" basis. Example config file contents: [MainWindow] 2 screens: Height=770 2 screens: Width=1122 2 screens: XPosition=1865 2 screens: YPosition=1274 This commit implements that change in the most minimal and backportable-to-kf5 manner. Further refactoring to remove now-unnecessary code will be done later only for KF6, to minimize risk. Test Plan: X11, single screen: 1. Open Info Center 2. Move it to another location on screen and resize it 3. Close Info Center 4. Re-open Info Center -> position and size are remembered Wayland, single screen as well as 2 screens 1. Open Info Center 2. Move it to another location on screen and resize it 3. Close Info Center 4. Re-open Info Center -> size is remembered; position is not wnd it instead opens on the screen with the cursor on it according to the active window positioning mode, which is intentional at this point in time on Wayland X11, 2 screens: 1. Pin Info Center to Task Manager on Panel 1. Open Info Center using Task Manager, and, if it doesn't open on the screen with the Panel, move it there, close it, and open it again 2. Move it to the other screen that does not have the Panel on it 3. Close Info Center 4. Re-open Info Center from Task manager pinned icon -> position and size are remembered, including opening on the screen that doesn't have the Panel on it M +11 -8src/gui/kwindowconfig.cpp https://invent.kde.org/frameworks/kconfig/commit/9d4418b3b9521514298c8aca1191617eb4be9985 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 466430] Wayland does not remember my monitor arrangement and crashes when I try to move a window into the second monitor.
https://bugs.kde.org/show_bug.cgi?id=466430 Zamundaaa changed: What|Removed |Added Product|kwayland-integration|kwin Component|general |wayland-generic Assignee|plasma-b...@kde.org |kwin-bugs-n...@kde.org Version|unspecified |5.27.1 -- You are receiving this mail because: You are watching all bug changes.
[kwayland-integration] [Bug 466430] Wayland does not remember my monitor arrangement and crashes when I try to move a window into the second monitor.
https://bugs.kde.org/show_bug.cgi?id=466430 Zamundaaa changed: What|Removed |Added CC||xaver.h...@gmail.com --- Comment #1 from Zamundaaa --- Please attach a backtrace for kwin_wayland. Assuming you have gdb and debuginfod installed, you can do that with > coredumpctl debug kwin_wayland and then just execute "bt" in the gdb console -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 466428] Power Settings Not Applied/Enforced
https://bugs.kde.org/show_bug.cgi?id=466428 --- Comment #1 from Myc --- Updated to 5.27.1 and problem still exists. Operating System: Fedora Linux 37 KDE Plasma Version: 5.27.1 KDE Frameworks Version: 5.103.0 Qt Version: 5.15.8 Kernel Version: 6.1.13-200.fc37.x86_64 (64-bit) Graphics Platform: Wayland Processors: 4 × Intel® Core™ i5-6500T CPU @ 2.50GHz Memory: 31.2 GiB of RAM Graphics Processor: Mesa Intel® HD Graphics 530 Manufacturer: LENOVO Product Name: 10FM001UUS System Version: ThinkCentre M900 -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 466428] Power Settings Not Applied/Enforced
https://bugs.kde.org/show_bug.cgi?id=466428 Myc changed: What|Removed |Added Version|5.27.0 |5.27.1 -- You are receiving this mail because: You are watching all bug changes.
[Tokodon] [Bug 466440] New: Duplicate copies of the same account in the "Switch User" menu
https://bugs.kde.org/show_bug.cgi?id=466440 Bug ID: 466440 Summary: Duplicate copies of the same account in the "Switch User" menu Classification: Applications Product: Tokodon Version: 23.02.0 Platform: Flatpak OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: spry.bed7...@fastmail.com CC: c...@carlschwan.eu, j...@redstrate.com Target Milestone: --- SUMMARY A very strange display issue. After authorizing a Mastodon account, all seems well. However, if I close and re-open the app, and click "Switch User", there are now two versions of that account, and I'm able to switch back and forth between them. If I delete one of them, things seem okay until the next time I close and re-open the app. At that point ALL of my accounts are logged out, not just the one I clicked "Log Out" for. STEPS TO REPRODUCE 1. Authorize an account. 2. Close Tokodon. 3. Re-open Tokodon. 4. Check the Switch User menu. OBSERVED RESULT One or more accounts are duplicated in the Switch User menu. EXPECTED RESULT Each authorized account appears once. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Kubuntu 22.04 Operating System: Kubuntu 22.04 KDE Plasma Version: 5.24.7 KDE Frameworks Version: 5.92.0 Qt Version: 5.15.3 ADDITIONAL INFORMATION This affects all accounts, not just the first one added. -- You are receiving this mail because: You are watching all bug changes.
[Tokodon] [Bug 466439] New: Feature request: Provide custom emoji picker in toot composer
https://bugs.kde.org/show_bug.cgi?id=466439 Bug ID: 466439 Summary: Feature request: Provide custom emoji picker in toot composer Classification: Applications Product: Tokodon Version: 23.02.0 Platform: Flatpak OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: spry.bed7...@fastmail.com CC: c...@carlschwan.eu, j...@redstrate.com Target Milestone: --- SUMMARY Tokodon can display custom emoji from local and remote servers, but the post composer view has no way to browse or select the local server emoji. It would be good to add an emoji picker for the custom emoji, as it can be hard for users to remember the shortcodes. STEPS TO REPRODUCE 1. Hit the "+ Toot" button 2. Observe the options associated with the post. OBSERVED RESULT There is no way to select emoji to add to a post. EXPECTED RESULT There is an emoji picker -- some button that can be clicked to open a menu of custom server emoji and select one. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Kubuntu 22.04 (available in About System) KDE Plasma Version: 5.24.7 KDE Frameworks Version: 5.92.0 Qt Version: 5.15.3 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 466181] powerdevil crashes in KScreen::AbstractDpmsHelper::isSupported()
https://bugs.kde.org/show_bug.cgi?id=466181 --- Comment #21 from Chema --- Sorry, I think I didn't take a good look at the logs before. I don't understand now what is happening, I don't think any KDE component has been updated today. Right now it's also failing me with Kernel 6.1.13 when it didn't fail before, I don't understand it... I have reviewed the logs and I see that it is effectively leaving the same log as in Kernel 6.2. What I don't understand is why this started to fail when a couple of days ago it worked perfectly... Anyway, I'm waiting for KDE 5.27.2 to see if the bug is fixed with the change you've made. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 450992] [Dolphin file manager] Search could use some improvements
https://bugs.kde.org/show_bug.cgi?id=450992 K Freed changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |NOT A BUG -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 464585] Visually mark hardlinks
https://bugs.kde.org/show_bug.cgi?id=464585 --- Comment #6 from Jens --- I would like to suggest *not* to create a kind of "counter" overlay icon, though it sounds great on first thought. Considerations: – In details/compact view (with smallest icon size) overlay icons are really tiny and a number is almost impossible to read. – In addition this needs to implement quite a lot of different overlay icons (→ mem load). – Alternatively a textual overlay (→ e.g. Unicode square/encircled numbers) would complicate the implementation unnecessarily as this needs to be rendered at least each time you change the directory (→ even more mem load/switch time). – And at last, this most likely will cause a (endless) discussion about, »where should it stop counting?«. Instead I think a different colored overlay icon (with normal file name font style for hardlinks, as suggested by Simone Gaiarin) might be a good "first sight hint" (e.g. symlinks→green / hardlinks→yellow). If colors might be hard(er) to implement, maybe a different position (symlinks→lower right/ hardlinks→upper left) will do. In addition a hardlink counter field in the preview (both pane & tooltip) and *maybe* a column (→ details view) could make it even more customizable. (And *if* this needs another column/field to be replaced, I really wouldn't miss the assessment field.) BTW, I really miss such a feature! It's a pain i.t.a. to create workarounds for this kind of link management. Even Krusader can't help here. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 466410] Title bars are being squashed when "tiled" to corner
https://bugs.kde.org/show_bug.cgi?id=466410 --- Comment #5 from K Freed --- If anyone can help me debug this further, it would be great. Can't find a reliable way to reproduce further. Using the new tiling system and custom themes makes show up faster. This issue is purely cosmetic as the buttons actually activate in the positions the UI should be. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 466410] Title bars are being squashed when "tiled" to corner
https://bugs.kde.org/show_bug.cgi?id=466410 --- Comment #4 from K Freed --- Created attachment 156738 --> https://bugs.kde.org/attachment.cgi?id=156738=edit Window is resized bigger than it was -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 466410] Title bars are being squashed when "tiled" to corner
https://bugs.kde.org/show_bug.cgi?id=466410 --- Comment #3 from K Freed --- Created attachment 156737 --> https://bugs.kde.org/attachment.cgi?id=156737=edit Window fails to resize#1 -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 466181] powerdevil crashes in KScreen::AbstractDpmsHelper::isSupported()
https://bugs.kde.org/show_bug.cgi?id=466181 --- Comment #20 from Nate Graham --- Sounds like a different issue; please submit a new bug report. Make sure to include a backtrace with debug symbols if Powerdevil is crashing. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 466410] Title bars are being squashed when "tiled" to corner
https://bugs.kde.org/show_bug.cgi?id=466410 --- Comment #2 from K Freed --- Created attachment 156736 --> https://bugs.kde.org/attachment.cgi?id=156736=edit Window original size -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 466438] Some of Krita Layer and Brush Effect are not working properly Like Lumminosity, Multiply, Linear Bun, and some other
https://bugs.kde.org/show_bug.cgi?id=466438 --- Comment #1 from Brandon --- I'm just hoping this bug will be fixed and so that I can continue coloring my art -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 466438] New: Some of Krita Layer and Brush Effect are not working properly Like Lumminosity, Multiply, Linear Bun, and some other
https://bugs.kde.org/show_bug.cgi?id=466438 Bug ID: 466438 Summary: Some of Krita Layer and Brush Effect are not working properly Like Lumminosity, Multiply, Linear Bun, and some other Classification: Applications Product: krita Version: 5.1.5 Platform: Microsoft Windows OS: Microsoft Windows Status: REPORTED Severity: normal Priority: NOR Component: Color models Assignee: krita-bugs-n...@kde.org Reporter: brandominat...@gmail.com Target Milestone: --- SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** STEPS TO REPRODUCE 1. - 2. - 3. - OBSERVED RESULT - EXPECTED RESULT All the effect to work properly again SOFTWARE/OS VERSIONS Windows: 11 macOS: - Linux/KDE Plasma: - (available in About System) KDE Plasma Version: - KDE Frameworks Version: - Qt Version: Version (compiled): 5.12.12 Version (loaded): 5.12.12 ADDITIONAL INFORMATION This Weird bugs that a lot of the effects in Krita just won't work properly. Sorry not really good at describing things Bugs Screenshot = https://drive.google.com/drive/folders/1uAH1uFScHLZvoSn3ViMNPmMJrtlncQMo?usp=share_link Krita -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 466410] Title bars are being squashed when "tiled" to corner
https://bugs.kde.org/show_bug.cgi?id=466410 K Freed changed: What|Removed |Added CC||kortra...@gmail.com --- Comment #1 from K Freed --- Have not figured out how to reproduce this, but i've seen it. Seems like whatever informs the titlebar what size it should be isn't always working. Only fix for this is to close the affected window or change themes. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-plasma] [Bug 466357] Flickering in systray for apps that change tooltip or on mouse hover
https://bugs.kde.org/show_bug.cgi?id=466357 Oliver Beard changed: What|Removed |Added CC||olib...@outlook.com --- Comment #2 from Oliver Beard --- I have seen this issue with qBittorrent before, but I am presently on 5.27.1 and can't see it. I think it's probably still around, but appears inconsistently. https://github.com/qbittorrent/qBittorrent/issues/18217 I'm believe this is a Plasma issue, not a qBittorrent one, but I don't recall seeing it with other tooltips (though none are as dynamic). -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 445082] user-places.xbel is not updated after change of user name / change of user home location
https://bugs.kde.org/show_bug.cgi?id=445082 Kjetil Kilhavn changed: What|Removed |Added Resolution|DUPLICATE |--- Status|RESOLVED|REOPENED Ever confirmed|0 |1 --- Comment #2 from Kjetil Kilhavn --- I installed openSUSE Tumbleweed to check if this bug really was fixed in 5.25. Either it was not, or there has been a regression. Steps to reproduce: 1. Logged in as any user, create a new user "user2" with home directory /home/user2 2. Log out 3. Log in as user2 4. Open Dolphin 5. Log out 6. Log in as root 7. Execute the following commands (e.g. in Konsole): 7a) usermod -l user1 user2 7b) usermod -d /home/user1 user1 7c) mv /home/user2 /home/user1 8. Log out 9. Log in as user1 You can now observe the following: * If you open Dolphin you will see an error message about non-existing directory * If you open System Settings → Applications → Locations the correct file paths are displayed * If you open ~/local/share/user-places.xbel the old paths are stored in the bookmarks, e.g. Home -- You are receiving this mail because: You are watching all bug changes.
[frameworks-plasma] [Bug 360457] Window Thumbnail renders with QSGTexture::Nearest on at least intel chips
https://bugs.kde.org/show_bug.cgi?id=360457 mira...@mirandastreeter.com changed: What|Removed |Added CC||mira...@mirandastreeter.com -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kirigami] [Bug 466437] Kirigami.Dialog has a workaround with particular Breeze qqc2-desktop-style implementation in mind
https://bugs.kde.org/show_bug.cgi?id=466437 --- Comment #1 from ratijas --- Created attachment 156735 --> https://bugs.kde.org/attachment.cgi?id=156735=edit KF6 qqc2-desktop-style flat disabled ToolButton Apparently, I was wrong about git/master part. Disabled flat tool button has both text and icon faded with KF6 qqc2-desktop-style / Breeze. So the hack can be removed for KF6 on git master, I guess. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 457553] Duplicating layers with layer styles, and changing style on new layer results in wrong serialization and both layer have same layer styles after load.
https://bugs.kde.org/show_bug.cgi?id=457553 Brandon changed: What|Removed |Added CC||brandominat...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kirigami] [Bug 466437] New: Kirigami.Dialog has a workaround with particular Breeze qqc2-desktop-style implementation in mind
https://bugs.kde.org/show_bug.cgi?id=466437
Bug ID: 466437
Summary: Kirigami.Dialog has a workaround with particular
Breeze qqc2-desktop-style implementation in mind
Classification: Frameworks and Libraries
Product: frameworks-kirigami
Version: Master
Platform: Other
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: general
Assignee: kdelibs-b...@kde.org
Reporter: m...@ratijas.tk
CC: notm...@gmail.com
Target Milestone: Not decided
Created attachment 156734
--> https://bugs.kde.org/attachment.cgi?id=156734=edit
qqc2-desktop-style flat disabled ToolButton
SUMMARY
The following code looks like a workaround for a styling issue in a particular
QQC2 or, more specifically, qqc2-desktop-style implementation, namely Breeze:
> // add custom footer buttons
> Repeater {
> model: root.customFooterActions
> // we have to use Button instead of ToolButton, because ToolButton has no
> visual distinction when disabled
> delegate: QQC2.Button {
> flat: flatFooterButtons
> action: modelData
> visible: modelData.visible
> }
> }
This kind of hacks are not suitable for core library components like Dialog.
Besides, the dialog itself should have some sort of templates+styling split in
two components like QQC2. Then, qqc2-desktop-style implementation of Kirigami
templates could use any hacks which are appropriate for known bugs and
limitations.
Actually, this is not even entirely true. The icon of a flat disabled
ToolButton does change opacity. It's just the text that stays bright. However,
the non-flat counterpart fades both text and icon; and the background too. It
looks like a bug in qqc2-desktop-style bridge? Because in QtWidgets, if I set
e.g. toolbar actions in Dolphin to display icons and text, then disabled
Back/Forward flat toolbuttons are fading all at once -- not just icons.
STEPS TO REPRODUCE
1. Open Kirigami/Dialog.qml
OBSERVED RESULT
See workarounds.
EXPECTED RESULT
Upstream bug fixes.
SOFTWARE/OS VERSIONS
KDE Frameworks Version: git/master, git/kf5
--
You are receiving this mail because:
You are watching all bug changes.
[Powerdevil] [Bug 466181] powerdevil crashes in KScreen::AbstractDpmsHelper::isSupported()
https://bugs.kde.org/show_bug.cgi?id=466181 --- Comment #19 from Chema --- Reviewing the KSystemLog log with Kernel 6.1.14, I see that the error it is giving now is not the same as the one with Kernel 6.2, now it is leaving the following error when trying to access the power management configuration: 26/2/23 0:37systemsettings Failed to query platform profile choices "The name org.kde.Solid.PowerManagement was not provided by any .service files" -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 464592] Scrolling speed setting has no effect since Plasma 5.27 beta
https://bugs.kde.org/show_bug.cgi?id=464592 mira...@mirandastreeter.com changed: What|Removed |Added CC||mira...@mirandastreeter.com -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 465396] Display Configuration disregards list of "Screen Priorities" at every login on KDE Plasma with three-screen arrangement (leftmost and rightmost are rotated)
https://bugs.kde.org/show_bug.cgi?id=465396 mira...@mirandastreeter.com changed: What|Removed |Added CC||mira...@mirandastreeter.com -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 466181] powerdevil crashes in KScreen::AbstractDpmsHelper::isSupported()
https://bugs.kde.org/show_bug.cgi?id=466181 --- Comment #18 from Chema --- I know this bug is marked as fixed, but I wanted to point it out, because it has come to my attention, that with the new Linux Kernel 6.1.14 that has just been released, Powerdevil has also started to crash as it was in version 6.2 (also tested with version 6.2.1 and it continues to fail), I am commenting on it because I found it interesting to note that with previous versions of 6.1 (tested up to 6.1.13) this problem did not occur, in case this could give some other important information. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 457461] Ability to ignore all faces except tag marked
https://bugs.kde.org/show_bug.cgi?id=457461 Petr Schonmann changed: What|Removed |Added Ever confirmed|0 |1 Status|RESOLVED|REOPENED Resolution|FIXED |--- --- Comment #3 from Petr Schonmann --- When i use this feature, not all faces are tagged as ignored. Faces with suggestions arent marked as ignored -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 464996] Resurrection of bug 422111
https://bugs.kde.org/show_bug.cgi?id=464996 --- Comment #6 from Bob --- As an addon to my last comment, that line: file:///usr/share/plasma/plasmoids/org.kde.plasma.battery/contents/ui/CompactRepresentation.qml:61:17: Unable to assign [undefined] to int Also gets emitted periodically from plasmashell while the battery applet is bugged, probably due to periodic battery discharge updates in the backend somewhere. Seems like battery information is being sent to the applet, but once its in the bugged state it will not update otherwise. The only thing that clears it is a restart of plasmashell so the applet reloads to get the proper data. -- You are receiving this mail because: You are watching all bug changes.
[kde-inotify-survey] [Bug 466432] Tar archive and top dir names differ
https://bugs.kde.org/show_bug.cgi?id=466432 Harald Sitter changed: What|Removed |Added Resolution|--- |NOT A BUG Status|REPORTED|RESOLVED --- Comment #1 from Harald Sitter --- Will go away once it is part of KDE Gear. -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 462695] Automatic DisplayPort screen dimming/sleep and system sleep stops working on Wayland
https://bugs.kde.org/show_bug.cgi?id=462695 kot...@hotmail.com changed: What|Removed |Added CC||kot...@hotmail.com -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 466265] the effect tab has no effects only a white screen
https://bugs.kde.org/show_bug.cgi?id=466265 Bernd changed: What|Removed |Added CC||bern...@yahoo.com --- Comment #2 from Bernd --- (In reply to henhen from comment #0) > i update my version of kdenlive to the newest version, i think. i opened > kdenlive and the effect tab was white > the effect tab has no effects only a white screen > > > > Release Linux Mint 21.1 Vera 64-bit > Kernel Linux 5.15.0-60-generic x86_64 > MATE 1.26.0 > 3,8 GiB > Intel® Core™2 Duo CPU P8600 @ 2.40GHz × 2 > Mesa Mobile Intel® GM45 Express Chipset (CTG) You may be missing a module. Run this in a terminal window: sudo apt-get install -y qml-module-org-kde-kcm Fixed it for me (on Pop!_OS 22.04) -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 466436] New: S22 DNG thumbnails are not well oriented
https://bugs.kde.org/show_bug.cgi?id=466436 Bug ID: 466436 Summary: S22 DNG thumbnails are not well oriented Classification: Applications Product: digikam Version: 7.9.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Albums-MainView Assignee: digikam-bugs-n...@kde.org Reporter: davm6...@gmail.com Target Milestone: --- SUMMARY The generated thumbnails from the DNG file taken from a S22 with the latest available version of the Camera app and Android 13 are landscape oriented when the picture has been taken in portrait. STEPS TO REPRODUCE 1. Take a picture in portrait with a Galaxy S22 in pro mode with DNG support 2. Open this picture in DIgikam 7.9 3. The displayed thumbnail is in landscape OBSERVED RESULT EXPECTED RESULT Generated thumbnail in portrait when the photo has been taken in portrait. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 466435] New: Weird night color behavior on external monitor
https://bugs.kde.org/show_bug.cgi?id=466435 Bug ID: 466435 Summary: Weird night color behavior on external monitor Classification: Plasma Product: kwin Version: 5.27.1 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: mira.j...@gmail.com Target Milestone: --- SUMMARY When I plug into my laptop any external monitor while night color is active, the yellow filter suddenly gets applied only on the external monitor - it completely disappears from my internal screen. STEPS TO REPRODUCE 1. Turn on night color 2. Plug in second monitor 3. Observe OBSERVED RESULT Night color filter gets applied on all of the active screens. EXPECTED RESULT Filter gets applied only on the external screen. Cannot confirm if only on one or all of them, as my laptop has only one HDMI port. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Arch Linux, kernel 6.1.12-zen KDE Plasma Version: 5.27.1 KDE Frameworks Version: 5.103.0 Qt Version: 5.15.8 ADDITIONAL INFORMATION Acer Aspire A515-56 Intel i5-1135G7, integrated graphics -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 466434] New: Monitor frequently fails to go to sleep and corruption occurs after it attempts to or is shut off.
https://bugs.kde.org/show_bug.cgi?id=466434 Bug ID: 466434 Summary: Monitor frequently fails to go to sleep and corruption occurs after it attempts to or is shut off. Classification: Plasma Product: KScreen Version: 5.27.1 Platform: openSUSE OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: common Assignee: kscreen-bugs-n...@kde.org Reporter: kdeb...@schells.com Target Milestone: --- Created attachment 156733 --> https://bugs.kde.org/attachment.cgi?id=156733=edit journalctl output when the bug occurs SUMMARY On 5.27.0 I had the kded5 crashes after the monitor went to sleep or was manually powered off. After upgrade to 5.27.1 while that no longer happens, now there is another problem with random behavior after the monitor attempts to go to sleep or is powered off. On my normal account when typically the monitor should go to sleep instead the monitor wakes back up but most of my desktop icons are missing, sometimes terminal output is messed up, etc. For the general problem though I'll discuss what happens with a brand new account with entirely default configuration. STEPS TO REPRODUCE 1. Create a new account 2. Let the screen timeout. (Either the default 10 minutes or do "xset dpms 5 6 7" to speed things up 3. At first everything is fine. Monitor goes to sleep. 4. Open a konsole and run "sudo journalctl -f" 5. Let the monitor try to go to sleep again, it won't. (Usually, sometimes I've had to move back to the konsole that I ran xset in, or do something to start the bug.) OBSERVED RESULT The monitor will not go to sleep and instead just before it should the desktop will wake back up. There may be corruption of open apps and the Desktop. The journalctl fills with lines from kscreen like in the attachment. This journalctl output does not occur when the monitor goes to sleep and wakes back up correctly. EXPECTED RESULT The monitor should go to sleep. When the session is resumed the desktop and all applications should be as they were before the monitor went to sleep. The logs should not fill with information about the screen after every sleep/wake cycle. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Opensuse Tumbleweed KDE Plasma Version: 5.27.1 KDE Frameworks Version: 5.103.0 Qt Version: 5.15.8 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 466433] New: Wrong cursor icon on Wayland
https://bugs.kde.org/show_bug.cgi?id=466433 Bug ID: 466433 Summary: Wrong cursor icon on Wayland Classification: Plasma Product: kwin Version: 5.27.1 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: mira.j...@gmail.com Target Milestone: --- SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** I have custom theme (Materia) & cursor icon (Material Cursors) selected in plasma settings. However, when I am hovering over certain desktop parts (e.g. the Plasma panel/Desktop), the cursor gets reseted to the default breeze one. When hovering over e.g. Firefox, it seems fine. This issue persists only in Wayland - in X11 everything seems fine. STEPS TO REPRODUCE 1. Set custom cursor icon 2. Hover over any plasma app, Desktop etc. 3. Observe OBSERVED RESULT Default breeze cursor icon is shown EXPECTED RESULT Material cursor icon will be shown. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.27.1 KDE Frameworks Version: 5.103.0 Qt Version: 5.15.8 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 466420] Add ability to delete devices from Dolphin faster
https://bugs.kde.org/show_bug.cgi?id=466420 --- Comment #3 from Andrei Rybak --- For those who don't mind editing Dolphin's data manually, zacharytalis proposed a hacky solution over at https://bugs.kde.org/show_bug.cgi?id=466416#c4: > For the time being, you can prune these spam entries by editing > "~/.local/share/user-places.xbel" directly. (make sure to be careful and > take a backup, yada yada) I looked at the structure of this XML file, which consisted mostly of tags. Each bookmark has a tag, which has the strings which I was interested in -- the names of the phones. I grepped the file for all tags. I noticed that all the erroneous entries are clumped together: > $ cd ~/.local/share > $ grep '' user-places.xbel | uniq > [...] > Xiaomi > Pixel 6A > Xiaomi > Pixel 6A > Xiaomi > Pixel 6A > Xiaomi > Pixel 6A > Xiaomi > Pixel 6A > Xiaomi > Pixel 6A > Xiaomi > Pixel 6A So I did the following: 1. Found the first bookmark with the of an erroneous entry 2. Started selection 3. Found the last erroneous bookmark 4. Made sure the selection starts at an opening tag and ends at a closing tag 5. Deleted the whole selection -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 466416] KDE Connect keeps adding devices to Dolphin over and over and over and over and over
https://bugs.kde.org/show_bug.cgi?id=466416 --- Comment #5 from Andrei Rybak --- (In reply to zacharytalis from comment #4) > For the time being, you can prune these spam entries by editing > "~/.local/share/user-places.xbel" directly. (make sure to be careful and > take a backup, yada yada) It would have taken me a looong time to figure out where this is being stored. Thank you for saving my sanity when using Dolphin and my time! -- You are receiving this mail because: You are watching all bug changes.
[kde-inotify-survey] [Bug 466432] New: Tar archive and top dir names differ
https://bugs.kde.org/show_bug.cgi?id=466432 Bug ID: 466432 Summary: Tar archive and top dir names differ Classification: Plasma Product: kde-inotify-survey Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: ide...@protonmail.com CC: sit...@kde.org Target Milestone: --- SUMMARY The tar archive you can download at https://download.kde.org/stable/kde-inotify-survey/kde-inotify-survey-1.0.0.tar.zst contains a top directory named "kde-inotify-survey-v1.0.0". The "v" is part of the tag name "v1.0.0", but shouldn't appear here. I tried to look at the source code myself but I admit I don't know how the publishing process works. STEPS TO REPRODUCE 1. download https://download.kde.org/stable/kde-inotify-survey/kde-inotify-survey-1.0.0.tar.zst 2. tar --zstd -xf kde-inotify-survey-1.0.0.tar.zst OBSERVED RESULT The extracted directory is called kde-inotify-survey-v1.0.0 EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kwayland-integration] [Bug 466430] Wayland does not remember my monitor arrangement and crashes when I try to move a window into the second monitor.
https://bugs.kde.org/show_bug.cgi?id=466430 juuso.maen...@tutanota.com changed: What|Removed |Added Keywords||multiscreen, usability, ||wayland -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 466431] New: Users KCM should provide field to set password hint
https://bugs.kde.org/show_bug.cgi?id=466431 Bug ID: 466431 Summary: Users KCM should provide field to set password hint Classification: Applications Product: systemsettings Version: master Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: kcm_users Assignee: plasma-b...@kde.org Reporter: m...@ratijas.tk CC: uhh...@gmail.com Target Milestone: --- SUMMARY Apparently, in org.freedesktop.Accounts service provides PasswordHint property and setter method for users: # qdbus --system org.freedesktop.Accounts /org/freedesktop/Accounts/User1006 org.freedesktop.Accounts.User.SetPasswordHint 'string:Yahaha!' $ qdbus --system --literal org.freedesktop.Accounts /org/freedesktop/Accounts/User1006 org.freedesktop.Accounts.User.PasswordHint [Variant(QString): "string:Yahaha!"] But in KCM there's no UI for it. And neither it is displayed in SDDM (but that's a topic for a separate bug report). STEPS TO REPRODUCE 1. Open Users KCM. OBSERVED RESULT No UI fo rit. EXPECTED RESULT to be able to set and see password hint. -- You are receiving this mail because: You are watching all bug changes.
[kwayland-integration] [Bug 466430] New: Wayland does not remember my monitor arrangement and crashes when I try to move a window into the second monitor.
https://bugs.kde.org/show_bug.cgi?id=466430 Bug ID: 466430 Summary: Wayland does not remember my monitor arrangement and crashes when I try to move a window into the second monitor. Classification: Plasma Product: kwayland-integration Version: unspecified Platform: Archlinux OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: juuso.maen...@tutanota.com Target Milestone: --- SUMMARY *** I have a dual-monitor setup (laptop screen + external screen). Whenever I connect my second monitor, Wayland doesn't remember the config I chose for it (extend to right). If I try to drag a window into the external monitor, the screen goes black for a few seconds and all open apps crash. This doesn't happen if I select "Extend to right" from the monitor config widget, but the option gets reset whenever I connect my external display again after unplugging it. This has never occured to me in X11. *** STEPS TO REPRODUCE 1. Attach an external monitor into a laptop on Wayland. Don't change any configs. 2. Open any app. 3. Try to drag the window to the external monitor. 4. All the apps crash and the screen goes black for a few seconds. 5. After the crash, you are able to move apps to the second monitor. 6. When you unplug and re-plug the monitor, the issue is repeated as the config is not changed. OBSERVED RESULT All the apps crash and the screens go black EXPECTED RESULT The window gets moved to the external monitor properly SOFTWARE/OS VERSIONS Linux/KDE Plasma: EndeavourOS with kernel version 6.1.12-arch1-1 (available in About System) KDE Plasma Version: 5.27.1 KDE Frameworks Version: 5.103.0 Qt Version: 5.15.8 ADDITIONAL INFORMATION This has been happening since the first time I tried Wayland in Plasma 5.26 and it has never worked. I deleted all my kscreen config files from "~/.local/share/kscreen" and it asked for the arrangement when I connected the external monitor. I chose "Extend to right" but it still didn't work. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 466416] KDE Connect keeps adding devices to Dolphin over and over and over and over and over
https://bugs.kde.org/show_bug.cgi?id=466416 --- Comment #4 from zacharyta...@gmail.com --- I'm also experiencing this bug (same software versions but on Arch Linux). My phone's a Samsung Galaxy S10, in case that's relevant. For the time being, you can prune these spam entries by editing "~/.local/share/user-places.xbel" directly. (make sure to be careful and take a backup, yada yada) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 464996] Resurrection of bug 422111
https://bugs.kde.org/show_bug.cgi?id=464996 --- Comment #5 from Bob --- In regular use I have a non-systemd system and plasmashell and powerdevil get started via their /etc/kde/xdg/autostart/ scripts. They are not always started in the same order on my system. Sometimes they are closer together, sometimes further apart, sometimes in reverse order. It would seem that on some of these occasions there is a timing that hits this bug. With that in mind, I managed to reproduce this bug from a running plasma session by opening konsole and running the following as my test user: # /usr/lib64/libexec/org_kde_powerdevil --replace & /usr/bin/plasmashell --replace Most of the time the two will restart as normal. However on rare occasion it will start with the bugged batterymonitor applet where it fails to report about my laptop's battery. Racing the two programs this way seems to trigger it as well, although only on rare occasion. The plasmashell console spew after the --replace command was is same everytime when the battery applet is working normally. When the applet gets bugged, the only difference is that plasmashell console will output the following: file:///usr/share/plasma/plasmoids/org.kde.plasma.battery/contents/ui/CompactRepresentation.qml:61:17: Unable to assign [undefined] to int This line gets emitted when clicking on the icon in the system tray when the battery icon that should be there is bugged and replaced with the display brightness icon instead. I am not a kde/plasma expert so its hard to know what to look into next here. Any insight on what to try next from a dev would be appreciated. -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 399646] Brightness control adjusts the wrong backlight control (multiple GPUs)
https://bugs.kde.org/show_bug.cgi?id=399646 Nils changed: What|Removed |Added Status|RESOLVED|REOPENED Resolution|FIXED |--- CC||nils.van-zuij...@mailo.com --- Comment #13 from Nils --- This is happening again in Plasma 5.27.1 Here are my hardware/software infos: Operating System: Manjaro Linux KDE Plasma Version: 5.27.1 KDE Frameworks Version: 5.103.0 Qt Version: 5.15.8 Kernel Version: 6.1.13-1-MANJARO (64-bit) Graphics Platform: Wayland Processors: 16 × AMD Ryzen 9 5900HX with Radeon Graphics Memory: 62.2 Gio of RAM Graphics Processor: AMD Radeon Graphics Manufacturer: TUXEDO Product Name: TUXEDO Stellaris AMD Gen3 (CZN) Here is a log of some values of the sys providers concerned. The backlight value changes for acpi_video0 but amdgpu_bl1 is the one controlling the screen. $ pwd /sys/class/backlight $ ls acpi_video0 amdgpu_bl1 $ cat acpi_video0/device/enable 1 $ cat amdgpu_bl1/device/enable 1 $ cat acpi_video0/max_brightness 49 $ cat amdgpu_bl1/max_brightness 255 -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 466319] Opening the phone menu of kdeconnect widget causes memory leak
https://bugs.kde.org/show_bug.cgi?id=466319 --- Comment #2 from rob.d...@telus.net --- Created attachment 156732 --> https://bugs.kde.org/attachment.cgi?id=156732=edit Laptop died, took photo of memory usage Since the laptop had died I was unable to take a screen shot so I photographed it. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 428112] Changing XDG folder locations in the KCM does not update items in the Places Model that point to the old location
https://bugs.kde.org/show_bug.cgi?id=428112 --- Comment #15 from Kjetil Kilhavn --- (In reply to LUBE from comment #13) > I have the same Problem in the newest version after a User Rename. > everything is still pointing to /home/[oldusername]/... I guess you are experiencing the problem I reported, which in my opinion erroneously was marked as a duplicate of this one. You should therefore probably reopen https://bugs.kde.org/show_bug.cgi?id=445082 instead, but please check my description first to ensure it actually is the same problem you are experiencing. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 460341] On X11 with proprietary NVIDIA GPU drivers, external monitor disabled after reboot or wake-from-sleep
https://bugs.kde.org/show_bug.cgi?id=460341 --- Comment #151 from Steven Robbins --- (In reply to Nate Graham from comment #146) > I suspect this has been fixed by the fix for Bug 462725. > > Anybody who can reproduce the issue and build software from source: can you > patch KWin with 1d237c29655c7e3fb15fb9b71e5f167bd207593f Very happy to report that patch (applied to 5.27.0 libkscreen as delivered in Debian sid) fixes the symptoms I've been experiencing -- namely that hot disconnect / reconnect of a monitor failed to enable it. Thank you to the KDE screen team!! -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 387673] menu headings corrupt, showing "no text"
https://bugs.kde.org/show_bug.cgi?id=387673 --- Comment #13 from Michael --- Created attachment 156731 --> https://bugs.kde.org/attachment.cgi?id=156731=edit from .local/share/kxmlgui5/okular that was causing "no text" This same issue with Okular and "no text" appearing in the menu bar has been present for me for about a year under KDE neon user edition. I kept thinking it would resolve itself with every new version of Plasma (now 5.27.1) or Okular (now 22.12.2), but it didn't. I finally removed the files in ".local/share/kxmlgui5/okular" and I'm back to normal. I'm attaching the old files from .local/share/kxmlgui5/okular. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 466416] KDE Connect keeps adding devices to Dolphin over and over and over and over and over
https://bugs.kde.org/show_bug.cgi?id=466416 zacharyta...@gmail.com changed: What|Removed |Added CC||zacharyta...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 387673] menu headings corrupt, showing "no text"
https://bugs.kde.org/show_bug.cgi?id=387673 --- Comment #12 from Michael --- Created attachment 156730 --> https://bugs.kde.org/attachment.cgi?id=156730=edit from .local/share/kxmlgui5/okular that was causing "no text" -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 466335] Task bar not visible on second monitor but fullscreen window acts as if it was
https://bugs.kde.org/show_bug.cgi?id=466335 --- Comment #4 from k...@imkx.dev --- I just discovered where the issue might come from while having an issue with games launching on my non primary monitor. In the settings i switched around the primary display between my two monitors a few times or generally just toggled settings, also disabled the non-primary display and that fixed this issue as well as the game starting on the wrong monitor. I am guessing that the issue initially begun when switching my Primary HDMI to my TV for watching a movie and going back to my normal display. -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 456210] Under certain circumstances when using multiple monitors, "unlock" button is clickable but does nothing
https://bugs.kde.org/show_bug.cgi?id=456210 Lewis L. Foster changed: What|Removed |Added CC||le...@sniff122.tech --- Comment #71 from Lewis L. Foster --- I am also experiencing this bug on the framework laptop and the fingerprint reader on 5.25.5 on ubuntu 22.04. I have the fingerprint setup with libfprint and i have it configured in `/etc/pam.d/common-auth`. With just the internal display, I can move my mouse or press a key on the keyboard and it will ask me to place my finger on the reader and it will show the unlock button which works. With multiple displays connected, the unlock button appears to do nothing and i have to run a loginctl unlock-session from another tty to be able to unlock. I have also tried entering my password before placing my finger on the reader with the same effect. I have a similar setup with my work machine (a HP probook 440 G8) so i'll test that and see how it works Ubuntu 22.04 Plasma 5.25.5 Wayland -- You are receiving this mail because: You are watching all bug changes.
