Your message dated Wed, 26 Feb 2020 17:34:19 +0000
with message-id
<CAD=6czr9vxfk5ooak8qxrxn915qvq62hpybzc+pxii9bzzf...@mail.gmail.com>
and subject line Close #942418 - libmutter-5-0: Blank screen after upgrading to
bullseye, caused by failing wayland
has caused the Debian Bug report #942418,
regarding libmutter-5-0: Blank screen after upgrading to bullseye, caused by
failing wayland
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
942418: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=942418
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: libmutter-5-0
Version: 3.34.1-1
Severity: critical
Justification: breaks the whole system
Dear Maintainer,
After upgrading from buster stable to bullseye testing and restarting,
only a blank screen appears.
Problem caused by failing wayland, which is by default enabled since
debian buster.
If wayland is disabled at /etc/gdm3/daemon.conf, the system started
without problem,
but with newer packages it only shows the logon-page, and after typing
correct password it shows blank screen with working mouse pointer.
Problem occurs both at mutter 3.34.0-4 (testing) and mutter 3.34.1-1
(unstable).
The log shows the next errors:
Oct 11 20:30:20 debian gnome-shell[970]: Failed to initialize
accelerated iGPU/dGPU framebuffer sharing: No matching EGL configs
Oct 11 20:30:20 debian gnome-shell[970]: Unable to initialize Clutter:
Unable to initialize the Clutter backend: no available drivers found.
Oct 11 20:30:20 debian gnome-shell[970]: Unable to initialize Clutter.
Oct 11 20:30:21 debian systemd[857]: gnome-shell-wayland.service: Failed
with result 'protocol'.
Oct 11 20:30:21 debian systemd[857]: Failed to start GNOME Shell on Wayland.
Oct 11 20:30:21 debian systemd[857]: Dependency failed for GNOME Shell
on Wayland.
Oct 11 20:30:21 debian systemd[857]: Dependency failed for GNOME Wayland
Session.
Oct 11 20:30:21 debian systemd[857]: Dependency failed for GNOME Wayland
Session (session: gnome-login).
Oct 11 20:30:21 debian systemd[857]:
[email protected]: Job
[email protected]/start failed with result
'dependency'.
Oct 11 20:30:21 debian systemd[857]: gnome-session-wayland.target: Job
gnome-session-wayland.target/start failed with result 'dependency'.
Oct 11 20:30:21 debian systemd[857]: gnome-session-wayland.target:
Triggering OnFailure= dependencies.
I am using a DELL D620:
Linux debian 5.2.0-3-686-pae #1 SMP Debian 5.2.17-1 (2019-09-26) i686
GNU/Linux
00:00.0 Host bridge: Intel Corporation Mobile 945GM/PM/GMS, 943/940GML
and 945GT Express Memory Controller Hub (rev 03)
Subsystem: Dell Mobile 945GM/PM/GMS, 943/940GML and 945GT Express
Memory Controller Hub
00:02.0 VGA compatible controller: Intel Corporation Mobile 945GM/GMS,
943/940GML Express Integrated Graphics Controller (rev 03)
Subsystem: Dell Mobile 945GM/GMS, 943/940GML Express Integrated
Graphics Controller
Kernel driver in use: i915
Kernel modules: i915
00:02.1 Display controller: Intel Corporation Mobile 945GM/GMS/GME,
943/940GML Express Integrated Graphics Controller (rev 03)
Subsystem: Dell Mobile 945GM/GMS/GME, 943/940GML Express Integrated
Graphics Controller
-- System Information:
Debian Release: bullseye/sid
APT prefers testing
APT policy: (500, 'testing'), (200, 'unstable')
Architecture: i386 (i686)
Kernel: Linux 5.2.0-3-686-pae (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8),
LANGUAGE=en_US:en (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages libmutter-5-0 depends on:
ii gsettings-desktop-schemas 3.34.0-2
ii libatk1.0-0 2.34.1-1
ii libc6 2.29-2
ii libcairo-gobject2 1.16.0-4
ii libcairo2 1.16.0-4
ii libcanberra0 0.30-7
ii libdrm2 2.4.99-1
ii libegl1 1.1.0-1+b1
ii libfontconfig1 2.13.1-2+b1
ii libfribidi0 1.0.7-1
ii libgbm1 19.1.6-1
ii libgdk-pixbuf2.0-0 2.40.0+dfsg-1
ii libgl1 1.1.0-1+b1
ii libglib2.0-0 2.62.1-1
ii libgnome-desktop-3-18 3.34.1-1
ii libgtk-3-0 3.24.12-1
ii libgudev-1.0-0 233-1
ii libice6 2:1.0.9-2
ii libinput10 1.14.1-2
ii libjson-glib-1.0-0 1.4.4-2
ii libpango-1.0-0 1.42.4-7
ii libpangocairo-1.0-0 1.42.4-7
ii libpangoft2-1.0-0 1.42.4-7
ii libpipewire-0.2-1 0.2.5-1
ii libsm6 2:1.2.3-1
ii libstartup-notification0 0.12-6
ii libsystemd0 242-7
ii libudev1 242-7
ii libwacom2 1.1-1
ii libwayland-server0 1.17.0-1
ii libx11-6 2:1.6.8-1
ii libx11-xcb1 2:1.6.8-1
ii libxau6 1:1.0.8-1+b2
ii libxcb-randr0 1.13.1-2
ii libxcb-res0 1.13.1-2
ii libxcb1 1.13.1-2
ii libxcomposite1 1:0.4.4-2
ii libxcursor1 1:1.2.0-2
ii libxdamage1 1:1.1.5-1
ii libxext6 2:1.3.3-1+b2
ii libxfixes3 1:5.0.3-1
ii libxi6 2:1.7.9-1
ii libxinerama1 2:1.1.4-2
ii libxkbcommon-x11-0 0.8.4-1
ii libxkbcommon0 0.8.4-1
ii libxkbfile1 1:1.0.9-2+b12
ii libxrandr2 2:1.5.1-1
ii libxtst6 2:1.2.3-1
ii mutter-common 3.34.1-1
libmutter-5-0 recommends no packages.
libmutter-5-0 suggests no packages.
Versions of packages libmutter-5-0 is related to:
ii libegl-mesa0 [libegl-vendor] 19.1.6-1
ii libgl1-mesa-dri 19.1.6-1
ii libglx-mesa0 [libglx-vendor] 19.1.6-1
-- no debconf information
--- End Message ---
--- Begin Message ---
version: 3.34.4-1
Hi,
I am closing this bug now since it seems to be fixed.
If you can still reproduce it feel free to reopen and provide more
information.
thanks,
regards,
Pedro
--- End Message ---
