From: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [ISSUE] [CLOSED] kscreen does not save settings between reboots
Date: Sun, 01 May 2022 04:13:45 +0200 [thread overview]
Message-ID: <20220501021345._7z5h8Hv8WmocwnJ-0_oy-Q_-viErptl4dZxaBIpFsI@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-22913@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1131 bytes --]
Closed issue by adojck on void-packages repository
https://github.com/void-linux/void-packages/issues/22913
Description:
<!-- Don't request update of package. We have a script for that. https://alpha.de.repo.voidlinux.org/void-updates/void-updates.txt . However, a quality pull request may help. -->
### System
* xuname:
Void 5.4.46_1 x86_64 GenuineIntel uptodate rrrrmmnFFFF
* package:
`kscreen-5.19.0_1`
### Expected behavior
When I set screen ordering in `kscreen` kcm, I expect it to keep the settings
### Actual behavior
After reboot `kscreen` kcm settings for screen ordering are reset
### Steps to reproduce the behavior
Go to `kscreen` kcm (System Settings -> Display and Monitor -> Display Configuration) and drag screens to re-arrange them. Reboot the system, settings are gone (reset to default).
### Extra
I'm using `nvidia` driver for my GPU, screens are connected via DisplayPorts.
### Edit
This happens now on Arch Linux with Intel iGPU too. I guess it might be a problem within `kscreen` itself. I reported the bug to KDE: https://invent.kde.org/plasma/kscreen/-/issues/1
parent reply other threads:[~2022-05-01 2:13 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-22913@inbox.vuxu.org>]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20220501021345._7z5h8Hv8WmocwnJ-0_oy-Q_-viErptl4dZxaBIpFsI@z \
--to=ml@inbox.vuxu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).