public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
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: Sun, 25 Feb 2024 11:17:39 -0700	[thread overview]
Message-ID: <CAK2H+edVHf-jWvwexGSBnYMMkdvCzmVBjUN3g6RHtbzhA3+fkQ@mail.gmail.com> (raw)
In-Reply-To: <fb23335a-772d-4989-ba00-db54a7d0764d@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1336 bytes --]

On Sun, Feb 25, 2024 at 10:35 AM Daniel Frey <djqfrey@gmail.com> wrote:
<SNIP>
> I probably should have added more details... I do have an nvidia card -
> RTX 3070Ti. Monitors use 2x DP ports and 1x HDMI port.
>
> KDE behaves very strangely. Like, it crashes often when using multiple
> monitors and I've never been able to figure that out.
>
> nvidia-settings (which I plain forgot about) can generate an Xorg.conf
> file from what I remember, maybe I'll try that.
>
> I currently don't have an Xorg.conf (as everything I've read says it
> should autodetect...) so maybe I'll try overriding it.
>
> Dan

I'm not Gentoo-based but have a similar setup. 3080ti, 2 Asus
monitors, 1 Samsung, all running 1920x1080, all in landscape.

I have absolutely no problems at all with KDE remembering where
everything goes, all 3 monitors, all taskbars, for multiple users
with different configurations. I use 1 HDMI cable and 2 HDMI->DVI
cables. Everything just works.

I have no xorg.conf file.

I tried Wayland for a while but there were too many weird artifacts
so I'm back to basics.

I'd suggest you look carefully at every flag you are using to
build your software. I've used 3 distros here recently, as well
as Win 10 & 11 and none of them have had problems like
you are describing.

Best of luck,
Mark

[-- Attachment #2: Type: text/html, Size: 1743 bytes --]

  reply	other threads:[~2024-02-25 18:17 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 [this message]
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
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+edVHf-jWvwexGSBnYMMkdvCzmVBjUN3g6RHtbzhA3+fkQ@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