[systemsettings] [Bug 436460] Box doesn't snap correctly when monitor is mirrored
https://bugs.kde.org/show_bug.cgi?id=436460 --- Comment #5 from Chef Niko --- Created attachment 138611 --> https://bugs.kde.org/attachment.cgi?id=138611=edit 5.21.90 snap to 1919 If you'd like me to test this against 5.22, please provide information on how to acquire 5.22 installation. I looked around online, but everything called 5.22 seems to link to 5.21.9. I did test it against 5.21.9, and it is much better. I really like how the snap is less aggressive. Unfortunately, it's not quite right yet. Here's a screenshot from the KDE Neon 5.21.9 live image, showing the snap to 1919 instead of 1920. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 437226] login script disappears after closing and re-opening the KCM
https://bugs.kde.org/show_bug.cgi?id=437226 --- Comment #9 from Chef Niko --- Thank you for the additional information... and point taken. :) I tried the neon testing addition live image, and it looks much better. When I closed and re-opened the settings window, the script showed up correctly. Unfortunately, I couldn't test if the script ran at log in, because I couldn't log out. I made a new user then logged out, but it just went right back to the desktop as the live user. I also tried to switch users, but that ended up hanging (not the entire system, but the animation stopped running). Anyway, that's good enough for me. If the scripts still aren't running properly in the future, I can re-address it then. Thanks for your help! -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 437226] login script disappears after closing and re-opening the KCM
https://bugs.kde.org/show_bug.cgi?id=437226 --- Comment #7 from Chef Niko --- Thank you for the additional information! I ran the command mentioned, and got a blank return... so I guess that's a no to using systemd startup feature. Konsole Output: ($) ~: kreadconfig5 --file startkderc --group General --key systemdBoot ($) ~: Just to confirm, do you want me to try the testing version from here: https://neon.kde.org/download Sorry for the back and forth, but KDE isn't the most accessible software to do things like getting source code or installing betas, so I just want to confirm I'm testing the right thing. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 437226] login script disappears after closing and re-opening the KCM
https://bugs.kde.org/show_bug.cgi?id=437226 --- Comment #3 from Chef Niko --- Sorry, I don't know how to answer your question. I'm not familiar with how systemd works. It looks like the login scripts aren't running. My log file isn't being updated at all when I log in, but when I run my script manually it does work. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 437225] No files match filter to install cursor themes
https://bugs.kde.org/show_bug.cgi?id=437225 --- Comment #2 from Chef Niko --- Thanks for the info! I didn't read in the wiki that I needed an archive. First, I tried making an archive out of the contents of the folder, and it said it was invalid. Then, I tried making an archive out of the entire folder, but then kcm_cursortheme crashed. I used 'tar -cvzf ' I believe this is a .tar.gz file, correct? Am I doing something wrong? Here's the konsole output: ($) ~/.icons: kcmshell5 kcm_cursortheme Model size of -82 is less than 0 Model size of -10 is less than 0 file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/kirigami.2/templates/InlineMessage.qml:259:9: QML ActionToolBar: Binding loop detected for property "atBottom" file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/kirigami.2/templates/InlineMessage.qml:259:9: QML ActionToolBar: Binding loop detected for property "atBottom" KCrash: crashing... crashRecursionCounter = 2 KCrash: Application Name = kcmshell5 path = /usr/bin pid = 13906 KCrash: Arguments: /usr/bin/kcmshell5 kcm_cursortheme KCrash: Attempting to start /usr/lib/x86_64-linux-gnu/libexec/drkonqi QSocketNotifier: Invalid socket 8 and type 'Read', disabling... QSocketNotifier: Invalid socket 15 and type 'Read', disabling... QSocketNotifier: Invalid socket 25 and type 'Read', disabling... [1]+ Stopped kcmshell5 kcm_cursortheme After some time, this appeared on the konsole as well: ($) ~/.icons: pa_write() failed while trying to wake up the mainloop: Bad file descriptor pa_write() failed while trying to wake up the mainloop: Bad file descriptor Invalid write to eventfd: Bad file descriptor Code should not be reached at pulsecore/fdsem.c:199, function pa_fdsem_post(). Aborting. Unable to start Dr. Konqi Re-raising signal for core dump handling. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 437226] New: login script doesn't show: cannot anchor....
https://bugs.kde.org/show_bug.cgi?id=437226 Bug ID: 437226 Summary: login script doesn't show: cannot anchor Product: systemsettings Version: 5.21.4 Platform: Ubuntu Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: kcm_autostart Assignee: nicolas.fe...@gmx.de Reporter: culinaryelat...@zohomail.com CC: plasma-b...@kde.org Target Milestone: --- SUMMARY When setting a login script to run in the system settings, it does not show again after the window is closed. STEPS TO REPRODUCE 1. Add login script to the autostart system settings. 2. Close the settings window. 3. Open the settings window again. OBSERVED RESULT No autostart scripts are shown. EXPECTED RESULT Previously selected autostart script is shown. SOFTWARE/OS VERSIONS Kubuntu 21.04 Plasma: 5.21.4 Frameworks: 5.80.0 QT: 5.15.2 Kernel 5.11.0-17-generic x64 ADDITIONAL INFORMATION Konsole output: $) ~: kcmshell5 autostart file:///usr/share/kpackage/kcms/kcm_autostart/contents/ui/main.qml:35:13: QML InlineMessage: Cannot anchor to an item that isn't a parent or sibling. Model size of -96 is less than 0 Model size of -13 is less than 0 ($) ~: kcmshell5 autostart file:///usr/share/kpackage/kcms/kcm_autostart/contents/ui/main.qml:35:13: QML InlineMessage: Cannot anchor to an item that isn't a parent or sibling. -- How do I remove the duplicate entries for the login script, when I can't see them in the UI? -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 437225] New: No files match filter to install cursor themes
https://bugs.kde.org/show_bug.cgi?id=437225
Bug ID: 437225
Summary: No files match filter to install cursor themes
Product: systemsettings
Version: 5.21.4
Platform: Ubuntu Packages
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: kcm_cursortheme
Assignee: plasma-b...@kde.org
Reporter: culinaryelat...@zohomail.com
Target Milestone: ---
SUMMARY
No files match the filter when attempting to install new cursor theme, so they
cannot be selected in the UI. This includes new and previously working files.
STEPS TO REPRODUCE
1. Open kcm_cursortheme
2. Click "Install From File..."
3. Browse to directory containing theme
OBSERVED RESULT
No files are shown to install
EXPECTED RESULT
Files are shown to install
SOFTWARE/OS VERSIONS
Kubuntu 21.04
Plasma: 5.21.4
Frameworks: 5.80.0
QT: 5.15.2
Kernel 5.11.0-17-generic x64
ADDITIONAL INFORMATION
Konsole output:
$) ~/.icons/SM: kcmshell5 kcm_cursortheme
Model size of -82 is less than 0
Model size of -10 is less than 0
kf.kio.widgets.kdirmodel: No node found for item that was just removed:
QUrl("file:///home/niko/.Xauthority")
Model size of -82 is less than 0
Model size of -10 is less than 0
Sample theme file
($) ~/.icons/warcraft-3-cursors: cat index.theme
[Icon Theme]
Name=Sorely's Warcraft cursors
Attempting to set a new cursor theme results in the following error:
QDBusConnection: error: could not send signal to service "" path
"//home/niko/.kde/share/config/kdeglobals" interface "org.kde.kconfig.notify"
member "ConfigChanged": Invalid object path:
//home/niko/.kde/share/config/kdeglobals
--
You are receiving this mail because:
You are watching all bug changes.
[systemsettings] [Bug 436662] Default Audio Device (profile) does not persist across login
https://bugs.kde.org/show_bug.cgi?id=436662 --- Comment #2 from Chef Niko --- Thank you for the information. When I set the default profile with pacmd, the default device does persist across logins, which is another fix, or at least workaround. E.g. `($) ~: pacmd set-default-sink alsa_output.pci-_04_00.0.analog-stereo` Please confirm if you would still like me to file a bug with pulseaudio, and if so, please update me with what KDE's pulseaudio UI is actually doing, so I can include that information. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 436662] New: Default Audio Device (profile) does not persist across login
https://bugs.kde.org/show_bug.cgi?id=436662 Bug ID: 436662 Summary: Default Audio Device (profile) does not persist across login Product: systemsettings Version: 5.21.4 Platform: Ubuntu Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: kcm_pulseaudio Assignee: now...@gmail.com Reporter: culinaryelat...@zohomail.com CC: plasma-b...@kde.org Target Milestone: --- SUMMARY When I log in to my system, the default audio device is not selected correctly. It is set to the original device instead of the device which was active at log out. STEPS TO REPRODUCE 1. Change the default audio device (and/or profile) to something different than what is initially selected in System Settings -> Audio. 2. Log out 3. Log in OBSERVED RESULT Default audio device is reset to the original device. EXPECTED RESULT Default audio device is the same when logging in, which it was when logging out. OR an additional option to set default device on log in. SOFTWARE/OS VERSIONS Kubuntu 21.04 Plasma: 5.21.4 Frameworks: 5.80.0 QT: 5.15 Kernel 5.11.0-16-generic x64 ADDITIONAL INFORMATION After manually editing the pulse configuration file '~/.config/pulse/default.pa', the desired audio device is active on login. However, this should be saved using KDE's system settings window, and not need to be done manually via editing config files. This has been a problem for a while now, but it is getting better. In the last version of KDE I was running, it didn't even show my desktop speakers after a reboot until I restarted pulseaudio. Now they show up initially, so that's good progress, but the default device after a login should be the same as before the logout. I don't know if this is related, but I am also having a problem where quite frequently (almost daily, but not every login or reboot) the default profile on my video card is reset. I.e. the active profile changes to 'Digital Stereo (HDMI 5) Output', instead of 'Digital Stero (HMDI 6) Output', which is what I repeatedly set it to. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 436465] Cannot pin certain apps to task-manager
https://bugs.kde.org/show_bug.cgi?id=436465 --- Comment #7 from Chef Niko --- Created attachment 138181 --> https://bugs.kde.org/attachment.cgi?id=138181=edit requested output from xprop, then clicking on "zerobrane studio" application I've included the output in the attached file 'xprop-zerobrane-studio', as requested. It was generated by running `xprop >> xprop-zerobrane-studio` in Konsole, then clicking on the 'Zerobrane Studio' Application, which is not pinning. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 436465] Cannot pin certain apps to task-manager
https://bugs.kde.org/show_bug.cgi?id=436465 --- Comment #5 from Chef Niko --- While I filed this bug against the task manager, I'm not sure that is correct. When I drag the application directly on to a panel (not the task manager), the same lack of result (failure) is occurring. I don't really know how the KDE components are coded, but this suggests to me that the panel, task manager, and icon only task manager are all calling a shared function to "pin" an icon to them, which is where the problem is occurring. Hopefully this helps clarify things, and I apologize if I chose the wrong component for this bug. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 436460] Box doesn't snap correctly when monitor is mirrored
https://bugs.kde.org/show_bug.cgi?id=436460 --- Comment #3 from Chef Niko --- Created attachment 138157 --> https://bugs.kde.org/attachment.cgi?id=138157=edit requested screenshot of "Display Configuration" Sorry I wasn't more clear in the description. Here's a screenshot showing the box snapping to 1918 instead of 1920. From moving the boxes around, it seems like the edge gets offset by 1 when they stack on top of each other. ($) ~: xrandr | grep connected DisplayPort-0 disconnected (normal left inverted right x axis y axis) DisplayPort-1 disconnected (normal left inverted right x axis y axis) HDMI-A-0 connected primary 1920x1080+1918+0 (normal left inverted right x axis y axis) 598mm x 336mm HDMI-A-1 connected 1920x1080+1919+0 (normal left inverted right x axis y axis) 886mm x 498mm DVI-D-0 connected 1920x1080+0+0 (normal left inverted right x axis y axis) 521mm x 293mm -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 436465] Cannot pin certain apps to task-manager
https://bugs.kde.org/show_bug.cgi?id=436465 --- Comment #4 from Chef Niko --- That's correct. When I click on it, nothing appears to happen. Here are my observations: 1. Menu closes (expected) 2. When opening up the menu again, the box is not filled in (unexpected, box should be filled in) 3. Upon closing the application, it is removed from the task manager (unexpected, it is expected to remain pinned). Other functions on other menus seem to work fine. E.g. "More Actions" -> "Keep Below Others". When clicking on this, the corresponding box is filled in, and the window is indeed kept below other windows. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 436465] Cannot pin certain apps to task-manager
https://bugs.kde.org/show_bug.cgi?id=436465 --- Comment #2 from Chef Niko --- Method 1: 1. Launch application 2. Right click application entry in the task bar 3. Mouse over "Pin To Task Manager" 4. Click box of the activity to pin the application on Method 2: 1. Launch Application 2. Drag application entry on the task bar on to a panel Neither of these methods produce the desired result. My apologies for not being more detailed originally. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 436452] Application launcher opening on secondary monitor when accessed via shortcut key
https://bugs.kde.org/show_bug.cgi?id=436452 --- Comment #1 from Chef Niko --- While configuring my desktops, I removed the original application launcher off my secondary monitor, and added a new one on my primary monitor. Now the shortcut key has no affect. So, it seems like it only calls the first application launcher that was created on system install. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 436465] Cannot pin certain apps to task-manager
https://bugs.kde.org/show_bug.cgi?id=436465 Chef Niko changed: What|Removed |Added CC||culinaryelat...@zohomail.co ||m -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 436465] New: Cannot pin certain apps to task-manager
https://bugs.kde.org/show_bug.cgi?id=436465 Bug ID: 436465 Summary: Cannot pin certain apps to task-manager Product: plasmashell Version: 5.21.4 Platform: Ubuntu Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Task Manager and Icons-Only Task Manager Assignee: h...@kde.org Reporter: culinaryelat...@zohomail.com CC: plasma-b...@kde.org Target Milestone: 1.0 SUMMARY Certain applications fail to pin to the task manager. This problem exists for both the task manager, and the icons only task manager. One such application is "ZeroBrane Studio". STEPS TO REPRODUCE 1. Launch application 2. Attempt to pin application to task manager OBSERVED RESULT Fails to pin to task manager. EXPECTED RESULT Pin to task manager succeeds. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Kubuntu 21.04 5.11.0-16-generic x64 KDE Plasma Version: 5.21.4 KDE Frameworks Version: 5.80.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION "Zerobrane Studio" was pinnable to task manager before upgrading Ubuntu/KDE. -- You are receiving this mail because: You are watching all bug changes.
[docs] [Bug 436458] Request for documentation on backing up config files
https://bugs.kde.org/show_bug.cgi?id=436458 --- Comment #2 from Chef Niko --- Thank you for the link to the existing documentation. Unfortunately it is quite out of date, and no longer applicable. Backing up the entirety of ~/.config will get most of the configuration settings, though not quite all of them. However, that will also backup the configuration setting for every application installed on the system (using the ~/.config folder), which is horribly inefficient. Backing up only the Plasma configuration allows the possibility of installing a new (or re-installing) an operating system, then easily applying the desired configuration, without having to spend time setting it up again. It's really great that Plasma is so configurable, but it's not something I want to do more than once. Unfortunately, that's exactly what I'm doing today. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 436460] Box doesn't snap correctly when monitor is mirrored
https://bugs.kde.org/show_bug.cgi?id=436460 --- Comment #1 from Chef Niko --- Co-ordinates should be `1920, 0`, not `0, 1920`. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 436460] Box doesn't snap correctly when monitor is mirrored
https://bugs.kde.org/show_bug.cgi?id=436460 Chef Niko changed: What|Removed |Added CC||culinaryelat...@zohomail.co ||m -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 436460] New: Box doesn't snap correctly when monitor is mirrored
https://bugs.kde.org/show_bug.cgi?id=436460 Bug ID: 436460 Summary: Box doesn't snap correctly when monitor is mirrored Product: systemsettings Version: 5.21.4 Platform: Ubuntu Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: kcm_kscreen Assignee: kscreen-bugs-n...@kde.org Reporter: culinaryelat...@zohomail.com CC: plasma-b...@kde.org Target Milestone: --- SUMMARY In the section "drag screens to re-arrange them" the boxes do not snap correctly when it has a replicate. It's close, but not quite accurate. This causes either a gap (offsetting full screen applications), or an overlap. STEPS TO REPRODUCE 1. Set tertiary monitor to replicate secondary 2. Drag secondary monitor around in the "drag screens" section 3. Try to snap secondary monitor to the primary (0,1920) OBSERVED RESULT Inaccurate co-ordinates on snap. I've seen them in the range of 1917-1921. EXPECTED RESULT Accurate co-ordinates on snap. 0,1920 in my case. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Kubuntu 21.04 5.11.0-16-generic x64 KDE Plasma Version: 5.21.4 KDE Frameworks Version: 5.80.0 Qt Version: 5.15.2 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 436459] FEATURE REQUEST: Backup/Restore (Import/Export) Settings Button
https://bugs.kde.org/show_bug.cgi?id=436459 Chef Niko changed: What|Removed |Added CC||culinaryelat...@zohomail.co ||m -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 436459] New: FEATURE REQUEST: Backup/Restore (Import/Export) Settings Button
https://bugs.kde.org/show_bug.cgi?id=436459 Bug ID: 436459 Summary: FEATURE REQUEST: Backup/Restore (Import/Export) Settings Button Product: systemsettings Version: 5.21.4 Platform: Ubuntu Packages OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: culinaryelat...@zohomail.com Target Milestone: --- SUMMARY There are a lot of settings in KDE, with no clear or easy way to backup and restore them. The settings files are a complete mess. There's files named `k...` in ~/.config, there's a bunch of different folders for the different KDE components, along every other application's settings. All of this should be in a root KDE folder. There is a root KDE folder, but there's a bunch of stuff outside of it too. On top of that, there are other settings that aren't even in ~/.config. OBSERVED RESULT Confusion and frustration about how all the settings are saved, with no easy way to back them up. EXPECTED RESULT Intuitive folder structure with all the settings files saved under a root folder, along with a way to easily back them up. STEPS TO REPRODUCE 1. Install and configure KDE 2. Attempt to backup settings. OBSERVED RESULT Confusion, frustration, and disappointment. EXPECTED RESULT Easily obtained copy of settings. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Kubuntu 21.04 5.11.0-16-generic x64 KDE Plasma Version: 5.21.4 KDE Frameworks Version: 5.80.0 Qt Version: 5.15.2 -- You are receiving this mail because: You are watching all bug changes.
[docs] [Bug 436458] New: Request for documentation on backing up config files
https://bugs.kde.org/show_bug.cgi?id=436458 Bug ID: 436458 Summary: Request for documentation on backing up config files Product: docs Version: unspecified Platform: Ubuntu Packages OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: Missing Content Assignee: kde-doc-engl...@kde.org Reporter: culinaryelat...@zohomail.com Target Milestone: --- SUMMARY There's a lot of config options in KDE, and no documentation on how to back them up. Looking at guides from others, there's a lot of outdated and hit-and-miss information. It would be really helpful if there was documentation on exactly how to back up the settings. STEPS TO REPRODUCE 1. Read KDE manual OBSERVED RESULT No documentation on how to backup settings. EXPECTED RESULT Clear documentation on how to backup settings. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 436452] Application launcher opening on secondary monitor when accessed via shortcut key
https://bugs.kde.org/show_bug.cgi?id=436452 Chef Niko changed: What|Removed |Added Platform|Other |Ubuntu Packages -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 436452] Application launcher opening on secondary monitor when accessed via shortcut key
https://bugs.kde.org/show_bug.cgi?id=436452 Chef Niko changed: What|Removed |Added CC||culinaryelat...@zohomail.co ||m -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 436452] New: Application launcher opening on secondary monitor when accessed via shortcut key
https://bugs.kde.org/show_bug.cgi?id=436452 Bug ID: 436452 Summary: Application launcher opening on secondary monitor when accessed via shortcut key Product: plasmashell Version: 5.21.4 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Application Launcher (Kickoff) Assignee: k...@davidedmundson.co.uk Reporter: culinaryelat...@zohomail.com CC: mikel5...@gmail.com, plasma-b...@kde.org Target Milestone: 1.0 SUMMARY Fresh install of Kubuntu 21.04 placed the default panel on my tertiary monitor. I changed the system settings, but application launcher shortcut key still opens the application launcher on secondary monitor instead of primary. (Tertiary is now a mirror of secondary). STEPS TO REPRODUCE 1. Install Kubuntu 21.04 with 3 monitors. 2. Press application launcher shortcut key OBSERVED RESULT Application launcher opens on secondary/tertiary monitor. EXPECTED RESULT Application launcher opens on primary desktop. SOFTWARE/OS VERSIONS KDE Plasma Version: 5.21.4 KDE Frameworks Version: 5.80.0 Qt Version: 5.15.2 Kubuntu 21.04 5.11.0-16-generic x64 -- You are receiving this mail because: You are watching all bug changes.
[kolourpaint] [Bug 436356] New: kolourpaint doesn't update png data correctly
https://bugs.kde.org/show_bug.cgi?id=436356 Bug ID: 436356 Summary: kolourpaint doesn't update png data correctly Product: kolourpaint Version: 20.08 Platform: Ubuntu Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kolourpaint-supp...@lists.sourceforge.net Reporter: culinaryelat...@zohomail.com Target Milestone: --- Created attachment 138003 --> https://bugs.kde.org/attachment.cgi?id=138003=edit sample .png file SUMMARY I have a png file converted from a tga source, using imagemagick. While this seems valid (I can see it in dolphin, open it in kolourpaint etc), it won't work with utilities like libpng. Metapicz.com reports the file contains errors. When I edit and save the file in kolourpaint, the errors remain. I can make a new file in kolourpaint, which then works with libpng, but the quality is unacceptable. STEPS TO REPRODUCE 1. Open .png file in kolourpaint 2. Edit file 3. Save file OBSERVED RESULT png data not updated EXPECTED RESULT png data updated SOFTWARE/OS VERSIONS KDE Plasma Version: 5.19.5 KDE Frameworks Version: 5.74.0 Qt Version: 5.14.2 ADDITIONAL INFORMATION Attached .png which can be used to demonstrate the problem. -- You are receiving this mail because: You are watching all bug changes.
