Snaps were designed to solve dependency hell, get modern software, security, among other issues. If it weren’t for the fact Flatpak does a better job, many more people would be praising Snap.
It’s good that Canonical is trying to make the desktop better. It would be better if they focused their efforts elsewhere.
I run all headless Linux machines, and snapd always managed to show up somehow. It’s got shared lib dependencies so that shit like Firefox would be installed and have snap mount points on my machine. Just a bunch of useless noisy garbage on a headless machine. I finally solved the problem by switching to Debian.
I don’t care what flatpak does or does not do, IMHO snap sucks objectively.
Flatpak is intended for end-user graphical applications, not many terminal applications are packaged by Flatpak so it makes sense why it wouldn’t show up. Snap IIRC was first intended for their embedded system.
According to this review they got 10 hours with wifi off, playing a 720p video that was stored locally on the machine. Youtube is going to have plenty of background tasks going on, wifi is going to be active downloading things, and you’ve probably got more than just youtube in the background so I would consider 5 hours to be expected without really delving deep into power saving (and probably killing performance).
Wayland replaces the older X protocol. It doesn’t have to operate with older protocols. You might be thinking of XWayland which is a proxy that receives X API calls from apps written for X, and translates those to the Wayland API so that those apps can run under Wayland implementations. Window managers can optionally run XWayland, and many do. But as more apps are updated to work natively with Wayland, XWayland becomes less important, and might fade away someday.
PipeWire replaces PulseAudio (the most popular sound server before PipeWire). Systems running PipeWire often run pipewire-pulse which does basically the same thing that XWayland does - it translates from the PulseAudio API to the PipeWire API. It’s a technically optional, but realistically necessary compatibility layer that may become less relevant over time if apps tend to update to work with PipeWire natively.
So no, both Wayland and PipeWire are capable of operating independently of other protocols.
youre right i was thinking of xwayland, tysm. also, yes i was thinking of pipewire-pulse. i was worried these compatibility layers WERE the programs in their entirety. as in, they had no protocols themselves but rather optimised older, deprecated ones.
I use 3. I never use anything integrated into an IDE for some reason, never started and probably never will.
Yakuake as drop down terminal 90%
Black box for nice looking full screen terminal for full screen.
Dolphin with emulator on bottom for niche things
If I could only have one for the rest of my life I’d be torn between Yakuake and Konsole. I love Konsole though, used it for years and is all round great for sticking with the DE aesthetics and integrating with themes.
Others have brought up open source solutions already so on a different note I’ll say I’ve used the (closed source and paid) Insync client successfully in the past, and it worked fine. An interesting bonus is you can have it on both Windows and Linux pointing to the same set of files if you dual boot and it’s supposed to work just fine.
Well Li-ion batteries are known in conventional wisdom to degrade to 70% of brand new battery life after being charged 500-1000 times. So if it was supposed to have 8 hours when new then 5-6 makes sense.
When I played around with my laptop’s power settings, the LCD screen and screen-brightness were a big power draw between 3W at dim to like 15W at max. That and all wireless functions off, if you can have an ethernet cord plugged in, no bluetooth or USB devices plugged then you can maximize your battery life. Years ago I got my laptop to host a minecraft server with screen off to like 4-5 W at idle.
E: And don’t forget if you have a backlit keyboard to turn that off.
ping 8.8.8.8 fails, and I don’t have traceroute installed (and no internet to install it)
<span style="color:#323232;">tubbadu@debianserver:~$ ip route show
</span><span style="color:#323232;">0.0.0.0 dev veth3492bf7 scope link
</span><span style="color:#323232;">0.0.0.0 dev vethc1bf668 scope link
</span><span style="color:#323232;">0.0.0.0 dev vethb41fd7e scope link
</span><span style="color:#323232;">0.0.0.0 dev veth2e39932 scope link
</span><span style="color:#323232;">0.0.0.0 dev veth68451d9 scope link
</span><span style="color:#323232;">default dev veth3492bf7 scope link
</span><span style="color:#323232;">default dev vethc1bf668 scope link
</span><span style="color:#323232;">default dev vethb41fd7e scope link
</span><span style="color:#323232;">default via 192.168.1.1 dev enp1s0
</span><span style="color:#323232;">169.254.0.0/16 dev veth68451d9 proto kernel scope link src 169.254.210.75
</span><span style="color:#323232;">169.254.0.0/16 dev veth2e39932 proto kernel scope link src 169.254.242.12
</span><span style="color:#323232;">169.254.0.0/16 dev vethb41fd7e proto kernel scope link src 169.254.185.90
</span><span style="color:#323232;">169.254.0.0/16 dev vethc1bf668 proto kernel scope link src 169.254.225.22
</span><span style="color:#323232;">169.254.0.0/16 dev veth3492bf7 proto kernel scope link src 169.254.123.220
</span><span style="color:#323232;">172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1 linkdown
</span><span style="color:#323232;">172.18.0.0/16 dev br-56cf32fc7cde proto kernel scope link src 172.18.0.1
</span><span style="color:#323232;">192.168.1.0/24 dev enp1s0 proto kernel scope link src 192.168.1.9
</span><span style="color:#323232;">192.168.1.1 dev enp1s0 scope link
</span>
This is kind of a nutty network config. It looks like docker is setting up extra default routes, which I could easily see fouling everything up. As a first experiment (warning, this may ruin your networking until the next reboot):
ip route flush 0/0
ip route add default via 192.168.1.1 dev enp1s0
... and see if that makes things work (start with ping 192.168.1.1 and ping 8.8.8.8). If that solves the problem, then I think something about your docker config is adding stuff to your networking that's causing the problem; maybe remove/disable docker completely and then re-add docker things one at a time to see where the problem comes in.
okay, I thought to have solved the problem but I was wrong, here I go again. When I docker compose up -d the immich server (the only one I have installed) all those routes are created, and apparently some of them conflicts with something else and now my host has no internet connection. however it seems that ip route flush 0/0 solves the problem until the reboot, which is strange. the other command returns RTNETLINK answers: File exists
Hm. Yeah, that's weird. The default routes you're seeing should basically never exist, so it sounds like there's some kind of manual network config happening inside the Docker container that's creating a broken network.
What does docker network inspect [network] say for each of your Docker networks (substituting each Docker network for "[network]")? What's the network section of docker-compose.yml look like?
Pipewire is a modern audio server that can drop-in replace the mess that is alsa, pulse audio, jack, etc.
Wayland is a communication protocol made to be a replacement for the X11 protocols, with it’s compositer implementations being the replacement for Xorg.
Is there a reset button somewhere on the router? Most of them have something like this in order to reset them to factory settings. If not, google for your device name and factory reset, maybe it’s something like „press button while turning on“ etc. I’d try something like that
Go to the outer status page. The router should display whether it has an internet connection to your provider. If no, then your router/modem has no credentials or another issue preventing access.
If it shows as working, then you can narrow it down to incorrect DNS and IP routing. Perhaps dynamic IP allocation is set to off or another configuration error or bug, in which case you might need to reset all the router settings. Then, is it only broken for a single end device?
thanks for the reply! Sorry it isn’t very clear from the post, but yes only one device (debianserver) has this problem (no internet connection, but yes local network connection), all other devices works as before. I’ll update the original post to clarify this
It’s a common wayland problem. Try editing xf86config to force the scanrate to something your monitor supports rather than relying on dpms ddc/ci auto config
linux
Oldest
This magazine is from a federated server and may be incomplete. Browse more on the original instance.