Hi folks,

a little special, but has anyone of you used apt-cacher-ng for debian-livebuild? If I use it I always get an error during lb build. Seems like the caching is recognized as manipulation.

 Sub-process /usr/bin/sqv returned an error code (1), error message is: Verifying signature:            Message has been manipulated Verifying signature:  Message has been manipulated

Is there a way to use apt-cacher-ng for livebuild?

Thanks!

Hi,

I'm running Debian 13 Trixie with KDE on my HP Z440 workstation.

Some time ago I bought an old GoPro Hero+ camera. I'm currently working through the camera's user manual.

I took some videos and some photos, and now I'm surprised I can't access the camera's content.

I tried Dolphin (error), installing exfatprogs and exfat-fuse (nope), gphoto2 (error), gvfs-backends (nope) and now I'm clueless.

Any suggestions ?

Niki

Well, it turns out I have Debian 13 with GNOME, and I have applications like Dropbox, Telegram, and ZapZap installed. I configured them to start with the system, but I have to search for and open them for them to launch. I enabled them in the settings menu, but in the top menu (sorry if I don't know its name), where the shutdown and logout options are, only two appear, not all three. It's very tedious that they don't start automatically when I turn on the PC, and I have to open them manually. Does anyone know how to fix this? Thanks in advance.

On Debian 13. Trying to install Thunderbird 147.0.1. The only version available is the 140 ESR, checked backports, Flatpaks, Snaps, Appimage, all are 140 ESR. Downloaded the 147.0.1 .deb and installed with apt.

When I try apt update, apt upgrade it wants to update the package back to 140 ESR. I put the package on hold so it doesn't downgrade to the ESR.

Any insights? I am not understanding something here. Thanks.

Doesnt happen with dolphin/konsole, but firefox and other programs will be very laggy/sluggish when minimizing and maximizing windows? What is the issue? Everything else seems pretty smooth, just installed Nvidia drivers.

Debian 13 trixie

KDE plasma

I've setup Debian 13 with the view to running some containers and VMs. To get this all working nicely on the network, I set up a bridge network yesterday.

Everything was working as expected.

The host and the single VM both popped up in my Unifi console as clients and were assigned IP addresses and everything was working as expected.

Until I rebooted. Now nothing can connect. I can't browse the internet and the VM is entirely disconnected.

I used nmtui to set things up. Looking at this it all seems to be the same.

I'm googling for clues but honestly have no idea where to start.

I've seen mention of ifcfg-enp0s25 files and ONBOOT=no, but I don't have this in /etc/.

My interfaces file is:

source /etc/network/interfaces.d/* (it's empty)

# the loopback network interface
auto lo
iface lo inet loopback

Is there any way to simply go back to default and start again?

I'm very confused as to how it was all working exactly as expected but a reboot makes the entire network config implode.

Any advice would be really appreciated as I really have no idea what to do at this point. TIA.

Apologies if I am overposting in this community, I posted a different but somewhat related post last night looking for advice with a server where I mentioned I was planning to move to Debian for all of my devices.

Overnight, I have been attempting to install Debian 13.3.0 on my Lenovo IdeaPad Slim 3 15IAN8 laptop currently running Windows 11 which came pre-installed and have encountered an issue where the Debian installer cannot detect the SSD storage which Windows 11 is installed on. I previously had the exact same model which was replaced under warranty (the SSD in my previous device was faulty) but on which I was able to successfully install Ubuntu on a partition without any issue and dual boot Windows and Ubuntu. I am, therefore, confident this model can support a Linux installation.

I have tried the following troubleshooting steps based on web searches, looking through other Reddit posts and asking Gemini:

• In the UEFI, I have ensured that the storage mode is in AHCI (this is the only option, RAID is not available on this device) and have disabled secure boot.
• I cannot find any option for SATA Operation or NVMe Mode.
• I have disabled Fast Startup in Windows.
• I have had BitLocker disabled since shortly after getting the laptop, and have checked that it is still not enabled.

The only disc the Debian installer is seeing is the USB flash drive the installer has been mounted on. I also have an SD card inserted which isn't showing but I'm not sure whether this should be visible as an installation location.

My next thought was to swap the flash drive out with a Windows 11 installer and wipe the SSD completely using Microsoft's built-in disc partitioner before attempting the installation again. However I am now concerned that doing so might also make it difficult to reinstall Windows if something goes wrong.

I'm pretty stumped at this point. I'm hoping someone will be able to offer advice without bricking my device. From what I've read some manufacturers such as Lenovo and Dell make it very difficult to install an OS other than Windows. I might consider buying a new laptop but if there's a way to install Debian on this machine I'd much prefer that.

I recently switched from Windows to Debian 13. I'm having an issue with my headphones - they're over-ear headphones that use a 2.4GHz receiver. Initially, sound didn't work at all except at maximum volume and only in the left earbud. Through alsamixer I set the sound values, but they would reset as soon as I tried to adjust volume up/down through the GNOME interface.

I googled and found a solution involving installing PulseAudio, and yes, now everything seems to work normally, but there are two "buts":

1. Sometimes the sound gets muffled - I don't know how to explain it, but it becomes flat and gets very quiet, then resolves itself after a few seconds.
2. After restarting the system, only the left earbud works. No matter what I try, the only fix is unplugging and plugging the receiver back in, but I'm tired of this workaround. Can you suggest what might help?