Package: intel-microcode Version: 3.20190514.1 Severity: normal Tags: d-i Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? A new installation with Buster RC1-installer made it impossible to login in GNOME with default Wayland-session enabled. You are not able to login and you are immediately back to GDM3. It was possible though to activate Gnome Xorg- session in GDM3 and you can login with Xorg. Processor is Intel Core I5-2520M and GPU is Intel Corporation 2nd generation core processor Family Integrated Graphics Controller (rev 09) * What exactly did you do (or not do) that was effective (or ineffective)? Installing intel-microcode provided the solution to login with Wayland. This was the only package that was added. No other packages or updates were applied. * What was the outcome of this action? * What outcome did you expect instead? -- System Information: Debian Release: 10.0 APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.19.0-5-amd64 (SMP w/8 CPU cores) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=nl_BE.UTF-8, LC_CTYPE=nl_BE.UTF-8 (charmap=UTF-8), LANGUAGE=nl_BE:nl (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages intel-microcode depends on: ii iucode-tool 2.3.1-1 Versions of packages intel-microcode recommends: ii initramfs-tools 0.133 intel-microcode suggests no packages. -- no debconf information
