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

            Bug ID: 431388
           Summary: Kscreen2 crash with activating internal display
           Product: systemsettings
           Version: 5.20.5
          Platform: openSUSE RPMs
                OS: Linux
            Status: REPORTED
          Keywords: drkonqi
          Severity: crash
          Priority: NOR
         Component: general
          Assignee: plasma-b...@kde.org
          Reporter: jcnen...@gmail.com
  Target Milestone: ---

Application: systemsettings5 (5.20.5)

Qt Version: 5.15.2
Frameworks Version: 5.77.0
Operating System: Linux 5.10.4-1-default x86_64
Windowing system: Wayland
Distribution: "openSUSE Tumbleweed"

-- Information about the crash:
- What I was doing when the application crashed:
I have my laptop's internal display and a second external display connected via
USB-C. Whenever kscreen2 is started, the internal display is disabled. Upon
trying to reactivate it via KDE settings, this crash happens.

The crash can be reproduced every time.

-- Backtrace:
Application: Systemeinstellungen (systemsettings5), signal: Segmentation fault

[KCrash Handler]
#4  0x00000000000000c0 in  ()
#5  0x00007f02f2346f9d in QtWayland::wl_output::handle_geometry(void*,
wl_output*, int, int, int, int, int, char const*, char const*, int)
(data=0x564f665cd5b0, object=<optimized out>, x=0, y=1080, physical_width=310,
physical_height=170, subpixel=0, make=0x564f6d13dd20 "BOE",
model=0x564f6d13dd28 "eDP-1-unbekannt", transform=0) at
qwayland-wayland.cpp:2207
#6  0x00007f02f195d42d in ffi_call_unix64 () at ../src/x86/unix64.S:106
#7  0x00007f02f19594f9 in ffi_call_int (cif=<optimized out>, fn=<optimized
out>, rvalue=<optimized out>, avalue=<optimized out>, closure=<optimized out>)
at ../src/x86/ffi64.c:669
#8  0x00007f02f229c8fe in wl_closure_invoke
(closure=closure@entry=0x564f6d13dc30, target=<optimized out>,
target@entry=0x564f6661b0b0, opcode=opcode@entry=0, data=<optimized out>,
flags=<optimized out>) at src/connection.c:1018
#9  0x00007f02f229cfcb in dispatch_event (display=0x564f66618ba0,
queue=<optimized out>, queue=<optimized out>) at src/wayland-client.c:1445
#10 0x00007f02f229d19c in dispatch_queue (queue=0x564f66618c70,
display=0x564f66618ba0) at src/wayland-client.c:1591
#11 wl_display_dispatch_queue_pending (display=0x564f66618ba0,
queue=0x564f66618c70) at src/wayland-client.c:1833
#12 0x00007f02f229d1ec in wl_display_dispatch_pending (display=<optimized out>)
at src/wayland-client.c:1896
#13 0x00007f02f2325c2b in QtWaylandClient::QWaylandDisplay::flushRequests()
(this=0x564f665cee40) at qwaylanddisplay.cpp:221
#14 0x00007f02f49e0900 in doActivate<false>(QObject*, int, void**)
(sender=0x564f6668c5f0, signal_index=4, argv=0x7fff0e59f060, argv@entry=0x0) at
kernel/qobject.cpp:3898
#15 0x00007f02f49d9c20 in QMetaObject::activate(QObject*, QMetaObject const*,
int, void**) (sender=sender@entry=0x564f6668c5f0, m=m@entry=0x7f02f4c8e0e0
<QAbstractEventDispatcher::staticMetaObject>,
local_signal_index=local_signal_index@entry=1, argv=argv@entry=0x0) at
kernel/qobject.cpp:3946
#16 0x00007f02f49a6e83 in QAbstractEventDispatcher::awake()
(this=this@entry=0x564f6668c5f0) at .moc/moc_qabstracteventdispatcher.cpp:149
#17 0x00007f02f4a0187c in
QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>)
(this=0x564f6668c5f0, flags=...) at kernel/qeventdispatcher_glib.cpp:430
#18 0x00007f02f49a8cab in
QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>)
(this=this@entry=0x7fff0e59f180, flags=..., flags@entry=...) at
../../include/QtCore/../../src/corelib/global/qflags.h:69
#19 0x00007f02f49b0f20 in QCoreApplication::exec() () at
../../include/QtCore/../../src/corelib/global/qflags.h:121
#20 0x0000564f6496d003 in main(int, char**) (argc=<optimized out>,
argv=0x7fff0e59f2a0) at
/usr/src/debug/systemsettings5-5.20.5-1.1.x86_64/app/main.cpp:209
[Inferior 1 (process 8949) detached]

Possible duplicates by query: bug 429407, bug 419493, bug 416253, bug 377347,
bug 377346.

Reported using DrKonqi

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

Reply via email to