https://bugs.kde.org/show_bug.cgi?id=493178
David Gow changed:
What|Removed |Added
CC||da...@ingeniumdigital.com
--
You are receiving
https://bugs.kde.org/show_bug.cgi?id=470266
David Gow changed:
What|Removed |Added
CC||da...@ingeniumdigital.com
--- Comment #6 from
https://bugs.kde.org/show_bug.cgi?id=445137
David Gow changed:
What|Removed |Added
CC||da...@ingeniumdigital.com
--
You are receiving
https://bugs.kde.org/show_bug.cgi?id=468053
--- Comment #2 from David Gow ---
Thanks — I can confirm that deleting the state file (or even just removing the
'deviceName' entry in it) fixes the issue here as well (at least until the next
time I start the program).
--
You are receiving
https://bugs.kde.org/show_bug.cgi?id=468053
Bug ID: 468053
Summary: Skanlite and Skanpage crash (deep in sane-backends)
when a net scanner is available
Classification: Frameworks and Libraries
Product: libksane
Version: 22.12.3
https://bugs.kde.org/show_bug.cgi?id=462027
David Gow changed:
What|Removed |Added
CC||da...@ingeniumdigital.com
--- Comment #3 from
https://bugs.kde.org/show_bug.cgi?id=418065
--- Comment #8 from David Gow ---
I also haven't noticed this recently, though I am now on a different setup that
when I first reported it.
Probably safe to close, and I'll reopen it if it recurs.
--
You are receiving this mail becaus
https://bugs.kde.org/show_bug.cgi?id=433460
--- Comment #13 from David Gow ---
This seems like it might have regressed for me, under openSUSE Tumbleweed
20220509 (Plasma 5.24.5, Frameworks 5.93.0).
Switching from X11 (at 2× scale) → Wayland gives a 1× scale display (even with
a reboot in
https://bugs.kde.org/show_bug.cgi?id=452938
--- Comment #1 from David Gow ---
(Forgot to fill in my system info, whoops:)
Linux/KDE Plasma: openSUSE Tumbleweed 20220422
(available in About System)
KDE Plasma Version: 5.24.4
KDE Frameworks Version: 5.93.0
Qt Version: 5.15.2
Kernel version
https://bugs.kde.org/show_bug.cgi?id=452938
Bug ID: 452938
Summary: pointer confinement regions misapplied to libdecor
decorations
Product: kwin
Version: 5.24.4
Platform: Other
OS: Linux
Status:
https://bugs.kde.org/show_bug.cgi?id=448844
David Gow changed:
What|Removed |Added
CC||da...@ingeniumdigital.com
--- Comment #12 from
https://bugs.kde.org/show_bug.cgi?id=436654
--- Comment #25 from David Gow ---
I can confirm that, while I used to get this issue (which often would result in
plasmashell OOMing), I've not been able to reproduce it recently. There's still
a (minor but noticeable) slowdown on a busy s
https://bugs.kde.org/show_bug.cgi?id=444962
--- Comment #8 from David Gow ---
There's apparently some debate about what getting a 0×0 configure message
actually means when a window is fullscreen.
See the discussion in the SDL github PR:
https://github.com/libsdl-org/SDL/pull/5064
I perso
https://bugs.kde.org/show_bug.cgi?id=444962
--- Comment #7 from David Gow ---
This is now looking like it's an SDL bug: I think the correct thing here is for
SDL to detect that a 0×0 window has been requested and interpret that as the
compositor not caring about the window size (so SDL shou
https://bugs.kde.org/show_bug.cgi?id=444962
--- Comment #5 from David Gow ---
I'm guessing the issue in 6.23.3 with the invisible 1×1 windows might be
related to bug #445444:
https://bugs.kde.org/show_bug.cgi?id=445444
In which case there might be a fix for that queued in the next re
https://bugs.kde.org/show_bug.cgi?id=444962
David Gow changed:
What|Removed |Added
CC||da...@ingeniumdigital.com
--- Comment #4 from
https://bugs.kde.org/show_bug.cgi?id=389298
David Gow changed:
What|Removed |Added
CC||da...@ingeniumdigital.com
--- Comment #9 from
https://bugs.kde.org/show_bug.cgi?id=433460
David Gow changed:
What|Removed |Added
CC||da...@ingeniumdigital.com
--- Comment #10 from
https://bugs.kde.org/show_bug.cgi?id=436654
David Gow changed:
What|Removed |Added
CC||da...@ingeniumdigital.com
--
You are receiving
https://bugs.kde.org/show_bug.cgi?id=439578
Bug ID: 439578
Summary: Maximize button sometimes appears even in
non-resizable windows with xdg-decoration
Product: kwin
Version: 5.22.2
Platform: Other
OS: Linux
https://bugs.kde.org/show_bug.cgi?id=428499
David Gow changed:
What|Removed |Added
CC||da...@ingeniumdigital.com
--
You are receiving
https://bugs.kde.org/show_bug.cgi?id=401031
--- Comment #20 from David Gow ---
For what it's worth, I'm still able to reproduce this bug on Dolphin 20.08.3 /
Plasma 5.20.3 as packaged by openSUSE Tumbleweed.
Stacktrace is still the same — it definitely seems to just still be c
https://bugs.kde.org/show_bug.cgi?id=418065
--- Comment #4 from David Gow ---
I don't think this is python-specific: I was seeing it with C code.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=418065
Bug ID: 418065
Summary: Crash during autocomplete under Wayland.
Product: kdevelop
Version: 5.5.0
Platform: openSUSE RPMs
OS: Linux
Status: REPORTED
Keywords: dr
https://bugs.kde.org/show_bug.cgi?id=401031
David Gow changed:
What|Removed |Added
CC||da...@ingeniumdigital.com
--- Comment #10 from
https://bugs.kde.org/show_bug.cgi?id=401031
David Gow changed:
What|Removed |Added
CC||da...@davidgow.net
--
You are receiving this mail
https://bugs.kde.org/show_bug.cgi?id=408227
--- Comment #8 from David Gow ---
I've filed this against libxkbcommon (and been able to reproduce it with their
interactive-evdev test):
https://github.com/xkbcommon/libxkbcommon/issues/97
--
You are receiving this mail because:
You are watchin
https://bugs.kde.org/show_bug.cgi?id=407221
--- Comment #6 from David Gow ---
Okay, it seems that I spoke too soon: I just got the hang again.
I have better debug symbols now, so here's an updated (example) stacktrace. As
before, it appears to be an infinite loop in KWin::Placement::place
https://bugs.kde.org/show_bug.cgi?id=407221
--- Comment #5 from David Gow ---
I've tried to reproduce this on the latest KWin git (c62650394) over the last
few days, and haven't been able to, so maybe it's fixed. I'd certainly have
expected it to show up by now if it were sti
https://bugs.kde.org/show_bug.cgi?id=408227
--- Comment #4 from David Gow ---
Thanks for pointing me to kxkbrc — I'm unable to reproduce the issue after
deleting it, unless I add multiple keyboard layouts. If there are multiple
layouts configured, I can reproduce the issue — deleting them
https://bugs.kde.org/show_bug.cgi?id=408227
--- Comment #3 from David Gow ---
Created attachment 120539
--> https://bugs.kde.org/attachment.cgi?id=120539&action=edit
kxkbrc which reproduces the problem
This is a kxkbrc which reproduces the problem. Having multiple keyboard layouts
seem
https://bugs.kde.org/show_bug.cgi?id=408227
Bug ID: 408227
Summary: Setting Caps Lock as Compose doesn't disable Caps Lock
functionality
Product: kwin
Version: git master
Platform: Other
OS: Linux
https://bugs.kde.org/show_bug.cgi?id=407221
David Gow changed:
What|Removed |Added
CC||da...@davidgow.net
--- Comment #4 from David Gow
33 matches
Mail list logo