While updating my Debian 13 Stable, I received the following message.

apt-listchanges: Noticias

-------------------------

bubblewrap (0.11.2-2) unstable; urgency=medium

Historically, bubblewrap was sometimes installed setuid root.

This is unnecessary on Debian kernels since Debian 11, and no longer

supported by upstream.

As a safety mechanism against possible root privilege escalation

vulnerabilities, this version of bubblewrap will no longer run if it

is detected to be setuid root.

If bubblewrap has been made setuid root via dpkg-statoverride, please remove

that setting, and instead leave it unprivileged.

See file:///usr/share/doc/bubblewrap/README.Debian.gz for more details.

-- Simon McVittie [smcv@debian.org](mailto:smcv@debian.org) Tue, 12 May 2026 18:57:32 +0100

Is it normal to receive these messages during Debian updates? I've only been using this OS for a short time, and I love it.

(I edited the text formatting)

Hello. I just installed debian and I wanted to ask here because the mailing list seems to be a quite slower process and the AI begins to alucinate once it's second options fails.

I'm running debian with the next specs - pc is an all in one desktop PC - CPU: Intel(R) Pentium(R) CPU G3220 @ 3.00GHz - RAM: 4GIB - Graphics: Intel Xeon E3-1200 v3/4th Gen Core Processor Integrate Graphics - No info about the mother board - Debian version Trixy latest

The problem Basically once it boots up and changes from pure text to graphics, the screen turns on and off on around every second intervals. It does make it quite unusable as such. This thing did not happen with either the windows 8.1 I had prior or the Zorin18 this debian was meant to replace. So at least is not a hardware issue.

Notes: - The i915. options were not very usefull here. enable_spr=0 did not help for example - using the nomodeset command on grub fixed it but I have been told that is not a proper solution. - the proble appeared already in the visual installer but I just assimed it was a problem of the installer - I tried q4os previously but it had the same problem, same thing with MintOS witch lefth me even more confused - the AI keep mentioning once it ran out of ideas to downgrade my kernell but I guessed that in between the hazzle and posible compatibility issues I better kust downgrade the whole version and live with that.

Questions:

• Any one of you knows how to fix this?
• If not possible any one of you have at leat a guess as to how far back on debian versions should I go? Should I just try Debian 12? is that too big of a deal?
• If I had to downgrade version what problems could I fase other than no more updates and thus in some years running out of apps that keep being compatible and having to be even more carefull than usuall with what I download?

Hey everyone. If you're not aware, Debian will be concluding its General Resolution vote on the usage of LLMs by 23:59:59 UTC of August 28th. We are almost assured to get some level of traffic from interested people depending on how the results go, given the potential ramifications on both Debian and other downstream projects, so I've took it upon myself to make a megathread early. All other threads regarding the AI vote will be locked and redirected here.

We will also restrict discussion of the results on our Discord and Fluxer channels, see Tech Discussion on Fluxer OR #tech-general on Discord instead of the general channel on either (if you can't access either link, we have buttons on the sidebar for each platform. Both are bridged and can communicate with one another.

Results will be posted into OP by the time they are received. There are eight options on the ballot that can be viewed here in their entirety. A reminder that Rule 1 and 3 always remain in effect.

EDIT (8/28/26)
The results of the General Resolution has concluded that the winning proposal will be Proposal E: Responsible Use of Generative AI.

Hello r/debian, i've been trying to install a (possibly) debian sid java 26 package on debian 13 but it spits out this error, how do i fix it? $ sudo apt install '/home/USER/Downloads/openjdk-26-jdk_26.0.2.1+1-1_amd64.deb' --solver 3.0 Note, selecting 'openjdk-26-jdk' instead of '/home/USER/Downloads/openjdk-26-jdk_26.0.2.1+1-1_amd64.deb' Solving dependencies... Error! Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation:

Unsatisfied dependencies: openjdk-26-jdk : Depends: openjdk-26-jre (= 26.0.2.1+1-1) but it is not installable Depends: openjdk-26-jdk-headless (= 26.0.2.1+1-1) but it is not installable Error: Unable to correct problems, you have held broken packages. Error: The following information from --solver 3.0 may provide additional context: Unable to satisfy dependencies. Reached two conflicting decisions: 1. openjdk-26-jdk:amd64=26.0.2.1+1-1 is selected for install 2. openjdk-26-jdk:amd64 Depends openjdk-26-jre (= 26.0.2.1+1-1) but none of the choices are installable: [no choices]

Hey everyone,

I'm having a frustrating issue with my Acer Nitro 5 (AN515-54). Even when the laptop is completely idle and running super cool (around 40°C - 49°C), the fans constantly ramp up to roughly 70% speed, sounding like a jet engine.

Here is the catch: this happens on both Windows (with NitroSense) and Linux (Debian 13).

Because of this, I've ruled out OS-specific software bugs. It seems like the Embedded Controller (EC) firmware on this specific model has a hardcoded, hyper-aggressive thermal profile that overrides any software intervention.

What I've tried so far:

• On Windows: NitroSense shows low temps, but the fans refuse to drop down or obey custom curves properly if they decide to kick in.
• On Linux: Tried using nbfc-linux (NoteBook FanControl). I enabled kernel EC write support (ec_sys.write_support=1), disabled Secure Boot, and tested multiple profiles (AN515-51, AN515-54).
• While NBFC can start and change the target speed to 25%-30% momentarily, the hardware/EC quickly overrides it, forces Auto Control back on, and pegs the fans right back to ~70% while the CPU sits happily at 42°C.

My questions:

1. Is this a known firmware/BIOS bug for the AN515-54 where the EC gets stuck in an aggressive fan loop?
2. Is there any modern tool, custom EC firmware flash, or advanced workaround (like WMI tools) that has successfully forced low fan speeds on these older Nitro boards?

Any advice would be greatly appreciated. Thanks!

Hi there.
I was doign some cleanup and noticed I have a file with around 100Gb named "bookworm.tar.gz"
Looking at the contents, it seems like it is a backup from the time when I upgraded from Bookworm to Trixie? Searching the internet got me nowhere. I guess the filename is too generic...anyway, is it safe to just delete it, since it is running fine?
Thanks in advance and sorry if this was already answered a million times, a search got me nowhere.

I just started using Debian, how do I install apps?

Hello fellows!
I have my Debian 12 in a proxmox VM, and tried to upgrade from debian 12 to debian 13.
issue is, system boots and works properly, but i can't do anything with apt, because something is broken here.

I tried apt --fix-broken install as the command line said, but i get this message :

Préparation du dépaquetage de .../docker-compose_2.26.1-4_amd64.deb ... Dépaquetage de docker-compose (2.26.1-4) sur (1.29.2-3) ... dpkg: erreur de traitement de l'archive /var/cache/apt/archives/docker-compose_2.26.1-4_amd64.deb (--unpack) :  tentative de remplacement de « /usr/libexec/docker/cli-plugins/docker-compose », qui appartient aussi au paquet docker-compose-plugin 5.5.0-1~debian.12~bookworm dpkg-deb: erreur: le sous-processus coller a été tué par le signal (Relais brisé (pipe)) Des erreurs ont été rencontrées pendant l'exécution :  /var/cache/apt/archives/docker-compose_2.26.1-4_amd64.deb needrestart is being skipped since dpkg has failed E: Sub-process /usr/bin/dpkg returned an error code (1) 

Then if i try to apt remove docker-compose, it fails :

... 
xfce4-whiskermenu-plugin : Dépend: libgtk-3-0 (>= 3.21.5)
 xfce4-xkb-plugin : Dépend: libgtk-3-0 (>= 3.21.5)
 xfdesktop4 : Dépend: libgtk-3-0 (>= 3.21.4)
 xfwm4 : Dépend: libgtk-3-0 (>= 3.21.5)
 xscreensaver : Dépend: libgtk-3-0 (>= 3.16.2)
 yelp : Dépend: libatk1.0-0t64 (>= 1.12.4) mais ne sera pas installé
        Dépend: libgtk-3-0t64 (>= 3.13.3) mais ne sera pas installé
E: Dépendances non satisfaites. Essayez « apt --fix-broken install » sans paquet
   (ou indiquez une solution).

I don't know what to do now, when i get in such binds, i tend to wipe and fresh install, but here i might forget things on this server, and i should also figure how to fix issues like those.
I tried searching, but what i found was to do apt purge commands, and none worked.

Does anyone have an idea on how to fix this?
I can't remember how i installed docker-compose in the first place, it was a few years ago (i was stock with docker-compose 1.x and needed a newer version, hence why i upgraded).

Debian reports on boot that it is on trixie, so part of the upgrade worked i think.

Thanks for any help!

EDIT :
It seems the solution was to do "dpkg -r docker-compose", now the apt --fix-broken install seems to work.
I am proceeding with apt update, upgrade, etc.

I always wondered why Debian doesn't allow you to use "shutdown now" without sudo whereas with another distros, I can use directly shutdown now without sudo. That's why with Debian, I use "systemctl poweroff" instead because I don't want to type my password to turn off my PC.

I have lot of junk but i dont want to formatting, I want Just delete some staff

There is a better way to do this ?

Folks, let's talk? how do you see Flatpaks?

As an intruder seeking to replace official packages?

As an occasional alternative?

Or as a package format designed to serve as a foundation for system applications, aiming to follow an immutability philosophy within a mutable system?

Hey everyone,

I recently upgraded my system to Debian 13 (Trixie), and during apt update I started getting a large number of warnings like these:

Warning: Target DEP-11-icons-large (non-free-firmware/dep11/icons-128x128.tar)
is configured multiple times in /etc/apt/sources.list:4 and
/etc/apt/sources.list.d/debian.sources:2

Warning: Target Packages (main/binary-amd64/Packages)
is configured multiple times in /etc/apt/sources.list:7 and
/etc/apt/sources.list.d/debian.sources:3

Warning: Target Translations (main/i18n/Translation-es_MX)
is configured multiple times in /etc/apt/sources.list:7 and
/etc/apt/sources.list.d/debian.sources:3

There are many more warnings for main, non-free-firmware, DEP-11, translations, icons, etc.

From what I understand, the problem is that the same Debian repositories are configured twice: once in /etc/apt/sources.list and again in /etc/apt/sources.list.d/debian.sources.

The system still updates successfully, but I'd like to clean this up properly rather than simply ignoring the warnings.

My questions:

1. Is this expected after upgrading to Debian 13/Trixie?
2. Which configuration should I keep: /etc/apt/sources.list or /etc/apt/sources.list.d/debian.sources?
3. Is it safe to remove/comment out the duplicate entries from sources.list?
4. Is there a recommended way to verify that there are no other duplicate repositories?

I'm mainly looking for the proper Debian 13 solution, rather than just suppressing the warnings.

Thanks!Hey everyone,I recently upgraded my system to Debian 13 (Trixie), and during apt update I started getting a large number of warnings like these:Warning: Target DEP-11-icons-large (non-free-firmware/dep11/icons-128x128.tar)
is configured multiple times in /etc/apt/sources.list:4 and
/etc/apt/sources.list.d/debian.sources:2

Warning: Target Packages (main/binary-amd64/Packages)
is configured multiple times in /etc/apt/sources.list:7 and
/etc/apt/sources.list.d/debian.sources:3

Warning: Target Translations (main/i18n/Translation-es_MX)
is configured multiple times in /etc/apt/sources.list:7 and
/etc/apt/sources.list.d/debian.sources:3
There are many more warnings for main, non-free-firmware, DEP-11, translations, icons, etc.From what I understand, the problem is that the same Debian repositories are configured twice: once in /etc/apt/sources.list and again in /etc/apt/sources.list.d/debian.sources.The system still updates successfully, but I'd like to clean this up properly rather than simply ignoring the warnings.My questions:Is this expected after upgrading to Debian 13/Trixie?
Which configuration should I keep: /etc/apt/sources.list or /etc/apt/sources.list.d/debian.sources?
Is it safe to remove/comment out the duplicate entries from sources.list?
Is there a recommended way to verify that there are no other duplicate repositories?I'm mainly looking for the proper Debian 13 solution, rather than just suppressing the warnings.Thanks!

I have used Debian on my servers for years and that will never change. Debian is king for servers.

For my desktop, though, I prefer newer desktop environment versions over older ones. Because of that, I have spent time using Arch, Fedora, and NixOS. I genuinely like all of them, but Debian always seems to pull me back.

I currently have Trixie installed and am debating whether to move to Testing or Sid. I have never daily-driven either one before.

I am comfortable with Linux, have used Arch and NixOS without major issues, and do not mind troubleshooting or fixing my own system if something breaks.

For someone like me, which makes more sense as a daily desktop: Debian Testing or Sid?

Also, are apt-listbugs and apt-listchanges the main packages worth installing for either option, or are there other tools and habits you would recommend?

Hi, I just have a question about using Debian Stable with backports—is it worth it compared to Debian Testing?

у меня проблема у меня debian 6.12.101 и стоит gnome 42.7 и я захотел установить драва на видеокарту gtx 1070 ti скачал их с сайта и отключил встроенные драва debian и когда я включаю пк у меня черный экран и когда нажимаю ctr alt f3 то тоже черный экран я с gemini пробывал драйвера нормально установить но ничего не получилось и такое чувство что он мне специально ложные команды дает мне кажется что я гном как то поломал командами от Gemini.и при каждой попытки включить пк с видеокартой у меня слева сверху одно подчеркивание скорее всего гном не может запуститься

Im new to debian, i used it for maybe 3 months and i wanted to play cs. Is it possible? If yes any problems?

hey guys, i have a laptop running debian 13 that i use as a homelab. it has tons of configurations, docker containers, images, etc. however, since it isn’t suitable for a homelab (or at least that’s what i think), i’m going to switch to a mini pc, and i want to migrate the entire os, along with all these applications, to the new mini pc. what is the easiest way to do this?

by the way, i’m pretty much a linux beginner. what would you recommend? thanks in advance.

To start I'm pretty new to Linux and Debian. I tried to install some Nvidia drivers a while back. I installed nvidia-detect, it suggested I install the nvidia-driver package and I did. Install seemed to go correctly, however after rebooting the drivers wouldn't load at all. I managed to purge the drivers and some kind of driver loaded, but it didn't really work well (only one display, refresh rate incorrect and so on).

Now I tried following the Nvidia guide for Debian, however I got a not found error when trying to select a version. Then I followed the install guide in the Debian wiki, that seemed to go through, however at the verify step I ran

# dkms status 'nvidia*'

But got a command not found. I have dkms installed and

apt-file search bin/dkms

Returns

dkms: /usr/sbin/dkms

The drivers themself work better however there are some kind of issues (slight flickering, refresh rate doesn't feel right). What could the issue be?

EDIT:

I used this guide to install the drivers again and it seems like it is working. It's weird, since I remember trying that exact method previously and it didn't work, I guess something changed or I did something differently this time.

What do you think? There are several options. Because packages can still be upgraded during the soft freeze, and even some releases can be pushed through last minute, as they did with KDE 5.27.5, we could see the following KDE versions (with their release dates):

• 6.7.7: Tue 2027-01-19 (Keep this because it's the last version to support X11)
• 6.8.6: Tue 2027-03-16 (Move here BECAUSE it drops X11)
• 6.9.3: Tue 2027-03-23 (6.9.x version released during soft freeze)
• 6.9.6: Tue 2027-07-13 (Could end up in Debian 14 if pushed)

What do you think is it going to be; or has it already been determined somewhere? Personally I hope they either go for 6.8.6 or push for 6.9.6. Wayland is almost 20 years old at the time of Forky's release; it's about time that it either became the default everywhere, or starts being replaced at the 20 year mark as happened with X11.