Bug#1052376: lxpanel: no longer obeys its geometry settings
Package: lxpanel Version: 0.10.2.rc1-1 Followup-For: Bug #1052376 X-Debbugs-Cc: pitsior...@outlook.com Since there is no interest from the maintainers in fixing a 6+ month old grave bug, I want to ask. Has anyone moved away from lxpanel or even lxde? I would switch to lxqt, but lxqt is one major version behind in debian (or 2, if you count the qt6-based lxde 2.0 which was released a week ago). Knowing that lxde, as a project, is not that actively developed from upstrean, that gtk3 migration of its apps should not have happened in the first place. In arch, they still build lxpanel with gtk2 and even pcmanfm has a seperate package for its gtk3 version. -- System Information: Debian Release: trixie/sid APT prefers testing APT policy: (990, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 6.6.15-amd64 (SMP w/2 CPU threads; PREEMPT) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) Versions of packages lxpanel depends on: ii libasound2 1.2.10-3 ii libc62.37-15 ii libcairo21.18.0-1+b1 ii libcurl3-gnutls 8.5.0-2 ii libfm-gtk3-4 1.3.2-4 ii libfm-modules1.3.2-4 ii libfm4 1.3.2-4 ii libgdk-pixbuf-2.0-0 2.42.10+dfsg-3+b1 ii libglib2.0-0 2.78.4-1 ii libgtk-3-0 3.24.41-1 ii libiw30 30~pre9-16+b1 ii libkeybinder-3.0-0 0.3.2-1.1+b1 ii libmenu-cache3 1.1.0-1.1+b1 ii libpango-1.0-0 1.52.0+ds-1 ii libwnck-3-0 43.0-3 ii libx11-6 2:1.8.7-1 ii libxkbfile1 1:1.1.0-1 ii libxml2 2.9.14+dfsg-1.3+b2 ii lxmenu-data 0.1.5-2.1 ii lxpanel-data 0.10.2.rc1-1 Versions of packages lxpanel recommends: ii alacritty [x-terminal-emulator] 0.12.2-2+b2 ii dunst [notification-daemon] 1.9.2-1 ii libnotify-bin 0.8.3-1 ii notification-daemon 3.20.0-4+b1 pn pavucontrol | gnome-alsamixer ii rxvt-unicode [x-terminal-emulator] 9.31-3 ii xkb-data2.41-2 Versions of packages lxpanel suggests: ii brave-browser [www-browser] 1.65.114 ii chromium [www-browser] 123.0.6312.105-1~deb13u1 ii firefox [www-browser]123.0-1 -- no debconf information
Bug#1052376: lxpanel: no longer obeys its geometry settings
Package: lxpanel Version: 0.10.2.rc1-1 Followup-For: Bug #1052376 X-Debbugs-Cc: pitsior...@outlook.com Judging from the infrequient updates the package gets in the last couple of years, I think that it will be fixed after the freeze for debian 13, because it must be sorted out as a grave but. And all that assuming that they get will the source from lxde-continued mentioned above. If that does not happen, it will probably be removed from the repo. -- System Information: Debian Release: trixie/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 6.5.0-5-amd64 (SMP w/2 CPU threads; PREEMPT) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) Versions of packages lxpanel depends on: ii libasound2 1.2.10-3 ii libc62.37-15~deb13u1 ii libcairo21.18.0-1+b1 ii libcurl3-gnutls 8.5.0-2 ii libfm-gtk3-4 1.3.2-4 ii libfm-modules1.3.2-4 ii libfm4 1.3.2-4 ii libgdk-pixbuf-2.0-0 2.42.10+dfsg-3 ii libglib2.0-0 2.78.3-2 ii libgtk-3-0 3.24.40-2 ii libiw30 30~pre9-16+b1 ii libkeybinder-3.0-0 0.3.2-1.1 ii libmenu-cache3 1.1.0-1.1 ii libpango-1.0-0 1.51.0+ds-4 ii libwnck-3-0 43.0-3 ii libx11-6 2:1.8.7-1 ii libxkbfile1 1:1.1.0-1 ii libxml2 2.9.14+dfsg-1.3+b2 ii lxmenu-data 0.1.5-2.1 ii lxpanel-data 0.10.2.rc1-1 Versions of packages lxpanel recommends: ii alacritty [x-terminal-emulator] 0.12.2-2+b1 ii dunst [notification-daemon] 1.9.2-1 ii libnotify-bin 0.8.3-1 ii notification-daemon 3.20.0-4+b1 pn pavucontrol | gnome-alsamixer ii rxvt-unicode [x-terminal-emulator] 9.31-2 ii xkb-data2.38-2 Versions of packages lxpanel suggests: ii brave-browser [www-browser] 1.62.156 ii chromium [www-browser] 121.0.6167.139-1 ii firefox [www-browser]122.0-1 -- no debconf information
Bug#1059782: mesa-vdpau-drivers: Upgrade to 23.3.* breaks video rendering in tkinter
Package: mesa-vdpau-drivers Followup-For: Bug #1059782 X-Debbugs-Cc: pitsior...@outlook.com I know that mesa 24 will fix the issue, and I know it has been packaged in experimental, since I first noticed my videos showing black with vaapi, 1+ week ago. Sadly, mesa is a core component of the os, like systemd, policykit, or the kernel, so I won't risk installing a version that is has not even reached stable from upstream! This is one of the reasons I am on testing and not on unstable. Having said that, I noticed that mesa 24 was released as stable today, so I will wait until it reaches unstable at the very least before updating it. Last but not least, I will try and contact any arch user who was affected by the same issue so as to know if their patch actually solved it. -- System Information: Debian Release: trixie/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 6.5.0-5-amd64 (SMP w/2 CPU threads; PREEMPT) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) Versions of packages mesa-vdpau-drivers depends on: ii libc62.37-14 ii libdrm-amdgpu1 2.4.120-1 ii libdrm-nouveau2 2.4.120-1 ii libdrm-radeon1 2.4.120-1 ii libdrm2 2.4.120-1 ii libelf1 0.190-1+b1 ii libexpat12.5.0-2+b2 ii libgcc-s113.2.0-10 ii libllvm171:17.0.6-5 ii libstdc++6 13.2.0-10 ii libvdpau11.5-2 ii libx11-xcb1 2:1.8.7-1 ii libxcb-dri2-01.15-1 ii libxcb-dri3-01.15-1 ii libxcb-present0 1.15-1 ii libxcb-sync1 1.15-1 ii libxcb-xfixes0 1.15-1 ii libxcb1 1.15-1 ii libxshmfence11.3-1 ii libzstd1 1.5.5+dfsg2-2 ii zlib1g 1:1.3.dfsg-3+b1 mesa-vdpau-drivers recommends no packages. mesa-vdpau-drivers suggests no packages.
Bug#1059782: mesa-vdpau-drivers: Upgrade to 23.3.* breaks video rendering in tkinter
Package: mesa-vdpau-drivers Followup-For: Bug #1059782 X-Debbugs-Cc: pitsior...@outlook.com Sadly, I do not have a gitlab account. But I think that the issue is discussed here https://gitlab.freedesktop.org/mesa/mesa/-/issues/10468 Below is the output of vaapi-info. Please notice the first lines which match mpv's log. This is what vainfo outputs since ever, there is nothing wrong with it (= vaapi), e.g. a missing file, it works (worked) fine. $ vainfo libva info: VA-API version 1.20.0 libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/r600_drv_video.so libva info: Found init function __vaDriverInit_1_20 libva info: va_openDriver() returns 0 vainfo: VA-API version: 1.20 (libva 2.12.0) vainfo: Driver version: Mesa Gallium driver 23.3.4-1 for AMD CAICOS (DRM 2.50.0 / 6.5.0-5-amd64, LLVM 17.0.6) vainfo: Supported profile and entrypoints VAProfileMPEG2Simple: VAEntrypointVLD VAProfileMPEG2Main : VAEntrypointVLD VAProfileVC1Simple : VAEntrypointVLD VAProfileVC1Main: VAEntrypointVLD VAProfileVC1Advanced: VAEntrypointVLD VAProfileH264ConstrainedBaseline: VAEntrypointVLD VAProfileH264Main : VAEntrypointVLD VAProfileH264High : VAEntrypointVLD VAProfileH264High10 : VAEntrypointVLD VAProfileNone : VAEntrypointVideoProc Anyway, if the bug reports are correct, this only applies to h264 as it seems and I have no h265 (or even mpeg2) files or streams to test! I just tried these, which are h265 and they played fine... but my card does not do vaapi for h265, so I assume mpv just plays them with xv. https://www.libde265.org/downloads-videos/ -- System Information: Debian Release: trixie/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 6.5.0-5-amd64 (SMP w/2 CPU threads; PREEMPT) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) Versions of packages mesa-vdpau-drivers depends on: ii libc62.37-14 ii libdrm-amdgpu1 2.4.120-1 ii libdrm-nouveau2 2.4.120-1 ii libdrm-radeon1 2.4.120-1 ii libdrm2 2.4.120-1 ii libelf1 0.190-1+b1 ii libexpat12.5.0-2+b2 ii libgcc-s113.2.0-10 ii libllvm171:17.0.6-5 ii libstdc++6 13.2.0-10 ii libvdpau11.5-2 ii libx11-xcb1 2:1.8.7-1 ii libxcb-dri2-01.15-1 ii libxcb-dri3-01.15-1 ii libxcb-present0 1.15-1 ii libxcb-sync1 1.15-1 ii libxcb-xfixes0 1.15-1 ii libxcb1 1.15-1 ii libxshmfence11.3-1 ii libzstd1 1.5.5+dfsg2-2 ii zlib1g 1:1.3.dfsg-3+b1 mesa-vdpau-drivers recommends no packages. mesa-vdpau-drivers suggests no packages.
Bug#1059782: mesa-vdpau-drivers: Upgrade to 23.3.* breaks video rendering in tkinter
Package: mesa-vdpau-drivers Followup-For: Bug #1059782 X-Debbugs-Cc: pitsior...@outlook.com So, 23.3.4 reached testing today and the problem is still there. As expected, it is not an upstream issue, so can the maintainer have a look at the forementioned patch and correct the package? If it helps, here is a verbose mpv log playing a local file and showing nothing but black https://paste.debian.net/hidden/55cf4d0f/ -- System Information: Debian Release: trixie/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 6.5.0-5-amd64 (SMP w/2 CPU threads; PREEMPT) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) Versions of packages mesa-vdpau-drivers depends on: ii libc62.37-14 ii libdrm-amdgpu1 2.4.120-1 ii libdrm-nouveau2 2.4.120-1 ii libdrm-radeon1 2.4.120-1 ii libdrm2 2.4.120-1 ii libelf1 0.190-1+b1 ii libexpat12.5.0-2+b2 ii libgcc-s113.2.0-10 ii libllvm171:17.0.6-5 ii libstdc++6 13.2.0-10 ii libvdpau11.5-2 ii libx11-xcb1 2:1.8.7-1 ii libxcb-dri2-01.15-1 ii libxcb-dri3-01.15-1 ii libxcb-present0 1.15-1 ii libxcb-sync1 1.15-1 ii libxcb-xfixes0 1.15-1 ii libxcb1 1.15-1 ii libxshmfence11.3-1 ii libzstd1 1.5.5+dfsg2-2 ii zlib1g 1:1.3.dfsg-3+b1 mesa-vdpau-drivers recommends no packages. mesa-vdpau-drivers suggests no packages.
Bug#1059782: mesa-vdpau-drivers: Upgrade to 23.3.* breaks video rendering in tkinter
Package: mesa-vdpau-drivers Followup-For: Bug #1059782 X-Debbugs-Cc: pitsior...@outlook.com @Vasyl Gello Shouldn't this be opened under mesa-VA-drivers as a new bug report with the same or greater severity? I am on a 6450, I am using radeon and I have lost vaapi on all my players since 23.3.x moved to testing. There isn't a single bug report for this and all I have found is a thread on debian forums. I commented on it, but there are no further replies, not even if 23.3.4 fixes it, which reached unstable a couple of days ago. So right now I am waiting for it to reach testing by the end of the week before posting again. The only patch that may fix it is this one I found on arch https://gitlab.archlinux.org/archlinux/packaging/packages/mesa/-/commit/15e037dba159f893360d642e4efa13e09682b080 -- System Information: Debian Release: trixie/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 6.5.0-5-amd64 (SMP w/2 CPU threads; PREEMPT) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) Versions of packages mesa-vdpau-drivers depends on: ii libc62.37-14 ii libdrm-amdgpu1 2.4.120-1 ii libdrm-nouveau2 2.4.120-1 ii libdrm-radeon1 2.4.120-1 ii libdrm2 2.4.120-1 ii libelf1 0.190-1+b1 ii libexpat12.5.0-2+b2 ii libgcc-s113.2.0-10 ii libllvm171:17.0.6-5 ii libstdc++6 13.2.0-10 ii libvdpau11.5-2 ii libx11-xcb1 2:1.8.7-1 ii libxcb-dri2-01.15-1 ii libxcb-dri3-01.15-1 ii libxcb-present0 1.15-1 ii libxcb-sync1 1.15-1 ii libxcb-xfixes0 1.15-1 ii libxcb1 1.15-1 ii libxshmfence11.3-1 ii libzstd1 1.5.5+dfsg2-2 ii zlib1g 1:1.3.dfsg-3+b1 mesa-vdpau-drivers recommends no packages. mesa-vdpau-drivers suggests no packages.
Bug#1052376: lxpanel: no longer obeys its geometry settings
Package: lxpanel Version: 0.10.1-4.1 Followup-For: Bug #1052376 X-Debbugs-Cc: pitsior...@outlook.com I would like to publically thank Jeroen Diederen for patching lxpanel for me (thus the .1 at the end of the package version) and for showing us the github repo of lxde-continued. He has replied at the other bug report, the one about the gtk3 issues of the app (1052050). Oddly, all 7 patches that are there fixed only one of my issues above, the one with the panel going off screen. However, this was the most annoying one for me and I am thankfull for his work. I probably do not use the functionality the others patches provide. There is a newer version of lxpanel on the github page of lxde-continued, 0.10.2, and, if the lxde project is really abandoned by its own devs who moved to lxqt, I would like to see the maintainers updating lxpanel from there, assuming that debian has no plans of removing lxde as a whole anytime soon, and since its other other apps like lxterminal still work. p.s. Yea, vala-panel did not make it for me because of some crashes it regularly had and I removed it a week later. -- System Information: Debian Release: trixie/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 6.5.0-4-amd64 (SMP w/2 CPU threads; PREEMPT) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) Versions of packages lxpanel depends on: ii libasound2 1.2.10-1 ii libc62.37-12 ii libcairo21.18.0-1 ii libcurl3-gnutls 8.4.0-2 ii libfm-gtk3-4 1.3.2-4 ii libfm-modules1.3.2-4 ii libfm4 1.3.2-4 ii libgdk-pixbuf-2.0-0 2.42.10+dfsg-3 ii libglib2.0-0 2.78.1-4 ii libgtk-3-0 3.24.38-6 ii libiw30 30~pre9-14 ii libkeybinder-3.0-0 0.3.2-1.1 ii libmenu-cache3 1.1.0-1.1 ii libpango-1.0-0 1.51.0+ds-3 ii libwnck-3-0 43.0-3 ii libx11-6 2:1.8.7-1 ii libxkbfile1 1:1.1.0-1 ii libxml2 2.9.14+dfsg-1.3 ii lxmenu-data 0.1.5-2.1 ii lxpanel-data 0.10.1-4.1 Versions of packages lxpanel recommends: ii alacritty [x-terminal-emulator] 0.12.2-2+b1 ii dunst [notification-daemon] 1.9.2-1 ii libnotify-bin 0.8.2-1 ii notification-daemon 3.20.0-4+b1 pn pavucontrol | gnome-alsamixer ii rxvt-unicode [x-terminal-emulator] 9.31-1 ii xkb-data2.38-2 Versions of packages lxpanel suggests: ii brave-browser [www-browser] 1.60.118 ii chromium [www-browser] 119.0.6045.159-1 ii firefox [www-browser]120.0-2 -- no debconf information
Bug#1052376: lxpanel: no longer obeys its geometry settings
Package: lxpanel Version: 0.10.1-4 Followup-For: Bug #1052376 X-Debbugs-Cc: pitsior...@outlook.com Has anyone tried (or even switched to) another panel? I am currently trying vala-panel. It is not perfect, e.g. it sometimes crashes and I had to symlink a lib so as to get the tray area working, but it seems fine for day to day usage until lxpanel gets patched. -- System Information: Debian Release: trixie/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 6.5.0-2-amd64 (SMP w/2 CPU threads; PREEMPT) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) Versions of packages lxpanel depends on: ii libasound2 1.2.10-1 ii libc62.37-12 ii libcairo21.18.0-1 ii libcurl3-gnutls 8.4.0-2 ii libfm-gtk3-4 1.3.2-4 ii libfm-modules1.3.2-4 ii libfm4 1.3.2-4 ii libgdk-pixbuf-2.0-0 2.42.10+dfsg-1+b1 ii libglib2.0-0 2.78.0-2 ii libgtk-3-0 3.24.38-5 ii libiw30 30~pre9-14 ii libkeybinder-3.0-0 0.3.2-1.1 ii libmenu-cache3 1.1.0-1.1 ii libpango-1.0-0 1.51.0+ds-2 ii libwnck-3-0 43.0-3 ii libx11-6 2:1.8.7-1 ii libxml2 2.9.14+dfsg-1.3 ii lxmenu-data 0.1.5-2.1 ii lxpanel-data 0.10.1-4 Versions of packages lxpanel recommends: ii alacritty [x-terminal-emulator] 0.12.2-2+b1 ii dunst [notification-daemon] 1.9.2-1 ii libnotify-bin 0.8.2-1 ii notification-daemon 3.20.0-4+b1 pn pavucontrol | gnome-alsamixer ii rxvt-unicode [x-terminal-emulator] 9.31-1 ii xkb-data2.38-2 Versions of packages lxpanel suggests: ii brave-browser [www-browser] 1.59.124 ii chromium [www-browser] 118.0.5993.117-1 ii firefox [www-browser]118.0.2-1 -- no debconf information
Bug#1029681: nvidia-legacy-340xx-driver: Qt5 apps fail to launch with a segfault
Package: nvidia-legacy-340xx-driver Followup-For: Bug #1029681 X-Debbugs-Cc: pitsior...@outlook.com 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. -- System Information: Debian Release: trixie/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 6.5.0-1-amd64 (SMP w/2 CPU threads; PREEMPT) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) Versions of packages nvidia-legacy-340xx-driver depends on: pn nvidia-installer-cleanup pn nvidia-legacy-340xx-alternative pn nvidia-legacy-340xx-driver-bin pn nvidia-legacy-340xx-driver-libs pn nvidia-legacy-340xx-kernel-dkms | nvidia-legacy-340xx-kernel-340.10 8 pn nvidia-legacy-340xx-vdpau-driver pn nvidia-support pn xserver-xorg-video-nvidia-legacy-340xx Versions of packages nvidia-legacy-340xx-driver recommends: pn nvidia-persistenced pn nvidia-settings-legacy-340xx Versions of packages nvidia-legacy-340xx-driver suggests: pn nvidia-legacy-340xx-kernel-dkms | nvidia-legacy-340xx-kernel-source
Bug#1052210: lxappearance: segfault after upgrade to lxappearance 0.6.3-3
Package: lxappearance Followup-For: Bug #1052210 X-Debbugs-Cc: pitsior...@outlook.com Lxde (= the package) is just a metapackage which installs all the relevant packages for lxde (= the desktop enviroment), lxappearance and lxappearance- obconf included. So, don't worry if it gets removed, it is only a metapackage, you will still be able to access your desktop :) -- System Information: Debian Release: trixie/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 6.5.0-1-amd64 (SMP w/2 CPU threads; PREEMPT) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) Versions of packages lxappearance depends on: ii libc62.37-10 ii libdbus-1-3 1.14.10-1 ii libgdk-pixbuf-2.0-0 2.42.10+dfsg-1+b1 ii libglib2.0-0 2.78.0-2 ii libgtk-3-0 3.24.38-5 ii libx11-6 2:1.8.6-1 Versions of packages lxappearance recommends: pn lxde-settings-daemon lxappearance suggests no packages. -- no debconf information
Bug#1052210: lxappearance: segfault after upgrade to lxappearance 0.6.3-3
Package: lxappearance Followup-For: Bug #1052210 X-Debbugs-Cc: pitsior...@outlook.com @10dmar10 Do you have lxapperance-obconf installed too? If yes, have you tried removing it? And if possible, please open a new bug report there, with grave severity. The patch is already available, so it won't be much work of fixing the package. -- System Information: Debian Release: trixie/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 6.5.0-1-amd64 (SMP w/2 CPU threads; PREEMPT) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) Versions of packages lxappearance depends on: ii libc62.37-10 ii libdbus-1-3 1.14.10-1 ii libgdk-pixbuf-2.0-0 2.42.10+dfsg-1+b1 ii libglib2.0-0 2.78.0-2 ii libgtk-3-0 3.24.38-5 ii libx11-6 2:1.8.6-1 Versions of packages lxappearance recommends: pn lxde-settings-daemon lxappearance suggests no packages. -- no debconf information
Bug#1052376: lxpanel: no longer obeys its geometry settings
Package: lxpanel Version: 0.10.1-4 Followup-For: Bug #1052376 X-Debbugs-Cc: pitsior...@outlook.com Any chance of merging any of the patches from the other bug report? Let's say that I can live with the panel being bright (I use numix as gtk theme)... or with the tooltips that show up on the top of the screen instead of above the panel (I have it on the bottom)... or with the icons' display in the task bar which is partially broken. What annoys me the most is that when opening more than 6 windows, the right side of the panel, with the clock and the tray, goes off screen (screen has 1280 pixels width). p.s. The panel being bright is something gtk3 related I guess, because pcmanfm is also bright and got its gtk3 upgrade at the same time. Forcing the gtk3 apps to use the dark version of the theme, by adding gtk-application-prefer-dark- theme=1 in .config/gtk-3.0/settings.ini makes all gtk3 apps dark, e.g. chromium or firefox, which is not wanted. -- System Information: Debian Release: trixie/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 6.5.0-1-amd64 (SMP w/2 CPU threads; PREEMPT) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) Versions of packages lxpanel depends on: ii libasound2 1.2.9-2 ii libc62.37-10 ii libcairo21.18.0-1 ii libcurl3-gnutls 8.2.1-2 ii libfm-gtk3-4 1.3.2-4 ii libfm-modules1.3.2-4 ii libfm4 1.3.2-4 ii libgdk-pixbuf-2.0-0 2.42.10+dfsg-1+b1 ii libglib2.0-0 2.78.0-2 ii libgtk-3-0 3.24.38-5 ii libiw30 30~pre9-14 ii libkeybinder-3.0-0 0.3.2-1.1 ii libmenu-cache3 1.1.0-1.1 ii libpango-1.0-0 1.51.0+ds-2 ii libwnck-3-0 43.0-3 ii libx11-6 2:1.8.6-1 ii libxml2 2.9.14+dfsg-1.3 ii lxmenu-data 0.1.5-2.1 ii lxpanel-data 0.10.1-4 Versions of packages lxpanel recommends: ii alacritty [x-terminal-emulator] 0.12.2-2 ii dunst [notification-daemon] 1.9.2-1 ii libnotify-bin 0.8.2-1 ii notification-daemon 3.20.0-4+b1 pn pavucontrol | gnome-alsamixer ii rxvt-unicode [x-terminal-emulator] 9.31-1 ii xkb-data2.38-2 ii xterm [x-terminal-emulator] 384-1 Versions of packages lxpanel suggests: ii brave-browser [www-browser] 1.58.135 ii chromium [www-browser] 117.0.5938.132-1 ii firefox [www-browser]117.0.1-1 -- no debconf information
Bug#1052210: lxappearance: segfault after upgrade to lxappearance 0.6.3-3
Package: lxappearance Followup-For: Bug #1052210 X-Debbugs-Cc: pitsior...@outlook.com If anyone is interested to patch lxappearance-obconf, there is this patch in its github page which fixes the segfault in gtk3. https://github.com/lxde/lxappearance- obconf/commit/b9d45ea632235f4a07eba4fd6b5e5cee3a27f59e There are also 10 more patches in there, all of which were made this month for addressing several other issues, because a new version won't come out anytime soon. -- System Information: Debian Release: trixie/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 6.4.0-4-amd64 (SMP w/2 CPU threads; PREEMPT) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) Versions of packages lxappearance depends on: ii libc62.37-10 ii libdbus-1-3 1.14.10-1 ii libgdk-pixbuf-2.0-0 2.42.10+dfsg-1+b1 ii libglib2.0-0 2.78.0-2 ii libgtk-3-0 3.24.38-5 ii libx11-6 2:1.8.6-1 Versions of packages lxappearance recommends: pn lxde-settings-daemon lxappearance suggests no packages. -- no debconf information
Bug#1052210: lxappearance: segfault after upgrade to lxappearance 0.6.3-3
Package: lxappearance Version: 0.6.3-4 Followup-For: Bug #1052210 X-Debbugs-Cc: pitsior...@outlook.com Same thing here, the -4 update did not fix the app for me as well. I do not have gdb installed and I have no idea how to debug something, thus no gdb output from me. dmesg output [ 284.595381] lxappearance[3593]: segfault at bd95f804 ip 7f6ed36fbfa4 sp 7ffe885b2dc8 error 5 in libcairo.so.2.11708.0[7f6ed3697000+e3000] likely on CPU 1 (core 1, socket 0) [ 284.595408] Code: e9 11 29 fb ff 90 31 c0 c3 0f 1f 44 00 00 89 f0 c3 0f 1f 44 00 00 f3 0f 1e fa 8b 47 10 c3 0f 1f 84 00 00 00 00 00 f3 0f 1e fa <8b> 47 14 c3 0f 1f 84 00 00 00 00 00 f3 0f 1e fa 8b 47 1c c3 0f 1f Then I noticed something in rujasu's output above: the obconf.so lib. So, I removed lxappearance-obconf and, poof, lxappearance launced like it used to! Maybe it is time to file a bug report for that package and leave this one closed. -- System Information: Debian Release: trixie/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 6.4.0-4-amd64 (SMP w/2 CPU threads; PREEMPT) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) Versions of packages lxappearance depends on: ii libc62.37-10 ii libdbus-1-3 1.14.10-1 ii libgdk-pixbuf-2.0-0 2.42.10+dfsg-1+b1 ii libglib2.0-0 2.78.0-1 ii libgtk-3-0 3.24.38-5 ii libx11-6 2:1.8.6-1 Versions of packages lxappearance recommends: pn lxde-settings-daemon lxappearance suggests no packages. -- no debconf information
Bug#1029681: nvidia-legacy-340xx-driver: Qt5 apps fail to launch with a segfault
Package: nvidia-legacy-340xx-driver Followup-For: Bug #1029681 X-Debbugs-Cc: pitsior...@outlook.com 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. -- System Information: Debian Release: trixie/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 6.4.0-4-amd64 (SMP w/2 CPU threads; PREEMPT) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) Versions of packages nvidia-legacy-340xx-driver depends on: pn nvidia-installer-cleanup pn nvidia-legacy-340xx-alternative pn nvidia-legacy-340xx-driver-bin pn nvidia-legacy-340xx-driver-libs pn nvidia-legacy-340xx-kernel-dkms | nvidia-legacy-340xx-kernel-340.10 8 pn nvidia-legacy-340xx-vdpau-driver pn nvidia-support pn xserver-xorg-video-nvidia-legacy-340xx Versions of packages nvidia-legacy-340xx-driver recommends: pn nvidia-persistenced pn nvidia-settings-legacy-340xx Versions of packages nvidia-legacy-340xx-driver suggests: pn nvidia-legacy-340xx-kernel-dkms | nvidia-legacy-340xx-kernel-source
Bug#1052210: lxappearance: segfault after upgrade to lxappearance 0.6.3-3
Package: lxappearance Version: 0.6.3-3 Followup-For: Bug #1052210 X-Debbugs-Cc: pitsior...@outlook.com Until the patch is applied in debian's package too, can someone raise this to grave, please? It does render the package unusable after all and I really wish apt-listbugs would catch it and prevent the upgrade. -- System Information: Debian Release: trixie/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 6.4.0-4-amd64 (SMP w/2 CPU threads; PREEMPT) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) Versions of packages lxappearance depends on: ii libc62.37-8 ii libdbus-1-3 1.14.10-1 ii libgdk-pixbuf-2.0-0 2.42.10+dfsg-1+b1 ii libglib2.0-0 2.78.0-1 ii libgtk-3-0 3.24.38-5 ii libx11-6 2:1.8.6-1 Versions of packages lxappearance recommends: pn lxde-settings-daemon lxappearance suggests no packages. -- no debconf information
Bug#996815: rxvt-unicode: Terminal text rendering too wide after upgrade to FreeType 2.11.0+dfsg-1
Package: rxvt-unicode Version: 9.31-1 Followup-For: Bug #996815 X-Debbugs-Cc: pitsior...@outlook.com I think it is time to close this. Fontconfig's update to 2.14.2 on August 16th (that is when it reached testing) made urxvt's font spacing return to normal, so the letterspace parameter in .Xdefaults is no longer needed. In fact, it makes the text harder to read because it is denser. Removing it made it look like it used to, so please verify it yourselves. Ugly screenshots and configs upon request. -- System Information: Debian Release: trixie/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 6.4.0-2-amd64 (SMP w/2 CPU threads; PREEMPT) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) Versions of packages rxvt-unicode depends on: ii base-passwd 3.6.1 ii libc6 2.37-7 ii libfontconfig12.14.2-3 ii libgcc-s1 13.2.0-2 ii libgdk-pixbuf-2.0-0 2.42.10+dfsg-1+b1 ii libglib2.0-0 2.77.2-1 ii libperl5.36 5.36.0-7 ii libptytty02.0-1+b1 ii libstartup-notification0 0.12-6+b1 ii libx11-6 2:1.8.6-1 ii libxext6 2:1.3.4-1+b1 ii libxft2 2.3.6-1 ii libxmu6 2:1.1.3-3 ii libxrender1 1:0.9.10-1.1 ii ncurses-base 6.4+20230625-2 ii ncurses-term 6.4+20230625-2 Versions of packages rxvt-unicode recommends: pn fonts-dejavu pn fonts-vlgothic | fonts-japanese-gothic Versions of packages rxvt-unicode suggests: ii sensible-utils 0.0.20 -- no debconf information
Bug#1029681: nvidia-legacy-340xx-driver: Qt5 apps fail to launch with a segfault
Package: nvidia-legacy-340xx-driver Version: 340.108-19 Followup-For: Bug #1029681 X-Debbugs-Cc: pitsior...@outlook.com 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. -- System Information: Debian Release: trixie/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 6.3.0-1-amd64 (SMP w/2 CPU threads; PREEMPT) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) Versions of packages nvidia-legacy-340xx-driver depends on: ii nvidia-installer-cleanup 20220217+3 ii nvidia-legacy-340xx-alternative 340.108-19 ii nvidia-legacy-340xx-driver-bin 340.108-19 ii nvidia-legacy-340xx-driver-libs 340.108-19 ii nvidia-legacy-340xx-kernel-dkms [nvidia-legacy-340xx-kernel-340 340.108-19 .108] ii nvidia-legacy-340xx-vdpau-driver 340.108-19 ii nvidia-support 20220217+3 ii xserver-xorg-video-nvidia-legacy-340xx 340.108-19 Versions of packages nvidia-legacy-340xx-driver recommends: pn nvidia-persistenced ii nvidia-settings-legacy-340xx 340.108-7 Versions of packages nvidia-legacy-340xx-driver suggests: ii nvidia-legacy-340xx-kernel-dkms 340.108-19 Versions of packages nvidia-legacy-340xx-driver-libs:amd64 depends on: ii libegl1-nvidia-legacy-340xx 340.108-19 ii libgl1-nvidia-legacy-340xx-glx 340.108-19 Versions of packages nvidia-legacy-340xx-driver-libs:amd64 recommends: ii libgles1-nvidia-legacy-340xx 340.108-19 ii libgles2-nvidia-legacy-340xx 340.108-19 pn libnvidia-legacy-340xx-cfg1 pn libnvidia-legacy-340xx-encode1 pn nvidia-legacy-340xx-driver-libs-i386 Versions of packages libgl1-nvidia-legacy-340xx-glx:amd64 depends on: ii libc62.36-9 ii libnvidia-legacy-340xx-glcore340.108-19 ii libx11-6 2:1.8.6-1 ii libxext6 2:1.3.4-1+b1 ii nvidia-installer-cleanup 20220217+3 ii nvidia-legacy-340xx-alternative 340.108-19 ii nvidia-support 20220217+3 Versions of packages libgl1-nvidia-legacy-340xx-glx:amd64 recommends: ii nvidia-legacy-340xx-kernel-dkms [nvidia-legacy-340xx-kernel-340 340.108-19 .108] Versions of packages libgl1-nvidia-legacy-340xx-glx:amd64 suggests: ii nvidia-legacy-340xx-kernel-dkms 340.108-19 Versions of packages xserver-xorg-video-nvidia-legacy-340xx depends on: ii libc6 2.36-9 ii libnvidia-legacy-340xx-glcore 340.108-19 ii nvidia-installer-cleanup 20220217+3 ii nvidia-legacy-340xx-alternative340.108-19 ii nvidia-support 20220217+3 ii xserver-xorg-core [xorg-video-abi-25] 2:21.1.7-3 Versions of packages xserver-xorg-video-nvidia-legacy-340xx recommends: ii nvidia-legacy-340xx-kernel-dkms [nvidia-legacy-340xx-kernel-340 340.108-19 .108] ii nvidia-legacy-340xx-vdpau-driver 340.108-19 ii nvidia-settings-legacy-340xx 340.108-7 Versions of packages xserver-xorg-video-nvidia-legacy-340xx suggests: ii
Bug#1029681: nvidia-legacy-340xx-driver: Qt5 apps fail to launch with a segfault
Package: nvidia-legacy-340xx-driver Version: 340.108-19 Followup-For: Bug #1029681 X-Debbugs-Cc: pitsior...@outlook.com 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. -- System Information: Debian Release: trixie/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 6.3.0-1-amd64 (SMP w/2 CPU threads; PREEMPT) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) Versions of packages nvidia-legacy-340xx-driver depends on: ii nvidia-installer-cleanup 20220217+3 ii nvidia-legacy-340xx-alternative 340.108-19 ii nvidia-legacy-340xx-driver-bin 340.108-19 ii nvidia-legacy-340xx-driver-libs 340.108-19 ii nvidia-legacy-340xx-kernel-dkms [nvidia-legacy-340xx-kernel-340 340.108-19 .108] ii nvidia-legacy-340xx-vdpau-driver 340.108-19 ii nvidia-support 20220217+3 ii xserver-xorg-video-nvidia-legacy-340xx 340.108-19 Versions of packages nvidia-legacy-340xx-driver recommends: pn nvidia-persistenced ii nvidia-settings-legacy-340xx 340.108-7 Versions of packages nvidia-legacy-340xx-driver suggests: ii nvidia-legacy-340xx-kernel-dkms 340.108-19 Versions of packages nvidia-legacy-340xx-driver-libs:amd64 depends on: ii libegl1-nvidia-legacy-340xx 340.108-19 ii libgl1-nvidia-legacy-340xx-glx 340.108-19 Versions of packages nvidia-legacy-340xx-driver-libs:amd64 recommends: ii libgles1-nvidia-legacy-340xx 340.108-19 ii libgles2-nvidia-legacy-340xx 340.108-19 pn libnvidia-legacy-340xx-cfg1 pn libnvidia-legacy-340xx-encode1 pn nvidia-legacy-340xx-driver-libs-i386 Versions of packages libgl1-nvidia-legacy-340xx-glx:amd64 depends on: ii libc62.36-9 ii libnvidia-legacy-340xx-glcore340.108-19 ii libx11-6 2:1.8.6-1 ii libxext6 2:1.3.4-1+b1 ii nvidia-installer-cleanup 20220217+3 ii nvidia-legacy-340xx-alternative 340.108-19 ii nvidia-support 20220217+3 Versions of packages libgl1-nvidia-legacy-340xx-glx:amd64 recommends: ii nvidia-legacy-340xx-kernel-dkms [nvidia-legacy-340xx-kernel-340 340.108-19 .108] Versions of packages libgl1-nvidia-legacy-340xx-glx:amd64 suggests: ii nvidia-legacy-340xx-kernel-dkms 340.108-19 Versions of packages xserver-xorg-video-nvidia-legacy-340xx depends on: ii libc6 2.36-9 ii libnvidia-legacy-340xx-glcore 340.108-19 ii nvidia-installer-cleanup 20220217+3 ii nvidia-legacy-340xx-alternative340.108-19 ii nvidia-support 20220217+3 ii xserver-xorg-core [xorg-video-abi-25] 2:21.1.7-3 Versions of packages xserver-xorg-video-nvidia-legacy-340xx recommends: ii nvidia-legacy-340xx-kernel-dkms [nvidia-legacy-340xx-kernel-340 340.108-19 .108] ii nvidia-legacy-340xx-vdpau-driver 340.108-19 ii nvidia-settings-legacy-340xx 340.108-7 Versions of packages xserver-xorg-video-nvidia-legacy-340xx suggests: ii nvidia-legacy-340xx-kernel-dkms 340.108-19 Versions of packages nvidia-legacy-340xx-alternative depends on: ii dpkg1.21.22 ii glx-alternative-nvidia 1.2.2 Versions of packages nvidia-legacy-340xx-kernel-dkms depends on: ii dkms 3.0.11-3 ii nvidia-installer-cleanup 20220217+3 ii nvidia-legacy-340xx-kernel-support [nvidia-legacy-340xx-kernel- 340.108-19 support--v1] nvidia-legacy-340xx-kernel-dkms recommends no packages. Versions of packages glx-alternative-nvidia depends on: ii dpkg 1.21.22 ii glx-alternative-mesa 1.2.2 ii glx-diversions1.2.2 ii update-glx1.2.2 Versions of packages glx-alternative-nvidia suggests: ii nvidia-legacy-340xx-driver [nvidia-driver-any] 340.108-19 Versions of packages nvidia-legacy-340xx-driver is related to: pn bumblebee pn bumblebee-nvidia
Bug#1029681: nvidia-legacy-340xx-driver: Qt5 apps fail to launch with a segfault
Package: nvidia-legacy-340xx-driver Version: 340.108-18 Followup-For: Bug #1029681 X-Debbugs-Cc: pitsior...@outlook.com 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. -- System Information: Debian Release: 12.0 APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 6.1.0-7-amd64 (SMP w/2 CPU threads; PREEMPT) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) Versions of packages nvidia-legacy-340xx-driver depends on: ii nvidia-installer-cleanup 20220217+2 ii nvidia-legacy-340xx-alternative 340.108-18 ii nvidia-legacy-340xx-driver-bin 340.108-18 ii nvidia-legacy-340xx-driver-libs 340.108-18 ii nvidia-legacy-340xx-kernel-dkms [nvidia-legacy-340xx-kernel-340 340.108-18 .108] ii nvidia-legacy-340xx-vdpau-driver 340.108-18 ii nvidia-support 20220217+2 ii xserver-xorg-video-nvidia-legacy-340xx 340.108-18 Versions of packages nvidia-legacy-340xx-driver recommends: pn nvidia-persistenced ii nvidia-settings-legacy-340xx 340.108-7 Versions of packages nvidia-legacy-340xx-driver suggests: ii nvidia-legacy-340xx-kernel-dkms 340.108-18 Versions of packages nvidia-legacy-340xx-driver-libs:amd64 depends on: ii libegl1-nvidia-legacy-340xx 340.108-18 ii libgl1-nvidia-legacy-340xx-glx 340.108-18 Versions of packages nvidia-legacy-340xx-driver-libs:amd64 recommends: ii libgles1-nvidia-legacy-340xx 340.108-18 ii libgles2-nvidia-legacy-340xx 340.108-18 pn libnvidia-legacy-340xx-cfg1 pn libnvidia-legacy-340xx-encode1 pn nvidia-legacy-340xx-driver-libs-i386 Versions of packages libgl1-nvidia-legacy-340xx-glx:amd64 depends on: ii libc62.36-8 ii libnvidia-legacy-340xx-glcore340.108-18 ii libx11-6 2:1.8.4-2 ii libxext6 2:1.3.4-1+b1 ii nvidia-installer-cleanup 20220217+2 ii nvidia-legacy-340xx-alternative 340.108-18 ii nvidia-support 20220217+2 Versions of packages libgl1-nvidia-legacy-340xx-glx:amd64 recommends: ii nvidia-legacy-340xx-kernel-dkms [nvidia-legacy-340xx-kernel-340 340.108-18 .108] Versions of packages libgl1-nvidia-legacy-340xx-glx:amd64 suggests: ii nvidia-legacy-340xx-kernel-dkms 340.108-18 Versions of packages xserver-xorg-video-nvidia-legacy-340xx depends on: ii libc6 2.36-8 ii libnvidia-legacy-340xx-glcore 340.108-18 ii nvidia-installer-cleanup 20220217+2 ii nvidia-legacy-340xx-alternative340.108-18 ii nvidia-support 20220217+2 ii xserver-xorg-core [xorg-video-abi-25] 2:21.1.7-2 Versions of packages xserver-xorg-video-nvidia-legacy-340xx recommends: ii nvidia-legacy-340xx-kernel-dkms [nvidia-legacy-340xx-kernel-340 340.108-18 .108] ii nvidia-legacy-340xx-vdpau-driver 340.108-18 ii nvidia-settings-legacy-340xx 340.108-7 Versions of packages xserver-xorg-video-nvidia-legacy-340xx suggests: ii nvidia-legacy-340xx-kernel-dkms 340.108-18 Versions of packages nvidia-legacy-340xx-alternative depends on: ii dpkg1.21.21 ii glx-alternative-nvidia 1.2.2 Versions of packages nvidia-legacy-340xx-kernel-dkms depends on: ii dkms 3.0.10-6 ii nvidia-installer-cleanup 20220217+2 ii nvidia-legacy-340xx-kernel-support [nvidia-legacy-340xx-kernel- 340.108-18 support--v1] nvidia-legacy-340xx-kernel-dkms recommends no packages. Versions of packages glx-alternative-nvidia depends on: ii dpkg 1.21.21 ii glx-alternative-mesa 1.2.2 ii glx-diversions1.2.2 ii update-glx1.2.2 Versions of packages glx-alternative-nvidia suggests: ii nvidia-legacy-340xx-driver [nvidia-driver-any] 340.108-18 Versions of packages nvidia-legacy-340xx-driver is related to: pn bumblebee pn
Bug#1029681: nvidia-legacy-340xx-driver: Qt5 apps fail to launch with a segfault
Package: nvidia-legacy-340xx-driver Version: 340.108-18 Followup-For: Bug #1029681 X-Debbugs-Cc: pitsior...@outlook.com 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 -- System Information: Debian Release: 12.0 APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 6.1.0-6-amd64 (SMP w/2 CPU threads; PREEMPT) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) Versions of packages nvidia-legacy-340xx-driver depends on: ii nvidia-installer-cleanup 20220217+2 ii nvidia-legacy-340xx-alternative 340.108-18 ii nvidia-legacy-340xx-driver-bin 340.108-18 ii nvidia-legacy-340xx-driver-libs 340.108-18 ii nvidia-legacy-340xx-kernel-dkms [nvidia-legacy-340xx-kernel-340 340.108-18 .108] ii nvidia-legacy-340xx-vdpau-driver 340.108-18 ii nvidia-support 20220217+2 ii xserver-xorg-video-nvidia-legacy-340xx 340.108-18 Versions of packages nvidia-legacy-340xx-driver recommends: pn nvidia-persistenced ii nvidia-settings-legacy-340xx 340.108-7 Versions of packages nvidia-legacy-340xx-driver suggests: ii nvidia-legacy-340xx-kernel-dkms 340.108-18 Versions of packages nvidia-legacy-340xx-driver-libs:amd64 depends on: ii libegl1-nvidia-legacy-340xx 340.108-18 ii libgl1-nvidia-legacy-340xx-glx 340.108-18 Versions of packages nvidia-legacy-340xx-driver-libs:amd64 recommends: ii libgles1-nvidia-legacy-340xx 340.108-18 ii libgles2-nvidia-legacy-340xx 340.108-18 pn libnvidia-legacy-340xx-cfg1 pn libnvidia-legacy-340xx-encode1 pn nvidia-legacy-340xx-driver-libs-i386 Versions of packages libgl1-nvidia-legacy-340xx-glx:amd64 depends on: ii libc62.36-8 ii libnvidia-legacy-340xx-glcore340.108-18 ii libx11-6 2:1.8.4-2 ii libxext6 2:1.3.4-1+b1 ii nvidia-installer-cleanup 20220217+2 ii nvidia-legacy-340xx-alternative 340.108-18 ii nvidia-support 20220217+2 Versions of packages libgl1-nvidia-legacy-340xx-glx:amd64 recommends: ii nvidia-legacy-340xx-kernel-dkms [nvidia-legacy-340xx-kernel-340 340.108-18 .108] Versions of packages libgl1-nvidia-legacy-340xx-glx:amd64 suggests: ii nvidia-legacy-340xx-kernel-dkms 340.108-18 Versions of packages xserver-xorg-video-nvidia-legacy-340xx depends on: ii libc6 2.36-8 ii libnvidia-legacy-340xx-glcore 340.108-18 ii nvidia-installer-cleanup 20220217+2 ii nvidia-legacy-340xx-alternative340.108-18 ii nvidia-support 20220217+2 ii xserver-xorg-core [xorg-video-abi-25] 2:21.1.7-1 Versions of packages xserver-xorg-video-nvidia-legacy-340xx recommends: ii nvidia-legacy-340xx-kernel-dkms [nvidia-legacy-340xx-kernel-340 340.108-18 .108] ii nvidia-legacy-340xx-vdpau-driver 340.108-18 ii nvidia-settings-legacy-340xx 340.108-7 Versions of packages xserver-xorg-video-nvidia-legacy-340xx suggests: ii nvidia-legacy-340xx-kernel-dkms 340.108-18 Versions of packages nvidia-legacy-340xx-alternative depends on: ii dpkg1.21.21 ii glx-alternative-nvidia 1.2.2 Versions of packages nvidia-legacy-340xx-kernel-dkms depends on: ii dkms 3.0.10-6 ii nvidia-installer-cleanup 20220217+2 ii nvidia-legacy-340xx-kernel-support
Bug#1032983: firefox-esr: TLS websites broken with libnss3 2:3.87.1-1 from Debian testing/bookworm
Package: firefox-esr Followup-For: Bug #1032983 X-Debbugs-Cc: pitsior...@outlook.com The same thing applies to thunderbird 102.9.0 that reached the repo yesterday. Broken tls support there means no email can be sent or received and rss feeds do not work. I also have an ms exchange calendar in tb, which I was too upset to check if it works, but it probably won't. So, can you please add libnss3>=2:3.89 as a version dependency for those packages? -- System Information: Debian Release: bookworm/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 6.1.0-6-amd64 (SMP w/2 CPU threads; PREEMPT) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) Versions of packages firefox-esr depends on: ii debianutils 5.7-0.4 ii fontconfig 2.14.1-4 ii libasound2 1.2.8-1+b1 ii libatk1.0-0 2.46.0-5 ii libc62.36-8 ii libcairo-gobject21.16.0-7 ii libcairo21.16.0-7 ii libdbus-1-3 1.14.6-1 ii libdbus-glib-1-2 0.112-3 ii libevent-2.1-7 2.1.12-stable-5+b1 ii libffi8 3.4.4-1 ii libfontconfig1 2.14.1-4 ii libfreetype6 2.12.1+dfsg-4 ii libgcc-s112.2.0-14 ii libgdk-pixbuf-2.0-0 2.42.10+dfsg-1+b1 ii libglib2.0-0 2.74.6-1 ii libgtk-3-0 3.24.37-2 ii libnspr4 2:4.35-1 ii libnss3 2:3.87.1-1 ii libpango-1.0-0 1.50.12+ds-1 ii libstdc++6 12.2.0-14 ii libvpx7 1.12.0-1 ii libx11-6 2:1.8.4-2 ii libx11-xcb1 2:1.8.4-2 ii libxcb-shm0 1.15-1 ii libxcb1 1.15-1 ii libxcomposite1 1:0.4.5-1 ii libxdamage1 1:1.1.6-1 ii libxext6 2:1.3.4-1+b1 ii libxfixes3 1:6.0.0-2 ii libxrandr2 2:1.5.2-2+b1 ii libxtst6 2:1.2.3-1.1 ii procps 2:4.0.2-3 ii zlib1g 1:1.2.13.dfsg-1 Versions of packages firefox-esr recommends: ii libavcodec58 10:4.4.3-dmo3 Versions of packages firefox-esr suggests: pn fonts-lmodern pn fonts-stix | otf-stix pn libcanberra0 ii libgssapi-krb5-2 1.20.1-1 pn pulseaudio
Bug#952583: mps-youtube: Mps-youtube failes to find anything because google disabled its api key... and a 2 more minor issues
Package: mps-youtube Followup-For: Bug #952583 X-Debbugs-Cc: pitsior...@outlook.com Speaking of progress from upstream, and only 2 days after my comment here, a new version was released from upstream! https://github.com/mps-youtube/yewtube/releases/tag/v2.9.4 The project was renamed to yewtube and its versioning scheme is continued from the forked project above. If anyone is willing to package it, please do, else remove it from the repo. -- System Information: Debian Release: bookworm/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 6.1.0-3-amd64 (SMP w/2 CPU threads; PREEMPT) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) Versions of packages mps-youtube depends on: ii ffmpeg 10:5.1.2-dmo3 ii mpv1:0.35.1-dmo1 ii python33.11.1-3 pn python3-pafy ii python3-pkg-resources 66.1.1-1 Versions of packages mps-youtube recommends: ii libnotify40.8.1-1 pn python3-dbus ii python3-gi3.42.2-3+b1 ii xclip 0.13-2 mps-youtube suggests no packages.
Bug#1029681: nvidia-legacy-340xx-driver: Qt5 apps fail to launch with a segfault
Package: nvidia-legacy-340xx-driver Version: 340.108-17 Followup-For: Bug #1029681 X-Debbugs-Cc: pitsior...@outlook.com 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 :( -- System Information: Debian Release: bookworm/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 6.1.0-3-amd64 (SMP w/2 CPU threads; PREEMPT) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) Versions of packages nvidia-legacy-340xx-driver depends on: ii nvidia-installer-cleanup 20220217+2 ii nvidia-legacy-340xx-alternative 340.108-17 ii nvidia-legacy-340xx-driver-bin 340.108-17 ii nvidia-legacy-340xx-driver-libs 340.108-17 ii nvidia-legacy-340xx-kernel-dkms [nvidia-legacy-340xx-kernel-340 340.108-17 .108] ii nvidia-legacy-340xx-vdpau-driver 340.108-17 ii nvidia-support 20220217+2 ii xserver-xorg-video-nvidia-legacy-340xx 340.108-17 Versions of packages nvidia-legacy-340xx-driver recommends: pn nvidia-persistenced ii nvidia-settings-legacy-340xx 340.108-7 Versions of packages nvidia-legacy-340xx-driver suggests: ii nvidia-legacy-340xx-kernel-dkms 340.108-17 Versions of packages nvidia-legacy-340xx-driver-libs:amd64 depends on: ii libegl1-nvidia-legacy-340xx 340.108-17 ii libgl1-nvidia-legacy-340xx-glx 340.108-17 Versions of packages nvidia-legacy-340xx-driver-libs:amd64 recommends: ii libgles1-nvidia-legacy-340xx 340.108-17 ii libgles2-nvidia-legacy-340xx 340.108-17 pn libnvidia-legacy-340xx-cfg1 pn libnvidia-legacy-340xx-encode1 pn nvidia-legacy-340xx-driver-libs-i386 Versions of packages libgl1-nvidia-legacy-340xx-glx:amd64 depends on: ii libc62.36-8 ii libnvidia-legacy-340xx-glcore340.108-17 ii libx11-6 2:1.8.3-3 ii libxext6 2:1.3.4-1+b1 ii nvidia-installer-cleanup 20220217+2 ii nvidia-legacy-340xx-alternative 340.108-17 ii nvidia-support 20220217+2 Versions of packages libgl1-nvidia-legacy-340xx-glx:amd64 recommends: ii nvidia-legacy-340xx-kernel-dkms [nvidia-legacy-340xx-kernel-340 340.108-17 .108] Versions of packages libgl1-nvidia-legacy-340xx-glx:amd64 suggests: ii nvidia-legacy-340xx-kernel-dkms 340.108-17 Versions of packages xserver-xorg-video-nvidia-legacy-340xx depends on: ii libc6 2.36-8 ii libnvidia-legacy-340xx-glcore 340.108-17 ii nvidia-installer-cleanup 20220217+2 ii nvidia-legacy-340xx-alternative340.108-17 ii nvidia-support 20220217+2 ii xserver-xorg-core [xorg-video-abi-25] 2:21.1.6-1 Versions of packages xserver-xorg-video-nvidia-legacy-340xx recommends: ii nvidia-legacy-340xx-kernel-dkms [nvidia-legacy-340xx-kernel-340 340.108-17 .108] ii nvidia-legacy-340xx-vdpau-driver
Bug#1029681: nvidia-legacy-340xx-driver: Qt5 apps fail to launch with a segfault
Package: nvidia-legacy-340xx-driver Version: 340.108-17 Followup-For: Bug #1029681 X-Debbugs-Cc: pitsior...@outlook.com 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. -- System Information: Debian Release: bookworm/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 6.1.0-3-amd64 (SMP w/2 CPU threads; PREEMPT) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) Versions of packages nvidia-legacy-340xx-driver depends on: ii nvidia-installer-cleanup 20220217+2 ii nvidia-legacy-340xx-alternative 340.108-17 ii nvidia-legacy-340xx-driver-bin 340.108-17 ii nvidia-legacy-340xx-driver-libs 340.108-17 ii nvidia-legacy-340xx-kernel-dkms [nvidia-legacy-340xx-kernel-340 340.108-17 .108] ii nvidia-legacy-340xx-vdpau-driver 340.108-17 ii nvidia-support 20220217+2 ii xserver-xorg-video-nvidia-legacy-340xx 340.108-17 Versions of packages nvidia-legacy-340xx-driver recommends: pn nvidia-persistenced ii nvidia-settings-legacy-340xx 340.108-7 Versions of packages nvidia-legacy-340xx-driver suggests: ii nvidia-legacy-340xx-kernel-dkms 340.108-17 Versions of packages nvidia-legacy-340xx-driver-libs:amd64 depends on: ii libegl1-nvidia-legacy-340xx 340.108-17 ii libgl1-nvidia-legacy-340xx-glx 340.108-17 Versions of packages nvidia-legacy-340xx-driver-libs:amd64 recommends: ii libgles1-nvidia-legacy-340xx 340.108-17 ii libgles2-nvidia-legacy-340xx 340.108-17 pn libnvidia-legacy-340xx-cfg1 pn libnvidia-legacy-340xx-encode1 pn nvidia-legacy-340xx-driver-libs-i386 Versions of packages libgl1-nvidia-legacy-340xx-glx:amd64 depends on: ii libc62.36-8 ii libnvidia-legacy-340xx-glcore340.108-17 ii libx11-6 2:1.8.3-3 ii libxext6 2:1.3.4-1+b1 ii nvidia-installer-cleanup 20220217+2 ii nvidia-legacy-340xx-alternative 340.108-17 ii nvidia-support 20220217+2 Versions of packages libgl1-nvidia-legacy-340xx-glx:amd64 recommends: ii nvidia-legacy-340xx-kernel-dkms [nvidia-legacy-340xx-kernel-340 340.108-17 .108] Versions of packages libgl1-nvidia-legacy-340xx-glx:amd64 suggests: ii nvidia-legacy-340xx-kernel-dkms 340.108-17 Versions of packages xserver-xorg-video-nvidia-legacy-340xx depends on: ii libc6 2.36-8 ii libnvidia-legacy-340xx-glcore 340.108-17 ii nvidia-installer-cleanup 20220217+2 ii nvidia-legacy-340xx-alternative340.108-17 ii nvidia-support 20220217+2 ii xserver-xorg-core [xorg-video-abi-25] 2:21.1.6-1 Versions of packages xserver-xorg-video-nvidia-legacy-340xx recommends: ii nvidia-legacy-340xx-kernel-dkms [nvidia-legacy-340xx-kernel-340 340.108-17 .108] ii nvidia-legacy-340xx-vdpau-driver 340.108-17 ii nvidia-settings-legacy-340xx 340.108-7 Versions of packages xserver-xorg-video-nvidia-legacy-340xx suggests: ii nvidia-legacy-340xx-kernel-dkms 340.108-17 Versions of packages nvidia-legacy-340xx-alternative depends on: ii dpkg1.21.19 ii glx-alternative-nvidia 1.2.2 Versions of packages nvidia-legacy-340xx-kernel-dkms depends on: ii dkms 3.0.10-2 ii nvidia-installer-cleanup 20220217+2 ii nvidia-legacy-340xx-kernel-support [nvidia-legacy-340xx-kernel- 340.108-17 support--v1] nvidia-legacy-340xx-kernel-dkms recommends no packages. Versions of packages glx-alternative-nvidia depends on: ii dpkg 1.21.19 ii glx-alternative-mesa 1.2.2 ii glx-diversions1.2.2 ii update-glx1.2.2 Versions of packages glx-alternative-nvidia suggests: ii nvidia-legacy-340xx-driver [nvidia-driver-any] 340.108-17 Versions of packages nvidia-legacy-340xx-driver is related to: pn bumblebee pn bumblebee-nvidia
Bug#1029681: nvidia-legacy-340xx-driver: Qt5 apps fail to launch with a segfault
Package: nvidia-legacy-340xx-driver Version: 340.108-17 Followup-For: Bug #1029681 X-Debbugs-Cc: pitsior...@outlook.com 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. -- System Information: Debian Release: bookworm/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 6.1.0-3-amd64 (SMP w/2 CPU threads; PREEMPT) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) Versions of packages nvidia-legacy-340xx-driver depends on: ii nvidia-installer-cleanup 20220217+2 ii nvidia-legacy-340xx-alternative 340.108-17 ii nvidia-legacy-340xx-driver-bin 340.108-17 ii nvidia-legacy-340xx-driver-libs 340.108-17 ii nvidia-legacy-340xx-kernel-dkms [nvidia-legacy-340xx-kernel-340 340.108-17 .108] ii nvidia-legacy-340xx-vdpau-driver 340.108-17 ii nvidia-support 20220217+2 ii xserver-xorg-video-nvidia-legacy-340xx 340.108-17 Versions of packages nvidia-legacy-340xx-driver recommends: pn nvidia-persistenced ii nvidia-settings-legacy-340xx 340.108-7 Versions of packages nvidia-legacy-340xx-driver suggests: ii nvidia-legacy-340xx-kernel-dkms 340.108-17 Versions of packages nvidia-legacy-340xx-driver-libs:amd64 depends on: ii libegl1-nvidia-legacy-340xx 340.108-17 ii libgl1-nvidia-legacy-340xx-glx 340.108-17 Versions of packages nvidia-legacy-340xx-driver-libs:amd64 recommends: ii libgles1-nvidia-legacy-340xx 340.108-17 ii libgles2-nvidia-legacy-340xx 340.108-17 pn libnvidia-legacy-340xx-cfg1 pn libnvidia-legacy-340xx-encode1 pn nvidia-legacy-340xx-driver-libs-i386 Versions of packages libgl1-nvidia-legacy-340xx-glx:amd64 depends on: ii libc62.36-8 ii libnvidia-legacy-340xx-glcore340.108-17 ii libx11-6 2:1.8.3-3 ii libxext6 2:1.3.4-1+b1 ii nvidia-installer-cleanup 20220217+2 ii nvidia-legacy-340xx-alternative 340.108-17 ii nvidia-support 20220217+2 Versions of packages libgl1-nvidia-legacy-340xx-glx:amd64 recommends: ii nvidia-legacy-340xx-kernel-dkms [nvidia-legacy-340xx-kernel-340 340.108-17 .108] Versions of packages libgl1-nvidia-legacy-340xx-glx:amd64 suggests: ii nvidia-legacy-340xx-kernel-dkms 340.108-17 Versions of packages xserver-xorg-video-nvidia-legacy-340xx depends on: ii libc6 2.36-8 ii libnvidia-legacy-340xx-glcore 340.108-17 ii nvidia-installer-cleanup 20220217+2 ii nvidia-legacy-340xx-alternative340.108-17 ii nvidia-support 20220217+2 ii xserver-xorg-core [xorg-video-abi-25] 2:21.1.6-1 Versions of packages xserver-xorg-video-nvidia-legacy-340xx recommends: ii nvidia-legacy-340xx-kernel-dkms [nvidia-legacy-340xx-kernel-340 340.108-17 .108] ii nvidia-legacy-340xx-vdpau-driver 340.108-17 ii nvidia-settings-legacy-340xx 340.108-7 Versions of packages xserver-xorg-video-nvidia-legacy-340xx suggests: ii nvidia-legacy-340xx-kernel-dkms 340.108-17 Versions of packages
Bug#1029681: nvidia-legacy-340xx-driver: Qt5 apps fail to launch with a segfault
Package: nvidia-legacy-340xx-driver Version: 340.108-17 Followup-For: Bug #1029681 X-Debbugs-Cc: pitsior...@outlook.com 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 -- System Information: Debian Release: bookworm/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 6.1.0-3-amd64 (SMP w/2 CPU threads; PREEMPT) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) Versions of packages nvidia-legacy-340xx-driver depends on: ii nvidia-installer-cleanup 20220217+2 ii nvidia-legacy-340xx-alternative 340.108-17 ii nvidia-legacy-340xx-driver-bin 340.108-17 ii nvidia-legacy-340xx-driver-libs 340.108-17 ii nvidia-legacy-340xx-kernel-dkms [nvidia-legacy-340xx-kernel-340 340.108-17 .108] ii nvidia-legacy-340xx-vdpau-driver 340.108-17 ii nvidia-support 20220217+2 ii xserver-xorg-video-nvidia-legacy-340xx 340.108-17 Versions of packages nvidia-legacy-340xx-driver recommends: pn nvidia-persistenced ii nvidia-settings-legacy-340xx 340.108-7 Versions of packages nvidia-legacy-340xx-driver suggests: ii nvidia-legacy-340xx-kernel-dkms 340.108-17 Versions of packages nvidia-legacy-340xx-driver-libs:amd64 depends on: ii libegl1-nvidia-legacy-340xx 340.108-17 ii libgl1-nvidia-legacy-340xx-glx 340.108-17 Versions of packages nvidia-legacy-340xx-driver-libs:amd64 recommends: ii libgles1-nvidia-legacy-340xx 340.108-17 ii libgles2-nvidia-legacy-340xx 340.108-17 pn libnvidia-legacy-340xx-cfg1 pn libnvidia-legacy-340xx-encode1 pn nvidia-legacy-340xx-driver-libs-i386 Versions of packages libgl1-nvidia-legacy-340xx-glx:amd64 depends on: ii libc62.36-8 ii libnvidia-legacy-340xx-glcore340.108-17 ii libx11-6 2:1.8.3-3 ii libxext6 2:1.3.4-1+b1 ii nvidia-installer-cleanup 20220217+2 ii nvidia-legacy-340xx-alternative 340.108-17 ii nvidia-support 20220217+2 Versions of packages libgl1-nvidia-legacy-340xx-glx:amd64 recommends: ii nvidia-legacy-340xx-kernel-dkms [nvidia-legacy-340xx-kernel-340 340.108-17 .108] Versions of packages libgl1-nvidia-legacy-340xx-glx:amd64 suggests: ii nvidia-legacy-340xx-kernel-dkms 340.108-17 Versions of packages xserver-xorg-video-nvidia-legacy-340xx depends on: ii libc6 2.36-8 ii libnvidia-legacy-340xx-glcore 340.108-17 ii nvidia-installer-cleanup 20220217+2 ii nvidia-legacy-340xx-alternative340.108-17 ii nvidia-support 20220217+2 ii xserver-xorg-core [xorg-video-abi-25] 2:21.1.6-1 Versions of packages xserver-xorg-video-nvidia-legacy-340xx recommends: ii nvidia-legacy-340xx-kernel-dkms [nvidia-legacy-340xx-kernel-340 340.108-17 .108] ii nvidia-legacy-340xx-vdpau-driver 340.108-17 ii nvidia-settings-legacy-340xx 340.108-7 Versions of packages xserver-xorg-video-nvidia-legacy-340xx suggests: ii nvidia-legacy-340xx-kernel-dkms 340.108-17 Versions of packages nvidia-legacy-340xx-alternative depends on: ii dpkg1.21.19 ii glx-alternative-nvidia 1.2.2 Versions of packages nvidia-legacy-340xx-kernel-dkms depends on: ii dkms 3.0.10-2 ii nvidia-installer-cleanup 20220217+2 ii nvidia-legacy-340xx-kernel-support [nvidia-legacy-340xx-kernel- 340.108-17 support--v1] nvidia-legacy-340xx-kernel-dkms recommends no packages. Versions of packages glx-alternative-nvidia depends on: ii dpkg 1.21.19 ii glx-alternative-mesa 1.2.2 ii glx-diversions1.2.2 ii update-glx1.2.2 Versions of packages glx-alternative-nvidia suggests: ii nvidia-legacy-340xx-driver [nvidia-driver-any] 340.108-17 Versions of packages nvidia-legacy-340xx-driver is related to: pn bumblebee pn bumblebee-nvidia pn ccache
Bug#1029681: nvidia-legacy-340xx-driver: Qt5 apps fail to launch with a segfault
Package: nvidia-legacy-340xx-driver Version: 340.108-17 Followup-For: Bug #1029681 X-Debbugs-Cc: pitsior...@outlook.com 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. -- Package-specific info: uname -a: Linux mitsos 6.1.0-3-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.1.8-1 (2023-01-29) x86_64 GNU/Linux /proc/version: Linux version 6.1.0-3-amd64 (debian-ker...@lists.debian.org) (gcc-12 (Debian 12.2.0-14) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40) #1 SMP PREEMPT_DYNAMIC Debian 6.1.8-1 (2023-01-29) /proc/driver/nvidia/version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 340.108 Wed Dec 11 11:06:58 PST 2019 GCC version: gcc version 12.2.0 (Debian 12.2.0-14) lspci 'display controller [030?]': 01:00.0 VGA compatible controller [0300]: NVIDIA Corporation G96C [GeForce 9500 GT] [10de:0640] (rev a1) (prog-if 00 [VGA controller]) Subsystem: XFX Pine Group Inc. G96C [GeForce 9500 GT] [1682:2412] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- Kernel driver in use: nvidia Kernel modules: nvidia dmesg: [0.187363] Console: colour VGA+ 80x25 [0.420949] pci :01:00.0: vgaarb: setting as boot VGA device [0.420960] pci :01:00.0: vgaarb: bridge control possible [0.421005] pci :01:00.0: vgaarb: VGA device added: decodes=io+mem,owns=io+mem,locks=none [0.421063] vgaarb: loaded [0.583338] Linux agpgart interface v0.103 [3.736958] nvidia: loading out-of-tree module taints kernel. [3.737021] nvidia: module license 'NVIDIA' taints kernel. [3.755518] nvidia: module verification failed: signature and/or required key missing - tainting kernel [3.822569] nvidia :01:00.0: vgaarb: changed VGA decodes: olddecodes=io+mem,decodes=none:owns=io+mem [3.825428] [drm] Initialized nvidia-drm 0.0.0 20150116 for :01:00.0 on minor 0 [3.825517] NVRM: loading NVIDIA UNIX x86_64 Kernel Module 340.108 Wed Dec 11 11:06:58 PST 2019 [6.512302] caller _nv000788rm+0xe4/0x1c0 [nvidia] mapping multiple BARs Device node permissions: crw-rw+ 1 root video 226, 0 Feb 5 19:06 /dev/dri/card0 crw-rw-rw- 1 root root 195, 0 Feb 5 19:06 /dev/nvidia0 crw-rw-rw- 1 root root 195, 255 Feb 5 19:06 /dev/nvidiactl /dev/dri/by-path: total 0 lrwxrwxrwx 1 root root 8 Feb 5 19:06 pci-:01:00.0-card -> ../card0 video:*:44:jim Alternative 'nvidia': nvidia - auto mode link best version is /usr/lib/nvidia/legacy-340xx link currently points to /usr/lib/nvidia/legacy-340xx link nvidia is /usr/lib/nvidia/nvidia slave nvidia--20-nvidia-legacy-340xx.conf is /etc/X11/xorg.conf.d/20-nvidia-legacy-340xx.conf slave nvidia--libEGL.so.1-x86_64-linux-gnu is /usr/lib/x86_64-linux-gnu/nvidia/libEGL.so.1 slave nvidia--libGL.so.1-x86_64-linux-gnu is /usr/lib/x86_64-linux-gnu/nvidia/libGL.so.1 slave nvidia--libGLESv1_CM.so.1-x86_64-linux-gnu is /usr/lib/x86_64-linux-gnu/nvidia/libGLESv1_CM.so.1 slave nvidia--libGLESv2.so.2-x86_64-linux-gnu is /usr/lib/x86_64-linux-gnu/nvidia/libGLESv2.so.2 slave nvidia--libglx.so is /usr/lib/nvidia/libglx.so slave nvidia--libnvidia-ml.so.1-x86_64-linux-gnu is /usr/lib/x86_64-linux-gnu/libnvidia-ml.so.1 slave nvidia--libvdpau_nvidia.so.1-x86_64-linux-gnu is /usr/lib/x86_64-linux-gnu/vdpau/libvdpau_nvidia.so.1 slave nvidia--monitoring.conf is /usr/share/nvidia/monitoring.conf slave nvidia--nv-control-dpy is /usr/bin/nv-control-dpy slave nvidia--nvidia-blacklists-nouveau.conf is /etc/nvidia/nvidia-blacklists-nouveau.conf slave nvidia--nvidia-bug-report.sh is /usr/lib/nvidia/nvidia-bug-report.sh slave nvidia--nvidia-debugdump is /usr/bin/nvidia-debugdump slave nvidia--nvidia-drm-outputclass.conf is /etc/nvidia/nvidia-drm-outputclass.conf slave nvidia--nvidia-load.conf is /etc/nvidia/nvidia-load.conf slave nvidia--nvidia-modprobe.conf is /etc/nvidia/nvidia-modprobe.conf slave nvidia--nvidia-options.conf is /etc/modprobe.d/nvidia-options.conf slave nvidia--nvidia-settings is /usr/bin/nvidia-settings slave
Bug#1029681: nvidia-legacy-340xx-driver: Qt5 apps fail to launch with a segfault
Package: nvidia-legacy-340xx-driver Version: 340.108-17 Followup-For: Bug #1029681 X-Debbugs-Cc: pitsior...@outlook.com 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 :'( -- Package-specific info: uname -a: Linux mitsos 6.1.0-3-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.1.8-1 (2023-01-29) x86_64 GNU/Linux /proc/version: Linux version 6.1.0-3-amd64 (debian-ker...@lists.debian.org) (gcc-12 (Debian 12.2.0-14) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40) #1 SMP PREEMPT_DYNAMIC Debian 6.1.8-1 (2023-01-29) /proc/driver/nvidia/version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 340.108 Wed Dec 11 11:06:58 PST 2019 GCC version: gcc version 12.2.0 (Debian 12.2.0-14) lspci 'display controller [030?]': 01:00.0 VGA compatible controller [0300]: NVIDIA Corporation G96C [GeForce 9500 GT] [10de:0640] (rev a1) (prog-if 00 [VGA controller]) Subsystem: XFX Pine Group Inc. G96C [GeForce 9500 GT] [1682:2412] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- Kernel driver in use: nvidia Kernel modules: nvidia dmesg: [0.187167] Console: colour VGA+ 80x25 [0.421532] pci :01:00.0: vgaarb: setting as boot VGA device [0.421532] pci :01:00.0: vgaarb: bridge control possible [0.421532] pci :01:00.0: vgaarb: VGA device added: decodes=io+mem,owns=io+mem,locks=none [0.421532] vgaarb: loaded [0.582847] Linux agpgart interface v0.103 [3.778538] nvidia: loading out-of-tree module taints kernel. [3.778601] nvidia: module license 'NVIDIA' taints kernel. [3.801703] nvidia: module verification failed: signature and/or required key missing - tainting kernel [3.848199] nvidia :01:00.0: vgaarb: changed VGA decodes: olddecodes=io+mem,decodes=none:owns=io+mem [3.848808] [drm] Initialized nvidia-drm 0.0.0 20150116 for :01:00.0 on minor 0 [3.848892] NVRM: loading NVIDIA UNIX x86_64 Kernel Module 340.108 Wed Dec 11 11:06:58 PST 2019 [6.474940] caller _nv000788rm+0xe4/0x1c0 [nvidia] mapping multiple BARs Device node permissions: crw-rw+ 1 root video 226, 0 Feb 5 17:50 /dev/dri/card0 crw-rw-rw- 1 root root 195, 0 Feb 5 17:50 /dev/nvidia0 crw-rw-rw- 1 root root 195, 255 Feb 5 17:50 /dev/nvidiactl /dev/dri/by-path: total 0 lrwxrwxrwx 1 root root 8 Feb 5 17:50 pci-:01:00.0-card -> ../card0 video:*:44:jim Alternative 'nvidia': nvidia - auto mode link best version is /usr/lib/nvidia/legacy-340xx link currently points to /usr/lib/nvidia/legacy-340xx link nvidia is /usr/lib/nvidia/nvidia slave nvidia--20-nvidia-legacy-340xx.conf is /etc/X11/xorg.conf.d/20-nvidia-legacy-340xx.conf slave nvidia--libEGL.so.1-x86_64-linux-gnu is /usr/lib/x86_64-linux-gnu/nvidia/libEGL.so.1 slave nvidia--libGL.so.1-x86_64-linux-gnu is /usr/lib/x86_64-linux-gnu/nvidia/libGL.so.1 slave nvidia--libGLESv1_CM.so.1-x86_64-linux-gnu is /usr/lib/x86_64-linux-gnu/nvidia/libGLESv1_CM.so.1 slave nvidia--libGLESv2.so.2-x86_64-linux-gnu is /usr/lib/x86_64-linux-gnu/nvidia/libGLESv2.so.2 slave nvidia--libglx.so is /usr/lib/nvidia/libglx.so slave nvidia--libnvidia-ml.so.1-x86_64-linux-gnu is /usr/lib/x86_64-linux-gnu/libnvidia-ml.so.1 slave nvidia--libvdpau_nvidia.so.1-x86_64-linux-gnu is /usr/lib/x86_64-linux-gnu/vdpau/libvdpau_nvidia.so.1 slave nvidia--monitoring.conf is /usr/share/nvidia/monitoring.conf slave nvidia--nv-control-dpy is /usr/bin/nv-control-dpy slave nvidia--nvidia-blacklists-nouveau.conf is /etc/nvidia/nvidia-blacklists-nouveau.conf slave nvidia--nvidia-bug-report.sh is /usr/lib/nvidia/nvidia-bug-report.sh slave nvidia--nvidia-debugdump is /usr/bin/nvidia-debugdump slave nvidia--nvidia-drm-outputclass.conf is /etc/nvidia/nvidia-drm-outputclass.conf slave nvidia--nvidia-load.conf is /etc/nvidia/nvidia-load.conf slave nvidia--nvidia-modprobe.conf is /etc/nvidia/nvidia-modprobe.conf slave nvidia--nvidia-options.conf is /etc/modprobe.d/nvidia-options.conf slave nvidia--nvidia-settings is /usr/bin/nvidia-settings slave nvidia--nvidia-settings.1.gz is /usr/share/man/man1/nvidia-settings.1.gz slave nvidia--nvidia-settings.desktop is /usr/share/applications/nvidia-settings.desktop slave nvidia--nvidia-smi is /usr/bin/nvidia-smi slave nvidia--nvidia-smi.1.gz is
Bug#1029681: nvidia-legacy-340xx-driver: Qt5 apps fail to launch with a segfault
Package: nvidia-legacy-340xx-driver Version: 340.108-17 Followup-For: Bug #1029681 X-Debbugs-Cc: pitsior...@outlook.com 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. -- Package-specific info: uname -a: Linux mitsos 6.1.0-3-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.1.8-1 (2023-01-29) x86_64 GNU/Linux /proc/version: Linux version 6.1.0-3-amd64 (debian-ker...@lists.debian.org) (gcc-12 (Debian 12.2.0-14) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40) #1 SMP PREEMPT_DYNAMIC Debian 6.1.8-1 (2023-01-29) /proc/driver/nvidia/version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 340.108 Wed Dec 11 11:06:58 PST 2019 GCC version: gcc version 12.2.0 (Debian 12.2.0-14) lspci 'display controller [030?]': 01:00.0 VGA compatible controller [0300]: NVIDIA Corporation G96C [GeForce 9500 GT] [10de:0640] (rev a1) (prog-if 00 [VGA controller]) Subsystem: XFX Pine Group Inc. G96C [GeForce 9500 GT] [1682:2412] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- Kernel driver in use: nvidia Kernel modules: nvidia dmesg: [0.187983] Console: colour VGA+ 80x25 [0.419986] pci :01:00.0: vgaarb: setting as boot VGA device [0.419986] pci :01:00.0: vgaarb: bridge control possible [0.419986] pci :01:00.0: vgaarb: VGA device added: decodes=io+mem,owns=io+mem,locks=none [0.419986] vgaarb: loaded [0.583524] Linux agpgart interface v0.103 [3.602208] nvidia: loading out-of-tree module taints kernel. [3.602271] nvidia: module license 'NVIDIA' taints kernel. [3.622324] nvidia: module verification failed: signature and/or required key missing - tainting kernel [3.676297] nvidia :01:00.0: vgaarb: changed VGA decodes: olddecodes=io+mem,decodes=none:owns=io+mem [3.678625] [drm] Initialized nvidia-drm 0.0.0 20150116 for :01:00.0 on minor 0 [3.678713] NVRM: loading NVIDIA UNIX x86_64 Kernel Module 340.108 Wed Dec 11 11:06:58 PST 2019 [6.367089] caller _nv000788rm+0xe4/0x1c0 [nvidia] mapping multiple BARs Device node permissions: crw-rw+ 1 root video 226, 0 Feb 5 16:54 /dev/dri/card0 crw-rw-rw- 1 root root 195, 0 Feb 5 16:54 /dev/nvidia0 crw-rw-rw- 1 root root 195, 255 Feb 5 16:54 /dev/nvidiactl /dev/dri/by-path: total 0 lrwxrwxrwx 1 root root 8 Feb 5 16:54 pci-:01:00.0-card -> ../card0 video:*:44:jim Alternative 'nvidia': nvidia - auto mode link best version is /usr/lib/nvidia/legacy-340xx link currently points to /usr/lib/nvidia/legacy-340xx link nvidia is /usr/lib/nvidia/nvidia slave nvidia--20-nvidia-legacy-340xx.conf is /etc/X11/xorg.conf.d/20-nvidia-legacy-340xx.conf slave nvidia--libEGL.so.1-x86_64-linux-gnu is /usr/lib/x86_64-linux-gnu/nvidia/libEGL.so.1 slave nvidia--libGL.so.1-x86_64-linux-gnu is /usr/lib/x86_64-linux-gnu/nvidia/libGL.so.1 slave nvidia--libGLESv1_CM.so.1-x86_64-linux-gnu is /usr/lib/x86_64-linux-gnu/nvidia/libGLESv1_CM.so.1 slave nvidia--libGLESv2.so.2-x86_64-linux-gnu is /usr/lib/x86_64-linux-gnu/nvidia/libGLESv2.so.2 slave nvidia--libglx.so is /usr/lib/nvidia/libglx.so slave nvidia--libnvidia-ml.so.1-x86_64-linux-gnu is /usr/lib/x86_64-linux-gnu/libnvidia-ml.so.1 slave nvidia--libvdpau_nvidia.so.1-x86_64-linux-gnu is /usr/lib/x86_64-linux-gnu/vdpau/libvdpau_nvidia.so.1 slave nvidia--monitoring.conf is /usr/share/nvidia/monitoring.conf slave nvidia--nv-control-dpy is /usr/bin/nv-control-dpy slave nvidia--nvidia-blacklists-nouveau.conf is /etc/nvidia/nvidia-blacklists-nouveau.conf slave nvidia--nvidia-bug-report.sh is /usr/lib/nvidia/nvidia-bug-report.sh slave nvidia--nvidia-debugdump is /usr/bin/nvidia-debugdump slave nvidia--nvidia-drm-outputclass.conf is /etc/nvidia/nvidia-drm-outputclass.conf slave nvidia--nvidia-load.conf is /etc/nvidia/nvidia-load.conf slave nvidia--nvidia-modprobe.conf is /etc/nvidia/nvidia-modprobe.conf slave nvidia--nvidia-options.conf is /etc/modprobe.d/nvidia-options.conf slave nvidia--nvidia-settings is /usr/bin/nvidia-settings slave nvidia--nvidia-settings.1.gz is /usr/share/man/man1/nvidia-settings.1.gz slave nvidia--nvidia-settings.desktop is /usr/share/applications/nvidia-settings.desktop slave nvidia--nvidia-smi is /usr/bin/nvidia-smi slave nvidia--nvidia-smi.1.gz is /usr/share/man/man1/nvidia-smi.1.gz slave nvidia--nvidia_drv.so is /usr/lib/nvidia/nvidia_drv.so /usr/lib/nvidia/legacy-340xx - priority 340 slave nvidia--20-nvidia-legacy-340xx.conf:
Bug#1029681: nvidia-legacy-340xx-driver: Qt5 apps fail to launch with a segfault
Package: nvidia-legacy-340xx-driver Version: 340.108-17 Followup-For: Bug #1029681 X-Debbugs-Cc: pitsior...@outlook.com 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? -- Package-specific info: uname -a: Linux mitsos 6.1.0-2-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.1.7-1 (2023-01-18) x86_64 GNU/Linux /proc/version: Linux version 6.1.0-2-amd64 (debian-ker...@lists.debian.org) (gcc-12 (Debian 12.2.0-14) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40) #1 SMP PREEMPT_DYNAMIC Debian 6.1.7-1 (2023-01-18) /proc/driver/nvidia/version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 340.108 Wed Dec 11 11:06:58 PST 2019 GCC version: gcc version 12.2.0 (Debian 12.2.0-14) lspci 'display controller [030?]': 01:00.0 VGA compatible controller [0300]: NVIDIA Corporation G96C [GeForce 9500 GT] [10de:0640] (rev a1) (prog-if 00 [VGA controller]) Subsystem: XFX Pine Group Inc. G96C [GeForce 9500 GT] [1682:2412] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- Kernel driver in use: nvidia Kernel modules: nvidia dmesg: [0.187829] Console: colour VGA+ 80x25 [0.422587] pci :01:00.0: vgaarb: setting as boot VGA device [0.422587] pci :01:00.0: vgaarb: bridge control possible [0.422587] pci :01:00.0: vgaarb: VGA device added: decodes=io+mem,owns=io+mem,locks=none [0.422587] vgaarb: loaded [0.583824] Linux agpgart interface v0.103 [3.854564] nvidia: loading out-of-tree module taints kernel. [3.854629] nvidia: module license 'NVIDIA' taints kernel. [3.882969] nvidia: module verification failed: signature and/or required key missing - tainting kernel [3.958566] nvidia :01:00.0: vgaarb: changed VGA decodes: olddecodes=io+mem,decodes=none:owns=io+mem [3.962467] [drm] Initialized nvidia-drm 0.0.0 20150116 for :01:00.0 on minor 0 [3.962555] NVRM: loading NVIDIA UNIX x86_64 Kernel Module 340.108 Wed Dec 11 11:06:58 PST 2019 [6.532744] caller _nv000788rm+0xe4/0x1c0 [nvidia] mapping multiple BARs Device node permissions: crw-rw+ 1 root video 226, 0 Feb 2 19:21 /dev/dri/card0 crw-rw-rw- 1 root root 195, 0 Feb 2 19:21 /dev/nvidia0 crw-rw-rw- 1 root root 195, 255 Feb 2 19:21 /dev/nvidiactl /dev/dri/by-path: total 0 lrwxrwxrwx 1 root root 8 Feb 2 19:21 pci-:01:00.0-card -> ../card0 video:*:44:jim Alternative 'nvidia': nvidia - auto mode link best version is /usr/lib/nvidia/legacy-340xx link currently points to /usr/lib/nvidia/legacy-340xx link nvidia is /usr/lib/nvidia/nvidia slave nvidia--20-nvidia-legacy-340xx.conf is /etc/X11/xorg.conf.d/20-nvidia-legacy-340xx.conf slave nvidia--libEGL.so.1-x86_64-linux-gnu is /usr/lib/x86_64-linux-gnu/nvidia/libEGL.so.1 slave nvidia--libGL.so.1-x86_64-linux-gnu is /usr/lib/x86_64-linux-gnu/nvidia/libGL.so.1 slave nvidia--libGLESv1_CM.so.1-x86_64-linux-gnu is /usr/lib/x86_64-linux-gnu/nvidia/libGLESv1_CM.so.1 slave nvidia--libGLESv2.so.2-x86_64-linux-gnu is /usr/lib/x86_64-linux-gnu/nvidia/libGLESv2.so.2 slave nvidia--libglx.so is /usr/lib/nvidia/libglx.so slave nvidia--libnvidia-ml.so.1-x86_64-linux-gnu is /usr/lib/x86_64-linux-gnu/libnvidia-ml.so.1 slave nvidia--libvdpau_nvidia.so.1-x86_64-linux-gnu is /usr/lib/x86_64-linux-gnu/vdpau/libvdpau_nvidia.so.1 slave nvidia--monitoring.conf is /usr/share/nvidia/monitoring.conf slave nvidia--nv-control-dpy is /usr/bin/nv-control-dpy slave nvidia--nvidia-blacklists-nouveau.conf is /etc/nvidia/nvidia-blacklists-nouveau.conf slave nvidia--nvidia-bug-report.sh is /usr/lib/nvidia/nvidia-bug-report.sh slave nvidia--nvidia-debugdump is /usr/bin/nvidia-debugdump slave nvidia--nvidia-drm-outputclass.conf is /etc/nvidia/nvidia-drm-outputclass.conf slave nvidia--nvidia-load.conf is /etc/nvidia/nvidia-load.conf slave nvidia--nvidia-modprobe.conf is /etc/nvidia/nvidia-modprobe.conf slave nvidia--nvidia-options.conf is /etc/modprobe.d/nvidia-options.conf slave nvidia--nvidia-settings is /usr/bin/nvidia-settings slave nvidia--nvidia-settings.1.gz is
Bug#1029681: nvidia-legacy-340xx-driver: Qt5 apps fail to launch with a segfault
Package: nvidia-legacy-340xx-driver Version: 340.108-17 Followup-For: Bug #1029681 X-Debbugs-Cc: pitsior...@outlook.com 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. -- Package-specific info: uname -a: Linux mitsos 6.1.0-1-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.1.4-1 (2023-01-07) x86_64 GNU/Linux /proc/version: Linux version 6.1.0-1-amd64 (debian-ker...@lists.debian.org) (gcc-12 (Debian 12.2.0-13) 12.2.0, GNU ld (GNU Binutils for Debian) 2.39.90.20221231) #1 SMP PREEMPT_DYNAMIC Debian 6.1.4-1 (2023-01-07) /proc/driver/nvidia/version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 340.108 Wed Dec 11 11:06:58 PST 2019 GCC version: gcc version 12.2.0 (Debian 12.2.0-14) lspci 'display controller [030?]': 01:00.0 VGA compatible controller [0300]: NVIDIA Corporation G96C [GeForce 9500 GT] [10de:0640] (rev a1) (prog-if 00 [VGA controller]) Subsystem: XFX Pine Group Inc. G96C [GeForce 9500 GT] [1682:2412] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- Kernel driver in use: nvidia Kernel modules: nvidia dmesg: [0.187388] Console: colour VGA+ 80x25 [0.418950] pci :01:00.0: vgaarb: setting as boot VGA device [0.418950] pci :01:00.0: vgaarb: bridge control possible [0.418950] pci :01:00.0: vgaarb: VGA device added: decodes=io+mem,owns=io+mem,locks=none [0.420921] vgaarb: loaded [0.583281] Linux agpgart interface v0.103 [3.634074] nvidia: loading out-of-tree module taints kernel. [3.634137] nvidia: module license 'NVIDIA' taints kernel. [3.666341] nvidia: module verification failed: signature and/or required key missing - tainting kernel [3.711786] nvidia :01:00.0: vgaarb: changed VGA decodes: olddecodes=io+mem,decodes=none:owns=io+mem [3.712233] [drm] Initialized nvidia-drm 0.0.0 20150116 for :01:00.0 on minor 0 [3.712304] NVRM: loading NVIDIA UNIX x86_64 Kernel Module 340.108 Wed Dec 11 11:06:58 PST 2019 [6.390322] caller _nv000788rm+0xe4/0x1c0 [nvidia] mapping multiple BARs Device node permissions: crw-rw+ 1 root video 226, 0 Jan 27 12:07 /dev/dri/card0 crw-rw-rw- 1 root root 195, 0 Jan 27 12:07 /dev/nvidia0 crw-rw-rw- 1 root root 195, 255 Jan 27 12:07 /dev/nvidiactl /dev/dri/by-path: total 0 lrwxrwxrwx 1 root root 8 Jan 27 12:07 pci-:01:00.0-card -> ../card0 video:*:44:jim Alternative 'nvidia': nvidia - auto mode link best version is /usr/lib/nvidia/legacy-340xx link currently points to /usr/lib/nvidia/legacy-340xx link nvidia is /usr/lib/nvidia/nvidia slave nvidia--20-nvidia-legacy-340xx.conf is /etc/X11/xorg.conf.d/20-nvidia-legacy-340xx.conf slave nvidia--libEGL.so.1-x86_64-linux-gnu is /usr/lib/x86_64-linux-gnu/nvidia/libEGL.so.1 slave nvidia--libGL.so.1-x86_64-linux-gnu is /usr/lib/x86_64-linux-gnu/nvidia/libGL.so.1 slave nvidia--libGLESv1_CM.so.1-x86_64-linux-gnu is /usr/lib/x86_64-linux-gnu/nvidia/libGLESv1_CM.so.1 slave nvidia--libGLESv2.so.2-x86_64-linux-gnu is /usr/lib/x86_64-linux-gnu/nvidia/libGLESv2.so.2 slave nvidia--libglx.so is /usr/lib/nvidia/libglx.so slave nvidia--libnvidia-ml.so.1-x86_64-linux-gnu is /usr/lib/x86_64-linux-gnu/libnvidia-ml.so.1 slave nvidia--libvdpau_nvidia.so.1-x86_64-linux-gnu is /usr/lib/x86_64-linux-gnu/vdpau/libvdpau_nvidia.so.1 slave nvidia--monitoring.conf is /usr/share/nvidia/monitoring.conf slave nvidia--nv-control-dpy is /usr/bin/nv-control-dpy slave nvidia--nvidia-blacklists-nouveau.conf is /etc/nvidia/nvidia-blacklists-nouveau.conf slave
Bug#1029681: nvidia-legacy-340xx-driver: Qt5 apps fail to launch with a segfault
Package: nvidia-legacy-340xx-driver Version: 340.108-17 Followup-For: Bug #1029681 X-Debbugs-Cc: pitsior...@outlook.com 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. -- Package-specific info: uname -a: Linux mitsos 6.1.0-1-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.1.4-1 (2023-01-07) x86_64 GNU/Linux /proc/version: Linux version 6.1.0-1-amd64 (debian-ker...@lists.debian.org) (gcc-12 (Debian 12.2.0-13) 12.2.0, GNU ld (GNU Binutils for Debian) 2.39.90.20221231) #1 SMP PREEMPT_DYNAMIC Debian 6.1.4-1 (2023-01-07) /proc/driver/nvidia/version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 340.108 Wed Dec 11 11:06:58 PST 2019 GCC version: gcc version 12.2.0 (Debian 12.2.0-13) lspci 'display controller [030?]': 01:00.0 VGA compatible controller [0300]: NVIDIA Corporation G96C [GeForce 9500 GT] [10de:0640] (rev a1) (prog-if 00 [VGA controller]) Subsystem: XFX Pine Group Inc. G96C [GeForce 9500 GT] [1682:2412] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- Kernel driver in use: nvidia Kernel modules: nvidia dmesg: [0.187186] Console: colour VGA+ 80x25 [0.418756] pci :01:00.0: vgaarb: setting as boot VGA device [0.418756] pci :01:00.0: vgaarb: bridge control possible [0.418756] pci :01:00.0: vgaarb: VGA device added: decodes=io+mem,owns=io+mem,locks=none [0.420726] vgaarb: loaded [0.582766] Linux agpgart interface v0.103 [3.643051] nvidia: loading out-of-tree module taints kernel. [3.643115] nvidia: module license 'NVIDIA' taints kernel. [3.667623] nvidia: module verification failed: signature and/or required key missing - tainting kernel [3.717886] nvidia :01:00.0: vgaarb: changed VGA decodes: olddecodes=io+mem,decodes=none:owns=io+mem [3.724814] [drm] Initialized nvidia-drm 0.0.0 20150116 for :01:00.0 on minor 0 [3.724897] NVRM: loading NVIDIA UNIX x86_64 Kernel Module 340.108 Wed Dec 11 11:06:58 PST 2019 [6.387154] caller _nv000788rm+0xe4/0x1c0 [nvidia] mapping multiple BARs Device node permissions: crw-rw+ 1 root video 226, 0 Jan 27 06:35 /dev/dri/card0 crw-rw-rw- 1 root root 195, 0 Jan 27 06:35 /dev/nvidia0 crw-rw-rw- 1 root root 195, 255 Jan 27 06:35 /dev/nvidiactl /dev/dri/by-path: total 0 lrwxrwxrwx 1 root root 8 Jan 27 06:35 pci-:01:00.0-card -> ../card0 video:*:44:jim Alternative 'nvidia': nvidia - auto mode link best version is /usr/lib/nvidia/legacy-340xx link currently points to /usr/lib/nvidia/legacy-340xx link nvidia is /usr/lib/nvidia/nvidia slave nvidia--20-nvidia-legacy-340xx.conf is /etc/X11/xorg.conf.d/20-nvidia-legacy-340xx.conf slave nvidia--libEGL.so.1-x86_64-linux-gnu is /usr/lib/x86_64-linux-gnu/nvidia/libEGL.so.1 slave nvidia--libGL.so.1-x86_64-linux-gnu is /usr/lib/x86_64-linux-gnu/nvidia/libGL.so.1 slave nvidia--libGLESv1_CM.so.1-x86_64-linux-gnu is /usr/lib/x86_64-linux-gnu/nvidia/libGLESv1_CM.so.1 slave nvidia--libGLESv2.so.2-x86_64-linux-gnu is /usr/lib/x86_64-linux-gnu/nvidia/libGLESv2.so.2 slave nvidia--libglx.so is /usr/lib/nvidia/libglx.so slave nvidia--libnvidia-ml.so.1-x86_64-linux-gnu is /usr/lib/x86_64-linux-gnu/libnvidia-ml.so.1 slave nvidia--libvdpau_nvidia.so.1-x86_64-linux-gnu is /usr/lib/x86_64-linux-gnu/vdpau/libvdpau_nvidia.so.1 slave nvidia--monitoring.conf is /usr/share/nvidia/monitoring.conf slave nvidia--nv-control-dpy is /usr/bin/nv-control-dpy slave nvidia--nvidia-blacklists-nouveau.conf is /etc/nvidia/nvidia-blacklists-nouveau.conf slave nvidia--nvidia-bug-report.sh is /usr/lib/nvidia/nvidia-bug-report.sh slave nvidia--nvidia-debugdump is /usr/bin/nvidia-debugdump slave nvidia--nvidia-drm-outputclass.conf is /etc/nvidia/nvidia-drm-outputclass.conf slave
Bug#1029681: nvidia-legacy-340xx-driver: Qt5 apps fail to launch with a segfault
Package: nvidia-legacy-340xx-driver Version: 340.108-17 Followup-For: Bug #1029681 X-Debbugs-Cc: pitsior...@outlook.com 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. -- Package-specific info: uname -a: Linux mitsos 6.1.0-1-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.1.4-1 (2023-01-07) x86_64 GNU/Linux /proc/version: Linux version 6.1.0-1-amd64 (debian-ker...@lists.debian.org) (gcc-12 (Debian 12.2.0-13) 12.2.0, GNU ld (GNU Binutils for Debian) 2.39.90.20221231) #1 SMP PREEMPT_DYNAMIC Debian 6.1.4-1 (2023-01-07) /proc/driver/nvidia/version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 340.108 Wed Dec 11 11:06:58 PST 2019 GCC version: gcc version 12.2.0 (Debian 12.2.0-13) lspci 'display controller [030?]': 01:00.0 VGA compatible controller [0300]: NVIDIA Corporation G96C [GeForce 9500 GT] [10de:0640] (rev a1) (prog-if 00 [VGA controller]) Subsystem: XFX Pine Group Inc. G96C [GeForce 9500 GT] [1682:2412] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- Kernel driver in use: nvidia Kernel modules: nvidia dmesg: [0.189673] Console: colour VGA+ 80x25 [0.421289] pci :01:00.0: vgaarb: setting as boot VGA device [0.421289] pci :01:00.0: vgaarb: bridge control possible [0.421289] pci :01:00.0: vgaarb: VGA device added: decodes=io+mem,owns=io+mem,locks=none [0.421289] vgaarb: loaded [0.605637] Linux agpgart interface v0.103 [3.651150] nvidia: loading out-of-tree module taints kernel. [3.651272] nvidia: module license 'NVIDIA' taints kernel. [3.677313] nvidia: module verification failed: signature and/or required key missing - tainting kernel [3.723917] nvidia :01:00.0: vgaarb: changed VGA decodes: olddecodes=io+mem,decodes=none:owns=io+mem [3.725067] [drm] Initialized nvidia-drm 0.0.0 20150116 for :01:00.0 on minor 0 [3.725144] NVRM: loading NVIDIA UNIX x86_64 Kernel Module 340.108 Wed Dec 11 11:06:58 PST 2019 [6.414073] caller _nv000788rm+0xe4/0x1c0 [nvidia] mapping multiple BARs Device node permissions: crw-rw+ 1 root video 226, 0 Jan 26 18:15 /dev/dri/card0 crw-rw-rw- 1 root root 195, 0 Jan 26 18:15 /dev/nvidia0 crw-rw-rw- 1 root root 195, 255 Jan 26 18:15 /dev/nvidiactl /dev/dri/by-path: total 0 lrwxrwxrwx 1 root root 8 Jan 26 18:15 pci-:01:00.0-card -> ../card0 video:*:44:jim Alternative 'nvidia': nvidia - auto mode link best version is /usr/lib/nvidia/legacy-340xx link currently points to /usr/lib/nvidia/legacy-340xx link nvidia is /usr/lib/nvidia/nvidia slave nvidia--20-nvidia-legacy-340xx.conf is /etc/X11/xorg.conf.d/20-nvidia-legacy-340xx.conf slave nvidia--libEGL.so.1-x86_64-linux-gnu is /usr/lib/x86_64-linux-gnu/nvidia/libEGL.so.1 slave nvidia--libGL.so.1-x86_64-linux-gnu is /usr/lib/x86_64-linux-gnu/nvidia/libGL.so.1 slave nvidia--libGLESv1_CM.so.1-x86_64-linux-gnu is /usr/lib/x86_64-linux-gnu/nvidia/libGLESv1_CM.so.1 slave nvidia--libGLESv2.so.2-x86_64-linux-gnu is /usr/lib/x86_64-linux-gnu/nvidia/libGLESv2.so.2 slave nvidia--libglx.so is /usr/lib/nvidia/libglx.so slave nvidia--libnvidia-ml.so.1-x86_64-linux-gnu is /usr/lib/x86_64-linux-gnu/libnvidia-ml.so.1 slave nvidia--libvdpau_nvidia.so.1-x86_64-linux-gnu is /usr/lib/x86_64-linux-gnu/vdpau/libvdpau_nvidia.so.1 slave nvidia--monitoring.conf is /usr/share/nvidia/monitoring.conf slave nvidia--nv-control-dpy is /usr/bin/nv-control-dpy slave nvidia--nvidia-blacklists-nouveau.conf is /etc/nvidia/nvidia-blacklists-nouveau.conf slave nvidia--nvidia-bug-report.sh is /usr/lib/nvidia/nvidia-bug-report.sh slave nvidia--nvidia-debugdump is /usr/bin/nvidia-debugdump slave nvidia--nvidia-drm-outputclass.conf is /etc/nvidia/nvidia-drm-outputclass.conf slave nvidia--nvidia-load.conf is /etc/nvidia/nvidia-load.conf slave nvidia--nvidia-modprobe.conf is /etc/nvidia/nvidia-modprobe.conf slave nvidia--nvidia-options.conf is /etc/modprobe.d/nvidia-options.conf slave nvidia--nvidia-settings is /usr/bin/nvidia-settings slave nvidia--nvidia-settings.1.gz is /usr/share/man/man1/nvidia-settings.1.gz slave nvidia--nvidia-settings.desktop is
Bug#1018895: gcolor3: color picking fails due to No such interface “org.freedesktop.portal.Screenshot”
Package: gcolor3 Version: 2.4.0-2 Followup-For: Bug #1018895 X-Debbugs-Cc: pitsior...@outlook.com Thank you for verifying it on gnome. I can't see the benefit of installing the remaining xdg-desktop-portal packages. For instance, the one for kde wants to install a ton of kde packages and the wlr one wants to install pipewire etc. On the other hand, I found this patch on its github page which may be related to the issue. I am mentioning it here because all similar issues to the one above were reported to gtk-related flatpak apps too. https://github.com/Hjdskes/gcolor3/commit/6699c150468e3af14c6a6d411abe6b83b44b4304 -- System Information: Debian Release: bookworm/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 6.0.0-6-amd64 (SMP w/2 CPU threads; PREEMPT) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) Versions of packages gcolor3 depends on: ii libatk1.0-0 2.46.0-4 ii libc62.36-7 ii libcairo21.16.0-7 ii libgdk-pixbuf-2.0-0 2.42.10+dfsg-1 ii libglib2.0-0 2.74.4-1 ii libgtk-3-0 3.24.35-3 ii libportal-gtk3-1 0.6-4 ii libportal1 0.6-4 gcolor3 recommends no packages. gcolor3 suggests no packages. -- no debconf information
Bug#1018895: gcolor3: color picking fails due to No such interface “org.freedesktop.portal.Screenshot”
Package: gcolor3 Version: 2.4.0-2 Followup-For: Bug #1018895 X-Debbugs-Cc: pitsior...@outlook.com This bug affects me as well. I am on openbox under x11 and the packages xdg- desktop-portal and xdg-desktop-portal-gtk (as suggested elsewhere) were already installed on my end. I have also installed xdg-desktop-portal-gnome, which supposedly solves the issue, all it does here is to change the error to ** (gcolor3:673): WARNING **: 14:11:57.458: Failed to pick color: Screenshot failed Sadly, gcolor3's github does not allow issue reporting, because I would definitely report the issue there first. -- System Information: Debian Release: bookworm/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 6.0.0-6-amd64 (SMP w/2 CPU threads; PREEMPT) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) Versions of packages gcolor3 depends on: ii libatk1.0-0 2.46.0-4 ii libc62.36-7 ii libcairo21.16.0-7 ii libgdk-pixbuf-2.0-0 2.42.10+dfsg-1 ii libglib2.0-0 2.74.4-1 ii libgtk-3-0 3.24.35-3 ii libportal-gtk3-1 0.6-4 ii libportal1 0.6-4 gcolor3 recommends no packages. gcolor3 suggests no packages. -- no debconf information
Bug#1009998: gvfs-backends: Unable to access smb://host/sharing on any file manager after upgrade
Package: samba Followup-For: Bug #1009998 X-Debbugs-Cc: pitsior...@outlook.com The 4.16.2 upgrade reached testing a moment ago, so I tested my filemanager (pcmanfm, gtk version) for the issue. It can connect to smb://host/sharename (or smb://ip/sharename) but not to smb://host (or smb://ip) This means the user is not able to see the shares from the host but has to remember the name of each share in order to connect to it and also do that by typing its name in the address bar. Does this happen to you as well? -- System Information: Debian Release: bookworm/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 5.17.0-3-amd64 (SMP w/2 CPU threads; PREEMPT) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages samba depends on: ii adduser 3.121 ii init-system-helpers 1.63 ii libbsd0 0.11.6-1 ii libc62.33-7 ii libcups2 2.4.2-1 ii libgnutls30 3.7.4-2 ii libldap-2.5-02.5.12+dfsg-2 ii libldb2 2:2.5.1+samba4.16.2-1 ii libpam-modules 1.4.0-13 ii libpam-runtime 1.4.0-13 ii libpopt0 1.18-3 ii libtalloc2 2.3.3-4 ii libtasn1-6 4.18.0-4 ii libtdb1 1.4.6-3 ii libtevent0 0.12.0-1 ii lsb-base 11.2 ii procps 2:3.3.17-7+b1 ii python3 3.10.4-1+b1 pn python3-dnspython pn python3-samba ii samba-common 2:4.16.2+dfsg-1 pn samba-common-bin ii samba-libs 2:4.16.2+dfsg-1 pn tdb-tools Versions of packages samba recommends: pn attr ii logrotate 3.20.1-1 pn python3-markdown pn samba-dsdb-modules pn samba-vfs-modules Versions of packages samba suggests: pn bind9 pn bind9utils pn ctdb pn ldb-tools pn ntp | chrony pn smbldap-tools pn ufw pn winbind
Bug#1009998: gvfs-backends: Unable to access smb://host/sharing on any file manager after upgrade
Source: gvfs Followup-For: Bug #1009998 X-Debbugs-Cc: pitsior...@outlook.com You are right about that. However, the bug is a problem of gvfs that does not work with samba 4.16 and not the other way round, because smbclient works as it should. I am still expecting an upstream patch or an upgrade on gvfs that would solve it, but since most popular distros are not yet on 4.16, I guess there is not much feedback and need to solve it. Anyway, samba was upgraded to 4.16.2 today from upstream and its changelog mentions something about smbclient, so I hope it is finally fixed. Can you please show me the relevant bug report under samba so as to bookmark it? Thank you. p.s. I would not be that upset for the bug if it wasn't for my workflow that demands access to samba shares at least every second day. -- System Information: Debian Release: bookworm/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 5.17.0-1-amd64 (SMP w/2 CPU threads; PREEMPT) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) -- no debconf information
Bug#1009998: gvfs-backends: Unable to access smb://host/sharing on any file manager after upgrade
Package: gvfs-backends Version: 1.50.2-1 Followup-For: Bug #1009998 X-Debbugs-Cc: pitsior...@outlook.com One month since I posted the relavant patch for samba, 2 minor upgrades for samba and 1 major upgrade for gvfs later and the problem is still there (at least on my end)! -- System Information: Debian Release: bookworm/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 5.17.0-1-amd64 (SMP w/2 CPU threads; PREEMPT) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages gvfs-backends depends on: ii dconf-gsettings-backend [gsettings-backend] 0.40.0-3 ii gvfs 1.50.2-1 ii gvfs-common 1.50.2-1 ii gvfs-daemons 1.50.2-1 ii gvfs-libs1.50.2-1 ii libarchive13 3.6.0-1 ii libavahi-client3 0.8-5 ii libavahi-common3 0.8-5 ii libavahi-glib1 0.8-5 ii libc62.33-7 ii libcdio-cdda210.2+2.0.1-dmo1 ii libcdio-paranoia210.2+2.0.1-dmo1 ii libcdio191:2.1.0-dmo3 ii libgcrypt20 1.10.1-2 ii libgdata22 0.18.1-2 ii libglib2.0-0 2.72.1-1 ii libgoa-1.0-0b3.44.0-1 ii libgphoto2-6 2.5.29-1 ii libgphoto2-port122.5.29-1 ii libgudev-1.0-0 237-2 ii libimobiledevice61.3.0-6+b1 ii libmtp9 1.1.19-1 ii libnfs13 1:4.0.0-dmo1 ii libplist32.2.0-6+b1 ii libpolkit-gobject-1-00.105-33 ii libsmbclient 2:4.16.1+dfsg-6 ii libsoup-3.0-03.0.6-1 ii libusb-1.0-0 2:1.0.26-1 ii libxml2 2.9.14+dfsg-1 ii psmisc 23.5-1 Versions of packages gvfs-backends recommends: ii gnome-keyring 42.1-1 Versions of packages gvfs-backends suggests: pn bluez-obexd ii samba-common 2:4.16.1+dfsg-6 -- no debconf information
Bug#1009998: gvfs-backends: Unable to access smb://host/sharing on any file manager after upgrade
Package: gvfs-backends Version: 1.50.1-1 Followup-For: Bug #1009998 X-Debbugs-Cc: pitsior...@outlook.com So, I was hoping that yesterday's update to 1.50.1 (in testing) would solve the issue, but nothing changed. Likewise, it was not solved with today's upgrade for samba (in unstable) to 4.16.1+dfsg-4. On the other hand, the relevant issue on arch's bug tracker (https://bugs.archlinux.org/task/74259) was closed with this patch here. https://gitlab.com/samba- team/samba/-/commit/34771e1931587807d0395c7ac7f4be18654997f4 How about getting this patch for debian too? -- System Information: Debian Release: bookworm/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 5.17.0-1-amd64 (SMP w/2 CPU threads; PREEMPT) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages gvfs-backends depends on: ii dconf-gsettings-backend [gsettings-backend] 0.40.0-3 ii gvfs 1.50.1-1 ii gvfs-common 1.50.1-1 ii gvfs-daemons 1.50.1-1 ii gvfs-libs1.50.1-1 ii libarchive13 3.6.0-1 ii libavahi-client3 0.8-5 ii libavahi-common3 0.8-5 ii libavahi-glib1 0.8-5 ii libc62.33-7 ii libcdio-cdda210.2+2.0.1-dmo1 ii libcdio-paranoia210.2+2.0.1-dmo1 ii libcdio191:2.1.0-dmo3 ii libgcrypt20 1.10.1-2 ii libgdata22 0.18.1-2 ii libglib2.0-0 2.72.1-1 ii libgoa-1.0-0b3.44.0-1 ii libgphoto2-6 2.5.27-1 ii libgphoto2-port122.5.27-1 ii libgudev-1.0-0 237-2 ii libimobiledevice61.3.0-6+b1 ii libmtp9 1.1.19-1 ii libnfs13 1:4.0.0-dmo1 ii libplist32.2.0-6+b1 ii libpolkit-gobject-1-00.105-33 ii libsmbclient 2:4.16.1+dfsg-3 ii libsoup-3.0-03.0.6-1 ii libusb-1.0-0 2:1.0.26-1 ii libxml2 2.9.14+dfsg-1 ii psmisc 23.4-2 Versions of packages gvfs-backends recommends: ii gnome-keyring 40.0-3 Versions of packages gvfs-backends suggests: pn bluez-obexd ii samba-common 2:4.16.1+dfsg-3 -- no debconf information
Bug#1006616: firefox: new upstream version
Package: firefox
Version: 96.0.3-1
Followup-For: Bug #1006616
X-Debbugs-Cc: pitsior...@outlook.com
Dear Maintainer,
First of all, I know that firefox 97 requires rustc, cargo and nss to build.
How about updating those 3 and building firefox 97+ for the experimental repo?
It is not just to get "the latest and greatest" but to close critical security
issues like the ones discovered here
https://www.mozilla.org/en-US/security/advisories/mfsa2022-09/
Like the user that opened this report, I am on debian testing and I use
unstable for firefox and a few other packages.
-- Package-specific info:
-- Extensions information
Name: Add-ons Search Detection
Location: /usr/lib/firefox/browser/omni.ja
Package: firefox
Status: enabled
Name: Amazon.co.uk
Location: /usr/lib/firefox/browser/omni.ja
Package: firefox
Status: enabled
Name: Amazon.com
Location: /usr/lib/firefox/browser/omni.ja
Package: firefox
Status: enabled
Name: Bing
Location: /usr/lib/firefox/browser/omni.ja
Package: firefox
Status: enabled
Name: Dark theme
Location: /usr/lib/firefox/browser/omni.ja
Package: firefox
Status: user-disabled
Name: DoH Roll-Out
Location: /usr/lib/firefox/browser/features/doh-roll...@mozilla.org.xpi
Package: firefox
Status: enabled
Name: DuckDuckGo
Location: /usr/lib/firefox/browser/omni.ja
Package: firefox
Status: enabled
Name: eBay
Location: /usr/lib/firefox/browser/omni.ja
Package: firefox
Status: enabled
Name: Firefox Alpenglow theme
Location: /usr/lib/firefox/browser/omni.ja
Package: firefox
Status: user-disabled
Name: Firefox Screenshots
Location: /usr/lib/firefox/browser/features/screensh...@mozilla.org.xpi
Package: firefox
Status: enabled
Name: Form Autofill
Location: /usr/lib/firefox/browser/features/formautof...@mozilla.org.xpi
Package: firefox
Status: enabled
Name: Google
Location: /usr/lib/firefox/browser/omni.ja
Package: firefox
Status: enabled
Name: Light theme
Location: /usr/lib/firefox/browser/omni.ja
Package: firefox
Status: user-disabled
Name: Picture-In-Picture
Location: /usr/lib/firefox/browser/features/pictureinpict...@mozilla.org.xpi
Package: firefox
Status: enabled
Name: Privacy Redirect
Location: ${PROFILE_EXTENSIONS}/{b7f9d2cd-d772-4302-8c3f-eb941af36f76}.xpi
Status: enabled
Name: Proxy Failover
Location: /usr/lib/firefox/browser/features/proxy-failo...@mozilla.com.xpi
Package: firefox
Status: enabled
Name: System theme — auto theme
Location: /usr/lib/firefox/omni.ja
Package: firefox
Status: enabled
Name: uBlock Origin
Location: ${PROFILE_EXTENSIONS}/ublo...@raymondhill.net.xpi
Status: enabled
Name: Video DownloadHelper
Location: ${PROFILE_EXTENSIONS}/{b9db16a4-6edc-47ec-a1f4-b86292ed211d}.xpi
Status: enabled
Name: Web Compatibility Interventions
Location: /usr/lib/firefox/browser/features/webcom...@mozilla.org.xpi
Package: firefox
Status: enabled
Name: WebCompat Reporter
Location: /usr/lib/firefox/browser/features/webcompat-repor...@mozilla.org.xpi
Package: firefox
Status: user-disabled
Name: Wikipedia (en)
Location: /usr/lib/firefox/browser/omni.ja
Package: firefox
Status: enabled
-- Addons package information
ii firefox96.0.3-1 amd64Mozilla Firefox web browser
-- System Information:
Debian Release: bookworm/sid
APT prefers testing
APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 5.16.0-3-amd64 (SMP w/2 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE,
TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages firefox depends on:
ii debianutils 5.7-0.1
ii fontconfig 2.13.1-4.4
ii libatk1.0-0 2.36.0-3
ii libc62.33-7
ii libcairo-gobject21.16.0-5
ii libcairo21.16.0-5
ii libdbus-1-3 1.14.0-1
ii libdbus-glib-1-2 0.112-2
ii libevent-2.1-7 2.1.12-stable-1
ii libffi8 3.4.2-4
ii libfontconfig1 2.13.1-4.4
ii libfreetype6 2.11.1+dfsg-1
ii libgcc-s112-20220302-1
ii libgdk-pixbuf-2.0-0 2.42.6+dfsg-2
ii libglib2.0-0 2.70.4-1
ii libgtk-3-0 3.24.31-1
ii libnspr4 2:4.32-3
ii libnss3 2:3.75-1
ii libpango-1.0-0 1.50.4+ds-1
ii libstdc++6 12-20220302-1
ii libvpx7 1.11.0-2
ii libx11-6 2:1.7.2-2+b1
ii libx11-xcb1 2:1.7.2-2+b1
ii libxcb-shm0 1.14-3
ii libxcb1 1.14-3
ii libxcomposite1 1:0.4.5-1
ii libxdamage1 1:1.1.5-2
ii libxext6 2:1.3.4-1
ii libxfixes3 1:6.0.0-1
ii libxrandr2 2:1.5.2-1
ii libxtst6 2:1.2.3-1
ii procps 2:3.3.17-6
ii zlib1g 1:1.2.11.dfsg-2
Versions of packages firefox recommends:
ii libavcodec58 10:4.4.1-dmo4
Versions of packages firefox suggests:
pn fonts-lmodern
Bug#989010: linux-image-5.10.0-7-amd64: No display (post, grub, boot messages and desktop) after the upgrade to 5.10.38
Source: linux Followup-For: Bug #989010 X-Debbugs-Cc: pitsior...@outlook.com Preface: In case I did not mention it above, I had a suspicion that the issue might be related to cpu frequency scaling. 1+ month has passed with 5.15. The blank screen issue appeared a few more times the following days. A couple of days later, I decided to disable cpufrequtils, which set my frequency scheduler to schedutil (from ondemand). And the issue has not happened since then! Then I checked debian wiki, which says that cpufrequtils is replaced in favor of cpupower, so I removed it completely and installed cpupower (linux-cpupower package). However, cpupower in debian does not come with a systemd service and it does not have /etc/default/cpupower so as to set a desired governor. I really need such functionality, because as I have said, I set my governor to powersave from May to September every year and now I have no way to. -- System Information: Debian Release: bookworm/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 5.15.0-3-amd64 (SMP w/2 CPU threads) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system)
Bug#989010: linux-image-5.10.0-7-amd64: No display (post, grub, boot messages and desktop) after the upgrade to 5.10.38
Source: linux Followup-For: Bug #989010 X-Debbugs-Cc: pitsior...@outlook.com And it just happened again, on the very first boot of the day, as if nothing has changed since May. I was right for not upgrading past 5.10.28 all those months. -- System Information: Debian Release: bookworm/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 5.15.0-2-amd64 (SMP w/2 CPU threads) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system)
Bug#992216: thunderbird: Version 91 available upstream and fixes security problems
Package: thunderbird Version: 1:91.0~b5-1 Followup-For: Bug #992216 X-Debbugs-Cc: pitsior...@outlook.com Although I agree with what you say about security, please consider uploading v91 to experimental, like you already do for firefox-esr. For anyone that is on 91b5, the upgrade to v91 as stable will come in November, when v78.x will be eol. By then, v91 will probably be on 91.3.x and debian's package of 91b5 will probaly have a few dozens of security holes. Downgrading to 78.x so as not to miss those security updates is not an option because it will definitely cause issues with a profile made/used in a newer version. Not even mozilla supports downgrading for that reason! And no, downgrading to 78.x, deleting profiles etc from 91.x and starting fresh is not an option, at least for me.
Bug#992410: move of /bin/run-parts to /usr/bin breaks network with ifup
Package: debianutils Followup-For: Bug #992410 X-Debbugs-Cc: pitsior...@outlook.com I second to that. It happened on my i686 pc that runs unstable. As a workaround, one can symlink /usr/bin/run-parts to /bin/run-parts ln -s /usr/bin/run-parts /bin/run-parts and network.service comes up as usual.
Bug#989010: linux-image-5.10.0-7-amd64: No display (post, grub, boot messages and desktop) after the upgrade to 5.10.38
Source: linux Followup-For: Bug #989010 X-Debbugs-Cc: pitsior...@gmail.com One thing I noticed this weekend. Time it took for 5.10.38/40 to reach testing from unstable: 7 days, despite this awful bug here. Time it took for 5.10.46 to reach testing from unstable: 20+ days and still counting. Please do not mention freeze as an excuse. Debian has been in hard freeze since March, so I doubt that some "full freeze policy" has to do anything with it. Imho, one more release critical bug like this one would delay the release of bullseye even more, so you just marked it as important and let it be until it is "magically" solved one day. "Quality" testing... In other news, I asked an experienced linux user to have a look at my logs and he said there is nothing unusual. He also asked if there is a copy of /var/log/kern.log from those problematic boots, but unfortunately there is none right now. If I knew, I would have kept a copy. Once again, a random user offered me more support that the debian kernel team... on an issue that has to do with the kernel which is built from that team.
Bug#990631: thunderbird: Preferences tab is completely blank after the upgrade to 90b2
Package: thunderbird Version: 1:90.0~b2-1 Followup-For: Bug #990631 X-Debbugs-Cc: pitsior...@gmail.com One minor update. My friend, the arch user, built thunderbird beta (91b1 as of yesterday) from source and he reports that the blank preferences issue is now gone there. So, please package 91b1 for the repo and I will do the testing.
Bug#990631: thunderbird: Preferences tab is completely blank after the upgrade to 90b2
Package: thunderbird Version: 1:90.0~b2-1 Followup-For: Bug #990631 X-Debbugs-Cc: pitsior...@gmail.com Any chance of fixing this? I found the reason for the egl errors (it's webrender that is being forced by default). But there is no way to access about:config and disable it, because it has to be opened through about:preferences. I tried disabling it by creating a user.js file and setting the preference in there manually, but I had no luck. Then I learned about prefs.js, so I made a file, added the preference there too and it messed up my tb! So now I am setting it up from scratch. Sadly, some settings, e.g. font size and time before rss entries are deleted etc that interest me, can only be set by about:preferences.
Bug#989010: linux-image-5.10.0-7-amd64: No display (post, grub, boot messages and desktop) after the upgrade to 5.10.38
Source: linux Followup-For: Bug #989010 X-Debbugs-Cc: pitsior...@gmail.com There are 2 words that can completely justify my "appaling lack of respect for debian developers": hardware failure. And it happened not once, but twice. Plus, the support I received from here is non existant in every troubleshooting step I made. Do you see any response now that the requested logs are at anyone's disposal? Did you see anyone replying on how will I get those logs when I asked before? Did you see any meaningful response to why did a card that had nothing to do with the nvidia driver (the ati one) died after a few boots with 5.10.38/40? No to all I guess. So, do you still call all that "support"? Because I definitely don't. All I see is an "nvidia is bad" attitude which has no foundations. On the other hand, the only good thing all this... condition has caused is for me to see how bad nouveau is compared to nvidia. I already knew it was bad before that, but now I have experienced it and I can judge it from every aspect. Tomorrow marks 30 full days and ~100 boots without a single issue and that is because I stayed on 5.10.28. I would try a newer kernel if I could afford a new card. Unfortunately I don't. I will stick to it as much as I can, but, as I see it, in the very end, I will probably upgrade straight to 5.13+ or move to arch. The latter seems more probable btw. Last but not least, for me, this issue remains of critical severity despite the downgrade it got. And I am sure if anyone of you faced the same you would have a similar attitude. Have a nice day. p.s. In case anyone is wondering why arch and not some other distro like opensuse or fedora or anything, the reason is simple. Arch, via aur, can still provide me with nvidia 340, the other distros can't.
Bug#990631: thunderbird: Preferences tab is completely blank after the upgrade to 90b2
Package: thunderbird Version: 1:90.0~b2-1 Followup-For: Bug #990631 X-Debbugs-Cc: pitsior...@gmail.com First things first, I missed message #20. It seems that the errors on the terminal are identical for ff 89 and tb 90b2 and, imho, irrelevant to the preferences tab issue. I do think nvidia is the culprit too and I will try to troubleshoot it on my own. So far I have enabled/disabled hardware acceleration and webgl with no luck. I will keep looking. I am sure it has to do with the proton redesign. I tried the binary that mozilla provides and the preferences tab opens there with no issues at all (fresh profile etc). The output in the terminal is the same though. My friend (arch user) also has tried both the binary and compiling it from source. And he mentions the same: the preferences tab opens at the binary but not at the compiled one. In both systems, the error console (ctrl+shift+j) reports this error Uncaught ReferenceError: XPCOMUtils is not defined chrome://messenger/content/preferences/preferences.js:37 and a link below that that leads here, which is too complicated for us to understand. I hope the above error helps though. https://developer.mozilla.org/en- US/docs/Web/JavaScript/Reference/Errors/Not_defined Last but not least, I also use the esr versions of tb (but not of ff), but once a year, when the new tb version is nearing its release, I switch to the beta one to see what is new. And to find issues like this one too, so as to report them early. To be honest, last time I used the preferences dialog was a couple of years ago that I wanted to make the font for my (incoming and outgoing) emails bigger and prettier. The default one was some tiny monospace one that looked bad. And I have not opened the preferences tab since then.
Bug#990631: thunderbird: Preferences tab is completely blank after the upgrade to 90b2
Package: thunderbird Version: 1:90.0~b2-1 Followup-For: Bug #990631 X-Debbugs-Cc: pitsior...@gmail.com So, a friend lended me his vm with debian unstable + gnome. Gnome defaults to wayland, but it can be configured to run on xorg too. Selecting either session (gnome or gnome on xorg) makes no difference for thunderbird. The preferences page remains blank, so the issue applies to tb 90b2 regardless of vga driver or display server. On the other hand, there are no messages when it is run from the terminal. Last but not least, tb on that installation was also on 78.11, but uncofigured, and upgraded to 90b2 a few minutes ago. It was also tested with a fresh profile. Unrelated to the above, but I noticed that firefox 89 also pops the same output when it is run from the terminal.
Bug#990631: thunderbird: Preferences tab is completely blank after the upgrade to 90b2
Package: thunderbird Version: 1:90.0~b2-1 Followup-For: Bug #990631 X-Debbugs-Cc: pitsior...@gmail.com You are right about nvidia, but I do not use wayland... And I probably won't be using it until it becomes as stable as xorg. Also, my card supports up to opengl 3.3, if this is the case. I found the report in bugzilla after I opened this bug report here and I have also tried launching it after setting this export MOZ_X11_EGL=1 but it still has the same issue. Does tb 90b2 show the preferences menu as usual in your setup?
Bug#990631: thunderbird: Preferences tab is completely blank after the upgrade to 90b2
Package: thunderbird Version: 1:90.0~b2-1 Severity: important X-Debbugs-Cc: pitsior...@gmail.com Dear Maintainer, I upgraded to 90b2 (from 78.11) a few minutes ago, because I really wanted to see if tb has adopted that proton redesign ff 89 introduced. It hasn't (yet). And I noticed that every single submenu under edit > preferences is now blank (attached image). And the same thing happens with a fresh profile. Launching it from the terminal shows these errors, althought I think they are irrelevant $ thunderbird [GFX1-]: glxtest: eglBindAPI returned an error [GFX1-]: glxtest: libEGL missing eglGetDisplayDriverName -- System Information: Debian Release: 11.0 APT prefers testing APT policy: (990, 'testing'), (500, 'testing-security'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 5.10.0-6-amd64 (SMP w/2 CPU threads) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages thunderbird depends on: ii debianutils 4.11.2 ii fontconfig 2.13.1-4.2 ii libatk1.0-0 2.36.0-2 ii libbotan-2-172.17.3+dfsg-2 ii libbz2-1.0 1.0.8-4 ii libc62.31-12 ii libcairo-gobject21.16.0-5 ii libcairo21.16.0-5 ii libdbus-1-3 1.12.20-2 ii libdbus-glib-1-2 0.110-6 ii libevent-2.1-7 2.1.12-stable-1 ii libffi7 3.3-6 ii libfontconfig1 2.13.1-4.2 ii libfreetype6 2.10.4+dfsg-1 ii libgcc-s110.2.1-6 ii libgdk-pixbuf-2.0-0 2.42.2+dfsg-1 ii libglib2.0-0 2.66.8-1 ii libgtk-3-0 3.24.24-4 ii libicu67 67.1-6 ii libjson-c5 0.15-2 ii libnspr4 2:4.29-1 ii libnss3 2:3.67-1 ii libpango-1.0-0 1.46.2-3 ii libstdc++6 10.2.1-6 ii libvpx6 1.10.0+really1.8.1-dmo1 ii libx11-6 2:1.7.1-1 ii libx11-xcb1 2:1.7.1-1 ii libxcb-shm0 1.14-3 ii libxcb1 1.14-3 ii libxext6 2:1.3.3-1.1 ii libxrender1 1:0.9.10-1 ii psmisc 23.4-2 ii x11-utils7.7+5 ii zlib1g 1:1.2.11.dfsg-2 Versions of packages thunderbird recommends: pn myspell-en-us | hunspell-dictionary | myspell-dictionary Versions of packages thunderbird suggests: pn apparmor pn fonts-lyx ii libgssapi-krb5-2 1.18.3-5 ii libgtk2.0-0 2.24.33-2
Bug#989010: linux-image-5.10.0-7-amd64: No display (post, grub, boot messages and desktop) after the upgrade to 5.10.38
Source: linux Followup-For: Bug #989010 X-Debbugs-Cc: pitsior...@gmail.com I noticed that 5.10.46 reached unstable yesterday. If it was not for this issue, I would have already upgraded, like I udually do when a kernel upgrade comes out. However, this time I had to check the config file for that -8 upgrade. And the only difference between -7 and -8 is this version number. The build flags, and I mean ALL of them, are EXACTLY the same. So, since I have no other gpus to sacrifice, I won't risk it again. If anyone with more experience can inform me about the worthy changes, please do. All I can see in the changelog that might be related is this bit - [x86] nmi_watchdog: Fix old-style NMI watchdog regression on old Intel CPUs If there is any more info on that change, please show me. In other news, the gpu that half-survived (gt210) was tested on a last year's ryzen pc (with windows though) and it boots and works fine. It was tested for ~1 hour with no issues.
Bug#989010: linux-image-5.10.0-7-amd64: No display (post, grub, boot messages and desktop) after the upgrade to 5.10.38
Source: linux Followup-For: Bug #989010 X-Debbugs-Cc: pitsior...@gmail.com Finally, a sane reply that does not blame nvidia's driver. I have written above that something must have changed, at least regarding intel hw, because I was missing the coretemp readings on my conky. However, from the page you mention, only 2 commits refer to intel and I think both of them are not related to my hardware. If it is a kernel issue, which means I will come accross it on any distro I choose, I should report it on kernel's github page... if it had issue reports. Besides that, I think I am not smart enough to do it. I reported an similar issue on openssh (bug 912087) some years ago, but I just could not follow the conversation until it was resolved, because it was way too technical for me. Shouldn't a maintainer do that for me like they did for openssh? Now they have all the logs they need. The other solution, hopefully, is to wait for the freeze to end, debian to move to 5.12 or newer and me praying it won't have the same issue.
Bug#989010: linux-image-5.10.0-7-amd64: No display (post, grub, boot messages and desktop) after the upgrade to 5.10.38
Source: linux Followup-For: Bug #989010 X-Debbugs-Cc: pitsior...@gmail.com One more week passed with no issues. That's how things are when a kernel works as it should and the gpu driver is flawless. Stability that matches the one of a really stable distro or the one of windows 7. As I expected, there were no replies on my issue, even now that you have full logs of what was going on. Maybe it was because I did not raise the severity to critical, so as to "force" you look at it. Or, one simple word, incompetence. You just want to blame others' configurations for your faulty builds and hide your irresponsibilities behind words like "tainted", admit it. As for the cards, now that they were tested by a different person, the ati is totally dead and the nvidia one fails to build on 8 out of 10 times. So it is not my hardware that makes them "seem dead". They ARE dead, thanks to that garbage kernel update you made. I read today that debian 11 will be released by the end of July, so I hope there will be at least one more kernel upgrade until then. I will check if any of the kernel parameters have changed by then and I will consider testing it again.
Bug#989010: linux-image-5.10.0-7-amd64: No display (post, grub, boot messages and desktop) after the upgrade to 5.10.38
Source: linux Followup-For: Bug #989010 X-Debbugs-Cc: pitsior...@gmail.com About the logs. Did anyone of you reply to my question "where can I find those logs?" and I missed it? All I have found, again BY MYSELF, is this file here that when I run cat on it, gibberish shows up in the terminal. I can zip it and send it to you if you want to examine it. # du -h /var/log/journal/somenumbersandletters/system.journal 25M /var/log/journal/somenumbersandletters/system.journal I have no idea what it may contain, because if it stores the logs from last 50 boots, it has been 2 weeks now and I boot my pc ~3 times a day, so most of those logs are probably gone. As for the hardware, it has been almost a week now that it works flawlessly with another nvidia gpu and 5.10.28 + nvidia 340xx. Can you imagine how boring it is to press the power button and see your pc boot just fine instead of checking the monitor to see if post/grub/boot messages/desktop showed up? How come this piece of hw did not become flaky, and the ones before it became just after one day of running with the new kernel? And what about nouveau and radeon? Running the "untainted" kernel on those (now broken) gpus did not do a single thing. Neither the nvidia continued to work, nor ati was saved from dying after the upgrade. About the "lots of bug reports about nvidia". Out of the 900+ (according to popcon) people (or systems) that run nvidia 340xx, how many of them do you think run testing/unstable? Judging from the feedback I get on my bug reports on every new kernel on which nvidia 340xx fails to build, I would say me plus 2 or 3 more. And those 2-3 people probably have different hardware than me, e.g. amd cpu and amd chipset, so the issue may not occur on their setups. As for the why use nvidia's driver? Because in order to prefer nvidia over nouvau you need to have demands and standards. If a simple user sees nouveau draw its 2d desktop fine, he will say it is enough for him. But, unlike that simple user, I, "unfortunately", want my driver to do hardware decoding on videos (we have 2021 and not 2010, so this should have been a standard now for all drivers), 3d and powersaving (also something that should be a standard). Do you now see the difference between something that "works" and something that works 110%? That's why I insist on nvidia's driver.
Bug#989010: linux-image-5.10.0-7-amd64: No display (post, grub, boot messages and desktop) after the upgrade to 5.10.38
Source: linux Followup-For: Bug #989010 X-Debbugs-Cc: pitsior...@gmail.com To no surprise, the severity was lowered again. Without a single suggestion or reason, again. Imho, that is the usual incompetence most devs here show, so I am not surprised. It's a real shame however for a distro this size. The attached file contains all the changes you devs have made in the kernel configs from 5.10.28 (-6 package) to 5.10.38/.40 (-7 package). It was made with meld. ~10 kernel parameters have changed and led to this mess, so I assume it would be trivial for you to find the faulty one. I bet on the ones related to intel, because my system's cpu and chipset are both made by intel. p.s.1 I apologize to those few devs that actually helped with the issues I have reported all those years. You really stand out of this mess and you will always have my respect. p.s.2 Above, I meant to write "it (= my psu) is NEWER than 5.10 is on debian". --- /boot/config-5.10.0-6-amd64 +++ /home/jim/config-5.10.0-7-amd64 @@ -1,6 +1,6 @@ # # Automatically generated file; DO NOT EDIT. -# Linux/x86 5.10.28 Kernel Configuration +# Linux/x86 5.10.40 Kernel Configuration # CONFIG_CC_VERSION_TEXT="gcc-10 (Debian 10.2.1-6) 10.2.1 20210110" CONFIG_CC_IS_GCC=y @@ -23,7 +23,7 @@ # CONFIG_COMPILE_TEST is not set CONFIG_LOCALVERSION="" # CONFIG_LOCALVERSION_AUTO is not set -CONFIG_BUILD_SALT="5.10.0-6-amd64" +CONFIG_BUILD_SALT="5.10.0-7-amd64" CONFIG_HAVE_KERNEL_GZIP=y CONFIG_HAVE_KERNEL_BZIP2=y CONFIG_HAVE_KERNEL_LZMA=y @@ -2464,8 +2464,8 @@ CONFIG_ALTERA_STAPL=m CONFIG_INTEL_MEI=m CONFIG_INTEL_MEI_ME=m -# CONFIG_INTEL_MEI_TXE is not set -# CONFIG_INTEL_MEI_HDCP is not set +CONFIG_INTEL_MEI_TXE=m +CONFIG_INTEL_MEI_HDCP=m CONFIG_VMWARE_VMCI=m # CONFIG_GENWQE is not set # CONFIG_ECHO is not set @@ -3939,7 +3939,7 @@ CONFIG_RMI4_F12=y CONFIG_RMI4_F30=y CONFIG_RMI4_F34=y -# CONFIG_RMI4_F3A is not set +CONFIG_RMI4_F3A=y # CONFIG_RMI4_F54 is not set CONFIG_RMI4_F55=y @@ -6303,7 +6303,7 @@ # CONFIG_SND_SOC_IMG is not set CONFIG_SND_SOC_INTEL_SST_TOPLEVEL=y CONFIG_SND_SOC_INTEL_SST=m -# CONFIG_SND_SOC_INTEL_CATPT is not set +CONFIG_SND_SOC_INTEL_CATPT=m CONFIG_SND_SST_ATOM_HIFI2_PLATFORM=m # CONFIG_SND_SST_ATOM_HIFI2_PLATFORM_PCI is not set CONFIG_SND_SST_ATOM_HIFI2_PLATFORM_ACPI=m @@ -6323,6 +6323,10 @@ CONFIG_SND_SOC_ACPI_INTEL_MATCH=m CONFIG_SND_SOC_INTEL_MACH=y CONFIG_SND_SOC_INTEL_USER_FRIENDLY_LONG_NAMES=y +CONFIG_SND_SOC_INTEL_HASWELL_MACH=m +CONFIG_SND_SOC_INTEL_BDW_RT5650_MACH=m +CONFIG_SND_SOC_INTEL_BDW_RT5677_MACH=m +CONFIG_SND_SOC_INTEL_BROADWELL_MACH=m CONFIG_SND_SOC_INTEL_BYTCR_RT5640_MACH=m CONFIG_SND_SOC_INTEL_BYTCR_RT5651_MACH=m CONFIG_SND_SOC_INTEL_CHT_BSW_RT5672_MACH=m @@ -6506,6 +6510,8 @@ CONFIG_SND_SOC_RT5651=m CONFIG_SND_SOC_RT5663=m CONFIG_SND_SOC_RT5670=m +CONFIG_SND_SOC_RT5677=m +CONFIG_SND_SOC_RT5677_SPI=m CONFIG_SND_SOC_RT5682=m CONFIG_SND_SOC_RT5682_I2C=m CONFIG_SND_SOC_RT5682_SDW=m @@ -8065,8 +8071,6 @@ CONFIG_AD7923=m CONFIG_AD7949=m CONFIG_AD799X=m -CONFIG_AD9467=m -CONFIG_ADI_AXI_ADC=m CONFIG_AXP20X_ADC=m CONFIG_AXP288_ADC=m CONFIG_CC10001_ADC=m
Bug#989010: linux-image-5.10.0-7-amd64: No display (post, grub, boot messages and desktop) after the upgrade to 5.10.38
Source: linux Followup-For: Bug #989010 X-Debbugs-Cc: pitsior...@gmail.com Finally a sane reply by someone! First of all, I do not think that my issue is related to sleep at all. I mentioned all that in the first post just in case. I know sleep is problematic in linux, thus I never use it. I also don't use it in windows too. Second, the procedure you mention with the power cable was done many times after the 2 cards failed to boot, but instead of a live cd I tried to boot from my drive. It succeeded a couple of times with the nvidia one, but once the ati started doing it, it died and had to be replaced. Again, 2 different cards died after the upgrade to that very specific kernel version. Let that sink in... Right now both cards are on their way to another city where a friend of mine will test them too on his main and spare pc. As for the kernels, why would I boot to such an old kernel like buster's? As I have said above, today's nouveau is very inferior to nvidia, so I imagine the one from 4.19 will be even worse. And as I have said, I have no other gpu to sacrifice for testing 5.10. Plus, that ati that died was my fallback gpu for the day I would be force to use nouveau with nvidia. That is why I do my best on every kernel update for the 340 legacy driver to stay in the repo. Regarding video acceleration. I do have firmware-misc-nonfree (as a direct dependency of firmware-linux-nonfree) and I saw ZERO video acceleration even on 480p videos. But vdpau works flawlessly on both the 9500 (currently using, borrowed too) and also on the gt210 that died, even on 1080p60 videos. I can post mpv's output if you wish to check it uses vdpau. I also found that bit of info that says some firmware must be extracted from nvidia's driver in order for vaapi to work, but I was too busy to try it. https://nouveau.freedesktop.org/VideoAcceleration.html As for the kernel itself, I am on 5.10 since it first reached debian, on December 31st 2020 (according to the tracker), i.e. 5.10.4 (package linux- image-5.10.0-1-amd64).There have been 6 more revisions of that 5.10 kernel since then, but the issue I am reporting happened only on 5.10.38/40 (package linux-image-5.10.0-1-amd64) and with 2 different cards. How isn't that a debian issue? A few kernels ago, something was changed in kernel's build config and caused the nvidia legacy 340 driver not to be built at all! And guess who found the patch for it again... Last but not least, because someone suggested that my psu is broken, I would like to add that it is a all new 80+ bronze, be quiet brand that was installed on January 6th 2021. Yes, it is older than 5.10 is on debian.
Bug#989010: linux-image-5.10.0-7-amd64: No display (post, grub, boot messages and desktop) after the upgrade to 5.10.38
Source: linux Followup-For: Bug #989010 X-Debbugs-Cc: pitsior...@gmail.com Control: severity -1 critical Now that I have your attention, because raising the severity is the only way to get an answer here, let me begin. I noticed that this mess of a kernel reached testing today. As it seems, its original severity status was not enough to prevent this from happening. A kernel that causes hardware failure will soon be in debian's stable release, who would have thought! So, right now I am forced to use an older kernel, thus miss all the security updates from .28 on. And all that because I want my pc to work as it is supposed to work. Because I want to press the power button in the morning and see my pc boot the way it has been booting all those years that it had no issues at all. I would do more testing with liquirix's or xanmod's kernels of the same version in order to prove that your kernel is problematic, but I have ran out of gpus. Thank you for your non existant support. It was also non existant in a another kernel related bug report for 4.19 (bug 919859), which I opened in late 2019. It was closed a few days for lack of activity and it was a monologue with only me reporting stuff and getting no feedback. To be honest, if I knew they would become a monologue, I would not file bug reports but I would open a blog instead. And who knows, maybe someone would share his feedback there. p.s. The only reason I am not in arch today, as I promised last week, is because its installer has some minor issues. In the long term, my decision is to remove debian from any of my machines, including an rpi4 with raspbian.
Bug#989010: linux-image-5.10.0-7-amd64: No display (post, grub, boot messages and desktop) after the upgrade to 5.10.38
Source: linux Followup-For: Bug #989010 X-Debbugs-Cc: pitsior...@gmail.com I came accross these 2 threads on r/debian and I am now thinking that my problem too may not be related to debian packaging/patching/configuration but to some upstream flaw(s) of 5.10. The guy in the second thread has done some very extensive testing that prove it. https://old.reddit.com/r/debian/comments/npvzyt/intel_nuc_8_freezing_when_idle_on_most_kernels/ https://old.reddit.com/r/debian/comments/mrxx76/irritating_problem_with_the_bullseyes_kernel/ -- System Information: Debian Release: 11.0 APT prefers testing APT policy: (990, 'testing'), (500, 'testing-security'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 5.10.0-6-amd64 (SMP w/2 CPU threads) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /bin/dash
Bug#989010: linux-image-5.10.0-7-amd64: No display (post, grub, boot messages and desktop) after the upgrade to 5.10.38
Source: linux Followup-For: Bug #989010 X-Debbugs-Cc: pitsior...@gmail.com How would YOU feel if a system upgrade destroyed an (old yet) perfectly working piece of important hardware? What if it destroyed another piece of similar hardware a few days later? How would you feel if all those days you had no support or feedback from anyone that created that upgrade? How would you feel if the only advice you were given changed absolutely nothing and did not even prevent the loss of the second piece of hardware? Btw, the word "tainted" has to be the worst characterization for a kernel that must use a specific out-of-tree driver in order to make the related hw work at 100% of its capabilities. >From my point of view, all I see is a kernel that destroyed my hardware TWICE, thus the raise of severity to critical, because it did break the entire system hardware wise. The sad thing is that your attention was drawn after I raised it. And all the above can result to one thing from my side: anger. And don't expect me to lower my tone while being angry. As for the logs, please tell me where to find them and I will zip them and send them straight to your email if you wish. And not only the ones from 5.10.38/40, ALL 50/100/any number of logs systemd has kept. On the other hand, how hard would it be to build a kernel with the latest update but with the config used for 5.10.28? I did check the differences between config-5.10.0-6-amd64 and config-5.10.0-7-amd64 last week, but I admit I am not smart enough to see which change could cause all this mess.
Bug#989010: Severity raise
Control: severity -1 critical
Bug#989010: linux-image-5.10.0-7-amd64: No display (post, grub, boot messages and desktop) after the upgrade to 5.10.38
Source: linux Followup-For: Bug #989010 X-Debbugs-Cc: pitsior...@gmail.com I borrowed an old pc from a friend to test those 2 gpus. NONE of them reached the post, which means they are damaged now. Moreover, when the ati was connected, the system was beeping as if it had no vga on. Thank you debian for destroying 2 perfectly working pieces of hardware. If I could sue anyone who is responsible for this crap, I would. How about someone tells me what was changed in that -7 version that made all this mess. I compared the config files from testing's 5.10.28 and unstable's 5.10.38/5.10.40 and the changes were minimal. As for nouveau, now that I have tested it for ~24 hours, I can definitely say it is way below average. 3d acceleration is poor, 2d acceleration is so and so and hardware video decoding (vaapi) seems to only exist on paper because I did not manage to make it work on all 3 of my players (mpv, mplayer and kodi). With all that going on, I did not have the time and the clear mind to check for the temperatures so as to find out how bad its powersaving abilities are.
Bug#989010: linux-image-5.10.0-7-amd64: No display (post, grub, boot messages and desktop) after the upgrade to 5.10.38
Source: linux Followup-For: Bug #989010 X-Debbugs-Cc: pitsior...@gmail.com One thing I forgot last time. The ati card was fucked up AFTER it ran on 5.10.40 for a couple of boots. I installed it because I wanted to check if it works any better there (scrolling is laggy on all browsers). Do you think it is a coincidence? 2 cards messed up after both running for a while on the same kernel? How can I raise the severity to critical? It seems to cause hw failure.
Bug#989010: linux-image-5.10.0-7-amd64: No display (post, grub, boot messages and desktop) after the upgrade to 5.10.38
Source: linux Followup-For: Bug #989010 X-Debbugs-Cc: pitsior...@gmail.com And the same thing happened again today, with the ati card this time! I logged in via ssh and, like with nvidia and nouveaum radeon was not found in lsmod. I then checked lspci and the entire vga part was not there, as if a gpu was not even connected! What the fuck was on this update that fucked my only pcie-x slot that bad? Since I get no replies and so far I have been troubleshooting it on my own, I decided to move to arch by the end of the week, provided that one of the cards still works. Thanks for nothing, I will surely leave a bad review on distrowatch for the rest of the people to see. p.s. I had to borrow an fresh (yet old) nvidia card in order to make my system boot again and right now I am using it with nouveau, which is godawful btw.
Bug#989010: linux-image-5.10.0-7-amd64: No display (post, grub, boot messages and desktop) after the upgrade to 5.10.38
Source: linux Followup-For: Bug #989010 X-Debbugs-Cc: pitsior...@gmail.com I never thought I would say that, but radeon's capabilities are inferior even to nvidia's legacy driver. It has been a few hours now and I am still struggling to get vaapi working on mpv and mplayer. 2d acceleration is bad, so bad that I can see the scrollbar on ALL webpages "struggle" to keep up with the rest of the page when I scroll with the wheel. And on top of the above, 5.10.40 messed up the cpu temperature sensor readings I get on my conky, so now I have nothing to look at. What a mess!
Bug#989010: linux-image-5.10.0-7-amd64: No display (post, grub, boot messages and desktop) after the upgrade to 5.10.38
Source: linux Version: linux-image-5.10.0-7-amd64 Followup-For: Bug #989010 X-Debbugs-Cc: pitsior...@gmail.com Impending rant, because I think it is indeed a hardware failure that was caused from the kernel upgrade. I successfully downgraded linux-compiler-gcc-10-x86 and linux-kbuild-5.10 to their 5.10.28 versions from testing. As usual, it failed to boot properly after shutdown. I then decided to completely remove nvidia legacy 340 and give nouveau a chance, although I hate it and the room temperature was high already, so the risk of frying the card was also high. Nothing changed, blank screen from boot to poweroff (via ssh). Out of curiosity, I ran lsmod on both nouveau and nvidia (while it was already installed). And none of them showed up in lsmod! Moreover, lightdm was not running at all and I cound not even switch to a tty (not that I could when the problem first started). Then I got mad and went for a walk to calm down. I came back a few hours later and I also borrowed an ati 6450 from a friend to try. I pressed the power button and the system booted up as usual, using nouveau for the very first time (maybe second) ever. I ran poweroff, it shut down, I pressed the power button again and the same thing happened. Blank screen, nothing on lsmod etc. Then I replaced it with my friend's ati so as to be able to come back and write all this text here. I have no way to test the gpu (e.g. no spare pc), however, if it is a hw failure, it will be the second time debian destroys one for me. First time was on summer of 2011, when debian decided to remove fglrx from the repo and force me to use radeon for my 3850 after the upgrade to a new kernel. Back then, radeon was so limited in capabilities that it could not do powersaving. Long story short, my 3850 gave up the ghost ~1 month later, after running in max clock speed for a month. Sadly for me, history has probably repeated itself today, and I don't know why. What was changed in that damn update that f-ed up my gpu so badly? This gives me one more reason to leave debian after 13,5 years and move to arch. I had taken the decision to go there if nouveau becomes my only way to make my old gpu work in debian, now I have one more.
Bug#989010: linux-image-5.10.0-7-amd64: No display (post, grub, boot messages and desktop) after the upgrade to 5.10.38
Source: linux Version: linux-image-5.10.0-7-amd64 Followup-For: Bug #989010 X-Debbugs-Cc: pitsior...@gmail.com Can I somehow determine that the button does run systemctl poweroff and not sleep when I press it? All I can see in the shutdown messages, for that split second they appear, is just the word "systemd" and nothing more. I want to count out the possibility of failing hw.
Bug#989010: linux-image-5.10.0-7-amd64: No display (post, grub, boot messages and desktop) after the upgrade to 5.10.38
Source: linux Followup-For: Bug #989010 X-Debbugs-Cc: pitsior...@gmail.com First of all, I removed 5.10.38 because I want grub to directly boot to the working kernel without me having to select it via grub's advanced menu. Yes, nvidia (340 legacy) is the reason the tainted message pops up. To be honest, I don't really want to remove nvidia (because unloading is not a real option), and let me explain why. First, I have to remove and purge every single nvidia package, so as to be sure nouveau isn't blacklisted somewhere and can be loaded. Second, I have to remove nomodeset from my kernel's boot parameters, because nouveau needs modesetting to work. Third, because nouveau does not do proper powersaving for almost any gpu, I will have to reinstall 5.10.38 and do all the testing while my gpu will be running at max clock speeds, and all that in a room that has 30oC now. That is the core reason I avoid and dislike nouveau. For the forementioned reasons, I would like to stick to nvidia and continue troubleshooting in a different way, e.g. why did the system went to sleep since I had disabled it completely years ago? Or why it has affected my system so much that even the post and grub were not shown? I must mention that I have already checked the package changelog for 5.10.38 and it does not mention nvidia somewhere. In other observations, my drive's precious space has gone down ~300MB after that incident and I can't find out why. I do not have a swap file or partition, apt's cache is in /tmp and /tmp is in ram (tmpfs).
Bug#989010: linux-image-5.10.0-7-amd64: No display (post, grub, boot messages and desktop) after the upgrade to 5.10.38
Package: src:linux Version: 5.10.38-1 Severity: important X-Debbugs-Cc: pitsior...@gmail.com Preface. I have disabled sleep, hibernate etc via systemd as you can see below. $ systemctl status sleep.target suspend.target hibernate.target hybrid- sleep.target ● sleep.target Loaded: masked (Reason: Unit sleep.target is masked.) Active: inactive (dead) ● suspend.target Loaded: masked (Reason: Unit suspend.target is masked.) Active: inactive (dead) ● hibernate.target Loaded: masked (Reason: Unit hibernate.target is masked.) Active: inactive (dead) ● hybrid-sleep.target Loaded: masked (Reason: Unit hybrid-sleep.target is masked.) Active: inactive (dead) and I have set my keyboard's sleep button to shutdown the system via systemctl systemctl poweroff So when I press the sleep button, the system shuts down. And I have been using it like so for the last 5+ years. But today, after I upgraded to 5.10.38 and rebooted, I pressed sleep and the system... must have gone to sleep. Pressing the powerbutton did not get me to post or grub or anything. It was just working with nothing on screen. I could ssh to it from my phone or my laptop, so I ran reboot and it hypothetically rebooted. I say "hypothetically", because there was no post, grub, boot messages or desktop again. I rebooted it with reisub, but same thing happened. Both network (leds on nic) and usb (light on optical mouse) showed that it was really powered on, on all the forementioned situations. Since I can ssh to it, I ran dmesg and it showed nothing weird. Systemd-analyze blade showed no delays or issues too. I installed 5.10.28 again (because I remove every old kernel when the new one works) and now I am able to see my desktop and write all this. Right now, I am on 5.10.28 (package linux-image-5.10.0-6-amd64) and I am trying to figure out why all this happened. -- Package-specific info: ** Kernel log: boot messages should be attached ** Model information sys_vendor: Gigabyte Technology Co., Ltd. product_name: P35-DS3R product_version: chassis_vendor: Gigabyte Technology Co., Ltd. chassis_version: bios_vendor: Award Software International, Inc. bios_version: F13 board_vendor: Gigabyte Technology Co., Ltd. board_name: P35-DS3R board_version: ** PCI devices: 00:00.0 Host bridge [0600]: Intel Corporation 82G33/G31/P35/P31 Express DRAM Controller [8086:29c0] (rev 02) Subsystem: Gigabyte Technology Co., Ltd 82G33/G31/P35/P31 Express DRAM Controller [1458:5000] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- 00:01.0 PCI bridge [0604]: Intel Corporation 82G33/G31/P35/P31 Express PCI Express Root Port [8086:29c1] (rev 02) (prog-if 00 [Normal decode]) Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- Reset- FastB2B- PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn- Capabilities: Kernel driver in use: pcieport 00:1a.0 USB controller [0c03]: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #4 [8086:2937] (rev 02) (prog-if 00 [UHCI]) Subsystem: Gigabyte Technology Co., Ltd 82801I (ICH9 Family) USB UHCI Controller [1458:5004] Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- SERR- Kernel driver in use: uhci_hcd Kernel modules: uhci_hcd 00:1a.1 USB controller [0c03]: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #5 [8086:2938] (rev 02) (prog-if 00 [UHCI]) Subsystem: Gigabyte Technology Co., Ltd 82801I (ICH9 Family) USB UHCI Controller [1458:5004] Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- SERR- Kernel driver in use: uhci_hcd Kernel modules: uhci_hcd 00:1a.2 USB controller [0c03]: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #6 [8086:2939] (rev 02) (prog-if 00 [UHCI]) Subsystem: Gigabyte Technology Co., Ltd 82801I (ICH9 Family) USB UHCI Controller [1458:5004] Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- SERR- Kernel driver in use: uhci_hcd Kernel modules: uhci_hcd 00:1a.7 USB controller [0c03]: Intel Corporation 82801I (ICH9 Family) USB2 EHCI Controller #2 [8086:293c] (rev 02) (prog-if 20 [EHCI]) Subsystem: Gigabyte Technology Co., Ltd 82801I (ICH9 Family) USB2 EHCI Controller [1458:5006] Control: I/O- Mem+
Bug#988630: onedrive: Please update to the latest version
Package: onedrive Version: 2.4.10-1 Severity: normal Tags: upstream X-Debbugs-Cc: pitsior...@gmail.com Dear Maintainer, As the title suggests, please update to the latest version (2.4.11 at the time of writing). I am having a serious issue with 502 and 504 errors when using the app. I have reported it to the project's github repo, asking for help, and they said they only provide support for the latest version and simply closed AND LOCKED my issue! I know that debian is under freeze and that the new version was released at that period too, so I can wait and use a web browser for my onedrive transfers until the freeze is over. On the other hand, if only the latest version is supported by upstream, maybe the package is not suitable for the stable versions of debian (lack of security updates and lack of support too). Thank you in advance. -- System Information: Debian Release: 11.0 APT prefers testing APT policy: (990, 'testing'), (500, 'testing-security'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 5.10.0-6-amd64 (SMP w/2 CPU threads) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages onedrive depends on: ii init-system-helpers 1.60 ii libc62.31-11 ii libgcc-s110.2.1-6 ii libglib2.0-0 2.66.8-1 ii libnotify4 0.7.9-3 ii libphobos2-ldc-shared94 1:1.24.0-2 ii libsqlite3-0 3.34.1-3 onedrive recommends no packages. onedrive suggests no packages.
Bug#973599: nvidia-graphics-drivers-legacy-340xx: EoL driver should not be released with bullseye
Package: nvidia-graphics-drivers-legacy-340xx Followup-For: Bug #973599 X-Debbugs-Cc: pitsior...@gmail.com I just found out about the removal of nvidia legacy 340xx through reddit and I admit I had not noticed it all those months. Since the first days of kernel 5.x in debian, back in mid 2019, I was the first to test if it builds and to find the relevant patch on every new kernel release. I was hoping this would keep it in the repos for debian 11, but there are more serious issues as it seems that forced its removal. Because the package will remain in sid, I would like to ask if you will accept patches for future versions of the kernel, or, in a few words, if the package will continue to be upgraded. I am one of those users who can not stand nouveau at all because of its sub par performance and, as I have said in a previous bug report, if debian does drop it one day, I will probably move to arch in order to keep my (old) hw functioning to its full potential. Thank you in advance. -- System Information: Debian Release: bullseye/sid APT prefers testing APT policy: (990, 'testing'), (500, 'testing-security'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 5.10.0-6-amd64 (SMP w/2 CPU threads) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /bin/dash
Bug#985951: upnp-router-control: New upstream version since February 2021
Package: upnp-router-control Version: 0.2-1.2+b1 Followup-For: Bug #985951 X-Debbugs-Cc: pitsior...@gmail.com Thank you for the clarification and the quick response. Feel free to close this bug now.
Bug#985951: upnp-router-control: New upstream version since February 2021
Package: upnp-router-control Version: 0.2-1.2+b1 Severity: minor Tags: upstream X-Debbugs-Cc: pitsior...@gmail.com Dear Maintainer, Earlier, I noticed that upnp-router-control was removed from the repo 1+ year ago. I had installed it a couple of years ago in order to troubleshoot some connection issues I had and I can say it helped me a bit. Then I went to its launchpad page to check if it is still developed from upstream and saw that a new version (0.3) was released a month ago, with the port to gtk3 being the most important new feature. A new version after 10 YEARS of inactivity! So, can you please bring it back to the repo after the freeze? -- System Information: Debian Release: bullseye/sid APT prefers testing APT policy: (990, 'testing'), (500, 'testing-security'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 5.10.0-5-amd64 (SMP w/2 CPU threads) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages upnp-router-control depends on: ii libatk1.0-0 2.36.0-2 ii libc62.31-10 ii libcairo21.16.0-5 ii libfontconfig1 2.13.1-4.2 ii libfreetype6 2.10.4+dfsg-1 ii libgdk-pixbuf2.0-0 2.40.2-2 ii libglib2.0-0 2.66.7-2 ii libgssdp-1.0-3 1.0.5-0+deb10u1 ii libgtk2.0-0 2.24.33-1 ii libgupnp-1.0-4 1.0.5-0+deb10u1 ii libpango-1.0-0 1.46.2-3 ii libpangocairo-1.0-0 1.46.2-3 ii libpangoft2-1.0-01.46.2-3 upnp-router-control recommends no packages. upnp-router-control suggests no packages.
Bug#981462: Please, provide a systemd service unit file too
Package: hddtemp Version: 0.3-beta15-54 Followup-For: Bug #981462 X-Debbugs-Cc: pitsior...@gmail.com I second to the above. If it helps, this is the systemd service file that arch provides https://github.com/archlinux/svntogit- packages/blob/packages/hddtemp/trunk/service -- System Information: Debian Release: bullseye/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 5.10.0-3-amd64 (SMP w/2 CPU threads) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages hddtemp depends on: ii debconf [debconf-2.0] 1.5.74 ii libc6 2.31-9 ii lsb-base 11.1.0 hddtemp recommends no packages. hddtemp suggests no packages.
Bug#983313: webfs: Please provide a systemd service for webfs
Package: webfs Severity: normal X-Debbugs-Cc: pitsior...@gmail.com On every boot, this message shows up in dmesg stating the obvious [ 16.606515] systemd-sysv-generator[153]: SysV service '/etc/init.d/webfs' lacks a native systemd unit file. Automatically generating a unit file for compatibility. Please update package to include a native systemd unit file, in order to make it more safe and robust. If it helps, arch provides this systemd service file for webfs https://github.com/archlinux/svntogit- community/blob/packages/webfs/trunk/webfsd.service -- System Information: Debian Release: bullseye/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 5.10.0-3-amd64 (SMP w/2 CPU threads) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages webfs depends on: ii debconf [debconf-2.0] 1.5.74 ii libc6 2.31-9 ii libgnutls303.7.0-5 ii lsb-base 11.1.0 ii ucf3.0043 webfs recommends no packages.
Bug#983309: inadyn: Please provide a systemd service for inadyn
Package: inadyn Followup-For: Bug #983309 X-Debbugs-Cc: pitsior...@gmail.com There is a systemd service file available from upstream! https://github.com/troglobit/inadyn/blob/5f7ef01e2b5597c02e15c0001a9a250f0356d774/inadyn.service.in
Bug#983309: inadyn: Please provide a systemd service for inadyn
Package: inadyn Severity: normal X-Debbugs-Cc: pitsior...@gmail.com Although I have no hopes for this getting fixed, because the package seems unmaintained for the last ~8 years, here goes. On every boot, this message shows up in dmesg stating the obvious systemd-sysv-generator[153]: SysV service '/etc/init.d/inadyn' lacks a native systemd unit file. Automatically generating a unit file for compatibility. Please update package to include a native systemd unit file, in order to make it more safe and robust. 8 years ago debian was still on sysvinit and sadly nothing has changed since then, not even the version of the package. -- System Information: Debian Release: bullseye/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 5.10.0-3-amd64 (SMP w/2 CPU threads) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages inadyn depends on: ii adduser 3.118 ii libc62.31-9 inadyn recommends no packages.
Bug#982062: chromium: Google is limiting private api availability for all chromium builds
Package: chromium Followup-For: Bug #982062 X-Debbugs-Cc: pitsior...@gmail.com So, in your opinion, a browser is useful only for rendering pages? Nowadays, web technologies have evolved and web pages are not static html. Sites are complex and the ability for someone to sync passwords/bookmarks/history in his browser helps him have some continuity for his work, even on different devices. For some, sync is not just another browser feature but a critical feature the browser MUST have. Leaving sync aside, these are the features that are expected to break Geolocation Click to Call Chrome spelling API Contacts API Chrome translate element Speaking for myself and only for myself, I am not affected by any of these. But I am not the average user. Other major distros have already announced or are discussing what they will do. Fedora has even removed their api keys already! Slackware is asking users if they are willing to use a muzzled browser. Why? Because building chromium takes a lot of time and that cut in usability may not worth it. Finally, if you consider this a minor issue, make an announcement beforehand so the users know what to expect by then and remove /etc/chromium.d/apikeys from the package on a future update, because it will be useless. -- System Information: Debian Release: bullseye/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 5.10.0-3-amd64 (SMP w/2 CPU threads) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages chromium depends on: pn chromium-common ii libasound2 1.2.4-1.1 ii libatk-bridge2.0-0 2.38.0-1 ii libatk1.0-0 2.36.0-2 ii libatomic1 10.2.1-6 ii libatspi2.0-02.38.0-2 ii libavcodec58 10:4.3.1-dmo10 ii libavformat5810:4.3.1-dmo10 ii libavutil56 10:4.3.1-dmo10 ii libc62.31-9 ii libcairo21.16.0-5 ii libcups2 2.3.3op2-2 ii libdbus-1-3 1.12.20-1 ii libdrm2 2.4.104-1 ii libevent-2.1-7 2.1.12-stable-1 ii libexpat12.2.10-1 ii libflac8 1.3.3-2 ii libfontconfig1 2.13.1-4.2 ii libfreetype6 2.10.4+dfsg-1 ii libgbm1 20.3.4-1 ii libgcc-s110.2.1-6 ii libgdk-pixbuf-2.0-0 2.42.2+dfsg-1 ii libglib2.0-0 2.66.6-1 ii libgtk-3-0 3.24.24-1 ii libharfbuzz0b2.7.4-1 ii libicu67 67.1-6 ii libjpeg62-turbo 1:2.0.5-2 pn libjsoncpp24 ii liblcms2-2 2.12~rc1-2 pn libminizip1 ii libnspr4 2:4.29-1 ii libnss3 2:3.60-1 ii libopenjp2-7 2.4.0-1 ii libopus0 1.3.1-0.1 ii libpango-1.0-0 1.46.2-3 ii libpng16-16 1.6.37-3 ii libpulse014.1-1 pn libre2-9 ii libsnappy1v5 1.1.8-1 ii libstdc++6 10.2.1-6 ii libvpx6 1.9.0-dmo1 ii libwebp6 0.6.1-2+b1 ii libwebpdemux20.6.1-2+b1 ii libwebpmux3 0.6.1-2+b1 ii libx11-6 2:1.7.0-2 ii libxcb1 1.14-3 ii libxcomposite1 1:0.4.5-1 ii libxdamage1 1:1.1.5-2 ii libxext6 2:1.3.3-1.1 ii libxfixes3 1:5.0.3-2 ii libxml2 2.9.10+dfsg-6.3+b1 ii libxrandr2 2:1.5.1-1 ii libxslt1.1 1.1.34-4 ii zlib1g 1:1.2.11.dfsg-2 Versions of packages chromium recommends: pn chromium-sandbox Versions of packages chromium suggests: pn chromium-driver pn chromium-l10n pn chromium-shell
Bug#981809: firefox: No binary package of firefox 85 in the repo
Package: firefox
Followup-For: Bug #981809
X-Debbugs-Cc: pitsior...@gmail.com
Fixed after today's upgrade to 85.0.1. It was probably built with the same
cargo version as the previous ones.
-- Package-specific info:
-- Extensions information
Name: Amazon.co.uk
Location: /usr/lib/firefox/browser/omni.ja
Package: firefox
Status: enabled
Name: Amazon.com
Location: /usr/lib/firefox/browser/omni.ja
Package: firefox
Status: enabled
Name: Bing
Location: /usr/lib/firefox/browser/omni.ja
Package: firefox
Status: enabled
Name: Dark theme
Location: /usr/lib/firefox/browser/omni.ja
Package: firefox
Status: user-disabled
Name: Default theme
Location: /usr/lib/firefox/omni.ja
Package: firefox
Status: enabled
Name: DoH Roll-Out
Location: /usr/lib/firefox/browser/features/doh-roll...@mozilla.org.xpi
Package: firefox
Status: enabled
Name: DuckDuckGo
Location: /usr/lib/firefox/browser/omni.ja
Package: firefox
Status: enabled
Name: Firefox Alpenglow theme
Location: /usr/lib/firefox/browser/omni.ja
Package: firefox
Status: user-disabled
Name: Firefox Screenshots
Location: /usr/lib/firefox/browser/features/screensh...@mozilla.org.xpi
Package: firefox
Status: user-disabled
Name: Form Autofill
Location: /usr/lib/firefox/browser/features/formautof...@mozilla.org.xpi
Package: firefox
Status: enabled
Name: Google
Location: /usr/lib/firefox/browser/omni.ja
Package: firefox
Status: enabled
Name: Light theme
Location: /usr/lib/firefox/browser/omni.ja
Package: firefox
Status: user-disabled
Name: PlayThis
Location: ${PROFILE_EXTENSIONS}/playt...@anxdpanic.xpi
Status: enabled
Name: Video DownloadHelper
Location: ${PROFILE_EXTENSIONS}/{b9db16a4-6edc-47ec-a1f4-b86292ed211d}.xpi
Status: enabled
Name: Web Compatibility Interventions
Location: /usr/lib/firefox/browser/features/webcom...@mozilla.org.xpi
Package: firefox
Status: enabled
Name: WebCompat Reporter
Location: /usr/lib/firefox/browser/features/webcompat-repor...@mozilla.org.xpi
Package: firefox
Status: user-disabled
Name: Wikipedia (en)
Location: /usr/lib/firefox/browser/omni.ja
Package: firefox
Status: enabled
Name: eBay
Location: /usr/lib/firefox/browser/omni.ja
Package: firefox
Status: enabled
Name: uBlock Origin
Location: ${PROFILE_EXTENSIONS}/ublo...@raymondhill.net.xpi
Status: enabled
-- Plugins information
-- Addons package information
ii firefox85.0.1-1 amd64Mozilla Firefox web browser
-- System Information:
Debian Release: bullseye/sid
APT prefers testing
APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 5.10.0-3-amd64 (SMP w/2 CPU threads)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE,
TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages firefox depends on:
ii debianutils 4.11.2
ii fontconfig 2.13.1-4.2
ii libatk1.0-0 2.36.0-2
ii libc62.31-9
ii libcairo-gobject21.16.0-5
ii libcairo21.16.0-5
ii libdbus-1-3 1.12.20-1
ii libdbus-glib-1-2 0.110-6
ii libevent-2.1-7 2.1.12-stable-1
ii libffi7 3.3-5
ii libfontconfig1 2.13.1-4.2
ii libfreetype6 2.10.4+dfsg-1
ii libgcc-s110.2.1-6
ii libgdk-pixbuf-2.0-0 2.42.2+dfsg-1
ii libglib2.0-0 2.66.4-1
ii libgtk-3-0 3.24.24-1
ii libnspr4 2:4.29-1
ii libnss3 2:3.60-1
ii libpango-1.0-0 1.46.2-3
ii libstdc++6 10.2.1-6
ii libvpx6 1.9.0-dmo1
ii libx11-6 2:1.7.0-2
ii libx11-xcb1 2:1.7.0-2
ii libxcb-shm0 1.14-3
ii libxcb1 1.14-3
ii libxcomposite1 1:0.4.5-1
ii libxdamage1 1:1.1.5-2
ii libxext6 2:1.3.3-1.1
ii libxfixes3 1:5.0.3-2
ii libxrender1 1:0.9.10-1
ii procps 2:3.3.16-5
ii zlib1g 1:1.2.11.dfsg-2
Versions of packages firefox recommends:
ii libavcodec58 10:4.3.1-dmo10
Versions of packages firefox suggests:
pn fonts-lmodern
pn fonts-stix | otf-stix
ii libcanberra0 0.30-7
ii libgssapi-krb5-2 1.18.3-4
ii libgtk2.0-02.24.33-1
pn pulseaudio
-- no debconf information
Bug#982062: chromium: Google is limiting private api availability for all chromium builds
Package: chromium Severity: important Tags: upstream X-Debbugs-Cc: pitsior...@gmail.com ~20 days ago, google announced that they are limiting api availability on March 15th 2021. https://blog.chromium.org/2021/01/limiting-private-api-availability-in.html This means that sync and some other features will stop working from that day on and users that use them will complain and file bug reports. Other distros are already discussing the subject and some even suggest the removal of chromium from their repos, so I think it is time for debian users and maintainers to do it too. So, what will debian do? Let me hear your thoughts. p.s. I am the least affected user by that change. I do not use sync or any other of the services that are will stop functioning. In fact, I do not use sync on any of my browsers. On top of that, I no longer use chromium after last year's huge delays in major updates. But here I am, opening the discussion for its future in debian. -- System Information: Debian Release: bullseye/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 5.10.0-3-amd64 (SMP w/2 CPU threads) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages chromium depends on: pn chromium-common ii libasound2 1.2.4-1.1 ii libatk-bridge2.0-0 2.38.0-1 ii libatk1.0-0 2.36.0-2 ii libatomic1 10.2.1-6 ii libatspi2.0-02.38.0-2 ii libavcodec58 10:4.3.1-dmo10 ii libavformat5810:4.3.1-dmo10 ii libavutil56 10:4.3.1-dmo10 ii libc62.31-9 ii libcairo21.16.0-5 ii libcups2 2.3.3op1-7 ii libdbus-1-3 1.12.20-1 ii libdrm2 2.4.104-1 ii libevent-2.1-7 2.1.12-stable-1 ii libexpat12.2.10-1 ii libflac8 1.3.3-2 ii libfontconfig1 2.13.1-4.2 ii libfreetype6 2.10.4+dfsg-1 ii libgbm1 20.3.4-1 ii libgcc-s110.2.1-6 ii libgdk-pixbuf-2.0-0 2.42.2+dfsg-1 ii libglib2.0-0 2.66.4-1 ii libgtk-3-0 3.24.24-1 ii libharfbuzz0b2.7.4-1 ii libicu67 67.1-6 ii libjpeg62-turbo 1:2.0.5-2 pn libjsoncpp24 ii liblcms2-2 2.12~rc1-2 pn libminizip1 ii libnspr4 2:4.29-1 ii libnss3 2:3.60-1 ii libopenjp2-7 2.4.0-1 ii libopus0 1.3.1-0.1 ii libpango-1.0-0 1.46.2-3 ii libpng16-16 1.6.37-3 ii libpulse014.1-1 pn libre2-9 ii libsnappy1v5 1.1.8-1 ii libstdc++6 10.2.1-6 ii libvpx6 1.9.0-dmo1 ii libwebp6 0.6.1-2+b1 ii libwebpdemux20.6.1-2+b1 ii libwebpmux3 0.6.1-2+b1 ii libx11-6 2:1.7.0-2 ii libxcb1 1.14-3 ii libxcomposite1 1:0.4.5-1 ii libxdamage1 1:1.1.5-2 ii libxext6 2:1.3.3-1.1 ii libxfixes3 1:5.0.3-2 ii libxml2 2.9.10+dfsg-6.3+b1 ii libxrandr2 2:1.5.1-1 ii libxslt1.1 1.1.34-4 ii zlib1g 1:1.2.11.dfsg-2 Versions of packages chromium recommends: pn chromium-sandbox Versions of packages chromium suggests: pn chromium-driver pn chromium-l10n pn chromium-shell
Bug#981809: firefox: No binary package of firefox 85 in the repo
Package: firefox
Version: 84.0.2-1
Followup-For: Bug #981809
X-Debbugs-Cc: pitsior...@gmail.com
I just read in r/debian that ff 85 needs a newer version of cargo.
Guess we are now waiting for it...
-- Package-specific info:
-- Extensions information
Name: Amazon.co.uk
Location: /usr/lib/firefox/browser/omni.ja
Package: firefox
Status: enabled
Name: Amazon.com
Location: /usr/lib/firefox/browser/omni.ja
Package: firefox
Status: enabled
Name: Bing
Location: /usr/lib/firefox/browser/omni.ja
Package: firefox
Status: enabled
Name: Dark theme
Location: /usr/lib/firefox/browser/omni.ja
Package: firefox
Status: user-disabled
Name: Default theme
Location: /usr/lib/firefox/omni.ja
Package: firefox
Status: enabled
Name: DoH Roll-Out
Location: /usr/lib/firefox/browser/features/doh-roll...@mozilla.org.xpi
Package: firefox
Status: enabled
Name: DuckDuckGo
Location: /usr/lib/firefox/browser/omni.ja
Package: firefox
Status: enabled
Name: eBay
Location: /usr/lib/firefox/browser/omni.ja
Package: firefox
Status: enabled
Name: Firefox Alpenglow theme
Location: /usr/lib/firefox/browser/omni.ja
Package: firefox
Status: user-disabled
Name: Firefox Screenshots
Location: /usr/lib/firefox/browser/features/screensh...@mozilla.org.xpi
Package: firefox
Status: user-disabled
Name: Form Autofill
Location: /usr/lib/firefox/browser/features/formautof...@mozilla.org.xpi
Package: firefox
Status: enabled
Name: Google
Location: /usr/lib/firefox/browser/omni.ja
Package: firefox
Status: enabled
Name: Light theme
Location: /usr/lib/firefox/browser/omni.ja
Package: firefox
Status: user-disabled
Name: PlayThis
Location: ${PROFILE_EXTENSIONS}/playt...@anxdpanic.xpi
Status: enabled
Name: uBlock Origin
Location: ${PROFILE_EXTENSIONS}/ublo...@raymondhill.net.xpi
Status: enabled
Name: Video DownloadHelper
Location: ${PROFILE_EXTENSIONS}/{b9db16a4-6edc-47ec-a1f4-b86292ed211d}.xpi
Status: enabled
Name: Web Compatibility Interventions
Location: /usr/lib/firefox/browser/features/webcom...@mozilla.org.xpi
Package: firefox
Status: enabled
Name: WebCompat Reporter
Location: /usr/lib/firefox/browser/features/webcompat-repor...@mozilla.org.xpi
Package: firefox
Status: user-disabled
Name: Wikipedia (en)
Location: /usr/lib/firefox/browser/omni.ja
Package: firefox
Status: enabled
-- Plugins information
-- Addons package information
ii firefox84.0.2-1 amd64Mozilla Firefox web browser
-- System Information:
Debian Release: bullseye/sid
APT prefers testing
APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 5.10.0-3-amd64 (SMP w/2 CPU threads)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE,
TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages firefox depends on:
ii debianutils 4.11.2
ii fontconfig 2.13.1-4.2
ii libatk1.0-0 2.36.0-2
ii libc62.31-9
ii libcairo-gobject21.16.0-5
ii libcairo21.16.0-5
ii libdbus-1-3 1.12.20-1
ii libdbus-glib-1-2 0.110-6
ii libevent-2.1-7 2.1.12-stable-1
ii libffi7 3.3-5
ii libfontconfig1 2.13.1-4.2
ii libfreetype6 2.10.4+dfsg-1
ii libgcc-s110.2.1-6
ii libgdk-pixbuf-2.0-0 2.42.2+dfsg-1
ii libglib2.0-0 2.66.4-1
ii libgtk-3-0 3.24.24-1
ii libnspr4 2:4.29-1
ii libnss3 2:3.60-1
ii libpango-1.0-0 1.46.2-3
ii libstdc++6 10.2.1-6
ii libvpx6 1.9.0-dmo1
ii libx11-6 2:1.7.0-2
ii libx11-xcb1 2:1.7.0-2
ii libxcb-shm0 1.14-3
ii libxcb1 1.14-3
ii libxcomposite1 1:0.4.5-1
ii libxdamage1 1:1.1.5-2
ii libxext6 2:1.3.3-1.1
ii libxfixes3 1:5.0.3-2
ii libxrender1 1:0.9.10-1
ii procps 2:3.3.16-5
ii zlib1g 1:1.2.11.dfsg-2
Versions of packages firefox recommends:
ii libavcodec58 10:4.3.1-dmo10
Versions of packages firefox suggests:
pn fonts-lmodern
pn fonts-stix | otf-stix
ii libcanberra0 0.30-7
ii libgssapi-krb5-2 1.18.3-4
ii libgtk2.0-02.24.33-1
pn pulseaudio
-- no debconf information
Bug#981809: firefox: No binary package of firefox 85 in the repo
Package: firefox
Version: 84.0.2-1
Severity: normal
X-Debbugs-Cc: pitsior...@gmail.com
Dear Maintainer,
Firefox 85 was released (from upstream) more than a week ago and its source
package reached the repo just a day later. However, the binary package is still
nowhere to be found. It is not even mentioned in buildd.debian.org.
Plus, reportbug mentions that there is a newer version available on the repo,
while there isn't!
On the other hand, both (source and binary) packages for firefox-esr 78.7 were
released last week and the binary one reached the repo a day later. It has also
reached testing, and even stable, since then!
So please package the regular firefox :)
-- Package-specific info:
-- Extensions information
Name: Amazon.co.uk
Location: /usr/lib/firefox/browser/omni.ja
Package: firefox
Status: enabled
Name: Amazon.com
Location: /usr/lib/firefox/browser/omni.ja
Package: firefox
Status: enabled
Name: Bing
Location: /usr/lib/firefox/browser/omni.ja
Package: firefox
Status: enabled
Name: Dark theme
Location: /usr/lib/firefox/browser/omni.ja
Package: firefox
Status: user-disabled
Name: Default theme
Location: /usr/lib/firefox/omni.ja
Package: firefox
Status: enabled
Name: DoH Roll-Out
Location: /usr/lib/firefox/browser/features/doh-roll...@mozilla.org.xpi
Package: firefox
Status: enabled
Name: DuckDuckGo
Location: /usr/lib/firefox/browser/omni.ja
Package: firefox
Status: enabled
Name: eBay
Location: /usr/lib/firefox/browser/omni.ja
Package: firefox
Status: enabled
Name: Firefox Alpenglow theme
Location: /usr/lib/firefox/browser/omni.ja
Package: firefox
Status: user-disabled
Name: Firefox Screenshots
Location: /usr/lib/firefox/browser/features/screensh...@mozilla.org.xpi
Package: firefox
Status: user-disabled
Name: Form Autofill
Location: /usr/lib/firefox/browser/features/formautof...@mozilla.org.xpi
Package: firefox
Status: enabled
Name: Google
Location: /usr/lib/firefox/browser/omni.ja
Package: firefox
Status: enabled
Name: Light theme
Location: /usr/lib/firefox/browser/omni.ja
Package: firefox
Status: user-disabled
Name: PlayThis
Location: ${PROFILE_EXTENSIONS}/playt...@anxdpanic.xpi
Status: enabled
Name: uBlock Origin
Location: ${PROFILE_EXTENSIONS}/ublo...@raymondhill.net.xpi
Status: enabled
Name: Video DownloadHelper
Location: ${PROFILE_EXTENSIONS}/{b9db16a4-6edc-47ec-a1f4-b86292ed211d}.xpi
Status: enabled
Name: Web Compatibility Interventions
Location: /usr/lib/firefox/browser/features/webcom...@mozilla.org.xpi
Package: firefox
Status: enabled
Name: WebCompat Reporter
Location: /usr/lib/firefox/browser/features/webcompat-repor...@mozilla.org.xpi
Package: firefox
Status: user-disabled
Name: Wikipedia (en)
Location: /usr/lib/firefox/browser/omni.ja
Package: firefox
Status: enabled
-- Plugins information
-- Addons package information
ii firefox84.0.2-1 amd64Mozilla Firefox web browser
-- System Information:
Debian Release: bullseye/sid
APT prefers testing
APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 5.10.0-3-amd64 (SMP w/2 CPU threads)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE,
TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages firefox depends on:
ii debianutils 4.11.2
ii fontconfig 2.13.1-4.2
ii libatk1.0-0 2.36.0-2
ii libc62.31-9
ii libcairo-gobject21.16.0-5
ii libcairo21.16.0-5
ii libdbus-1-3 1.12.20-1
ii libdbus-glib-1-2 0.110-6
ii libevent-2.1-7 2.1.12-stable-1
ii libffi7 3.3-5
ii libfontconfig1 2.13.1-4.2
ii libfreetype6 2.10.4+dfsg-1
ii libgcc-s110.2.1-6
ii libgdk-pixbuf-2.0-0 2.42.2+dfsg-1
ii libglib2.0-0 2.66.4-1
ii libgtk-3-0 3.24.24-1
ii libnspr4 2:4.29-1
ii libnss3 2:3.60-1
ii libpango-1.0-0 1.46.2-3
ii libstdc++6 10.2.1-6
ii libvpx6 1.9.0-dmo1
ii libx11-6 2:1.7.0-2
ii libx11-xcb1 2:1.7.0-2
ii libxcb-shm0 1.14-3
ii libxcb1 1.14-3
ii libxcomposite1 1:0.4.5-1
ii libxdamage1 1:1.1.5-2
ii libxext6 2:1.3.3-1.1
ii libxfixes3 1:5.0.3-2
ii libxrender1 1:0.9.10-1
ii procps 2:3.3.16-5
ii zlib1g 1:1.2.11.dfsg-2
Versions of packages firefox recommends:
ii libavcodec58 10:4.3.1-dmo10
Versions of packages firefox suggests:
pn fonts-lmodern
pn fonts-stix | otf-stix
ii libcanberra0 0.30-7
ii libgssapi-krb5-2 1.18.3-4
ii libgtk2.0-02.24.33-1
pn pulseaudio
-- no debconf information
Bug#981535: apt: Upgrade shows held back packages, dist-upgrade does not
Package: apt Version: 2.1.18 Severity: normal X-Debbugs-Cc: pitsior...@gmail.com Dear Maintainer, It must be the 4th or 5th time that I notice the following behavior, so I report it today. I do this to update my system apt-get update && apt-get upgrade && apt-get dist-upgrade The update part finishes successfully as usual, the upgrade part says that there are some packages that were held back, e.g. Reading package lists... Done Building dependency tree Reading state information... Done Calculating upgrade... Done The following packages have been kept back: kodi-inputstream-adaptive kodi-inputstream-rtmp kodi-vfs-libarchive 0 upgraded, 0 newly installed, 0 to remove and 3 not upgraded. But dist-upgrade that comes right after mentions no packages were held back Reading package lists... Done Building dependency tree Reading state information... Done Calculating upgrade... Done 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. Last time, firefox was the package in question and it could was not upgraded to 84.0.2, even with dist-upgrade, because it depended on a newer version of libx11-6 that was only on unstable that time. Dist-upgrade could not pull that dependency, so I had to "update" it with apt-get install -t unstable firefox I am on testing with select packages from unstable, e.g. firefox. That is why I have the APT::Default-Release preference set to testing in apt.conf. I have been using this setting for the last 8+ years and I notice the forementioned behavior only lately. -- Package-specific info: -- apt-config dump -- APT ""; APT::Architecture "amd64"; APT::Build-Essential ""; APT::Build-Essential:: "build-essential"; APT::Install-Recommends "0"; APT::Install-Suggests "0"; APT::Sandbox ""; APT::Sandbox::User "_apt"; APT::Authentication ""; APT::Authentication::TrustCDROM "true"; APT::NeverAutoRemove ""; APT::NeverAutoRemove:: "^firmware-linux.*"; APT::NeverAutoRemove:: "^linux-firmware$"; APT::NeverAutoRemove:: "^linux-image-[a-z0-9]*$"; APT::NeverAutoRemove:: "^linux-image-[a-z0-9]*-[a-z0-9]*$"; APT::VersionedKernelPackages ""; APT::VersionedKernelPackages:: "linux-.*"; APT::VersionedKernelPackages:: "kfreebsd-.*"; APT::VersionedKernelPackages:: "gnumach-.*"; APT::VersionedKernelPackages:: ".*-modules"; APT::VersionedKernelPackages:: ".*-kernel"; APT::Never-MarkAuto-Sections ""; APT::Never-MarkAuto-Sections:: "metapackages"; APT::Never-MarkAuto-Sections:: "contrib/metapackages"; APT::Never-MarkAuto-Sections:: "non-free/metapackages"; APT::Never-MarkAuto-Sections:: "restricted/metapackages"; APT::Never-MarkAuto-Sections:: "universe/metapackages"; APT::Never-MarkAuto-Sections:: "multiverse/metapackages"; APT::Move-Autobit-Sections ""; APT::Move-Autobit-Sections:: "oldlibs"; APT::Move-Autobit-Sections:: "contrib/oldlibs"; APT::Move-Autobit-Sections:: "non-free/oldlibs"; APT::Move-Autobit-Sections:: "restricted/oldlibs"; APT::Move-Autobit-Sections:: "universe/oldlibs"; APT::Move-Autobit-Sections:: "multiverse/oldlibs"; APT::LastInstalledKernel "5.10.0-2-amd64"; APT::Default-Release "testing"; APT::AutoRemove ""; APT::AutoRemove::SuggestsImportant "false"; APT::AutoRemove::RecommendsImportant "false"; APT::Architectures ""; APT::Architectures:: "amd64"; APT::Compressor ""; APT::Compressor::. ""; APT::Compressor::.::Name "."; APT::Compressor::.::Extension ""; APT::Compressor::.::Binary ""; APT::Compressor::.::Cost "0"; APT::Compressor::zstd ""; APT::Compressor::zstd::Name "zstd"; APT::Compressor::zstd::Extension ".zst"; APT::Compressor::zstd::Binary "false"; APT::Compressor::zstd::Cost "60"; APT::Compressor::lz4 ""; APT::Compressor::lz4::Name "lz4"; APT::Compressor::lz4::Extension ".lz4"; APT::Compressor::lz4::Binary "false"; APT::Compressor::lz4::Cost "50"; APT::Compressor::gzip ""; APT::Compressor::gzip::Name "gzip"; APT::Compressor::gzip::Extension ".gz"; APT::Compressor::gzip::Binary "gzip"; APT::Compressor::gzip::Cost "100"; APT::Compressor::gzip::CompressArg ""; APT::Compressor::gzip::CompressArg:: "-6n"; APT::Compressor::gzip::UncompressArg ""; APT::Compressor::gzip::UncompressArg:: "-d"; APT::Compressor::xz ""; APT::Compressor::xz::Name "xz"; APT::Compressor::xz::Extension ".xz"; APT::Compressor::xz::Binary "xz"; APT::Compressor::xz::Cost "200"; APT::Compressor::xz::CompressArg ""; APT::Compressor::xz::CompressArg:: "-6"; APT::Compressor::xz::UncompressArg ""; APT::Compressor::xz::UncompressArg:: "-d"; APT::Compressor::bzip2 ""; APT::Compressor::bzip2::Name "bzip2"; APT::Compressor::bzip2::Extension ".bz2"; APT::Compressor::bzip2::Binary "bzip2"; APT::Compressor::bzip2::Cost "300"; APT::Compressor::bzip2::CompressArg ""; APT::Compressor::bzip2::CompressArg:: "-6"; APT::Compressor::bzip2::UncompressArg ""; APT::Compressor::bzip2::UncompressArg:: "-d"; APT::Compressor::lzma ""; APT::Compressor::lzma::Name "lzma"; APT::Compressor::lzma::Extension ".lzma"; APT::Compressor::lzma::Binary "xz"; APT::Compressor::lzma::Cost "400"; APT::Compressor::lzma::CompressArg "";
Bug#980285: libpam-runtime: Incorrect password expiration warning after the update to 1.4.0
Package: libpam-runtime Version: 1.4.0-2 Severity: normal X-Debbugs-Cc: pitsior...@gmail.com Dear Maintainer, After today's upgrade to 1.4.0 in testing, I get this message everytime I run su $ su Password: Warning: your password will expire in 32632 days. And the number changes everytime, but it is always over 32000 days. All I could find about it was this report in redhat's bugzilla https://bugzilla.redhat.com/show_bug.cgi?id=1887077 If it helps, my user on this machine is sudo capable and nothing similar shows up when I use sudo instead of su. I also have another machine with unstable, without sudo and the message does not show up there. -- System Information: Debian Release: bullseye/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 5.10.0-1-amd64 (SMP w/2 CPU threads) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages libpam-runtime depends on: ii debconf [debconf-2.0] 1.5.74 ii libpam-modules 1.4.0-2 libpam-runtime recommends no packages. libpam-runtime suggests no packages. -- debconf information: libpam-runtime/profiles: unix, systemd libpam-runtime/no_profiles_chosen: libpam-runtime/title: libpam-runtime/override: false libpam-runtime/conflicts:
Bug#979689: pepperflashplugin-nonfree: Installation script fails to download flash from adobe's servers
Package: pepperflashplugin-nonfree Version: 1.8.7 Severity: grave Tags: upstream Justification: renders package unusable X-Debbugs-Cc: pitsior...@gmail.com Dear Maintainer, Please consider this a followup of #978954, which talks about flash's deprecation from adobe. As mentioned in the title, the installation script fails to download the relevant file. Wget tries 3 times, but the download url redirects here https://www.adobe.com/products/flashplayer/end-of-life.html where there is nothing to download, rendering the package not installable. Here is the full output of apt Unpacking pepperflashplugin-nonfree (1.8.7) ... Setting up pepperflashplugin-nonfree (1.8.7) ... --2021-01-10 07:26:28-- https://get.adobe.com/flashplayer/webservices/json/?platform_type=Linux_arch=x86_64_dist=Chrome Resolving get.adobe.com (get.adobe.com)... 193.104.215.66 Connecting to get.adobe.com (get.adobe.com)|193.104.215.66|:443... connected. HTTP request sent, awaiting response... 302 Found Location: https://www.adobe.com/products/flashplayer/end-of- life.html?platform_type=Linux_arch=x86_64_dist=Chrome [following] --2021-01-10 07:26:29-- https://www.adobe.com/products/flashplayer/end-of- life.html?platform_type=Linux_arch=x86_64_dist=Chrome Resolving www.adobe.com (www.adobe.com)... 212.205.43.11, 212.205.43.26, 2a02:587:8ff:25::d4cd:4da2, ... Connecting to www.adobe.com (www.adobe.com)|212.205.43.11|:443... connected. HTTP request sent, awaiting response... Read error (Connection timed out) in headers. Retrying. --2021-01-10 07:26:45-- (try: 2) https://www.adobe.com/products/flashplayer/end-of- life.html?platform_type=Linux_arch=x86_64_dist=Chrome Connecting to www.adobe.com (www.adobe.com)|212.205.43.11|:443... connected. HTTP request sent, awaiting response... Read error (Connection timed out) in headers. Retrying. --2021-01-10 07:27:02-- (try: 3) https://www.adobe.com/products/flashplayer/end-of- life.html?platform_type=Linux_arch=x86_64_dist=Chrome Connecting to www.adobe.com (www.adobe.com)|212.205.43.11|:443... connected. HTTP request sent, awaiting response... Read error (Connection timed out) in headers. Giving up. ERROR: failed to determine upstream version More information might be available at: http://wiki.debian.org/PepperFlashPlayer -- System Information: Debian Release: bullseye/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 5.10.0-1-amd64 (SMP w/2 CPU threads) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages pepperflashplugin-nonfree depends on: ii binutils 2.35.1-7 ii ca-certificates 20200601 ii libgcc-s110.2.1-3 ii libstdc++6 10.2.1-3 ii wget 1.21-1+b1 pepperflashplugin-nonfree recommends no packages. Versions of packages pepperflashplugin-nonfree suggests: pn chromium pn ttf-dejavu ii ttf-mscorefonts-installer 3.8 pn ttf-xfree86-nonfree -- no debconf information
Bug#979232: lighttpd: does not start with media-types 1.1.0
Package: lighttpd Version: 1.4.57-1 Followup-For: Bug #979232 X-Debbugs-Cc: pitsior...@gmail.com I have that one too! Downgrading media-types to 1.0.1 from testing fixes the issue, so I am pinning it until the next lighttpd update. Thank you both. -- System Information: Debian Release: bullseye/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 5.9.0-5-amd64 (SMP w/2 CPU threads) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages lighttpd depends on: ii init-system-helpers 1.60 ii libc62.31-6 ii libcrypt11:4.4.17-1 ii libnettle8 3.6-2 ii libpcre3 2:8.39-13 ii libxxhash0 0.8.0-1 ii lsb-base 11.1.0 ii mime-support 3.66 Versions of packages lighttpd recommends: pn lighttpd-mod-deflate pn lighttpd-mod-openssl ii perl 5.32.0-6 pn spawn-fcgi Versions of packages lighttpd suggests: pn apache2-utils pn lighttpd-doc pn lighttpd-mod-authn-gssapi pn lighttpd-mod-authn-pam pn lighttpd-mod-authn-sasl pn lighttpd-mod-geoip pn lighttpd-mod-maxminddb pn lighttpd-mod-trigger-b4-dl pn lighttpd-mod-vhostdb-pgsql pn lighttpd-mod-webdav pn lighttpd-modules-dbi pn lighttpd-modules-ldap pn lighttpd-modules-lua pn lighttpd-modules-mysql ii openssl 1.1.1i-1 pn php-cgi pn php-fpm pn rrdtool -- no debconf information
Bug#978749: reportbug: Updating python3-chardet to 4.0.0 wants to remove reportbug
Package: reportbug Version: 7.9.0 Severity: normal X-Debbugs-Cc: pitsior...@gmail.com As said in the title, today's upgrade of python3-chardet to 4.0.0 (in unstable) wants to remove reportbug The following packages were automatically installed and are no longer required: python-apt-common python3-apt python3-certifi python3-chardet python3-debian python3-debianbts python3-httplib2 python3-idna python3-pycurl python3-pysimplesoap python3-urllib3 Use 'apt autoremove' to remove them. The following packages will be REMOVED: python3-reportbug python3-requests reportbug The following packages will be upgraded: python3-chardet 1 upgraded, 0 newly installed, 3 to remove and 0 not upgraded. Need to get 0 B/99.0 kB of archives. After this operation, 218 kB disk space will be freed. Do you want to continue? [Y/n] n Python3-chardet is a dependency of python3-requests, which in turn is a dependency of python3-reportbug. It is that simple. Thank you in advance and happy new year :) -- Package-specific info: ** Environment settings: INTERFACE="gtk" ** /home/jim/.reportbugrc: reportbug_version "7.8.0" mode standard ui gtk realname "jim_p" email "pitsior...@gmail.com" no-cc list-cc-me smtphost reportbug.debian.org -- System Information: Debian Release: bullseye/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 5.9.0-5-amd64 (SMP w/2 CPU threads) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages reportbug depends on: ii apt2.1.12+deb11u1 ii python33.9.0-4 ii python3-reportbug 7.9.0 ii sensible-utils 0.0.12+nmu1 reportbug recommends no packages. Versions of packages reportbug suggests: pn claws-mail pn debconf-utils pn debsums pn dlocate pn emacs-bin-common ii file 1:5.39-3 ii gnupg 2.2.20-1 pn python3-urwid pn reportbug-gtk ii ssmtp [mail-transport-agent] 2.64-9 ii xdg-utils 1.1.3-2 Versions of packages python3-reportbug depends on: ii apt2.1.12+deb11u1 ii file 1:5.39-3 ii python33.9.0-4 ii python3-apt2.1.7 ii python3-debian 0.1.39 ii python3-debianbts 3.1.0 ii python3-requests 2.24.0+dfsg-1 ii sensible-utils 0.0.12+nmu1 python3-reportbug suggests no packages. -- no debconf information
Bug#973785: gcc-10: Huge package sizes of gcc-10 and cpp-10 on amd64
Package: gcc-10 Followup-For: Bug #973785 X-Debbugs-Cc: pitsior...@gmail.com Solved after today's update to 10.2.1-3. You can close this bug report. -- System Information: Debian Release: bullseye/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 5.9.0-5-amd64 (SMP w/2 CPU threads) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages gcc-10 depends on: ii binutils 2.35.1-6 ii cpp-10 10.2.1-3 ii gcc-10-base10.2.1-3 ii libc6 2.31-6 ii libcc1-0 10.2.1-3 ii libgcc-10-dev 10.2.1-3 ii libgcc-s1 10.2.1-3 ii libgmp10 2:6.2.1+dfsg-1 ii libisl23 0.23-1 ii libmpc31.2.0-1 ii libmpfr6 4.1.0-3 ii libstdc++6 10.2.1-3 ii libzstd1 1.4.5+dfsg-4 ii zlib1g 1:1.2.11.dfsg-2 Versions of packages gcc-10 recommends: pn libc6-dev Versions of packages gcc-10 suggests: pn gcc-10-doc pn gcc-10-locales pn gcc-10-multilib -- no debconf information
Bug#975398: reportbug crashes with Python 3.9
Package: python3-reportbug Version: 7.8.0 Followup-For: Bug #975398 X-Debbugs-Cc: pitsior...@gmail.com When shall we expect the updated version to reach the repos? Obviously, reportbug stopped working properly for me too and I (well... a friend of mine) had to apply the forementioned patch to get it back. -- System Information: Debian Release: bullseye/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 5.9.0-4-amd64 (SMP w/2 CPU threads) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages python3-reportbug depends on: ii apt2.1.12 ii file 1:5.39-3 ii python33.9.0-4 ii python3-apt2.1.7 ii python3-debian 0.1.38 ii python3-debianbts 3.0.2 ii python3-requests 2.24.0+dfsg-1 ii sensible-utils 0.0.12+nmu1 python3-reportbug recommends no packages. Versions of packages python3-reportbug suggests: ii reportbug 7.8.0 -- no debconf information
Bug#977263: midori: A lot of changes in midori
Package: midori Severity: normal Tags: upstream X-Debbugs-Cc: pitsior...@gmail.com Dear Maintainer, Leaving aside that midori in debian completely missed versions 8 and 9, although they were both released in 2019 from upstream, TIL that a lot has changed in midori since 2019. First, it is now made by astian.org as you can see here. It also has a new logo. https://astian.org/en/midori-browser/ Second, its code is now on gitlab and it versioning scheme is now 1.x. https://gitlab.com/midori-web/midori-desktop Last but not least, it is now chromium based and its ui is built with electron. So, maybe it is time to remove it from the repo. -- System Information: Debian Release: bullseye/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 5.9.0-4-amd64 (SMP w/2 CPU threads) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages midori depends on: ii libc6 2.31-5 ii libcairo2 1.16.0-4 ii libgcr-base-3-1 3.38.0-1 ii libgcr-ui-3-1 3.38.0-1 ii libgdk-pixbuf2.0-02.40.2-2 ii libglib2.0-0 2.66.3-2 ii libgtk-3-03.24.23-3 pn libpeas-1.0-0 ii libsoup2.4-1 2.72.0-2 ii libsqlite3-0 3.34.0-1 pn libwebkit2gtk-4.0-37 Versions of packages midori recommends: ii gnome-icon-theme 3.12.0-3 ii gnome-keyring 3.36.0-1 midori suggests no packages.
Bug#976056: nvidia-legacy-340xx-driver: requires DRM_LEGACY, disabled from Linux 5.9.11 onwards
Package: nvidia-legacy-340xx-driver Followup-For: Bug #976056 X-Debbugs-Cc: pitsior...@gmail.com Thank you very much! I promise to do my best to keep the driver in the repo. -- Package-specific info: uname -a: Linux mitsos 5.9.0-4-amd64 #1 SMP Debian 5.9.11-1 (2020-11-27) x86_64 GNU/Linux /proc/version: Linux version 5.9.0-4-amd64 (debian-ker...@lists.debian.org) (gcc-10 (Debian 10.2.0-19) 10.2.0, GNU ld (GNU Binutils for Debian) 2.35.1) #1 SMP Debian 5.9.11-1 (2020-11-27) /proc/driver/nvidia/version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 340.108 Wed Dec 11 11:06:58 PST 2019 GCC version: gcc version 10.2.0 (Debian 10.2.0-19) lspci 'display controller [030?]': 01:00.0 VGA compatible controller [0300]: NVIDIA Corporation GT218 [GeForce 210] [10de:0a65] (rev a2) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. GT218 [GeForce 210] [1043:8490] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- Kernel driver in use: nvidia Kernel modules: nvidia dmesg: [0.152317] Console: colour VGA+ 80x25 [0.590606] pci :01:00.0: vgaarb: setting as boot VGA device [0.590606] pci :01:00.0: vgaarb: VGA device added: decodes=io+mem,owns=io+mem,locks=none [0.590606] pci :01:00.0: vgaarb: bridge control possible [0.590606] vgaarb: loaded [0.775094] Linux agpgart interface v0.103 [3.173415] nvidia: loading out-of-tree module taints kernel. [3.173428] nvidia: module license 'NVIDIA' taints kernel. [3.208547] nvidia: module verification failed: signature and/or required key missing - tainting kernel [3.231209] nvidia :01:00.0: vgaarb: changed VGA decodes: olddecodes=io+mem,decodes=none:owns=io+mem [3.236669] [drm] Initialized nvidia-drm 0.0.0 20150116 for :01:00.0 on minor 0 [3.236681] NVRM: loading NVIDIA UNIX x86_64 Kernel Module 340.108 Wed Dec 11 11:06:58 PST 2019 [3.591137] snd_hda_intel :01:00.1: Handle vga_switcheroo audio client [3.679014] input: HDA NVidia HDMI/DP,pcm=3 as /devices/pci:00/:00:01.0/:01:00.1/sound/card1/input13 [3.692947] input: HDA NVidia HDMI/DP,pcm=7 as /devices/pci:00/:00:01.0/:01:00.1/sound/card1/input18 [3.693015] input: HDA NVidia HDMI/DP,pcm=8 as /devices/pci:00/:00:01.0/:01:00.1/sound/card1/input19 [3.693255] input: HDA NVidia HDMI/DP,pcm=9 as /devices/pci:00/:00:01.0/:01:00.1/sound/card1/input20 [9.534743] caller _nv000788rm+0xe4/0x1c0 [nvidia] mapping multiple BARs Device node permissions: crw-rw+ 1 root video 226, 0 Dec 9 11:55 /dev/dri/card0 crw-rw-rw- 1 root root 195, 0 Dec 9 11:56 /dev/nvidia0 crw-rw-rw- 1 root root 195, 255 Dec 9 11:56 /dev/nvidiactl /dev/dri/by-path: total 0 lrwxrwxrwx 1 root root 8 Dec 9 11:55 pci-:01:00.0-card -> ../card0 video:*:44:jim OpenGL and NVIDIA library files installed: lrwxrwxrwx 1 root root 15 Jun 8 2020 /etc/alternatives/glx -> /usr/lib/nvidia lrwxrwxrwx 1 root root 44 Jun 8 2020 /etc/alternatives/glx--libEGL.so.1-x86_64-linux-gnu -> /usr/lib/x86_64-linux-gnu/nvidia/libEGL.so.1 lrwxrwxrwx 1 root root 43 Jun 8 2020 /etc/alternatives/glx--libGL.so.1-x86_64-linux-gnu -> /usr/lib/x86_64-linux-gnu/nvidia/libGL.so.1 lrwxrwxrwx 1 root root 43 Jun 8 2020 /etc/alternatives/glx--libGL.so.1-x86_64-linux-gnu -> /usr/lib/x86_64-linux-gnu/nvidia/libGL.so.1 lrwxrwxrwx 1 root root 25 Jun 8 2020 /etc/alternatives/glx--linux-libglx.so -> /usr/lib/nvidia/libglx.so lrwxrwxrwx 1 root root 42 Jun 8 2020 /etc/alternatives/glx--nvidia-blacklists-nouveau.conf -> /etc/nvidia/nvidia-blacklists-nouveau.conf lrwxrwxrwx 1 root root 36 Jun 8 2020 /etc/alternatives/glx--nvidia-bug-report.sh -> /usr/lib/nvidia/nvidia-bug-report.sh lrwxrwxrwx 1 root root 39 Jun 8 2020 /etc/alternatives/glx--nvidia-drm-outputclass.conf -> /etc/nvidia/nvidia-drm-outputclass.conf lrwxrwxrwx 1 root root 28 Jun 8 2020 /etc/alternatives/glx--nvidia-load.conf -> /etc/nvidia/nvidia-load.conf lrwxrwxrwx 1 root root 32 Jun 8 2020 /etc/alternatives/glx--nvidia-modprobe.conf -> /etc/nvidia/nvidia-modprobe.conf lrwxrwxrwx 1 root root 29 Jun 8 2020 /etc/alternatives/glx--nvidia_drv.so -> /usr/lib/nvidia/nvidia_drv.so lrwxrwxrwx 1 root root 28 Dec 1 16:00 /etc/alternatives/nvidia -> /usr/lib/nvidia/legacy-340xx lrwxrwxrwx 1 root root 57 Dec 1 16:00 /etc/alternatives/nvidia--libEGL.so.1-x86_64-linux-gnu -> /usr/lib/x86_64-linux-gnu/nvidia/legacy-340xx/libEGL.so.1 lrwxrwxrwx 1 root root 56 Dec 1 16:00 /etc/alternatives/nvidia--libGL.so.1-x86_64-linux-gnu -> /usr/lib/x86_64-linux-gnu/nvidia/legacy-340xx/libGL.so.1 lrwxrwxrwx 1 root root 56 Dec 1 16:00 /etc/alternatives/nvidia--libGL.so.1-x86_64-linux-gnu ->
Bug#976007: adb: Adb completely broken after today's update in android-libboringssl (testing branch)
Package: adb Followup-For: Bug #976007 X-Debbugs-Cc: pitsior...@gmail.com Now that every single package of android-platform-system-core has reached testing, the bug has been resolved, so please close this report. The same applies to #975707. Thank you. -- System Information: Debian Release: bullseye/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 5.9.0-3-amd64 (SMP w/2 CPU threads) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages adb depends on: ii android-libadb 1:10.0.0+r36-1~stage1.3 ii android-libbase 1:10.0.0+r36-1~stage1.3 ii libc62.31-5 ii libgcc-s110.2.0-19 ii libstdc++6 10.2.0-19 Versions of packages adb recommends: ii android-sdk-platform-tools-common 27.0.0+12 adb suggests no packages. -- no debconf information
Bug#976632: obsession: Project dead from upstream
Package: obsession Version: 20140608-2+b1 Followup-For: Bug #976632 X-Debbugs-Cc: pitsior...@gmail.com Well, I use it alongside fbpanel, which was removed from testing due to some ftbfs issue with gcc10. I plan to replace it with lxpanel, which has some built in function for a shutdown "menu"... that I do not recall now. I have no idea about xdg-autostart and the like, sorry :( Leaving that rise in popularity aside, which is really big for a package that has not seen a single update for years, I think it should be removed from the repo. Sadly, there is no similar or equivalent right now so as to make a transitional package for it. -- System Information: Debian Release: bullseye/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 5.9.0-3-amd64 (SMP w/2 CPU threads) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages obsession depends on: ii libc6 2.31-5 ii libcairo2 1.16.0-4 ii libgdk-pixbuf2.0-0 2.40.0+dfsg-8 ii libglib2.0-02.66.3-2 ii libgtk2.0-0 2.24.32-5 Versions of packages obsession recommends: ii gnome-icon-theme 3.12.0-3 obsession suggests no packages. -- no debconf information
Bug#976056: nvidia-legacy-340xx-driver: requires DRM_LEGACY, disabled from Linux 5.9.11 onwards
Package: nvidia-legacy-340xx-driver Version: 340.108-8 Followup-For: Bug #976056 X-Debbugs-Cc: pitsior...@gmail.com First of all, I am really sorry about the annoying logs that spawn under every message of mine. I am not putting them there on purpose, this is all reportbug's work. I tried setting it to advanced and expert, hoping that it will be less spammy, but it isn't. I admit I have no idea on how to report a bug outside reportbug. About the "nvidia-blacklists-nouveau.conf". I had to use nouveau some months ago too (for like 1 hour at most, thankfully) and that file was removed when I purged some nvidia package. I have no idea why it is not removed anymore. A file with the same name but under a different path exists in nvidia- legacy-340xx-kernel-support. As for the rest. I accept that the bug is not related to the driver directly but to the kernel. But from my point of view, because it showed up when I upgraded to 5.9.11 from sid, it remains a bug in the driver and the patch I posted above IS for the driver! However, the patch does not work, probably because it conflicts with another patch. It does work with no issues on another distro that uses the same kernel version and the has the same kernel parameter disabled. It also works when it is applied to the "source" of the driver (tested on a virtual machine by a friend of mine). Last but not least, although I can not say I am "mad" at debian for this, I think that it non-free is a part of debian and should receive equal support. Besides, for ~2 years now (since 5.2 if I recall correctly), I do my best to keep this driver in the repo. I am (usually) the first to open the bug report and to find the needed patches. My last hope is 5.10. It will stay in the repos for the entire first half of 2021, since debian will be on a freeze for 11. I will do my best to make nvidia legacy 340 work with it, but if if I get no help, I will move to another distro (arch) before the release of debian 11. At least I will enjoy an up to date chromium there... -- Package-specific info: uname -a: Linux mitsos 5.9.0-3-amd64 #1 SMP Debian 5.9.9-1 (2020-11-19) x86_64 GNU/Linux /proc/version: Linux version 5.9.0-3-amd64 (debian-ker...@lists.debian.org) (gcc-10 (Debian 10.2.0-17) 10.2.0, GNU ld (GNU Binutils for Debian) 2.35.1) #1 SMP Debian 5.9.9-1 (2020-11-19) /proc/driver/nvidia/version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 340.108 Wed Dec 11 11:06:58 PST 2019 GCC version: gcc version 10.2.0 (Debian 10.2.0-19) lspci 'display controller [030?]': 01:00.0 VGA compatible controller [0300]: NVIDIA Corporation GT218 [GeForce 210] [10de:0a65] (rev a2) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. GT218 [GeForce 210] [1043:8490] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- Kernel driver in use: nvidia Kernel modules: nvidia dmesg: [0.152130] Console: colour VGA+ 80x25 [0.588297] pci :01:00.0: vgaarb: setting as boot VGA device [0.588297] pci :01:00.0: vgaarb: VGA device added: decodes=io+mem,owns=io+mem,locks=none [0.588297] pci :01:00.0: vgaarb: bridge control possible [0.588297] vgaarb: loaded [0.774547] Linux agpgart interface v0.103 [3.185919] nvidia: loading out-of-tree module taints kernel. [3.185930] nvidia: module license 'NVIDIA' taints kernel. [3.220590] nvidia: module verification failed: signature and/or required key missing - tainting kernel [3.250196] nvidia :01:00.0: vgaarb: changed VGA decodes: olddecodes=io+mem,decodes=none:owns=io+mem [3.250623] [drm] Initialized nvidia-drm 0.0.0 20150116 for :01:00.0 on minor 0 [3.250636] NVRM: loading NVIDIA UNIX x86_64 Kernel Module 340.108 Wed Dec 11 11:06:58 PST 2019 [3.834283] snd_hda_intel :01:00.1: Handle vga_switcheroo audio client [3.923444] input: HDA NVidia HDMI/DP,pcm=3 as /devices/pci:00/:00:01.0/:01:00.1/sound/card1/input9 [3.923538] input: HDA NVidia HDMI/DP,pcm=7 as /devices/pci:00/:00:01.0/:01:00.1/sound/card1/input10 [3.923959] input: HDA NVidia HDMI/DP,pcm=8 as /devices/pci:00/:00:01.0/:01:00.1/sound/card1/input11 [3.924154] input: HDA NVidia HDMI/DP,pcm=9 as /devices/pci:00/:00:01.0/:01:00.1/sound/card1/input12 [8.576505] caller _nv000788rm+0xe4/0x1c0 [nvidia] mapping multiple BARs Device node permissions: crw-rw+ 1 root video 226, 0 Dec 7 15:17 /dev/dri/card0 crw-rw-rw- 1 root root 195, 0 Dec 7 15:19 /dev/nvidia0 crw-rw-rw- 1 root root 195, 255 Dec 7 15:19 /dev/nvidiactl /dev/dri/by-path: total 0 lrwxrwxrwx 1 root root 8 Dec 7 15:17 pci-:01:00.0-card -> ../card0 video:*:44:jim OpenGL and NVIDIA library files installed: lrwxrwxrwx 1 root root 15 Jun 8 11:36 /etc/alternatives/glx -> /usr/lib/nvidia lrwxrwxrwx 1 root root
Bug#976632: obsession: Project dead from upstream
Package: obsession Version: 20140608-2+b1 Severity: normal Tags: upstream X-Debbugs-Cc: pitsior...@gmail.com As it seems, the project is dead. The link to bitbucket leads to a 404. Plus its developer* has probably moved to github and obsession is not among the things he currently maintains. So, I think it is time to remove it from the repo. 6 years with no new versions are more than enough to justify that. * https://github.com/fabriceT -- System Information: Debian Release: bullseye/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 5.9.0-3-amd64 (SMP w/2 CPU threads) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages obsession depends on: ii libc6 2.31-5 ii libcairo2 1.16.0-4 ii libgdk-pixbuf2.0-0 2.40.0+dfsg-8 ii libglib2.0-02.66.3-1 ii libgtk2.0-0 2.24.32-5 Versions of packages obsession recommends: ii gnome-icon-theme 3.12.0-3 obsession suggests no packages. -- no debconf information
Bug#976056: nvidia-legacy-340xx-driver: requires DRM_LEGACY, disabled from Linux 5.9.11 onwards
Package: nvidia-legacy-340xx-driver Version: 340.108-8 Followup-For: Bug #976056 X-Debbugs-Cc: pitsior...@gmail.com I tried using the patch for 5.9 from aur, with the help of a friend who is using arch, but dkms failed to build the module dkms: running auto installation service for kernel 5.9.0-4-amd64: Kernel preparation unnecessary for this kernel. Skipping... applying patch unregister_procfs_on_failure.patch...patching file nv.c applying patch kmem_cache_create_usercopy.patch...patching file nv-linux.h Hunk #1 succeeded at 772 (offset 15 lines). applying patch buildfix_kernel_4.11.patch...patching file uvm/nvidia_uvm_lite.c Hunk #1 FAILED at 820. Hunk #2 FAILED at 868. 2 out of 2 hunks FAILED -- saving rejects to file uvm/nvidia_uvm_lite.c.rej (bad exit status: 1) Error! Application of patch buildfix_kernel_4.11.patch failed. Check /var/lib/dkms/nvidia-legacy-340xx/340.108/build/ for more information. On the other hand, I tried the liquorix kernel, which has the parameter in question still set to Y, and dkms builds the module successfully Building module: cleaning build area... unset ARCH; env NV_VERBOSE=1 make -j2 modules KERNEL_UNAME=5.9.0-12.1-liquorix- amd64; env CCACHE_DISABLE=1 NV_VERBOSE=1 make -C uvm modules KERNEL_UNAME=5.9.0-12.1-liquorix-amd64 KBUILD_EXTMOD=/var/lib/dkms/nvidia- legacy-340xx/340.108/build/uvm... cleaning build area... DKMS: build completed. nvidia-legacy-340xx.ko: Running module version sanity check. - Original module - No original module exists within this kernel - Installation - Installing to /lib/modules/5.9.0-12.1-liquorix-amd64/updates/dkms/ nvidia-legacy-340xx-uvm.ko: Running module version sanity check. - Original module - No original module exists within this kernel - Installation - Installing to /lib/modules/5.9.0-12.1-liquorix-amd64/updates/dkms/ depmod... DKMS: install completed. -- Package-specific info: uname -a: Linux mitsos 5.9.0-3-amd64 #1 SMP Debian 5.9.9-1 (2020-11-19) x86_64 GNU/Linux /proc/version: Linux version 5.9.0-3-amd64 (debian-ker...@lists.debian.org) (gcc-10 (Debian 10.2.0-17) 10.2.0, GNU ld (GNU Binutils for Debian) 2.35.1) #1 SMP Debian 5.9.9-1 (2020-11-19) /proc/driver/nvidia/version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 340.108 Wed Dec 11 11:06:58 PST 2019 GCC version: gcc version 10.2.0 (Debian 10.2.0-16) lspci 'display controller [030?]': 01:00.0 VGA compatible controller [0300]: NVIDIA Corporation GT218 [GeForce 210] [10de:0a65] (rev a2) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. GT218 [GeForce 210] [1043:8490] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- Kernel driver in use: nvidia Kernel modules: nvidia dmesg: [0.152307] Console: colour VGA+ 80x25 [0.589115] pci :01:00.0: vgaarb: setting as boot VGA device [0.589115] pci :01:00.0: vgaarb: VGA device added: decodes=io+mem,owns=io+mem,locks=none [0.589115] pci :01:00.0: vgaarb: bridge control possible [0.589115] vgaarb: loaded [0.773963] Linux agpgart interface v0.103 [3.240399] nvidia: loading out-of-tree module taints kernel. [3.240410] nvidia: module license 'NVIDIA' taints kernel. [3.304505] nvidia: module verification failed: signature and/or required key missing - tainting kernel [3.343455] nvidia :01:00.0: vgaarb: changed VGA decodes: olddecodes=io+mem,decodes=none:owns=io+mem [3.348688] [drm] Initialized nvidia-drm 0.0.0 20150116 for :01:00.0 on minor 0 [3.348701] NVRM: loading NVIDIA UNIX x86_64 Kernel Module 340.108 Wed Dec 11 11:06:58 PST 2019 [3.779449] snd_hda_intel :01:00.1: Handle vga_switcheroo audio client [3.884763] input: HDA NVidia HDMI/DP,pcm=3 as /devices/pci:00/:00:01.0/:01:00.1/sound/card1/input9 [3.884858] input: HDA NVidia HDMI/DP,pcm=7 as /devices/pci:00/:00:01.0/:01:00.1/sound/card1/input10 [3.884992] input: HDA NVidia HDMI/DP,pcm=8 as /devices/pci:00/:00:01.0/:01:00.1/sound/card1/input11 [3.886571] input: HDA NVidia HDMI/DP,pcm=9 as /devices/pci:00/:00:01.0/:01:00.1/sound/card1/input12 [8.695372] caller _nv000788rm+0xe4/0x1c0 [nvidia] mapping multiple BARs Device node permissions: crw-rw+ 1 root video 226, 0 Dec 5 15:35 /dev/dri/card0 crw-rw-rw- 1 root root 195, 0 Dec 5 15:36 /dev/nvidia0 crw-rw-rw- 1 root root 195, 255 Dec 5 15:36 /dev/nvidiactl /dev/dri/by-path: total 0 lrwxrwxrwx 1 root root 8 Dec 5 15:35 pci-:01:00.0-card -> ../card0 video:*:44:jim OpenGL and NVIDIA library files installed: lrwxrwxrwx 1 root root 15 Jun 8 11:36 /etc/alternatives/glx -> /usr/lib/nvidia lrwxrwxrwx 1 root root 44 Jun 8 11:36 /etc/alternatives/glx--libEGL.so.1-x86_64-linux-gnu ->
Bug#976007: adb: Adb completely broken after today's update in android-libboringssl (testing branch)
Package: adb Followup-For: Bug #976007 X-Debbugs-Cc: pitsior...@gmail.com Fixed in v10.x that finally reached unstable earlier for amd64 and i386! $ adb devices List of devices attached ABCDEF1234567890device The same applies to #975707. Thank you very much. -- System Information: Debian Release: bullseye/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 5.9.0-3-amd64 (SMP w/2 CPU threads) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages adb depends on: ii android-libadb 1:10.0.0+r36-1~stage1.3 ii android-libbase 1:10.0.0+r36-1~stage1.3 ii libc62.31-4 ii libgcc-s110.2.0-19 ii libstdc++6 10.2.0-19 Versions of packages adb recommends: ii android-sdk-platform-tools-common 27.0.0+12 adb suggests no packages. -- no debconf information
Bug#976056: nvidia-legacy-340xx-driver: requires DRM_LEGACY, disabled from Linux 5.9.11 onwards
Package: nvidia-legacy-340xx-driver Version: 340.108-8 Followup-For: Bug #976056 X-Debbugs-Cc: pitsior...@gmail.com So, 5.9.11 has just reached testing. Too bad I can not upgrade to it because of this bug here. I will wait for 5.10 to reach the repos and hope that a patch will be found by then. -- Package-specific info: uname -a: Linux mitsos 5.9.0-3-amd64 #1 SMP Debian 5.9.9-1 (2020-11-19) x86_64 GNU/Linux /proc/version: Linux version 5.9.0-3-amd64 (debian-ker...@lists.debian.org) (gcc-10 (Debian 10.2.0-17) 10.2.0, GNU ld (GNU Binutils for Debian) 2.35.1) #1 SMP Debian 5.9.9-1 (2020-11-19) /proc/driver/nvidia/version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 340.108 Wed Dec 11 11:06:58 PST 2019 GCC version: gcc version 10.2.0 (Debian 10.2.0-16) lspci 'display controller [030?]': 01:00.0 VGA compatible controller [0300]: NVIDIA Corporation GT218 [GeForce 210] [10de:0a65] (rev a2) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. GT218 [GeForce 210] [1043:8490] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- Kernel driver in use: nvidia Kernel modules: nvidia dmesg: [0.151969] Console: colour VGA+ 80x25 [0.588136] pci :01:00.0: vgaarb: setting as boot VGA device [0.588136] pci :01:00.0: vgaarb: VGA device added: decodes=io+mem,owns=io+mem,locks=none [0.588136] pci :01:00.0: vgaarb: bridge control possible [0.588136] vgaarb: loaded [0.773397] Linux agpgart interface v0.103 [3.167781] nvidia: loading out-of-tree module taints kernel. [3.167793] nvidia: module license 'NVIDIA' taints kernel. [3.204354] nvidia: module verification failed: signature and/or required key missing - tainting kernel [3.227012] nvidia :01:00.0: vgaarb: changed VGA decodes: olddecodes=io+mem,decodes=none:owns=io+mem [3.230993] [drm] Initialized nvidia-drm 0.0.0 20150116 for :01:00.0 on minor 0 [3.231007] NVRM: loading NVIDIA UNIX x86_64 Kernel Module 340.108 Wed Dec 11 11:06:58 PST 2019 [3.764470] snd_hda_intel :01:00.1: Handle vga_switcheroo audio client [3.911808] input: HDA NVidia HDMI/DP,pcm=3 as /devices/pci:00/:00:01.0/:01:00.1/sound/card1/input10 [3.911934] input: HDA NVidia HDMI/DP,pcm=7 as /devices/pci:00/:00:01.0/:01:00.1/sound/card1/input11 [3.912015] input: HDA NVidia HDMI/DP,pcm=8 as /devices/pci:00/:00:01.0/:01:00.1/sound/card1/input12 [3.912089] input: HDA NVidia HDMI/DP,pcm=9 as /devices/pci:00/:00:01.0/:01:00.1/sound/card1/input13 [8.757001] caller _nv000788rm+0xe4/0x1c0 [nvidia] mapping multiple BARs Device node permissions: crw-rw+ 1 root video 226, 0 Dec 2 10:25 /dev/dri/card0 crw-rw-rw- 1 root root 195, 0 Dec 2 10:26 /dev/nvidia0 crw-rw-rw- 1 root root 195, 255 Dec 2 10:26 /dev/nvidiactl /dev/dri/by-path: total 0 lrwxrwxrwx 1 root root 8 Dec 2 10:25 pci-:01:00.0-card -> ../card0 video:*:44:jim OpenGL and NVIDIA library files installed: lrwxrwxrwx 1 root root 15 Jun 8 11:36 /etc/alternatives/glx -> /usr/lib/nvidia lrwxrwxrwx 1 root root 44 Jun 8 11:36 /etc/alternatives/glx--libEGL.so.1-x86_64-linux-gnu -> /usr/lib/x86_64-linux-gnu/nvidia/libEGL.so.1 lrwxrwxrwx 1 root root 43 Jun 8 11:36 /etc/alternatives/glx--libGL.so.1-x86_64-linux-gnu -> /usr/lib/x86_64-linux-gnu/nvidia/libGL.so.1 lrwxrwxrwx 1 root root 43 Jun 8 11:36 /etc/alternatives/glx--libGL.so.1-x86_64-linux-gnu -> /usr/lib/x86_64-linux-gnu/nvidia/libGL.so.1 lrwxrwxrwx 1 root root 25 Jun 8 11:36 /etc/alternatives/glx--linux-libglx.so -> /usr/lib/nvidia/libglx.so lrwxrwxrwx 1 root root 42 Jun 8 11:36 /etc/alternatives/glx--nvidia-blacklists-nouveau.conf -> /etc/nvidia/nvidia-blacklists-nouveau.conf lrwxrwxrwx 1 root root 36 Jun 8 11:36 /etc/alternatives/glx--nvidia-bug-report.sh -> /usr/lib/nvidia/nvidia-bug-report.sh lrwxrwxrwx 1 root root 39 Jun 8 11:36 /etc/alternatives/glx--nvidia-drm-outputclass.conf -> /etc/nvidia/nvidia-drm-outputclass.conf lrwxrwxrwx 1 root root 28 Jun 8 11:36 /etc/alternatives/glx--nvidia-load.conf -> /etc/nvidia/nvidia-load.conf lrwxrwxrwx 1 root root 32 Jun 8 11:36 /etc/alternatives/glx--nvidia-modprobe.conf -> /etc/nvidia/nvidia-modprobe.conf lrwxrwxrwx 1 root root 29 Jun 8 11:36 /etc/alternatives/glx--nvidia_drv.so -> /usr/lib/nvidia/nvidia_drv.so lrwxrwxrwx 1 root root 28 Dec 1 16:00 /etc/alternatives/nvidia -> /usr/lib/nvidia/legacy-340xx lrwxrwxrwx 1 root root 57 Dec 1 16:00 /etc/alternatives/nvidia--libEGL.so.1-x86_64-linux-gnu -> /usr/lib/x86_64-linux-gnu/nvidia/legacy-340xx/libEGL.so.1 lrwxrwxrwx 1 root root 56 Dec 1 16:00 /etc/alternatives/nvidia--libGL.so.1-x86_64-linux-gnu -> /usr/lib/x86_64-linux-gnu/nvidia/legacy-340xx/libGL.so.1
