If you are using :manjaro: #Manjaro or :arch: #Arch and you have #Nvidia graphics card, and you updated to Plasma 6, you are up for a nasty surprise, as after typing your password to login, you will get into a black screen. It seems X11 doesn't have this issue, but Wayland is completely toasted!
The only solution I found is to create /etc/modprobe.d/nvidia.conf and put these two lines in it:
@Mehrad thanks am going to try that. I had the first line in already but second must be key. Yes, bit worrying about the testing as many know there was an Nvidia issue to get fixed.
@dduque what made my #qemu blindingly fast (for a Windows VM) was to set aside a partition formatted to NTFS, instead of using the default virtual file on the host OS (also #manjaro Linux).
@ercanbrack Yes, I've heard good things about it again and again. But what would actually appeal to me more at the moment is pure Arch Linux or maybe VanillaOS 2.0. Let's see. I don't have the time for a new installation at the moment anyway. 🫣
It is a bummer that the only way to get #rstats on #Manjaro is through AUR. I have nothing but bad experiences of AUR in Manjaro, even if something works initially, it will break eventually.
I would love to have it in the Manjaro repos or as a #flatpak. It is officially available for #Linux on Ubuntu/Debian, Fedora and OpenSuse, so it ought to be possible.
On a related note, how difficult is it to turn a .deb file into a flatpak?
@waeiski@alxlg after 30 years of that I sometimes get a bit weary when it happens.
I remember I got invited to a physical party that led to a very very drunk me back in the fall of 1994 when I posted a ‘that’s not ok’ remark in alt.humor.jokes
Round about the time that #slackware was the ‘right choice’ since it ‘just worked’ in a sense that the default X configuration didn’t immediately blow up your monitor. 🤘🏻
Fives is back, only he's traded #Manjaro GNOME for Ultramarine Linux KDE!
Installing #Ultramarine was the simplest and easiest time I've EVER had installing Fedora. All of the proprietary stuff, extra repos, and drivers are already installed, making setup a breeze.
When I first dove into using #Linux full-time, #KDE was my desktop of choice. Now I've come back to a MUCH improved KDE after trying out #Cinnamon, #Xfce, and #GNOME, and I'm excited for #Plasma 6!
Maybe one of you #linuxaudio nerds knows. I'm trying to use the #plugin Instinct by Inertia Audio Systems with Bitwig Studio Flatpak, but Bitwig reports libwebkit2gtk-4.0.so.37: cannot open shared object file: No such file or directory, which makes sense, since the package is present in another version webkit2gtk-4.1 2.42.5-1 on my #manjaro system. I think this dependency is not ideal. But what could I recommend to the developers so that they could deliver the plugin in a "smarter" fashion?
Although some might not like #Manjaro because of how it is run/managed, I love it for the combination of easy installation combined with the software availability of #Arch. It's one of my favorite distributions for software development.
I liked it until a grub update nuked my work machine. Fixing grub issues with LUKS is not for the faint of heart. Then I switched to EndeavourOS, and the same thing happened again. Now I'm off of all Arch distros for the forseeable future.
I may give OpenSuSE Tumbleweed another try again. It needs more configuration out of the box (It doesn't even ask you for the hostname in the setup by default), but it's a solid distro.
So i finally switched to #wayland on #manjaro with #nvidia 545.29.06 and it is the first time it worked for me... i have some issues like vivaldi flickering like hell randomly.
Since i run #mastodon in vivaldi (because reasons) I am giving #tokodon as desktop client a try.
While it has some nice features i would like something more like the deck-layout with multiple columns, be able to search who you want to mention while writing and having a way to create threads. Any #fedihints for that?
@blackcoffeerider I get the point that he is disappointed that some core features are not working but to blame Wayland for the chaos that X11 and the workarounds for its age has caused is not the way to go to solve the mess created over many many years from my point of view. It is also at least partly wrong to ask to implement the same things again which are intended to be avoided.
@inpector the second article makes very good counterpoints to the whole argument but also admits that some things could have been approached better... the extremist angle is useless indeed...
#Brother fait juste bien les choses pour que son matériel soit reconnu sous linux.
Bon, sur ma #manjaro j'ai pas les droits pour scanner, il faut que je fasse un sudo, mais ça va se régler.
Sous #mageia, suffit de se servir du script bash proposer par le fabriquant et tout est OK.
@parigotmanchot je ne te jouerai pas le refrain à propos de l'OS de Microsoft.
Mais je compatis. L'obsolescence décidée par ces grosses boîtes c'est pénible.
Dernière en date ici, la squeezebox qui sert de réveil pour Madame dont les services en ligne viennent d'être déconnectés. Résultat, si tu n'es pas débrouillard, le matériel ne sert plus que de presse-papier.
@Tom23 Sur ce coup le tort semble partagé : Canon n'a pas sorti de drivers pour l'imprimante, programmant son obsolescence et MS pourrait avoir un driver universel...
Bref, de toute façon, elle déconne sec... ça précipite sa chûte sur le PC qui n'imprime pas habituellement, il reste l'autre PC sous Windows 10...