[kwin] [Bug 479387] Crash in KWin::Window::constrainFrameSize
https://bugs.kde.org/show_bug.cgi?id=479387
Miren Radia changed:
What|Removed |Added
Status|RESOLVED|REOPENED
Resolution|DUPLICATE |---
--- Comment #6 from Miren Radia ---
(In reply to Zamundaaa from comment #5)
>
> *** This bug has been marked as a duplicate of bug 478269 ***
Are we sure this is a duplicate of bug 478269? Whilst I agree that the tops of
the stack traces look the same (#0-#10), they look a bit different further down
the stack and I think the fix for bug 478269 may have been made where they
differ.
The fixes for bug 478269 seem to be in wayland/xdgshell and xdgshellwindow.
Code from these components is in the stack trace for bug 478269:
#15 0x7f06087468fd in KWin::XdgSurfaceWindow::handleNextWindowGeometry()
(this=0x55afdb3e04f0) at
/usr/src/debug/kwin/kwin-5.27.10/src/xdgshellwindow.cpp:242
boundingGeometry = {xp = 0, yp = 0, w = 58, h = 27}
frameGeometry = {xp = 0, yp = 0, w = 58, h = 27}
#16 KWin::XdgSurfaceWindow::handleCommit() (this=0x55afdb3e04f0) at
/usr/src/debug/kwin/kwin-5.27.10/src/xdgshellwindow.cpp:169
However, I don't see anything from these components in my stack trace for this
bug.
Sorry if I'm being completely naive about this as I'm not too familiar with KDE
development. I just really want to make sure the fix for this bug is released
asap as it's really inconvenient.
--
You are receiving this mail because:
You are watching all bug changes.
[kwin] [Bug 479387] Crash in KWin::Window::constrainFrameSize
https://bugs.kde.org/show_bug.cgi?id=479387 --- Comment #3 from Miren Radia --- (In reply to David Edmundson from comment #2) > It's an assert, presumably min > max or vice versa. > > Miren this probably means you have some window rules set somewhere that > might be causing this. I don't have any Window Rules under System Settings -> Window Management -> Window Rules and I don't remember setting any elsewhere. Anywhere else I should check? I tried disabling some non-default KWin scripts (specifically "Sticky Window Snapping" and "Ultrawide Windows") but that didn't seem to help either. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 479387] New: kwin_wayland crashes when thunderbolt dock with external monitors connected
https://bugs.kde.org/show_bug.cgi?id=479387 Bug ID: 479387 Summary: kwin_wayland crashes when thunderbolt dock with external monitors connected Classification: Plasma Product: kwin Version: 5.27.10 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: miren_ra...@yahoo.co.uk Target Milestone: --- Created attachment 164663 --> https://bugs.kde.org/attachment.cgi?id=164663=edit gdb session with backtrace SUMMARY Most times I connect my laptop to a Dell WD22TB4 thunderbolt dock with 2 external screens (both 4K), kwin_wayland crashes. I can consistently reproduce the problem using the steps below and usually reproduce it if I connect the laptop to the dock some time after logging in. For context, this dock is at work. Before the break over the holidays, I had no issues with this set up and only started experiencing it after I came back to work. During this break, I upgraded the KDE Plasma stack from 5.27.9 to 5.27.10 (and related KDE framework dependencies) which is where I suspect the problem comes from. My normal screen set up with the dock connected is to have both monitors enabled at 125% scaling (side-by-side) and to disable the laptop screen. I have tried modifying this set up by enabling the laptop screen as well and setting the display scaling on the external screens to 100% but I still have the same problem. I have also tried disconnecting 1 screen. STEPS TO REPRODUCE 1. Turn on laptop with dock connected and external monitors to dock. 2. Log into my account from SDDM login screen. OBSERVED RESULT kwin_wayland crashes almost immediately and I am eventually left with black screens and a cursor. EXPECTED RESULT No crash. SOFTWARE/OS VERSIONS Operating System: Fedora Linux 39 KDE Plasma Version: 5.27.10 KDE Frameworks Version: 5.111.0 Qt Version: 5.15.11 Kernel Version: 6.6.8-200.fc39.x86_64 (64-bit) Graphics Platform: Wayland Processors: 16 × 12th Gen Intel® Core™ i7-1260P Memory: 31.1 GiB of RAM Graphics Processor: Mesa Intel® Graphics Manufacturer: Framework Product Name: Laptop (12th Gen Intel Core) System Version: A6 ADDITIONAL INFORMATION Please find a stack trace generated from the coredump using gdb attached. Please let me know if there is any further information I can provide to help debug this. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 468129] Be smarter about finding the app icon like Plasmashell does for apps that set their desktop files incorrectly
https://bugs.kde.org/show_bug.cgi?id=468129 Miren Radia changed: What|Removed |Added CC||miren_ra...@yahoo.co.uk -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 456210] Under certain circumstances when using multiple monitors, "unlock" button is clickable but does nothing
https://bugs.kde.org/show_bug.cgi?id=456210 Miren Radia changed: What|Removed |Added CC|miren_ra...@yahoo.co.uk | -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 465790] Resizing an Aurorae-decorated window leads to malformed decorations
https://bugs.kde.org/show_bug.cgi?id=465790 --- Comment #34 from Miren Radia --- I should have added that it happens for me sometimes when I move windows between my 2 monitors (1x 2256x1504 laptop screen + 1x 3840x2160 external monitor both at 100% scaling) *after* they have been quick-tiled (e.g. to the right of the screen). However, it definitely isn't consistent. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 465790] Resizing an Aurorae-decorated window leads to malformed decorations
https://bugs.kde.org/show_bug.cgi?id=465790 --- Comment #28 from Miren Radia --- I can reproduce this problem on my multi-monitor setup (1x 2256x1504 laptop screen + 1x 3840x2160 external monitor both at 100% scaling) using the WhiteSur-dark theme (https://github.com/vinceliuice/WhiteSur-kde). It seems to happen mostly when I move windows from one monitor to the other (or I disconnect the external monitor). My setup is as follows: Operating System: Fedora Linux 37 KDE Plasma Version: 5.27.2 KDE Frameworks Version: 5.103.0 Qt Version: 5.15.8 Kernel Version: 6.1.14-200.fc37.x86_64 (64-bit) Graphics Platform: Wayland Processors: 16 × 12th Gen Intel® Core™ i7-1260P Memory: 31.1 GiB of RAM Graphics Processor: Mesa Intel® Graphics Manufacturer: Framework Product Name: Laptop (12th Gen Intel Core) System Version: A6 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 465790] Resizing an Aurorae-decorated window leads to malformed decorations
https://bugs.kde.org/show_bug.cgi?id=465790 Miren Radia changed: What|Removed |Added CC||miren_ra...@yahoo.co.uk -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 456210] Cannot unlock screen when using multiple monitors
https://bugs.kde.org/show_bug.cgi?id=456210 --- Comment #54 from Miren Radia --- I think this is fixed for me as of KDE Plasma 5.26.4. I no longer see the unlock screen after authenticating with my fingerprint and it unlocks straight away (probably the change in this MR: https://invent.kde.org/plasma/plasma-workspace/-/merge_requests/2349). I won't change the status in case other people are still affected. -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 456210] Cannot unlock screen when using multiple monitors
https://bugs.kde.org/show_bug.cgi?id=456210 --- Comment #46 from Miren Radia --- I have an alternative workaround (which has yet to fail me) rather than changing to a different TTY and using loginctl. I have fingerprint unlocking enabled but instead of using my one registered finger which results in the issue, I use the wrong one until it gives up (3 attempts). It will say "Failed to match fingerprint" but then I use my password instead and it unlocks successfully. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 424485] GDbus-DBusMenu-Proxy does not work for GTK Wayland apps
https://bugs.kde.org/show_bug.cgi?id=424485 Miren Radia changed: What|Removed |Added CC||miren_ra...@yahoo.co.uk -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 457184] Kate crashes everytime when opening settings
https://bugs.kde.org/show_bug.cgi?id=457184 Miren Radia changed: What|Removed |Added CC||miren_ra...@yahoo.co.uk --- Comment #1 from Miren Radia --- I have the same problem (although DrKonqi doesn't seem to pick it up for me) with the following setup: OS: Fedora 36 KDE Plasma: 5.25.4 KDE Frameworks: 5.96.0 Qt: 5.15.5 Kernel: 5.18.16-200.fc36.x86_64 Graphics: Wayland When, I launch kate from a terminal and open Settings -> Configure Kate... to cause the crash, I get the following output QSocketNotifier: Can only be used with threads started with QThread qt.qpa.wayland: Wayland does not support QWindow::requestActivate() KCrash: Application 'kate' crashing... The Wayland connection experienced a fatal error: Bad file descriptor -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 456210] Cannot unlock screen when using multiple monitors
https://bugs.kde.org/show_bug.cgi?id=456210 --- Comment #38 from Miren Radia --- I still have this bug on a system with the following setup: OS: Fedora 36 KDE Plasma: 5.25.4 KDE Frameworks: 5.96.0 Qt: 5.15.5 Kernel: 5.18.16-200.fc36.x86_64 Graphics Platform: Wayland I observe a similar `journalctl` output as provided by Johan Sköld in comment 35. -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 456210] Cannot unlock screen when using multiple monitors
https://bugs.kde.org/show_bug.cgi?id=456210 Miren Radia changed: What|Removed |Added CC||miren_ra...@yahoo.co.uk -- You are receiving this mail because: You are watching all bug changes.
[kamoso] [Bug 447270] New: Kamoso segfaults when switching camera
https://bugs.kde.org/show_bug.cgi?id=447270 Bug ID: 447270 Summary: Kamoso segfaults when switching camera Product: kamoso Version: unspecified Platform: Ubuntu Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: aleix...@kde.org Reporter: miren_ra...@yahoo.co.uk Target Milestone: --- Application: kamoso (19.12.3) Qt Version: 5.12.8 Frameworks Version: 5.68.0 Operating System: Linux 5.11.0-43-generic x86_64 Windowing system: X11 Distribution: Ubuntu 20.04.3 LTS -- Information about the crash: - What I was doing when the application crashed: I clicked "Configure Kamoso" and switched from the default "Cameras" option, "Integrated_Webcam_HD" (my laptop's integrated webcam), to an external one, "UVC Camera". The crash can be reproduced every time. -- Backtrace: Application: Kamoso (kamoso), signal: Segmentation fault [KCrash Handler] #6 convert_ubyte (void_dst=, num_dst_channels=, void_src=, src_type=, num_src_channels=3, swizzle=, normalized=true, count=832) at ../src/mesa/main/format_utils.c:1113 #7 0x7f83c191512e in _mesa_format_convert (void_dst=, dst_format=dst_format@entry=145, dst_stride=dst_stride@entry=3328, void_src=void_src@entry=0x7f836c040e00, src_format=src_format@entry=2148173936, src_stride=src_stride@entry=2496, width=, height=, rebase_swizzle=) at ../src/mesa/main/format_utils.c:448 #8 0x7f83c1986d78 in texstore_rgba (srcPacking=, srcAddr=, srcType=5121, srcFormat=6407, srcDepth=1, srcHeight=3456, srcWidth=832, dstSlices=, dstRowStride=, dstFormat=PIPE_FORMAT_R8G8B8X8_UNORM, baseInternalFormat=, dims=, ctx=) at ../src/mesa/main/texstore.c:811 #9 _mesa_texstore (srcPacking=0x55f4b0956710, srcAddr=0x7f836c040e00, srcType=, srcFormat=, srcDepth=1, srcHeight=3456, srcWidth=832, dstSlices=, dstRowStride=, dstFormat=, baseInternalFormat=, dims=, ctx=) at ../src/mesa/main/texstore.c:937 #10 _mesa_texstore (ctx=, dims=, baseInternalFormat=, dstFormat=, dstRowStride=, dstSlices=, srcWidth=832, srcHeight=3456, srcDepth=1, srcFormat=, srcType=, srcAddr=0x7f836c040e00, srcPacking=0x55f4b0956710) at ../src/mesa/main/texstore.c:916 #11 0x7f83c19877ec in store_texsubimage (ctx=ctx@entry=0x55f4b0923b40, texImage=texImage@entry=0x7f835c1c3190, xoffset=xoffset@entry=0, yoffset=yoffset@entry=0, zoffset=, zoffset@entry=0, width=832, height=3456, depth=, format=6407, type=5121, pixels=0x7f836c040e00, packing=0x55f4b0956710, caller=0x7f83c26eb660 "glTexSubImage") at ../src/mesa/main/texstore.c:1078 #12 0x7f83c1987aa5 in _mesa_store_texsubimage (ctx=ctx@entry=0x55f4b0923b40, dims=dims@entry=2, texImage=texImage@entry=0x7f835c1c3190, xoffset=xoffset@entry=0, yoffset=yoffset@entry=0, zoffset=zoffset@entry=0, width=, height=, depth=, format=, type=, pixels=, packing=) at ../src/mesa/main/texstore.c:1142 #13 0x7f83c17b8242 in st_TexSubImage (ctx=ctx@entry=0x55f4b0923b40, dims=dims@entry=2, texImage=texImage@entry=0x7f835c1c3190, xoffset=xoffset@entry=0, yoffset=, yoffset@entry=0, zoffset=, zoffset@entry=0, width=832, height=, depth=, format=6407, type=5121, pixels=, unpack=0x55f4b0956710) at ../src/mesa/state_tracker/st_cb_texture.c:1750 #14 0x7f83c17b9e87 in st_TexImage (unpack=0x55f4b0956710, pixels=0x7f836c040e00, type=5121, format=6407, texImage=0x7f835c1c3190, dims=2, ctx=0x55f4b0923b40) at ../src/mesa/state_tracker/st_cb_texture.c:1775 #15 st_TexImage (ctx=0x55f4b0923b40, dims=2, texImage=0x7f835c1c3190, format=6407, type=5121, pixels=0x7f836c040e00, unpack=0x55f4b0956710) at ../src/mesa/state_tracker/st_cb_texture.c:1757 #16 0x7f83c196f0fc in teximage (no_error=false, pixels=0x7f836c040e00, imageSize=0, type=5121, format=6407, border=0, depth=, height=, width=, internalFormat=, level=0, target=3553, texObj=0x55f4aff53100, dims=2, compressed=0 '\000', ctx=0x55f4b0923b40) at ../src/mesa/main/teximage.c:3153 #17 teximage_err (ctx=0x55f4b0923b40, compressed=compressed@entry=0 '\000', dims=dims@entry=2, target=3553, level=0, internalFormat=, width=832, height=3456, depth=1, border=, format=6407, type=5121, imageSize=0, pixels=0x7f836c040e00) at ../src/mesa/main/teximage.c:3180 #18 0x7f83c1971062 in _mesa_TexImage2D (target=, level=, internalFormat=, width=, height=, border=, format=6407, type=5121, pixels=0x7f836c040e00) at ../src/mesa/main/teximage.c:3251 #19 0x7f83994ff8fb in () at /usr/lib/x86_64-linux-gnu/gstreamer-1.0/gstkamosoqt5videosink.so #20 0x7f83994ff9f6 in () at /usr/lib/x86_64-linux-gnu/gstreamer-1.0/gstkamosoqt5videosink.so #21 0x7f839955 in () at /usr/lib/x86_64-linux-gnu/gstreamer-1.0/gstkamosoqt5videosink.so #22 0x7f83d16f5676 in QSGBatchRenderer::Renderer::renderMergedBatch(QSGBatchRenderer::Batch const*) (batch=0x7f835c164e80, this=0x7f835c0068e0) at scenegraph/coreapi/qsgbatchrenderer.cpp:2306 #23
[kamoso] [Bug 447270] Kamoso segfaults when switching camera
https://bugs.kde.org/show_bug.cgi?id=447270 --- Comment #1 from Miren Radia --- This only seems to occur if the "Mirror camera" option is selected (which is the default for me). -- You are receiving this mail because: You are watching all bug changes.
