[07:54] <BrianHechinger[m> OvenWerks: opinion on the 14 vs the 24?
[07:58] <BrianHechinger[m> The 14 is 2x as much as the 24.
[12:24] <BrianHechinger[m> Well, I found a 24 locally so I'm picking that up tomorrow
[15:56] <BrianHechinger[m> Eickmeyer: Where would be the best place to open a ticket for kde/plasma issues? The Ubuntu Studio bug tracker or the Kubuntu one?
[15:57] <Eickmeyer> BrianHechinger[m: "ubuntu-bug {package name}" in a terminal window.
[15:57] <Eickmeyer> It's all Ubuntu, there is no division.
[15:57] <BrianHechinger[m> I don't know what package to blame it on though. :-D
[15:57] <Eickmeyer> What's the problem?
[16:03] <BrianHechinger[m> https://askubuntu.com/questions/1404013/screen-becomes-fuzzy-ubuntu-studio-22-04
[16:07] <Eickmeyer> BrianHechinger[m: I *think* that's a known bug with the Nvidia drivers, not with plasma.
[16:07] <Eickmeyer> Either that or Mesa.
[16:07] <Eickmeyer> I can't reproduce on my hardware using same drivers though.
[16:07] <BrianHechinger[m> Hmmm.
[16:07] <Eickmeyer> Have you tried disconnecting/reconnecting your monitor?
[16:09] <Eickmeyer> On my hardware, using the same drivers, it appeared fuzzy so I just disconnected/reconnected and it was fine. *shrug*
[16:18] <BrianHechinger[m> I'll try that next time.
[16:28] <BrianHechinger[m> Nope, didn't help.
[16:35] <Eickmeyer> :/
[16:35] <Eickmeyer> Well, I'm sure it's not a plasma bug because plasma doesn't work that intricately. Try adjusting your font hinting?
[16:37] <BrianHechinger[m> Ok. What does that mean? :-D
[16:37] <Eickmeyer> vm, I see more than that is weird.
[16:38] <Eickmeyer> It *almost* seems like your native res and your output res are out of alignment.
[16:38] <Eickmeyer> Some weird anti-aliasing going on.
[16:38] <Eickmeyer> Check your nvidia-settings.
[16:40] <Eickmeyer> And also check to make sure you don't have an /etc/X11/xorg.conf file that could be mucking things up.
[16:43] <BrianHechinger[m> just the one that nvidia-settings made
[16:44] <BrianHechinger[m> and nvidia-settings shows that it's a 2560x1440 display (which it is)
[16:44] <BrianHechinger[m> Display Configuration agrees
[16:44] <Eickmeyer> BrianHechinger[m: Yeah, that's the culpret. I've had nothing but bad experiences with the xorg.conf files. X11 doesn't need them anymore, and Nvidia hasn't figured that out yet. Delete it.
[16:45] <BrianHechinger[m> ok
[16:47] <Eickmeyer> Just let System Settings > Display Configuration handle stuff and you'll be fine. No need for nvidia-settings to do it.
[16:48] <Eickmeyer> If you have hybrid graphics (like a laptop), install plasma-optimus (a tool I forked/rewrote) and you'll have a nice mode switcher.
[16:48] <BrianHechinger[m> desktop, so no integrated graphics
[16:49] <Eickmeyer> Gotcha.
[16:50] <BrianHechinger[m> I'm assuming I need to relog for that change to take effect?
[16:58] <BrianHechinger[m> Still experiencing the same issue even with the xorg.conf file moved out of the way. :(
[16:58] <Eickmeyer> Dangit...
[16:59] <Eickmeyer> I'm willing to bet it's mesa.
[16:59] <Eickmeyer> Let me get the package name.
[17:00] <BrianHechinger[m> Should I re-enabled the newer mesa stuff?
[17:00] <Eickmeyer> Actually, let's try this.
[17:01] <Eickmeyer> "ubuntu-bug xserver-xorg-video-nvidia-510". I'm willing to bet that's a good starting point, and if that's not the culpret, they'll at least redirect it.
[17:01] <Eickmeyer> Attach your screenshot to the bug report.
[17:02] <Eickmeyer> Mesa mostly covers intel anyhow.
[17:13] <mstrgecko> i know it's most common in ubuntu to just go with a solution once someonehas figured it out and put it into the distro, but i'm looking for a deeper understanding of how ubuntu-studio automagically creates nodes/clients in jack that relate to programs i'm running as well as soundcards. i know when i plug-in/unplug my USBDAC, it creates and destroys things in Carla.  where should i start learning 
[17:13] <mstrgecko> deeper?
 "Mesa mostly covers intel anyhow." <- Yeah, I had been tracking the kisak repo but thought mesa was mostly for amd/intel so when it didn't have jammy yet I just skipped it for now.
[17:15] <BrianHechinger[m> mstrgecko: studio-controls creates pulse audio bridges, but nothing else. Any other client is created by the application. (this includes the device drivers creating the devices you see in Carla)
[17:15] <Eickmeyer> !studio-controls | mstrgecko 
[17:16] <Eickmeyer> Also 
[17:16] <Eickmeyer> !jack | mstrgecko 
[17:16] <Eickmeyer> also
[17:16] <Eickmeyer> !morehelp | mstrgecko 
[17:17] <BrianHechinger[m> Oh, I didn't know about the pipe thing for those bot commands. That's nifty
[17:17] <BrianHechinger[m> * That's nifty.
[17:21] <mstrgecko> BrianHechinger[m: to clarify, the device driver is creating the the nodes in carla for my USBDAC?
[17:21] <BrianHechinger[m> yes
[17:22] <BrianHechinger[m> every app (drivers included) is responsible for its own connections into jack.
[17:22] <BrianHechinger[m> bug 1970458
[17:22] <BrianHechinger[m> Eickmeyer: if you wanted to follow along
[17:23] <Eickmeyer> Holup.... your hardware itself is heavily modified????
[17:23] <Eickmeyer> BrianHechinger[m: ^ ?
[17:24] <BrianHechinger[m> huh?
[17:24] <BrianHechinger[m> You referring to this? `It's heavily modded BattleTech which sometimes needs killing.`
[17:24] <Eickmeyer> "It's heavily modded BattleTech which sometimes needs killing."
[17:24] <Eickmeyer> Yes.
[17:24] <BrianHechinger[m> the game is modded
[17:24] <Eickmeyer> Ohhhhhh
[17:25] <Eickmeyer> Well, a heavily modded game could almost certainly cause it.
[17:26] <BrianHechinger[m> no, any game causes it. Sometimes the screensaver being on too long causes it.
[17:26] <BrianHechinger[m> s/no/No/
[17:26] <Eickmeyer> Ah, I see.
[17:26] <Eickmeyer> Well, expect a few questions along those lines.
[21:14] <OvenWerks> opps he already quit... the answer would have been zita-ajbridge