[kwin] [Bug 444335] Full sticky keys functionality does not work under Wayland
https://bugs.kde.org/show_bug.cgi?id=444335 --- Comment #13 from Nick W --- It's great to see work being done on this! Question - when a patch is merged, how do I know which version of KDE/Plasma it will be available? As far as I can tell these are my only blockers to giving Wayland a go, so I'd like to know when I can test a fix. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 444335] Full sticky keys functionality does not work under Wayland
https://bugs.kde.org/show_bug.cgi?id=444335 --- Comment #21 from Nick W --- In response to "It would be great to have some input on which of these are most important/should be prioritized or which of them may be unimportant enough to drop them" I would say any accessibility features are going to have widely differing priorities depending who you ask. My impairment is purely motor, but others it's vision, motion, color, the list unfortunately is long. All these features exist because *someone* needs it. And by needs, I mean the system is utterly unusable without it. For that reason, any accessibility functions should be considered as hard blockers, imo. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 444335] Sticky keys does not work under Wayland
https://bugs.kde.org/show_bug.cgi?id=444335 --- Comment #4 from Nick W --- This bug unfortunately makes KDE completely unusable under Wayland for those that need this feature. Given that a number of major distros are pushing to make Wayland default, I'm hoping to draw attention to it before that happens. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 444335] New: Sticky keys does not work under Wayland
https://bugs.kde.org/show_bug.cgi?id=444335 Bug ID: 444335 Summary: Sticky keys does not work under Wayland Product: kwin Version: 5.22.5 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: input Assignee: kwin-bugs-n...@kde.org Reporter: n...@customdesigns.ca Target Milestone: --- Turning on sticky keys in Wayland has no effect. STEPS TO REPRODUCE Turn on sticky keys in system settings -> accessibility Press & release shift Press a letter key OBSERVED RESULT A lower case letter is typed EXPECTED RESULT An upper case letter is typed -- You are receiving this mail because: You are watching all bug changes.
[kdevplatform] [Bug 283209] Built in Konsole should remember it's working dir
https://bugs.kde.org/show_bug.cgi?id=283209 Nick W changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED --- Comment #4 from Nick W --- Unfortunately my workflow has forced me away from kDevelop, so I'll close this as it's no longer something I can comment on. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 400074] Accessibility Sticky-Keys Becoming Disabled At Random At Times
https://bugs.kde.org/show_bug.cgi?id=400074 Nick W changed: What|Removed |Added CC||n...@customdesigns.ca --- Comment #2 from Nick W --- I have encountered this bug with multiple wireless keyboards. Its quite frustrating to have to go re-enable sticky keys every time my keyboard hibernates. Also, when it happens the checkbox for sticky keys still shows on as if it was never disabled. You have to uncheck the box, re-check it then hit apply. I have to do this 3-4 times some days. Easy way to reproduce: While sticky keys is on, unplug a usb keyboard and plug it back in. Sticky keys will show it's active, but it won't be working. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 397644] baloo_file crashes in Baloo::DocumentTimeDB::get()
https://bugs.kde.org/show_bug.cgi?id=397644 Nick W changed: What|Removed |Added CC||n...@customdesigns.ca -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 353983] Turning off compositing breaks Plasma panel rendering
https://bugs.kde.org/show_bug.cgi?id=353983 Nick W changed: What|Removed |Added CC|n...@customdesigns.ca | -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 403637] New: Better handling of untracked fles
https://bugs.kde.org/show_bug.cgi?id=403637 Bug ID: 403637 Summary: Better handling of untracked fles Product: kdevelop Version: unspecified Platform: Other OS: All Status: REPORTED Severity: wishlist Priority: NOR Component: VCS: Git Assignee: kdevelop-bugs-n...@kde.org Reporter: n...@customdesigns.ca Target Milestone: --- In the patch review window, perhaps a 3rd pane could be added at the bottom beside "Commit Message" and "Changes" labeled "Untracked" that lists these files and allows you to add them to the commit. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 499771] New: Auto-hide panel stops working after screen lock
https://bugs.kde.org/show_bug.cgi?id=499771 Bug ID: 499771 Summary: Auto-hide panel stops working after screen lock Classification: Plasma Product: plasmashell Version: 6.2.5 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Panel Assignee: plasma-b...@kde.org Reporter: n...@customdesigns.ca CC: niccolo.venera...@gmail.com Target Milestone: 1.0 SUMMARY I have my panel set to auto hide and my screen to auto lock. After my screen locks and I unlock it,the panel no longer hides.I have to log out to get it to hide. STEPS TO REPRODUCE 1. Set panel to auto hide 2. Lock session (might need to allow screens to turn off?) 3. Log back in OBSERVED RESULT Panel doesn't auto hide EXPECTED RESULT Panel auto-hides SOFTWARE/OS VERSIONS Windows: macOS: (available in the Info Center app, or by running `kinfo` in a terminal window) Linux/KDE Plasma: Gentoo/6.2.5 KDE Plasma Version: 6.2.5 KDE Frameworks Version: 6.6.9 Qt Version: 6.8.1 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 499771] Auto-hide panel stops working after screen lock
https://bugs.kde.org/show_bug.cgi?id=499771 Nick W changed: What|Removed |Added Platform|Other |Gentoo Packages -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 499771] Auto-hide panel stops working after screen lock
https://bugs.kde.org/show_bug.cgi?id=499771 Nick W changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |NOT A BUG --- Comment #1 from Nick W --- It turns out I just need to click on it, then click off again. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 503684] New: Crash when unlocking & screens out of order
https://bugs.kde.org/show_bug.cgi?id=503684 Bug ID: 503684 Summary: Crash when unlocking & screens out of order Classification: Plasma Product: plasmashell Version: 6.3.4 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Power management & brightness Assignee: plasma-b...@kde.org Reporter: n...@customdesigns.ca Target Milestone: 1.0 SUMMARY Important to note I am on X11. I'm stuck here until Rustdesk works properly on Wayland :( I have 4 monitors.My screens auto-lock after 20 minutes.Seems fine. They blank and my computer goes into power save after a few more minutes. When I return and unlock, one of my monitors (not one in particular, a random one) will be black even though it's on. The ordering of my screens will change and my Yakuake window will be on a random monitor. I hit F2 and run "kquitapp5 plasmashell && kstart5 plasmashell" which restores the black monitor to normal. Then I have to move my Yakuake window to each screen until I figure out what random order they are in. SOFTWARE/OS VERSIONS Windows: No. macOS: Definitely not. (available in the Info Center app, or by running `kinfo` in a terminal window) Operating System: Gentoo Linux 2.17 KDE Plasma Version: 6.3.4 KDE Frameworks Version: 6.13.0 Qt Version: 6.8.3 Kernel Version: 6.12.21-gentoo-x86_64 (64-bit) Graphics Platform: X11 Processors: 32 × AMD Ryzen 9 7950X 16-Core Processor Memory: 62.6 GiB of RAM Graphics Processor: AMD Radeon RX 6900 XT Other info: It was doing this in 6.2 as well. I waited to upgrade to 6.3. Still present :( -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 503684] Crash when unlocking & screens out of order
https://bugs.kde.org/show_bug.cgi?id=503684 Nick W changed: What|Removed |Added Platform|Other |Gentoo Packages -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 496926] On X11, desktop is black/missing after resuming from suspend or hibernation until plasmashell is restarted or TTYs are switched
https://bugs.kde.org/show_bug.cgi?id=496926 --- Comment #54 from Nick W --- I understand the focus is on Wayland. It is clearly the way forward and I try to make the switch every few weeks. It is disappointing however to see this given low priority as Wayland for me is not usable. I need things that are missing protocol wise that aren't optional - mostly to do with remote screen functionality. I can't log in unattended using Rustdesk because Wayland is missing requisite permissions for screen sharing. If it was just minor annoyances with Wayland I'd put up with it. Unfortunately Wayland is notorious for taking literal years to add basic functionality. So it puts me in a position where I need to put up with this bug (an annoyance) or switch to Wayland and break my workflow completely. If you want users to switch to Wayland, the issues there need to get fixed before you abandon X11 users. I want to switch. But I literally can't. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 507828] New: Screen numbers change after lock/unlock cycle
https://bugs.kde.org/show_bug.cgi?id=507828 Bug ID: 507828 Summary: Screen numbers change after lock/unlock cycle Classification: Plasma Product: kwin Version First 6.4.3 Reported In: Platform: Gentoo Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: core Assignee: kwin-bugs-n...@kde.org Reporter: n...@customdesigns.ca Target Milestone: --- SUMMARY This has been an issue for me since 5.x, on both Wayland & X11. When I boot up, Yakuake launches on the last used screen (1 in my case). This is on the wrong screen, so I switch it to screen 3. Then I leave my PC for a time, screens lock. I come back, and now have to move it back to screen 1. Subsequent locks don't affect it afterward, it stays on screen 1 until I reboot and the cycle repeats. Hardware might matter? I have 4 screens, all running off of 1 Radeon 6900XT. 1 screen runs off a USBC port on the same card. The one on the USB port is the one that registers as Screen 1 after screen lock. Screen arrangement remains correct, just the screen number changes. -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 138370] todo attachments stop working after a time
https://bugs.kde.org/show_bug.cgi?id=138370 Nick W changed: What|Removed |Added Resolution|--- |INVALID Status|UNCONFIRMED |RESOLVED --- Comment #1 from Nick W --- It appears this functionality has been completely changed -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 353983] Turning off compositing breaks Plasma panel rendering
https://bugs.kde.org/show_bug.cgi?id=353983 Nick W changed: What|Removed |Added CC||n...@customdesigns.ca --- Comment #36 from Nick W --- Another "me too". https://paste.kde.org/ptwwwkems I think something dies in the background and the non-composited panel stops rendering. For instance, my current local time is 1:23PM but if I alt+shift+f12 I see 3:28PM, which is presumably yesterday, and presumably when it got suck as I've watched it for an hour or so and it hasn't moved from 3:28PM. I'm running 3 displays on 2x GTX 580s in SLI (Propreitary drivers) Resizing it caused an immediate update here as well. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 369590] New: Crash on Gitkraken file open
https://bugs.kde.org/show_bug.cgi?id=369590 Bug ID: 369590 Summary: Crash on Gitkraken file open Product: kate Version: 3.13.2 Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: application Assignee: kwrite-bugs-n...@kde.org Reporter: n...@mistoffolees.me.uk Running Gitkraken, selected old commit, file open, then kate (trying to open the file) crashes. Reproducible: Always Steps to Reproduce: 1.Run Gitkraken 2.Select any commit 3.Rt clk a text file (eg .cpp) 4.Select open file Actual Results: Doesn't open - crash report Expected Results: Opening file Running on Ubuntu 14.04.4, Gnome desktop. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 369590] Crash on Gitkraken file open
https://bugs.kde.org/show_bug.cgi?id=369590 --- Comment #1 from Nick W --- Whilst this may mean nothing at all, doing exactly the same thing on Windows works fine and it brings up the file in the default editor (notepad++ in this case). -- You are receiving this mail because: You are watching all bug changes.
