public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Dale <rdalek1967@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 09:08:46 -0600	[thread overview]
Message-ID: <b16c4f72-dd8e-3e27-1303-aa86c6706b8a@gmail.com> (raw)
In-Reply-To: <5759155.DvuYhMxLoT@rogueboard>

Michael wrote:
> On Sunday, 25 February 2024 05:52:20 GMT Dale wrote:
>> 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?
>>>
>>> All I'm trying to do is get it to remember *where* my monitors are (I
>>> have two side-by-side and one above the right monitor.) I go into
>>> System Settings, set it up and it works perfectly... until I log out.
>>> Then it resets everything and I have to set it up again.
>>>
>>> Anyone have any clue why it refuses to save settings?
>>>
>>> -Dan
>> I have two monitors too, sort of.  One monitor is for computer stuff,
>> checking email, surfing the net etc etc etc.  The other monitor I use to
>> watch TV with.  The output from the video card second output goes to a
>> splitter so I can have the same video in both my bedroom and the living
>> room.  I use Nvidia settings to manage mine but I run into the same
>> problem you do.  Sometimes when I login, the second monitor output is
>> dead.  TV shows the dreaded "No signal" thing floating around.  I have
>> to open Nvidia settings, disable the second monitor output, hit apply,
>> click that I can see the screen still, re-enable the second monitor,
>> click apply, click I can see the monitor and then the second monitor
>> works again.  It's annoying as heck.  I'm on the 470 series of Nvidia
>> drivers.  Best my old card can do.  LOL 
>>
>> I looked in the KDE System Settings display settings screen and it shows
>> the same as Nvidia.  Maybe one copies the other???  There's really
>> nothing for me to change there so I can't hit apply.  :/   I've always
>> wondered if I can set this up in xorg.conf file instead of the GUI. 
>> Maybe it would work better.  Thing is, everything says it should "just
>> work" and the file shouldn't be needed. 
>>
>> This may not be a KDE problem.  It could be a Nvidia problem.  It may be
>> KDE but I'm not sure which to blame.  I don't let my screen go off
>> except for the once a week trip to town to get shots so I just put up
>> with it.  The rest of the time, my monitors and TVs tend to stay on. 
>>
>> You are not alone.  I'm just not real sure this is a KDE problem.  It's
>> possible tho.  Mostly, you are not alone. 
>>
>> Dale
>>
>> :-)  :-) 
> I used to experience the same when using Xorg with AMD-Radeon graphics instead 
> of Nvidia, but since I moved to Wayland the problem of losing screen settings 
> has gone.  One monitor is using the DVI port of the card and the other HDMI.  
> It should be worth trying Wayland instead of Xorg to see if it works out 
> better for your setup.


I've read where Wayland still has a few other issues.  I'm sure at some
point, Xorg is going to end and the switch will be the only option. 
When that time comes, likely most all issues will be fixed.  That said,
I've also read where some people really like it.  I think it is
installed here and even used by some things.  I've seen the USE flag on
a lot of packages. 

Given this only affects me once a week, I'll stay where I am at the
moment.  It is nice to know there is another option tho.  One that might
even work better.  ;-)

Dale

:-)  :-) 


  reply	other threads:[~2024-02-25 15:09 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 [this message]
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
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=b16c4f72-dd8e-3e27-1303-aa86c6706b8a@gmail.com \
    --to=rdalek1967@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