[kwin] [Bug 470266] kwin_wayland crash in QOpenGLContext::shareGroup
https://bugs.kde.org/show_bug.cgi?id=470266 David Gow changed: What|Removed |Added CC||da...@ingeniumdigital.com --- Comment #6 from David Gow --- I have been able to (thus far) reproduce this crash when Alt+Tabbing away from a Steam game properties window after a game data verification completes. The system is running openSUSE Tumbleweed, and has an Intel Arc A380 GPU, as well as the integrated Intel HSW GPU. The former is the default, and is what OpenGL apps including Steam are using. The stack trace STEPS TO REPRODUCE 1. Run Steam in XWayland 2. Right-click on a game (in my case, Age of Empires IV), and select 'Properties' 3. Select 'Installed Files', then 'Verify Integrity of Game Files' 4. Wait for the verification to complete. In my case, the message was '1 file failed to validate and will be reacquired'. 5. Alt+Tab away from the window. kwin_wayland will SIGSEGV OBSERVED RESULT A SIGSEGV in kwin_wayland. The faulting thread stacktrace is: ``` #0 QOpenGLContext::shareGroup() const (this=this@entry=0x0) at kernel/qopenglcontext.cpp:1179 #1 0x7f194ff3f497 in QOpenGLMultiGroupSharedResource::value(QOpenGLContext*) (context=0x0, this=0x7f1950137040 <(anonymous namespace)::Q_QGS_qt_gl_functions_resource::innerFunction()::holder>) at ../../include/QtGui/5.15.12/QtGui/private/../../../../../src/gui/kernel/qopenglcontext_p.h:173 #2 qt_gl_functions(QOpenGLContext*) (context=0x0) at opengl/qopenglfunctions.cpp:191 #3 0x7f194ff3f712 in qopenglfSpecialClearDepthf(GLclampf) (depth=1) at opengl/qopenglfunctions.cpp:2138 #4 0x7f1950bdfc42 in QSGBatchRenderer::Renderer::renderBatches() () at /lib64/libQt5Quick.so.5 #5 0x7f1950be050c in QSGBatchRenderer::Renderer::render() () at /lib64/libQt5Quick.so.5 #6 0x7f1950bc83e0 in QSGRenderer::renderScene(QSGBindable const&) () at /lib64/libQt5Quick.so.5 #7 0x7f1950bc8893 in QSGRenderer::renderScene(unsigned int) () at /lib64/libQt5Quick.so.5 #8 0x7f1950c2a713 in QSGDefaultRenderContext::renderNextFrame(QSGRenderer*, unsigned int) () at /lib64/libQt5Quick.so.5 #9 0x7f1950c99eb9 in QQuickWindowPrivate::renderSceneGraph(QSize const&, QSize const&) () at /lib64/libQt5Quick.so.5 #10 0x7f1950c161d1 in () at /lib64/libQt5Quick.so.5 #11 0x7f1950ca8c05 in QQuickWindow::event(QEvent*) () at /lib64/libQt5Quick.so.5 #12 0x7f194eda51ae in QApplicationPrivate::notify_helper(QObject*, QEvent*) (this=, receiver=0x55765cee0360, e=0x7fffc0335f00) at kernel/qapplication.cpp:3640 #13 0x7f194f6ed938 in QCoreApplication::notifyInternal2(QObject*, QEvent*) (receiver=0x55765cee0360, event=0x7fffc0335f00) at kernel/qcoreapplication.cpp:1064 #14 0x7f194f6edafe in QCoreApplication::sendEvent(QObject*, QEvent*) (receiver=, event=) at kernel/qcoreapplication.cpp:1462 #15 0x7f194fb6c153 in QPlatformWindow::deliverUpdateRequest() (this=) at kernel/qplatformwindow.cpp:796 #16 QPlatformWindow::windowEvent(QEvent*) (this=, event=) at kernel/qplatformwindow.cpp:476 #17 0x7f194edac4ec in QApplication::notify(QObject*, QEvent*) (this=0x7fffc03365b0, receiver=0x55765cee0360, e=0x7fffc0336170) at kernel/qapplication.cpp:2882 #18 0x7f194f6ed938 in QCoreApplication::notifyInternal2(QObject*, QEvent*) (receiver=0x55765cee0360, event=0x7fffc0336170) at kernel/qcoreapplication.cpp:1064 #19 0x7f194f6edafe in QCoreApplication::sendEvent(QObject*, QEvent*) (receiver=, event=) at kernel/qcoreapplication.cpp:1462 #20 0x7f194f745c69 in QTimerInfoList::activateTimers() (this=this@entry=0x55765b562598) at kernel/qtimerinfo_unix.cpp:643 #21 0x7f194f7433ec in QEventDispatcherUNIXPrivate::activateTimers() (this=this@entry=0x55765b562510) at kernel/qeventdispatcher_unix.cpp:249 #22 0x7f194f744110 in QEventDispatcherUNIX::processEvents(QFlags) (this=, flags=...) at kernel/qeventdispatcher_unix.cpp:516 #23 0x55765abae1dd in QUnixEventDispatcherQPA::processEvents(QFlags) (this=, flags=...) at qunixeventdispatcher.cpp:63 #24 0x7f194f6ec3cb in QEventLoop::exec(QFlags) (this=this@entry=0x7fffc0336310, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:69 #25 0x7f194f6f4860 in QCoreApplication::exec() () at ../../include/QtCore/../../src/corelib/global/qflags.h:121 #26 0x7f194fb705dc in QGuiApplication::exec() () at kernel/qguiapplication.cpp:1870 #27 0x7f194eda5125 in QApplication::exec() () at kernel/qapplication.cpp:2832 #28 0x55765aad13aa in main(int, char**) (argc=, argv=) at /usr/src/debug/kwin-5.27.10/src/main_wayland.cpp:628 ``` (I can provide a complete stacktrace of all threads on request, but it looks useless to me.) EXPECTED RESULT The window switcher works. SOFTWARE/OS VERSIONS Operating System: openSUSE Tumbleweed 20240129 KDE Plasma Version: 5.27.10 KDE Frameworks V
[partitionmanager] [Bug 445137] KPM sets flags on GPT partitions with no indication that this is happening and no option to turn it off
https://bugs.kde.org/show_bug.cgi?id=445137 David Gow changed: What|Removed |Added CC||da...@ingeniumdigital.com -- You are receiving this mail because: You are watching all bug changes.
[libksane] [Bug 468053] Skanlite and Skanpage crash (deep in sane-backends) when a net scanner is available
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 this mail because: You are watching all bug changes.
[libksane] [Bug 468053] New: Skanlite and Skanpage crash (deep in sane-backends) when a net scanner is available
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
Platform: openSUSE
OS: Linux
Status: REPORTED
Severity: crash
Priority: NOR
Component: general
Assignee: kare.s...@iki.fi
Reporter: da...@ingeniumdigital.com
Target Milestone: ---
SUMMARY
Both skanlite and skanpage crash on boot when connecting to a saned-based
network scanner. Xsane is able to connect fine.
The stacktrace is:
```
Thread 1 "skanlite" received signal SIGSEGV, Segmentation fault.
__strlen_avx2 () at ../sysdeps/x86_64/multiarch/strlen-avx2.S:76
Downloading 0.01 MB source file
/usr/src/debug/glibc-2.37/string/../sysdeps/x86_64/multiarch/strlen-avx2.S
76 VPCMPEQ (%rdi), %ymm0, %ymm1
Missing separate debuginfos, use: zypper install
skanlite-debuginfo-22.12.3-1.2.x86_64
(gdb) bt
#0 __strlen_avx2 () at ../sysdeps/x86_64/multiarch/strlen-avx2.S:76
#1 0x7fffcc0fb42a in do_authorization (dev=0x555af800, resource=0x58
)
at /usr/src/debug/sane-backends-1.1.1/backend/net.c:650
#2 0x7fffcc0fe2ad in sane_net_control_option (handle=0x55bae6e0,
option=2, action=, value=0x7fffcd80,
info=0x7fffcd24) at
/usr/src/debug/sane-backends-1.1.1/backend/net.c:1792
#3 0x77753b87 in KSaneCore::ListOption::readValue
(this=0x55a5a3a0) at
/usr/src/debug/ksanecore-22.12.3/src/options/listoption.cpp:33
#4 0x777588f8 in KSaneCore::InterfacePrivate::loadDeviceOptions
(this=)
at /usr/src/debug/ksanecore-22.12.3/src/interface_p.cpp:151
#5 0x77f7966f in KSaneIface::KSaneWidget::openDevice
(this=0x55901330, deviceName=...)
at /usr/src/debug/libksane-22.12.3/src/ksanewidget.cpp:293
#6 0x555655fb in Skanlite::Skanlite (parent=0x0, device=...,
this=0x7fffd500) at /usr/src/debug/skanlite-22.12.3/src/skanlite.cpp:198
#7 main (argc=, argv=) at
/usr/src/debug/skanlite-22.12.3/src/main.cpp:84
```
This warning appeared immediately before the crash:
```
[13:18:01.754776] [sanei_wire] sanei_w_array: DECODE: maximum amount of
allocated memory exceeded (limit: 1048576, new allocation: 7008781732, total:
7009830308 bytes)
```
More details from the crash in sane-backends, where reply.resource_to_authorise
is 0x58 for some reason:
```
#2 0x7fffcc0fe2ad in sane_net_control_option (handle=0x55bae6e0,
option=2, action=, value=0x7fffcd80, info=0x7fffcd24) at
/usr/src/debug/sane-backends-1.1.1/backend/net.c:1792
1792 do_authorization (s->hw, reply.resource_to_authorize);
(gdb) list
1787 status = reply.status;
1788 need_auth = (reply.resource_to_authorize != 0);
1789 if (need_auth)
1790{
1791 DBG (3, "sane_control_option: auth required\n");
1792 do_authorization (s->hw, reply.resource_to_authorize);
1793 sanei_w_free (>hw->wire,
1794(WireCodecFunc) sanei_w_control_option_reply,
);
1795
1796 sanei_w_set_dir (>hw->wire, WIRE_DECODE);
(gdb) print reply
$1 = {status = SANE_STATUS_GOOD, info = 2, value_type = 0, value_size = 57,
value = 0x7fffce50, resource_to_authorize = 0x58 }
(gdb) q
```
STEPS TO REPRODUCE
1. Configure the 'net' sane backend. (Uncomment 'net' from
/etc/saned.d/dll.conf, and add the hostname of the saned server to
/etc/saned.d/net.conf)
2. Make sure there is a saned server running. (I'm using Debian armhf
'sane-utils' version 1.0.31-4.1)
3.
OBSERVED RESULT
The crash above when either skanpage or skanlite starts.
EXPECTED RESULT
Like non-ksanecore-based scanning programs, they work without crashing.
SOFTWARE/OS VERSIONS
Operating System: openSUSE Tumbleweed 20230330
KDE Plasma Version: 5.27.3
KDE Frameworks Version: 5.104.0
Qt Version: 5.15.8
Kernel Version: 6.2.8-1-vanilla (64-bit)
Graphics Platform: Wayland
Processors: 4 × Intel® Core™ i7-7560U CPU @ 2.40GHz
Memory: 15.3 Gio of RAM
Graphics Processor: Mesa Intel® Iris® Plus Graphics 640
Manufacturer: Dell Inc.
Product Name: XPS 13 9360
ADDITIONAL INFORMATION
This looks like it's probably a sane-backends or saned issue, but clearly
KSaneCore is doing something to trigger it that Xsane isn't.
--
You are receiving this mail because:
You are watching all bug changes.
[kwin] [Bug 462027] Notification Pop-Up from Steam, causes Steam client to hang Wayland
https://bugs.kde.org/show_bug.cgi?id=462027 David Gow changed: What|Removed |Added CC||da...@ingeniumdigital.com --- Comment #3 from David Gow --- (In reply to Nate Graham from comment #1) > How reproducible is this for you? Does it always happen or only sometimes? > Does it affect all games, or only some? This used to occur sporadically for me (~6–12 months ago), then mysteriously stopped (or became very rare), but then mysteriously started again about ~½ an hour ago, after a reboot and an upgrade of the nVidia drivers (→ 525.53_k6.0.8_1-16.3), fcitx (→5.0.20-1.1), and Qt6 (→6.4.1-1.1) from openSUSE Tumbleweed. It's now happening pretty consistently (there are a lot of pending notifications on Steam, all of which successfully display, then one of the other steam windows will 'freeze'). One notification doesn't seem like it's enough to knock it over (unless it's badly timed), but I'd wager that lots of moving/resizing windows probably does… This has only occurred with nVidia for me, and I think was helped last time by an upgrade (or hack to fix threading bugs) of libnvidia-egl-wayland. I'm currently running version 1.1.11, which should have all of the previously-useful fixes. (I had assumed we were hitting this issue: https://github.com/NVIDIA/egl-wayland/pull/53 ) Stacktrace from steam while it's frozen (only putting the active thread: the others didn't seem hugely useful. It's all in X11/the nVidia driver): > Thread 1 (Thread 0xf7cbeb80 (LWP 9253) "steam"): > #0 __kernel_vsyscall () at ../arch/x86/entry/vdso/vdso32/system_call.S:72 > #1 0xf7b157a7 in __GI___poll (timeout=-1, nfds=1, fds=0xfff68f1c) at > ../sysdeps/unix/sysv/linux/poll.c:29 > #2 __GI___poll (fds=0xfff68f1c, nfds=1, timeout=-1) at > ../sysdeps/unix/sysv/linux/poll.c:26 > #3 0xf7cd2b65 in poll (__timeout=-1, __nfds=1, __fds=0xfff68f1c) at > /usr/include/bits/poll2.h:39 > #4 _xcb_conn_wait (c=0x5840c2a0, vector=0x0, count=0x0, cond= out>) at /usr/src/debug/libxcb-1.15-1.4.i386/src/xcb_conn.c:508 > #5 0xf7cd4c7d in _xcb_conn_wait (count=0x0, vector=0x0, cond=0x58c63dd8, > c=0x5840c2a0) at /usr/src/debug/libxcb-1.15-1.4.i386/src/xcb_conn.c:474 > #6 xcb_wait_for_special_event (c=0x5840c2a0, se=0x58c63dc0) at > /usr/src/debug/libxcb-1.15-1.4.i386/src/xcb_in.c:806 > #7 0xf75160bd in () at /lib/libGLX_nvidia.so.0 > #8 0xf74fa46b in () at /lib/libGLX_nvidia.so.0 > #9 0xf615f6e3 in () at /lib/libnvidia-glcore.so.525.53 > #10 0xf751948c in () at /lib/libGLX_nvidia.so.0 > #11 0xf74e4192 in () at /lib/libGLX_nvidia.so.0 > #12 0xedf85cd7 in () at /home/david/.local/share/Steam/ubuntu12_32/vgui2_s.so > #13 0xedf760f6 in () at /home/david/.local/share/Steam/ubuntu12_32/vgui2_s.so > #14 0xedf85811 in () at /home/david/.local/share/Steam/ubuntu12_32/vgui2_s.so > #15 0xedf8cbec in () at /home/david/.local/share/Steam/ubuntu12_32/vgui2_s.so > #16 0xf1d4408e in () at /home/david/.local/share/Steam/ubuntu12_32/steamui.so > #17 0xf1d46799 in () at /home/david/.local/share/Steam/ubuntu12_32/steamui.so > #18 0xf1d481f0 in () at /home/david/.local/share/Steam/ubuntu12_32/steamui.so > #19 0x5664dc99 in () > #20 0x5664ebae in () > #21 0x56638b30 in () > #22 0xf7a23295 in __libc_start_call_main (main=main@entry=0x56638b00, > argc=argc@entry=1, argv=argv@entry=0xfff6f954) at > ../sysdeps/nptl/libc_start_call_main.h:58 > #23 0xf7a23358 in __libc_start_main_impl (main=0x56638b00, argc=1, > argv=0xfff6f954, init=0x56ab1bb0 <__libc_csu_init>, fini=0x56ab1c20 > <__libc_csu_fini>, rtld_fini=0xf7f6c990 <_dl_fini>, stack_end=0xfff6f94c) at > ../csu/libc-start.c:381 > #24 0x5663d9f5 in _start () System info: Operating System: openSUSE Tumbleweed 20221121 KDE Plasma Version: 5.26.3 KDE Frameworks Version: 5.100.0 Qt Version: 5.15.7 Kernel Version: 6.0.8-1-default (64-bit) Graphics Platform: Wayland Processors: 8 × Intel® Core™ i7-4770K CPU @ 3.50GHz Memory: 31.3 GiB of RAM Graphics Processor: NVIDIA GeForce GTX 1060 3GB/PCIe/SSE2 Manufacturer: Gigabyte Technology Co., Ltd. Product Name: Z87X-UD5H -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 418065] Crash during autocomplete under Wayland.
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 because: You are watching all bug changes.
[plasmashell] [Bug 433460] [Wayland] Automatically chosen scale factor of 200% does not seem to take effect until manually applied
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 between), but shows 200% in system settings. I have to switch to another scale, apply, and switch back to get 200% working again. (And some applications remain a bit 'blurry', not taking the new scale factor into account.) -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 452938] pointer confinement regions misapplied to libdecor decorations
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: 5.17.3-1-vanilla -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 452938] New: pointer confinement regions misapplied to libdecor decorations
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: REPORTED Severity: normal Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: da...@ingeniumdigital.com Target Milestone: --- SUMMARY If an application uses client side decorations as implemented by libdecor[1], when it sets a pointer confinement region using zwp_pointer_constraints_v1_confine_pointer() on the content surface, that region includes the titlebar, not just the content surface. (i.e., location (0,0) is the top-left of the parent surface, not the child surface). This means that the pointer can escape into the titlebar (which was not intended), and the bottom, titlebar-sized area of the window is inaccessible. Weston shows the expected behaviour. Note that libdecor does not use client-side decorations when SSDs are available: the recently-added LIBDECOR_FORCE_CSD=1 environment variable should be used, and hence a recent git version of libdecor. STEPS TO REPRODUCE 1. Get the latest git versions of SDL and libdecor, and build them (and their tests). 2. Set the following environment variables: SDL_VIDEODRIVER=wayland SDL_VIDEO_WAYLAND_PREFER_LIBDECOR=1 LIBDECOR_FORCE_CSD=1 3. Run a program which confines the mouse cursor. For example: ./test/testgl2 --confine-cursor 0,0,640,480 OBSERVED RESULT The pointer is confined to a 640×480 region which includes the titlebar, but not the bottom of the content area. EXPECTED RESULT The pointer is confined to the 640×480-sized content area, but cannot escape into the titlebar. The bottom few pixels of the content area are accessible. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION See also bug #449620, which seems related. I've also seen this occur on the Tomb Raider (2013) game. [1]: https://gitlab.gnome.org/jadahl/libdecor [2]: https://github.com/libsdl-org/SDL -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 448844] [NVIDIA Wayland] Panel stops visually updating after some time, but remains functional and interactive
https://bugs.kde.org/show_bug.cgi?id=448844 David Gow changed: What|Removed |Added CC||da...@ingeniumdigital.com --- Comment #12 from David Gow --- FYI: There is an nVidia/Wayland specific issue with identical symptoms to this, which https://codereview.qt-project.org/c/qt/qtwayland/+/393273 alone doesn't fix. It seems to be due to a bug in libnvidia-egl-wayland: https://github.com/NVIDIA/egl-wayland/issues/52 I can't reproduce the issue with this patch, but can without it: https://github.com/NVIDIA/egl-wayland/pull/53 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 436654] Hovering combined tasks increases CPU load on one core to 80-90%
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 system when hovering over a lot of combined tasks, but it doesn't render the system unusable in the way that it used to. So it's definitely fixed as of 5.24.1 here. Thanks! -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 444962] Some wayland native games in KDE 5.23 open in corner of screen unless I force them to run in xwayland (and in 5.23.3 they open as an invisible window)
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 personally think KWin's older behaviour of sending a valid size in the event is nice, but equally it makes no sense to me that getting a 0×0 configure event should result in SDL resizing the window to 0×0 (and hence crashing, as that's not valid). Given every SDL application is now crashing on startup, this is definitely a bug, but whether its KWin's bug, SDL's bug, or (possibly) both remains to be seen… -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 444962] Some wayland native games in KDE 5.23 open in corner of screen unless I force them to run in xwayland (and in 5.23.3 they open as an invisible window)
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 shouldn't change it). It works fine for me with KWin 5.23.4 and this patch to SDL2: https://github.com/libsdl-org/SDL/pull/5064 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 444962] Some wayland native games in KDE 5.23 open in corner of screen unless I force them to run in xwayland (and in 5.23.3 they open as an invisible window)
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 release: https://invent.kde.org/plasma/kwin/-/commit/325208347c40d7311aea83572b5150ba3750cba9 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 444962] Some wayland native games in KDE 5.23 open in corner of screen unless I force them to run in xwayland (and in 5.23.3 they open as an invisible window)
https://bugs.kde.org/show_bug.cgi?id=444962 David Gow changed: What|Removed |Added CC||da...@ingeniumdigital.com --- Comment #4 from David Gow --- I'm seeing what I think is the same issue with Plasma 5.23.3 on OpenSUSE Tumbleweed with all SDL2 applications when fullscreen. What appears to be happening is that the application is receiving a configure request to resize itself to 1×1, which SDL2 accepts. In my case, due to a scale factor of 2.00, this results in the game rendering to a 2px×2px buffer, which is what shows up in the taskbar thumbnail preview. SDL2 has code to ignore resizes from configure events which try to resize a non-resizable window, but it only takes effect in non-fullscreen modes. I haven't found toggling VSync does anything here: the game gets a 1×1 configure event regardless. Nor am I running applications in Flatpack. Equally, I can reproduce this with the latest main branch of SDL2. As noted, setting SDL_VIDEODRIVER=x11 works around the issue by using XWayland. Excerpts from WAYLAND_DEBUG which illustrate the issue: [449104.573] -> xdg_toplevel@29.set_fullscreen(wl_output@16) [449106.869] wl_display@1.delete_id(27) [449107.012] xdg_toplevel@29.configure(1600, 900, array) [449107.061] xdg_surface@28.configure(65673) [449107.112] -> wl_surface@23.set_buffer_scale(2) […] [449384.857] xdg_toplevel@29.configure(1, 1, array) [449384.874] xdg_surface@28.configure(65674) [449384.887] -> wl_surface@23.set_buffer_scale(2) [449384.899] -> wl_compositor@4.create_region(new id wl_region@32) [449384.909] -> wl_reg...@32.add(0, 0, 1, 1) [449384.929] -> wl_surface@23.set_opaque_region(wl_region@32) [449384.938] -> wl_region@32.destroy() [449384.944] -> xdg_surface@28.set_window_geometry(0, 0, 1, 1) [449384.963] -> xdg_surface@28.ack_configure(65674) -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 389298] GZDoom (SDL2), at least, run with SDL_VIDEODRIVER=wayland under kwin_wayland experience alpha transparency bleeding weirdness
https://bugs.kde.org/show_bug.cgi?id=389298 David Gow changed: What|Removed |Added CC||da...@ingeniumdigital.com --- Comment #9 from David Gow --- This sounds like it's a well-known issue with the game / SDL's understanding of rendering to buffers with alpha channels. Basically, on X11 the alpha channel was ignored, and on Wayland it's used (to be able to provide nicely alpha-blended windows with interesting shapes, etc). There's been an EGL extension proposed to allow SDL to request the alpha channel is ignored: https://www.khronos.org/registry/EGL/extensions/EXT/EGL_EXT_present_opaque.txt SDL already has support for this extension, though it's not yet part of a release: https://github.com/libsdl-org/SDL/pull/4646 There's an in-progress implementation for Mesa: https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/12373 So I doubt this is actually a KWin bug, but I could be wrong… -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 433460] [Wayland] Automatically chosen scale factor of 200% does not seem to take effect until manually applied
https://bugs.kde.org/show_bug.cgi?id=433460 David Gow changed: What|Removed |Added CC||da...@ingeniumdigital.com --- Comment #10 from David Gow --- I reported what I think is this issue to openSUSE some time ago: https://bugzilla.opensuse.org/show_bug.cgi?id=1186893 It's still reproducible on 5.22.5, even though openSUSE has changed how it handles Plasma sessions a bit since I originally reported it. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 436654] Task Manager crashes when hovering combined tasks
https://bugs.kde.org/show_bug.cgi?id=436654 David Gow changed: What|Removed |Added CC||da...@ingeniumdigital.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 439578] New: Maximize button sometimes appears even in non-resizable windows with xdg-decoration
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 Status: REPORTED Severity: normal Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: da...@ingeniumdigital.com Target Milestone: --- SUMMARY A wayland window using xdg-decoration to request server-side decorations will sometimes show a (non-functional) maximize button in the title bar for windows which are not resizable. This seems to occur if the decoration is created before set_min_size() and set_max_size() are called, but I've been unable thus far to conclusively confirm that. This affects libdecor, which always creates an xdg-decoration object when a window is first created, and then simply toggles the mode later: https://gitlab.gnome.org/jadahl/libdecoration/-/blob/82e8653af75348e5fcad4f490217c25959bb762a/src/libdecor.c#L497 SDL has worked around the issue in this commit: https://github.com/libsdl-org/SDL/commit/efbb6ff9d70e791d755c9ece95f248d1055b10ab There's some further discussion in the SDL issue for libdecor support: https://github.com/libsdl-org/SDL/pull/4068#issuecomment-874626945 STEPS TO REPRODUCE 1. Build a version of SDL with libdecor support from this merge request: https://github.com/libsdl-org/SDL/pull/4068 - Note that you'll need to build libdecor first. 2. Run the SDL testwm2 app with this version of SDL. The maximize button should be visible, but useless. 3. Running the same testwm2 app with libdecor disabled will correctly not have a maximise button. SOFTWARE/OS VERSIONS Linux/KDE Plasma: openSUSE Tumbleweed (available in About System) KDE Plasma Version: 5.22.2 KDE Frameworks Version: 5.15.2 Qt Version: 5.83.0 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 428499] Frame callbacks not send on 'empty' commits
https://bugs.kde.org/show_bug.cgi?id=428499 David Gow changed: What|Removed |Added CC||da...@ingeniumdigital.com -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 401031] Font thumbnailer crashes on Wayland
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 calling Xft functions even when not running under X11: Thread 1 (Thread 0x7fea401ec840 (LWP 17934)): [KCrash Handler] #4 0x7fea42a96d63 in XAddExtension (dpy=dpy@entry=0x559ab935a140) at InitExt.c:73 #5 0x7fea1a62f9ed in _XftDisplayInfoGet (dpy=0x559ab935a140, createIfNecessary=) at xftdpy.c:91 #6 0x7fea1a633785 in _XftDisplayInfoGet (createIfNecessary=1, dpy=0x7ffdd2157620) at xftdpy.c:85 #7 XftFontInfoFill (dpy=dpy@entry=0x559ab935a140, pattern=pattern@entry=0x559ab9a74290, fi=fi@entry=0x7ffdd2157620) at xftfreetype.c:367 #8 0x7fea1a633bac in XftFontOpenPattern (dpy=0x559ab935a140, pattern=0x559ab9a74290) at xftfreetype.c:1015 #9 0x7fea208da144 in KFI::CFcEngine::queryFont() () from /usr/lib64/libkfontinstui.so.5 [... truncated ...] -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 418065] Crash during autocomplete under Wayland.
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.
[kdevelop] [Bug 418065] New: Crash during autocomplete under Wayland.
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: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdevelop-bugs-n...@kde.org Reporter: da...@ingeniumdigital.com Target Milestone: --- Application: kdevelop (5.5.0) Qt Version: 5.14.1 Frameworks Version: 5.67.0 Operating System: Linux 5.5.4-1-vanilla x86_64 Windowing system: Wayland Distribution: "openSUSE Tumbleweed" -- Information about the crash: - What I was doing when the application crashed: The crash occurs sporadically when autocomplete appears. Usually, upon restarting, the same autocomplete window will work fine, but a future one will crash KDevelop. - Custom settings of the application: Running under wayland. The crash can be reproduced sometimes. -- Backtrace: Application: KDevelop (kdevelop), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f9af178eac0 (LWP 24336))] Thread 18 (Thread 0x7f9a97fff700 (LWP 24509)): #0 0x7f9aff2ed795 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f9b01df223b in QWaitConditionPrivate::wait (deadline=..., this=0x55a993517660) at thread/qwaitcondition_unix.cpp:146 #2 QWaitCondition::wait (this=, mutex=0x55a9934e6d00, deadline=...) at thread/qwaitcondition_unix.cpp:225 #3 0x7f9b01df22f9 in QWaitCondition::wait (this=0x55a9934e6c68, mutex=0x55a9934e6d00, time=) at ../../include/QtCore/../../src/corelib/kernel/qdeadlinetimer.h:68 #4 0x7f9afe8766b0 in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*, bool, bool, bool) () from /usr/lib64/libKF5ThreadWeaver.so.5 #5 0x7f9afe876a1a in ?? () from /usr/lib64/libKF5ThreadWeaver.so.5 #6 0x7f9afe86ecce in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () from /usr/lib64/libKF5ThreadWeaver.so.5 #7 0x7f9afe876a71 in ?? () from /usr/lib64/libKF5ThreadWeaver.so.5 #8 0x7f9afe86ecce in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () from /usr/lib64/libKF5ThreadWeaver.so.5 #9 0x7f9afe876a71 in ?? () from /usr/lib64/libKF5ThreadWeaver.so.5 #10 0x7f9afe86ecce in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () from /usr/lib64/libKF5ThreadWeaver.so.5 #11 0x7f9afe876a71 in ?? () from /usr/lib64/libKF5ThreadWeaver.so.5 #12 0x7f9afe86ecce in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () from /usr/lib64/libKF5ThreadWeaver.so.5 #13 0x7f9afe876a71 in ?? () from /usr/lib64/libKF5ThreadWeaver.so.5 #14 0x7f9afe86ecce in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () from /usr/lib64/libKF5ThreadWeaver.so.5 #15 0x7f9afe876a71 in ?? () from /usr/lib64/libKF5ThreadWeaver.so.5 #16 0x7f9afe86ecce in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () from /usr/lib64/libKF5ThreadWeaver.so.5 #17 0x7f9afe876a71 in ?? () from /usr/lib64/libKF5ThreadWeaver.so.5 #18 0x7f9afe86ecce in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () from /usr/lib64/libKF5ThreadWeaver.so.5 #19 0x7f9afe876a71 in ?? () from /usr/lib64/libKF5ThreadWeaver.so.5 #20 0x7f9afe86ecce in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () from /usr/lib64/libKF5ThreadWeaver.so.5 #21 0x7f9afe876a71 in ?? () from /usr/lib64/libKF5ThreadWeaver.so.5 #22 0x7f9afe86ecce in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () from /usr/lib64/libKF5ThreadWeaver.so.5 #23 0x7f9afe876a71 in ?? () from /usr/lib64/libKF5ThreadWeaver.so.5 #24 0x7f9afe86ecce in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () from /usr/lib64/libKF5ThreadWeaver.so.5 #25 0x7f9afe87609b in ThreadWeaver::Thread::run() () from /usr/lib64/libKF5ThreadWeaver.so.5 #26 0x7f9b01dec6f8 in QThreadPrivate::start (arg=0x7f9a900032e0) at thread/qthread_unix.cpp:342 #27 0x7f9aff2e6efa in start_thread () from /lib64/libpthread.so.0 #28 0x7f9b03a5d3bf in clone () from /lib64/libc.so.6 Thread 17 (Thread 0x7f9aa4de2700 (LWP 24508)): #0 0x7f9aff2ed795 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f9b01df223b in QWaitConditionPrivate::wait (deadline=..., this=0x55a993517660) at thread/qwaitcondition_unix.cpp:146 #2 QWaitCondition::wait (this=, mutex=0x55a9934e6d00, deadline=...) at thread/qwaitcondition_unix.cpp:225 #3 0x7f9b01df22f9 in QWaitCondition::wait (this=0x55a9934e6c68, mutex=0x55a9934e6d00, time=) at ../../include/QtCore/../../src/corelib/kernel/qdeadlinetimer.h:68 #4 0x7f9afe8766b0 in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*, bool, bool, bool) () from
[systemsettings] [Bug 401031] Font thumbnailer crashes on Wayland
https://bugs.kde.org/show_bug.cgi?id=401031 David Gow changed: What|Removed |Added CC||da...@ingeniumdigital.com --- Comment #10 from David Gow --- For what it's worth, this is still happening with Plasma 5.18 (on OpenSUSE Tumbleweed) Stacktrace is basically the same (I've only included the relevant thread here:) Thread 1 (Thread 0x7fda93445580 (LWP 18086)): [KCrash Handler] #6 0x7fda95a5b313 in XAddExtension (dpy=dpy@entry=0x55ada1f26e60) at InitExt.c:73 #7 0x7fda7c0422dd in _XftDisplayInfoGet (createIfNecessary=, dpy=0x55ada1f26e60) at xftdpy.c:91 #8 _XftDisplayInfoGet (dpy=dpy@entry=0x55ada1f26e60, createIfNecessary=createIfNecessary@entry=1) at xftdpy.c:62 #9 0x7fda7c04423e in XftFontInfoFill (dpy=dpy@entry=0x55ada1f26e60, pattern=pattern@entry=0x55ada25dc6a0, fi=fi@entry=0x7ffd37fa90f0) at xftfreetype.c:367 #10 0x7fda7c04521f in XftFontOpenPattern (dpy=0x55ada1f26e60, pattern=pattern@entry=0x55ada25dc6a0) at xftfreetype.c:1015 #11 0x7fda8c00837d in KFI::CFcEngine::getFont (this=this@entry=0x55ada252fdd8, size=size@entry=8) at /usr/src/debug/plasma5-desktop-5.18.0-3.1.x86_64/kcms/kfontinst/lib/FcEngine.cpp:1299 #12 0x7fda8c008602 in KFI::CFcEngine::queryFont (this=this@entry=0x55ada252fdd8) at /usr/src/debug/plasma5-desktop-5.18.0-3.1.x86_64/kcms/kfontinst/lib/FcEngine.cpp:1233 #13 0x7fda8c008718 in KFI::CFcEngine::getSizes (this=0x55ada252fdd8) at /usr/src/debug/plasma5-desktop-5.18.0-3.1.x86_64/kcms/kfontinst/lib/FcEngine.cpp:1391 #14 KFI::CFcEngine::getSizes (this=this@entry=0x55ada252fdd8) at /usr/src/debug/plasma5-desktop-5.18.0-3.1.x86_64/kcms/kfontinst/lib/FcEngine.cpp:1383 #15 0x7fda8c00ad71 in KFI::CFcEngine::draw (this=this@entry=0x55ada252fdd8, name=..., style=style@entry=4294967295, faceNo=faceNo@entry=0, txt=..., bgnd=..., w=256, h=256, thumb=true, range=..., chars=0x0) at /usr/src/debug/plasma5-desktop-5.18.0-3.1.x86_64/kcms/kfontinst/lib/FcEngine.cpp:876 #16 0x7fda8c01476f in KFI::CFontThumbnail::create (this=0x55ada252fdd0, path=..., width=128, height=128, img=...) at /usr/include/qt5/QtGui/qbrush.h:159 #17 0x7fda9156f06c in ThumbnailProtocol::createSubThumbnail (segmentHeight=34, segmentWidth=54, filePath=..., thumbnail=..., this=0x7ffd37fa96e0) at /usr/src/debug/kio-extras5-19.12.2-2.1.x86_64/thumbnail/thumbnail.cpp:727 #18 ThumbnailProtocol::drawSubThumbnail (this=this@entry=0x7ffd37fa9c20, p=..., filePath=..., width=width@entry=54, height=height@entry=34, xPos=xPos@entry=9, yPos=38, frameWidth=2) at /usr/src/debug/kio-extras5-19.12.2-2.1.x86_64/thumbnail/thumbnail.cpp:759 #19 0x7fda9156fb57 in ThumbnailProtocol::thumbForDirectory (this=this@entry=0x7ffd37fa9c20, directory=...) at /usr/src/debug/kio-extras5-19.12.2-2.1.x86_64/thumbnail/thumbnail.cpp:562 #20 0x7fda9157152e in ThumbnailProtocol::get (this=0x7ffd37fa9c20, url=...) at /usr/src/debug/kio-extras5-19.12.2-2.1.x86_64/thumbnail/thumbnail.cpp:238 #21 0x7fda9164278e in KIO::SlaveBase::dispatch (this=0x7ffd37fa9c20, command=67, data=...) at /usr/src/debug/kio-5.67.0-1.1.x86_64/src/core/slavebase.cpp:1197 #22 0x7fda91649a56 in KIO::SlaveBase::dispatchLoop (this=this@entry=0x7ffd37fa9c20) at /usr/src/debug/kio-5.67.0-1.1.x86_64/src/core/slavebase.cpp:338 #23 0x7fda91572629 in kdemain (argc=, argv=0x55ada1f105b0) at /usr/src/debug/kio-extras5-19.12.2-2.1.x86_64/thumbnail/thumbnail.cpp:138 #24 0x55ada0ef4bcb in launch (argc=4, _name=0x55ada1f10c98 "/usr/lib64/qt5/plugins/kf5/kio/thumbnail.so", args=, cwd=, envc=0, envs=0x55ada1f10d3e "", reset_env=false, tty=0x0, avoid_loops=false, startup_id_str=0x55ada0ef7175 "0") at /usr/src/debug/kinit-5.67.0-1.2.x86_64/src/kdeinit/kinit.cpp:704 #25 0x55ada0ef5df8 in handle_launcher_request (sock=, who=) at /usr/src/debug/kinit-5.67.0-1.2.x86_64/src/kdeinit/kinit.cpp:1142 #26 0x55ada0ef67d4 in handle_requests (waitForPid=0) at /usr/src/debug/kinit-5.67.0-1.2.x86_64/src/kdeinit/kinit.cpp:1335 #27 0x55ada0ef164d in main (argc=5, argv=) at /usr/src/debug/kinit-5.67.0-1.2.x86_64/src/kdeinit/kinit.cpp:1773 [Inferior 1 (process 18086) detached] -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 401031] Font thumbnailer crashes on Wayland
https://bugs.kde.org/show_bug.cgi?id=401031 David Gow changed: What|Removed |Added CC||da...@davidgow.net -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 408227] Setting Caps Lock as Compose doesn't disable Caps Lock functionality
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 watching all bug changes.
[kwin] [Bug 407221] Random KWin hang on VirtualDesktop RefCount
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::placeSmart(): #0 0x7f9e7d2211d4 in KWin::Client::metaObject() const (this=) at /home/david/kde/build/kwin/kwin_autogen/EWIEGA46WW/moc_client.cpp:264 #1 0x7f9e7c1dab69 in QMetaObject::cast(QObject const*) const () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #2 0x7f9e7d0d9c4d in qobject_cast(QObject*) (object=) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qobject.h:499 #3 0x7f9e7d0d9c4d in KWin::Placement::placeSmart(KWin::AbstractClient*, QRect const&, KWin::Placement::Policy) (this=, c=c@entry=0x5623225705c0, area=...) at /home/david/kde/src/kwin/placement.cpp:243 #4 0x7f9e7d0db9d8 in KWin::Placement::place(KWin::AbstractClient*, QRect&, KWin::Placement::Policy, KWin::Placement::Policy) (this=, c=0x5623225705c0, area=..., policy=, nextPlacement=) at /home/david/kde/src/kwin/placement.cpp:106 #5 0x7f9e7d1ca38d in KWin::ShellClient::placeIn(QRect&) (this=this@entry=0x5623225705c0, area=...) at /home/david/kde/src/kwin/placement.h:107 #6 0x7f9e7d1ca849 in KWin::ShellClient::finishInit() (this=0x5623225705c0) at /home/david/kde/src/kwin/shell_client.cpp:378 #7 0x7f9e7c1fb563 in QMetaObject::activate(QObject*, int, int, void**) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7f9e77e0381e in ffi_call_unix64 () at /usr/lib/x86_64-linux-gnu/libffi.so.6 #9 0x7f9e77e031ef in ffi_call () at /usr/lib/x86_64-linux-gnu/libffi.so.6 #10 0x7f9e79bc88fd in () at /usr/lib/x86_64-linux-gnu/libwayland-server.so.0 #11 0x7f9e79bc5379 in () at /usr/lib/x86_64-linux-gnu/libwayland-server.so.0 #12 0x7f9e79bc6942 in wl_event_loop_dispatch () at /usr/lib/x86_64-linux-gnu/libwayland-server.so.0 #13 0x7f9e7cd083ae in KWayland::Server::Display::Private::dispatch() (this=) at /home/david/kde/src/kwayland/src/server/display.cpp:147 #14 0x7f9e7c1fb563 in QMetaObject::activate(QObject*, int, int, void**) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #15 0x7f9e7c206bd9 in QSocketNotifier::activated(int, QSocketNotifier::QPrivateSignal) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #16 0x7f9e7c206f21 in QSocketNotifier::event(QEvent*) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #17 0x7f9e7c5e8551 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #18 0x7f9e7c5ef930 in QApplication::notify(QObject*, QEvent*) () at /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #19 0x7f9e7c1d18e9 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #20 0x7f9e7c76 in QEventDispatcherUNIXPrivate::activateSocketNotifiers() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #21 0x7f9e7c222587 in QEventDispatcherUNIX::processEvents(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #22 0x7f9e74cac65d in QUnixEventDispatcherQPA::processEvents(QFlags) () at /home/david/kde/usr/lib/x86_64-linux-gnu/plugins/platforms/KWinQpaPlugin.so #23 0x7f9e7c1d05bb in QEventLoop::exec(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #24 0x7f9e7c1d85e2 in QCoreApplication::exec() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #25 0x56231f48c25e in main(int, char**) (argc=, argv=) at /home/david/kde/src/kwin/main_wayland.cpp:676 Sorry for the spam — let me know if there's anything more I should be looking at. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 407221] Random KWin hang on VirtualDesktop RefCount
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 still happening, though my environment for git KWin is slightly different (started from a VT instead of SDDM). So… maybe fixed? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 408227] Setting Caps Lock as Compose doesn't disable Caps Lock functionality
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 fixes it.
For example, creating a US English ("us") and Japanese ("jp") keyboard layout,
allows me to reproduce the issue from within the us layout. Disabling the
"Configure Layouts" checkbox doesn't fix the issue by itself, the layouts seem
to have to be deleted.
--
You are receiving this mail because:
You are watching all bug changes.
[kwin] [Bug 408227] Setting Caps Lock as Compose doesn't disable Caps Lock functionality
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=edit kxkbrc which reproduces the problem This is a kxkbrc which reproduces the problem. Having multiple keyboard layouts seems to be a prerequisite — I'm unable to reproduce the issue from a clean kxkbrc by just following the instructions in the original report. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 408227] New: Setting Caps Lock as Compose doesn't disable Caps Lock functionality
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 Status: REPORTED Severity: normal Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: da...@davidgow.net Target Milestone: --- SUMMARY When running KDE as a Wayland session, setting "Position of Compose key" to "Caps Lock" in kcm_keyboard causes the Caps Lock key to work as _both_ Compose and Caps Lock — pressing it toggles the Caps Lock LED and inverts the case of characters, but also activates the "dead key" nature of Compose. Additionally, disabling Caps Lock specifically with "Caps Lock behaviour"→"Caps Lock is disabled" doesn't seem to work. Setting "Caps Lock is also a Ctrl" seems to successfully make Caps Lock a Ctrl (in addition to Compose), but this is still suboptimal. These all work as expected under X11. STEPS TO REPRODUCE 1. Run a Plasma Wayland session. 2. Set "Position of Compose Key" to "Caps Lock" in kcm_keyboard's "Advanced" tab. 3. Press Caps Lock: the LED will toggle, and Caps Lock mode will activate. OBSERVED RESULT Caps Lock is enabled in addition to the Compose key functioning. Caps Lock cannot be disabled with the "Caps Lock behaviour"→"Caps Lock is disabled" setting. EXPECTED RESULT Setting "Position of Compose Key" to "Caps Lock" disables Caps Lock. Caps Lock can be disabled with the "Caps Lock is disabled" setting. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Kubuntu 19.04 (kernel 5.0.0-15-lowlatency, libxkbcommon0: 0.8.2-1, xkb-data 2.23.1-1ubuntu1.18.10.1) (available in About System) KDE Plasma Version: 5.16.80 (kwin git c6265039...), also happens with stock Kubuntu KDE Frameworks Version: 5.56.0 Qt Version: 5.12.2 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 407221] Random KWin hang on VirtualDesktop RefCount
https://bugs.kde.org/show_bug.cgi?id=407221 David Gow changed: What|Removed |Added CC||da...@davidgow.net --- Comment #4 from David Gow --- I'm getting similar, frequent hangs with the kubuntu beta PPA (which claims to be KWin 5.15.90), which appear to point to an infinite loop somewhere in KWin::Placement::placeSmart(). This only ever occurs when a new window is being opened, though I've never been able to get it to work consistently. I haven't seen a stacktrace that goes as far as the VirtualDesktop RefCount thus far, but have seen them in AbstractClient::isCurrentTab(). It seems to mostly occurs just in the KWin::Placement::placeSmart() function directly. Note that this didn't occur with the normal Kubuntu 19.04 build of KWin (which seems to be 5.15.4). Alas, I don't have full debug symbols available at the moment, but here's an example stacktrace anyway: #0 0x7fafa5258d2e in KWin::Placement::placeSmart(KWin::AbstractClient*, QRect const&, KWin::Placement::Policy) () at /usr/lib/x86_64-linux-gnu/libkwin.so.5 #1 0x7fafa525aa18 in KWin::Placement::place(KWin::AbstractClient*, QRect&, KWin::Placement::Policy, KWin::Placement::Policy) () at /usr/lib/x86_64-linux-gnu/libkwin.so.5 #2 0x7fafa5348c7d in KWin::ShellClient::placeIn(QRect&) () at /usr/lib/x86_64-linux-gnu/libkwin.so.5 #3 0x7fafa5348dd1 in KWin::ShellClient::finishInit() () at /usr/lib/x86_64-linux-gnu/libkwin.so.5 #4 0x7fafa4407563 in QMetaObject::activate(QObject*, int, int, void**) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7fafa002d81e in ffi_call_unix64 () at/usr/lib/x86_64-linux-gnu/libffi.so.6 #6 0x7fafa002d1ef in ffi_call () at /usr/lib/x86_64-linux-gnu/libffi.so.6 #7 0x7fafa1de68fd in () at /usr/lib/x86_64-linux-gnu/libwayland-server.so.0 #8 0x7fafa1de3379 in () at /usr/lib/x86_64-linux-gnu/libwayland-server.so.0 #9 0x7fafa1de4942 in wl_event_loop_dispatch () at /usr/lib/x86_64-linux-gnu/libwayland-server.so.0 #10 0x7fafa4f05f2e in KWayland::Server::Display::Private::dispatch() () at /usr/lib/x86_64-linux-gnu/libKF5WaylandServer.so.5 #11 0x7fafa4407563 in QMetaObject::activate(QObject*, int, int, void**) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #12 0x7fafa4412bd9 in QSocketNotifier::activated(int, QSocketNotifier::QPrivateSignal) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #13 0x7fafa4412f21 in QSocketNotifier::event(QEvent*) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #14 0x7fafa47f4551 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #15 0x7fafa47fb930 in QApplication::notify(QObject*, QEvent*) () at /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #16 0x7fafa43dd8e9 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #17 0x7fafa442e276 in QEventDispatcherUNIXPrivate::activateSocketNotifiers() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #18 0x7fafa442e587 in QEventDispatcherUNIX::processEvents(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #19 0x7faf9ced762d in () at /usr/lib/x86_64-linux-gnu/qt5/plugins/platforms/KWinQpaPlugin.so #20 0x7fafa43dc5bb in QEventLoop::exec(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #21 0x7fafa43e45e2 in QCoreApplication::exec() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 Hope that helps. -- You are receiving this mail because: You are watching all bug changes.
