Bug 444927 - kwin crashes when turning on a second monitor with xrandr --auto
Summary: kwin crashes when turning on a second monitor with xrandr --auto
Status: RESOLVED WORKSFORME
Alias: None
Product: kwin
Classification: Plasma
Component: general (show other bugs)
Version: 5.23.2
Platform: Slackware Linux
: NOR crash
Target Milestone: ---
Assignee: KWin default assignee
URL:
Keywords: drkonqi
Depends on:
Blocks:
 
Reported: 2021-11-04 08:44 UTC by Luigi Genoni
Modified: 2021-12-04 04:39 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Luigi Genoni 2021-11-04 08:44:39 UTC
Application: kwin_x11 (5.23.2)

Qt Version: 5.15.3
Frameworks Version: 5.87.0
Operating System: Linux 5.15.0 x86_64
Windowing System: X11
Distribution: Slackware 15.0 x86_64
DrKonqi: 5.23.2 [KCrashBackend]

-- Information about the crash:
- What I was doing when the application crashed:
my second monitor is usually turned off, I turn it on
with:

xrandr -d :0.1 --output HDMI-A-1  --auto --rotate left --set vrr_capable 1

and kwin shashes asking me to run another wm, if I choose fvmw then I have kwin on my primary monitor and fvwm on the secondary one (wich is ok, but I would prefer kwin not to crash.

My xorg is a dual head configuration, no xinerama

- Custom settings of the application:


My xorg is a dual head configuration, no xinerama

The crash can be reproduced every time.

-- Backtrace:
Application: KWin (kwin_x11), signal: Segmentation fault

[KCrash Handler]
#4  0x00007fa4a6e80364 in KWin::Workspace::clientArea(KWin::clientAreaOption, KWin::AbstractOutput const*, KWin::VirtualDesktop const*) const () at /usr/lib64/libkwin.so.5
#5  0x00007fa4a6ea0cf4 in KWin::X11Client::manage(unsigned int, bool) () at /usr/lib64/libkwin.so.5
#6  0x00007fa4a6e84ce6 in KWin::Workspace::createClient(unsigned int, bool) () at /usr/lib64/libkwin.so.5
#7  0x00007fa4a6e87c19 in KWin::Workspace::initializeX11() () at /usr/lib64/libkwin.so.5
#8  0x00007fa4a6e88d27 in KWin::Workspace::init() () at /usr/lib64/libkwin.so.5
#9  0x00007fa4a6e8974c in KWin::Workspace::Workspace() () at /usr/lib64/libkwin.so.5
#10 0x00007fa4a6dd8bc0 in KWin::Application::createWorkspace() () at /usr/lib64/libkwin.so.5
#11 0x0000000000409143 in  ()
#12 0x00007fa4a4afc6fd in  () at /usr/lib64/libQt5Core.so.5
#13 0x00007fa4a4432f83 in  () at /usr/lib64/libKF5WindowSystem.so.5
#14 0x00007fa4a4af2dbf in QObject::event(QEvent*) () at /usr/lib64/libQt5Core.so.5
#15 0x00007fa4a3eeca8f in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /usr/lib64/libQt5Widgets.so.5
#16 0x00007fa4a4ac84ea in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /usr/lib64/libQt5Core.so.5
#17 0x00007fa4a4b1b41b in QTimerInfoList::activateTimers() () at /usr/lib64/libQt5Core.so.5
#18 0x00007fa4a4b199af in QEventDispatcherUNIX::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib64/libQt5Core.so.5
#19 0x00007fa49f9724ae in  () at /usr/lib64/libQt5XcbQpa.so.5
#20 0x00007fa4a4ac706b in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib64/libQt5Core.so.5
#21 0x00007fa4a4acecbc in QCoreApplication::exec() () at /usr/lib64/libQt5Core.so.5
#22 0x0000000000407f92 in  ()
#23 0x00007fa4a370001d in __libc_start_main () at /lib64/libc.so.6
#24 0x000000000040846a in  ()
[Inferior 1 (process 2720) detached]

Possible duplicates by query: bug 443985, bug 443166, bug 442809, bug 441577, bug 438738.

Reported using DrKonqi
Comment 1 kde.org 2021-11-04 18:50:59 UTC
Thank you for taking the time to report this bug. Unfortunately, the backtrace provided does not contain debug information. Can you please install debugging packages following the instructions given here: https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports
and then reproduce the bug.
Comment 2 Bug Janitor Service 2021-11-19 04:39:18 UTC
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!
Comment 3 Bug Janitor Service 2021-12-04 04:39:04 UTC
This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now 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

Thank you for helping us make KDE software even better for everyone!