Manjaro was my intro to Linux, but now that I know more about it, I can’t recommend it in good conscience. Letting their SSL certs expire is something that happens (even though they could automate it), but telling their users to change their clocks so it works is a big no-no.
Worse than that is how they manage packages from upstream. Simply freezing them for two weeks is, in my opinion, the worst of both worlds. You don’t get timely security updates, but you still end up with the issues of being on the bleeding edge - just late. It also means that if you use the AUR (which is really one of the biggest perks of Arch-based systems), it’s possible that the necessary dependencies are out of date.
I think that if one wants “Arch with an installer” they should go with EndeavourOS, or try the archinstall script.
Sure. When it comes to updates, Manjaro is pretty much doing what every single other distro is doing. Updates that are buggy don’t get pushed to the stable branch until they’re fixed up, and security updates tend to get pushed through faster than feature updates. The time period that updates get held up by is not a fixed duration, it depends on the specific package and update and can be anywhere between a few days and a few weeks.
As a concrete example, with some major Plasma updates Manjaro has waited for three or even four point releases (4 / 8 weeks) before considering it stable enough vs the newest point release of the previous major release, and following point releases after that get pushed to stable much faster.
As another point, even Arch has a very similar process… Their policy on pushing updates is far more geared towards pushing updates quickly than towards not breaking things, but otherwise it’s pretty much the same.
Manjaro packages start their lives in the unstable branch. Once they are a deemed stable, they are moved to the testing branch, where more tests will be realized to ensure the package is ready to be submitted to the stable branch
However, Valve notes the fact that enabling hardware acceleration on NVIDIA GPUs may cause X11 to crash. As such, hardware acceleration will be disabled by default for NVIDIA systems. In addition, Valve says that DPI scaling may not work correctly when hardware acceleration is disabled.
What happened to Nvidia open sourcing their graphics driver last year? It seems like nothing came out of it. I know the userland is still closed, but wasn't there an effort to include the driver in Mesa?
I’m not too sure, but I wish there was more action from the code being open sourced. I remember reading a little while back some newer code was leaked for NVIDIA as well, but pretty much the similar issue as there hasn’t been too much done with the info as far as I know.
I’ll take it! Was experimenting with Wayland on Plasma yesterday on my 1080 TI. Still a bit glitchy. Some issues with wine (although it might be Plasma related). But it seems like slowly getting better. I’ll check it out with the new drivers once they are on Fedora and see what happens.
No, they won’t. The community-driven KDE team at Fedora plans to drop the X11 session but that’s not a Red Hat thing. Fedora will support X11 for the time being. No plans to drop any of the many other X11 desktops at all.
Little late to the party, but I’ll chime in. I have a 3080, and for the most part, Wayland works, but there are a few problems that keep me from using it as a daily driver. G-Sync doesn’t work at all, and when I put my PC to sleep, upon wake I end up needing to do a full reboot because of severe graphical issues. When it is running though, it’s pretty smooth, with only a few graphical issues here and there. I still daily drive X11 though until the major bugs are fixed.
That is exactly why I choose to use FOSS including Linux. As much as I want to standby this principle, I have come to a breaking point after dealing with its issues, issues we have all experienced. I believe it is hands down the best choice for server use, but for work and productivity, I need something more matured that is going to work out of the box. I am glad that the community here took this criticism well but I think it’s important to discuss and understand that there are still some strides to be made. But at the end of the day, I’m just some guy ranting and who knows, maybe I’ll be installing a Linux distro after a month of using Mac OS.
This summer I use Linux on my desktop for 25 years. What do you think the first years looked like? My first laptop took me 3 weeks to get it properly installed with Suse back in 1998. For the last 10 years installing and configuring whatever distro is a piece of cake. Ofcourse soms things are not as you want them to be: the good thing is you can change everything in FOSS, and if it does not excist you can create it. People complaining at Linux Desktop are realy complaining on their own limitations. Don’t complain! Not about yourself. Not about the Linux Desktop. Never ever give up! Make your list of whats not working for you. And than work and change until your list is history. Keep your head up strong. You’ll never walk alone!
Same story, same tips, but I started with SuSE Linux 4.3 in 1996. Just try stuff, read the error messages, read docs and ask. A lot of peaople who know stuff are happy to help out of altruism or the chance to show off. ;-)
You can kinda make it bend a bit to your whim. While it is technically immutable if you don’t mess with it, it does have everything necessary for using pacman. It just all reverts next time steamos updates. Anything you install directly through the discover portal is permanent, but it does technically have access to anything in the pacman repos as well.
I unlocked mine long enough to download neofetch and take the screenshot for this. It’ll revert back soon, but I only needed it temporarily for imaginary internet points. :)
My laptop is my oldest install, running Ubunutu. Started out on 14.04 and I’ve been updating ever since. My desktop runs Arch, although it used to be Antergos. I kinda convinced it to be Arch after Antergos died so I kept getting updates. Finally I’m currently trying Fedora on my secondary PC filled with old hardware from previous builds.
Honestly, out of these I personally like Fedora most currently. It seems to have up-to-date enough packages and seems quite stable. The AUR on Arch is a powerful thing, but it can also be quite hit or miss. While Ubuntu was fine as a first distro, I don’t really like how outdated all the packages are. I’ve had quite a few cases where packages where more than a year out of date.
Currently… Slackware on main laptop. Slint (Slackware-based) on mini-pc. MX Linux (fvwm respin), Void, and OpenBSD on old laptop. NsCDE is desktop on all except MX.
My laptop is on Manjaro and has been running flawlessly for years …such a great experience with gnome 40+
My desktop is also on Manjaro, and things could not be more different. No Wayland, no animations in the gnome desktop, visual glitches since the last update …guess it doesn’t play well with Nvidia drivers. Anyone managing something decent with gnome+Nvidia?
Skeptical. Writing a graphical UI toolkit is a freight train of work. I’m positively curious about anything that’s not GTK but I’m not sure going with a new toolkit is the right decision. Qt is the mature kid on the block that’s been proven in more environments than I can count. Moreover it’s a complete application framework with a ton of convenience libraries needed for speedy development already included. I guess those can be supplanted in the form of separate Rust libs. Personally I’d have gone with Qt for such a project but I’d be happy to be proven wrong.
This is coming from personal experience/opinion, but after trying to create a simple app in GTK4 Rust bindings I was so confused because of how alien the programming style was compared to typical Rust programming. After trying Iced it was much simpler and made so much more sense, no silly decorators or anything, you can define the view and the update loop separately, and interactions are handled by messages using pattern matching. The inheritance based OOP doesn’t work well with Rust, and Iced has none of it, because it was made for Rust specifically.
I’m guessing QT bindings are similarly in a different style of programming and can’t imagine that meshing well with native Rust code. Iced has a lot of merits to it and having the opportunity to both help it develop and use a native Rust framework in a Rust project makes a lot of sense.
Fedora is also worth a look, Debian was my first distro so I always appreciate keeping up with it. But Fedora is SUPER stable and also a top option for privacy and security, so I switched over.
Maybe because he’s not “American” and comes from a country with regulations like the rest of the world, and people care when they vote to make things work.
And like most of the rest of the world, there are more than two political parties, and is not a drama show.
He has American citizenship and lives in America, he’s talking about America here. And I promise you that other countries, yes even those in the magical fantasy land of Europe, also have lots of political drama despite having more than two parties in the government (They tend to form alliances based on left/right and split into two blocks anyway).
I know, im from Europe.
The drama is not compared to USA, we don’t vote on celebrities.
In my country we even have a party for the animals and climate, so when USA still trying to vote for basic rights, we already ahead and vote for animal rights and more climate change.
linux
Top
This magazine is from a federated server and may be incomplete. Browse more on the original instance.