Summary: | KWin crashed when moving borderless window between virtual desktops on desktop grid | ||
---|---|---|---|
Product: | [Plasma] kwin | Reporter: | Erik Quaeghebeur <bugs.kde.org> |
Component: | general | Assignee: | KWin default assignee <kwin-bugs-null> |
Status: | RESOLVED WORKSFORME | ||
Severity: | crash | CC: | kde.org, the.fedora |
Priority: | NOR | Keywords: | drkonqi |
Version: | 5.16.5 | ||
Target Milestone: | --- | ||
Platform: | Gentoo Packages | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Attachments: | New crash information added by DrKonqi |
Description
Erik Quaeghebeur
2019-10-23 16:19:30 UTC
Created attachment 127550 [details]
New crash information added by DrKonqi
kwin_x11 (5.18.4) using Qt 5.14.2
- What I was doing when the application crashed:
Moving a gwenview window between virtual desktops in grid view. Keyboard shortcut to open grid view, then mouse drag window.
- Custom settings of the application:
16 virtual desktops with 10 open applications.
-- Backtrace (Reduced):
#6 0x00007f62c3cf7749 in KWin::AbstractClient::setDesktops(QVector<KWin::VirtualDesktop*>) () at /usr/lib/libkwin.so.5
#7 0x00007f62c3d5b072 in KWin::EffectsHandlerImpl::windowToDesktops(KWin::EffectWindow*, QVector<unsigned int> const&) () at /usr/lib/libkwin.so.5
#8 0x00007f62c24300b9 in () at /usr/lib/libkwin4_effect_builtins.so.1
#9 0x00007f62c3d5c8a7 in KWin::EffectsHandlerImpl::checkInputWindowEvent(QMouseEvent*) () at /usr/lib/libkwin.so.5
#10 0x00007f62bb42f58d in () at /usr/lib/qt/plugins/org.kde.kwin.platforms/KWinX11Platform.so
Thank you for reporting this bug. Unfortunately, the backtrace doesn't contain proper debugging information. Can you please install debugging packages following the info provided in https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports, try to reproduce the bug and resubmit a backtrace with debugging information. Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! The first backtrace (mine) is complete enough, no? @Erik Quaeghebeur There are two issues with this backtrace. First, it's quite old. We do not know if it has been fixed in the meantime, or not. Hence the request to confirm and provide an updated backtrace. The developers do not have the resources, to reproduce issues with old code. They can barely look at the issues reported against the current source. The second issue is, that it doesn't contain debug information for Kwin, e.g. the following lines are missing information about the file and line numbers the error occurred: #6 0x00007f316bc322d5 in KWin::AbstractClient::setDesktops(QVector<KWin::VirtualDesktop*>) () from /usr/lib64/libkwin.so.5 #7 0x00007f316bd084db in KWin::EffectsHandlerImpl::windowToDesktops(KWin::EffectWindow*, QVector<unsigned int> const&) () from /usr/lib64/libkwin.so.5 That's why I asked you to kindly have a look at https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! |