[plasmashell] [Bug 367666] Add option to change wallpaper for lock screen, login screen, and desktop all at once
https://bugs.kde.org/show_bug.cgi?id=367666 Peter Hoeg changed: What|Removed |Added CC||peterh...@gmail.com --- Comment #8 from Peter Hoeg --- There are other ways to work around this. You can use the plasma-apply-wallpaperimage to set the desktop at least across all desktops in one go. -- You are receiving this mail because: You are watching all bug changes.
[Skanlite] [Bug 456576] New: Skanlite needs to be closed in order to scan new page
https://bugs.kde.org/show_bug.cgi?id=456576 Bug ID: 456576 Summary: Skanlite needs to be closed in order to scan new page Product: Skanlite Version: 22.04.2 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kare.s...@iki.fi Reporter: p.hai...@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 *** When using Skanlite, after scanning one page and saving it, I am not able to scan a new page until I close and re-open Skanlite. Error message given is "Device busy". Bug does not occur if I do not save the page. STEPS TO REPRODUCE 1. Open Skanlite 2. Scan one page 3. Save page 4. Try to scan a new page OBSERVED RESULT Scanning fails due to "Device busy". EXPECTED RESULT Scanning to be successful. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION When Skanlite shows the error message "Device busy", the scanner shows the message "Scanning" but does nothing. After Skanlite is closed, the scanner stops showing "Scanning" and is again available. Device model : HP Photosmart C4380 series -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 455649] latte crashes when closing steam from systray
https://bugs.kde.org/show_bug.cgi?id=455649 Michail Vourlakos changed: What|Removed |Added Summary|Latte Dock crashes when |latte crashes when closing |closing Steam |steam from systray -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 456519] Bleachbit crashes latte everytime
https://bugs.kde.org/show_bug.cgi?id=456519 Michail Vourlakos changed: What|Removed |Added Summary|Bleachbit crashes Mate Dock |Bleachbit crashes latte |everytime |everytime -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 456519] Bleachbit crashes Mate Dock everytime
https://bugs.kde.org/show_bug.cgi?id=456519 Michail Vourlakos changed: What|Removed |Added Resolution|--- |UPSTREAM Status|REPORTED|RESOLVED --- Comment #1 from Michail Vourlakos --- this is a plasma crash not Latte, you should be able to reproduce with default plasma panel and taskmanager -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 456416] Since 5.25.2 update, colors in maximized mode always go white
https://bugs.kde.org/show_bug.cgi?id=456416 Michail Vourlakos changed: What|Removed |Added Resolution|--- |WAITINGFORINFO Status|REPORTED|NEEDSINFO --- Comment #2 from Michail Vourlakos --- I suppose plasma 5.25.3 will fix it -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 450893] [x11/virtual desktops] panels only persist onallvirtualdesktops if they have been edited during the current session
https://bugs.kde.org/show_bug.cgi?id=450893 Michail Vourlakos changed: What|Removed |Added CC||tale...@gmail.com --- Comment #2 from Michail Vourlakos --- *** Bug 456575 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 456575] Top bar disappears in other virtual desktops
https://bugs.kde.org/show_bug.cgi?id=456575 Michail Vourlakos changed: What|Removed |Added Resolution|--- |DUPLICATE Status|REPORTED|RESOLVED --- Comment #1 from Michail Vourlakos --- *** This bug has been marked as a duplicate of bug 450893 *** -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 455805] At start of digikam: "Your locale has changed since this album was last opened."
https://bugs.kde.org/show_bug.cgi?id=455805 --- Comment #6 from Ferry <06f13.41...@mailbox.org> --- (In reply to Maik Qualmann from comment #5) > No, this change does not affect adding GPX data either. Can you describe > your problem when adding GPX data? > There is a change due to bug reports that the decimal separator (dot or > comma) for GPS coordinates should match the locale. > > Maik Thanks Maik. Here comes the overall picture. My configuration: Windows: 10 Pro / 21H2 / Build 19044.1806 / Region Germany / Format German / Date Time: ISO 8601: -MM-DD hh:mm:ss Digikam: 7.7.0 since 2022-07-08 (until version 7.6 the insertion of GPX data worked) GPX data: Garmin Oregon 600, alternatively 'GPS Logging App'@Android12 When installing digikam 7.7.0 I got a hint about changed code page: 'Old locale: System, new locale: windows-1252' (attachment, page 1). I did not understand what is meant by this and what to do. My Windows is installed as usual. When trying to add coordinates to photos using GPX data, the message came up "Correlation failed - No image could be correlated - please make sure time zone and time difference settings are correct." My understanding is that everything is set correctly in Windows. However, if digikam is meant, I don't know where to look. -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 456563] When editing splits, grid row height truncates the text
https://bugs.kde.org/show_bug.cgi?id=456563 --- Comment #1 from Thomas Baumgart --- You may want to take a look at SplitDelegate::sizeHint() and its counterpart JournalDelegate::sizeHint() if you can find any obvious problem and make it work on MacOS (i.e. all platforms) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 405981] plasmashell locks up randomly when attempting to save Spectacle screenshots
https://bugs.kde.org/show_bug.cgi?id=405981 A. Wilcox (awilfox) changed: What|Removed |Added Resolution|WAITINGFORINFO |UPSTREAM Status|NEEDSINFO |RESOLVED --- Comment #8 from A. Wilcox (awilfox) --- The computer I experienced this on no longer has a graphics card, so I'm unable to try this out on a newer Plasma release. However, I don't recall having this issue on 5.18 LTS. In addition to this report being filed against 5.12 LTS… I can't say for sure this was an upstream issue, but musl libc's memory allocator was fully rewritten since then (as malloc-ng) which I know solved some other issues like this. Additionally, Qt 5.15 may have solved some issues (this was back in the relatively dark days of 5.9 LTS). I'm satisfied with closing this as RESO UP for now; if I run into this again, I'll reopen. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 454856] `ctrl` modifier not reset even after the key has been released.
https://bugs.kde.org/show_bug.cgi?id=454856 Bug Janitor Service changed: What|Removed |Added Ever confirmed|1 |0 Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |REPORTED --- Comment #4 from Bug Janitor Service --- Thanks for your comment! Automatically switching the status of this bug to REPORTED so that the KDE team knows that the bug is ready to get confirmed. In the future you may also do this yourself when providing needed information. -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 455027] Latte-dock crash
https://bugs.kde.org/show_bug.cgi?id=455027 Bug Janitor Service changed: What|Removed |Added Resolution|WAITINGFORINFO |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.
[kmymoney] [Bug 454905] CertCreateCertificateContext not found in libQt5Network.dll
https://bugs.kde.org/show_bug.cgi?id=454905 --- Comment #11 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.
[plasmashell] [Bug 413862] Panel will not go into auto hide mode
https://bugs.kde.org/show_bug.cgi?id=413862 --- 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.
[kdenlive] [Bug 443516] Scene split does nothing
https://bugs.kde.org/show_bug.cgi?id=443516 --- 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.
[lattedock] [Bug 456575] New: Top bar disappears in other virtual desktops
https://bugs.kde.org/show_bug.cgi?id=456575 Bug ID: 456575 Summary: Top bar disappears in other virtual desktops Product: lattedock Version: git (master) Platform: Manjaro OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: application Assignee: mvourla...@gmail.com Reporter: tale...@gmail.com Target Milestone: --- Created attachment 150531 --> https://bugs.kde.org/attachment.cgi?id=150531&action=edit Video demonstrating that the bar does not appear in other environments. SUMMARY *** If you place a top bar with 100% length, Justified and have more workspaces active, the top bar will only appear on the first one. This happens randomly, if you keep restarting the latte several times, it will work at some point, but it's random, most of the time it doesn't work. *** STEPS TO REPRODUCE 1. Edit the top bar, on the "Behavior" tab, "Justified" alignment. 2. Add the systray in the top bar 3. Change desktop. OBSERVED RESULT The top bar disappears in other workspaces. EXPECTED OUTCOME Keep the top bar on all desktops. SOFTWARE/OS VERSIONS Linux, Manjaro Plasma Linux/KDE: 5.24.5 (available at About System) KDE Plasma Version: 5.24.5 KDE Frameworks Version: 5.95.0 Qt Version: 5.15.5 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 456574] New: System Settings - Desktop Effects - Missing scrollbar
https://bugs.kde.org/show_bug.cgi?id=456574 Bug ID: 456574 Summary: System Settings - Desktop Effects - Missing scrollbar Product: systemsettings Version: 5.25.2 Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: kcm_kwin_effects Assignee: kwin-bugs-n...@kde.org Reporter: polarathene-sig...@hotmail.com CC: plasma-b...@kde.org Target Milestone: --- SUMMARY Without one it is a bit tedious to navigate, especially when you want to toggle an effect or modify settings at the bottom of the list. This issue seems similar to a previous one, however the package qqc2-desktop-style is installed, something else has changed since: https://bugs.kde.org/show_bug.cgi?id=406182 STEPS TO REPRODUCE 1. Open System Settings, navigate to Desktop Effects. OBSERVED RESULT No scroll bar available. EXPECTED RESULT A scroll bar should be present. SOFTWARE/OS VERSIONS Tested via VMware and QEMU-KVM VM guests with 3D accel enabled: Operating System: openSUSE Tumbleweed 20220708 (Krypton, daily build of KDE git) KDE Plasma Version: 5.25.80 KDE Frameworks Version: 5.97.0 Qt Version: 5.15.5 Kernel Version: 5.18.9 Graphics Platform: X11 + Wayland Extra: xorg: 21.1.3, xwayland 22.1.2, mesa 22.1.3 SVGA3D => vmwgfx 2.20.0 (VMware guest) virgl => virtio_gpu (QEMU-KVM guest) Operating System: EndeavourOS (ArchLinux based, fresh and updated install) KDE Plasma Version: 5.25.2 KDE Frameworks Version: 5.95.0 Qt Version: 5.15.5 Kernel Version: 5.18.10 Graphics Platform: X11 + Wayland Extra: xorg: 21.1.3, xwayland 22.1.2, mesa 22.1.3 SVGA3D => vmwgfx 2.20.0 (VMware guest) virgl => virtio_gpu (QEMU-KVM guest) -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 456573] New: Ability to identify payee with no transactions
https://bugs.kde.org/show_bug.cgi?id=456573 Bug ID: 456573 Summary: Ability to identify payee with no transactions Product: kmymoney Version: unspecified Platform: Other OS: Other Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kmymoney-de...@kde.org Reporter: spill...@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 *** Home->Payee currently display all the Payees. Need an ability to filter payees without transactions. STEPS TO REPRODUCE 1. From home page click on the Payee on the sidebar 2. 3. OBSERVED RESULT All the payee are listed without any filter of their number of transactions EXPECTED RESULT Provide ability to filter the payees with/without transactions SOFTWARE/OS VERSIONS Windows: Windows 11 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 456572] New: KWin effects Overview and Present Windows poor contrast with underlay
https://bugs.kde.org/show_bug.cgi?id=456572 Bug ID: 456572 Summary: KWin effects Overview and Present Windows poor contrast with underlay Product: kwin Version: 5.25.2 Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: effects-overview Assignee: kwin-bugs-n...@kde.org Reporter: polarathene-sig...@hotmail.com Target Milestone: --- SUMMARY This may be dependent upon the theme, but looked unpleasant in both default Breeze and a third-party dark theme. For the dark theme, the underlay almost blended in with the window colours. STEPS TO REPRODUCE 1. Enable and toggle each of the effects. 2. "Overview" and "Present Windows" should have underlays that can look washed out, and the latter cannot remove or adjust blur (blur effect settings don't seem to have any effect to it). OBSERVED RESULT Washed out underlay provides poor contrast to windows shown, even with a dark background. Especially with a dark theme. EXPECTED RESULT No underlay, or control over colour/opacity or contrast so that windows shown stand out better. SOFTWARE/OS VERSIONS Tested via VMware and QEMU-KVM VM guests with 3D accel enabled: Operating System: openSUSE Tumbleweed 20220708 (Krypton, daily build of KDE git) KDE Plasma Version: 5.25.80 KDE Frameworks Version: 5.97.0 Qt Version: 5.15.5 Kernel Version: 5.18.9 Graphics Platform: X11 + Wayland Extra: xorg: 21.1.3, xwayland 22.1.2, mesa 22.1.3 SVGA3D => vmwgfx 2.20.0 (VMware guest) virgl => virtio_gpu (QEMU-KVM guest) Operating System: EndeavourOS (ArchLinux based, fresh and updated install) KDE Plasma Version: 5.25.2 KDE Frameworks Version: 5.95.0 Qt Version: 5.15.5 Kernel Version: 5.18.10 Graphics Platform: X11 + Wayland Extra: xorg: 21.1.3, xwayland 22.1.2, mesa 22.1.3 SVGA3D => vmwgfx 2.20.0 (VMware guest) virgl => virtio_gpu (QEMU-KVM guest) ADDITIONAL INFORMATION Only "Overview" effect provides an option to disable blur (which does not affect "Present Windows" that lacks this option). I mention that so that both effects settings can be resolved. The related effect "Desktop Grid" behaves a bit differently (if only 1 virtual desktop), by omitting any underlay. There's a bit of disparity between UI elements (virtual desktop add/remove, search) between the effects. In earlier releases, I remember "Present Windows" having a dark contrasting underlay. Now I am given the impression it is tied to the theme/color scheme, but not obvious as to a user what to change / look for to adjust (or if that will affect other parts of UI visuals negatively in doing so). I'd be happy with no underlay at all vs the current experience that gets in the way with a washed out look, even when the background/wallpaper is quite dark and contrasting, the underlay is far brighter. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 451698] Actually applied accent color is not the exact color you chose in the UI
https://bugs.kde.org/show_bug.cgi?id=451698 Brennan Kinney changed: What|Removed |Added CC||polarathene-signup@hotmail. ||com --- Comment #10 from Brennan Kinney --- Chiming in as I think this is what I've just noticed when testing latest daily build of openSUSE Krypton. "Use accent color" results in different appearance between "From current color scheme" and "Custom", despite providing the same colour value. I am not familiar with the color scheme or accent feature. Playing around with editing a color scheme, it seemed the "Selection Color" was mapped to the accent used by the scheme, and the contrast slider in the options tab made no difference. I liked the brighter accent from the scheme, but when text was involved (white text in a dark theme), the text was not readable. I was hoping the contrast slider would have helped with that. When using "Custom" for accent source instead, the dimmed accent was much better for readability (file selected in Dolphin). --- I also noticed in the systray "Audio Volume" applet that the tabs used the color scheme "Hover Decoration". That colour change would not be visible until I changed back to "Custom" accent, applied, and back to "From current color scheme", or by changing the "Selection" colour in the scheme also would update the colour used in the applet tab.. I guess it relied on the accent colour being adjusted as other settings did not seem to make a difference at updating the visual. When "Custom" is used for the accent, it would override the "Hover Decoration" from the colour scheme, it seems to be the colour value assigned to "Custom" without any alterations, while the applets sliders beneath the "Devices" tab have the dulled accent (testing with a bright red). I guess "Custom" accent overrides multiple colors from the scheme this way? Or the other way around, and the "From current color scheme" replaces the accent with a variety of sources? As a user who's not strayed from the defaults before, it's unclear to me what is overriding the other, and what values in a color scheme map to the accents "Custom" affects. --- While the accent adjustments for contrast with "Custom" seem to be otherwise good for readability, I get the impression there is a consistency issue. Not only is the "Selection" colour used from the scheme as an accent, with "Custom" adjusting the value, "Custom" is also applying the accent chosen on other colours from the scheme that were a different colour. It's a very different experience between the two for me. My expectation was that "Use accent color" selects a source for the accent, not to modify it or override other colours from the scheme too. That sounds like a different setting that provides dynamic contrast (nice), and overrides (vague, possibly some visual/contextual hierarchy?) -- You are receiving this mail because: You are watching all bug changes.
[frameworks-solid] [Bug 456571] New: Plasma stopped mounting my attached device On Login
https://bugs.kde.org/show_bug.cgi?id=456571 Bug ID: 456571 Summary: Plasma stopped mounting my attached device On Login Product: frameworks-solid Version: 5.94.0 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: lu...@kde.org Reporter: skierp...@gmail.com CC: kdelibs-b...@kde.org Target Milestone: --- SUMMARY When I installed Fedora 36 KDE spin, instead of adding my Windows NTFS drive to /etc/fstab, in System Settings > Removable Devices > Attached Devices I checked "On Login" for that drive (as I recall, to enable the per-drive checkboxes I first had to uncheck "All Known Devices - On Login" and "All Known Devices - On Attach"). After this, upon logging into Plasma, I got a prompt (as I recall "Authentical Required - PolicyKit Authentication is required to mount...") and Plasma/KDE/Solid mounts the drive. This worked, until a Fedora package update sometime around a week or so ago. Now Plasma never mounts my Windows drive on reboot or logging out and back in. The checkmark's tooltip is quite specific "This device will be automatically mounted at login", but it ain't happening. STEPS TO REPRODUCE 1. Have an attached drive not in /etc/fstab. 2. In System Settings > Removable Devices > Attached Devices, check "On Login" for that drive 3. Reboot. OBSERVED RESULT On latest Fedora/KDE the drive isn't mounted. There's no prompt for password. EXPECTED RESULT At some point in booting into Plasma, the drive is mounted. SOFTWARE/OS VERSIONS Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.25.2 KDE Frameworks Version: 5.94.0 Qt Version: 5.15.3 on Wayland Kernel Version: 5.18.10-200.fc36.x86_64 (64-bit) ADDITIONAL INFORMATION One workaround to manually mount the partition is to enter in a terminal like Konsole the command line `udisksctl mount -b /dev/sda3` where /dev/sda3 is the device of the attached drive. I didn't find anything relevant in journalctl. Is there any relevant logging to turn on? I think Plasma - Solid - kded - udisks talk to each other through DBUS. KDE's defaults for automount behavior changed recently. The merge ttps://invent.kde.org/plasma/plasma-desktop/-/merge_requests/974 in response to https://invent.kde.org/plasma/plasma-desktop/-/merge_requests/549#note_436564 seem relevant. FWIW, my ~/.config/kded_device_automounterrc contains: [Devices][/org/freedesktop/UDisks2/block_devices/sda3] EverMounted=true ForceLoginAutomount=true Icon=drive-harddisk LastNameSeen=Windows LastSeenMounted=true ... [General] AutomountEnabled=true AutomountOnLogin=false AutomountOnPlugin=false -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 456570] "Run current document" fails if path contains spaces
https://bugs.kde.org/show_bug.cgi?id=456570 mittbrukern...@protonmail.com changed: What|Removed |Added Attachment #150528|pyhton with shebang |python with shebang description|| -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 456570] "Run current document" fails if path contains spaces
https://bugs.kde.org/show_bug.cgi?id=456570 mittbrukern...@protonmail.com changed: What|Removed |Added Attachment #150530|Using .sh and no shebang|.sh without shebang description|| -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 456570] "Run current document" fails if path contains spaces
https://bugs.kde.org/show_bug.cgi?id=456570 mittbrukern...@protonmail.com changed: What|Removed |Added Attachment #150528|Screenshot of kate's|pyhton with shebang description|terminal output | -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 456570] "Run current document" fails if path contains spaces
https://bugs.kde.org/show_bug.cgi?id=456570 mittbrukern...@protonmail.com changed: What|Removed |Added Attachment #150530|Using sh extension and no |Using .sh and no shebang description|shebang | -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 456570] "Run current document" fails if path contains spaces
https://bugs.kde.org/show_bug.cgi?id=456570 --- Comment #1 from mittbrukern...@protonmail.com --- Created attachment 150530 --> https://bugs.kde.org/attachment.cgi?id=150530&action=edit Using sh extension and no shebang -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 456569] External monitor goes black when video player is fullscreen
https://bugs.kde.org/show_bug.cgi?id=456569 Danilo changed: What|Removed |Added Attachment #150526|0 |1 is obsolete|| --- Comment #2 from Danilo --- Created attachment 150529 --> https://bugs.kde.org/attachment.cgi?id=150529&action=edit kwin logs and drm logs -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 456570] "Run current document" fails if path contains spaces
https://bugs.kde.org/show_bug.cgi?id=456570 mittbrukern...@protonmail.com changed: What|Removed |Added Keywords||usability -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 456570] New: "Run current document" fails if path contains spaces
https://bugs.kde.org/show_bug.cgi?id=456570 Bug ID: 456570 Summary: "Run current document" fails if path contains spaces Product: kate Version: 22.04.2 Platform: Manjaro OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kwrite-bugs-n...@kde.org Reporter: mittbrukern...@protonmail.com Target Milestone: --- Created attachment 150528 --> https://bugs.kde.org/attachment.cgi?id=150528&action=edit Screenshot of kate's terminal output STEPS TO REPRODUCE 1. create a directory containing a space 2. create any executable file inside it 3. tools>Run Current Document OBSERVED RESULT Kate's console-module outputs that the path is not valid and displays space-broken filepath SOFTWARE/OS VERSIONS Manjaro Ruah 21.3.2 Plasma vers.: 5.24.5 Qt vers.: 5.15.5 ADDITIONAL INFORMATION Sorry if this is a duplicate, it is basically the same as this: https://bugs.kde.org/show_bug.cgi?id=443618 It's no real biggie since copy file path and pasting works just fine. Anyways: Thank you for a wonderful editor, all your hard work and valuable contributions to the linux ecosystem! -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 455080] Maliit virtual keyboard fails to activate when an input field is focused
https://bugs.kde.org/show_bug.cgi?id=455080 --- Comment #13 from Aleix Pol --- QT_IM_MODULE should be unset at all times. Make sure that you have maliit selected in the Virtual Keyboard KCM. I see you mentioned you're running Fedora, there's some mechanisms there to inject some environment variables that override Plasma's default settings to make it accessible to ibus and would break maliit usage. Please reach out to them to address this, For reference: https://pagure.io/fedora-kde/SIG/issue/220 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 455080] Maliit virtual keyboard fails to activate when an input field is focused
https://bugs.kde.org/show_bug.cgi?id=455080 --- Comment #12 from Aleix Pol --- Created attachment 150527 --> https://bugs.kde.org/attachment.cgi?id=150527&action=edit maliit selected -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 456569] External monitor goes black when video player is fullscreen
https://bugs.kde.org/show_bug.cgi?id=456569 Zamundaaa changed: What|Removed |Added CC||xaver.h...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 456569] External monitor goes black when video player is fullscreen
https://bugs.kde.org/show_bug.cgi?id=456569
--- Comment #1 from Danilo ---
Comment on attachment 150526
--> https://bugs.kde.org/attachment.cgi?id=150526
Output of journalctl --boot 0 | grep kwin_wayland
>Jul 10 16:36:36 artemis kwin_wayland_wrapper[877]: No backend specified
>through command line argument, trying auto resolution
>Jul 10 16:36:37 artemis kwin_wayland_wrapper[877]: OpenGL vendor string:
>AMD
>Jul 10 16:36:37 artemis kwin_wayland_wrapper[877]: OpenGL renderer string:
>AMD RENOIR (LLVM 14.0.6, DRM 3.42, 5.15.53-2-lts)
>Jul 10 16:36:37 artemis kwin_wayland_wrapper[877]: OpenGL version string:
>4.6 (Core Profile) Mesa 22.1.3
>Jul 10 16:36:37 artemis kwin_wayland_wrapper[877]: OpenGL shading language
>version string: 4.60
>Jul 10 16:36:37 artemis kwin_wayland_wrapper[877]: Driver:
>RadeonSI
>Jul 10 16:36:37 artemis kwin_wayland_wrapper[877]: GPU class:
>Vega
>Jul 10 16:36:37 artemis kwin_wayland_wrapper[877]: OpenGL version:
>4.6
>Jul 10 16:36:37 artemis kwin_wayland_wrapper[877]: GLSL version:
>4.60
>Jul 10 16:36:37 artemis kwin_wayland_wrapper[877]: Mesa version:
>22.1.3
>Jul 10 16:36:37 artemis kwin_wayland_wrapper[877]: Linux kernel version:
>5.15.53
>Jul 10 16:36:37 artemis kwin_wayland_wrapper[877]: Requires strict binding:
>no
>Jul 10 16:36:37 artemis kwin_wayland_wrapper[877]: GLSL shaders:
>yes
>Jul 10 16:36:37 artemis kwin_wayland_wrapper[877]: Texture NPOT support:
>yes
>Jul 10 16:36:37 artemis kwin_wayland_wrapper[877]: Virtual Machine:
>no
>Jul 10 16:36:37 artemis kwin_wayland[877]: kwin_xkbcommon: XKB: inet:323:58:
>unrecognized keysym "XF86EmojiPicker"
>Jul 10 16:36:37 artemis kwin_wayland[877]: kwin_xkbcommon: XKB: inet:324:58:
>unrecognized keysym "XF86Dictate"
>Jul 10 16:36:37 artemis kwin_wayland_wrapper[909]: (WW) Option "-listen" for
>file descriptors is deprecated
>Jul 10 16:36:37 artemis kwin_wayland_wrapper[909]: Please use "-listenfd"
>instead.
>Jul 10 16:36:37 artemis kwin_wayland_wrapper[909]: (WW) Option "-listen" for
>file descriptors is deprecated
>Jul 10 16:36:37 artemis kwin_wayland_wrapper[909]: Please use "-listenfd"
>instead.
>Jul 10 16:36:37 artemis kwin_wayland_wrapper[962]: The XKEYBOARD keymap
>compiler (xkbcomp) reports:
>Jul 10 16:36:37 artemis kwin_wayland_wrapper[962]: > Warning:
>Unsupported maximum keycode 708, clipping.
>Jul 10 16:36:37 artemis kwin_wayland_wrapper[962]: > X11
>cannot support keycodes above 255.
>Jul 10 16:36:37 artemis kwin_wayland_wrapper[962]: Errors from xkbcomp are not
>fatal to the X server
>Jul 10 16:38:38 artemis kwin_wayland[877]: This plugin does not support raise()
>Jul 10 16:38:51 artemis kwin_wayland[877]: This plugin does not support raise()
>Jul 10 17:12:20 artemis kwin_wayland[877]: kwin_core: Could not find window
>with uuid "{05873055-23ba-43b5-9c5c-48c6b580b630}"
>Jul 10 17:12:20 artemis kwin_wayland[877]: kwin_core: Could not find window
>with uuid "{05873055-23ba-43b5-9c5c-48c6b580b630}"
>Jul 10 17:12:20 artemis kwin_wayland[877]: kwin_core: Could not find window
>with uuid "{05873055-23ba-43b5-9c5c-48c6b580b630}"
>Jul 10 17:12:40 artemis kwin_wayland[877]: kwin_libinput: Libinput: event8 -
>BY Tech Gaming Keyboard: client bug: event processing lagging behind by 37ms,
>your system is too slow
>Jul 10 17:13:08 artemis kwin_wayland[877]: QMetaProperty::read: Unable to
>handle unregistered datatype 'KWin::SessionState' for property
>'KWin::EffectsHandlerImpl::sessionState'
>Jul 10 17:13:26 artemis kwin_wayland[877]: This plugin does not support raise()
>Jul 10 17:13:26 artemis kwin_wayland[877]: This plugin does not support raise()
>Jul 10 17:15:40 artemis kwin_wayland[877]: kwin_libinput: Libinput: event8 -
>BY Tech Gaming Keyboard: client bug: event processing lagging behind by 42ms,
>your system is too slow
>Jul 10 17:16:45 artemis kwin_wayland[877]: kwin_libinput: Libinput: event8 -
>BY Tech Gaming Keyboard: client bug: event processing lagging behind by 42ms,
>your system is too slow
>Jul 10 17:28:00 artemis kwin_wayland[877]: kwin_core: Could not find window
>with uuid "{21eacee4-db47-448e-8af9-5d4709805fcb}"
>Jul 10 17:28:00 artemis kwin_wayland[877]: kwin_core: Could not find window
>with uuid "{21eacee4-db47-448e-8af9-5d4709805fcb}"
>Jul 10 17:28:00 artemis kwin_wayland[877]: kwin_core: Could not find window
>with uuid "{21eacee4-db47-448e-8af9-5d4709805fcb}"
>Jul 10 17:49:56 artemis kwin_wayland[877]: QMetaProperty::read: Unable to
>handle unregistered datatype 'KWin::SessionState' for property
>'KWin::EffectsHandlerImpl::sessionState'
>Jul 10 17:49:56 artemis kwin_wayland[877]: QMetaProperty::read: Unable to
>handle unregistered datatype 'KWin::Se
[kwin] [Bug 456569] New: External monitor goes black when video player is fullscreen
https://bugs.kde.org/show_bug.cgi?id=456569 Bug ID: 456569 Summary: External monitor goes black when video player is fullscreen Product: kwin Version: 5.25.2 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: danilo@tutanota.com Target Milestone: --- Created attachment 150526 --> https://bugs.kde.org/attachment.cgi?id=150526&action=edit Output of journalctl --boot 0 | grep kwin_wayland STEPS TO REPRODUCE 1. Open VLC in external monitor (also happens with Celluloid, Haruna, Kodi...) 2. Open a video file 3. Make it fullscreen OBSERVED RESULT When the menu with the progress bar disappears, the external monitor's screen goes black for a couple of seconds. Move the mouse, the progress bar comes back normally. The screen will continue to go black every time the menu with the progress bar disappears. EXPECTED RESULT Monitor screen keeps on, displaying the video. SOFTWARE/OS VERSIONS Linux: 5.15.53-2-lts (available in About System) KDE Plasma Version: 5.25.2 KDE Frameworks Version: 5.96.0 Qt Version: 5.15.5 ADDITIONAL INFORMATION Here's a reddit post where I've attached a video showing the bug: https://www.reddit.com/r/kde/comments/vunmtk/external_monitor_goes_black_when_video_player_is/ -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 456568] Keystrokes don't exist to apply some settings.
https://bugs.kde.org/show_bug.cgi?id=456568 David Chmelik changed: What|Removed |Added OS|All |Linux -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 456568] Keystrokes don't exist to apply some settings.
https://bugs.kde.org/show_bug.cgi?id=456568 David Chmelik changed: What|Removed |Added OS|Linux |All -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 456568] New: Keystrokes don't exist to apply some settings.
https://bugs.kde.org/show_bug.cgi?id=456568
Bug ID: 456568
Summary: Keystrokes don't exist to apply some settings.
Product: systemsettings
Version: 5.25.2
Platform: Other
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: general
Assignee: plasma-b...@kde.org
Reporter: dchme...@gmail.com
Target Milestone: ---
SUMMARY
Keystrokes don't exist to apply some settings.
STEPS TO REPRODUCE
1. Run systemsettings.
2. Go to settings such as appearance: global theme (possibly/probably others:
check all.)
3. Look for underlined letter to do keystroke (can't see any.)
OBSERVED RESULT
Keystrokes don't exist to apply some settings: global theme no longer has
standard underlined letter buttons indicating keystrokes to
'apply' nor 'cancel' (though ) cancels) etc: mouse usage forced (if
works.)
EXPECTED RESULT
Allow & process consistent standard underlined-letter button keystrokes
('apply' usually being a or sometimes p, l, or y but should
be same/standardized/consistent for all cases (no menu uses those letters for
other buttons) and include keystrokes for 'cancel' and all systemsettings
buttons.) Don't assume touchscreen-only (no keyboard) PC!
SOFTWARE/OS VERSIONS
Linux/KDE Plasma: KDE Neon User 5.25.2 (up-to-date,) Slackware64 15.1-current
(up-to-date ) / 5.25.2
KDE Plasma Version: 5.25.2
KDE Frameworks Version: 5.95.0
Qt Version: 5.15.5 (Neon,) 5.15.4 (Slackware)
--
You are receiving this mail because:
You are watching all bug changes.
[kwin] [Bug 455080] Maliit virtual keyboard fails to activate when an input field is focused
https://bugs.kde.org/show_bug.cgi?id=455080 old486wh...@gmail.com changed: What|Removed |Added CC||old486wh...@gmail.com --- Comment #11 from old486wh...@gmail.com --- So I'm in a similar boat. Fedora 36 (wayland + KWIN used) KDE Plasma 5.25.2 Framework 5.94 QT version 5.15.3 I find it amazing that no-one from KDE seems to care that an accessibility requirement like a virtual keyboard is not working. Alex - could you try checking your environment variables on a "konsole" (type the following - without quotes - "set |grep MODULE"). Also, on that same window, try typing (again no quotes): "QT_IM_MODULE=qtvirtualkeyboard kwrite" On mine, I get an error message and the "maliit" keyboard flashes up. The error is: "qt.qpa.wayland: qtvirtualkeyboard currently is not supported at client-side, use QT_IM_MODULE=qtvirtualkeyboard at compositor-side." I suspect that because "ibus" is set then the virtual keyboard isn't appearing. Which is silly isn't it? ibus is purposely built to use an input method mechanism, while force-setting it to ONLY virtualkeyboard is wrong for things where you can plug in keyboards, or 2-in-1 laptops where the keyboard folds away. Even worse - where can I set the IM module variable on the compositor-side? do I have to manually edit the "kwinrc" file? Other files? I will try to take this further myself, but why is the virtual keyboard not showing in ALL situations where it's enabled!? This is just bad user experience! -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 456567] The WiFi QR is not displayed well on HD or lower screens
https://bugs.kde.org/show_bug.cgi?id=456567 --- Comment #1 from Andrus Diaz --- Created attachment 150525 --> https://bugs.kde.org/attachment.cgi?id=150525&action=edit A screenshot of what the problem looks like This screenshot is from my laptop with a wayland session and a screen (1366x768) -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 456567] The WiFi QR is not displayed well on HD or lower screens
https://bugs.kde.org/show_bug.cgi?id=456567 Andrus Diaz changed: What|Removed |Added Keywords||wayland CC||andrusdiazale...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 448995] some systemsettings options don't apply (though keystroke changes button appearance) until new tab selected then press popup's 'apply'
https://bugs.kde.org/show_bug.cgi?id=448995 --- Comment #11 from David Chmelik --- I did NOT report duplicate issues--reread the title: this always only was about the keystroke doesn't 'apply' the button, though apparently is duplicate of bug 440255. -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 456567] New: The WiFi QR is not displayed well on HD or lower screens
https://bugs.kde.org/show_bug.cgi?id=456567 Bug ID: 456567 Summary: The WiFi QR is not displayed well on HD or lower screens Product: plasma-nm Version: 5.24.5 Platform: Manjaro OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: applet Assignee: jgrul...@redhat.com Reporter: andrusdiazale...@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. Open the network applet bar 2. Right click on a Wi-Fi connection 3. Click on view QR connection OBSERVED RESULT I see an incomplete QR because it is below the applet, which makes it impossible for me to scan it EXPECTED RESULT I hope that this 'QR' is above the applet, or that the applet is automatically hidden when generating a QR SOFTWARE/OS VERSIONS Linux/KDE Plasma: 5.15.15 / 5.24.5 (available in About System) KDE Plasma Version: 5.24.5 KDE Frameworks Version: 5.95 Qt Version: 5.15 ADDITIONAL INFORMATION This is visible on screens that do not have a large size, But on an example laptop screen (1366x768) or less this will always happen -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 396826] Kmymoney window is not drawn correctly on Wayland
https://bugs.kde.org/show_bug.cgi?id=396826 Kenneth Perry changed: What|Removed |Added CC||thothone...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[Books] [Bug 456375] Invalid link to download the book
https://bugs.kde.org/show_bug.cgi?id=456375
--- Comment #8 from David C. Bryant ---
I have been digging into the CMAKE files for project kf5book
(https://invent.kde.org/documentation/kf5book). I finally got the .pdf file to
generate using "kdesrc-build kf5book". I had to do several things to get it to
go.
-- I had to install "pandocs" and also "snippetextractor". "pandocs" is part of
my distro (Gentoo), so that was easy. "snippetextractor" is sort of obscure, so
I had to clone the source for snippetextractor, after which "qmake -o Makefile
snippetextractor.pro && make" generated the object program. I then moved the
object program from the build directory into my PATH, so it woud be usable.
-- I had to change a command line in the CMakeLists.txt file:
add_custom_command(OUTPUT KDE-Frameworks-Cookbook.pdf
COMMAND ${PANDOC} --toc --number-sections ${files} -o
KDE-Frameworks-Cookbook.pdf
--template=${CMAKE_SOURCE_DIR}/pdf-template.tex
--chapters
DEPENDS ${files} pdf-template.tex
)
The "pandocs" program no longer supports a "--chapters" option. It works OK if
"--chapters" is changed to "--top-level-division=chapter".
-- I had to add some customization to the "pdf-template.tex" file from the
repo.
(add after line 131)
\providecommand{\tightlist}{%
\setlength{\itemsep}{0pt}\setlength{\parskip}{0pt}}
because "pandocs" throws a "\tightlist" command into every itemized list it
generates, and \tightlist is not a standard LaTeX function.
-- With these changes, kdesrc-build can create an html file, and a pdf file.
The "epub" command is still not working correctly. Maybe I can get that fixed
tomorrow.
--
You are receiving this mail because:
You are watching all bug changes.
[kdenlive] [Bug 456566] Master Audio is About 5 dB Higher than the Individual Tracks
https://bugs.kde.org/show_bug.cgi?id=456566 --- Comment #1 from falloutgame...@gmail.com --- Created attachment 150524 --> https://bugs.kde.org/attachment.cgi?id=150524&action=edit Even with every Audio Track set to 0 the problem persists At first I thought maybe the Master Track might have just been the only Audio Track adjusting to my audio manipulation but after turning all volumes back to default the problem still occurs. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 456566] New: Master Audio is About 5 dB Higher than the Individual Tracks
https://bugs.kde.org/show_bug.cgi?id=456566 Bug ID: 456566 Summary: Master Audio is About 5 dB Higher than the Individual Tracks Product: kdenlive Version: 22.04.3 Platform: Microsoft Windows OS: Microsoft Windows Status: REPORTED Severity: minor Priority: NOR Component: Effects & Transitions Assignee: vpi...@kde.org Reporter: falloutgame...@gmail.com Target Milestone: --- Created attachment 150523 --> https://bugs.kde.org/attachment.cgi?id=150523&action=edit The Master Track being louder than the Audio Track of me talking despite both of the other tracks being muted SUMMARY When Using the Audio Mixer the Master Volume is Louder than the individual Audio Tracks by about 5 dB, it seems like this even follows it into the render. STEPS TO REPRODUCE Adjusting each track individually OBSERVED RESULT Master Track is louder than individual tracks even when those tracks are set to play solo. EXPECTED RESULT The Master Track to be the same volume as shown on the individual Audio Tracks SOFTWARE/OS VERSIONS Windows: 11 ADDITIONAL INFORMATION Latest version downloaded within the past week -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 443168] gwenview ignores settings in initial sort order
https://bugs.kde.org/show_bug.cgi?id=443168 Jörg <2un1yj...@sneakemail.com> changed: What|Removed |Added CC||2un1yj...@sneakemail.com -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 448447] System Settings freezes and crashes when trying to open Cursors KCM when two installed themes inherit each other
https://bugs.kde.org/show_bug.cgi?id=448447 David Edmundson changed: What|Removed |Added CC||k...@davidedmundson.co.uk --- Comment #13 from David Edmundson --- >XcursorScanTheme is outside our stack. Interestingly our code does have infinite recursion protection. But only for our own usage. Then we add it anyway and let Xcursor parse the data -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 453640] Home page Copy an amount no longer works
https://bugs.kde.org/show_bug.cgi?id=453640 --- Comment #5 from Pete --- This problem also affects Fedora 36. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 456526] Crash when switching between cursor themes
https://bugs.kde.org/show_bug.cgi?id=456526 David Edmundson changed: What|Removed |Added CC||bugsefor...@gmx.com --- Comment #2 from David Edmundson --- *** Bug 453535 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[LabPlot2] [Bug 455579] X offset of 2 hours after reopening an saved project file
https://bugs.kde.org/show_bug.cgi?id=455579 --- Comment #6 from Stefan Gerlach --- The fix is also in flatpak via patch. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 453535] System Settings crashes when I try to apply another cursor theme with double-click
https://bugs.kde.org/show_bug.cgi?id=453535 David Edmundson changed: What|Removed |Added CC||k...@davidedmundson.co.uk Resolution|--- |DUPLICATE Status|CONFIRMED |RESOLVED --- Comment #12 from David Edmundson --- I haven't reproduced it, but I saw another bug with the same timer which gave a good clue. *** This bug has been marked as a duplicate of bug 456526 *** -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 456564] Accepting an imported transaction is a low-severity action, should rather not require modal confirmation dialog
https://bugs.kde.org/show_bug.cgi?id=456564 --- Comment #1 from Jack --- I also point out that for consistency, an imported transaction is accepted by editing it or by clicking on the status column to change from not marked to confirmed, neither of which requires confirmation. -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 455735] When editing a transaction, choosing a category from the list and confirming with 'Enter' resets it back to 'Asset'
https://bugs.kde.org/show_bug.cgi?id=455735 --- Comment #5 from Dawid Wróbel --- Created attachment 150522 --> https://bugs.kde.org/attachment.cgi?id=150522&action=edit Drop-down list misbehavior So I noticed today that it happens with mouse selection at times, too, except slightly differently and only for some accounts. Even more weirdly, it can be reset by choosing another account from the list. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 456526] Crash when switching between cursor themes
https://bugs.kde.org/show_bug.cgi?id=456526 Bug Janitor Service changed: What|Removed |Added Status|REPORTED|ASSIGNED Ever confirmed|0 |1 --- Comment #1 from Bug Janitor Service --- A possibly relevant merge request was started @ https://invent.kde.org/plasma/plasma-workspace/-/merge_requests/1908 -- You are receiving this mail because: You are watching all bug changes.
[LabPlot2] [Bug 455579] X offset of 2 hours after reopening an saved project file
https://bugs.kde.org/show_bug.cgi?id=455579 Stefan Gerlach changed: What|Removed |Added Latest Commit||https://invent.kde.org/educ ||ation/labplot/commit/0d2494 ||a924fa35b4d471052f8c97e2d26 ||e2a12fc Resolution|--- |FIXED Status|CONFIRMED |RESOLVED --- Comment #5 from Stefan Gerlach --- Git commit 0d2494a924fa35b4d471052f8c97e2d26e2a12fc by Stefan Gerlach. Committed on 10/07/2022 at 22:03. Pushed by sgerlach into branch 'master'. Consistently use date time in UTC to avoid confusion with locale date time settings M +4-4src/backend/lib/Range.h M +5-2src/backend/worksheet/plots/cartesian/Axis.cpp M +14 -14 src/backend/worksheet/plots/cartesian/CartesianPlot.cpp M +5-0src/backend/worksheet/plots/cartesian/XYCurve.cpp M +20 -16 src/kdefrontend/dockwidgets/CartesianPlotDock.cpp https://invent.kde.org/education/labplot/commit/0d2494a924fa35b4d471052f8c97e2d26e2a12fc -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 456565] New: Category autocomplete should focus on the parent, if child account also matches
https://bugs.kde.org/show_bug.cgi?id=456565 Bug ID: 456565 Summary: Category autocomplete should focus on the parent, if child account also matches Product: kmymoney Version: git (master) Platform: Other OS: Other Status: REPORTED Severity: wishlist Priority: NOR Component: ux-ui Assignee: kmymoney-de...@kde.org Reporter: m...@dawidwrobel.com Target Milestone: --- SUMMARY When more than one account in a branch matches the typed-in search term, the autocomplete should stop at the first matching parent account, not the leaf. The rationale here is that the child account is a more specific account of the generic parent, and as such, there can be many more such leafs under said parent. We should assume the generic account is likely to be chosen more frequently. In my example, I use that for denoting same categories of different currencies, but the parent account is always of my main currency, which indeed means I am more likely to assign a category to it, as I usually spend in that currency. Alternatively, a more sophisticated logic would preselect an account that matches the transaction's currency — and maybe even mark the other with an appropriate icon, to warn that currency conversion would be required. STEPS TO REPRODUCE 1. Create category hierarchy, where two accounts, a parent and a leaf, have the same name, but the leaf also bears and additional suffix 2. In transaction editing dialog, type in the account name such that both are shown OBSERVED RESULT The leaf is automatically selected, even though the parent account also matches. EXPECTED RESULT The parent account should be preselected. 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.
[NeoChat] [Bug 456554] Room list footer and chatbar different heights
https://bugs.kde.org/show_bug.cgi?id=456554 Tobias Fella changed: What|Removed |Added Status|REPORTED|CONFIRMED Ever confirmed|0 |1 -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 456564] New: Accepting an imported transaction is a low-severity action, should rather not require modal confirmation dialog
https://bugs.kde.org/show_bug.cgi?id=456564 Bug ID: 456564 Summary: Accepting an imported transaction is a low-severity action, should rather not require modal confirmation dialog Product: kmymoney Version: git (master) Platform: Other OS: Other Status: REPORTED Severity: normal Priority: NOR Component: ux-ui Assignee: kmymoney-de...@kde.org Reporter: m...@dawidwrobel.com Target Milestone: --- SUMMARY Accepting an imported transaction is a low-severity action, should rather not require modal confirmation dialog. The action can be reverted and by itself does not edit the content of the transaction, outside of changing its flag. STEPS TO REPRODUCE 1. Accept an imported transaction OBSERVED RESULT A modal dialog is shown asking to confirm the action EXPECTED RESULT Action should be accepted immediately. If needed, it can be reverted either by "Undoing" the action, or by switching its "Imported" flag back on with Transaction -> Mark Transaction As... -> Imported (which currently is *not* one of the items listed there) -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 456363] App crashes when hitting "OK" in Split Edit dialog
https://bugs.kde.org/show_bug.cgi?id=456363 Dawid Wróbel changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED --- Comment #1 from Dawid Wróbel --- Fixed in master -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 454856] `ctrl` modifier not reset even after the key has been released.
https://bugs.kde.org/show_bug.cgi?id=454856 --- Comment #3 from levi.duncan.s...@gmail.com --- I am very sorry for such a late response. I have built Krita with my system's Qt. Unfortunately I do not currently have access to my main (Linux) PC, and thus have no way of verifying the fix. I will check the nightly builds as soon as I'll have an opportunity. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 454600] PWA on wayland don't get their own window icon in the taskbar
https://bugs.kde.org/show_bug.cgi?id=454600 Komorebi changed: What|Removed |Added CC||markovs.i.m...@gmail.com --- Comment #3 from Komorebi --- Well, I'm using 5.25.2 and the issue still persists. -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 456563] New: When editing splits, grid row height truncates the text
https://bugs.kde.org/show_bug.cgi?id=456563 Bug ID: 456563 Summary: When editing splits, grid row height truncates the text Product: kmymoney Version: git (master) Platform: macOS (DMG) OS: Other Status: REPORTED Severity: normal Priority: NOR Component: ux-ui Assignee: kmymoney-de...@kde.org Reporter: m...@dawidwrobel.com Target Milestone: --- Created attachment 150521 --> https://bugs.kde.org/attachment.cgi?id=150521&action=edit The truncated text in split editor Likely specific to macOS, and specific to Qt. See screenshot for details. -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 456548] Screenshot contains ghost image of the spectacle because of close/hide window animation on kwin
https://bugs.kde.org/show_bug.cgi?id=456548 Ömer Fadıl USTA changed: What|Removed |Added Status|REPORTED|CONFIRMED Ever confirmed|0 |1 --- Comment #1 from Ömer Fadıl USTA --- I can confirm this bug with git version on wayland too -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 456548] Screenshot contains ghost image of the spectacle because of close/hide window animation on kwin
https://bugs.kde.org/show_bug.cgi?id=456548 Ömer Fadıl USTA changed: What|Removed |Added CC||omeru...@gmail.com Summary|Screenshot problem |Screenshot contains ghost ||image of the spectacle ||because of close/hide ||window animation on kwin -- You are receiving this mail because: You are watching all bug changes.
[KDE Itinerary] [Bug 456510] Ticket documents not available
https://bugs.kde.org/show_bug.cgi?id=456510 Bug Janitor Service changed: What|Removed |Added Ever confirmed|0 |1 Status|REPORTED|ASSIGNED --- Comment #2 from Bug Janitor Service --- A possibly relevant merge request was started @ https://invent.kde.org/pim/itinerary/-/merge_requests/79 -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 423191] kate does not remember position and size on 2nd monitor
https://bugs.kde.org/show_bug.cgi?id=423191 --- Comment #17 from slartibar...@gmail.com --- any updates on this? i tested with wayland and a current kde version 5.25.2, frameworks 5.96, qt 5.15.3 Neither on x11 nor in wayland is the kate editor behaving properly (in comparison to kwrite, there it works surprisingly well) -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 456467] fullscreen window on the wrong screen
https://bugs.kde.org/show_bug.cgi?id=456467 --- Comment #2 from bibitocar...@gmail.com --- Created attachment 150520 --> https://bugs.kde.org/attachment.cgi?id=150520&action=edit screenshot screenshot -- You are receiving this mail because: You are watching all bug changes.
[frameworks-knewstuff] [Bug 425819] Margin in close button is not consistent
https://bugs.kde.org/show_bug.cgi?id=425819 Alexander Lohnau changed: What|Removed |Added Assignee|jpwhit...@kde.org |alexander.loh...@gmx.de -- You are receiving this mail because: You are watching all bug changes.
[frameworks-knewstuff] [Bug 425819] Margin in close button is not consistent
https://bugs.kde.org/show_bug.cgi?id=425819 Alexander Lohnau changed: What|Removed |Added CC||alexander.loh...@gmx.de Status|CONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #1 from Alexander Lohnau --- This was "fixed" by removing the button -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 456562] New: Searching for files in application launchers fails
https://bugs.kde.org/show_bug.cgi?id=456562 Bug ID: 456562 Summary: Searching for files in application launchers fails Product: krunner Version: 5.25.2 Platform: Manjaro OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: alexander.loh...@gmx.de Reporter: smowten...@protonmail.com CC: plasma-b...@kde.org Target Milestone: --- SUMMARY Since the update to Plasma 5.25.2, searching for files doesn't work in application launchers, except the default Kickoff and directly in Krunner. STEPS TO REPRODUCE 1. Add or change Kickoff to alternative application launcher (e.g. Simple Menu, Tiled Menu). 2. Search for any file in the search box. OBSERVED RESULT List is empty, unless the text matches application name. EXPECTED RESULT List should contain the file you're looking for. SOFTWARE/OS VERSIONS Operating System: Manjaro Linux KDE Plasma Version: 5.25.2 KDE Frameworks Version: 5.95.0 Qt Version: 5.15.5 Kernel Version: 5.18.10-1-MANJARO (64-bit) Graphics Platform: X11 ADDITIONAL INFORMATION To investigate it further I - created another user account on my working machine, - installed Manjaro in virtual machine with Plasma 5.25 and succesfully reproduced it in both cases. See also https://forum.manjaro.org/t/cant-search-for-files-in-application-launchers-except-in-kickoff/116132/6. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 456497] Icons and Widgets Move on Second Monitor
https://bugs.kde.org/show_bug.cgi?id=456497 smow changed: What|Removed |Added CC||smowten...@protonmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 353975] Black screen on second display (no wallpaper, can't get a context menu on right-click)
https://bugs.kde.org/show_bug.cgi?id=353975 Samuel García changed: What|Removed |Added CC||k...@samueldgv.com --- Comment #191 from Samuel García --- Hello, just chiming in. I am also experiencing this issue after switching to a dual monitor layout, just as mikro and others reported. This is only happening on Wayland, and the only relevant log messages I see are several these ones, repeated over time, which I do not think are very relevant: Jul 10 20:57:14 mostro plasmashell[27061]: [2022-07-10 20:57:14.840] [27081] (device_info_linux.cc:45): NumberOfDevices Jul 10 20:57:17 mostro plasmashell[27061]: [2022-07-10 20:57:17.842] [27081] (device_info_linux.cc:45): NumberOfDevices Jul 10 20:57:20 mostro plasmashell[27061]: [2022-07-10 20:57:20.845] [27081] (device_info_linux.cc:45): NumberOfDevices Jul 10 20:57:23 mostro plasmashell[5843]: kf.plasma.quick: Couldn't create KWindowShadow for ToolTipDialog(0x5574fabb33e0) Jul 10 20:57:23 mostro plasmashell[5843]: kf.plasma.quick: Couldn't create KWindowShadow for ToolTipDialog(0x5574fabb33e0) Jul 10 20:57:23 mostro plasmashell[5843]: kf.plasma.quick: Couldn't create KWindowShadow for ToolTipDialog(0x5574fabb33e0) Jul 10 20:57:23 mostro plasmashell[27061]: [2022-07-10 20:57:23.848] [27081] (device_info_linux.cc:45): NumberOfDevices I personally don't have scaling enabled, and the X.org session works perfectly, only the Wayland one has these problems. Also, the workarounds mentioned above about deleting old configuration files didn't help at all. My plasma version is 5.25.2. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 456561] New: Plasma crashes when I left click on Digital Clock in Panel.
https://bugs.kde.org/show_bug.cgi?id=456561 Bug ID: 456561 Summary: Plasma crashes when I left click on Digital Clock in Panel. Product: plasmashell Version: 5.25.2 Platform: Neon Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: lnx...@westlot.net CC: k...@davidedmundson.co.uk Target Milestone: 1.0 Application: plasmashell (5.25.2) Qt Version: 5.15.5 Frameworks Version: 5.95.0 Operating System: Linux 5.13.0-35-generic x86_64 Windowing System: Wayland Distribution: KDE neon User - 5.25 DrKonqi: 5.25.2 [KCrashBackend] -- Information about the crash: Every time I left click on the Digital Clock in the Panel in Wayland, Plasma crashes. This does not happen in X. The crash can be reproduced every time. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault [New LWP 4838] [New LWP 4839] [New LWP 4860] [New LWP 5194] [New LWP 5254] [New LWP 5255] [New LWP 5256] [New LWP 5257] [New LWP 5258] [New LWP 5259] [New LWP 5260] [New LWP 5262] [New LWP 5263] [New LWP 5264] [New LWP 5265] [New LWP 5266] [New LWP 5267] [New LWP 5268] [New LWP 5269] [New LWP 5270] [New LWP 5271] [New LWP 5272] [New LWP 5273] [New LWP 5493] [New LWP 5494] [New LWP 5495] [New LWP 5499] [New LWP 5506] [New LWP 5510] [New LWP 5511] [New LWP 5516] [New LWP 5517] [New LWP 5518] [New LWP 5687] [New LWP 6156] [New LWP 6950] [New LWP 6951] [New LWP 6952] [New LWP 6955] [New LWP 6956] [New LWP 6957] [New LWP 6959] [New LWP 6960] [New LWP 6961] [New LWP 7895] [New LWP 7896] [New LWP 7897] [New LWP 8357] [New LWP 16479] [New LWP 16480] [New LWP 16481] [New LWP 20885] [New LWP 20886] [New LWP 20887] [New LWP 30175] [New LWP 30176] [New LWP 30177] [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". 0x7f9e0b9dc99f in __GI___poll (fds=0x7fffa7596138, nfds=1, timeout=1000) at ../sysdeps/unix/sysv/linux/poll.c:29 __preamble__ [Current thread is 1 (Thread 0x7f9e07ac79c0 (LWP 4814))] Thread 58 (Thread 0x7f9cfbfff700 (LWP 30177)): #0 futex_wait_cancelable (private=, expected=0, futex_word=0x561416e1e150) at ../sysdeps/nptl/futex-internal.h:183 #1 __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x561416e1e100, cond=0x561416e1e128) at pthread_cond_wait.c:508 #2 __pthread_cond_wait (cond=0x561416e1e128, mutex=0x561416e1e100) at pthread_cond_wait.c:647 #3 0x7f9e0bd725fb in QWaitConditionPrivate::wait(QDeadlineTimer) (deadline=..., this=0x561416e1e100) at thread/qwaitcondition_unix.cpp:146 #4 QWaitCondition::wait(QMutex*, QDeadlineTimer) (this=, mutex=0x561414d0be20, deadline=...) at thread/qwaitcondition_unix.cpp:225 #5 0x7f9e0d9fe2f4 in () at /lib/x86_64-linux-gnu/libQt5Quick.so.5 #6 0x7f9e0d9fe769 in () at /lib/x86_64-linux-gnu/libQt5Quick.so.5 #7 0x7f9e0bd6c553 in QThreadPrivate::start(void*) (arg=0x561414d0bd80) at thread/qthread_unix.cpp:331 #8 0x7f9e0b700609 in start_thread (arg=) at pthread_create.c:477 #9 0x7f9e0b9e9133 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 57 (Thread 0x7f9d14dea700 (LWP 30176)): #0 futex_wait_cancelable (private=, expected=0, futex_word=0x561418562b90) at ../sysdeps/nptl/futex-internal.h:183 #1 __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x561418562b40, cond=0x561418562b68) at pthread_cond_wait.c:508 #2 __pthread_cond_wait (cond=0x561418562b68, mutex=0x561418562b40) at pthread_cond_wait.c:647 #3 0x7f9df5b50e8b in () at /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so #4 0x7f9df5b50bdb in () at /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so #5 0x7f9e0b700609 in start_thread (arg=) at pthread_create.c:477 #6 0x7f9e0b9e9133 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 56 (Thread 0x7f9ca700 (LWP 30175)): #0 futex_wait_cancelable (private=, expected=0, futex_word=0x5614175b5c30) at ../sysdeps/nptl/futex-internal.h:183 #1 __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x5614175b5be0, cond=0x5614175b5c08) at pthread_cond_wait.c:508 #2 __pthread_cond_wait (cond=0x5614175b5c08, mutex=0x5614175b5be0) at pthread_cond_wait.c:647 #3 0x7f9df5b50e8b in () at /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so #4 0x7f9df5b50bdb in () at /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so #5 0x7f9e0b700609 in start_thread (arg=) at pthread_create.c:477 #6 0x7f9e0b9e9133 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 55 (Thread 0x7f9d155eb700 (LWP 20887)): #0 futex_wait_cancelable (private=, expected=0, futex_word=0x561414ba4c14) at ../sysdeps/nptl/futex-internal.h:183 #1 __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x561414ba4bc0, cond=0x561414ba4be8) at pthread_cond_wait.c:508 #2 __pthread_c
[Discover] [Bug 456560] New: KDE Crashes when changing the theme in system settings
https://bugs.kde.org/show_bug.cgi?id=456560 Bug ID: 456560 Summary: KDE Crashes when changing the theme in system settings Product: Discover Version: 5.25.2 Platform: openSUSE RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: discover Assignee: lei...@leinir.dk Reporter: paulflaher...@protonmail.com CC: aleix...@kde.org Target Milestone: --- Application: plasma-discover (5.25.2) Qt Version: 5.15.5 Frameworks Version: 5.95.0 Operating System: Linux 5.18.9-1-default x86_64 Windowing System: X11 Distribution: openSUSE Tumbleweed DrKonqi: 5.25.2 [KCrashBackend] -- Information about the crash: When changing the theme from the openSUSE default theme to breeze dark when clicking the button right after the action the entire plasma desktop crashes. But Kwin stays open and then plasma relaunches. I am using openSUSE tumbleweed with KDE. The crash can be reproduced every time. -- Backtrace: Application: Discover (plasma-discover), signal: Segmentation fault [KCrash Handler] #4 0x7eff254b63ab in QTextStream::operator<<(char) () from /lib64/libQt5Core.so.5 #5 0x7eff044ec13d in ?? () from /usr/lib64/qt5/plugins/discover/flatpak-backend.so #6 0x7eff045020d9 in ?? () from /usr/lib64/qt5/plugins/discover/flatpak-backend.so #7 0x7eff2545ae6f in ?? () from /lib64/libQt5Core.so.5 #8 0x7eff2734840e in Transaction::statusChanged(Transaction::Status) () from /usr/lib64/plasma-discover/libDiscoverCommon.so #9 0x7eff2734ebac in Transaction::setStatus(Transaction::Status) () from /usr/lib64/plasma-discover/libDiscoverCommon.so #10 0x7eff2544f760 in QObject::event(QEvent*) () from /lib64/libQt5Core.so.5 #11 0x7eff2667441e in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib64/libQt5Widgets.so.5 #12 0x7eff25423fb8 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib64/libQt5Core.so.5 #13 0x7eff25426f51 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /lib64/libQt5Core.so.5 #14 0x7eff2547bc53 in ?? () from /lib64/libQt5Core.so.5 #15 0x7eff23c18ea0 in g_main_context_dispatch () from /lib64/libglib-2.0.so.0 #16 0x7eff23c19258 in ?? () from /lib64/libglib-2.0.so.0 #17 0x7eff23c192ec in g_main_context_iteration () from /lib64/libglib-2.0.so.0 #18 0x7eff2547b456 in QEventDispatcherGlib::processEvents(QFlags) () from /lib64/libQt5Core.so.5 #19 0x7eff25422a2b in QEventLoop::exec(QFlags) () from /lib64/libQt5Core.so.5 #20 0x7eff2542ab96 in QCoreApplication::exec() () from /lib64/libQt5Core.so.5 #21 0x55672fb99edf in ?? () #22 0x7eff24d2b5b0 in __libc_start_call_main () from /lib64/libc.so.6 #23 0x7eff24d2b679 in __libc_start_main_impl () from /lib64/libc.so.6 #24 0x55672fb9a895 in ?? () [Inferior 1 (process 6173) detached] Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 456529] The pen pressure in krita isn't working
https://bugs.kde.org/show_bug.cgi?id=456529 --- Comment #2 from diro...@gmail.com --- I did all of those things and the pen pressure still isn't working On Sat, Jul 9, 2022, 4:09 PM vanyossi wrote: > https://bugs.kde.org/show_bug.cgi?id=456529 > > vanyossi changed: > >What|Removed |Added > > > Resolution|--- |NOT A BUG > Status|REPORTED|RESOLVED >Keywords||triaged > CC||ghe...@gmail.com > > --- Comment #1 from vanyossi --- > We can't do anything with so little information you provide. First and all > you > have to check you have everything in your windows and tablet drivers > properly > installed. Tablet issues are rarely and issue of krita. Please try > reinstalling > your tablet drivers and more specifically the next recommendations: > > For Windows, all devices: > Change API in Settings ‣ Configure Krita… ‣ Tablet Settings. > Wintab: older standard; it supports multiple buttons and high > number of pressure levels. If it works fine for you, don’t change to > Windows > Ink. 2-in-1 devices by default use Windows Ink, you can get a Wintab > driver but > you need to install it separately. > Windows 8+ Pointer (Windows Ink): newer standard; it cuts the > pressure levels to 1024. It is more suitable for 2-in-1 devices like > Surface > Pro and Yoga. Some less known brands might not have this standard > implemented. > > For Windows, tablet/digitizer devices (not convertible/2-in-1 ones): > Reinstall your driver (Windows Update often breaks tablet driver > settings, > reinstallation helps). > Wacom tablets: if you get straight lines at the beginnings of the > strokes, > first try to update your driver: it should be fixed in 6.3.34-3. If it > doesn’t > work, disable/minimize “double-click distance” in Wacom settings. > XP-Pen tablets, pressure being uneven: either switch to Windows 8+ > Pointer > (Windows Ink) in Configure Krita ‣ Tablet Settings, or disable Windows Ink > in > XP-Pen settings. > > If all this fails please ask around for help in https://krita-artists.org/ > before reporting a bug. > > -- > You are receiving this mail because: > You reported the bug. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 456525] Radio group «Text display:» on configuration page may have no options selected
https://bugs.kde.org/show_bug.cgi?id=456525 Nate Graham changed: What|Removed |Added CC||n...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 456556] Widget Explorer sometimes cannot be opened until Plasma restart
https://bugs.kde.org/show_bug.cgi?id=456556 Patrick Silva changed: What|Removed |Added CC||bugsefor...@gmx.com --- Comment #1 from Patrick Silva --- possibly duplicate of bug 439159 -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 456559] Dolphin does not recognize .mp4 video files as videos when viewing files on my mobile phone via USB connection.
https://bugs.kde.org/show_bug.cgi?id=456559 --- Comment #2 from HeathenHacks --- Created attachment 150518 --> https://bugs.kde.org/attachment.cgi?id=150518&action=edit Showcase of what's happening 2 -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 456559] Dolphin does not recognize .mp4 video files as videos when viewing files on my mobile phone via USB connection.
https://bugs.kde.org/show_bug.cgi?id=456559 --- Comment #1 from HeathenHacks --- Created attachment 150517 --> https://bugs.kde.org/attachment.cgi?id=150517&action=edit Showcase of what's Happening -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 456559] New: Dolphin does not recognize .mp4 video files as videos when viewing files on my mobile phone via USB connection.
https://bugs.kde.org/show_bug.cgi?id=456559 Bug ID: 456559 Summary: Dolphin does not recognize .mp4 video files as videos when viewing files on my mobile phone via USB connection. Product: dolphin Version: 22.04.3 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: mrressipiyent...@gmail.com CC: kfm-de...@kde.org Target Milestone: --- SUMMARY Dolphin does not seem to recognize .mp4 video files as videos when viewing files on my mobile phone via USB connection. I have set the "Skip previews for remote files" to 9MB and I have ffmpegthumbs installed/enabled on the preview settings of Dolphin. STEPS TO REPRODUCE 1. If you have a mobile phone that records videos with .mp4 extensions, view the media files on your mobile phone via USB connection using Dolphin 2. If you're not seeing the thumbnail of your video, check properties and see if it says MPEG-4 audio instead of MPEG-4 video. 3. Then, transfer the .mp4 file to your local storage and check the properties again to see if it changed to MPEG-4 video. OBSERVED RESULT Dolphin sees the .mp4 videos on my phone as MPEG-4 audio for some reason. But, when I play it, it plays the video as expected, and when I transfer an mp4 file from my phone to my local storage, it becomes an MPEG-4 video and reveals its thumbnail. I'm really confused, because .mov video files are showing their thumbnails, but .mp4 video files doesn't. The provided images below showcases what was said above. I can view the thumbnails of all my locally stored media files properly, tho. EXPECTED RESULT Normally, it should just show all the thumbnails of media files because that's what I set it to do. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: ArcoLinux [5.18.10-arch1-1] (available in About System) KDE Plasma Version: 5.25.2 KDE Frameworks Version: 5.95.0 Qt Version: 5.15.5 ADDITIONAL INFORMATION Device Used: Samsung Galaxy A71 Reddit Post Link: https://www.reddit.com/r/kde/comments/vvobhj/confused_as_to_what_im_doing_wrong_dolphin_does/ -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 444741] CSV importer: account name auto detection generates too many false-positives
https://bugs.kde.org/show_bug.cgi?id=444741 Dawid Wróbel changed: What|Removed |Added Latest Commit|https://invent.kde.org/offi |https://invent.kde.org/offi |ce/kmymoney/commit/9ec90abb |ce/kmymoney/commit/1ebd8c70 |c80a92bf8a7673bedac73219c10 |4deb2af890aa54c60411f6e627b |b7902 |d8a4b --- Comment #4 from Dawid Wróbel --- Git commit 1ebd8c704deb2af890aa54c60411f6e627bd8a4b by Dawid Wróbel. Committed on 10/07/2022 at 09:42. Pushed by wrobelda into branch 'master'. [CSV] Configure account autodetection per profile CSV importer had a global option enabling account name autodetection based on the header contents. This, however, should only really be enabled if the CSV file contains actual account name, and therefore configurable *per profile*. Also: run clang-format against touched source files. M +31 -29 kmymoney/plugins/csv/import/core/csvimportercore.cpp M +120 -65 kmymoney/plugins/csv/import/core/csvimportercore.h M +39 -24 kmymoney/plugins/csv/import/core/tests/csvimportercore-test.cpp M +4-0kmymoney/plugins/csv/import/csvwizard.cpp M +0-6kmymoney/plugins/csv/import/pluginsettings.kcfg M +44 -1kmymoney/plugins/csv/import/rowswizardpage.ui M +7-1kmymoney/settings/kmymoney.upd https://invent.kde.org/office/kmymoney/commit/1ebd8c704deb2af890aa54c60411f6e627bd8a4b -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 444741] CSV importer: account name auto detection generates too many false-positives
https://bugs.kde.org/show_bug.cgi?id=444741 Dawid Wróbel changed: What|Removed |Added Latest Commit||https://invent.kde.org/offi ||ce/kmymoney/commit/9ec90abb ||c80a92bf8a7673bedac73219c10 ||b7902 Status|ASSIGNED|RESOLVED Resolution|--- |FIXED --- Comment #3 from Dawid Wróbel --- Git commit 9ec90abbc80a92bf8a7673bedac73219c10b7902 by Dawid Wróbel. Committed on 10/07/2022 at 09:47. Pushed by wrobelda into branch '5.1'. [CSV] Configure account autodetection per profile CSV importer had a global option enabling account name autodetection based on the header contents. This, however, should only really be enabled if the CSV file contains actual account name, and therefore configurable *per profile*. Also: run clang-format against touched source files. M +31 -29 kmymoney/plugins/csv/import/core/csvimportercore.cpp M +120 -65 kmymoney/plugins/csv/import/core/csvimportercore.h M +39 -24 kmymoney/plugins/csv/import/core/tests/csvimportercore-test.cpp M +4-0kmymoney/plugins/csv/import/csvwizard.cpp M +0-6kmymoney/plugins/csv/import/pluginsettings.kcfg M +44 -1kmymoney/plugins/csv/import/rowswizardpage.ui M +8-1kmymoney/settings/kmymoney.upd https://invent.kde.org/office/kmymoney/commit/9ec90abbc80a92bf8a7673bedac73219c10b7902 -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 456558] New: UI Elements get blurred and makes the PC unusable.
https://bugs.kde.org/show_bug.cgi?id=456558 Bug ID: 456558 Summary: UI Elements get blurred and makes the PC unusable. Product: kde Version: unspecified Platform: unspecified OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: fpsusern...@protonmail.com Target Milestone: --- Created attachment 150516 --> https://bugs.kde.org/attachment.cgi?id=150516&action=edit UI elements get blurred 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 *** Whenever I use KDE for an extensive time, it sometimes can happen that the UI glitches out and everything becomes blurry. In the attachment you can see the top bar (blue blur), the application launcher and latte dock. This can happen when the compositor is enabled or disabled. STEPS TO REPRODUCE 1. Wait for it to happen. It often triggers for me when I press the meta key. OBSERVED RESULT UI elements get blurry and the PC is unusable. EXPECTED RESULT UI to work fine SOFTWARE/OS VERSIONS Linux/KDE Plasma: Arch Linux with 5.18.10-xanmod1-1-haswell (64-bit) (available in About System) KDE Plasma Version: 5.25.2 KDE Frameworks Version: 5.95.0 Qt Version: 5.15.5 ADDITIONAL INFORMATION EVGA GTX 960 SSC 4GB GPU running on latest proprietary nvidia drivers. This issue exists for me at least since KDE 5.21 and Linux kernel v5.12. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 456557] New: Present Windows ignores all keyboard input after plasmashell is restarted
https://bugs.kde.org/show_bug.cgi?id=456557 Bug ID: 456557 Summary: Present Windows ignores all keyboard input after plasmashell is restarted Product: kwin Version: 5.25.2 Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: effects-present-windows Assignee: kwin-bugs-n...@kde.org Reporter: bizy...@zoho.com Target Milestone: --- When I restart plasmashell (to mitigate one of the other bugs or a memory leak), I can no longer use keyboard at all in the new Present Windows effect. Before 5.25.0, this has not been a problem. STEPS TO REPRODUCE 1. Restart plasmashell 2. Trigger the Present Windows effect with a screen corner or a keyboard shortcut 3. Try typing, pressing Ctrl-F or the arrow keys OBSERVED RESULT Nothing happens, cannot even select the search field with the mouse; only selecting windows with a mouse click is possible. EXPECTED RESULT The effect behaves as usual. SOFTWARE/OS VERSIONS Operating System: openSUSE Leap 15.4 KDE Plasma Version: 5.25.2 KDE Frameworks Version: 5.95.0 Qt Version: 5.15.5 Graphics Platform: X11 Graphics Processor: Mesa Intel® UHD Graphics -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 456556] New: Widget Explorer sometimes cannot be opened until Plasma restart
https://bugs.kde.org/show_bug.cgi?id=456556 Bug ID: 456556 Summary: Widget Explorer sometimes cannot be opened until Plasma restart Product: plasmashell Version: 5.25.2 Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Widget Explorer Assignee: plasma-b...@kde.org Reporter: bizy...@zoho.com Target Milestone: 1.0 Sometimes Plasma stops being able to trigger the Widget Explorer completely until plasmashell is restarted. It also appears that `plasmashell --replace` is not enough, while `killall plasmashell && kstart5 plasmashell` works. STEPS TO REPRODUCE I wish I knew, but for me, it is: 1. Use Plasma for some time 2. When I need to add a widget and use "Add widgets" in the desktop's context menu, nothing happens SOFTWARE/OS VERSIONS Operating System: openSUSE Leap 15.4 KDE Plasma Version: 5.25.2 KDE Frameworks Version: 5.95.0 Qt Version: 5.15.5 Graphics Platform: X11 Graphics Processor: Mesa Intel® UHD Graphics ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 456555] New: Dragging windows across monitors sometimes makes them invisible until you let go of them
https://bugs.kde.org/show_bug.cgi?id=456555 Bug ID: 456555 Summary: Dragging windows across monitors sometimes makes them invisible until you let go of them Product: kwin Version: 5.25.2 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: effects-overview Assignee: kwin-bugs-n...@kde.org Reporter: indecisiveautoma...@gmail.com Target Milestone: --- SUMMARY When trying to drag a window to another monitor with the Overview effect, it is invisible in a couple of situations. If that window has been scaled down at all - for example if you drag it up towards other virtual desktops, it gets a bit smaller. If you try to drag a window onto another display with it in this state it will be invisible until you let go of it, and then it will pop into existence on the other display. For example, a maximised window or just a very large window (such as Info Center Sometimes though, the window will glitch and flicker when dragged between displays and then once it's fully on another display it will disappear. This is the behaviour when dragging smaller windows (such as Info Center) across displays and back again. This behaviour is a little less consistent. If I'm dragging windows that aren't on the primary display, they are always invisible if I drag them between displays. For example moving a window from my middle display to one on the left, it is always invisible in the Overview effect until I let go. Sometimes if I'm dragging a window from my middle display onto my primary display, the window will show up on the primary display but under any existing windows, and only until my mouse cursor goes across the display "border" and then the window disappears. Other times it might flicker. It's very strange, seemingly inconsistent and "ugly" flickering behaviour but it's invisible for 99% of cases. This bug is cosmetic to the Overview effect, the windows appear on the correct display once I let go and there is no issue once the Overview effect is closed. The problem is purely with regards to how the windows look when they are being dragged between displays, before the user lets go of the window. STEPS TO REPRODUCE 1. Scale a window down in the Overview effect, such as by trying to move it up as if it were going onto a virtual desktop 2. Drag it to another display 3. Window will be invisible Dragging to a primary display (the above still applies, this is for non-scaled windows) 1. Drag a window from one display to a primary display (if its scaled down 2. It will either be invisible or it will flicker OBSERVED RESULT Windows sometimes become invisible or are invisible with some very occasional flickering, when dragging them between displays with the Overview effect. EXPECTED RESULT Windows should always be visible and smoothly scale and animate in the Overview effect. SOFTWARE/OS VERSIONS Linux/KDE Plasma: 5.18.10-zen1-1-zen KDE Plasma Version: 5.25.2 KDE Frameworks Version: 5.95.0 Qt Version: 5.15.5 ADDITIONAL INFORMATION Tested on Wayland, have not tried X11 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 433045] Tablet configuration does not exist in wayland
https://bugs.kde.org/show_bug.cgi?id=433045 --- Comment #13 from Bug Janitor Service --- A possibly relevant merge request was started @ https://invent.kde.org/plasma/kwin/-/merge_requests/2627 -- You are receiving this mail because: You are watching all bug changes.
[NeoChat] [Bug 456554] New: Room list footer and chatbar different heights
https://bugs.kde.org/show_bug.cgi?id=456554 Bug ID: 456554 Summary: Room list footer and chatbar different heights Product: NeoChat Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: General Assignee: fe...@posteo.de Reporter: james.h.gra...@protonmail.com CC: c...@carlschwan.eu Target Milestone: --- Created attachment 150515 --> https://bugs.kde.org/attachment.cgi?id=150515&action=edit Neochat roomlist footer height SUMMARY When logged in to multiple accounts a footer appears on the roomlist which allows the user to select between the accounts. Currently the height of this footer is different to the chatbar height which is not very aesthetically pleasing. STEPS TO REPRODUCE 1. Login to a second account 2. Observe roomlist footer and chatbar heights OBSERVED RESULT The roomlist footer is slightly shorter EXPECTED RESULT The roomlist footer should be the same size at least when the chatbar is a single line SOFTWARE/OS VERSIONS Operating System: EndeavourOS KDE Plasma Version: 5.25.2 KDE Frameworks Version: 5.95.0 Qt Version: 5.15.5 Kernel Version: 5.18.10-arch1-1 (64-bit) Graphics Platform: Wayland Processors: 12 × AMD Ryzen 5 3600 6-Core Processor Memory: 15.5 GiB of RAM Graphics Processor: AMD Radeon RX 580 Series Manufacturer: Micro-Star International Co., Ltd Product Name: MS-7C02 System Version: 1.0 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 456553] New: Dragged windows that scale down don't smoothly transform back to their original size
https://bugs.kde.org/show_bug.cgi?id=456553 Bug ID: 456553 Summary: Dragged windows that scale down don't smoothly transform back to their original size Product: kwin Version: 5.25.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: effects-overview Assignee: kwin-bugs-n...@kde.org Reporter: indecisiveautoma...@gmail.com Target Milestone: --- SUMMARY Dragging a window up in the Overview effect to make it smaller (as if you were dragging it onto a virtual desktop) and letting go causes the window to move down to its original position, but then suddenly snaps back to its original size instead of smoothly scaling back to that size. STEPS TO REPRODUCE 1. Open Overview effect 2. Drag a window up towards virtual desktops list 3. Let go of window 4. Window will move back but won't smoothly transform back to its correct size, instead sharply going back to its original size with no animation OBSERVED RESULT Window suddenly snaps back to its original size when let go EXPECTED RESULT Window should smoothly animate back to its original size (I believe it did this in 5.24) SOFTWARE/OS VERSIONS Linux/KDE Plasma: 5.18.10-zen1-1-zen (64bit) KDE Plasma Version: 5.25.2 KDE Frameworks Version: 5.95.0 Qt Version: 5.15.5 ADDITIONAL INFORMATION Tested on Wayland, have not tried X11 -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 322935] disInstr(arm): unhandled instruction: 0xF1010200, valgrind: Unrecognised instruction on Raspbian
https://bugs.kde.org/show_bug.cgi?id=322935 Sam James changed: What|Removed |Added CC||s...@gentoo.org -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kirigami] [Bug 456047] Crashes once at startup in ImageColors::update()
https://bugs.kde.org/show_bug.cgi?id=456047 Aleix Pol changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |FIXED -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 447774] File system expose cannot expose certain folders on Android 11
https://bugs.kde.org/show_bug.cgi?id=447774 Lewis L. Foster changed: What|Removed |Added CC||le...@sniff122.tech --- Comment #4 from Lewis L. Foster --- Im having this on android 12 with my Galaxy S20 FE 5G running security patch 1 June 2022 and one UI 4.1 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 445356] Show virtual desktop related shortcuts in the Virtual Desktops KCM
https://bugs.kde.org/show_bug.cgi?id=445356 Nate Graham changed: What|Removed |Added Status|REPORTED|CONFIRMED Ever confirmed|0 |1 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 410366] New desktops are named exactly the same
https://bugs.kde.org/show_bug.cgi?id=410366 Nate Graham changed: What|Removed |Added CC||germano.massu...@gmail.com --- Comment #3 from Nate Graham --- *** Bug 442162 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 442162] Add new desktop adds "New Desktop" rather than "Desktop "
https://bugs.kde.org/show_bug.cgi?id=442162 Nate Graham changed: What|Removed |Added Status|CONFIRMED |RESOLVED Resolution|--- |DUPLICATE --- Comment #2 from Nate Graham --- *** This bug has been marked as a duplicate of bug 410366 *** -- You are receiving this mail because: You are watching all bug changes.
[kdebugsettings] [Bug 448514] KDebugSettings has bad discoverability
https://bugs.kde.org/show_bug.cgi?id=448514 ratijas changed: What|Removed |Added Status|ASSIGNED|RESOLVED Latest Commit||https://invent.kde.org/util ||ities/kdebugsettings/commit ||/e3b76f4de17e098bc046dd96d9 ||e476d5359e1b0c Resolution|--- |FIXED --- Comment #8 from ratijas --- Git commit e3b76f4de17e098bc046dd96d9e476d5359e1b0c by ivan tkachenko. Committed on 10/07/2022 at 14:46. Pushed by ngraham into branch 'master'. Make KDebugSettings app actually discoverable M +1-1src/org.kde.kdebugsettings.desktop https://invent.kde.org/utilities/kdebugsettings/commit/e3b76f4de17e098bc046dd96d9e476d5359e1b0c -- You are receiving this mail because: You are watching all bug changes.
[kolourpaint] [Bug 456498] cannot insert zero-width joiner and zero-width non-joiner characters in text tool
https://bugs.kde.org/show_bug.cgi?id=456498 Martin Koller changed: What|Removed |Added Latest Commit||https://invent.kde.org/grap ||hics/kolourpaint/commit/297 ||feb5453c2ea7d3b27e9e5717211 ||841fe20ac8 Resolution|--- |FIXED Status|CONFIRMED |RESOLVED --- Comment #4 from Martin Koller --- Git commit 297feb5453c2ea7d3b27e9e5717211841fe20ac8 by Martin Koller. Committed on 10/07/2022 at 15:50. Pushed by mkoller into branch 'master'. Only disallow control characters for text input This now allows to insert e.g. zero-width joiner and zero-width non-joiner characters, which are needed for arabic/persian input M +2-3 tools/selection/text/kpToolText_KeyboardEvents_HandleTypingKeys.cpp https://invent.kde.org/graphics/kolourpaint/commit/297feb5453c2ea7d3b27e9e5717211841fe20ac8 -- You are receiving this mail because: You are watching all bug changes.
[kolourpaint] [Bug 456498] cannot insert zero-width joiner and zero-width non-joiner characters in text tool
https://bugs.kde.org/show_bug.cgi?id=456498 Martin Koller changed: What|Removed |Added Ever confirmed|0 |1 Status|REPORTED|CONFIRMED --- Comment #3 from Martin Koller --- Great, thanks. With this description I could see that my fix works indeed. -- You are receiving this mail because: You are watching all bug changes.
