Dear Maintainer,


   * What led up to the situation?
Opening gnome-software showed "Unsere Empfehlungen" (en: recommendation) for applications "Builder". When selected all screenshots fail with "Bildschirmfoto nicht gefunden". Builder is just an example. It also applies to other applications.

   * What outcome did you expect instead?
Screenshots should be displayed.

I tracked it down to the usage of the following file which has a date 2021-08-08:
16:48:20:0682 XbSilo compiling /var/lib/app-info/yaml/deb.debian.org_debian_dists_bullseye_main_dep11_Components-amd64.yml.gz:ctime=1640794691.680796:func-id=AddIcons@2:func-id=AppStreamUpgrade2@3:func-id=AddOriginKeyword@1:scope=system:filename=/var/lib/app-info/yaml/deb.debian.org_debian_dists_bullseye_main_dep11_Components-amd64.yml.gz…
$ ls -l --dereference-command-line /var/lib/app-info/yaml/deb.debian.org_debian_dists_bullseye_main_dep11_Components-amd64.yml.gz
-rw-r--r-- 1 root root 6213469  8. Aug 10:16 /var/lib/app-info/yaml/deb.debian.org_debian_dists_bullseye_main_dep11_Components-amd64.yml.gz

All resized images in this fail:
$ wget --no-verbose --spider --input-file=<(appstreamcli dump org.gnome.Builder.desktop | grep image | egrep --only-matching 'https?://[^<]*')
https://appstream.debian.org/media/bullseye/org/gnome/Builder.desktop/80ccb2db1c02d5a6749463723e614f20/screenshots/image-1_1248x702.png:
Die Datei auf dem Server existiert nicht -- Verweis ist nicht gültig!
https://appstream.debian.org/media/bullseye/org/gnome/Builder.desktop/80ccb2db1c02d5a6749463723e614f20/screenshots/image-1_752x423.png:
Die Datei auf dem Server existiert nicht -- Verweis ist nicht gültig!
https://appstream.debian.org/media/bullseye/org/gnome/Builder.desktop/80ccb2db1c02d5a6749463723e614f20/screenshots/image-1_624x351.png:
Die Datei auf dem Server existiert nicht -- Verweis ist nicht gültig!
https://appstream.debian.org/media/bullseye/org/gnome/Builder.desktop/80ccb2db1c02d5a6749463723e614f20/screenshots/image-1_224x126.png:
Die Datei auf dem Server existiert nicht -- Verweis ist nicht gültig!
2021-12-29 19:01:08 URL: https://appstream.debian.org/media/bullseye/org/gnome/Builder.desktop/80ccb2db1c02d5a6749463723e614f20/screenshots/image-1_orig.png 200 OK
https://appstream.debian.org/media/bullseye/org/gnome/Builder.desktop/80ccb2db1c02d5a6749463723e614f20/screenshots/image-2_1248x702.png:
Die Datei auf dem Server existiert nicht -- Verweis ist nicht gültig!
https://appstream.debian.org/media/bullseye/org/gnome/Builder.desktop/80ccb2db1c02d5a6749463723e614f20/screenshots/image-2_752x423.png:
Die Datei auf dem Server existiert nicht -- Verweis ist nicht gültig!
https://appstream.debian.org/media/bullseye/org/gnome/Builder.desktop/80ccb2db1c02d5a6749463723e614f20/screenshots/image-2_624x351.png:
Die Datei auf dem Server existiert nicht -- Verweis ist nicht gültig!
https://appstream.debian.org/media/bullseye/org/gnome/Builder.desktop/80ccb2db1c02d5a6749463723e614f20/screenshots/image-2_224x126.png:
Die Datei auf dem Server existiert nicht -- Verweis ist nicht gültig!
2021-12-29 19:01:08 URL: https://appstream.debian.org/media/bullseye/org/gnome/Builder.desktop/80ccb2db1c02d5a6749463723e614f20/screenshots/image-2_orig.png 200 OK
https://appstream.debian.org/media/bullseye/org/gnome/Builder.desktop/80ccb2db1c02d5a6749463723e614f20/screenshots/image-3_1248x702.png:
Die Datei auf dem Server existiert nicht -- Verweis ist nicht gültig!
https://appstream.debian.org/media/bullseye/org/gnome/Builder.desktop/80ccb2db1c02d5a6749463723e614f20/screenshots/image-3_752x423.png:
Die Datei auf dem Server existiert nicht -- Verweis ist nicht gültig!
https://appstream.debian.org/media/bullseye/org/gnome/Builder.desktop/80ccb2db1c02d5a6749463723e614f20/screenshots/image-3_624x351.png:
Die Datei auf dem Server existiert nicht -- Verweis ist nicht gültig!
https://appstream.debian.org/media/bullseye/org/gnome/Builder.desktop/80ccb2db1c02d5a6749463723e614f20/screenshots/image-3_224x126.png:
Die Datei auf dem Server existiert nicht -- Verweis ist nicht gültig!
2021-12-29 19:01:09 URL: https://appstream.debian.org/media/bullseye/org/gnome/Builder.desktop/80ccb2db1c02d5a6749463723e614f20/screenshots/image-3_orig.png 200 OK
https://appstream.debian.org/media/bullseye/org/gnome/Builder.desktop/80ccb2db1c02d5a6749463723e614f20/screenshots/image-4_1248x702.png:
Die Datei auf dem Server existiert nicht -- Verweis ist nicht gültig!
https://appstream.debian.org/media/bullseye/org/gnome/Builder.desktop/80ccb2db1c02d5a6749463723e614f20/screenshots/image-4_752x423.png:
Die Datei auf dem Server existiert nicht -- Verweis ist nicht gültig!
https://appstream.debian.org/media/bullseye/org/gnome/Builder.desktop/80ccb2db1c02d5a6749463723e614f20/screenshots/image-4_624x351.png:
Die Datei auf dem Server existiert nicht -- Verweis ist nicht gültig!
https://appstream.debian.org/media/bullseye/org/gnome/Builder.desktop/80ccb2db1c02d5a6749463723e614f20/screenshots/image-4_224x126.png:
Die Datei auf dem Server existiert nicht -- Verweis ist nicht gültig!
2021-12-29 19:01:09 URL: https://appstream.debian.org/media/bullseye/org/gnome/Builder.desktop/80ccb2db1c02d5a6749463723e614f20/screenshots/image-4_orig.png 200 OK
https://appstream.debian.org/media/bullseye/org/gnome/Builder.desktop/80ccb2db1c02d5a6749463723e614f20/screenshots/image-5_1248x702.png:
Die Datei auf dem Server existiert nicht -- Verweis ist nicht gültig!
https://appstream.debian.org/media/bullseye/org/gnome/Builder.desktop/80ccb2db1c02d5a6749463723e614f20/screenshots/image-5_752x423.png:
Die Datei auf dem Server existiert nicht -- Verweis ist nicht gültig!
https://appstream.debian.org/media/bullseye/org/gnome/Builder.desktop/80ccb2db1c02d5a6749463723e614f20/screenshots/image-5_624x351.png:
Die Datei auf dem Server existiert nicht -- Verweis ist nicht gültig!
https://appstream.debian.org/media/bullseye/org/gnome/Builder.desktop/80ccb2db1c02d5a6749463723e614f20/screenshots/image-5_224x126.png:
Die Datei auf dem Server existiert nicht -- Verweis ist nicht gültig!
2021-12-29 19:01:10 URL: https://appstream.debian.org/media/bullseye/org/gnome/Builder.desktop/80ccb2db1c02d5a6749463723e614f20/screenshots/image-5_orig.png 200 OK
https://appstream.debian.org/media/bullseye/org/gnome/Builder.desktop/80ccb2db1c02d5a6749463723e614f20/screenshots/image-6_1248x702.png:
Die Datei auf dem Server existiert nicht -- Verweis ist nicht gültig!
https://appstream.debian.org/media/bullseye/org/gnome/Builder.desktop/80ccb2db1c02d5a6749463723e614f20/screenshots/image-6_752x423.png:
Die Datei auf dem Server existiert nicht -- Verweis ist nicht gültig!
https://appstream.debian.org/media/bullseye/org/gnome/Builder.desktop/80ccb2db1c02d5a6749463723e614f20/screenshots/image-6_624x351.png:
Die Datei auf dem Server existiert nicht -- Verweis ist nicht gültig!
https://appstream.debian.org/media/bullseye/org/gnome/Builder.desktop/80ccb2db1c02d5a6749463723e614f20/screenshots/image-6_224x126.png:
Die Datei auf dem Server existiert nicht -- Verweis ist nicht gültig!
2021-12-29 19:01:10 URL: https://appstream.debian.org/media/bullseye/org/gnome/Builder.desktop/80ccb2db1c02d5a6749463723e614f20/screenshots/image-6_orig.png 200 OK

https://appstream.debian.org/bullseye/main/metainfo/gnome-builder.html has writes "Last updated on: 2021-12-18 14:31 [UTC]" and has other URLs that do work as they can be found in https://appstream.debian.org/media/bullseye/org/gnome/Builder.desktop/80ccb2db1c02d5a6749463723e614f20/screenshots/ .

It seems that DEP-11/appstream-data on https://ftp.debian.org/debian/dists/bullseye/main/dep11/ and the other releases is never updated with new data from https://appstream.debian.org/data/bullseye/main/ and therefore more and more metadata will fail over time.

Workaround is to download the updated file without 'apt update' to the
same location and doing an appstream refresh. Screenshots of "Builder"
are visible after that:

# wget --timestamping
'https://appstream.debian.org/data/bullseye/main/Components-amd64.yml.gz' -O
'/var/lib/app-info/yaml/deb.debian.org_debian_dists_bullseye_main_dep11_Components-amd64.yml.gz'
[...]
# ls -l --dereference-command-line
/var/lib/app-info/yaml/deb.debian.org_debian_dists_bullseye_main_dep11_Components-amd64.yml.gz
-rw-r--r-- 1 root root 6270308 18. Dez 15:25 
/var/lib/app-info/yaml/deb.debian.org_debian_dists_bullseye_main_dep11_Components-amd64.yml.gz
# appstreamcli refresh-cache --force
[...]

The source of these files is configured in
/etc/apt/apt.conf.d/50appstream of package appstream and can be read for
example by:
# apt-get indextargets --format '$(URI) $(FILENAME)' 'Component: main'
'Identifier: DEP-11'
http://deb.debian.org/debian/dists/bullseye/main/dep11/Components-amd64.yml
/var/lib/apt/lists/deb.debian.org_debian_dists_bullseye_main_dep11_Components-amd64.yml.gz

APT can not be configured to download single files of an otherwise
non-repo like https://appstream.debian.org/data/bullseye/main/ so the
files have to be integrated somewhere in the repo for APT to get them or
have to be synced not using APT.

The changelog tells the download via APT is probably done since 2015,
but how where updates supposed to work?

<<<
appstream (0.9.0-1) unstable; urgency=medium

   * New upstream release: 0.9.0
   * Adjust to libappstream ABI break
   * Enable APT support

Checking all releases with the following script it seems to me that updates from appstream to ftp-master are done on "testing" and "unstable" only leaving out "stable" notably since the beginning in 2016. Is there some rationale behind this or is it a bug?
package appstream has hard reverse dependencies for GNOME and others that rely on it to get the *updated* AppStream-Data for them to use.

$ cat appstream-check.sh
#!/bin/bash

WGET='wget --quiet --show-progress --timestamping'
for RELEASE in sid buzz rex bo hamm slink potato woody sarge etch lenny squeeze wheezy jessie stretch buster bullseye bookworm trixie; do
	for COMPONENT in main contrib non-free; do
		${WGET} "https://appstream.debian.org/data/${RELEASE}/${COMPONENT}/Components-amd64.yml.gz"         -O "${RELEASE}-${COMPONENT}-appstream-Components-amd64.yml.gz"
		${WGET} "https://ftp.debian.org/debian/dists/${RELEASE}/${COMPONENT}/dep11/Components-amd64.yml.gz" -O "${RELEASE}-${COMPONENT}-mirrorcpy-Components-amd64.yml.gz"
	done
done
stat --format '%y %n X%sX' *.yml.gz | grep -v 'X0X' | cut -d' ' -f1,4 | column --table | sort
$ ./appstream-check.sh
[...]
2017-06-16  stretch-contrib-mirrorcpy-Components-amd64.yml.gz
2017-06-16  stretch-main-mirrorcpy-Components-amd64.yml.gz
2017-06-16  stretch-non-free-mirrorcpy-Components-amd64.yml.gz
2017-06-18  stretch-contrib-appstream-Components-amd64.yml.gz
2017-06-18  stretch-main-appstream-Components-amd64.yml.gz
2017-06-18  stretch-non-free-appstream-Components-amd64.yml.gz
2019-06-24  buster-non-free-appstream-Components-amd64.yml.gz
2019-06-24  buster-non-free-mirrorcpy-Components-amd64.yml.gz
2019-06-27  buster-contrib-appstream-Components-amd64.yml.gz
2019-06-27  buster-contrib-mirrorcpy-Components-amd64.yml.gz
2019-07-03  buster-main-appstream-Components-amd64.yml.gz
2019-07-03  buster-main-mirrorcpy-Components-amd64.yml.gz
2021-08-01  bullseye-contrib-mirrorcpy-Components-amd64.yml.gz
2021-08-08  bullseye-main-mirrorcpy-Components-amd64.yml.gz
2021-08-08  bullseye-non-free-mirrorcpy-Components-amd64.yml.gz
2021-09-11  bullseye-non-free-appstream-Components-amd64.yml.gz
2021-10-09  bullseye-contrib-appstream-Components-amd64.yml.gz
2021-12-18  bullseye-main-appstream-Components-amd64.yml.gz
2021-12-31  bookworm-contrib-appstream-Components-amd64.yml.gz
2021-12-31  bookworm-contrib-mirrorcpy-Components-amd64.yml.gz
2021-12-31  bookworm-non-free-appstream-Components-amd64.yml.gz
2021-12-31  bookworm-non-free-mirrorcpy-Components-amd64.yml.gz
2021-12-31  sid-contrib-appstream-Components-amd64.yml.gz
2021-12-31  sid-contrib-mirrorcpy-Components-amd64.yml.gz
2022-01-01  bookworm-main-appstream-Components-amd64.yml.gz
2022-01-01  bookworm-main-mirrorcpy-Components-amd64.yml.gz
2022-01-01  sid-main-appstream-Components-amd64.yml.gz
2022-01-01  sid-main-mirrorcpy-Components-amd64.yml.gz
2022-01-01  sid-non-free-appstream-Components-amd64.yml.gz
2022-01-01  sid-non-free-mirrorcpy-Components-amd64.yml.gz

I believe the root cause is in https://salsa.debian.org/ftp-team/dak/-/blob/master/config/debian/dinstall.variables#L25

<<<
# dists for which we import external data (i18n, dep11)
# as thats usually testing and unstable, but we need codenames,
# get em out of the db.
extimportdists=""
if [ "${functionname}" = ftp-master.debian.org ]; then
   for suite in testing unstable; do
     codename=$(dak admin suite-config get-value ${suite} codename)
     extimportdists="${extimportdists} ${codename}"
   done
fi

${extimportdists} is later used for iteration in function dep11() in https://salsa.debian.org/ftp-team/dak/-/blob/master/config/debian/dinstall.functions#L106 so only testing and unstable have updated AppStream-data.

https://blog.tenstral.net/2015/12/appstreamdep-11-fully-supported-in-debian-now.html and the debian wiki promote otherwise:

This seemingly never has been resolved and the most prevalent linux app
store (to my knowledge, I only use aptitude 🤩) `gnome-software` looks
direly broken on a current trixie live system.. log shows loads of

If that script not including `stable` is in fact the source of the
problem, can someone privileged to change it please fix it to boost up
debian's reputation amongst linux noobs that tiny bit? 😂

Am Fr., 18. Sept. 2026 um 14:33 Uhr schrieb Marcel Partap <mpartap@gmx.net>:

Your metadata must be ancient... Did you run an `apt update` recently?
Can you provide the output of `appstreamcli status`?

If you remove GNOME Software's own cache, does that solve the issue?
```
gnome-software --quit
rm -r ~/.cache/gnome-software
gnome-software --verbose
```

I can't reproduce this here, so I assume you must have stale metadata
somehow (and that might indeed be some kind of bug, because this data
should update via APT).

Best,
    Matthias

This is still happening on a fresh install of Debian 13 with KDE - so it's
not gnome specific.  All tested thumbnails return 404 not found.  I'm not
sure how you aren't able to reproduce this issue.  How can I help?
https://appstream.debian.org/media/trixie/org/gnome/TwentyFortyEight/ff33fadaa7c0dff69bd6e4c6a7b9c8d5/screenshots/image-1_224x240@1.png
'

works

Hello,

I can confirm that this issue is reproducible on Debian 13 (Trixie) as of
October 11–12, 2026.

I investigated the problem after noticing that KDE Discover displayed
broken screenshot placeholders for essentially every application, despite
successfully loading application descriptions, ratings, and other metadata.

The investigation indicates that Debian's official stable APT repository is
distributing outdated DEP-11 metadata whose screenshot references no longer
exist on Debian's AppStream servers.

Importantly, this does not appear to be caused by a stale local APT cache.
The metadata currently distributed by Debian's official repository is
itself outdated relative to the AppStream generator.


1. SYSTEM INFORMATION
=====================

Distribution: Debian GNU/Linux 13 (Trixie)
Desktop environment: KDE Plasma
KDE Discover: 6.3.6-1
AppStream: 1.0.5-1
Architecture: amd64
Repository: deb.debian.org, trixie/main
Investigation date: October 11–12, 2026

AppStream reports a populated software catalog:

AppStream Status:
Version: 1.0.5

OS metadata sources:
 Software catalog data
 Group: os-catalog
  /var/lib/swcatalog/yaml
   • YAML: 4
  /var/lib/swcatalog/icons
   • Iconsets:
       debian-trixie-main
       debian-trixie-contrib
       debian-trixie-non-free-firmware
       debian-trixie-non-free

Summary:
✔ We have information on 2626 software components.

The system's AppStream metadata was refreshed successfully, but this did
not resolve the missing screenshots.


2. KDE DISCOVER REQUESTS NONEXISTENT SCREENSHOT URLS
===================================================

When launching Discover from a terminal and viewing GIMP, the following
errors appear:

QML QQuickImage: Error transferring
https://appstream.debian.org/media/trixie/org/gimp/GIMP/81aa8be6edc018b9d60a2f0cd75bd113/screenshots/image-1_orig.png
- server replied:

Similar errors occur for all four GIMP screenshots and their thumbnail
variants.

Testing the URL directly:

curl -IL --max-time 15 \
'
https://appstream.debian.org/media/trixie/org/gimp/GIMP/81aa8be6edc018b9d60a2f0cd75bd113/screenshots/image-1_orig.png
'

Result:

HTTP/2 404
server: Apache

The thumbnail variant also returns HTTP 404:

https://appstream.debian.org/media/trixie/org/gimp/GIMP/81aa8be6edc018b9d60a2f0cd75bd113/screenshots/image-1_1248x702@1.png


3. VERIFIED AGAINST FOUR DEBIAN SERVER ADDRESSES
================================================

To rule out DNS filtering, resolver problems, or a single out-of-sync
server, I tested the same URL against all four IPv4 addresses returned by
public DNS for appstream.debian.org.

The tests used curl's --resolve option to preserve the correct HTTPS
hostname while selecting each server directly.

Results:

194.177.211.216  HTTP 404
128.31.0.62     HTTP 404
130.89.148.77   HTTP 404
194.71.11.122   HTTP 404

All four servers returned HTTP 404.

Local DNS resolution also returned the same addresses as Cloudflare
(1.1.1.1) and Google (8.8.8.8).

This makes local DNS filtering or an individual server synchronization
problem unlikely.


4. BROKEN URLS ORIGINATE IN DEBIAN'S OFFICIAL DEP-11 METADATA
=============================================================

The installed DEP-11 metadata is located at:

/var/lib/apt/lists/deb.debian.org_debian_dists_trixie_main_dep11_Components-amd64.yml.gz

The corresponding AppStream catalog entry is accessed through:

/var/lib/swcatalog/yaml/

Examining the compressed YAML confirms that the GIMP entry contains the
exact screenshot paths Discover attempts to download:

Screenshots:
- default: true
  thumbnails:
  - url:
org/gimp/GIMP/81aa8be6edc018b9d60a2f0cd75bd113/screenshots/image-1_1248x702@1.png
    width: 1248
    height: 702
  source-image:
    url:
org/gimp/GIMP/81aa8be6edc018b9d60a2f0cd75bd113/screenshots/image-1_orig.png
    width: 1920
    height: 1080

The catalog header specifies:
Thus, the screenshot URLs are not being incorrectly constructed by KDE
Discover. They originate directly from Debian's distributed DEP-11 metadata.


5. OFFICIAL APT REPOSITORY STILL DISTRIBUTES AUGUST 2025 METADATA
=================================================================

The local DEP-11 file was downloaded on October 11, 2026.

Its filesystem timestamps show:

Modify: 2025-08-08 16:14:57 -0400
Change: 2026-10-11 15:14:37 -0400
Birth:  2026-10-11 15:14:36 -0400

The catalog header identifies its generation time as August 8, 2025.

To verify whether this was merely a stale local copy, I queried Debian's
official repository directly:

curl -sSI \
'
https://deb.debian.org/debian/dists/trixie/main/dep11/Components-amd64.yml.gz
'

Result:

HTTP/2 200
last-modified: Fri, 08 Aug 2025 20:14:49 GMT
etag: "7ac722-63be039d4a02b"
content-length: 8046370

The remote file's timestamp and size match the locally installed catalog.

Therefore, a freshly updated Debian 13 system is still receiving DEP-11
metadata generated in August 2025.


6. DEBIAN'S APPSTREAM GENERATOR PROVIDES NEWER METADATA
=======================================================

I then checked the catalog distributed directly by Debian's AppStream
generator:

curl -sSI \
'https://appstream.debian.org/data/trixie/main/Components-amd64.yml.gz'

Result:

HTTP/2 200
last-modified: Sat, 12 Sep 2026 14:11:19 GMT
etag: "7b1f4e-65b49c65f8737"
content-length: 8068942

Comparison:

Source                       Last modified   Size
------------------------------------------------------
Official Debian APT repo     2025-08-08      8,046,370 bytes
AppStream generator          2026-09-12      8,068,942 bytes

The AppStream generator has produced substantially newer metadata, but the
stable APT repository continues distributing the older catalog.


7. NEWER METADATA REFERENCES WORKING SCREENSHOTS
================================================

I downloaded the newer catalog directly:

curl -fL \
'https://appstream.debian.org/data/trixie/main/Components-amd64.yml.gz' \
-o /tmp/trixie-appstream-new.yml.gz

Examining its GIMP entry reveals different screenshot paths:

org/gimp/GIMP/c34d2bf00231e1cf30bb916c4bd19be7/screenshots/image-1_orig.png
org/gimp/GIMP/c34d2bf00231e1cf30bb916c4bd19be7/screenshots/image-2_orig.png
org/gimp/GIMP/c34d2bf00231e1cf30bb916c4bd19be7/screenshots/image-3_orig.png
org/gimp/GIMP/c34d2bf00231e1cf30bb916c4bd19be7/screenshots/image-4_orig.png

The directory hash differs from the one distributed through APT:

APT metadata (2025):
81aa8be6edc018b9d60a2f0cd75bd113

AppStream generator (2026):
c34d2bf00231e1cf30bb916c4bd19be7

Testing the newer screenshot URL:

curl -IL --max-time 15 \
'
https://appstream.debian.org/media/trixie/org/gimp/GIMP/c34d2bf00231e1cf30bb916c4bd19be7/screenshots/image-1_orig.png
'

Result:

HTTP/2 200
last-modified: Sat, 12 Sep 2026 14:10:53 GMT
content-length: 1366764
content-type: image/png
server: Apache

The screenshot referenced by the newer metadata exists and is downloadable,
whereas the screenshot referenced by the official APT metadata returns HTTP
404.

This demonstrates a direct relationship between the outdated repository
metadata and the missing screenshots.


8. REPRODUCTION PROCEDURE
=========================

On a Debian 13 system using the official Trixie repositories:

1. Run sudo apt update.
2. Install KDE Discover and AppStream if not already installed.
3. Open Discover and navigate to GIMP.
4. Observe that application information loads, but screenshots are missing.
5. Inspect the GIMP screenshot URLs in the DEP-11 catalog under
/var/lib/apt/lists/.
6. Request one of those URLs using curl and observe HTTP 404.
7. Download the newer catalog from the AppStream generator.
8. Extract its GIMP screenshot URL and observe that it returns HTTP 200.

Alternatively, the underlying metadata discrepancy can be reproduced
without KDE Discover by comparing the two catalog sources and testing their
respective screenshot URLs.


9. SUSPECTED ROOT CAUSE
=======================

The evidence suggests that Debian's AppStream generator continues updating
Trixie metadata and associated screenshot files, while the official Debian
Stable APT repository is not receiving the regenerated DEP-11 catalogs.

As screenshot references change, the older catalog eventually points to
image files that are no longer available.

This appears consistent with the issue described in this bug report.

The primary problem does not appear to be KDE Discover, local DNS, TLS
certificates, or an outdated local cache.


10. REQUEST FOR MAINTAINER INVESTIGATION
========================================

Could the maintainers please investigate whether updated DEP-11 metadata is
being imported into the Debian Stable archive as intended?

In particular:

- Is it expected that Trixie's official APT repository still distributes
DEP-11 metadata generated on August 8, 2025?
- Should the newer catalog generated on September 12, 2026, have been
propagated to the Stable repository?
- Is the apparent lack of synchronization related to the archive import
configuration discussed earlier in this bug?
- Can the newer DEP-11 metadata be published to Stable without requiring a
Debian point release?

I have not manually replaced the system's APT-managed metadata or installed
a local override. The system remains in its standard repository-managed
configuration.

I hope these findings help identify and reproduce the underlying issue.

Thank you for your work on Debian and AppStream.
https://appstream.debian.org/media/trixie/org/gnome/TwentyFortyEight/ff33fadaa7c0dff69bd6e4c6a7b9c8d5/screenshots/image-1_224x240@1.png
'