| Summary: | Crash in ScreenPool::handleScreenRemoved | ||
|---|---|---|---|
| Product: | [Plasma] plasmashell | Reporter: | Ryan <itsbugfood> |
| Component: | generic-multiscreen | Assignee: | Plasma Bugs List <plasma-bugs> |
| Status: | RESOLVED DUPLICATE | ||
| Severity: | crash | CC: | aleixpol, kde, kde, nate, notmart, salamanetwork, tmanczak, wolfmercer |
| Priority: | NOR | Keywords: | drkonqi |
| Version: | 5.25.5 | ||
| Target Milestone: | 1.0 | ||
| Platform: | Compiled Sources | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
| Attachments: |
New crash information added by DrKonqi
New crash information added by DrKonqi New crash information added by DrKonqi New crash information added by DrKonqi attachment-518575-0.html |
||
|
Description
Ryan
2022-05-19 21:31:54 UTC
There were was a lot of multi-monitor code changes related to ScreenPool in Plasma 5.25 Would you be able to see if this still happens in the Plasma 5.25 beta or the final 5.25 release in a month? Thanks! Also, do you have more than one screen connected on login? Or just one? 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! 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! Created attachment 151092 [details]
New crash information added by DrKonqi
plasmashell (5.25.3) using Qt 5.15.5
crashed just after loged in. Don't know wh,y this was a clean install on a new SSD.
-- Backtrace (Reduced):
#6 0x00007efdfbe87bd9 in QMessageLogger::fatal(char const*, ...) const () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#7 0x00007efdfbe86fe5 in qt_assert(char const*, char const*, int) () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#8 0x0000556814d53b15 in ScreenPool::handleScreenRemoved (this=0x5568153a2db0, screen=0x556815306aa0) at /tmp/git-sources/plasma-workspace/shell/screenpool.cpp:442
#9 0x0000556814d59ce5 in QtPrivate::FunctorCall<QtPrivate::IndexesList<0>, QtPrivate::List<QScreen*>, void, void (ScreenPool::*)(QScreen*)>::call (f=(void (ScreenPool::*)(ScreenPool * const, QScreen *)) 0x556814d5375e <ScreenPool::handleScreenRemoved(QScreen*)>, o=0x5568153a2db0, arg=0x7ffe3b62d6a0) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qobjectdefs_impl.h:152
#10 0x0000556814d597bf in QtPrivate::FunctionPointer<void (ScreenPool::*)(QScreen*)>::call<QtPrivate::List<QScreen*>, void> (f=(void (ScreenPool::*)(ScreenPool * const, QScreen *)) 0x556814d5375e <ScreenPool::handleScreenRemoved(QScreen*)>, o=0x5568153a2db0, arg=0x7ffe3b62d6a0) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qobjectdefs_impl.h:185
Created attachment 153549 [details]
New crash information added by DrKonqi
plasmashell (5.25.5) using Qt 5.15.6
The crash occurred right after I logged in. It occurs not always, but it did already occur in the past. I am not aware of doing anything special.
-- Backtrace (Reduced):
#6 0x00007fd2769ffbd9 in QMessageLogger::fatal(char const*, ...) const () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#7 0x00007fd2769fefe5 in qt_assert(char const*, char const*, int) () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#8 0x000055981fe95c55 in ScreenPool::handleScreenRemoved (this=0x559821f7fbe0, screen=0x559821ee0710) at /tmp/git-sources/plasma-workspace/shell/screenpool.cpp:445
#9 0x000055981fe9be25 in QtPrivate::FunctorCall<QtPrivate::IndexesList<0>, QtPrivate::List<QScreen*>, void, void (ScreenPool::*)(QScreen*)>::call (f=(void (ScreenPool::*)(ScreenPool * const, QScreen *)) 0x55981fe9589e <ScreenPool::handleScreenRemoved(QScreen*)>, o=0x559821f7fbe0, arg=0x7ffe71d69520) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qobjectdefs_impl.h:152
#10 0x000055981fe9b8ff in QtPrivate::FunctionPointer<void (ScreenPool::*)(QScreen*)>::call<QtPrivate::List<QScreen*>, void> (f=(void (ScreenPool::*)(ScreenPool * const, QScreen *)) 0x55981fe9589e <ScreenPool::handleScreenRemoved(QScreen*)>, o=0x559821f7fbe0, arg=0x7ffe71d69520) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qobjectdefs_impl.h:185
Created attachment 153597 [details]
New crash information added by DrKonqi
plasmashell (5.25.5) using Qt 5.15.6
Crash happened directory after login. Until now, Plasma did not reload automatically again. This is a fresh install, running stable for several hours, including reboots.
-- Backtrace (Reduced):
#6 0x00007f19bfa22bd9 in QMessageLogger::fatal(char const*, ...) const () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#7 0x00007f19bfa21fe5 in qt_assert(char const*, char const*, int) () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#8 0x00005566981eac55 in ScreenPool::handleScreenRemoved (this=0x556698cc33d0, screen=0x556698c21550) at /tmp/git-sources/plasma-workspace/shell/screenpool.cpp:445
#9 0x00005566981f0e25 in QtPrivate::FunctorCall<QtPrivate::IndexesList<0>, QtPrivate::List<QScreen*>, void, void (ScreenPool::*)(QScreen*)>::call (f=(void (ScreenPool::*)(ScreenPool * const, QScreen *)) 0x5566981ea89e <ScreenPool::handleScreenRemoved(QScreen*)>, o=0x556698cc33d0, arg=0x7ffd1a648df0) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qobjectdefs_impl.h:152
#10 0x00005566981f08ff in QtPrivate::FunctionPointer<void (ScreenPool::*)(QScreen*)>::call<QtPrivate::List<QScreen*>, void> (f=(void (ScreenPool::*)(ScreenPool * const, QScreen *)) 0x5566981ea89e <ScreenPool::handleScreenRemoved(QScreen*)>, o=0x556698cc33d0, arg=0x7ffd1a648df0) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qobjectdefs_impl.h:185
*** Bug 461605 has been marked as a duplicate of this bug. *** *** Bug 463396 has been marked as a duplicate of this bug. *** Created attachment 155029 [details]
New crash information added by DrKonqi
plasmashell (5.25.5) using Qt 5.15.6
It happens when I log in, almost every time. 9 out of 10 or so. I have the laptop on a dock, from where the external display is connected via DVI/HDMI.
Also, if the laptop has been sleeping in dock, then the display cannot be woken up. None of this happens when NOT in dock or not connected to a monitor.
-- Backtrace (Reduced):
#6 0x00007fb208ba5bd9 in QMessageLogger::fatal(char const*, ...) const () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#7 0x00007fb208ba4fe5 in qt_assert(char const*, char const*, int) () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#8 0x00005626d9413c55 in ScreenPool::handleScreenRemoved (this=0x5626da754770, screen=0x5626da6b5020) at /tmp/git-sources/plasma-workspace/shell/screenpool.cpp:445
#9 0x00005626d9419e25 in QtPrivate::FunctorCall<QtPrivate::IndexesList<0>, QtPrivate::List<QScreen*>, void, void (ScreenPool::*)(QScreen*)>::call (f=(void (ScreenPool::*)(ScreenPool * const, QScreen *)) 0x5626d941389e <ScreenPool::handleScreenRemoved(QScreen*)>, o=0x5626da754770, arg=0x7ffc953c6990) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qobjectdefs_impl.h:152
#10 0x00005626d94198ff in QtPrivate::FunctionPointer<void (ScreenPool::*)(QScreen*)>::call<QtPrivate::List<QScreen*>, void> (f=(void (ScreenPool::*)(ScreenPool * const, QScreen *)) 0x5626d941389e <ScreenPool::handleScreenRemoved(QScreen*)>, o=0x5626da754770, arg=0x7ffc953c6990) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qobjectdefs_impl.h:185
An enormous amount of multimonitor fixes went into Plasma 5.27; any chance you could check to see if *this specific crash* is still an issue in Plasma 5.27.4 or newer? Thanks! Created attachment 158442 [details] attachment-518575-0.html Thankyou for your reply. I will look and see if it helped. Thanks. Regards Tom fre. 21. apr. 2023 17.37 skrev Nate Graham <bugzilla_noreply@kde.org>: > https://bugs.kde.org/show_bug.cgi?id=454057 > > Nate Graham <nate@kde.org> changed: > > What |Removed |Added > > ---------------------------------------------------------------------------- > Status|REPORTED |NEEDSINFO > Resolution|--- |WAITINGFORINFO > > --- Comment #10 from Nate Graham <nate@kde.org> --- > An enormous amount of multimonitor fixes went into Plasma 5.27; any chance > you > could check to see if *this specific crash* is still an issue in Plasma > 5.27.4 > or newer? Thanks! > > -- > You are receiving this mail because: > You are on the CC list for the bug. 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! 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! *** This bug has been marked as a duplicate of bug 484687 *** |