From: Mark Knecht <markknecht@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Why is KDE so bad at multiple monitors?
Date: Wed, 28 Feb 2024 15:43:36 -0700 [thread overview]
Message-ID: <CAK2H+ecexzN4OyvbhdvqZ-VJeB6CAfCc_xARFByxuRMCQAY=2Q@mail.gmail.com> (raw)
In-Reply-To: <a4e19e83-977f-0d80-d3c4-14df44be5b68@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1248 bytes --]
On Wed, Feb 28, 2024 at 3:24 PM Dale <rdalek1967@gmail.com> wrote:
>
> Paul B. Henson wrote:
> > On Sat, Feb 24, 2024 at 08:53:37PM -0800, Daniel Frey wrote:
> >> After cursing KDE for a while with three monitors, does anyone have any
> >> idea why KDE is so bad at managing multiple monitors?
> > <shrug>. I ended up adding this to /usr/share/sddm/scripts/Xsetup:
> >
> > xrandr --output DVI-D-0 --primary --output HDMI-A-0 --left-of DVI-D-0
> > --output DisplayPort-0 --right-of DVI-D-0
> >
> > Always perfect since then :).
>
> I have two questions. Does a upgrade change it back to defaults? If
> so, there may be a file in /etc somewhere that is more permanent. If
> not, cool. :-)
>
> How did you get the info to match the hardware you have? My main
> display is on a DB15HD port. My second display in on a HDMI port. I
> figure you ran a command to gather that info or there is a source of all
> the possibilities.
>
> I'd like to give that a shot. Might help with my occasional issue.
>
> Dale
>
> :-) :-)
If you're just looking for what's connected to what port then xrandr will
tell you that.
To get to Paul's equation you would need to figure out the ordering
yourself I think
HTH,
Mark
[-- Attachment #2: Type: text/html, Size: 1596 bytes --]
next prev parent reply other threads:[~2024-02-28 22:43 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-25 4:53 [gentoo-user] Why is KDE so bad at multiple monitors? Daniel Frey
2024-02-25 5:52 ` Dale
2024-02-25 9:01 ` Michael
2024-02-25 15:08 ` Dale
2024-02-25 17:36 ` Daniel Frey
2024-02-25 18:10 ` Michael
2024-02-25 17:34 ` Daniel Frey
2024-02-25 18:17 ` Mark Knecht
2024-02-27 15:21 ` Daniel Frey
2024-02-25 11:29 ` Paul Colquhoun
2024-02-28 22:13 ` Paul B. Henson
2024-02-28 22:23 ` Dale
2024-02-28 22:43 ` Mark Knecht [this message]
2024-02-29 11:27 ` Dale
2024-03-03 18:59 ` Daniel Frey
2024-03-03 19:31 ` Dale
2024-03-03 19:39 ` Daniel Frey
2024-03-03 21:57 ` Dale
2024-03-03 22:39 ` Daniel Frey
2024-03-03 23:47 ` Dale
2024-03-03 21:20 ` Michael
2024-03-04 2:39 ` Dale
2024-03-14 21:23 ` Mart Raudsepp
2024-03-05 10:56 ` Arsen Arsenović
2024-03-02 5:11 ` Paul B. Henson
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='CAK2H+ecexzN4OyvbhdvqZ-VJeB6CAfCc_xARFByxuRMCQAY=2Q@mail.gmail.com' \
--to=markknecht@gmail.com \
--cc=gentoo-user@lists.gentoo.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