13 ms·

Debian 13 “Trixie”

• gorgoiler 1y ago
  Congratulations! Debian has been the stable footing of my Free computing life for three decades. Everything about their approach — from showing me Condorcet, organising stable chaos, moving forward by measured consensus, and basing everything on hard wrought principles — has had an effect on me in some way, from technical to social and back again. I love this project and the immeasurable impact it has had on the world through their releases and culture. With all my love, g’o xx
• markus_zhang 1y ago
  When can we have Bandit or Bluey?
  • Balinares 1y ago
    Presumably not before Debian runs out of Toy Story characters.
    • seba_dos1 1y ago
      ...and since there's Toy Story 5 scheduled for 2026, the pool of yet unused characters will become larger again soon.
• jm4 1y ago
  [flagged]
  • wiseowise 1y ago
    Your comment might be taken more seriously if you provide more context.
  • heikkilevanto 1y ago
    Citation needed. I honestly do not know what you are referring to. Even if I had to take your "sexual predator" at face value, I would still have to balance that against the good stable reliable distro they have been done for so many years.
    • josteink 1y ago
      I believe this is the guy he's talking about. By linking to this, I'm not saying the allegations are true, but it's the discussion I've seen mentioned elsewhere, which I believe OP is referring to: https://x.com/LundukeJournal/status/1944505084919816337 https://x.com/LundukeJournal/status/1944505084919816337 > Tomorrow, July 14th, at the annual Debian Conference (DebConf ‘25), Jeremy Bicha will be speaking. > Bicha, as we learned last week (after he defaced an open source wiki page, calling people “Nazis”), is a registered sex offender — convicted after having committed “thousands” of assaults of young children. > Bicha, an employee of Canonical (the parent company of Ubuntu) will be representing both Debian and GNOME at DebConf 25. Edit: Digging deeper into the X threads, this seems to be one of the root the sources of the claim: https://wng.org/articles/the-high-cost-of-negligence-1617309216 https://wng.org/articles/the-high-cost-of-negligence-1617309... Edit 2: Just to be clear, I myself am a Debian user. Not a hater. I'd just hate to see Debian's reputation needlessly tarnished by having the wrong people promoted to publicly represent the project.
      • abrouwers 1y ago
        I'm not commenting about the allegations themselves (which may be true), but be careful citing Lunduke - he's a pretty famous click-baity megatroll in the OSS world.
    • LtdJorge 1y ago
      Jeremy Bicha
    • stouset 1y ago
      I too had no idea what he’s talking about, so I did some digging. So, an open-source contributor who works for Canonical on Ubuntu gave a talk at Debconf. He is a convicted and admitted sexual predator who served time in prison for his crimes. This all is pretty well-documented. But… then what? He did the time for his crimes. He’s on the national sex offender registry. What now? Should he be unemployable? Should his contributions to open-source projects be rejected? Should he not be able to give a talk on some technical topic he’s presumably an expert on? Either we agree that serving your prison sentence is sufficient atonement for your crimes or we have to work to change the prison system such that it is. I don’t know that excluding someone from contributing to society for the rest of their life is the right answer. Please note that this is a very shallow summary for those who (like me) were unaware of the drama here. I have no idea of the extent of his crimes past what I wrote above, nor if the time he served “seems” appropriate (not that a single value there could ever be considered appropriate by everyone simultaneously). My assumptions are that he was convicted, served a reasonably appropriate amount of time, was released, and has committed no further crimes of that nature in the intervening period since (any or all of which I could be wrong about). I also have seen accusations of rude/antagonistic behavior outside of this specific topic, but am leaving those aside since they weren’t part of GP’s complaint.
• Paianni 1y ago
  The Devuan version may end up being the last that GNOME will run on...
  • UncleSlacky 1y ago
    You say that like it's a bad thing.
    • Paianni 1y ago
      I don't like GNOME's engineering or license, but as far as the UI and design are concerned I don't think anyone has topped it (minus the hot corner I guess).
      • kasabali 1y ago
        Meh, it looks pretty in screenshots but it's a huge waste of screen space in the end.
        • Paianni 1y ago
          I suppose 'power-users' can put up with 'small-button' GUIs but I do think a general purpose GUI needs to be easy to use for people who aren't used to controlling mice and keyboards all the time.
          • account42 1y ago
            Those users won't use Devuan or Gnome but Android/iOS.
            • Paianni 1y ago
              They may not personally choose Devuan or GNOME but they might end up using them because an administrator chose them.
          • kasabali 1y ago
• superkuh 1y ago
  Biggest change for me is /tmp behavior. In Debian 13 /tmp become RAM-disk by default (instead of files on the file system) and uses up to 50% of available ram. But as expected of Debian the release notes included an easy fix to restore normal /tmp behavior for people and applications that place many small or large files there. https://www.debian.org/releases/trixie/release-notes/issues.en.html#the-temporary-files-directory-tmp-is-now-stored-in-a-tmpfs https://www.debian.org/releases/trixie/release-notes/issues.... >"You can return to /tmp being a regular directory by running systemctl mask tmp.mount as root and rebooting." I kind of wish the distros had decided on a new /tmpfs (or /tmp/tmpfs, etc) directory for applications to opt-in to using ram-disk rather than replacing /tmp and having to opt-out.
  • b112 1y ago
    Also watch out for surprise file deletes in /tmp and /var/tmp at 10 and 30 days. This too can be turned off.
    • KORraN 1y ago
      Isn't this the feature of /tmp? I set my default download location in Firefox to /tmp exactly for this reason, so that all the junk gets automatically removed after some time. Also, whenever I need a temporary Python script or test a package, I create a venv under /tmp.
      • superkuh 1y ago
        On boot has been the standard for a long time and is still the most common. I am personally surprised to hear that now Debian and some distros do it via various automated ways at time intervals.
        • saint_yossarian 1y ago
          It's a systemd thing, see `man systemd-tmpfiles`.
• 3eb7988a1663 1y ago
  Maybe title should note that it has now been released? There has been many updates about Trixie in the past few months in preparation for today.
  • cocoto 1y ago
    I think the title has been trimmed from the word “realeased”. Might be another case of HN auto title edit botching the original title.
• hiprob 1y ago
  I can't believe we've come to such a high number, and a particularly lucky one at that Alas it's still not suitable as a daily driver for the average home user and probably never will be. It is unfortunate that Ubuntu has to reign supreme in that regard.
  • cocoto 1y ago
    The installation is slightly easier (but still hard because of USB install) and the website has a more appealing design. Except from that what is better in Ubuntu for the average casual user? Proprietary blobs are now included in the default installer since version 12.
  • amtamt 1y ago
    Two kids in 4 to 16 range, and two adults in 30 to 46 age ranges have been using Debian on daily basis for almost a decade now. At least three of them are pretty "average home user". There has been forced use of windows (since school and employers wanted), but for home use Debian has always been better due to less maintenance needs and no distractions.
  • accrual 1y ago
    > Alas it's still not suitable as a daily driver for the average home user I think that's fine for Debian. Maybe even a good thing. Debian supplies a rock solid base for many general purpose tasks. Ubuntu and other distros are free to package that up in a user friendly way, but as a technical user I want to be able to go upstream and get a basic Linux system without extra stuff.
  • josteink 1y ago
    Don't feed the troll, etc... But I just had to bite on this bit: > Alas it's still not suitable as a daily driver for the average home user and probably never will be. It is unfortunate that Ubuntu has to reign supreme in that regard. It's true that Ubuntu used to be the OOB ready version of Debian, which "just worked", while base Debian took look of fiddling to even have wifi working. These day though I find the opposite to be true: Ubuntu does lots of weird things I don't want, and I have to "fiddle" to disable all that. A base Debian install however (ISO with firmware bundled), just works. For me, Ubuntu is officially off my list of distros I bother spending my time on.
• josteink 1y ago
  I've upgraded all my servers and laptops to Debian 13. Lucky 13 and all... And not a single issue so far. Very happy! Thanks to the Debian team for putting out yet another high quality, reliable release :)
• b112 1y ago
  You can still use sysvinit, I've already tested servers and desktop builds. From my build box: chroot $MOUNTPOINT/ /bin/bash -c "http_proxy=$aptproxy apt-get -y --purge --allow remove-essential install sysvinit-core sysvinit-utils systemd-sysv- systemd-" There is a weird depends you cannot get around without simultaneously removing and installing in parallel. A Debian bug highlighted the above, with a "-" for systemd-sysv- systemd- as a fix, along with allow remove essential. After this fix, sysvinit builds with debootstrap were almost identical as to bookworm. This includes for desktops. As per with bookworm through buster, you'll still need something like this too: $ cat /etc/apt/preferences.d/systemd # this is the only systemd package that is required, so we up its priority first... Package: libsystemd0 Pin: release trixie Pin-Priority: 700 # exclude the rest Package: systemd Pin: release * Pin-Priority: -1 Package: *systemd* Pin: release * Pin-Priority: -1 Package: systemd:i386 Pin: release * Pin-Priority: -1 Package: systemd:amd64 Pin: release * Pin-Priority: -1
  • egorfine 1y ago
    Wait, sysvinit on debian 13 truly practically works?? as in, one can remove systemd and have a working server OS with sysv init??
    • b112 1y ago
      Yes. I run a full desktop too, without it. Multiple variants. I don't use gnome's Desktop Environment though (although I do run gtk/gnome software), so cannot comment on that.
    • UncleSlacky 1y ago
      Yes, MX Linux will be doing this (as a separate ISO, until now they're been able to provide a single ISO that lets you choose between systemd and sysvinit at every boot): https://mxlinux.org/blog/changes-coming-with-mx-25/ https://mxlinux.org/blog/changes-coming-with-mx-25/
  • foresto 1y ago
    Thank you for sharing this. I'm inclined to adopt it in my lxc containers, at least.
• accrual 1y ago
  > i386 is no longer supported as a regular architecture: there is no official kernel and no Debian installer for i386 systems. The i386 architecture is now only intended to be used on a 64-bit (amd64) CPU. Users running i386 systems should not upgrade to trixie. Instead, Debian recommends either reinstalling them as amd64, where possible, or retiring the hardware. Impressive that i386 support made it all the way to August 2025. I have Debian 10 Buster running on a Pentium 3 which only EOL'd last year in June 2024. It's still useful on that hardware and I'm grateful support continued as long as it did! OpenBSD still supports i386 for those looking for a modern OS on old 32-bit hardware.
  • zozbot234 1y ago
    Hopefully i386 (or perhaps a new i386-like port with added support for 64-bit time values) can move to the unofficial Debian Ports infrastructure for Debian 14 (forky) or Debian 15 (duke). Debian Ports has a m68k port, so supporting one for i386 shouldn't be a huge problem.
    • 3eb7988a1663 1y ago
      To what end? Outside of sheer nostalgia if you are running ancient hardware, you probably have a bespoke application which requires that environment. Either you cannot change for hard technical, compliance, or just fear of the unknown. Firewall it from the internet and continue to run whatever release last worked. I am not happy about unnecessary ewaste, but an i386 almost certainly has and order of magnitude less horsepower than a raspberry pi or N100.
      • michaelt 1y ago
        My Linux machine is very modern, but I still need i386 architecture support installed, because Steam requires 32-bit support. And Steam requires 32-bit support so people can play 15-year-old games. (Admittedly, the 32-bit support Ubuntu ships is less than a full OS and you can't install Ubuntu on a 32-bit machine these days)
        • 1y ago
• potato-peeler 1y ago
  > The overall disk usage for trixie is 403,854,660 kB (403 GB) What does this mean? If all 69k+ packages are installed, it will take up this much space?
  • toenail 1y ago
    As this also lists lines of code, it sounds more like sources plus packages. Think space that a full mirror (src + generic + arch specific packages) would need.
    • tremon 1y ago
      Indeed, this is the amount of space that a Debian mirror would need to host all Trixie packages. So it's the compressed packages total size, not the space it would take to have all packages installed simultaneously (which also happens to be impossible, because of package conflicts/alternatives and Debian supporting 7+ different architectures).
  • ethan_smith 1y ago
    The 403GB figure represents the total size of all source packages in the Debian archive, not the disk space required for a typical installation which is usually under 10GB for a desktop system.
• ACS_Solver 1y ago
  Writing this from my Debian system, it's a great distro that has been excellent to me as a daily driver. I switched to Debian 6 after Ubuntu went way downhill and haven't had cause to regret it. I like Debian's measured pragmatism with ideology, how it's a distro of free software by default but it also makes it easy to install non-free software or firmware blobs. I like Debian's package guidelines, I like dpkg, I like the Debian documentation even if Arch remains the best on that front. I like the stable/testing package streams, which make it easy to choose old but rock-stable vs just a bit old and almost as stable. And one of the best parts is, I've never had a Debian system break without it being my fault in some way. Every case I've had of Debian being outright unbootable or having other serious problems, it's been due to me trying to add things from third-party repositories, or messing up the configuration or something else, but not a fault of the Debian system itself.
  • zvmaz 1y ago
    > after Ubuntu went way downhill and haven't had cause to regret it. In what way Ubuntu went downhill?
    • happymellon 1y ago
      Snaps? Proprietary package managers are never great.
      • mmcnl 1y ago
        I don't really understand why this is such a big problem. You don't have to use snaps.
        • wkat4242 1y ago
          Yes you do. Some packages aren't available anymore in apt
        • yjftsjthsd-h 1y ago
          You really have to work to avoid them; ex. `apt install firefox` will install the snap
• SilverElfin 1y ago
  [flagged]
  • felixgallo 1y ago
    that's not 'content about the increasing politicization of Linux', that's just whiny reverse-victim maga youtuber ragebait. Sail on right past it.
    • SilverElfin 1y ago
      I did find some actual tutorials in the end but … I’ll be honest it seems intimidating. I thought it would be more geared towards the everyday person in 2025.
  • baobun 1y ago
    The "controversy" in this case seems manufactured and flames mostly fuelled by talking heads like this one and their herds. Psyops with a dash of opportunism. The man is a professional agitator.
• master_crab 1y ago
  Debian 13 trixie includes numerous updated software packages (over 63% of all packages from the previous release) I’m not familiar with the metric definition they use, but I’d be worried if close to 100% of the packages they included in bookworm hadn’t been updated in the roughly 2 years between releases. I use Debian for most of my servers, so I’m sure there is a valid explanation of that phrase.
  • baobun 1y ago
    > I’d be worried if close to 100% of the packages they included in bookworm hadn’t been updated in the roughly 2 years between releases. Code doesn't "go bad" and not everything is affected by ecosystem churn and CVEs. An established package not having updates for 2y is not in and of itself problematic.
  • b112 1y ago
    I don't know why you think it would be different. Are you concerned about security updates? That's not part of the metric, as far as I can see. And even if it was? If you look at the number of packages in Debian, only a small portion have CVEs. There are nearly 30k package sources, and an output of 60k binary packages. Yet we only get a few security updates weekly. Another example? Both trixie and bookworm use the same firefox ESR (extended release) version. Both will get updated when firefox forces everyone to the next ESR. Beyond that, some packages are docs. Some are 'glue' packages, eg scripts to manage Debian. These may not change between releases. Lastly, Debian actually maintains an enormous number of upstream orphaned packages. In those cases, the version number is the same (sometimes), but with security updates slapped on if required. From my perspective, outside of timely and quick security updates, I have zero desire for a lot of churn. Why would I? Churn means work. Churn means changed stability. We get plenty of fun and churn from kernel, and driver related changes (X, Wayland, audio/nic, etc), and desktop apps. And of course from anything running forward, with scissors, like network connected joy.
  • duskwuff 1y ago
    It's not uncommon for small software packages to go years between updates - either because they're a simple utility that's feature-complete and rarely needs bug fixes, or because they're data files (e.g. packages of icons or fonts) which might not need to change at all.
• binwiederhier 1y ago
  Thank you to all the Debian volunteers that make Debian and all its derivatives possible. It's remarkable how many people and businesses have been enabled by your work. Thank you! On a personal note, Trixie is very exciting for me because my side project, ntfy [1], was packaged [2] and is now included in Trixie. I only learned about the fact that it was included very late in cycle when the package maintainer asked for license clarifications. As a result the Debian-ized version of ntfy doesn't contain a web app (which is a reaaal bummer), and has a few things "patched out" (which is fine). I approached the maintainer and just recently added build tags [3] to make it easier to remove Stripe, Firebase and WebPush, so that the next Debian-ized version will not have to contain (so many) awkward patches. As an "upstream maintainer", I must say it isn't obvious at all why the web app wasn't included. It was clearly removed on purpose [4], but I don't really know what to do to get it into the next Debian release. Doing an "apt install ntfy" is going to be quite disappointing for most if the web app doesn't work. Any help or guidance is very welcome! [1] https://github.com/binwiederhier/ntfy https://github.com/binwiederhier/ntfy [2] https://tracker.debian.org/pkg/ntfy https://tracker.debian.org/pkg/ntfy [3] https://github.com/binwiederhier/ntfy/pull/1420 https://github.com/binwiederhier/ntfy/pull/1420 [4] https://salsa.debian.org/ahmadkhalifa/ntfy/-/blob/debian/latest/debian/rules?ref_type=heads https://salsa.debian.org/ahmadkhalifa/ntfy/-/blob/debian/lat...
  • heywire 1y ago
    Just wanted to say thanks for ntfy! I use it daily to notify me on events from my home Meshtastic node.
  • tremon 1y ago
    The maintainer has a short explanation here: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1098866#10 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1098866#10 > The webapp is a nodejs app that requires packages that are not currently in debian. Since vendoring dependencies inside packages is frowned upon in Debian, the maintainer would have needed to add those packages themselves and maintain them. My guess is that they didn't want to take on that effort.
    • 1y ago
• Venn1 1y ago
  I have been tracking Trixie on my Resolve workstation for the past couple of months. The only hiccup was that the latest kernel did not support the ondemand governor, so I had to build a custom kernel to fix that.
• sheerun 1y ago
  Debian was often the only linux os that worked on old "spacestations" of mine. Great sentiment
  • sheerun 1y ago
    And I mean Debian 12, not some old version, much more impressive
    • spauldo 1y ago
      Do you mean SparcStations?
• gcarvalho 1y ago
  Looking forward to upgrade over the weekend. Have had my RPi on Debian since Debian 9, with smooth upgrades every time.
• imoverclocked 1y ago
  I have used Debian starting sometime around slink. I still type "apt-get ..." and it still works reasonably well. There have definitely been hiccups in upgrades over the last 25+ years but the amount of time/effort dealing with those is almost nothing in comparison to other linux and non-OSS systems I've dealt with over the same span of time. My only regret is not contributing more to the community. The thing I like most about Debian is that you need to know at least a little about what is going on to use it. For me, it does a good job of following "as simple as possible and no simpler."
  • Nursie 1y ago
    Which one was slink? My first Debian install was in 1996. I had no real idea what I was doing, but it was amazing to me that I could remote-display windows from machines across campus, and it was alien compared to the windows 3.x/95 I was used to at that point. There was no apt at that point, or none that I was aware of, and adding new stuff was painful. I started using debian preferentially as my workstation/desktop OS in about 2005, and was installing it on embedded systems (linksys nslu2) to make micro servers by … etch I think it was. By 2008 I was at IBM and they allowed a choice of windows or redhat on your laptop, and if you were adventurous there was experimental support for Ubuntu which might work on Debian. I made it work and discovered that among 330k people there were 22 of us running it! Always loved it, it always just made more sense than other distros somehow. My daily driver is a Mac now, but I still have a few Debian machines around.
• juujian 1y ago
  I have been using Debian Trixie for a few months in testing now, I can attest that its a great, stable operating system. Definitely better than Ubuntu in terms of user experience.
  • lucb1e 1y ago
    The only complaint on a fresh install is that Cinnamon seems to use a ton of CPU when there's a little moving thingy anywhere on the screen (a browser tab that has a loading icon in the tab list is sufficient). This is most noticeable when you have a VM without graphics acceleration (don't ask why in the world my job requires that). Graphics without acceleration is always heavy, but this is an extra process doing whatever on top of the actual load Then my private laptop has had a bunch of graphic issues after upgrading to 13 (it manifests differently in a lot of applications and it changes when you pick a different desktop theme, not even sure how to describe it). The new pipewire (pulseaudio replacement, idk why that needed replacing) does not work properly when the CPU is busy (so I currently play games without game sounds or music in the background). The latter then also sometimes (1 in 5 times maybe?) crashes when resuming from suspend, but instead of dying, spams systemd which diligently stores it all in a shitty binary file (that you can't selectively prune), runs completely out of disk space, and breaks various things on the rest of the system until you restart the pipewire process and purge any and all logs (remember, no selective pruning)... Tried various things I found in web searches and threw an LLM at it as well, but no dice. I assume these issues are from it not being a fresh install, so no blame/complaint here really, just annoying and I haven't had these issues when doing previous upgrades. Not yet sure how to resolve, perhaps I'll end up doing a completely new install and seeing what configs I can port until issues start showing up Surely these things are not a Debian-specific issue, but I haven't noticed something like that with either 11 or 12 Edit: oh yeah, and the /tmp(fs) counter is at 1 so far. I wonder how many times I'll have run out of RAM by Debian 14, by forgetting I can't just dump temporary files into /tmp anymore without estimating the size correctly beforehand
    • esperent 1y ago
      I've been testing Cinnamon on my Ubuntu machine recently. I was close to deciding to switch from Gnome but I keep running into an issue whenever I have long running tasks in Blender. In Gnome, Blender becomes unresponsive but everything else is still usuable. In Cinnamon, the entire system becomes unresponsive.
• b112 1y ago
  For those worrying about the NIC change with systemd, this comes from the release doc: https://www.debian.org/releases/trixie/release-notes/issues.en.html#network-interface-names-may-change https://www.debian.org/releases/trixie/release-notes/issues.... # example: udevadm test-builtin net_setup_link /sys/class/net/eno4 2>/dev/null ID_NET_LINK_FILE=/usr/lib/systemd/network/99-default.link ID_NET_LINK_FILE_DROPINS= ID_NET_NAME=eno4 <-- note the NIC name that will happen after reboot Here's a one-liner, excluding a bond interface and lo. Gives a nice list of pre and post change. for x in $(cat /etc/network/interfaces | grep auto | cut -d ' ' -f 2 | grep -Ev 'lo|bond0'); do echo -n $x:; udevadm test-builtin net_setup_link /sys/class/net/$x 2>/dev/null | grep NET_NAME| cut -d = -f 2; done The doc's logic is that after you've upgraded to trixie, and before reboot, you're running enough of systemd to see what it will name interfaces after reboot. So far I have not had an interface change due to upgrade, so I cannot say that the above does detect it.
  • foresto 1y ago
    Do you happen to know if this change can affect people who have disabled systemd's Predictable* Network Interface Names before upgrading to Trixie? *haha
    • champtar 1y ago
      You can easily keep the current naming behavior with the 'net.naming_scheme=' kargs
      • foresto 1y ago
        I already have systems that use net.ifnames=0. My question is about whether this new behavior can affect them.
        • champtar 1y ago
          It'll not, the new behavior is just a new naming scheme, and you just choose not to use any, which is totally fine if you have a single NIC.
• bayindirh 1y ago
  Debian's signature feature (upgrade from stable to stable under 15 minutes) shines here too. My first system migrated in less than 10 minutes, incl. package downloads and reboot. It's not a beast either. N100 mini PC connected to a ~50mbps network.
  • mr_sturd 1y ago
    What was the process for this? Does it involve manually modifying the sources.lists files, or is there a single command to instigate the upgrade?
    • bayindirh 1y ago
      There are two main ways: If your sources file references the release name (e.g.:bookworm), you change them to trixie, then “apt update && apt dist-upgrade”. or, If your sources file directly reference distro-suites (e.g.: stable), you just “apt update && apt dist-upgrade” since stable is now pointing to trixie. In the first reboot, you run “apt autopurge” to remove packages which are not needed anymore. …and you’re done.
  • account42 1y ago
    Is this really a signature feature when rolling release distros are common?
    • bayindirh 1y ago
      Yes, esp. if you are using Debian at infra and in production. I upgraded three servers in the morning while sipping my tea. Nobody noticed anything. For RedHat family, this is nigh impossible, requiring hours of planning, downtimes, etc., and even then, it's not guaranteed to work. If you prefer a rolling release, and won't use it on a server, Debian Testing got you covered (unless you are in a security sensitive environment). My systems are well-isolated from outside, so desktop systems can run Testing without issues. Servers and exposed systems always run stable with security updates installed automatically, though.
• Pet_Ant 1y ago
  It can be a little hard to navigate to so the .torrent links for x86-64 are Minimal: https://cdimage.debian.org/debian-cd/current/amd64/bt-cd/debian-13.0.0-amd64-netinst.iso.torrent https://cdimage.debian.org/debian-cd/current/amd64/bt-cd/deb... Full: https://cdimage.debian.org/debian-cd/current/amd64/bt-dvd/debian-13.0.0-amd64-DVD-1.iso.torrent https://cdimage.debian.org/debian-cd/current/amd64/bt-dvd/de...
  • duskwuff 1y ago
    Note that you probably don't need the DVD ("full") image. Most users should use the "minimal" netinstall CD and download packages at install time.
    • synack 1y ago
      Agreed, but for laptops it’s nice to keep a copy of the DVD iso on disk and in your apt sources so that you can install stuff offline.
    • Pet_Ant 1y ago
      I downloaded both because I intend to seed, but yes, if you have a fast internet connection then minimal is perfect... but if you are on a crappy third-world connection where it might take all day to get the image, it's nice to have it all in place when you are ready to install.
  • wltr 1y ago
    It baffles me I keep searching for these files every time I want to download Debian. And it’s been like that for over a decade at least.
    • pabs3 1y ago
      They are linked from the "Other downloads" page linked from the front page.
      • wltr 1y ago
• yonatan8070 1y ago
  A total of seven architectures are officially supported for "trixie": "trixie" 64-bit PC (amd64), 64-bit ARM (arm64), ARM EABI (armel), ARMv7 (EABI hard-float ABI, armhf), 64-bit little-endian PowerPC (ppc64el), 64-bit little-endian RISC-V (riscv64), IBM System z (s390x) It's good to see RISC-V becoming a first-class citizen, despite the general lack of hardware using it at the moment. I do wonder, where are PowerPC and IBM System z being used these days? Are there modern Linux systems being deployed with something other than amd64, arm64, and (soon?) riscv64?
  • kev009 1y ago
    Both Power and z are many billion dollar businesses each. Banking and other high finance is the stronghold for both. IBM still seems proud of z, Power seems merely tolerated these days which is a shame because it is a nice ISA and the systems are very nice too.
  • Palomides 1y ago
    IBM puts a lot of work and money into making sure open source stuff runs properly on those two, even if they aren't that popular them being kept by major distros is therefore not as "natural" as other architectures
    • pabs3 1y ago
      For Debian s390x (IBM Z), they only employ two people to work on the port, which isn't really enough. I think ppc64el has even less people.
  • ndiddy 1y ago
    Mainframes are still holding on in use cases where a single server having continuous uptime is vital. They're designed to have uptime measured in decades, so even components like the processors and main memory have hot spares available and can be hot-swapped without interrupting the OS or running services. They also have continually running system monitoring and diagnostics at the hardware level (not running as an OS service) that will alert both the owner and IBM if they detect some sort of hardware fault. IBM has supported Linux as a first-class OS option for their mainframes since the early 2000s. From a developer perspective, s390x is also the last active big-endian architecture (I guess there's SPARC as well, but that's on life support and Oracle doesn't care about anyone running anything but Solaris on it), so it's useful for picking up endianness bugs. Another interesting thing is that the only two 32-bit architectures left supported are armel and armhf. Debian has already announced that this will be the last release that supports armel (https://www.debian.org/releases/trixie/release-notes/issues.html#last-release-for-armel https://www.debian.org/releases/trixie/release-notes/issues....), so I guess it'll be a matter of time before they drop 32-bit support altogether.
• Narishma 1y ago
  > Users running i386 systems should not upgrade to trixie. Instead, Debian recommends either reinstalling them as amd64, where possible, or retiring the hardware. What I did is switch to NetBSD.
  • yjftsjthsd-h 1y ago
    In the abstract I'm a big fan of supporting me old machines forever, but I have to ask out of curiosity - what hardware is practical to run these days and only has a 32-bit processor?
    • jabl 1y ago
      I tried to repurpose an old laptop I had lying around as a "lie on the couch and surf the web or watch youtube" machine. It was one of the last 32-bit only cpus (pentium m), so I installed Debian bookworm (12) on it. Unfortunately it turned out it couldn't even play youtube videos at 144p without stuttering. So I E-wasted the machine. I suppose as some kind of headless home server it could still have been useful. OTOH for something that runs 24/7 a RPi would use a fraction of the electricity and still be a lot more powerful. So yes, beyond nostalgia and some embedded/industrial usecases, it's hard to see a use for a 32-bit only PC these days.
    • Linux-Fan 1y ago
      I have a few old PCs (towers) here which don't support amd64 mostly Pentium 4-based. They all still have DVD reader drives and are nice for ripping CDs. Despite the fact that the drives are nearing 20 years of age (machines are from ~2005) they still perform better than most “new” external drives. Of course one could also move the drives to a newer machine but many of them use the IDE connector which is not commonly found on modern systems. Also, modern cases typically don't account for (multiple) 5.25" drives. The other use case is to flash microcontrollers. When fiddeling around with electronics there is always a risk of a short circuit or other error that could in worst case kill the attached PC's mainboard. I feel much safer attaching my self-built electronics to an old machine than to my amd64 workstation. Due to their age, I think the old machines may not live much longer -- I fear not even 10 more years, some of my old 32-bit laptops have already failed. Hence even for me it does not make sense to try keeping up the software support. Maybe I switch them to a BSD or other Linux distribution if they live long enough but for now the machines run OK with Debian Bookworm (newly oldstable), too.
• krylon 1y ago
  As an owner of two i386 systems (both netbooks built around Intel's Atom N270), that run Debian, I am a little sad. I understand the reasoning, and I won't deny it is a very niche platform by now. But I had hoped Debian, with a history of supporting a wide range of platforms, would keep i386 going for a while longer. Fortunately, bookworm will continue to receive updates for almost 3 years, so I am not in a hurry to look for a new OS for these relics. OpenBSD looks like the natural successor, but I am not sure if the wifi chips are supported. (And who knows how long these netbooks will continue to work, they were built in 2008 and 2009, so they've had a long life already.) EDIT: Hooray, thanks to everyone who made this possible, is what I meant to say.
  • dschuessler 1y ago
    Out of curiosity, what do you use these netbooks for?
    • krylon 1y ago
      One sits in my bathroom so I can browse random Wikipedia articles while I'm, uh, busy. The other one sits on my nightstand and plays audiobooks/podcasts when I'm going to sleep. So nothing critical. But something they are still good at, and being very small makes them a natural fit for these use cases.
      • thiht 1y ago
        Curious, why not use your phone for both these use cases? Seems like it would be even more convenient
        • CogitoCogito 1y ago
          I can't speak for the other poster, but I like the idea a lot. Having tools with specific purposes means I can avoid using my phone for everything. No matter what games I play to remove notifications/interruptions/etc. it's always a distraction and easy to be distracted from whatever I originally intended to use the phone for.
• kachapopopow 1y ago
  Plasma 6.3 - I can finally ditch kde neon.
  • ACS_Solver 1y ago
    Not if you want to remain on new Plasma, you can expect Debian to lag several minor versions behind. I've found it pretty easy though to use some KDE components built from source on top of the standard Debian packages. Build with kdesrc-build, then have those binaries linked to from your ~/bin and you're set. It might get difficult if you want to rebuild some key components like plasmashell itself but I've been using locally built versions of Kate and Konsole without issue.
    • foresto 1y ago
      > you can expect Debian to lag several minor versions behind. Not necessarily forever, though. Bookworm got minor Plasma updates, so I wouldn't be surprised if Trixie does as well.
      • jpetso 1y ago
        Bookworm stayed on Plasma 5.27.5 when Plasma shipped bugfix releases up to 5.27.12. Debian may have cherry-picked a handful of patches from there, but that's a lot of bugfixes missed on a release that was already super old. Even at this point, Plasma 6.4 has been out for almost two months and 6.3 will not get any more updates ever. While everyone else is upgrading, Debian is going to be stuck on an already unsupported version for another two years or however much. Debian is great for what it is, but you better hope you don't run into issues with your desktop environment because they will not be addressed.
        • spauldo 1y ago
          There are options if you're willing to put in the work and run the risk of breaking things. You can always not install QT or KDE packages and compile your desktop from source. It's a major pain in the ass but I did it for years. A side benefit is you can participate in testing and interact with KDE developers directly. Another option is to go all FrankenUNIX and add neon sources to your apt cache. I've done similar but I don't recommend it. Or you can just run unstable. Lots of people do. I did for a long time, and as long as you're willing to fix the package system occasionally it's not a bad experience. Certainly better than the two previous options.
• charcircuit 1y ago
  So what is the actual difference. These release notes are not very clear. They just give version bumps. How can people get excited when you give them nothing to get excited about?
• aborsy 1y ago
  The difference between Debian and Ubuntu is decreasing with each release recently. I was pleasantly surprised that Debian recognized all hardware components in my laptop released one year ago out of the box. Hardware support is good and UI is great! It feels snappier than Ubuntu, may be due to lack of snap and fewer services and applications installed by default.
• sohrob 1y ago
  I love Debian and have a tremendous amount of respect for the people who work on the project. I no longer use Debian, but I think it's vitally important to have an anchor Linux distribution which isn't overly reliant on a for-profit entity and is truly community driven.
  • Santosh83 1y ago
    Arch isn't truly community driven?
• perdomon 1y ago
  How soon can I update my raspberry pi 5 from Bookworm to Trixie? Does PiOS have to initiate that first?
  • treve 1y ago
    Raspberry Pi OS is a derivative and not straight up debian. It's not a released yet. A beta exists and looks like this one will support an in-place update
  • kwk1 1y ago
    The images are a bit out of date, but check out https://raspi.debian.net/ https://raspi.debian.net/
• pss314 1y ago
  A new APT sources format "debian.sources" is announced with trixie. The now older "sources.list" format is still supported, but is likely to be deprecated in a future Debian release. See below: APT is moving to a different format for configuring where it downloads packages from. The files /etc/apt/sources.list and *.list files in /etc/apt/sources.list.d/ are replaced by files still in that directory but with names ending in .sources, using the new, more readable (deb822 style) format. For details see sources.list(5). Examples of APT configurations in these notes will be given in the new deb822 format. If your system is using multiple sources files then you will need to ensure they stay consistent. - https://wiki.debian.org/SourcesList#APT_sources_format https://wiki.debian.org/SourcesList#APT_sources_format - https://www.debian.org/releases/trixie/release-notes/upgrading.en.html#start-from-pure-debian https://www.debian.org/releases/trixie/release-notes/upgradi... "apt modernize-sources" command can be used to simulate and replace ".list" files with the new ".sources" format. Modernizing will replace .list files with the new .sources format, add Signed-By values where they can be determined automatically, and save the old files into .list.bak files. This command supports the 'signed-by' and 'trusted' options. If you have specified other options inside [] brackets, please transfer them manually to the output files; see sources.list(5) for a mapping.
  • __david__ 1y ago
    > apt modernize-sources Oh nifty, I hand converted all mine a couple years back. It would have been nice to have that then (or know about it?). I do really like the new deb822 format, having the gpg key inline is nice. I do hope that once this is out there the folks with custom public apt repos will start giving out .sources files directly. Should be more straightforward than all the apt-key junk one used to have to do (especially when a key rotated).
    • sgarland 1y ago
      Same. It took me a little bit to get used to it; my initial snap judgment was “this will be more annoying to create via scripting,” but then Ansible added deb822_repository [0] in 2.15 (shortly before Bookworm was released), and then it was no longer a concern. [0]: https://docs.ansible.com/ansible/latest/collections/ansible/builtin/deb822_repository_module.html https://docs.ansible.com/ansible/latest/collections/ansible/...
• lucb1e 1y ago
  > "trixie" includes numerous updated software packages (over 63% of all packages from the previous release) Wow, I'm amazed a third of packages haven't seen an update in, ehm checks > After 2 years, 1 month, and 30 days of development, the Debian project is proud to present its new stable version I'm a fan of old software myself, in the sense that I find it cool to see F-Droid having a (usually tiny) package that is over 10 years old but it does exactly what I want with no bugs and it works perfectly on Android 10. I wonder if those 30% more commonly fall in the "it's fine as it is" category or in the "no maintainers available" category
• luismedel 1y ago
  Kudos to the team. My first contact with Linux was with Debian 2.1. Exactly with this distro CDs https://archive.org/details/linux-actual-06-2/LinuxActual_014.jpg https://archive.org/details/linux-actual-06-2/LinuxActual_01... To be honest, it was a miserable experience to install it on your main computer without anything else available to look for help in case of problems. It was also hard to really try it due to lack of drivers for current (at that moment) ADSL modems. But here I am a crapload of years later, still loving it :-)
• dismalaf 1y ago
  I've kind of been using Debian 13 for awhile now (I'm on Unstable) and for me what's impressive is how polished a default Debian installation is these days. With Gnome, you literally can run it as is, no config needed. It just works. That being said, I like Flatpak, so I installed it (was super easy and Flathub provides instructions), and I added a few Gnome Shell extensions (a Dock so my wife can find apps when she occasionally uses my laptop). Debian gives you a feeling of ownership of your computer in a way the corporate distros don't, but is still pretty user friendly (unlike Arch). I'd definitely install Debian Stable on a grandparents' computer.
• natebc 1y ago
  Lots of debian love in this thread and it's great to see. If you're so inclined I encourage you to donate to Debian. We're all better off the more support goes to an ecosystem and operation like Debian. https://www.debian.org/donations https://www.debian.org/donations Not affiliated, just a happy user for a long, long time.
  • pabs3 1y ago
    Lots of other ways for individuals, companies and other organisations to help too: https://www.debian.org/intro/help https://www.debian.org/intro/help
• fhdnfjf 1y ago
  I'm too impatient to use a non-rolling release distro like Debian as my main OS, that, by my standards, already starts a new distro version with some outdated packages. I admire Debian though and it is my favorite server OS.
  • JonChesterfield 1y ago
    Testing is a rolling release. Unstable is a more exciting rolling release.
• theandrewbailey 1y ago
  > The overall disk usage for trixie is 403,854,660 kB (403 GB) That's too big. I'm going to need a smaller distro.
  • JonChesterfield 1y ago
    You're unlikely to install everything in it.
  • hsbauauvhabzb 1y ago
    I’m sure it’s small compared to some alternatives.
  • Biganon 1y ago
    You're probably being sarcastic, but in the eventuality you aren't, this is if you install every single package.
    • LtdJorge 1y ago
      No, it’s actually the disk usage of hosting a full mirror, other users commented on that
• keernan 1y ago
  Apparently Trixie needs a larger boot petition than prior versions and therefore I have to do new installs on three of my homelab machines - and probably my proxmox machine too. What a headache.
  • o11c 1y ago
    That sounds concerning, especially since Debian had hard-coded (!) a tiny /boot partition for encrypted disks for a long time. This already caused problems quite frequently (you have to manually delete them quite frequently, and which inhibits your ability to revert after a kernel regression - which, hm, I have noted to have been relatively common for Debian 12 "Bookworm" compared to usual ... hopefully Trixie is better, but if it makes the kernel-management problem harder that's a bad sign)
• shmerl 1y ago
  Congrats to the Debian team!
• nodesocket 1y ago
  I just upgraded a mini pc with no real issues. Main steps were: 1.) sudo apt-get update && sudo apt-get --yes upgrade && sudo apt-get --yes autoremove --purge 2.) Update all entries of bookworm to trixie in /etc/apt/sources.list. 3.) sudo apt full-upgrade 4.) sudo reboot 5.) sudo apt modernize-sources
• int_19h 1y ago
  I see that systemd is still doing this thing where they are trying to strong-arm all Linux distros into arbitrary stuff that someone decided is the only right way to do something: > 5.2.2. systemd message: System is tainted: unmerged-bin systemd upstream, since version 256, considers systems having separate /usr/bin and /usr/sbin directories noteworthy. At startup systemd emits a message to record this fact: System is tainted: unmerged-bin. It is recommended to ignore this message. Merging these directories manually is unsupported and will break future upgrades. Further details can be found in bug #1085370. No option to disable this either, per discussion in https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1085370 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1085370
  • jcgl 1y ago
    You may not like it, but “arbitrary” isn’t a fair description; there’s reasoning behind it that is over 10 years old: http://0pointer.net/blog/projects/stateless.html http://0pointer.net/blog/projects/stateless.html https://www.freedesktop.org/wiki/Software/systemd/TheCaseForTheUsrMerge/ https://www.freedesktop.org/wiki/Software/systemd/TheCaseFor... That said, my knee-jerk is also that this is about strong-arming distros. Which leaves a bad taste in my mouth. I’d be interested to hear other viewpoints though.
    • int_19h 1y ago
      Note that this is about a different thing - Debian has also merged its /bin into /usr/bin, but now systemd also wants /usr/bin and /usr/sbin to be merged.
      • jcgl 1y ago
        Oh thanks, I totally missed that distinctions. You’re right. My first thought is to wonder: why would systemd care about this then? Any idea? My second thought is: with a merged /usr, where /usr/{bin,sbin} are on the same filesystem, what’s the benefit of even having a distinct sbin? My understanding is that sbin has historically been useful to have statically linked binaries that can be made available early during boot without needing various lib dirs mounted. But that need seems obviated by a unified /usr…
• vwwvwvwv 1y ago
  [flagged]
  • deleted 1y ago
    [deleted]
• ilvez 1y ago
  Nice, more chaos to unstable again. Sincerely happy because of the release and new stable, but also selfishly happy because now unstable starts moving again.
• marsven_422 1y ago
  [dead]
• starkparker 1y ago
  Maybe a niche concern, but SDL2 is still in Trixie. The sdl2-compat layer (translating SDL2 APIs to SDL3) is in testing, where SDL2 also exists side-by-side with it and is intended to be used to test and verify that SDL2 apps that use it are actually compatible. Night-and-day decision-making process compared to Fedora and Arch, which both replaced SDL2 with sdl2-compat, broke a bunch of SDL2 apps because sdl2-compat isn't actually SDL2-compatible yet, and sent everyone to yell at the SDL team about it.
  • account42 1y ago
    Well Fedora is the equivalent of testing for Red Hat and Arch is Arch.
    • starkparker 1y ago
      Even Arch kept SDL2 libs in the repo as a fallback. Fedora jumped straight from SDL2 in the repo to sdl2-compat or nothing. The only way to get consistent SDL2 builds on F42 is by building SDL2 from source.
• anthk 1y ago
  I used to like Debian when configuring ALSA/OSS, XFree86 and such was a source of nightmares. Thus, debconf as a middle layer mechanism to handle several distinct architectures, setups and hardware was a neccesity. Ditto with Yast2 on SuSE. By 2004-2005... not much. Even a bare Slackware with KDE and KDEi (and even XFCE) can do tons of work by itself by just adding an user and accepting the default group belonging array by pressing 'up' at the prompt. Heck, even OpenBSD, minus the volume automount, which can be handled in a breeze with toadd or tray-app in seconds; and if you are smart you can figure DBUS/FDo mount points and integrate then with XFCE/Plasma/Gnome without too much issues (hotplugd can handle device umounting if you set up doas.conf accordinly). The rest? MESA and X.org will handle most of the graphics stuff. Video and audio drivers are autodetected on almost every GNU and *BSD. Printers are often wireless bound so any assistant with look it up fast and attach it to CUPS. Still, I can't handle DPKG/APT's slowness, even if there are libre distros as Trisquel with it. If they rebased their distro as a simpler Parabola LTS release with either Mate or LXDE setups, the user experience would be almost the same, but installing packages would happen at a much faster pace.
  • rs_rs_rs_rs_rs 1y ago
    dpkg/apt in Debian fells slower even compared with dpkg/apt in Ubuntu, not sure why that's the case
• endorphine 1y ago
  If you're upgrading, see https://www.debian.org/releases/trixie/release-notes/upgrading.en.html https://www.debian.org/releases/trixie/release-notes/upgradi....
• LoveMortuus 1y ago
  I'm very sad to see them drop support for 32-bit, since that is the computer on which I have been using Debian for the past 10 years... Does anyone have any suggestions for a 32-bit distro that's still being updated?
  • jama211 1y ago
    Linux mint technically still does, perhaps because they’re lagging behind Debian. AntiX does but that has its own tradeoffs. With full potential respect for your situation, if you’re not able to obtain 64 bit hardware, there’s nothing that wrong with not upgrading your OS for now
    • 2b3a51 1y ago
      Bookworm will get updates for another year if I have read the Debian Wiki correctly so perhaps there is no need for immediate action as Bookworm becomes oldstable? In addition to Mint and AntiX there is also Slackware (I use xfce rather than KDE) but adding software outside the (large) base install is not an 'apt-get thing' process. Salix Linux, based on Slackware, does have package repositories with a reasonable selection of applications. Salix is based on the stable Slackware 15.0 so has nicely aged packages. Void Linux also has an xfce4 based live i686 iso you can look at and decide to install from.
      • LoveMortuus 1y ago
        I also use xfce, my computer is an Acer Aspire One, limited in ... well everything, I did upgrade the storage to an SSD, but it's still an Atom CPU, so whatever is the lightest is the best.
  • account42 1y ago
    Gentoo still supports it but depending on what you want, compile times with modern compilers on old hardware are a pain.
• morserer 1y ago
  They only mentioned it briefly, and not by number, but this release includes 95%+ bit-for-bit reproducibility on AMD64, ARM64, and RISC-V across more than 30,000 packages (92% mean across all architectures). Congratulations to the team--phenomenal work! https://reproduce.debian.net/ https://reproduce.debian.net/
  • guerby 1y ago
    Is there a tool on a given debian trixie system to know what installed packages are not currently reproducible? Alternative to parsing the reproduce web site :)
    • morserer 1y ago
      Yes! From the site: sudo apt install debian-repro-status; debian-repro-status
  • MuffinFlavored 1y ago
    Could you help me understand why the remaining 5% is not bit-for-bit reproducible? For example... if you download a tar of sources pinned to a version, and you run `./configure` and `make` in some kind of container and it doesn't embed some kind of timestamp... why are 95% reproducible and some aren't? Would like to learn/understand.
    • JonChesterfield 1y ago
      Hashtables keyed off the address of objects would be an example. On multiple runs, malloc gives out different addresses (thanks to threads or security concerns) which means things end up in different slots in the table. Then you iterate through it in memory order and you're seeing objects in non-deterministic order, which you do things with. Embedding file paths / timestamps / git shas and similar was popular for a while too and unhelpful for reproducible builds.
• andersa 1y ago
  I've been using the Debian trixie branch for about a year now on my local server, never once had a real issue with anything. Very impressive.
• jjgreen 1y ago
  I've been on Debian forever and love it to bits. But in an act which can only be described as batshit insanity, they have chosen to patch Python's pip3 in a manner which breaks the --prefix option. On Debian pip3 install <whatever> --prefix=/usr/local will install into /usr/local/local, so one has to use the prefix /usr. The same command on, say, OpenSuSE will install into /usr and break your system. Barking mad. https://sources.debian.org/src/python3.7/3.7.3-2+deb10u3/debian/patches/distutils-install-layout.diff/ https://sources.debian.org/src/python3.7/3.7.3-2+deb10u3/deb...
  • zahlman 1y ago
    > python3.7 Certainly a terrible UX, but the motivation is clear: they're trying to get PEP 668 protections for older versions. Virtual environments work a lot better anyway, honestly. (With a properly crafted `pyvenv.cfg`, it should be possible to convince Python that your /usr/local is a virtual environment, but I can't be sure offhand if there are any serious negative consequences of that.)
    • MuffinFlavored 1y ago
      python3.7 is from June 27th, 2018 https://www.python.org/downloads/release/python-370/ https://www.python.org/downloads/release/python-370/ Why is that the default?
      • zahlman 1y ago
        I don't think it is? Or at least, it only was on some particular older Debian release.
        • jjgreen 1y ago
          I think that was the version the patch was introduced, it's certainly in-place on Trixie (which has 3.13).
          • zahlman 1y ago
• Aldipower 1y ago
  Looking forward to 13! Debian 12 in combination with Pipewire is my go to daily use professional audio workstation for 2 years. Coming from Windows, there are no more forced updates anymore preventing me from doing my job. This is a releave. It works so good! Linux for professional audio is really an option now! Most high-end converters are connected via MADI or ADAT anyway, so there is no driver problem existent. Drivers are a consumer grade discussion..
• teleforce 1y ago
  > The overall disk usage for trixie is 403,854,660 kB (403 GB), and is made up of 1,463,291,186 lines of code. This makes Debian Trixie about 32 times larger than Windows XP with approximately 45 millions lines of code, arguably the best Windows OS ever. Debian Trixie is released about 24 years after Windows XP.
  • 3836293648 1y ago
    Sure, but XP came with minimal amounts of bundled software, that's every package in the debian repo.
  • CRConrad 1y ago
    > Windows XP with approximately 45 millions lines of code, arguably the best Windows OS ever. Naah. Early(ish) Win7, or maybe even late Vista.
• torium 1y ago
  Ooo la la, GnuCash 5.10. I'm still on 4.4. Can't find release notes though, help? I've found the docs, but they're huge. I'll looking specifically for a list of differences between 4.4 and 5.10. (Or at least the biggest differences)
• geeB 1y ago
  Io i
• whydoyouasking 1y ago
  TL;DR: Big fat warning to everyone, who's using X11 session on Debian (especially, laptop users): DO NOT UPDATE. Issues I experiencing right now *AFTER* migration Debian 12 -> 13 on X11: 1. kwin_x11, kscreenlocker_greet, Xorg and ksmserver are eating CPU as hell after screen is locked: known issues in KDE6/QT6, affected versions Qt 6.8, 6.9 and 6.10, fixed in Qt 6.9.2 and 6.10.0. Guess which version of Qt is used in Debian 13. 2. "Disks & Devices" applet is reporting wrong disk state (mounted/unmounted) when disk have Device Auto-Mount enabled "On Attach". 3. Track-point device, touch-pad and Bluetooth mouse now is treated as a single device without a way of separating settings for them. Yep, touch-pad settings tab says "No touchpad found". Right now I basically need either agree with changed way of navigation in CAD and browsers with my mouse, or forget about using scroll with my track-pad, or switch the "Press middle button and move mouse to scroll" on every occasion of switching input device. And all of these I found in just two days of using this release. I need to stress the fact that before the update, when it was Debian 12 and KDE5 it was working smoothly, as expected and with all settings accessible from UI. Now, to fix all of this, I need to crawl configs, add scripts, workarounds and so on. It looks like Debian updates now needs to be ignored the same way as it happening with Ubuntu (3+ month), MacOS (5+ month) or Windows (don't).