Small problem with two files ..

Totone · 2026-03-03 16:00

Hello

I'm having a small problem with two files, /etc/apt/sources.list and /etc/apt/sources.list.d, which are filling up and causing errors with Synaptic. I don't know how to fix this.

Attached is a preview of the 42 lines:

5000
W: The target Packages (main/binary-amd64/Packages) is specified multiple times in /etc/apt/sources.list:2 and /etc/apt/sources.list.d/20_debian.sources:1
W: The target Packages (main/binary-i386/Packages) is specified multiple times in /etc/apt/sources.list:2 and /etc/apt/sources.list.d/20_debian.sources:1
W: The target Packages (main/binary-all/Packages) is specified multiple times in /etc/apt/sources.list:2 and /etc/apt/sources.list.d/20_debian.sources:1
W: The target Translations (main/i18n/Translation-fr_FR) is specified multiple times in /etc/apt/sources.list:2 and /etc/apt/sources.list.d/20_debian.sources:1
W: The target Translations (main/i18n/Translation-fr) is specified multiple times in /etc/apt/sources.list:2 and /etc/apt/sources.list.d/20_debian.sources:1

W: The Translations target (main/i18n/Translation-en) is specified multiple times in /etc/apt/sources.list:2 and /etc/apt/sources.list.d/20_debian.sources:1
W: The DEP-11 target (main/dep11/Components-amd64.yml) is specified multiple times in /etc/apt/sources.list:2 and /etc/apt/sources.list.d/20_debian.sources:1
W: The DEP-11 target (main/dep11/Components-all.yml) is specified multiple times in /etc/apt/sources.list:2 and /etc/apt/sources.list.d/20_debian.sources:1
W: The target DEP-11-icons-small (main/dep11/icons-48x48.tar) is specified multiple times in /etc/apt/sources.list:2 and /etc/apt/sources.list.d/20_debian.sources:1
W: The target DEP-11-icons (main/dep11/icons-64x64.tar) is specified multiple times in /etc/apt/sources.list:2 and /etc/apt/sources.list.d/20_debian.sources:1
W: The target DEP-11-icons-hidpi (main/dep11/icons-64x64@2.tar) is specified multiple times in /etc/apt/sources.list:2 and /etc/apt/sources.list.d/20_debian.sources:1
W: The The target DEP-11-icons-large (main/dep11/icons-128x128.tar) is specified multiple times in /etc/apt/sources.list:2 and /etc/apt/sources.list.d/20_debian.sources:1

Regards

q4osteam · 2026-03-03 21:40

Run commands in terminal and post the output:
$ cat /etc/apt/sources.list
$ cat /etc/apt/sources.list.d/20_debian.sources

Totone · 2026-03-04 08:22

# cat /etc/apt/sources.list
# See https://wiki.debian.org/SourcesList for more information.
deb http://deb.debian.org/debian trixie main non-free-firmware
deb-src http://deb.debian.org/debian trixie main non-free-firmware

deb http://deb.debian.org/debian trixie-updates main non-free-firmware
deb-src http://deb.debian.org/debian trixie-updates main non-free-firmware

deb http://security.debian.org/debian-security/ trixie-security main non-free-firmware
deb-src http://security.debian.org/debian-security/ trixie-security main non-free-firmware

# Backports allow you to install newer versions of software made available for this release
deb http://deb.debian.org/debian trixie-backports main non-free-firmware
deb-src http://deb.debian.org/debian trixie-backports main non-free-firmware

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

# cat /etc/apt/sources.list.d/20_debian.sources
### Debian essential repositories

Enabled: yes
Types: deb
URIs: http://deb.debian.org/debian/
Suites: trixie
Components: main contrib non-free non-free-firmware
Signed-By: /usr/share/keyrings/debian-archive-keyring.gpg
#^^^
##_origin deb.debian.org | o=Debian,a=stable,n=trixie,l=Debian,c=[main|contrib|non-free],b=[amd64|i386|arm64|armhf]
## deb http://deb.debian.org/debian/ trixie main contrib non-free non-free-firmware
## deb-src http://deb.debian.org/debian/ trixie main contrib non-free non-free-firmware

Enabled: yes
Types: deb
URIs: http://security.debian.org/
Suites: trixie-security
Components: main contrib non-free non-free-firmware
Signed-By: /usr/share/keyrings/debian-archive-keyring.gpg
#^^^
##_origin security.debian.org | o=Debian,a=stable-security,n=trixie-security,l=Debian-Security,c=[main|contrib|non-free],b=[amd64|i386|arm64|armhf]
## deb http://security.debian.org/ trixie-security main contrib non-free non-free-firmware
## deb-src http://security.debian.org/ trixie-security main contrib non-free non-free-firmware

Enabled: yes
Types: deb
URIs: http://deb.debian.org/debian/
Suites: trixie-updates
Components: main contrib non-free non-free-firmware
Signed-By: /usr/share/keyrings/debian-archive-keyring.gpg
#^^^
##_origin deb.debian.org | o=Debian,a=stable-updates,n=trixie-updates,l=Debian,c=[main|contrib|non-free],b=[amd64|i386|arm64|armhf]
## deb http://deb.debian.org/debian/ trixie-updates main contrib non-free non-free-firmware
## deb-src http://deb.debian.org/debian/ trixie-updates main contrib non-free non-free-firmware

## Enabled: no
## Types: deb
## URIs: http://deb.debian.org/debian/
## Suites: trixie-proposed-updates
## Components: main contrib non-free non-free-firmware
## Signed-By: /usr/share/keyrings/debian-archive-keyring.gpg
#^^^
##_origin deb.debian.org
## deb http://deb.debian.org/debian/ trixie-proposed-updates main contrib non-free non-free-firmware
## deb-src http://deb.debian.org/debian/ trixie-proposed-updates main contrib non-free non-free-firmware

q4osteam · 2026-03-04 14:16

You have conflicting repositories in your sources list. The file "/etc/apt/sources.list" should be empty in Q4OS, do you know how it got populated ? Did you take some repositories related action before the issue arises ?

Totone · 2026-03-04 15:31

I have no idea if this could be related to an installation from a snapshot created with setup_s4-snapshot-extq_1.1-a1.qsi. This occurred after the OS detected a disk problem that required me to reformat.

On the other hand, I regularly perform a partial backup with timeshift.
Does this mean I'll have to destroy the timeshift and snapshot files?
Regards

q4osteam · 2026-03-04 15:43

Totone wrote:

I have no idea if this could be related to an installation from a snapshot created with setup_s4-snapshot-extq_1.1-a1.qsi. ..

Maybe.
- Did the installation from the snapshot work properly for at least some time ?
- What config option did you select when creating the .iso snapshot ? Keep users/System, etc...

Totone wrote:

Does this mean I'll have to destroy the timeshift and snapshot files?

No, you don't need to destroy them. Just use Timeshift as before.

We would guess, you will be fine if you empty the /etc/apt/sources.list file. Please post back answers and the result for us to make investigation.

q4osteam · 2026-03-05 09:52

We have been able to reproduce the issue. It's connected to installation from the S4-snapshot installation. We are going to make a fix now.

Totone · 2026-03-05 12:42

hello,

I launch s4-snapshot, I choose the directory where I save the ISO.
I leave the default startup options:
"quiet splash loglevel=3 systemd.log_color=0 systemd.show_status=1"
and after a while it finishes and there are 2 files: an ISO and an MD5 file.

If it turns out there's a problem with s4-snapshot,
regarding modifications to make MX-snapshot work on Q4oq,
you should contact "adrian@debian.org"; this is the email address that
appears in the "About" section.

regards

q4osteam · 2026-03-06 12:38

We have fixed the issue. You only need to update your original system to create new snapshots.

Totone · 2026-03-07 12:21

Hello,
System updated and snapshot created, but I think something's wrong:

The size remained the same as on the 69GB disk with the newsnapshot,
which took about an hour to complete, and there was no compression.

In comparison, with Mx-Linux, the size was 43GB before and 13.5GB after the snapshot performed compression.
The duration was 17 minutes.

I uninstalled setup_s4-snapshot, reinstalled the update, and created a snapshot again. The problem persists.

Parallel mksquashfs: Using 2 processors
Creating 4.0 filesystem on /home/ /s4-snapshot-LinQTxIJ/iso-template/antiX/linuxfs, block size 131072.
[=====================================================\ ] 1099100/1123697 97%
File /run/s4-snapshot/bind-root-overlay/root/var/lib/smartmontools/attrlog.SPCC_Solid_State_Disk-WWDD250314050004249.ata.csv changed size while reading filesystem, attempting to re-read

Unrecognised xattr prefix system.posix_acl_access
Unrecognised xattr prefix system.posix_acl_access
Unrecognised xattr prefix system.posix_acl_access

Unrecognised xattr prefix system.posix_acl_access
Unrecognised xattr prefix system.posix_acl_access

Unrecognised xattr prefix system.posix_acl_access

Unrecognised xattr prefix system.posix_acl_access
Unrecognised xattr prefix system.posix_acl_access

Unrecognised xattr prefix system.posix_acl_access
[=======================================================|] 1123697/1123697 100%

regards,

q4osteam · 2026-03-07 15:52

What Q4OS system are you using ? Desktop environment, OS version ?

Size of snapshot:
How much disk space do you use ? Please run in terminal and post back the result:
$ df -h
You can also set the compression level in the S4 snapshot window. The resulting size depends on the amount of disk space used. For example, we created an .iso file with a size of 3 GB.

Message “Unrecognised xattr prefix system.posix_acl_access”:
You may need to reboot after installing the **s4-snapshot** package to eliminate this message. However, the message should not cause any issues as the ISO image has been created successfully. Does it boot properly?

Totone · 2026-03-08 11:02

Hello,

So far, I've always used the default settings on the MX system
and haven't had any compression issues.

The snapshot created a snapshot of about a third of the system.
(Example given in the previous post.)

Where can I download the new s4-snapshot?

Q4OS 6 Andromeda KDE X11
q4os-6.5-x64.r2.iso

version :
cat /etc/debian_version
13.3

cat /etc/issue
Debian GNU/Linux 13 \n \l

df -h
Sys. de fichiers Taille Utilisé Dispo Uti% Monté sur
udev 5,8G 0 5,8G 0% /dev
tmpfs 1,2G 15M 1,2G 2% /run
/dev/sda2 221G 78G 133G 37% /
tmpfs 5,9G 0 5,9G 0% /dev/shm
efivarfs 128K 64K 60K 52% /sys/firmware/efi/efivars
tmpfs 5,0M 0 5,0M 0% /run/lock
tmpfs 1,0M 0 1,0M 0% /run/credentials/systemd-journald.service
tmpfs 5,9G 4,0K 5,9G 1% /tmp
/dev/sda1 300M 16M 284M 6% /boot/efi
tmpfs 1,2G 108K 1,2G 1% /run/user/1000
tmpfs 1,2G 60K 1,2G 1% /run/user/0

regards,

Last edited by Totone (2026-03-08 11:03)

q4osteam · 2026-03-08 11:37

Thanks for the information. We checked the resulted compression of s4-snapshot, and it works fine. The compression ratio depends on the data being compressed, so it may vary quite significantly.

Totone wrote:

/dev/sda2 221G 78G 133G 37% /

We can see that you are using 78 GB of the root disk space. The created .iso file is 64 GB, which is quite expected and correct.

We don't see any issue with your installation. If you have any, please specify, we will take a look.

Q4OS Forum

#1 2026-03-03 16:00

Small problem with two files ..

#2 2026-03-03 21:40

Re: Small problem with two files ..

#3 2026-03-04 08:22

Re: Small problem with two files ..

#4 2026-03-04 14:16

Re: Small problem with two files ..

#5 2026-03-04 15:31

Re: Small problem with two files ..

#6 2026-03-04 15:43

Re: Small problem with two files ..

#7 2026-03-05 09:52

Re: Small problem with two files ..

#8 2026-03-05 12:42

Re: Small problem with two files ..

#9 2026-03-06 12:38

Re: Small problem with two files ..

#10 2026-03-07 12:21

Re: Small problem with two files ..

#11 2026-03-07 15:52

Re: Small problem with two files ..

#12 2026-03-08 11:02

Re: Small problem with two files ..

#13 2026-03-08 11:37

Re: Small problem with two files ..

Board footer