[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] 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] 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.
[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.
[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.
[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.
[kate] [Bug 369590] Crash on Gitkraken file open
https://bugs.kde.org/show_bug.cgi?id=369590 --- Comment #1 from Nick W <n...@mistoffolees.me.uk> --- 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.
[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.
[plasmashell] [Bug 353983] Turning off compositing breaks Plasma panel rendering
https://bugs.kde.org/show_bug.cgi?id=353983 Nick W <n...@customdesigns.ca> changed: What|Removed |Added CC||n...@customdesigns.ca --- Comment #36 from Nick W <n...@customdesigns.ca> --- 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.
[kontact] [Bug 138370] todo attachments stop working after a time
https://bugs.kde.org/show_bug.cgi?id=138370 Nick W <n...@customdesigns.ca> changed: What|Removed |Added Resolution|--- |INVALID Status|UNCONFIRMED |RESOLVED --- Comment #1 from Nick W <n...@customdesigns.ca> --- It appears this functionality has been completely changed -- You are receiving this mail because: You are watching all bug changes.
