is 39 going to be updated at all while 40 is working out its weird spots or no
is 39 going to be updated at all while 40 is working out its weird spots or no
Ei love you all
T39 will receive security updates until it's end of life when 41 is released
Tmy Nvidia hardware isn't, and not everyone has the financial voodoo to be able to switch just like that, and besides I'm a musician and server maintainer, I can't afford to switch hardware all the time
Ti understand that
Tnew nvidia drivers are coming that supposedly fix wayland issues
Tbut they won't release them until the middle of may
Rgotcha cool ty
TI hate windows and microsoft with a burning passion you wouldn't believe, I really wish I could have a distro that just works
Tim just saying the difference between a vendor who releases open source GPU drivers (AMD) and Nvidia (closed source drivers)
Tmint isn't perfect either though, I had to type in a command anytime I plugged in a different set of headphones
Ti understand most of the PC gaming population uses Nvidia
Tin my case not by choice
TI got this card off a friend for an incredibly low price
Tunderstandable
Tthere's nothing we can do on our end
Tcompared to anything I could've gotten for that amount of money from AMD there was nothing to even consider
L@LJ I was having similar glitches with wayland, have you tried using X11? it fixed KDE for me
TX11 causes other issues for them
Tplasma is sluggish
TI am on X11 sadly 
Rrecommend just rebasing back to 39
Tdo you think switching to gnome could resolve my problems?
Twould do a fresh reinstallation at this point
Tbut yes
Tit may
TGNOME X11 on Nvidia might be better
Tsigh, here goes nothing
DI notice that fastfetch (neofetch too) prints the amount of packages. Is it possible for me to add aditional package manager packages to be counted
Khas to be done in their source code, but yeah
LI had the same typing issue on wayland
LAppreciated. I'm having a hard time getting it to work.
(This is obviously NOT an emergency, so don't feel obligated to respond in any kind of speed. I know there's a lot more important happening)
Even after commenting out every line, changing the
I can't even manually specify by running fastfetch with
I'm clearly missing something fundamental, which isn't too unexpected in my case.
(This is obviously NOT an emergency, so don't feel obligated to respond in any kind of speed. I know there's a lot more important happening)
Even after commenting out every line, changing the
-cbazzite-neofetch.shI can't even manually specify by running fastfetch with
-c /path/to/configI'm clearly missing something fundamental, which isn't too unexpected in my case.
Kyou can also just delete that script
Kand then reboot
LI'm going to be so mad at myself if that's the only option I didn't try. BRB
Dif it involves modifying the source code I won't even bother
Tbtw i understand the finanical situation part. it's completely unfair that Nvidia is the only graphics vendor to not follow what AMD and Intel do and release the source code of their drivers meaning you will always be stuck with more issues and reliant soley on Nvidia and nobody else. I really hope, even as someone who doesn't own a Nvidia GPU, that the new drivers fix all of the issues with wayland like speculaton is indicating
Tmy stance on this is what LT said on the topic, simply "nvidia, f**k you"
Ttrue
TI'm a big advocate for FOSS myself and open-source in general so this really pisses me off
RThey should change their name to that TBH /s
Tsome users reported a black screen logging into wayland with nvidia GPUs here like 4 different times
Tso true
RIt's even more of a mess now.
RThey like have three different codebases that they are supporting.
RThe crappy closed one, the half working "open" one, and now nouveau.
RFu** hell, decide on one and freaking make it work on all hardware, god damn.
LPost reboot. No dice.
KAnd that's bash?
KTry ~/.config for me as well
K
