Debian operating system

#i386 machines running #Debian 12 Bookworm

@debian@lemmy.ml

Debian 13 drops support for i386, which is bad news for my parents' laptops. I don't have the time to help them hop on a different distro right now, but I wonder if anybody here is in the same boat.

@VoidLinux@chaos.social and @alpinelinux@fosstodon.org, my two faves, still offer support. FreeBSD demoted i386 to tier 2 in 2021. What else is out there?

Previously on Debian 12 I followed a guide to install the AAC audio codec for my Air Pods yet after upgrading to Debian 13 I seem to have lost the codec as I can no longer select it in KDE sound settings leaving only A2DP/SBC and A2DP/SBC-XQ, now I’m a bit at a lost as I remember all I had to do was put a aac.so file into /usr/lib/x86_64-linux-gnu/spa-0.2/bluez5/

Bluez5 directory list:

• libspa-codec-bluez5-sbc.so
• libspa-codec-bluez5-opus-g.so
• libspa-codec-bluez5-opus.so
• libspa-codec-bluez5-ldac.so
• libspa-codec-bluez5-lc3.so
• libspa-codec-bluez5-g722.so
• libspa-codec-bluez5-faststream.so
• libspa-codec-bluez5-aptx.so
• libspa-codec-bluez5-aac.so
• libspa-bluez5.so

Anyone here by chance know a solution to this?

Are you contributing to Debian? Check out suggested best practices for submitting and reviewing Merge Request on Salsa, Debian's GitLab instance.

Are there any security things I should set up or configure after installing Trixie for normal desktop use?

I would assume that Debian ship it in good shape out of the box. Or should I look at things like firewall and apparmor?

I've downloaded an iso for trixie but I can't see any checksums for it on the website. The 'Verifying Authenticity' page makes it sound like the download should include something but all I got was the .iso file.

How do verify it?

Thanks

cross-posted from: https://lemmy.ml/post/34425422

It is with huge pleasure that the Debian GNU/Hurd team announces the release of Debian GNU/Hurd 2025.

This is a snapshot of Debian "sid" at the time of the stable Debian "Trixie" release (August 2025), so it is mostly based on the same sources. It is not an official Debian release, but it is an official Debian GNU/Hurd port release.

Images can be downloaded from here: https://www.debian.org/distrib/

According to this @phoronix article @debian #Trixie (targetting 9th August) to still work on the #RISCV HiFive Unleashed board? I've still got a couple kicking around and this seems like a useful way to update it!
This article suggests their build farm is on HiFive Unmatched hardware for now: https://www.phoronix.com/news/Debian-13-RISC-V-Ready

So I've upgraded to trixie and it comes with apt 3. For some reason the new apt insists on opening the output of some commands in less. For example, "apt list --upgradable" or "apt search" opens the output i less. I can't find how I turn this behavior off. Any advice?

What is the easiest way to track how close to stable release Debian 13 is?

I'd like to get an informed idea about a release date, without relying on outdated and vague news articles.

Thanks!

Are there any suggestions for a firewall with an easy GUI? I want to open a port for kde connect so i can use sms and fling my phone to the back of the room. Thanks in advance

I tested Debian 13 RC1 by installing the Nvidia proprietary driver using:

apt install nvidia-driver

The error from systemctl status dkms is as follows:

× dkms.service - Builds and install new kernel modules through DKMS
     Loaded: loaded (/usr/lib/systemd/system/dkms.service; enabled; preset: enabled)
     Active: failed (Result: exit-code) since Sun 2025-05-18 07:37:53 +07; 1min 22s ago
 Invocation: da858b6286f04dd6965e54bc964fc78f
       Docs: man:dkms(8)
    Process: 855 ExecStart=/usr/sbin/dkms autoinstall --verbose --kernelver 6.12.27-amd64 (code=exited, status=21)
   Main PID: 855 (code=exited, status=21)
   Mem peak: 6.3M
        CPU: 204ms

May 18 07:37:53 vlegion systemd[1]: Starting dkms.service - Builds and install new kernel modules through DKMS...
May 18 07:37:53 vlegion dkms[1069]: Error! Your kernel headers for kernel 6.12.27-amd64 cannot be found at /lib/modules/6.12.27-amd64/build or /lib/modules/6.12.27-amd64/source.
May 18 07:37:53 vlegion dkms[1069]: Please install the linux-headers-6.12.27-amd64 package or use the --kernelsourcedir option to tell DKMS where it's located.
May 18 07:37:53 vlegion systemd[1]: dkms.service: Main process exited, code=exited, status=21/n/a
May 18 07:37:53 vlegion systemd[1]: dkms.service: Failed with result 'exit-code'.
May 18 07:37:53 vlegion systemd[1]: Failed to start dkms.service - Builds and install new kernel modules through DKMS.

Of course, this problem was fixed by installing 'linux-headers-6.12.27-amd64.'

However, I wonder if 'linux-headers-6.12.27-amd64' should be installed automatically. Is this a bug? How can I check if anyone has reported this already?

I'd like to progressively rate limit ssh connections by 3 per minute, 12 an hour and 24 a day.

I have these rules that don't seem to be working:

tcp dport 22 ct state new limit rate over 24/day drop comment "24+ a day"
tcp dport 22 ct state new limit rate over 12/hour drop comment "12+ an hour"
tcp dport 22 ct state new limit rate over 3/minute drop comment "3+ a minute"
tcp dport 22 ct state new limit rate 3/minute accept comment "Good SSH"

I'm still stuck in debian 10.13, stock kernel 4.19.316-1 (2024-06-25) and nftables v0.9.0 (Fearless Fosdick).

sets are not yet available, as far as I know.

In older versions of Debian I used to be able to pass sec=ntlm,vers=1.0 as options to mount.cifs (and fstab) and it would allow me to mount my shared disk from my AirPort Extreme.

In Bookworm, due to the bundled kernel version, I am now told ntlm is a bad security option. If I try to use ntlmssp, I am told Unable to select appropriate authentication method!. If I use ntlmv2 or remove the sec option, I get Status code returned 0xc000006d NT_STATUS_LOGON_FAILURE.

Funny thing is, if I use smbclient, I can browse my shared drive just fine.

Using a newer version of Samba protocol is not an option since Apple gave up on their products just like Linux gave up on ntlm.

Aside of throwing everything out the window, what can I do to get this working on Bookworm?

Edit: I gave up. Because the maintainers of the kernel decided to remove ntlm support, the only option I had was to downgrade to buster, as it was the last distro to use a pre-6 kernel. Suffice it to say, I'm very disappointed; both in Apple for abandoning their Airport's to use SMBv1, and the kernel devs for further eroding Airport support by removing ntlm. Yes, I get ntlm "bad" (both from an FOSS and security standpoint), but it's still disappointing to be punished simply because I do not wish to litter the landfill with still useful hardware (nor do I wish to spend more money on something I shouldn't need). Anyway, /rant over.

Looking at Debian's release-critical bugs, you can see that Trixie is close:
Testing now has fewer critical bugs than Stable, and the number is dropping quickly.
About 200 bugs still need to be fixed to get the number down to where the previous releases were done.

Maybe you can help? Bugs blocking the next release can be as simple as missing translations for the upgrade instructions.

AI models released under open source license without original training data or program are not seen as DFSG-compliant.

The GR is in his discussion step, and may be other vote options are presented.

The discussion can be read in the Debian-vote mailing list, and the resolution could impact other software (scanners, text2speach...) ^[See https://lists.debian.org/debian-vote/2025/04/msg00114.html].

Besides having the latest version available, what do Debian users who run MariaDB wish to see in future versions of MariaDB, or how it is integrated and packaged in Debian?

I am the maintainer in Debian - looking for feedback and ideas.

I'm a retired Unix (AIX) admin and I run some Linux servers at home. But, I'm still using Windows as a desktop. This whole Windows recall thing is the final straw - I'm switching to Linux for desktop. I've done a bit of research and believe Debian is the best fit for me. So, I recently installed it on one of my small servers.

I like it but I find the "half baked" approach to systemd a bit confusing. My default minimal server install has both cron jobs and systemd timers configured for basic system maintenance tasks. For example logrotate is fired twice a day - once by /etc/cron.daily/logrotate and once by /lib/systemd/system/logrotate.service. I'm tempted confirm that everything cron does is actually also done by systemd and then apt purge cron\* && rm -rf /etc/cron*. But, I suspect that might break future package installs and updates?

I'm also not excited by ifup/ifdown - why not just use the capability already included with systemd? This is just a minor thing for me as there's no real duplication I guess.

Is the a Debian based "pure systemd" distro??