@ada@lemmy.blahaj.zone
@ada@lemmy.blahaj.zone avatar

ada

@ada@lemmy.blahaj.zone

Admin of lemmy.blahaj.zone

I can also be found on the microblog fediverse at @ada or on matrix at @ada:chat.blahaj.zone

This profile is from a federated server and may be incomplete. Browse more on the original instance.

ada,
@ada@lemmy.blahaj.zone avatar

They’re going to use LLMs to analyse user usage data to make things better?

[Resolved] Saving x11 configs?

I’m running an nvidia card on X11 Plasma 6, with a 4K monitor alongside a QHD monitor. Both monitors are the same physical size, despite being different resolutions, so in the nvidia settings app, I’ve got the second X screen setup to generate 4K but downscale it to QHD in the output. It makes the second screen slightly...

ada, (edited )
@ada@lemmy.blahaj.zone avatar

After updating nvidia-settings, the x conf looks correct and reads like this

Option “metamodes” “DP-2: nvidia-auto-select +0+0 {ForceCompositionPipeline=On, ForceFullCompositionPipeline=On}, DP-0: nvidia-auto-select +3840+132 {viewportin=3840x2160, ForceCompositionPipeline=On, ForceFullCompositionPipeline=On}”

But then when I reboot, it reads as follows


<span style="color:#323232;"># Removed Option "metamodes" "DP-2: nvidia-auto-select +0+0 {ForceCompositionPipeline=On, ForceFullCompositionPipeline=On}, DP-0: nvidia-auto-select +3840+132 {viewportin=3840x2160, ForceCompositionPipeline=On, ForceFullCompositionPipeline=On}"
</span><span style="color:#323232;">
</span><span style="color:#323232;">Option         "metamodes" "DP-2: nvidia-auto-select +0+0 {ForceCompositionPipeline=On, ForceFullCompositionPipeline=On}, DP-0: nvidia-auto-select +3840+132 {ForceCompositionPipeline=On, ForceFullCompositionPipeline=On}"
</span>

Which is to say the correct line is commented out, and the incorrect version replaces it.

I can’t work out how or why that is happening though

ada,
@ada@lemmy.blahaj.zone avatar

Ok, with further digging, I discovered that it was only getting updated on user login. The actual login screen itself was running with the updated resolution. So something in the KDE login process was to blame.

My girlfriend did some research, and it turns out that KDE kscreen service is the problem. I’ve disabled that, and everything works now

ada,
@ada@lemmy.blahaj.zone avatar

Yep, sometimes you just can’t without emergency dice. It’s just no dice

ada,
@ada@lemmy.blahaj.zone avatar

I don’t know? I’m a mum. I don’t know what that means. I don’t know how it differs from being a dad. Aside from the label, it feels pretty much the same, yet the label is important…

  • All
  • Subscribed
  • Moderated
  • Favorites
  • JUstTest
  • kavyap
  • DreamBathrooms
  • thenastyranch
  • magazineikmin
  • tacticalgear
  • khanakhh
  • Youngstown
  • mdbf
  • slotface
  • rosin
  • everett
  • ngwrru68w68
  • Durango
  • megavids
  • InstantRegret
  • cubers
  • GTA5RPClips
  • cisconetworking
  • ethstaker
  • osvaldo12
  • modclub
  • normalnudes
  • provamag3
  • tester
  • anitta
  • Leos
  • lostlight
  • All magazines