Bug 447605 - When starting the computer plasma do not handle two monitors as two, but one
Summary: When starting the computer plasma do not handle two monitors as two, but one
Status: RESOLVED DUPLICATE of bug 396359
Alias: None
Product: plasmashell
Classification: Plasma
Component: general (show other bugs)
Version: 5.23.4
Platform: Arch Linux Linux
: NOR crash
Target Milestone: 1.0
Assignee: David Edmundson
URL:
Keywords: drkonqi
Depends on:
Blocks:
 
Reported: 2021-12-28 16:41 UTC by aasheimvebjorn
Modified: 2022-01-11 17:03 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description aasheimvebjorn 2021-12-28 16:41:56 UTC
Application: plasmashell (5.23.4)

Qt Version: 5.15.2
Frameworks Version: 5.89.0
Operating System: Linux 5.15.11-arch2-1 x86_64
Windowing System: X11
Distribution: "Arch Linux"
DrKonqi: 5.23.4 [KCrashBackend]

-- Information about the crash:
- What I was doing when the application crashed:
When booth monitores comes alaive plasma is still confused since it treated it as 1 after grub on the sign on screen. Than I have to turn off and on one monitor for plasma to recognize two monitors and then plasma craches and restarts.

I think the cause is that something do not start in the correct sequence during startup

The crash can be reproduced every time.

-- Backtrace:
Application: Plasma (plasmashell), signal: Segmentation fault

[KCrash Handler]
#4  0x00007f18e8d740b2 in QQuickItemPrivate::addToDirtyList() () at /usr/lib/libQt5Quick.so.5
#5  0x00007f18e8d78aaf in QQuickItemPrivate::dirty(QQuickItemPrivate::DirtyType) () at /usr/lib/libQt5Quick.so.5
#6  0x00007f18e7432506 in QObject::event(QEvent*) () at /usr/lib/libQt5Core.so.5
#7  0x00007f18e803e1a6 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /usr/lib/libQt5Widgets.so.5
#8  0x00007f18e740e89a in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /usr/lib/libQt5Core.so.5
#9  0x00007f18e740f399 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () at /usr/lib/libQt5Core.so.5
#10 0x00007f18e7455b88 in  () at /usr/lib/libQt5Core.so.5
#11 0x00007f18e576052c in g_main_context_dispatch () at /usr/lib/libglib-2.0.so.0
#12 0x00007f18e57b47b9 in  () at /usr/lib/libglib-2.0.so.0
#13 0x00007f18e575dc11 in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0
#14 0x00007f18e7459a8a in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib/libQt5Core.so.5
#15 0x00007f18e7406a9b in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib/libQt5Core.so.5
#16 0x00007f18e74122c7 in QCoreApplication::exec() () at /usr/lib/libQt5Core.so.5
#17 0x0000559e1c86e51a in  ()
#18 0x00007f18e6dd7b25 in __libc_start_main () at /usr/lib/libc.so.6
#19 0x0000559e1c86e8de in  ()
[Inferior 1 (process 1391) detached]

Possible duplicates by query: bug 447244, bug 447063, bug 446947, bug 446808, bug 446671.

Reported using DrKonqi
Comment 1 Nate Graham 2022-01-11 17:03:17 UTC

*** This bug has been marked as a duplicate of bug 396359 ***