https://bugs.kde.org/show_bug.cgi?id=452083

            Bug ID: 452083
           Summary: KWin crashes when connecting Displayport monitor via
                    usb-c dock
           Product: kwin
           Version: 5.24.3
          Platform: openSUSE RPMs
                OS: Linux
            Status: REPORTED
          Keywords: drkonqi
          Severity: crash
          Priority: NOR
         Component: general
          Assignee: kwin-bugs-n...@kde.org
          Reporter: kato...@gmail.com
  Target Milestone: ---

Application: kwin_x11 (5.24.3)

Qt Version: 5.15.2
Frameworks Version: 5.92.0
Operating System: Linux 5.16.15-1-default x86_64
Windowing System: X11
Distribution: "openSUSE Tumbleweed"
DrKonqi: 5.24.3 [KCrashBackend]

-- Information about the crash:
- What I was doing when the application crashed: I have connected my USB-C dock
to the laptop. The USB-C dock has a monitor connected to Displayport. After
connection the external screen is activated and KWin cracsh is reported. The
crash result is versatile, sometimes nothing strange is visible, but it also
happens, that the panel is not at the bottom of the screen but somewhere above.
In other cases windows loose activity binding and appear on all activities.
These effects are random, however the crash is permanent. In case of the
current report the panel moved from the bottom.

The crash can be reproduced every time.

-- Backtrace:
Application: KWin (kwin_x11), signal: Segmentation fault
Content of s_kcrashErrorMessage: std::unique_ptr<char []> = {get() = <optimized
out>}
[KCrash Handler]
#6  0x0000000000000000 in  ()
#7  0x00007fdc979685a2 in KWin::Toplevel::isOnOutput(KWin::AbstractOutput*)
const (this=0x55f11bac1450, output=<optimized out>) at
/usr/src/debug/kwin5-5.24.3-1.2.x86_64/src/toplevel.cpp:423
#8  0x00007fdc979a0b29 in KWin::Workspace::activeOutput() const
(this=0x55f11b71e580) at
/usr/src/debug/kwin5-5.24.3-1.2.x86_64/src/workspace.cpp:2419
#9  0x00007fdc979adc5f in KWin::X11Client::manage(unsigned int, bool)
(this=0x55f11ba98370, w=<optimized out>, isMapped=<optimized out>) at
/usr/src/debug/kwin5-5.24.3-1.2.x86_64/src/workspace.h:811
#10 0x00007fdc97993843 in KWin::Workspace::createClient(unsigned int, bool)
(this=0x55f11b71e580, w=37749093, is_mapped=<optimized out>) at
/usr/src/debug/kwin5-5.24.3-1.2.x86_64/src/workspace.cpp:654
#11 0x00007fdc978cbb1d in KWin::Workspace::workspaceEvent(xcb_generic_event_t*)
(this=0x55f11b71e580, e=0x7fdc8800a220) at
/usr/src/debug/kwin5-5.24.3-1.2.x86_64/src/events.cpp:223
#12 0x00007fdc95dba3cf in
QAbstractEventDispatcher::filterNativeEvent(QByteArray const&, void*, long*)
(this=<optimized out>, eventType=..., message=message@entry=0x7fdc8800a220,
result=result@entry=0x7ffe66c2d2f8) at kernel/qabstracteventdispatcher.cpp:495
#13 0x00007fdc902cd491 in QXcbConnection::handleXcbEvent(xcb_generic_event_t*)
(this=this@entry=0x55f11b46c270, event=event@entry=0x7fdc8800a220) at
qxcbconnection.cpp:536
#14 0x00007fdc902ceb96 in
QXcbConnection::processXcbEvents(QFlags<QEventLoop::ProcessEventsFlag>)
(this=0x55f11b46c270, flags=...) at qxcbconnection.cpp:1020
#15 0x00007fdc902f51bc in
QXcbUnixEventDispatcher::processEvents(QFlags<QEventLoop::ProcessEventsFlag>)
(this=0x55f11b533d30, flags=...) at qxcbeventdispatcher.cpp:61
#16 0x00007fdc95dbb83b in
QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>)
(this=this@entry=0x7ffe66c2d440, flags=..., flags@entry=...) at
../../include/QtCore/../../src/corelib/global/qflags.h:69
#17 0x00007fdc95dc3b10 in QCoreApplication::exec() () at
../../include/QtCore/../../src/corelib/global/qflags.h:121
#18 0x00007fdc9620d25c in QGuiApplication::exec() () at
kernel/qguiapplication.cpp:1867
#19 0x00007fdc953729f5 in QApplication::exec() () at
kernel/qapplication.cpp:2824
#20 0x000055f119ec2509 in main(int, char**) (argc=<optimized out>,
argv=0x7ffe66c2d708) at
/usr/src/debug/kwin5-5.24.3-1.2.x86_64/src/main_x11.cpp:482
[Inferior 1 (process 5626) detached]

Possible duplicates by query: bug 451972, bug 450954, bug 450924, bug 450337,
bug 448064.

Reported using DrKonqi

-- 
You are receiving this mail because:
You are watching all bug changes.

Reply via email to