Le ven. 10 avr. 2020 à 14:42, Simon McVittie <s...@debian.org> a écrit : > > 3.36.x should be in unstable, or even in testing, by then. You might > want to put your working 3.34.3 setup on "hold" in apt/aptitude for now. >
Seeing that you released to unstable 2 days ago, but doing an apt-get update doesn't change anything for me. Should I conclude that my mirror is late? (seeing the package when browing it though... http://ftp.fr.debian.org/debian/pool/main/m/mutter/) ``` $ date dimanche 12 avril 2020, 15:28:36 (UTC+0200) $ sudo apt-get update | grep sid Atteint :4 http://ftp.fr.debian.org/debian sid InRelease $ apt-cache policy mutter mutter: Installé : 3.34.3-1 Candidat : 3.34.4-1 Table de version : 3.34.4-1 500 500 http://ftp.fr.debian.org/debian bullseye/main amd64 Packages 2 http://ftp.fr.debian.org/debian sid/main amd64 Packages *** 3.34.3-1 100 100 /var/lib/dpkg/status ``` > > > You appear to have a dual-GPU system. Is the NVIDIA device completely > > > disabled, or are they both active via some sort of dual-GPU arrangement > > > like Bumblebee? > > You didn't answer this. If the NVIDIA device is disabled, how did you > disable it? Yes, actually I just didn't do any bumblebee setup of whatever related to nvidia drivers, but you're right that it doesn't mean my chip is disabled. Unfortunately, I just figured out that I cannot disable the chip since the wiring is the following: ``` $ sudo ls -l /sys/class/drm/card* lrwxrwxrwx 1 root root 0 avril 12 15:12 /sys/class/drm/card0 -> ../../devices/pci0000:00/0000:00:02.0/drm/card0 lrwxrwxrwx 1 root root 0 avril 12 15:12 /sys/class/drm/card0-LVDS-1 -> ../../devices/pci0000:00/0000:00:02.0/drm/card0/card0-LVDS-1 lrwxrwxrwx 1 root root 0 avril 12 15:12 /sys/class/drm/card0-VGA-1 -> ../../devices/pci0000:00/0000:00:02.0/drm/card0/card0-VGA-1 lrwxrwxrwx 1 root root 0 avril 12 15:12 /sys/class/drm/card1 -> ../../devices/pci0000:00/0000:00:01.0/0000:01:00.0/drm/card1 lrwxrwxrwx 1 root root 0 avril 12 15:12 /sys/class/drm/card1-DP-1 -> ../../devices/pci0000:00/0000:00:01.0/0000:01:00.0/drm/card1/card1-DP-1 lrwxrwxrwx 1 root root 0 avril 12 15:12 /sys/class/drm/card1-DP-2 -> ../../devices/pci0000:00/0000:00:01.0/0000:01:00.0/drm/card1/card1-DP-2 lrwxrwxrwx 1 root root 0 avril 12 15:12 /sys/class/drm/card1-DP-3 -> ../../devices/pci0000:00/0000:00:01.0/0000:01:00.0/drm/card1/card1-DP-3 ``` So in my case, LVDS-1 and DP-1 connected. > > Let me tell you that it's a mess if we consider all graphics + > > gnome-shell + plugins related logs :) > > Yes it is, but it might be helpful to show us anyway. Just did an apt-get upgrade + gdm3 stop/start > bug > gdm3 stop + dpkg-i <old_packages>. You'll find in attachment the full journald logs (between the gdm3 start and stop), concretely if I clean the thing a bit (remove pids, etc.) and do a diff, I see nothing obvious.. (I mean, there are a lot of errors, but present in both cases). > > If you're using GNOME Shell extensions, please test with them all disabled > and see whether that works (you can re-enable them afterwards). > Disabled everything, same behavior. > If you run the lspci command (install pciutils if you don't already have > it), what device is 00:1f.2? OK, it seems unrelated (and older anyway). ``` $ lspci | grep 00:1f.2 00:1f.2 RAID bus controller: Intel Corporation 82801 Mobile SATA Controller [RAID mode] (rev 04) ``` > Similarly, what device is 01:00.0? It's on its own separate PCIE bus if I > understand correctly, which probably means it's either your Intel GPU or > NVIDIA GPU. True, the NVIDIA GPU. ``` $ lspci | grep 01:00.0 01:00.0 VGA compatible controller: NVIDIA Corporation GK107GLM [Quadro K2000M] (rev a1) ``` > > Searching for the log messages suggests that booting with > intel_iommu=igfx_off > or > intel_iommu=off Tried these, didn't change anything.
logs.out
Description: Binary data