Debian operating system

I have suddenly found that /usr/games has disappeared off my path. Not only that but my normal otherwise but sudo enabled user seems to have a superuser's path?

rhudson@adam:~$ echo $PATH /usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin

rhudson@adam:~$ id -u 1000

What would have changed suddenly? It was not like this yesterday. kpat is in /usr/games and I was able to launch it from task manager yesterday, but not today.

I have rebooted twice so far. I can run kpat by opening it from Dolphin.

I don't want to have to re-install : ^ (

Hi, I am building the Linux kernel, with the following make command to enable multi core compilation: make -j. This ends up freezing the system and eventually some applications get killed (I am using KDE). If I pass an argument to -j, then system compiles normally. However, full multi-core compilation is enabled when no argument is specified.

I am on Debian stable, kernel 6.1.0-13-amd64. Is there a way make system do full multi-core compilation without freezing the system?

I installed Bookworm, Docker and Frigate (in docker) on an older i5 Dell with a Coral TPU (USB) and an old GeForce 6600 GPU, the TPU and GPU are for use with Frigate frame processing and video conversion. It was working well for months and then I upset the apple cart by adding whisper and Piper in the docker for my Home Assistant (different server) to use. After I got that all working I noticed that Debian would freeze after several hours of no user use (no one logged in either on the console or SSH). This seems to happen now even after I removed the Piper and whisper containers. Thinking it might be a suspend issue I masked all the suspend points and set the power profile to “never” but that did not help. Looking at journalctl does not show anything I can see, it seems to just stop logging at the freeze point, interestingly the ethernet jack still shows activity but no ping :(

What would be the next troubleshooting steps to find what is causing the freeze?

By Jonathan Corbet October 23, 2023

Debian 12 (Bookworm) My Wi-Fi has just started randomly dropping the connection and re-connecting. It seems to connect and pass data normally until it decides to drop again.

I thought I solved this part by disconnecting and re-connecting myself but no it just deactivated and activated just now again.

I also have a wired connection.

Is there any issue with having both a wired connection and a wireless one at the same time?

Does it do any good? That is does the network traffic balance over the two connections give a little more bandwidth?

Update 1: For now until I can reboot I have disabled the wi-fi connection.

Update 2: The Wife works at home on wi-fi and says her connection has been bad this afternoon too. I rebooted and I still have the problem.

cross-posted from: https://monero.town/post/824123

Implements support for waydroid in vso, this includes creating and deleting a waydroid container, as well as using fdroid repositories to install and search for applications.

Listening to high quality audio with Bluetooth headphones is now easier than ever on @Raspberry_Pi thanks to @debian Bookworm and @pipewire!

I have an annoying problem on my server and google has been of no help. I have two drives mirrored for the OS through mdadm, and I recently replaced them with larger versions through the normal process of replacing one at a time and letting the new drive re-sync, then growing the raids in place. Everything is working as expected, with the exception of systemd... It is filling my logs with messages of timing out while trying to locate both of the old drives that no longer exist. Mdadm itself is perfectly happy with the new storage space and has reported no issues, and since this is a server I can't just blindly reboot it to get systemd to shut the hell up.

So what's the solution here? What can I do to make this error message go away? Thanks.

[Update] Thanks to everyone who made suggestions below, it looks like I finally found the solution in systemctl daemon-reload however there is a lot of other great info provided to help with troubleshooting. I'm still trying to learn the systemd stuff so this has all been greatly appreciated!

I'm actually looking forward to trying the new @Raspberry_Pi desktop based on @debian Bookworm.

I've never run a desktop on my Pis, I run them all headless, but I'm curious what the performance is like now with Wayland and Pipewire (both things I run on my actual desktop/laptop).

I've got a Pi4 in an Argon One with m.2 SSD just waiting to try it.

First test will be 4K Netflix/Disney+ in @firefox thanks to that Widevine availability 👌

I've been fighting an install of the latest Gnome iso. Got a working install now, but the CPU is always chugging, even at idle on the desktop. I know that previously this machine was buttery smooth. But now my cursor can't even smoothly move across the screen.

Occasionally, the task tray button area will acknowledge my screen can flip.

More often though, it doesn't show the rotation option.

My Wi-Fi card works, but cuts out if Bluetooth is active. I know this is a sign it isn't using the correct drivers, as this issue didn't exist prior.

Ath10k needs to be loaded, and no amount of installing it via Synpatic puts it where it needs to be.

I'm wondering if since the machine no longer has a battery... can that screw up something in the detection of hardware? Is it possible I'm missing something on a deeper level?

I know this machine was far quicker and smoother on the prior Debian release... and the battery was still present when it was installed... but it became a spicy pillow in the meantime and had to be disposed of.

Still losing my mind over this.

I've been unsuccessful in getting a properly working system today, installing from a freshly downloaded LiveGnome.iso from the Debian page.

The first install actually crashed, because the USB drive was jostled.

The second install went fine, but had no USB support (hub devices seen, but no attached devices seen)

Now I'm doing a third install.

cross-posted from: https://lemmy.myserv.one/post/2233387

If you like Debian and like to help make it better, and also want to use testing please review this guide where I try to cover many common things and improve your experience:

https://makedebianfunagainandlearnhowtodoothercoolstufftoo.computer/doku.php?id=start

Thanks for being a Debian testing user :)

I have been struggling with this for over a month and still keep running into a brick wall. I am building a new firewall which has six network interfaces, and want to rename them to a known order (wan[0-1], and eth[0-3]). Since Bullseye has stopped honoring udev rules, I have created link files under /etc/systemd/network/ for each interface based on their MAC address. The two WAN interfaces seem to be working reliably but they're not actually plugged into anything yet (this may be an important but untested distinction).

What I've found is that I might get the interfaces renamed correctly when logging in from the keyboard, and this continues to work for multiple reboots. However if I SSH into the machine (which of course is my standard method of working on my servers) it seems to destroy systemd's ability to rename the interface on the next boot. I have played around with the order of the link file numbers to ensure the renumbering doesn't have the devices trying to step on each other, but to no avail. Fixing this problem seems to come down to three different solutions...

• I can simply touch the eth*.link files and I'm back up afte a reboot.
• Sometimes I have to get more drastic, actually opening and saving each of the files (without making any changes). WHY these two methods give me different results, I cannot say.
• When nothing else works, I simply rename one or more of the eth*.link files, giving them a different numerical order. So far it doesn't seem to matter which of the files I rename, but systemd sees that something has changed and re-reads them.

Another piece of information I ran across is that systemd does the interface renaming very early in the boot process, even before the filesystems are mounted, and that you need to run update-initramfs -u to create a new initrd.img file for grub. OK, sounds reasonable... however I would expect the boot behavior to be identical every time I reboot the machine, and not randomly stop working after I sign in remotely. I've also found that generating a new initrd.img does no good unless I also touch or change the link files first, so perhaps this is a false lead.

This behavior just completely baffles me. Renaming interfaces based on MAC addresses should be an extremely simple task, and yet systemd is completely failing unless I change the link files every time I remote connect? Surely someone must have found a reliable way to change multiple interface names in the years since Bullseye was released?

Sorry, I know this is a rant against systemd and this whole "predictable" naming scheme, but all of this stuff worked just fine for the last 24 years that I've been running linux servers, it's not something that should require any effort at all to set up. What do I need to change so that systemd does what it is configured to do, and why is something as simple as a remote connection enough to completely break it when I do get it to work? Please help save my sanity!

(I realize essential details are missing, but this post is already way too long -- ask what you need and I shall provide!)

tl;dr -- Systemd fails to rename network interfaces on the next cycle if I SSH in and type 'reboot'

Debian 12.1 (6.1.0-11-amd64) running LXD/LXC and on an unprivileged container setting security.idmap.isolated=true seems to fail to update the owner/group of the container's files.

Here is an example:

# lxc launch images:debian/12 debian
(...)

# lxc config get debian volatile.idmap.base
296608

# lxc stop debian
Error: The instance is already stopped

# lxc config set debian security.idmap.isolated true

# lxc config get debian security.idmap.isolated
true

# lxc start debian

Now if I list the files on the container volume I'll get they're all owned by the host root user:

# ls -la /mnt/NVME1/lxd/containers/debian/rootfs/
total 24
drwxr-xr-x 1 root   root  154 Sep  5 06:28 .
d--x------ 1 296608 root   78 Sep  5 15:59 ..
lrwxrwxrwx 1 root   root    7 Sep  5 06:25 bin -> usr/bin
drwxr-xr-x 1 root   root    0 Jul 14 17:00 boot
drwxr-xr-x 1 root   root    0 Sep  5 06:28 dev
drwxr-xr-x 1 root   root 1570 Sep  5 06:28 etc

I tried multiple versions of LXD/LXC. This happens with both 5.0.2 from apt as well with 4.0 and 5.17 (latest) from snap.

Interestingly enough I have another Debian 10 (4.19.0-25-amd64) running and older LXD 4 from snap and on that one things work as expected:

# ls -la /mnt/NVME1/lxd/containers/debian/rootfs/
total 0
drwxr-xr-x 1 1065536 1065536  138 Oct 29  2020 .
d--x------ 1 1065536 root      78 Oct 14  2020 ..
drwxr-xr-x 1 1065536 1065536 1328 Jul 24 19:07 bin
drwxr-xr-x 1 1065536 1065536    0 Sep 19  2020 boot
drwxr-xr-x 1 1065536 1065536    0 Oct 14  2020 dev
drwxr-xr-x 1 1065536 1065536 1716 Jul 24 19:08 etc

As you can see on this systems all the files are owned by 1065536:1065536.

Update:

I tried to probe around the maps with lxc config show debian in both machines and I saw this:

Machine running Debian 10:

security.idmap.isolated: "true"
(...)
volatile.idmap.base: "1065536"
volatile.idmap.current: '[{"Isuid":true,"Isgid":false,"Hostid":1065536,"Nsid":0,"Maprange":65536},{"Isuid":false,"Isgid":true,"Hostid":1065536,"Nsid":0,"Maprange":65536}]'
volatile.idmap.next: '[{"Isuid":true,"Isgid":false,"Hostid":1065536,"Nsid":0,"Maprange":65536},{"Isuid":false,"Isgid":true,"Hostid":1065536,"Nsid":0,"Maprange":65536}]'
volatile.last_state.idmap: '[{"Isuid":true,"Isgid":false,"Hostid":1065536,"Nsid":0,"Maprange":65536},{"Isuid":false,"Isgid":true,"Hostid":1065536,"Nsid":0,"Maprange":65536}]'

Machine running Debian 12:

security.idmap.isolated: "true"
(...)
volatile.idmap.base: "231072"
volatile.idmap.current: '[{"Isuid":true,"Isgid":false,"Hostid":231072,"Nsid":0,"Maprange":65536},{"Isuid":false,"Isgid":true,"Hostid":231072,"Nsid":0,"Maprange":65536}]'
volatile.idmap.next: '[{"Isuid":true,"Isgid":false,"Hostid":231072,"Nsid":0,"Maprange":65536},{"Isuid":false,"Isgid":true,"Hostid":231072,"Nsid":0,"Maprange":65536}]'
volatile.last_state.idmap: '[]'

Why didn't it populate volatile.last_state.idmap: '[]'?

How can I fix it? Thank you.

Hi everyone, so I'm having this weird issue. No matter the DNS and IP settings I use in NetworkManager, it will always generate the same resolv.conf.

resolv.conf

# Generated by NetworkManager
nameserver ::1

IPv6 is disabled by the way.

Debian turns 30 today!

https://simplex.chat/contact#/?v=1-4&smp=smp%3A%2F%2Fhejn2gVIqNU6xjtGM3OwQeuk8ZEbDXVJXAlnSBJBWUA%3D%40smp16.simplex.im%2F9qOMeGL2HgMCDCZ1G6GDw0uI9JIzIBHC%23%2F%3Fv%3D1-2%26dh%3DMCowBQYDK2VuAyEAAhYJRP2-VnRiIOapCcmXpat2byJIb_XSlX95oIHy7xg%253D%26srv%3Dp3ktngodzi6qrf7w64mmde3syuzrv57y55hxabqcq3l5p6oi7yzze6qd.onion&data=%7B%22type%22%3A%22group%22%2C%22groupLinkId%22%3A%22NYwp2h1tY2L8xXGOApn2UA%3D%3D%22%7D

With contributions in that room and various 'Jitsi Meet' events from Kochi.

These annual 'DebConfs' and several 'MiniDebConfs' in a year, are a unique selling point of Debian and springs from the spirit, philosophy of GNU/Linux. Opening these events around the world to Debian users and getting them involved is the idea behind them.

Debian also lives from the discussion of controversial topics. For this, I think, Jitsi Meet lends itself.

😃

I've been running systems up to Buster and have always had the 'quiet' option in the grub settings to show the regular service startup messages (the colored ones showing [ok] and such but not all the dmesg stuff). I just upgraded a server to bullseye and there are zero messages being displayed now except an immediate message about not being able to use IRQ 0. Worse, google can't seem to find any information on this. If I remove the quiet option from grub then I see those service messages again, along with all the other stuff I don't need.

What is broken and how do I fix this issue? I assumed it would be safe to upgrade by now but this seems like a pretty big problem if I ever need to troubleshoot a system.

[Edit] In case anyone else finds this post searching for the same issue… Apparently the trick is that now you MUST install plymouth, even on systems that do not have a desktop environment. For whatever reason plymouth has taken over the job of displaying the text startup messages now. Keep your same grub boot parameters (quiet by itself, without the splash option) and you will get the old format of startup messages showing once again. It’s been working fine the old way for 20+ years but hey let’s change something just for the sake of confusing everyone.

[Edit 2] Thanks to marvin below, I now have a final solution that no longer requires plymouth to be installed. Edit /etc/default/grub and add systemd.show_status=true to GRUB_CMDLINE_LINUX_DEFAULT. In my case to full line is:

GRUB_CMDLINE_LINUX_DEFAULT="quiet systemd.show_status=true"

Don't forget to run update-grub after you save your changes.

[Solved by going to X11]

I am working with my Debian 12 system and suddenly the whole screen goes blank and comes right back. I am not sure what triggers it, it seems to happen when I am exiting a program, I think when It comes back any program I had running is gone now. This is very intermittent and does not happen very often.

Here as a start have a neofetch:

OS: Debian GNU/Linux 12 (bookworm) x86_64

Host: VivoBook_ASUSLaptop S5402ZA_S5402ZA 1.0

Kernel: 6.1.0-11-amd64

Uptime: 12 hours, 2 mins

Packages: 2361 (dpkg)

Shell: bash 5.2.15

Resolution: 2880x1800

DE: Plasma 5.27.5

WM: kwin

WM Theme: plastik

Theme: [Plasma], Breeze [GTK2/3]

Icons: [Plasma], breeze-dark [GTK2/3]

Terminal: konsole

Terminal Font: Hack 19

CPU: 12th Gen Intel i7-12700H (20) @ 4.600GHz

GPU: Intel Alder Lake-P Memory: 3406MiB / 11577MiB

I did journalctl -b - there is a crazy amount of detail in there.

If there is anything specific I can do, please let me know - I am more than a noob, but a lot of the time I only know just enough to be dangerous.

Thanks!

Running Bookworm, Plasma DE if that's relevant.

Background: I'm learning here. Decent amount of coding and embedded hardware experience but I'm usually missing one or two key concepts with this stuff.

Getting a box running, and wrestling with NVIDIA drivers. I successfully installed the driver (I think), but now lightdm isn't working. From what I read it appears there's a common issue around a race condition where lightdm tries to fire up before the drivers ready, so I need to add the nvidia driver to initramfs.

Can anyone give me some pointers? Specifically while I get the above:

1. I'm not sure what modules need to be added and if they're named something specific for debian vs other distros
2. The correct file to modify
3. The correct format/syntax that needs to be added

I've found lots of examples, just none specific to debian, and screwing around at this level I don't want to bork something enough I need to do a bare install.

Thanks for any help!

Edit: Solved for now, going to use Flatpak Steam and Flatpak Lutris to automatically use recent Mesa versions from freedesktop-sdk.

I recently switched from Arch to Debian Stable and so far I've been able to get updates for everything I actually need to keep modern from Flatpaks, Homebrew, personal backporting, compiling from source, etc. It's going well, and I think that stable base + a dozen cutting edge pieces of software is a better strategy for a modern desktop in general than something like Arch, where the entire system is bleeding edge.

The one thing I'm not sure about is getting a recent Mesa version - right now it doesn't matter much, but the Mesa that shipped with Bookworm was already half a year old on launch, so it might be 2.5 years old by the next release. If I end up wanting a newer Mesa version at some point before the next release, is there a recommended way to do it? I've read that backporting Mesa doesn't work very well, so it's probably not going to be a backport in the future.

I've found this script to build a local Mesa environment and allow arbitrary applications to use it instead of the system version, and it seemed to work well in a VM with some tests. You can specify which Mesa version to build, so I'm planning on building the latest stable Mesa branch if needed (e.g. not an x.x.0 release).

It seems like this is the way to go, but I'm wondering if anyone else has dealt with this problem before, and what the recommended path to solve it is if so. As before, I'm not sure I'll need a new Mesa in the next 2 years, but if I do I want to have a plan ready that doesn't push me to move to Sid or a new distro.