Package: libgl1-mesa-dri
Version: 20.3.5-1
My journal log shows, among other weird stuff, the following error message:
Mai 10 21:01:20 AnonymizedComputerName gnome-shell[1026]: Running GNOME
Shell (using mutter 42.3) as a Wayland display server
Mai 10 21:01:21 AnonymizedComputerName gnome-shell[1026]: Device
'/dev/dri/card0' prefers shadow buffer
Mai 10 21:01:21 AnonymizedComputerName goa-daemon[1048]: goa-daemon
version 3.38.0 starting
Mai 10 21:01:21 AnonymizedComputerName gnome-shell[1026]: Added device
'/dev/dri/card0' (ast) using atomic mode setting.
Mai 10 21:01:21 AnonymizedComputerName dbus-daemon[962]: [session
uid=119 pid=962] Activating service name='org.gnome.Identity' requested
by ':1.15' (uid=119 pid=1048 comm="/usr/libexec/goa-daemon ")
Mai 10 21:01:21 AnonymizedComputerName gnome-shell[1026]: Device
'/dev/dri/card1' prefers shadow buffer
Mai 10 21:01:21 AnonymizedComputerName dbus-daemon[962]: [session
uid=119 pid=962] Successfully activated service 'org.gnome.OnlineAccounts'
Mai 10 21:01:21 AnonymizedComputerName dbus-daemon[962]: [session
uid=119 pid=962] Successfully activated service 'org.gnome.Identity'
Mai 10 21:01:21 AnonymizedComputerName dbus-daemon[962]: [session
uid=119 pid=962] Successfully activated service
'org.gtk.vfs.GoaVolumeMonitor'
Mai 10 21:01:21 AnonymizedComputerName systemd[920]: Started Virtual
filesystem service - GNOME Online Accounts monitor.
Mai 10 21:01:21 AnonymizedComputerName dbus-daemon[962]: [session
uid=119 pid=962] Activating via systemd: service
name='org.gtk.vfs.GPhoto2VolumeMonitor'
unit='gvfs-gphoto2-volume-monitor.service' requested by ':1.3' (uid=119
pid=955 comm="/usr/libexec/tracker-miner-fs ")
Mai 10 21:01:21 AnonymizedComputerName systemd[920]: Starting Virtual
filesystem service - digital camera monitor...
Mai 10 21:01:21 AnonymizedComputerName dbus-daemon[962]: [session
uid=119 pid=962] Successfully activated service
'org.gtk.vfs.GPhoto2VolumeMonitor'
Mai 10 21:01:21 AnonymizedComputerName systemd[920]: Started Virtual
filesystem service - digital camera monitor.
Mai 10 21:01:21 AnonymizedComputerName dbus-daemon[778]: [system]
Activating via systemd: service name='org.freedesktop.UPower'
unit='upower.service' requested by ':1.37' (uid=119 pid=955
comm="/usr/libexec/tracker-miner-fs ")
Mai 10 21:01:21 AnonymizedComputerName systemd[1]: Starting Daemon for
power management...
Mai 10 21:01:21 AnonymizedComputerName systemd[1]: Started Console Mouse
manager.
Mai 10 21:01:21 AnonymizedComputerName gnome-shell[1026]: Added device
'/dev/dri/card1' (nouveau) using non-atomic mode setting.
Mai 10 21:01:21 AnonymizedComputerName org.gnome.Shell.desktop[1026]:
pci id for fd 9: 1a03:2000, driver (null)
Mai 10 21:01:21 AnonymizedComputerName org.gnome.Shell.desktop[1026]:
MESA-LOADER: failed to open ast: /usr/lib/dri/ast_dri.so: Kann die
Shared-Object-Datei nicht öffnen: Datei oder Verzeichnis nicht gefunden
(search paths /usr/lib/x86_64-linux-gnu/dri:\$${ORIGIN}/dri:/usr/lib/dri)
Mai 10 21:01:21 AnonymizedComputerName org.gnome.Shell.desktop[1026]:
failed to load driver: ast
So MESA-LOADER complains that /usr/lib/dri/ast_dri.so is not found.
This is correct because on my machine, /usr/lib/dri doesn't exist and
ast_dri.so doesn't exist elsewhere. Does my Aspeed chip have no driver?
Should I ever need it a VGA output, don't I get it? My request is to
deal with this error message, ideally, by introducing ast_dri.so into to
Debian (or making MESA-LOADER work without it).