Yup, that’s the exact same problem I had. And I heard more stories of people having this problem. It’s bad…
Yup, that’s the exact same problem I had. And I heard more stories of people having this problem. It’s bad…
I had the same display failure, but 4 times in about 9 months. It made me pretty done with the whole thing. I only got the laptop back from the repair centre 2 or so weeks ago but I have no faith the issue is properly fixed now. Let’s see how it turns out, if it happens again I’m going to throw this thing out of the window.
Wayland hasn’t been experimental for a while. Both KDE Plasma and GNOME have defaulted to Wayland for a while now indicating it’s ready to be used. And in fact, scaling works better on Wayland than on X11 but I suppose ymmv.
I have the AMD edition and overall the laptop is nice but since I received the laptop about 9 months ago the screen broke 4 times. I only got it back 2 or so weeks ago from the repaircenter so I have only been able to actually use it for a few weeks. So my experience is pretty terrible so far. I honestly have no faith the screen is durably fixed this time but let’s see, I’m pretty done with it.
Distrobox is Toolbx but more portable (packaged on basically all distributions) and supports way more distributions as guests. I recommend using that if not on Fedora or you want to run a different guest than Fedora.
It’s off right now.
Also, inxi? Better use uptime
, that command is actually available on all systems and literally exists to check uptime.
It’s made in collaboration with Framework.
Thank you 🤗 I hope not too many people see us as obscure though…
It definitely makes it less interesting and feels the opposite of what Framework wants to do. I hope future models will be as replaceable and upgradable as their x86_64 machines.
Have you actually read the article? It mostly lists problems and reasons not to get a Tuxedo laptop. I’d advise to go for a Framework machine instead, they actually have good Linux support and do not require custom software written in Electron…
No, Lomiri. It is a succesor of Unity
Ubuntu Touch uses Lomiri (a successor of Unity), not GNOME.
Correction, hi postmarketOS dev here, we are using whatever the user wants. We ship Phosh, GNOME Mobile, Plasman Mobile, SXMO, Lomiri. We don’t have just one interface.
Correction, hi postmarketOS dev here, we are using whatever the user wants. We ship Phosh, GNOME Mobile, Plasman Mobile, SXMO, Lomiri. We don’t have just one interface.
You don’t have to configure KDE you know. You can just keep the defaults like you’re probably doing with GNOME.
You’re right, you can’t run the Android (or iOS app) twice. If you want a second device running WhatsApp you’ll need the web app.
I definitely hope so, so far it’s looking promising!
I think installing all those dependencies by hand is not a good solution in the long run.
Well, no. “In the long run” this gets packaged by distributions so you don’t have to compile anything. Right now it’s available for Alpine Linux and there is an AUR package for Arch.
Wasn’t there supposed to be a flatpack container to be downloaded somewhere?
There is a Flatpak (no c in that name!) base app available, and Newpipe has been packaged with that as a Flatpak, see https://flathub.org/apps/net.newpipe.NewPipe Ideally we get more stuff packaged up once more works but I don’t think it’s feasible to repackage everything out there so for a lot of applications you’ll just have to have a locally installed ATL outside of Flatpak.
Ok but you’re talking about Cinnamon. Cinnamon’s Wayland support is experimental sure, but that doesn’t mean Wayland itself is. I mentioned KDE Plasma and GNOME because they are the ones using Wayland for the longest now and have the best support for it and there it works better than X11.