Fedora 40, Ubuntu 24.04 LTS, Flathub Redesign, Nextcloud & more Linux news 

huh their battle will be legendary

flathub >>>

That’s the great thing about Linux. We can have two, or three, or 10! 😊

Both are very inefficient. I tried some flatpaks but they use more resources. Like ram and storage.

​@@J-wm4ss Native Binary Packages>appimages/potable tar>flatpak>snaps.

WHOA! Thank you so much for the supercomment! That is so nice of you!!! I am glad you enjoy the show and thanks for being part of the community!

Whoa! Thank you so much for the super thanks, or super chat, or well I dont know what its called when its a comment. Thanks so much for that and you're welcome for the content. :D

Thanks a lot! I am working on trying to build up this channel more and more so if all goes well then it should get much bigger. :D

I didn’t know that was a thing to cover 🤷‍♂️

understandable decision and yes, Nvidia still has issues with Wayland. I covered some news on a previous episode that will fix that in a few months or so but right now it is still an problem. I am curious if you have tried Plasma and have the same problems. I think you might with Fedora 40 KDE as it will have Wayland only but Kubuntu 24.04 supports X11. It's not Plasma 6 but Plasma 5 is very good too so I think Kubuntu is worth looking into if you haven't. Alternatively, just keeping Mint Cinnamon is a solid option too. :D

@@michael_tunnell Last time I tried Kde was few months after debian 12 came out and I had very similar issues. But no, I have not tried it on Fedora yet. Also I just tested these on live USB. To be fair maybe if I had fully installed and updated, it could work out (I did this with debian and it didn't). I am going to wait for a bit more. Mint works for now but Clem says he will eventually move to wayland too. I hope Wayland gets good with nvidia drivers very soon.

Modify /etc/default/grub and add nvidia_drm.modeset=1 in GRUB_CMDLINE_LINUX_DEFAULT. Regenerate grub.cfg by running grub-mkconfig -o /boot/grub/grub.cfg Reboot. The line will look like this : GRUB_CMDLINE_LINUX_DEFAULT="loglevel=3 quiet nvidia_drm.modeset=1 "

Nvidia will release a new driver next month with wayland support.

Thanks for commenting and sharing your thoughts, my response to your question is "probably a couple more years". The context of that answer expresses that in a good way because Wayland is very very close to done and when you compare it to the Xorg timeline, it is drastically faster than X development. For direct comparison sake, it took X 22 years to become a solid option for those looking to use Linux. X was first released in 1984. The point of which Linux became a solid option for a large amount of people was around 2006. X had been out for 22 years and X11 had been out for 19 years at this time . . . yes X11 was the last major version of X and it was released in 1987. Wayland is taking a while but less than X and X had nothing to be compared to and Wayland is trying to replace something that has been in use for 40 years . . . its a lot to do.

@@michael_tunnell its been 10 years though, more than that, by the time wayland gets "ready", it may as well be almost as old as x was or is soon.

Yes, Wayland is taking a while, in fact its been developed for almost 16 years now. Yea I think maybe it takes 2 more years and a total of 18 years to replace X11 but that is 4 years faster than Xorg did it in and Xorg in 2006 was still far from solid. I dont think it was until 2010 that Linux desktop became average user friendly to use. Here's the thing though Wayland is having to do this while having to implement 4 decades worth of feature parity. If they only need 2 more years to do it then I would find that rather impressive. X was competing with nothing and didnt have to offer feature parity with anything. Wayland has to replace a massive project that has had 4 decades of development and is required to offer feature parity. This is a very difficult thing to do and takes a lot of time. A display server is one of the most core components of a desktop solution so it is going to be a mountain to climb to replace one so I am not all that surprised it is taking so long and a drop in replacement where most people never notice the change is what is needed from Wayland. This is a very hard thing to do at any level but at this level its kind of insane.

It is ready even if it is not ready. It is impossible to implement all X features, and it is impossible to fix all bugs. That's the only weak side of the Open Source world - it is difficult to concentrate a lot of resources to implement just one very needed feature. However, I hope that the time was used wisely and it will be rock solid in a year.

@@gost "it is ready even if it is not ready" , no either it is ready for production or not - save minor bugs here or there; but if this project has been bogged by drama or something like that, its a shame, because the software itself has been in dev for a decade now; that is way more than enough time.

Yes, this is possible to do but not all distros are made by people who know how to change things. There’s a lot of Ubuntu based distributions but most aren’t that appealing imo.

And then do a full install anyway because upgrading never works fully, always some odd issue

that doesnt sound like a OS problem but an ISP problem, have you contacted your ISP?

@@michael_tunnell It‘s not the ISP. I have no problems with Windows and my other devices.

Using fprint-open on popos, I'm sure it's the same for fedora

@@GabrielGabeRodriguez taking up your advice after research i found out my device (goodix fingerprint device) is on the unsupported list for fprint thanks anyway

@@GabrielGabeRodriguez after some research i found out that my fedora comes with fprint but it doesn't support my sensor it's listed in their page for unsupported devices thanks anyway

🤨

I did not say it was the only possibility for issues, but rather I said that’s all that happened to me.

@@michael_tunnell I wonder, am I doing anything wrong? Does audacity and it's main cursor work for you with kde and wayland?

I dont have an answer for you because I do not use Audacity, I do not think it is that good. I use it only when I have to. Have you tried the fork Tenacity? That might work better.

@@michael_tunnell hi, I didn't know that this exists. Unfortunately I also didn't find a package for opensuse

doesnt look like it is packaged for opensuse but there is a verified Flatpak at flathub.org/apps/org.tenacityaudio.Tenacity again, not saying this is a solution, I have no idea lol

older native games still only run on X11 an many games just get ported to linux to run native then forgotten.

Thanks for commenting and sharing your thoughts. Breaking compatibility is certainly not good but in some ways it can be good in the long run like with trying to push Wayland forward for example. I dont think it is fair to say that Ubuntu is breaking debs for snaps though because they arent breaking debs necessarily, but instead they are focused on snaps because debs do have massive flaws and these flaws need something to address them. I like flatpaks better but snaps are bettter than debs in some ways. If you are referring to the app center not installing deb files anymore, they didnt do that for years even when the Software Center was DEB based because it is a different purpose. The Mac App Store doesnt launch when installed DMG files and Windows Store doesnt launch when EXE files are installed. Ubuntu's App Center doesnt have to support DEB files that are downloaded from the internet in my opinion, but they do need to support them in some way which is why they should just install "gdebi" by default. gdebi sole purpose is to install local deb files which is similar to how Mac has a DMG utility. I'd be okay with that. Compatibility on the other hand can't be provided forever . . . otherwise every Linux distro wouldn't be able to drop support for 32 bit hardware. 64 bit hardware has been the goto for 20 years and 32bit hardware isnt made anymore so keeping compatibility with those on new distro releases would be unnecessary but some people got really mad because they wanted to keep using super old hardware. As for Wayland, they are trying to make things work which is why people have been working on it for around 16 years but it takes time. For direct comparison sake, it took X 22 years to become a solid option for those looking to use Linux. Display Server timelines: First release: X = 1984 Wayland = 2008 The point of which Linux became a solid option for a large amount of people was around 2006. X had been out for 22 years and X11 had been out for 19 years at this time . . . yes X11 was the last major version of X and it was released in 1987. There is a reason it needs replacing.

God I hate YAML when it's longer than one screen, or with more than 3-4 levels of indentation.... It's seriously fragile, and config doesn't need more ways to break.

LOL what?! At what point in the video was I passive aggressive? I think you are just seeing me being tired but I’m curious where you see it that way

What part was TMI? It was a monster size episode so I dont disagree but which parts specifically lol

​@@michael_tunnell No, that's not it. I felt like the topics were all interesting; it just felt like too many in the same video.

LOL oh I gotcha. I saw TMI as "being excessive" on a specific topic as in I made a topic go too long and be boring. If you just meant TMI as in too much overall then yea I could see that since it was a pretty long episode. The reason I laughed though is because it amuses me based on the history of this show. You are saying there are too many topics and if you go back far enough you will find that some episodes ranged from 12-25 topics and the duration of these episodes were minimum 35 minutes with the longest being 1 hour 10 minutes 51 seconds. LOL adding to my amusement is that I removed 2 topics slots this episode because I knew it would be a long one 😆