When any pc starts, isn’t there the boot up menu etc? I’m referring to that. In that menus there are options of remote access or firmware updates etc apart of course the usual setup options like in what turn the boots take place eg HDD, network, dvdrom , USB and others like time, date etc.
Intel ME is one concern yes but I doubt I can flash corevoot on this machine as it is almost 2 years old.
So this comment made me realize pipewire.service wasn’t enabled (I had to use the command ‘systemctl --now enable pipewire --user’ as the ones you provided didn’t work on my system.)
It’s up and running now, but after a reboot I still have the same issue.
It wasn’t, but this still doesn’t fix the issue. I’m honestly perplexed and might just deal with triple reinstalling alsa-utils after every reboot. I’ll probably start from a fresh install soon enough anyway :P
Yes, which is why it is a little odd for the article author to include it without context, because we all immediately think of one social mistake that has nothing to do with Linux.
He did mention the murder of his wife and said he would detail his regret to anyone who asked. The rest of the letter describes the “social mistakes” in dealing with co-workers and the Linux community. He even asks that those co-workers’ names be added to the credits and his negative comments about them be deleted. There’s no forgiving what he did to his wife but there’s at least some evidence he’s changed since that happened.
He did mention the murder of his wife and said he would detail his regret to anyone who asked.
This is true - I’m reacting more to the title than the content. It’s a very peculiar choice of words.
There’s no forgiving what he did to his wife but there’s at least some evidence he’s changed since that happened.
Perhaps - it’s hard to tell. It still reads a lot like one of his standard narcissistic rants even as he’s complimenting others. It’s still all about his “dream”.
I’m not a doctor but he certainly seems neurodivergent based on his writing. It’s hard to imagine him ever changing in some significant way and being “rehabilitated” enough to be allowed back into society, hence the “some evidence”. It’s might be best he remains in jail rather than be paroled.
Yeah - I mean - I don’t want to get into the business of analyzing somebody’s metal state but he definitely seems to have issues with fixation. But I also don’t want to cross the line into saying that he’s necessarily dangerous because of that. He’s dangerous for other reasons though. I agree with your “some evidence” line in that he does seem to be focusing on the part of his personality that does seem to be the most dangerous - inability to manage conflict. Prison does provide for that conflict - but it also provides many rules and structures that he wouldn’t have on the outside. Dunno. I have a difficult time saying that anybody who has murdered their wife should ever see freedom again at all - “reformed” or not.
While I think that 5h of battery life with yt videos running is ok for a t490 you could still try to recalibrate the battery with tlp.
I have a t470s (has two internal batteries) where suddenly the performance of one of the batteries somehow got really bad. After calibration it works as good as before (upower says it’s at about 80%). I did the calibration in windows tho with Lenovo vantage as I’m still running a dual boot setup and didn’t know about tlp before.
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
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
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
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.
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?
linux
Newest
This magazine is from a federated server and may be incomplete. Browse more on the original instance.