Summary: | Failed to open system configuration screen - monitor | ||
---|---|---|---|
Product: | [Plasma] KScreen | Reporter: | Regis Rodrigues <regisarodrigues> |
Component: | kcm | Assignee: | Sebastian Kügler <sebas> |
Status: | RESOLVED FIXED | ||
Severity: | crash | CC: | herzenschein, kde, nate |
Priority: | NOR | Keywords: | drkonqi |
Version First Reported In: | unspecified | ||
Target Milestone: | --- | ||
Platform: | Neon | ||
OS: | Linux | ||
Latest Commit: | https://commits.kde.org/libkscreen/08d494c401cbd60830cecd2a4c60df889d65901c | Version Fixed In: | |
Sentry Crash Report: |
Description
Regis Rodrigues
2019-01-24 19:53:35 UTC
Can reproduce, both from systemsettings5 and from kcmshell5 kcm_kscreen individually. Gamma and Compositing KCMs are unaffected. This seems to have happened after an update from the last three days, since I managed to change scaling through the KCM yesterday (25/01), either to 1.2 or 1.3. This also seems to break the Kscreen's popup that is usually accessible through Meta+P. Operating System: KDE neon Developer Edition (Git Unstable) KDE Plasma Version: 5.15.80 KDE Frameworks Version: 5.54.0 Qt Version: 5.11.2 Kernel Version: 4.15.0-43-generic I'm marking this crash as CONFIRMED (not sure if this is too hasty) and suggesting that this be marked as Major, as the ability to handle monitor settings and multi-screen setups is crucial. Should I attach my backtrace as well? Git commit 08d494c401cbd60830cecd2a4c60df889d65901c by David Edmundson. Committed on 26/01/2019 at 17:57. Pushed by davidedmundson into branch 'Plasma/5.15'. Guard failing to load backend Summary: BackendManager::loadBackendPlugin can return a nullptr. We currently use that pointer regardless. The caller of this method ConfigOperationPrivate::loadBackend does handle a nullptr and shows a relevant warning message. Test Plan: Not done Reviewers: #plasma, broulik Reviewed By: #plasma, broulik Subscribers: plasma-devel Tags: #plasma Differential Revision: https://phabricator.kde.org/D18508 M +3 -0 src/backendmanager.cpp https://commits.kde.org/libkscreen/08d494c401cbd60830cecd2a4c60df889d65901c If we're in this path it means you failed to load the relevant kscreen backend. It shouldn't have crashed, but we were already in a problem state. Failing to load the backend is most likely some packaging situation rather than an upstream bug. |