All Qt5 apps fail to launch with a segfault

As an example I am attaching the log from kodi which shows the grave fault
error <general>: GLX Error: vInfo is NULL!

############## Kodi CRASH LOG ###############

################ SYSTEM INFO ################
 Date: Wed 25 Jan 23:33:02 EET 2023
 Kodi Options:
 Arch: x86_64
 Kernel: Linux 6.1.0-2-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.1.7-1 (2023-01-18)
 Release: Debian GNU/Linux
############## END SYSTEM INFO ##############

############### STACK TRACE #################
############# END STACK TRACE ###############

################# LOG FILE ##################

2023-01-25 23:33:00.032 T:48870    info <general>:
-----------------------------------------------------------------------
2023-01-25 23:33:00.032 T:48870    info <general>: Starting Kodi from Debian
(20.0 Debian package version: 2:20.0+dfsg-1). Platform: Linux x86 64-bit
2023-01-25 23:33:00.032 T:48870    info <general>: Using Release Kodi from
Debian x64
2023-01-25 23:33:00.032 T:48870    info <general>: Kodi from Debian compiled
2023-01-21 by GCC 12.2.0 for Linux x86 64-bit version 6.1.4 (393476)
2023-01-25 23:33:00.032 T:48870    info <general>: Running on Debian GNU/Linux
bookworm/sid n/a, kernel: Linux x86 64-bit version 6.1.0-2-amd64
2023-01-25 23:33:00.034 T:48870    info <general>: FFmpeg version/source:
5.1.2-2
2023-01-25 23:33:00.034 T:48870    info <general>: Host CPU: Intel(R) Core(TM)2
Duo CPU     E7300  @ 2.66GHz, 2 cores available
2023-01-25 23:33:00.034 T:48870    info <general>: special://xbmc/ is mapped
to: /usr/share/kodi
2023-01-25 23:33:00.034 T:48870    info <general>: special://xbmcbin/ is mapped
to: /usr/lib/x86_64-linux-gnu/kodi
2023-01-25 23:33:00.034 T:48870    info <general>: special://xbmcbinaddons/ is
mapped to: /usr/lib/x86_64-linux-gnu/kodi/addons
2023-01-25 23:33:00.034 T:48870    info <general>: special://masterprofile/ is
mapped to: /home/george/.kodi/userdata
2023-01-25 23:33:00.034 T:48870    info <general>: special://envhome/ is mapped
to: /home/george
2023-01-25 23:33:00.034 T:48870    info <general>: special://home/ is mapped
to: /home/george/.kodi
2023-01-25 23:33:00.034 T:48870    info <general>: special://temp/ is mapped
to: /home/george/.kodi/temp
2023-01-25 23:33:00.034 T:48870    info <general>: special://logpath/ is mapped
to: /home/george/.kodi/temp
2023-01-25 23:33:00.034 T:48870    info <general>: Webserver extra whitelist
paths:
2023-01-25 23:33:00.034 T:48870    info <general>: The executable running is:
/usr/lib/x86_64-linux-gnu/kodi/kodi.bin
2023-01-25 23:33:00.034 T:48870    info <general>: Local hostname: home
2023-01-25 23:33:00.034 T:48870    info <general>: Log File is located:
/home/george/.kodi/temp/kodi.log
2023-01-25 23:33:00.036 T:48870    info <general>:
-----------------------------------------------------------------------
2023-01-25 23:33:00.039 T:48870    info <general>: loading settings
2023-01-25 23:33:00.050 T:48870    info <general>: special://profile/ is mapped
to: special://masterprofile/
2023-01-25 23:33:00.065 T:48870 warning <CSettingsManager>: missing version
attribute
2023-01-25 23:33:00.066 T:48870 warning <CSettingsManager>: unable to read
value of setting "videolibrary.showunwatchedplots"
2023-01-25 23:33:00.066 T:48870 warning <CSettingsManager>: unable to read
value of setting "videoplayer.autoplaynextitem"
2023-01-25 23:33:00.067 T:48870    info <general>: No settings file to load
(special://xbmc/system/advancedsettings.xml)
2023-01-25 23:33:00.067 T:48870    info <general>: No settings file to load
(special://masterprofile/advancedsettings.xml)
2023-01-25 23:33:00.067 T:48870    info <general>: Default Video Player:
VideoPlayer
2023-01-25 23:33:00.067 T:48870    info <general>: Default Audio Player:
paplayer
2023-01-25 23:33:00.067 T:48870    info <general>: Disabled debug logging due
to GUI setting. Level 0.
2023-01-25 23:33:00.067 T:48870    info <general>: Log level changed to "info"
2023-01-25 23:33:00.067 T:48870    info <general>: CMediaSourceSettings:
loading media sources from special://masterprofile/sources.xml
2023-01-25 23:33:00.076 T:48870    info <general>: creating subdirectories
2023-01-25 23:33:00.077 T:48870    info <general>: userdata folder:
special://masterprofile/
2023-01-25 23:33:00.077 T:48870    info <general>: recording folder:
2023-01-25 23:33:00.077 T:48870    info <general>: screenshots folder:
2023-01-25 23:33:00.088 T:48870    info <general>: Old database found -
updating from version 27 to 33
2023-01-25 23:33:00.287 T:48870    info <general>: Attempting to update the
database Addons33 from version 27 to 33
2023-01-25 23:33:00.466 T:48870    info <general>: CreateAnalytics creating
indices
2023-01-25 23:33:00.604 T:48870    info <general>: Update to version 33
successful
2023-01-25 23:33:00.718 T:48870 warning <general>: CAddonMgr::FindAddons: Addon
'metadata.artists.universal' already present with higher version 4.3.3 at
'/usr/share/kodi/addons/metadata.artists.universal/' - other version 3.7.5 at
'/home/george/.kodi/addons/metadata.artists.universal/' will be ignored
2023-01-25 23:33:00.790 T:48870 warning <general>: CAddonMgr::FindAddons: Addon
'metadata.common.allmusic.com' already present with higher version 3.2.2 at
'/usr/share/kodi/addons/metadata.common.allmusic.com/' - other version 3.2.0 at
'/home/george/.kodi/addons/metadata.common.allmusic.com/' will be ignored
2023-01-25 23:33:00.793 T:48870 warning <general>: CAddonMgr::FindAddons: Addon
'metadata.album.universal' already present with higher version 3.1.4 at
'/usr/share/kodi/addons/metadata.album.universal/' - other version 2.7.5 at
'/home/george/.kodi/addons/metadata.album.universal/' will be ignored
2023-01-25 23:33:00.794 T:48870 warning <general>: CAddonMgr::FindAddons: Addon
'metadata.common.musicbrainz.org' already present with higher version 2.2.4 at
'/usr/share/kodi/addons/metadata.common.musicbrainz.org/' - other version 2.2.1
at '/home/george/.kodi/addons/metadata.common.musicbrainz.org/' will be ignored
2023-01-25 23:33:00.797 T:48870 warning <general>: CAddonMgr::FindAddons: Addon
'metadata.common.theaudiodb.com' already present with higher version 2.0.3 at
'/usr/share/kodi/addons/metadata.common.theaudiodb.com/' - other version 2.0.1
at '/home/george/.kodi/addons/metadata.common.theaudiodb.com/' will be ignored
2023-01-25 23:33:00.799 T:48870 warning <general>: CAddonMgr::FindAddons: Addon
'metadata.common.fanart.tv' already present with higher version 3.6.3 at
'/usr/share/kodi/addons/metadata.common.fanart.tv/' - other version 3.6.0 at
'/home/george/.kodi/addons/metadata.common.fanart.tv/' will be ignored
2023-01-25 23:33:00.923 T:48870    info <general>: CAddonMgr::FindAddons:
audioencoder.kodi.builtin.aac v1.0.2 installed
2023-01-25 23:33:00.923 T:48870    info <general>: CAddonMgr::FindAddons:
audioencoder.kodi.builtin.wma v1.0.2 installed
2023-01-25 23:33:00.923 T:48870    info <general>: CAddonMgr::FindAddons:
game.controller.default v1.0.35 installed
2023-01-25 23:33:00.923 T:48870    info <general>: CAddonMgr::FindAddons:
game.controller.keyboard v1.1.26 installed
2023-01-25 23:33:00.923 T:48870    info <general>: CAddonMgr::FindAddons:
game.controller.mouse v1.0.19 installed
2023-01-25 23:33:00.923 T:48870    info <general>: CAddonMgr::FindAddons:
game.controller.snes v1.0.34 installed
2023-01-25 23:33:00.924 T:48870    info <general>: CAddonMgr::FindAddons:
kodi.binary.global.audioengine v1.1.1 installed
2023-01-25 23:33:00.924 T:48870    info <general>: CAddonMgr::FindAddons:
kodi.binary.global.filesystem v1.1.7 installed
2023-01-25 23:33:00.924 T:48870    info <general>: CAddonMgr::FindAddons:
kodi.binary.global.general v1.0.5 installed
2023-01-25 23:33:00.924 T:48870    info <general>: CAddonMgr::FindAddons:
kodi.binary.global.gui v5.15.0 installed
2023-01-25 23:33:00.924 T:48870    info <general>: CAddonMgr::FindAddons:
kodi.binary.global.main v2.0.2 installed
2023-01-25 23:33:00.924 T:48870    info <general>: CAddonMgr::FindAddons:
kodi.binary.global.network v1.0.4 installed
2023-01-25 23:33:00.924 T:48870    info <general>: CAddonMgr::FindAddons:
kodi.binary.global.tools v1.0.4 installed
2023-01-25 23:33:00.925 T:48870    info <general>: CAddonMgr::FindAddons:
kodi.binary.instance.audiodecoder v4.0.0 installed
2023-01-25 23:33:00.925 T:48870    info <general>: CAddonMgr::FindAddons:
kodi.binary.instance.audioencoder v3.0.0 installed
2023-01-25 23:33:00.925 T:48870    info <general>: CAddonMgr::FindAddons:
kodi.binary.instance.game v3.0.0 installed
2023-01-25 23:33:00.925 T:48870    info <general>: CAddonMgr::FindAddons:
kodi.binary.instance.imagedecoder v3.0.1 installed
2023-01-25 23:33:00.925 T:48870    info <general>: CAddonMgr::FindAddons:
kodi.binary.instance.inputstream v3.2.0 installed
2023-01-25 23:33:00.925 T:48870    info <general>: CAddonMgr::FindAddons:
kodi.binary.instance.peripheral v2.0.0 installed
2023-01-25 23:33:00.925 T:48870    info <general>: CAddonMgr::FindAddons:
kodi.binary.instance.pvr v8.2.0 installed
2023-01-25 23:33:00.926 T:48870    info <general>: CAddonMgr::FindAddons:
kodi.binary.instance.screensaver v2.2.0 installed
2023-01-25 23:33:00.926 T:48870    info <general>: CAddonMgr::FindAddons:
kodi.binary.instance.vfs v3.0.1 installed
2023-01-25 23:33:00.926 T:48870    info <general>: CAddonMgr::FindAddons:
kodi.binary.instance.videocodec v2.0.3 installed
2023-01-25 23:33:00.926 T:48870    info <general>: CAddonMgr::FindAddons:
kodi.binary.instance.visualization v4.0.0 installed
2023-01-25 23:33:00.926 T:48870    info <general>: CAddonMgr::FindAddons:
kodi.resource v1.0.0 installed
2023-01-25 23:33:00.926 T:48870    info <general>: CAddonMgr::FindAddons:
metadata.album.universal v3.1.4 installed
2023-01-25 23:33:00.927 T:48870    info <general>: CAddonMgr::FindAddons:
metadata.artists.universal v4.3.3 installed
2023-01-25 23:33:00.927 T:48870    info <general>: CAddonMgr::FindAddons:
metadata.common.allmusic.com v3.2.2 installed
2023-01-25 23:33:00.927 T:48870    info <general>: CAddonMgr::FindAddons:
metadata.common.fanart.tv v3.6.3 installed
2023-01-25 23:33:00.927 T:48870    info <general>: CAddonMgr::FindAddons:
metadata.common.imdb.com v3.1.4 installed
2023-01-25 23:33:00.927 T:48870    info <general>: CAddonMgr::FindAddons:
metadata.common.musicbrainz.org v2.2.4 installed
2023-01-25 23:33:00.927 T:48870    info <general>: CAddonMgr::FindAddons:
metadata.common.theaudiodb.com v2.0.3 installed
2023-01-25 23:33:00.928 T:48870    info <general>: CAddonMgr::FindAddons:
metadata.common.themoviedb.org v3.1.9 installed
2023-01-25 23:33:00.928 T:48870    info <general>: CAddonMgr::FindAddons:
metadata.generic.albums v1.0.14 installed
2023-01-25 23:33:00.929 T:48870    info <general>: CAddonMgr::FindAddons:
metadata.generic.artists v1.0.14 installed
2023-01-25 23:33:00.929 T:48870    info <general>: CAddonMgr::FindAddons:
metadata.local v1.0.1 installed
2023-01-25 23:33:00.929 T:48870    info <general>: CAddonMgr::FindAddons:
metadata.themoviedb.org v5.1.4 installed
2023-01-25 23:33:00.930 T:48870    info <general>: CAddonMgr::FindAddons:
metadata.themoviedb.org.python v1.3.1+matrix.1 installed
2023-01-25 23:33:00.930 T:48870    info <general>: CAddonMgr::FindAddons:
metadata.tvdb.com v3.0.14 installed
2023-01-25 23:33:00.930 T:48870    info <general>: CAddonMgr::FindAddons:
metadata.tvshows.themoviedb.org.python v1.6.0 installed
2023-01-25 23:33:00.930 T:48870    info <general>: CAddonMgr::FindAddons:
repository.xbmc.org v3.3.1 installed
2023-01-25 23:33:00.931 T:48870    info <general>: CAddonMgr::FindAddons:
resource.images.weathericons.default v1.1.9 installed
2023-01-25 23:33:00.931 T:48870    info <general>: CAddonMgr::FindAddons:
resource.language.af_za v9.0.43 installed
2023-01-25 23:33:00.931 T:48870    info <general>: CAddonMgr::FindAddons:
resource.language.am_et v9.0.40 installed
2023-01-25 23:33:00.931 T:48870    info <general>: CAddonMgr::FindAddons:
resource.language.ar_sa v9.0.43 installed
2023-01-25 23:33:00.931 T:48870    info <general>: CAddonMgr::FindAddons:
resource.language.ast_es v1.0.31 installed
2023-01-25 23:33:00.931 T:48870    info <general>: CAddonMgr::FindAddons:
resource.language.az_az v9.0.34 installed
2023-01-25 23:33:00.931 T:48870    info <general>: CAddonMgr::FindAddons:
resource.language.be_by v9.0.48 installed
2023-01-25 23:33:00.932 T:48870    info <general>: CAddonMgr::FindAddons:
resource.language.bg_bg v9.0.62 installed
2023-01-25 23:33:00.932 T:48870    info <general>: CAddonMgr::FindAddons:
resource.language.bs_ba v9.0.37 installed
2023-01-25 23:33:00.932 T:48870    info <general>: CAddonMgr::FindAddons:
resource.language.ca_es v9.0.44 installed
2023-01-25 23:33:00.932 T:48870    info <general>: CAddonMgr::FindAddons:
resource.language.cs_cz v9.0.64 installed
2023-01-25 23:33:00.932 T:48870    info <general>: CAddonMgr::FindAddons:
resource.language.cy_gb v9.0.42 installed
2023-01-25 23:33:00.932 T:48870    info <general>: CAddonMgr::FindAddons:
resource.language.da_dk v9.0.66 installed
2023-01-25 23:33:00.932 T:48870    info <general>: CAddonMgr::FindAddons:
resource.language.de_de v9.0.68 installed
2023-01-25 23:33:00.933 T:48870    info <general>: CAddonMgr::FindAddons:
resource.language.el_gr v9.0.50 installed
2023-01-25 23:33:00.933 T:48870    info <general>: CAddonMgr::FindAddons:
resource.language.en_au v9.0.38 installed
2023-01-25 23:33:00.933 T:48870    info <general>: CAddonMgr::FindAddons:
resource.language.en_gb v2.0.2 installed
2023-01-25 23:33:00.933 T:48870    info <general>: CAddonMgr::FindAddons:
resource.language.en_nz v9.0.41 installed
2023-01-25 23:33:00.933 T:48870    info <general>: CAddonMgr::FindAddons:
resource.language.en_us v9.0.50 installed
2023-01-25 23:33:00.933 T:48870    info <general>: CAddonMgr::FindAddons:
resource.language.eo v9.0.36 installed
2023-01-25 23:33:00.933 T:48870    info <general>: CAddonMgr::FindAddons:
resource.language.es_ar v9.0.40 installed
2023-01-25 23:33:00.934 T:48870    info <general>: CAddonMgr::FindAddons:
resource.language.es_es v9.0.64 installed
2023-01-25 23:33:00.934 T:48870    info <general>: CAddonMgr::FindAddons:
resource.language.es_mx v9.0.49 installed
2023-01-25 23:33:00.934 T:48870    info <general>: CAddonMgr::FindAddons:
resource.language.et_ee v9.0.57 installed
2023-01-25 23:33:00.934 T:48870    info <general>: CAddonMgr::FindAddons:
resource.language.eu_es v9.0.47 installed
2023-01-25 23:33:00.934 T:48870    info <general>: CAddonMgr::FindAddons:
resource.language.fa_af v9.0.36 installed
2023-01-25 23:33:00.934 T:48870    info <general>: CAddonMgr::FindAddons:
resource.language.fa_ir v9.0.43 installed
2023-01-25 23:33:00.934 T:48870    info <general>: CAddonMgr::FindAddons:
resource.language.fi_fi v9.0.73 installed
2023-01-25 23:33:00.935 T:48870    info <general>: CAddonMgr::FindAddons:
resource.language.fil v1.0.9 installed
2023-01-25 23:33:00.935 T:48870    info <general>: CAddonMgr::FindAddons:
resource.language.fo_fo v9.0.37 installed
2023-01-25 23:33:00.935 T:48870    info <general>: CAddonMgr::FindAddons:
resource.language.fr_ca v9.0.57 installed
2023-01-25 23:33:00.935 T:48870    info <general>: CAddonMgr::FindAddons:
resource.language.fr_fr v9.0.71 installed
2023-01-25 23:33:00.935 T:48870    info <general>: CAddonMgr::FindAddons:
resource.language.gl_es v9.0.47 installed
2023-01-25 23:33:00.935 T:48870    info <general>: CAddonMgr::FindAddons:
resource.language.he_il v9.0.47 installed
2023-01-25 23:33:00.936 T:48870    info <general>: CAddonMgr::FindAddons:
resource.language.hi_in v9.0.34 installed
2023-01-25 23:33:00.936 T:48870    info <general>: CAddonMgr::FindAddons:
resource.language.hr_hr v9.0.52 installed
2023-01-25 23:33:00.936 T:48870    info <general>: CAddonMgr::FindAddons:
resource.language.hu_hu v9.0.60 installed
2023-01-25 23:33:00.936 T:48870    info <general>: CAddonMgr::FindAddons:
resource.language.hy_am v9.0.35 installed
2023-01-25 23:33:00.936 T:48870    info <general>: CAddonMgr::FindAddons:
resource.language.id_id v9.0.46 installed
2023-01-25 23:33:00.936 T:48870    info <general>: CAddonMgr::FindAddons:
resource.language.is_is v9.0.50 installed
2023-01-25 23:33:00.936 T:48870    info <general>: CAddonMgr::FindAddons:
resource.language.it_it v9.0.64 installed
2023-01-25 23:33:00.937 T:48870    info <general>: CAddonMgr::FindAddons:
resource.language.ja_jp v9.0.50 installed
2023-01-25 23:33:00.937 T:48870    info <general>: CAddonMgr::FindAddons:
resource.language.kn_in v1.0.30 installed
2023-01-25 23:33:00.937 T:48870    info <general>: CAddonMgr::FindAddons:
resource.language.ko_kr v9.0.58 installed
2023-01-25 23:33:00.937 T:48870    info <general>: CAddonMgr::FindAddons:
resource.language.lt_lt v9.0.59 installed
2023-01-25 23:33:00.937 T:48870    info <general>: CAddonMgr::FindAddons:
resource.language.lv_lv v9.0.46 installed
2023-01-25 23:33:00.937 T:48870    info <general>: CAddonMgr::FindAddons:
resource.language.mi v9.0.37 installed
2023-01-25 23:33:00.937 T:48870    info <general>: CAddonMgr::FindAddons:
resource.language.mk_mk v9.0.40 installed
2023-01-25 23:33:00.938 T:48870    info <general>: CAddonMgr::FindAddons:
resource.language.ml_in v9.0.30 installed
2023-01-25 23:33:00.938 T:48870    info <general>: CAddonMgr::FindAddons:
resource.language.mn_mn v9.0.35 installed
2023-01-25 23:33:00.938 T:48870    info <general>: CAddonMgr::FindAddons:
resource.language.ms_my v9.0.46 installed
2023-01-25 23:33:00.938 T:48870    info <general>: CAddonMgr::FindAddons:
resource.language.mt_mt v9.0.39 installed
2023-01-25 23:33:00.938 T:48870    info <general>: CAddonMgr::FindAddons:
resource.language.my_mm v9.0.37 installed
2023-01-25 23:33:00.938 T:48870    info <general>: CAddonMgr::FindAddons:
resource.language.nb_no v9.0.47 installed
2023-01-25 23:33:00.938 T:48870    info <general>: CAddonMgr::FindAddons:
resource.language.nl_nl v9.0.58 installed
2023-01-25 23:33:00.939 T:48870    info <general>: CAddonMgr::FindAddons:
resource.language.os_os v1.0.31 installed
2023-01-25 23:33:00.939 T:48870    info <general>: CAddonMgr::FindAddons:
resource.language.pl_pl v9.0.52 installed
2023-01-25 23:33:00.939 T:48870    info <general>: CAddonMgr::FindAddons:
resource.language.pt_br v9.0.66 installed
2023-01-25 23:33:00.939 T:48870    info <general>: CAddonMgr::FindAddons:
resource.language.pt_pt v9.0.47 installed
2023-01-25 23:33:00.939 T:48870    info <general>: CAddonMgr::FindAddons:
resource.language.ro_ro v9.0.49 installed
2023-01-25 23:33:00.939 T:48870    info <general>: CAddonMgr::FindAddons:
resource.language.ru_ru v9.0.64 installed
2023-01-25 23:33:00.939 T:48870    info <general>: CAddonMgr::FindAddons:
resource.language.si_lk v9.0.36 installed
2023-01-25 23:33:00.940 T:48870    info <general>: CAddonMgr::FindAddons:
resource.language.sk_sk v9.0.59 installed
2023-01-25 23:33:00.940 T:48870    info <general>: CAddonMgr::FindAddons:
resource.language.sl_si v9.0.43 installed
2023-01-25 23:33:00.940 T:48870    info <general>: CAddonMgr::FindAddons:
resource.language.sq_al v9.0.38 installed
2023-01-25 23:33:00.940 T:48870    info <general>: CAddonMgr::FindAddons:
resource.language.sr_rs v9.0.47 installed
2023-01-25 23:33:00.940 T:48870    info <general>: CAddonMgr::FindAddons:
resource.language.sr_rs@latin v9.0.39 installed
2023-01-25 23:33:00.940 T:48870    info <general>: CAddonMgr::FindAddons:
resource.language.sv_se v9.0.62 installed
2023-01-25 23:33:00.940 T:48870    info <general>: CAddonMgr::FindAddons:
resource.language.szl v9.0.40 installed
2023-01-25 23:33:00.941 T:48870    info <general>: CAddonMgr::FindAddons:
resource.language.ta_in v9.0.40 installed
2023-01-25 23:33:00.941 T:48870    info <general>: CAddonMgr::FindAddons:
resource.language.te_in v9.0.31 installed
2023-01-25 23:33:00.941 T:48870    info <general>: CAddonMgr::FindAddons:
resource.language.tg_tj v9.0.37 installed
2023-01-25 23:33:00.941 T:48870    info <general>: CAddonMgr::FindAddons:
resource.language.th_th v9.0.41 installed
2023-01-25 23:33:00.941 T:48870    info <general>: CAddonMgr::FindAddons:
resource.language.tr_tr v9.0.58 installed
2023-01-25 23:33:00.941 T:48870    info <general>: CAddonMgr::FindAddons:
resource.language.uk_ua v9.0.48 installed
2023-01-25 23:33:00.941 T:48870    info <general>: CAddonMgr::FindAddons:
resource.language.uz_uz v9.0.35 installed
2023-01-25 23:33:00.942 T:48870    info <general>: CAddonMgr::FindAddons:
resource.language.vi_vn v9.0.46 installed
2023-01-25 23:33:00.942 T:48870    info <general>: CAddonMgr::FindAddons:
resource.language.zh_cn v9.0.59 installed
2023-01-25 23:33:00.942 T:48870    info <general>: CAddonMgr::FindAddons:
resource.language.zh_tw v9.0.64 installed
2023-01-25 23:33:00.942 T:48870    info <general>: CAddonMgr::FindAddons:
resource.timezone v1.0.0 installed
2023-01-25 23:33:00.942 T:48870    info <general>: CAddonMgr::FindAddons:
resource.uisounds.kodi v1.0.1 installed
2023-01-25 23:33:00.942 T:48870    info <general>: CAddonMgr::FindAddons:
screensaver.xbmc.builtin.black v1.0.34 installed
2023-01-25 23:33:00.943 T:48870    info <general>: CAddonMgr::FindAddons:
screensaver.xbmc.builtin.dim v1.0.66 installed
2023-01-25 23:33:00.943 T:48870    info <general>: CAddonMgr::FindAddons:
script.module.pil v5.1.0 installed
2023-01-25 23:33:00.943 T:48870    info <general>: CAddonMgr::FindAddons:
script.module.pycryptodome v3.4.3 installed
2023-01-25 23:33:00.943 T:48870    info <general>: CAddonMgr::FindAddons:
skin.estouchy v3.0.8 installed
2023-01-25 23:33:00.943 T:48870    info <general>: CAddonMgr::FindAddons:
skin.estuary v3.0.10 installed
2023-01-25 23:33:00.943 T:48870    info <general>: CAddonMgr::FindAddons:
visualization.spectrum v20.2.0 installed
2023-01-25 23:33:00.943 T:48870    info <general>: CAddonMgr::FindAddons:
webinterface.default v2.2.33 installed
2023-01-25 23:33:00.944 T:48870    info <general>: CAddonMgr::FindAddons:
xbmc.addon v20.0.0 installed
2023-01-25 23:33:00.944 T:48870    info <general>: CAddonMgr::FindAddons:
xbmc.core v0.1.0 installed
2023-01-25 23:33:00.944 T:48870    info <general>: CAddonMgr::FindAddons:
xbmc.gui v5.16.0 installed
2023-01-25 23:33:00.944 T:48870    info <general>: CAddonMgr::FindAddons:
xbmc.json v13.0.0 installed
2023-01-25 23:33:00.944 T:48870    info <general>: CAddonMgr::FindAddons:
xbmc.metadata v2.1.0 installed
2023-01-25 23:33:00.944 T:48870    info <general>: CAddonMgr::FindAddons:
xbmc.python v3.0.1 installed
2023-01-25 23:33:00.945 T:48870    info <general>: CAddonMgr::FindAddons:
xbmc.webinterface v1.0.0 installed
2023-01-25 23:33:00.949 T:48870    info <general>: Selected Logind/UPower as
PowerSyscall
2023-01-25 23:33:01.031 T:48891    info <general>: Loading
special://xbmc/system/Lircmap.xml
2023-01-25 23:33:01.033 T:48891    info <general>: * Adding remote mapping for
device 'mceusb'
2023-01-25 23:33:01.033 T:48891    info <general>: * Adding remote mapping for
device 'XboxDVDDongle'
2023-01-25 23:33:01.033 T:48891    info <general>: * Adding remote mapping for
device 'Microsoft_Xbox'
2023-01-25 23:33:01.033 T:48891    info <general>: * Adding remote mapping for
device 'PinnacleSysPCTVRemote'
2023-01-25 23:33:01.033 T:48891    info <general>: * Adding remote mapping for
device 'anysee'
2023-01-25 23:33:01.033 T:48891    info <general>: * Adding remote mapping for
device 'iMON-PAD'
2023-01-25 23:33:01.033 T:48891    info <general>: * Adding remote mapping for
device 'Antec_Veris_RM200'
2023-01-25 23:33:01.033 T:48891    info <general>: * Adding remote mapping for
device 'MCE_via_iMON'
2023-01-25 23:33:01.033 T:48891    info <general>: * Adding remote mapping for
device 'TwinHanRemote'
2023-01-25 23:33:01.033 T:48891    info <general>: * Adding remote mapping for
device 'linux-input-layer'
2023-01-25 23:33:01.033 T:48891    info <general>: * Linking remote mapping for
'linux-input-layer' to 'cx23885_remote'
2023-01-25 23:33:01.033 T:48891    info <general>: * Adding remote mapping for
device 'mediacenter'
2023-01-25 23:33:01.033 T:48891    info <general>: * Adding remote mapping for
device 'devinput'
2023-01-25 23:33:01.033 T:48891    info <general>: * Adding remote mapping for
device 'devinput-32'
2023-01-25 23:33:01.033 T:48891    info <general>: * Adding remote mapping for
device 'devinput-64'
2023-01-25 23:33:01.651 T:48870   error <general>: DBus error:
org.freedesktop.DBus.Error.InvalidArgs - No such property “OnLowBattery”
2023-01-25 23:33:01.653 T:48870    info <general>: Selected UPower as
PowerSyscall
2023-01-25 23:33:01.655 T:48870   error <general>: DBus error:
org.freedesktop.DBus.Error.InvalidArgs - No such property “CanSuspend”
2023-01-25 23:33:01.656 T:48870   error <general>: DBus error:
org.freedesktop.DBus.Error.InvalidArgs - No such property “CanHibernate”
2023-01-25 23:33:01.690 T:48870    info <general>: CKeyboardLayoutManager:
loading keyboard layouts from special://xbmc/system/keyboardlayouts...
2023-01-25 23:33:02.012 T:48870    info <general>: Available videomodes
(xrandr):
2023-01-25 23:33:02.012 T:48870    info <general>: Output 'DVI-I-0' has 19
modes
2023-01-25 23:33:02.012 T:48870    info <general>: ID:0x249 Name:1920x1080
Refresh:60.000000 Width:1920 Height:1080
2023-01-25 23:33:02.012 T:48870    info <general>: Pixel Ratio: 1.001116
2023-01-25 23:33:02.012 T:48870    info <general>: ID:0x24a Name:1920x1080
Refresh:74.972504 Width:1920 Height:1080
2023-01-25 23:33:02.012 T:48870    info <general>: Pixel Ratio: 1.001116
2023-01-25 23:33:02.013 T:48870    info <general>: ID:0x24b Name:1680x1050
Refresh:59.954250 Width:1680 Height:1050
2023-01-25 23:33:02.013 T:48870    info <general>: Pixel Ratio: 1.112351
2023-01-25 23:33:02.013 T:48870    info <general>: ID:0x24c Name:1440x900
Refresh:59.887451 Width:1440 Height:900
2023-01-25 23:33:02.013 T:48870    info <general>: Pixel Ratio: 1.112351
2023-01-25 23:33:02.013 T:48870    info <general>: ID:0x24d Name:1280x1024
Refresh:75.024673 Width:1280 Height:1024
2023-01-25 23:33:02.013 T:48870    info <general>: Pixel Ratio: 1.423810
2023-01-25 23:33:02.013 T:48870    info <general>: ID:0x24e Name:1280x1024
Refresh:60.019741 Width:1280 Height:1024
2023-01-25 23:33:02.013 T:48870    info <general>: Pixel Ratio: 1.423810
2023-01-25 23:33:02.013 T:48870    info <general>: ID:0x24f Name:1280x960
Refresh:60.000000 Width:1280 Height:960
2023-01-25 23:33:02.013 T:48870    info <general>: Pixel Ratio: 1.334821
2023-01-25 23:33:02.013 T:48870    info <general>: ID:0x250 Name:1280x720
Refresh:60.000000 Width:1280 Height:720
2023-01-25 23:33:02.013 T:48870    info <general>: Pixel Ratio: 1.001116
2023-01-25 23:33:02.013 T:48870    info <general>: ID:0x251 Name:1152x864
Refresh:75.000000 Width:1152 Height:864
2023-01-25 23:33:02.013 T:48870    info <general>: Pixel Ratio: 1.334821
2023-01-25 23:33:02.013 T:48870    info <general>: ID:0x252 Name:1024x768
Refresh:75.028580 Width:1024 Height:768
2023-01-25 23:33:02.013 T:48870    info <general>: Pixel Ratio: 1.334821
2023-01-25 23:33:02.013 T:48870    info <general>: ID:0x253 Name:1024x768
Refresh:70.069359 Width:1024 Height:768
2023-01-25 23:33:02.013 T:48870    info <general>: Pixel Ratio: 1.334821
2023-01-25 23:33:02.013 T:48870    info <general>: ID:0x254 Name:1024x768
Refresh:60.003841 Width:1024 Height:768
2023-01-25 23:33:02.013 T:48870    info <general>: Pixel Ratio: 1.334821
2023-01-25 23:33:02.013 T:48870    info <general>: ID:0x255 Name:800x600
Refresh:75.000000 Width:800 Height:600
2023-01-25 23:33:02.013 T:48870    info <general>: Pixel Ratio: 1.334821
2023-01-25 23:33:02.013 T:48870    info <general>: ID:0x256 Name:800x600
Refresh:72.187569 Width:800 Height:600
2023-01-25 23:33:02.013 T:48870    info <general>: Pixel Ratio: 1.334821
2023-01-25 23:33:02.013 T:48870    info <general>: ID:0x257 Name:800x600
Refresh:60.316540 Width:800 Height:600
2023-01-25 23:33:02.013 T:48870    info <general>: Pixel Ratio: 1.334821
2023-01-25 23:33:02.013 T:48870    info <general>: ID:0x258 Name:800x600
Refresh:56.250000 Width:800 Height:600
2023-01-25 23:33:02.013 T:48870    info <general>: Pixel Ratio: 1.334821
2023-01-25 23:33:02.013 T:48870    info <general>: ID:0x259 Name:640x480
Refresh:75.000000 Width:640 Height:480
2023-01-25 23:33:02.013 T:48870    info <general>: Pixel Ratio: 1.334821
2023-01-25 23:33:02.013 T:48870    info <general>: ID:0x25a Name:640x480
Refresh:72.808800 Width:640 Height:480
2023-01-25 23:33:02.013 T:48870    info <general>: Pixel Ratio: 1.334821
2023-01-25 23:33:02.013 T:48870    info <general>: ID:0x25b Name:640x480
Refresh:59.940479 Width:640 Height:480
2023-01-25 23:33:02.013 T:48870    info <general>: Pixel Ratio: 1.334821
2023-01-25 23:33:02.013 T:48870    info <general>: CApplication::CreateGUI -
using the x11 windowing system
2023-01-25 23:33:02.013 T:48870    info <general>: Checking resolution 16
2023-01-25 23:33:02.147 T:48870    info <general>: RetroPlayer[RENDER]:
Registering renderer factory for OpenGL
2023-01-25 23:33:02.170 T:48870   error <general>: failed to bind rendering API
2023-01-25 23:33:02.174 T:48870 warning <general>: Visual 0x21 of the window is
not suitable, looking for another one...
2023-01-25 23:33:02.204 T:48870   error <general>: GLX Error: vInfo is NULL!


############### END LOG FILE ################

############ END Kodi CRASH LOG #############

Control: tag -1 upstream wontfix
support current Xorg (only with a ignore version mismatch hack) or
anything else more recent.


Andreas

PS: the 340xx legacy driver package in sid is mainly for supporting
people with old gpu hardware running buster with a current kernel

As a user who is also facing the issue, allow me to disagree with what you say.
First and foremost, the most important reason for a user to keep that driver,
despite its age, is its superiority against nouveau, which is still garbage. I
tested it 2 years ago and I absolutely hated it for all the well known reasons
(poor performance in 3d, non existant hardware decoding for h264 and non
existant power management to name a few).
So yes, I am VERY happy that I can still run it, despite that "hack" for xorg
21+.

Also, the claim "the 340xx legacy driver package in sid is mainly for
supporting
people with old gpu hardware running buster with a current kernel" does not
stand. Buster's latest backported kernel is 5.10, which means it can be built
even with 2021's package for nvidia 340.
Moreover, the driver is patched for every single kernel that reaches unstable,
all the way up to today's 6.1. Since I was one of the few that were opening bug
reports about its compatibility back when the first 5.x kernels were released.
I have to admit I am really happy with all the progress that has been done
since then, so I no longer submit any reports for it

Ontopic now. For starters, the bug's severity should have been set to grave,
because it renders some other apps completely unusable. On my end, the only qt5
apps that are not affected are smplayer and keepassxc. All the remaining ones,
e.g qbittorrent, show something like this in dmesg (strace output available in
attachment).

[  300.175202] qbittorrent[1928]: segfault at 0 ip 0000000000000000 sp
00007ffd323b3548 error 14 in qbittorrent[55b854d8f000+10a000] likely on CPU 0
(core 0, socket 0)
[  300.175225] Code: Unable to access opcode bytes at 0xffffffffffffffd6.

I tried deleting every config file that lied under my ~ and is related to qt5
and launcing the apps as root or with sudo, but nothing changed. What did work
was to substitute libqt5gui5 with its inferior implementation from
libqt5gui5-gles and my qt5 apps started working again. Please not that the
above does not affect qt6 apps.

And yesterday I got the upgrade to kodi 20, which fails to launch completely
with "GLX Error: vInfo is NULL!". Kodi 19 was working perfectly when I used it
a few hours before. For that issue, not even the kodi devs have an answer, but
we all know it is related to some gl lib not loading. Here is a coredump debug
if you want to check
https://paste.debian.net/1268410/

And all that happened after the upgrade to 6.1 AND the driver's update to the
-17 version, which the one that made it compatible with 6.1. There were ZERO
issues 1 month ago with 6.0, so I reinstalled 6.0 from snapshot.debian.org, but
since the driver dkms builds gets the same patches, the issues remained. If I
knew how to disable that last patch, I would give it a try, but I don't know.
Moreover, the aur's page for nvidia 340 (the place I always check first for
patches) lists no new patch for 6.1, which means that maybe it can be built
without one.

That's all for today. I hope someone finds something helpful above. If any
other logs are needed, please tell me and I will post them.

p.s. I have A LOT of work to do with kodi now that a new version is relased, so
I really want it to be fixed.

libc6-dbgsym, kodi-dbgsym might make the backtrace more informative.

No patches are needed for 6.1, only for 6.2.

The patch should have zero impact on versions before, but then again
it's only compile tested ... The patch is made by me and not backported
from an existing upstream release since there is no release yet
containing corresponding fixes. (IIRC, the problematic code path is only
present up to version 470, and there were only new 525 releases so far
where I took the second part of the 6.2 support from - not needed for 340xx)

In dkms.conf there is a list of patches, remove the 0042 patch from that
list. Or just get -16 from snapshot.d.o.


Andreas

Nonsense, I was already a bit ahead in time...
The 6.2 patch is so far only in git. -17 *does* bring fixes for 6.1.

A significant change in -17 over -16 was the replacement of various
(actually 8) acpi related patches backported from multiple versions with
one backported from the last 390xx release.
version from -17 to get support for 6.1


Andreas

PS: I can only check that the module builds, I cannot test it.

Thank you for all that info.
Please allow me to check the -dbgsym packages and post a new strace the
following days. It is something new for me and I will probably make a mess when
trying for the first time.
As for the patches, there is no 0042 patch, neither as a file from nvidia-
legacy-340xx-kernel-dkms, nor as text inside /usr/src/nvidia-
legacy-340xx-340.108/dkms.conf, they both stop at 0041.

As for getting the -16 version from snapshot.d.o. I think it will be hard to
get all the correct packages that are derived from its source because they are
way too many! For instance, I now have 17 packages that are built from nvidia
340 sources!
Compare that to the kernels... 4 packages (image, headers, headers-common and
one more) and you will understand.

Yep, 0042 is for Linux 6.2 and currently only in sid.

You should only need the -dkms package in version -16, everything else
can stay at -17. Sorry I wasn't clear about that.


Andreas

Goodmorning. Before I start, I would like to say that yesterday I completely
missed message #27 above and that I am really sorry for that useless wall of
text that reportbug adds to whatever I post.

So, I tested -16 and dkms simply fails to build the modules for 6.1 with it. I
have attached the make.log in case someone wants to have a look. This means
that the -17 version is mandatory for 6.1.
I respect the effort that you put in keeping this package in the repo, but
allow me to say that there is a big difference between something that compiles
successfully with a patch and something that works on all conditions. And right
now, it does not work for qt5 and kodi. And there is no workaround for kodi!
How about adding that 0042 patch to nvidia 340?

As for the debug packages for kodi and libc6, I can not find the packages you
suggested. The closest ones I can find are libc6-dbg and kodi-bin-dbgsym.
Kodi's only shows up in packages.debian.org and not in apt's search. Likewise,
I can not find any debug packages for qt5. Also, the LIBGL_DEBUG=verbose
parameter that woud supposedly give more info on gl stuff does not seem to do
anything on my end.

How can I install 6.0 alongside -16 to test if it works with qt5 5.15.8 and
kodi 20? Installing 6.0 is easy, installing -16 is easy too. The problem is
that when I install -16, with 6.0 already installed, dkms tries to build the
module for 6.1, fails and does not continue for 6.0!

I am looking for an app that is built with the same toolkit as kodi so as to
test it too. I thought it was built on sdl, so I tried retroach which uses it
too, but retroarch launches fine. I have no roms to play with it, so I can not
test it further.

And since I did not mention it earlier, this is the bigger picture of the issue
for me. Right now, debian is on freeze for bookworm (debian 12), which will
probably be released in summer or autumn. All this time, and because 6.1 is an
lts kernel, there will be no upgrades to the kernel itself. This means that if
6.2 will be released e.g. next month, it won't reach in the repo and the next
kernel that will reach it will probably be 6.4 or 6.5. In turn, this means
someone with nvidia 340 has to face 6+ months with broken qt5 apps and a
broken... whatever that gl lib kodi 20 needs to work.
Yes, I know that this is the nature of unstable, but that is a lot of time,
especially for something that was working perfectly fine a few weeks ago (I am
counting from the day 6.1 reached unstable). Or a month ago, if you count when
-17 reached the repo.

First of all, the title should be "gl related apps fail to launch" and let me
explain why.

I tried libreelec 11 beta 1 which came out a few days ago. It uses kernel 6.1,
nvidia 340 and nvidia is definitely used for my card because I can check it in
lspci -k.
Kodi 20 works fine and it even has vdpau decoding. And, as seen here, it uses
no extra patch for 6.1
https://github.com/LibreELEC/LibreELEC.tv/tree/master/packages/x11/driver/xf86-video-
nvidia-legacy/patches

Back on debian, I removed kodi after 10+ years of usage, because it does not
work at all, and reinstalled the gles vesion of libqt5gui5 to restore the
functionality on my qt5 apps. I also installed kitty, a terminal which uses
opengl for its ui, and it fails to launch too.

So, what if something is broken on the kernel's side, assuming that the last
patch for nvidia 340 is good?

Did you try nvidia-legacy-340xx-kernel-dkms -16 (get it from
snapshot.d.o) with only the use-nv-kernel-ARCH.o_binary.patch patch
replaced by the version from -17 to get support for Linux 6.1?
That gives you again the older set of acpi patches.
If that works I'll look again into the acpi patches and the difference
between the two sets.
There is no need to replace any other package besides the -dkms one for
these tests.

Andreas

Please help me on that...
I have already backed up the patch file on my dekstop. If I install -16 from
snapshot.d.o, dkms will rebuild the driver right after apt installs it and it
will fail. I will then move the patch to the right folder, replacing the one
from -16. How will I force dkms to rebuild it after that?
Also, I definitely don't want it to build a faulty driver and debian to fail
reaching the desktop on next boot.

Ok I just did it, but nothing changed. In detail:
- I installed -16 from snapshot
- I let dkms fail to build the driver and apt/dpkg with its failed exit status
- I moved the backed up file back to its original place
- I ran "dkms install nvidia-legacy-340xx/340.108 --force" and it did build the
driver successfully
- I removed kitty... so as to have something to install because I do not know
how to force dpkg continue a failed install
- I installed kitty again and dpkg retried building the driver and succeeded
this time
- I rebooted and ran kitty, but the issue is still there
And after all that I reinstalled -17 :'(

Since the package installation failed, you can just resume that with
dpkg --configure --pending

Otherwise, you can also invoke dkms manually:

dkms build nvidia-legacy-340xx/340.108 [--force] [-k 6.1.0-3-amd64]
dkms install nvidia-legacy-340xx/340.108 [--force] [-k 6.1.0-3-amd64]
dkms status nvidia-legacy-340xx/340.108 [-k 6.1.0-3-amd64]

The kernel flag (-k ..., please use the correct kernel for your machine,
the current kernel in sid would be 6.1.0-3-amd64) is optional if you
just want to target the running kernel version (that would be what
'uname -r' outputs).

;-)

Andreas

Thanks for testing. So it's maybe the kernel module ...

Do you remember the last working configuration?


Andreas

Sorry but no, I can not trace it to something specific. Everything was working
fine on 6.0 and -16, but they are like 2 months old now. I have very few qt
apps and I rarely use most of them. For instance, I use qbittorrent or rclone-
browser almost once a month. I use keepassxc more, but it is not affected by
the issue.

When I noticed that the qt5 apps were not working, I thought it was because of
the transition to 5.15.8, but, judging from the above "intervals" on my usage,
qt5 might have been on 5.16.x back then.
As for kodi, I was waiting for the update to v20 for like a week and when it
finally came, kodi could not launch! While on v19, which had no issue, I was
launching kodi once every like 10 days. And the last time I launched kodi 19
was right before the upgrade to 20.
If you show me how to use the dbg stuff for kodi and libc6, maybe a log can
provide you with better info.

According to these reports that come from ubuntu, mint and arch, kodi 20 has
the same issue with the nvidia 340 driver, regardless of kernel and xorg
version. Thus, I think it can now be ignored when troubleshooting the issue
mentioned here.

https://forum.kodi.tv/showthread.php?tid=371747
https://github.com/xbmc/xbmc/issues/22491
https://aur.archlinux.org/packages/nvidia-340xx#comment-900519

The only thing I was thinking about testing was
* going back to a 6.0 kernel (you may still have it installed?,
otherwiese get linux-image-..., linux-headers-..., and dependencies from
snaphot.d.o)
* downgrading the -dkms package to -16 maybe adding the 6.1 patch from -17
* downgrading kodi to 19

That should be your previously working setup, with the difference of a
lot of libraries (e.g. Qt) being at a newer version now - if that no
longer works, it is to blame on some other library.

But we can probably just say "R.i.P. 340xx driver."


Andreas

Please excuse me if I have already said anything of the following and I am now
repeating myself. I have so much in my mind that sometimes I forget what I said
a couple of days ago. Good thing some of them are written down on bug reports
and forums.

- I tried 6.0 with -17 the day I noticed the issue with qt5, but the issue
remained. Qt5 was probably at v5.18.7 back then and I waited for the migration
to v5.18.8 to complete, thus moving all its related packages to testing.
- Didn't we try downgrading to -16 and adding a patch from -17 (I can not
remember its name) last week? I remember asking how to make dkms force-build
modules...
- There is no way to install kodi 19 now. Debian did not have that version on
testing/unstable for months and dmo has no equivalend of snapshot.d.o.

In other news, I tried kitty's latest static binary from its github page and it
runs just fine, reporting these when the --debug-rendering or --debug-gl
parameter is used

$ ./kitty --debug-rendering
GL version string: '3.3.0 NVIDIA 340.108' Detected version: 3.3
ignoreboth or ignorespace present in bash HISTCONTROL setting, showing running
command in window title will not be robust

I am looking for other gl apps (not games!) to try. As for kodi, I am pretty
sure it looks for some gl-related variable at launch and the system fails to
provide it with one, so it returns that null output in its log and does not
start.

Some manjaro user from github found a solution for kodi v20. Launching it like
so makes it work, so this probably means that kodi v20, unlike v19, does not
detect the library properly.

LD_PRELOAD=/usr/lib/x86_64-linux-gnu/nvidia/libGL.so.1 kodi

This workaround does not work for qt5 apps and kitty, as they still pop the
same error.

On the other hand, I tried amoeba, an opengl visualization thingy, and works
with no issues or workarounds.

Control: tag -1 upstream wontfix

That workaround is very helpful for understanding the problem.
Thanks for digging it out.

The 340 legacy driver predates libglvnd and ships a monolithic
libGL.so.1. With libglvnd libGL.so.1 has been split into libOpenGL.so.0
and libGLX.so.0, all three are being just dispatch libraries (instead of
actual implementations) that forward the OpenGL etc. calls to the
corresponding vendor implementations.
While it worked in the past to replace the system libGL.so.1 (from
libglvnd) with the nvidia provided one, new application versions may
have moved on to expect a libglvnd based environment ...

Just checked ... kodi 20 is linked against libGLX.so.0 and libGL.so.1,
while kodi 19 was only linked against libGL.so.1

Starting kodi 20 with the nvidia legacy 340xx driver installed gets you
two halves of two different OpenGL implementations: libGLX.so.0
(libglvnd) which uses the MESA implementation and libGL.so.1 from nvidia
- of course that mixture does not work. As libGLX.so.0 is a subset of
libGL.so.1 preloading the nvidia libGL.so.1 gets you lucky here because
it overrides the symbols from libGLX.so.0 and you are afterwards running
with only one consistent implementation.
For other applications this does not seem to work since not all
entrypoints can be redirected to the nvidia libGL.so.1 - perhaps because
there are some symbols being used that didn't even exist in the old
days. Could it be that Qt5 now makes use of Wayland, and that does not
work at all with a legacy libGL.so.1 ?

That seems to be another indicator that the breakage is unrelated to the
kernel module but that the OpenGL world has moved on, assuming a
libglvnd based setup.

In bookworm:

# apt-cache rdepends libopengl0 | wc -l
68
# apt-cache rdepends libglx0 | wc -l
43
# apt-cache rdepends libgl1 | wc -l
509
# apt-cache rdepends libwayland-server0 | wc -l
50
# apt-cache rdepends libwayland-client0 | wc -l
153

Btw, kitty uses wayland (but already in bullseye).
And libqt6opengl6 depends on libopengl0 ...

In bullseye:

# apt-cache rdepends libopengl0 | wc -l
39
# apt-cache rdepends libglx0 | wc -l
31
# apt-cache rdepends libgl1 | wc -l
540
# apt-cache rdepends libwayland-server0 | wc -l
39
# apt-cache rdepends libwayland-client0 | wc -l
91

Andreas

Thank you for the clarifications. No offence, but as you described it, this is
practically "planned obsolescence in the opensouce world". Ok, the 340 driver
is old and it does not have a libglx. But its functionality is provided by its
libgl, so why can't we make a symlink of that libgl for libglx?
Also, why should I have any mesa lib installed since I do not use mesa for my
gpus needs?

About libglx.
The 390 is the oldest supported driver that does have libglx, so one could
upgrade its gpu to one that supported by 390. The problem is that nvidia
gt710/730, the lowest end gpu supported by it and has been around for ~10 years
now, costs 50+ euros new, which is unacceptable for a low end hardware of that
age!

Nouveau on the other hand is trash and with its devs focusing mostly on support
for newer cards (on which someone has to be crazy to use nouveau because it
lacks powersaving abilities), I will be long gone before it fully supports any
card that the legacy drivers do for years now. The word "lacking" is too little
to describe nouveau compared to nvidia.

And yes, I consider powersaving to be a very important feature of a driver. I
owned an ati 3850 back in the days of fglrx, which was the worst driver ever.
Back then, debian "had to" update xorg to a new version which was incompatible
with fglrx. That left me with radeon as the only option for the card, which was
at a very early stage and could not do powersaving at that time, so it simply
died ~2 months later from heat issues. I switched to nvidia, with the nvidia as
a driver, and I never looked back since.

To sum up, all this makes it a lose-lose situation for nvidia 340 users :(

I contacted an arch user who still uses nvidia 340 from aur and, as he mentions
in the comments, there is no issue with qt5 apps and nvidia 340 there.
I do not know how arch builds qt5, or if it builds the -gles variant, but I
think someone with the relevant knowledge should check the patches there in
case they patch something differently.

In other news, gtk4 will bring more gl related issues as it seems. Pictured is
blackbox-terminal, a gtk4 app and that huge black rectangle around the menu is,
supposedly, where its shadow would be. Launching it from a terminal pops these
errors

$ blackbox-terminal
Gsk-Message: 11:43:02.022: Failed to realize renderer of type 'GskGLRenderer'
for surface 'GdkX11Toplevel': Compilation failure in shader.
Source Code:   1| #version 100

(140+ lines of source code here)

Error Message:
0(30) : error C7551: OpenGL first class arrays require #version 120
0(43) : error C7551: OpenGL first class arrays require #version 120
0(120) : error C7551: OpenGL first class arrays require #version 120

Honest question to the maintainers, and to the qt5 maintainers too:

What if someone wants to install/run a package that explicitly depends on
libqt5gui5?
I wanted to try corectrl that reached the repo a few days ago, but installing
it removes the -gles version of the above lib, thus breaking all my installed
qt5 apps.

p.s. I would not care for corectrl if the maintainer of cpupower-gui had
updated the package in order to fix both its open bugs. But it will remain
abandoned as it seems.

Kodi, with today's release of 20.2, fixed the gl library issue with this commit
here
https://github.com/xbmc/xbmc/pull/23226

In other news, a few days ago, qbittorrent became my first qt5 app to migrate
to qt6 and it just worked, without any workarounds or extra -gles packages.
So, can a patch like the one for kodi be applied to qt5? I am mentioning again
that arch does not have a seperate -gles package for qt5, so a single lib that
works everywhere should be possible.

Control: reopen -1
to support last century's technology (and therefore probably be unable
to draw full power out of todays technology).

But if all that kodi did is linking against libGL instead of (the
subset) libGLX, maybe we can just replace libGLX.so.1 with a link to
libGL.so.1 s.t. we always end in the same implementation regardless of
the entry point being used ...

Could you try

   ln -sf libGL.so.1 /usr/lib/x86_64-linux-gnu/libGLX.so.0

(assuming amd64) and see if that fixes Qt5 operation? Or breaks other stuff?

Note: this change is only active until you install/upgrade some package,
i.e. something runs ldconfig. (You can also run ldconfig manually to
restore the original link.)


Andreas

Last century's? The tesla (nv50) family was release near the end of the 2010's
decade and it, luckily, had full support by nvidia until the end of 2019! And
since then, it is the community who is keeping it alive with patches for all
recent kernels and xorg 21+.
I am sure no one would care if nouveau was good enough to replace it, but it
isn't and, as it seems, it won't even be by the end of this decade! Sadly, the
features matrix here tells less than half the story about it. Moreover, I am
also glad that kodi's issue made more people try nouveau and judge by
themselves how lacking it is, even for stuff that we take for granted today.
https://nouveau.freedesktop.org/FeatureMatrix.html

But enough with the rant. I want to try what you suggested with the symlink,
but I want to know the procedure to undo it. Btw, the file is already symlinked
to some other lib

$ file /usr/lib/x86_64-linux-gnu/libGLX.so.0
/usr/lib/x86_64-linux-gnu/libGLX.so.0: symbolic link to libGLX.so.0.0.0

That lib is part of mesa's libglx0, which brings me to another serious question
I had forgotten for almost a decade. If the system does not use mesa's libs for
anything, because it uses nvidia's libs, why must it have them installed?

I won't mention again that it does not happen on arch... but I think you can
take some ideas on how arch builds qt5, or at least built it like you do for
qt6 which just works.
Last but not least, arch does not install mesa's stuff on systems with nvidia
drivers.

binaries and libraries needing GLX), libGLX.so.0.0.0 the actual filename.

To restore the original link (as ldconfig would do):
ln -sf libGLX.so.0.0.0 /usr/lib/x86_64-linux-gnu/libGLX.so.0

Andreas

If GLVND is used (e.g. all nvidia drivers newer than the 340 series),
libGL.so.1 is no longer the implementation, but just a dispatch library,
and no more replacement of the system libGL.so.1 is needed.
The actual implementations are in
   libglx-{nvidia,nvidia-legacy*,nvidia-tesla*}0
which can coexist with libglx-mesa0.

Things are much easier after the 340 series ...

Pre-GLVND monolithic GL is only used by a certain proprietary EoL
driver, thus nobody is considering that any more when building software.
Similarily software that doesn't build with gcc-12 or that requires
python2 gets kicked out unless someone volunteers to port it to current
compiler/python interpreter versions (something that cannot happen to
the sourceless nvidia 340 driver).


Andreas

Did you already find some time to test this?

Andreas

First and foremost, sorry for not replying earlier and for not testing the glx
symlink as proposed. The storms, the floods and the power outages that happened
here the first days of September caused enough damage to my hardware that
forced me to make more changes in those 2 weeks than in my entire time with
nvidia, which is more than 10 years.
Long story short, my 9500 died completely and I had to replace it with an ati
6450 that a friend gave me.

If you really want me to test the symlinks solution, I can ask for a gt210, but
I won't reach me before the Xmas holidays.

In other news, the ts informed me that 340 can not be built with kernel 6.5 of
unstable. I would help him file a new bug report, but I no longer have 340
installed.

Anyway, the patch is here
https://github.com/archlinux-
jerry/nvidia-340xx/blob/master/0014-kernel-6.5.patch

p.s. I thought it would be patched alongside 390 and 470 which were patched for
6.5 a month ago.

Sorry to hear that.

I had a patch ready since then, but since 6.5 was only in experimental I
wanted to wait for feedback on the Qt GLX test before I implement that
GLX hack properly. Uploaded now without any GLX changes ;-)

So I'll wait for someone still actively using such an old card with Qt
apps to do these (and maybe some further) tests.


Andreas

The ts contacted me and said that the symlink does not work.

Since last time, we had another, bigger flood that caused even more damage, and
I do not know if I will have the gt210 by Christmas so as to test it, as I had
promised last time.