Bug#1025213: DRM platform with kms_swrast

[Gert van de Kraats]

If the i915 dri driver is present gnome-shell is using the DRM platform
(not the Wayland platform?) with this driver.
If i915 is not present gnome-shell uses the DRM platform with the
kms_swrast-driver!
I did not see this with the lsof-command, because the name of the 
"zink"-driver was
shown which is hard-linked to the other dri-drivers and was opened and 
checked

unsuccessfully before the "kms_swrast" driver.

I tried an old version 22.0.5-1 of kms_swrast driver, but that did not help.
I will open an issue upstream.

Bug#1025213: i915g

[Gert van de Kraats]

The Gallium dri driver i915 22.3.0 also at my laptop is working and
stops the flickering problem.
Unfortunately it still is not supported and also has issues.
Specially with shaders it is not compatible with classic i915.
Less shaders are compiled without errors and also there is no fallback
(which works at classic i915 but can be very slow).
See https://gitlab.freedesktop.org/mesa/mesa/-/issues/5417.

Bug#1025213: Extra info

[Gert van de Kraats]

I tried to install gnome-shell-common gnome-shell and
gnome-shell-extension-prefs 43.0.2.
This did not succeed because of failing login  (protocol)?

Then I compiled source gnome-shell 43.0.2 and installed at /usr/local...
I verified the version with gnome-shell --version.

This downgrade did not change anything. So gnome-shell itself is not the 
problem.


Subframes seem to be rendered OK, but old, already deleted subframes are 
repeatedly shown.

Do not know how to investigate further.
Upstream??

Bug#1025213: gnome-shell: Flickering and mangled screens on wayland if dri driver not available

[Gert van de Kraats]

Hello Simon,

Unfortunately my 32-bit Dell-laptop does not crash and I think the 
software-boys should not stop delivery of


software for older hardware, forcing to waste good working hardware.

Therefore I will use Debian testing as long as it supports 32-bit, so at 
least some one is testing something at 32-bit.


My previous upgrade was 2022-11-06, the next failing upgrade was 2022-11-27.

It contains 921 packages; also upgrade libgl1-mesa-dri:i386 22.2.0-1 
22.2.4-1 .


I am not sure problem is at gnome-shell itself.

I am almost sure it is not at mesa/swrast. I ran lsof for gnome-shell to 
check the open files.


If the i915 driver is present at X and wayland the i915 shared library 
is shown.


If the driver is not present at X the swrast library is shown, but not 
at wayland.


Perhaps gtk/pango is used for software-rendering at wayland.

I will try to downgrade gnome-shell and dependent packages.

Bug#1025213: gnome-shell: Flickering and mangled screens on wayland if dri driver not available

[Gert van de Kraats]

Package: gnome-shell
Version: 43.1-2
Severity: serious
Justification: Policy 3.8

Dear Maintainer,

Recently a general upgrade was executed with gnome-shell
upgrading from version 43.0-2 to 43.1-2.

After this upgrade the gnome-shell wayland screen is flickering
and mangled at any action. Flickering stops after short time,
but screen often is mangled.
During flickering different old or background screens are shown.
Also the logon-screen is flickering and mangled.

Some user-friendly person has decided to stop support for the i915 dri 
driver.

As a "service" the mesa-upgrade at Debian also automatically deletes this
driver.

If an old i915-dri driver is moved to the original location,
the flickering problem is gone.
Also if "Gnome on Xorg" is started there is no flickering problem.
In that case swrast is used for software rendering.
I do not know which method gnome with wayland is using, but it is not 
swrast.



-- System Information:
Debian Release: bookworm/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: i386 (i686)

Kernel: Linux 6.0.0-4-686-pae (SMP w/2 CPU threads; PREEMPT)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US:en

Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages gnome-shell depends on:
ii  dconf-gsettings-backend [gsettings-backend]  0.40.0-3
ii  gir1.2-accountsservice-1.0   22.08.8-1+b1
ii  gir1.2-adw-1 1.2.0-1
ii  gir1.2-atk-1.0   2.46.0-4
ii  gir1.2-atspi-2.0 2.46.0-4
ii  gir1.2-freedesktop   1.74.0-2
ii  gir1.2-gcr-3 3.41.1-1+b1
ii  gir1.2-gdesktopenums-3.0 43.0-1
ii  gir1.2-gdkpixbuf-2.0 2.42.10+dfsg-1
ii  gir1.2-gdm-1.0   43.0-1
ii  gir1.2-geoclue-2.0   2.6.0-2
ii  gir1.2-glib-2.0  1.74.0-2
ii  gir1.2-gnomebluetooth-3.0    42.4-1
ii  gir1.2-gnomedesktop-3.0  43-2
ii  gir1.2-graphene-1.0  1.10.8-1
ii  gir1.2-gstreamer-1.0 1.20.4-1
ii  gir1.2-gtk-3.0   3.24.35-1
ii  gir1.2-gtk-4.0   4.8.2+ds-3
ii  gir1.2-gweather-4.0  4.2.0-1
ii  gir1.2-ibus-1.0  1.5.27-4
ii  gir1.2-mutter-11 43.0-2
ii  gir1.2-nm-1.0    1.40.4-1
ii  gir1.2-nma-1.0   1.10.4-2
ii  gir1.2-pango-1.0 1.50.10+ds-1
ii  gir1.2-polkit-1.0    122-1
ii  gir1.2-rsvg-2.0  2.54.5+dfsg-1
ii  gir1.2-soup-3.0  3.2.1-2
ii  gir1.2-upowerglib-1.0    0.99.20-1+b1
ii  gir1.2-webkit2-4.1   2.38.2-1+b1
ii  gnome-backgrounds    43-1
ii  gnome-settings-daemon    43.0-3
ii  gnome-shell-common   43.1-2
ii  gsettings-desktop-schemas    43.0-1
ii  gstreamer1.0-pipewire    0.3.61-1
ii  libatk-bridge2.0-0   2.46.0-4
ii  libatk1.0-0  2.46.0-4
ii  libc6    2.36-5
ii  libcairo2    1.16.0-6
ii  libecal-2.0-2    3.46.1-1+b2
ii  libedataserver-1.2-27    3.46.1-1+b2
ii  libgcr-base-3-1  3.41.1-1+b1
ii  libgdk-pixbuf-2.0-0  2.42.10+dfsg-1
ii  libgirepository-1.0-1    1.74.0-2
ii  libgjs0g 1.74.1-1
ii  libgles2 1.5.0-1
ii  libglib2.0-0 2.74.1-2
ii  libglib2.0-bin   2.74.1-2
ii  libgnome-autoar-0-0  0.4.3-1
ii  libgnome-desktop-3-20    43-2
ii  libgraphene-1.0-0    1.10.8-1
ii  libgtk-3-0   3.24.35-1
ii  libgtk-4-1   4.8.2+ds-3
ii  libical3 3.0.16-1+b1
ii  libjson-glib-1.0-0   1.6.6-1
ii  libmutter-11-0   43.0-2
ii  libnm0   1.40.4-1
ii  libpango-1.0-0   1.50.10+ds-1
ii  libpangocairo-1.0-0  1.50.10+ds-1
ii  libpolkit-agent-1-0  122-1
ii  libpolkit-gobject-1-0    122-1
ii  libpulse-mainloop-glib0  16.1+dfsg1-2+b1
ii  libpulse0    16.1+dfsg1-2+b1
ii  libsecret-1-0

Bug#1008907: backtrace

[Gert van de Kraats]

Reading symbols from /usr/bin/pipewire...
(No debugging symbols found in /usr/bin/pipewire)

warning: Can't open file /memfd:pipewire-memfd (deleted) during 
file-backed mapping note processing

[New LWP 1511]
[New LWP 1515]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/i386-linux-gnu/libthread_db.so.1".
Core was generated by `/usr/bin/pipewire'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0  0xb59e85da in ?? () from 
/usr/lib/i386-linux-gnu/spa-0.2/alsa/libspa-alsa.so

[Current thread is 1 (Thread 0xb7bf9700 (LWP 1511))]
(gdb) bt
#0  0xb59e85da in ?? () from 
/usr/lib/i386-linux-gnu/spa-0.2/alsa/libspa-alsa.so
#1  0xb59f0637 in ?? () from 
/usr/lib/i386-linux-gnu/spa-0.2/alsa/libspa-alsa.so
#2  0xb59d9cf1 in ?? () from 
/usr/lib/i386-linux-gnu/spa-0.2/alsa/libspa-alsa.so
#3  0xb4f3d125 in ?? () from 
/usr/lib/i386-linux-gnu/spa-0.2/audioconvert/libspa-audioconvert.so
#4  0xb4f3f5e8 in ?? () from 
/usr/lib/i386-linux-gnu/spa-0.2/audioconvert/libspa-audioconvert.so
#5  0xb7e69285 in pw_impl_node_for_each_param () from 
/lib/i386-linux-gnu/libpipewire-0.3.so.0

#6  0xb7e69976 in ?? () from /lib/i386-linux-gnu/libpipewire-0.3.so.0
#7  0xb736d9f8 in ?? () from 
/usr/lib/i386-linux-gnu/pipewire-0.3/libpipewire-module-protocol-native.so
#8  0xb7369019 in ?? () from 
/usr/lib/i386-linux-gnu/pipewire-0.3/libpipewire-module-protocol-native.so
#9  0xb7369227 in ?? () from 
/usr/lib/i386-linux-gnu/pipewire-0.3/libpipewire-module-protocol-native.so
#10 0xb77648a5 in ?? () from 
/usr/lib/i386-linux-gnu/spa-0.2/support/libspa-support.so
#11 0xb7766c36 in ?? () from 
/usr/lib/i386-linux-gnu/spa-0.2/support/libspa-support.so
#12 0xb7e5dbaa in pw_main_loop_run () from 
/lib/i386-linux-gnu/libpipewire-0.3.so.0

#13 0x004164b1 in ?? ()
#14 0xb7c1c905 in __libc_start_main (main=0x4161c0, argc=1, 
argv=0xbfa91a04, init=0x4167c0, fini=0x416820,
    rtld_fini=0xb7f0f480 <_dl_fini>, stack_end=0xbfa919fc) at 
../csu/libc-start.c:332

#15 0x00416691 in ?? ()

Bug#1008907: pipewire: Pipewire.service dump at start, status=11/SEGV after upgrade 0.3.49-1

[Gert van de Kraats]

Package: pipewire
Version: 0.3.49-1
Severity: grave
Justification: renders package unusable

Dear Maintainer,

2022-04-03 13:26:47 upgrade pipewire:i386 0.3.48-1 0.3.49-1

No sound and no speaker symbol visible.

Apr 3 14:02:25 debian wireplumber[755]: Failed to set scheduler settings:
Operation not permitted
Apr 3 14:02:27 debian dbus-daemon[763]: [session uid=117 pid=763] 
Successfully

activated service 'org.gtk.vfs.Daemon'
Apr 3 14:02:27 debian systemd[672]: Started Virtual filesystem service.
Apr 3 14:02:27 debian bluetoothd[531]: Player registered: sender=:1.33
path=/media_player0
Apr 3 14:02:27 debian bluetoothd[531]: Endpoint registered: sender=:1.33
path=/MediaEndpoint/A2DPSource/ldac
Apr 3 14:02:27 debian bluetoothd[531]: Endpoint registered: sender=:1.33
path=/MediaEndpoint/A2DPSink/aptx_hd
Apr 3 14:02:27 debian bluetoothd[531]: Endpoint registered: sender=:1.33
path=/MediaEndpoint/A2DPSource/aptx_hd
Apr 3 14:02:27 debian bluetoothd[531]: Endpoint registered: sender=:1.33
path=/MediaEndpoint/A2DPSink/aptx
Apr 3 14:02:27 debian bluetoothd[531]: Endpoint registered: sender=:1.33
path=/MediaEndpoint/A2DPSource/aptx
Apr 3 14:02:27 debian bluetoothd[531]: Endpoint registered: sender=:1.33
path=/MediaEndpoint/A2DPSink/sbc
Apr 3 14:02:27 debian bluetoothd[531]: Endpoint registered: sender=:1.33
path=/MediaEndpoint/A2DPSource/sbc
Apr 3 14:02:27 debian bluetoothd[531]: Endpoint registered: sender=:1.33
path=/MediaEndpoint/A2DPSink/sbc_xq
Apr 3 14:02:27 debian bluetoothd[531]: Endpoint registered: sender=:1.33
path=/MediaEndpoint/A2DPSource/sbc_xq
Apr 3 14:02:27 debian bluetoothd[531]: Endpoint registered: sender=:1.33
path=/MediaEndpoint/A2DPSource/aptx_ll_1
Apr 3 14:02:27 debian bluetoothd[531]: Endpoint registered: sender=:1.33
path=/MediaEndpoint/A2DPSource/aptx_ll_0
Apr 3 14:02:27 debian bluetoothd[531]: Endpoint registered: sender=:1.33
path=/MediaEndpoint/A2DPSource/aptx_ll_duplex_1
Apr 3 14:02:27 debian bluetoothd[531]: Endpoint registered: sender=:1.33
path=/MediaEndpoint/A2DPSource/aptx_ll_duplex_0
Apr 3 14:02:27 debian bluetoothd[531]: Endpoint registered: sender=:1.33
path=/MediaEndpoint/A2DPSource/faststream
Apr 3 14:02:27 debian bluetoothd[531]: Endpoint registered: sender=:1.33
path=/MediaEndpoint/A2DPSource/faststream_duplex
Apr 3 14:02:30 debian rtkit-daemon[785]: Supervising 5 threads of 3 
processes

of 1 users.
Apr 3 14:02:30 debian rtkit-daemon[785]: Successfully made thread 1070 of
process 753 owned by '117' RT at priority 5.
Apr 3 14:02:30 debian rtkit-daemon[785]: Supervising 6 threads of 3 
processes

of 1 users.
Apr 3 14:02:30 debian rtkit-daemon[785]: Supervising 6 threads of 3 
processes

of 1 users.
Apr 3 14:02:30 debian rtkit-daemon[785]: Successfully made thread 1071 of
process 753 owned by '117' RT at priority 5.
Apr 3 14:02:30 debian rtkit-daemon[785]: Supervising 7 threads of 3 
processes

of 1 users.
Apr 3 14:02:31 debian systemd[672]: Started Sound Service.
Apr 3 14:02:32 debian gnome-session[1046]: gnome-session-binary[1046]: GLib-
GIO-CRITICAL: g_bus_get_sync: assertion 'error == NULL || *error == NULL'
failed
Apr 3 14:02:32 debian gnome-session[1046]: gnome-session-binary[1046]: GLib-
GIO-CRITICAL: g_bus_get_sync: assertion 'error == NULL || *error == NULL'
failed
Apr 3 14:02:32 debian gnome-session-binary[1046]: GLib-GIO-CRITICAL:
g_bus_get_sync: assertion 'error == NULL || *error == NULL' failed
Apr 3 14:02:32 debian gnome-session-binary[1046]: GLib-GIO-CRITICAL:
g_bus_get_sync: assertion 'error == NULL || *error == NULL' failed
Apr 3 14:02:35 debian bluetoothd[531]: src/profile.c:record_cb() Unable 
to get

Hands-Free Voice gateway SDP record: Host is down
Apr 3 14:02:38 debian kernel: [ 92.842352] pipewire[752]: segfault at 1 ip
b5aaf5da sp bfdedb30 error 4 in libspa-alsa.so[b5a7d000+7d000]
Apr 3 14:02:38 debian kernel: [ 92.842386] Code: 47 0c 83 c0 08 89 47 0c 8b
47 14 85 c0 74 0b 90 83 00 08 8b 40 08 85 c0 75 f6 89 f3 8b 03 89 44 24 
08 85
c0 0f 84 34 23 00 00 <0f> b6 00 88 44 24 1b 3c 3f 0f 84 87 16 00 00 83 
c3 04 31

d2 89 54
Apr 3 14:02:38 debian bluetoothd[531]: Endpoint unregistered: sender=:1.33
path=/MediaEndpoint/A2DPSource/ldac
Apr 3 14:02:38 debian [755]: 0xf9feb0: leaked proxy 0x10fa2e0 id:4
Apr 3 14:02:38 debian bluetoothd[531]: Endpoint unregistered: sender=:1.33
path=/MediaEndpoint/A2DPSink/aptx_hd
Apr 3 14:02:38 debian [755]:  sync error: core disconnected
Apr 3 14:02:38 debian bluetoothd[531]: Endpoint unregistered: sender=:1.33
path=/MediaEndpoint/A2DPSource/aptx_hd
Apr 3 14:02:38 debian [755]:  core sync error: core
disconnected
Apr 3 14:02:38 debian bluetoothd[531]: Endpoint unregistered: sender=:1.33
path=/MediaEndpoint/A2DPSink/aptx
Apr 3 14:02:38 debian [755]:  sync error: core disconnected
Apr 3 14:02:38 debian bluetoothd[531]: Endpoint unregistered: sender=:1.33
path=/MediaEndpoint/A2DPSource/aptx
Apr 3 14:02:38 debian [755]:  core sync error: core
disconnected
Apr 3 14:02:38 debian bluetoothd[531]: Endpoint unregistered: sender=:1.33

Bug#969395: chromium 83.0.4103.116-3+b1 crash immediately, SEGV_MAPERR

[Gert van de Kraats]

Package: chromium
Version: 83.0.4103.116-3+b1
Severity: grave
Justification: renders package unusable

Dear Maintainer,

Chromium crashes immediately with screen awsnap errorcode 256

Log;
Sep  1 20:37:43 debian dbus-daemon[439]: [system] Activating via systemd:
service name='org.bluez' unit='dbus-org.bluez.service' requested by ':1.156'
(uid=1000 pid=5370 comm="/usr/lib/chromium/chromium 
--show-component-extens")

Sep  1 20:37:43 debian chromium.desktop[5370]:
[5370:5370:0901/203743.006490:ERROR:edid_parser.cc(102)] Too short EDID 
data:

manufacturer id
Sep  1 20:37:43 debian chromium.desktop[5370]:
[5370:5370:0901/203743.006978:ERROR:edid_parser.cc(102)] Too short EDID 
data:

manufacturer id
Sep  1 20:37:43 debian systemd[1]: Condition check resulted in Bluetooth
service being skipped.
Sep  1 20:37:45 debian chromium.desktop[5436]: 
../../sandbox/linux/seccomp-bpf-

helpers/sigsys_handlers.cc:**CRASHING**:seccomp-bpf failure in syscall 0403
Sep  1 20:37:45 debian chromium.desktop[5436]: Received signal 11 
SEGV_MAPERR

0bc01193
Sep  1 20:37:45 debian chromium.desktop[5436]: #0 0x04f1577f
(/usr/lib/chromium/chromium+0x4b1177e)
Sep  1 20:37:45 debian chromium.desktop[5436]: #1 0x04e66a12
(/usr/lib/chromium/chromium+0x4a62a11)
Sep  1 20:37:45 debian chromium.desktop[5436]: #2 0x04f153ee
(/usr/lib/chromium/chromium+0x4b113ed)
Sep  1 20:37:45 debian chromium.desktop[5436]: #3 0xb7ee61e4
([vdso]+0x11e3)
Sep  1 20:37:45 debian chromium.desktop[5436]: #4 0x060eed28
(/usr/lib/chromium/chromium+0x5cead27)
Sep  1 20:37:45 debian chromium.desktop[5436]: #5 0x060f5cf4
(/usr/lib/chromium/chromium+0x5cf1cf3)
Sep  1 20:37:45 debian chromium.desktop[5436]: #6 0x060f5a4a
(/usr/lib/chromium/chromium+0x5cf1a49)
Sep  1 20:37:45 debian chromium.desktop[5436]: #7 0xb7ee61e4
([vdso]+0x11e3)
Sep  1 20:37:45 debian chromium.desktop[5436]: #8 0xb7ee61cd
([vdso]+0x11cc)
Sep  1 20:37:45 debian chromium.desktop[5436]: #9 0xb7ee612a
([vdso]+0x1129)
Sep  1 20:37:45 debian chromium.desktop[5436]: #10 0xb3855f69
(/usr/lib/i386-linux-gnu/libc-2.31.so+0xc3f68)
Sep  1 20:37:45 debian chromium.desktop[5436]:   gs: 0033  fs: 
es: 007b  ds: 007b
Sep  1 20:37:45 debian chromium.desktop[5436]:  edi: 0193 esi: bfbd9b08
ebp: bfbd9ad8 esp: bfbd9ac0
Sep  1 20:37:45 debian chromium.desktop[5436]:  ebx: 09b3cd38 edx: 0007
ecx: 0bc01193 eax: 1000
Sep  1 20:37:45 debian chromium.desktop[5436]:  trp: 000e err: 0006
ip: 060eed28  cs: 0073
Sep  1 20:37:45 debian chromium.desktop[5436]:  efl: 00210206 usp: bfbd9ac0
ss: 007b
Sep  1 20:37:45 debian chromium.desktop[5436]: [end of stack trace]
Sep  1 20:37:45 debian chromium.desktop[5436]: Calling _exit(1). Core 
file will

not be generated.
Sep  1 20:37:45 debian chromium.desktop[5439]: 
../../sandbox/linux/seccomp-bpf-

helpers/sigsys_handlers.cc:**CRASHING**:seccomp-bpf failure in syscall 0403



-- System Information:
Debian Release: bullseye/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: i386 (i686)

Kernel: Linux 5.7.0-3-686-pae (SMP w/2 CPU threads)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US:en

Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages chromium depends on:
ii  chromium-common  83.0.4103.116-3+b1
ii  libasound2   1.2.3.2-1
ii  libatk-bridge2.0-0   2.34.1-3
ii  libatk1.0-0  2.36.0-2
ii  libatomic1   10.2.0-5
ii  libatspi2.0-0    2.36.0-3
ii  libavcodec58 7:4.3.1-2
ii  libavformat58    7:4.3.1-2
ii  libavutil56  7:4.3.1-2
ii  libc6    2.31-3
ii  libcairo2    1.16.0-4
ii  libcups2 2.3.3-2
ii  libdbus-1-3  1.12.20-1
ii  libdrm2  2.4.102-1
ii  libevent-2.1-7   2.1.12-stable-1
ii  libexpat1    2.2.9-1
ii  libflac8 1.3.3-1
ii  libfontconfig1   2.13.1-4.2
ii  libfreetype6 2.10.2+dfsg-3
ii  libgbm1  20.1.5-1
ii  libgcc-s1    10.2.0-5
ii  libgdk-pixbuf2.0-0   2.40.0+dfsg-5
ii  libglib2.0-0 2.64.4-1
ii  libgtk-3-0   3.24.22-1
ii  libharfbuzz0b    2.6.7-1
ii  libicu67 67.1-4
ii  libjpeg62-turbo  1:2.0.5-1.1
ii  libjsoncpp1  1.7.4-3.1
ii  liblcms2-2   2.9-4+b1
ii  libminizip1  1.1-8+b1
ii  libnspr4 2:4.27-1
ii  libnss3  2:3.55-1
ii  libopenjp2-7 2.3.1-1
ii  libopus0 1.3-1+b1
ii  libpango-1.0-0   1.46.1-1
ii  libpangocairo-1.0-0  1.46.1-1
ii  libpng16-16  1.6.37-2
ii  libpulse0    13.0-5
ii  libre2-8 20200801+dfsg-1
ii  libsnappy1v5 1.1.8-1
ii  libstdc++6   10.2.0-5
ii  libvpx6  1.8.2-1
ii  libwebp6 0.6.1-2+b1
ii  libwebpdemux2    0.6.1-2+b1
ii  libwebpmux3  0.6.1-2+b1
ii  libx11-6 2:1.6.10-3
ii  libx11-xcb1  2:1.6.10

Bug#958566: Minor comment

[Gert van de Kraats]

Andreas, thanks for the bug fix. It is working.

But there still is a minor cosmetic bug, not influencing the correct 
working of the package.


The display of an unknown card will never work, because it displays the 
list of unsupported cards.


Besides the lspci-command also detects the wired network connection from 
broadcom.


lspci -n -d 14e4: | grep -o "14e4:[1234567890abcdef]\+"
14e4:1600
14e4:4312

So if the construction worked it would incorrectly display card 1600 as 
unknown.


Although I also prefer the check for an unknown card, I have the 
impression this check cannot be simply made because of the weird card 
naming of Broadcom.

Bug#958566: Improved patch added.

[Gert van de Kraats]

Tags: patch

Improved patch is included, which contains correct indentation.

It also displays  more information about the chosen version of firmware.

#!/bin/sh
set -e

#

make_download_vars()
{
if [ -n "$latest" ]; then
VERSION="6.30.163.46"
BROADCOM_WL="broadcom-wl-${VERSION}"
WL_APSTA="${BROADCOM_WL}.wl_apsta.o"

SHA512SUM="0144894fbbb5e8ebab6c423d9bd0f3249be94f2f468a50b8bf721a3b17f1f6e57467c79e87abc8d136bfc92e701ed046885fead892e9a73efa5217d710311ae9"
else
VERSION="5.100.138"
BROADCOM_WL="broadcom-wl-${VERSION}"
WL_APSTA="${BROADCOM_WL}/linux/wl_apsta.o"

SHA512SUM="02487e76e3eca7fe97ce2ad7dc9c5d39fac82b8d5f7786cce047f9c85e2426f5b7ea085d84c7d4aae43e0fe348d603e3229211bab601726794ef633441d37a8b"
fi

DOWNLOAD="${BROADCOM_WL}.tar.bz2"

URL="https://www.lwfinger.com/b43-firmware/${DOWNLOAD}";

FIRMWARE_INSTALL_DIR="/lib/firmware"

B43="b43"
}

#
# stable sections below, not updated for firmware updates   #
#

. /usr/share/debconf/confmodule

install_firmware ()
{
tmp=$(mktemp -q -d)

cd $tmp

# use apt proxy
APT_PROXIES=$(apt-config shell \
http_proxy Acquire::http::Proxy \
https_proxy Acquire::https::Proxy \
ftp_proxy Acquire::ftp::Proxy \
)

if [ -n "$APT_PROXIES" ]; then
eval export $APT_PROXIES
fi

if ! wget --timeout=60 "${URL}"; then
echo "$0: Some problem occurred during the firmware download. Please 
check your internet connection." 1>&2
exit 1
fi
if ! sha512sum -c /dev/stdin << EOF; then
${SHA512SUM}  ${DOWNLOAD}
EOF
echo "$0: Downloaded firmware did not match known SHA512 checksum, 
aborting." 1>&2
exit 1
fi
if [ "${DOWNLOAD}" != "${WL_APSTA}" ]; then
if ! tar xvjf "${DOWNLOAD}" "${WL_APSTA}"; then
echo "$0: Unpacking firmware file failed, unable to continue 
(is /tmp full?)." 1>&2
exit 1
fi
fi
catalog="${FIRMWARE_INSTALL_DIR}/${B43}/firmware-${B43}-installer.catalog"
if [ -f "${catalog}" ]; then
echo "$0: Deleting old extracted firmware..." 1>&2
xargs -r -0 -a "${catalog}" dpkg-query -S 2>&1 1>/dev/null | sed 
-es',[^/]\+,,' | xargs -r rm --
rm "${catalog}"
fi
mkdir -p "${FIRMWARE_INSTALL_DIR}/${B43}"
retcode=0
b43-fwcutter -w "${FIRMWARE_INSTALL_DIR}" "${WL_APSTA}" | while read line
do  echo "${line}"
file="${line#Extracting }"
if [ "${file}" != "${line}" ]
thenif [ "${retcode}" -ne 0 ]
thenrm "${FIRMWARE_INSTALL_DIR}/${file}"

elif [ -z "${FIRMWARE_INSTALL_DIR}/${file}" ] || \
! printf %s/%s\\000 "${FIRMWARE_INSTALL_DIR}" "${file}" >> 
"${catalog}"
thenecho "$0: Failed during extraction of ${file} from 
${WL_APSTA}" 1>&2
echo "$0: Warning, manual removal/cleaning of 
${FIRMWARE_INSTALL_DIR}/${B43} may be needed!" 1>&2
rm "${FIRMWARE_INSTALL_DIR}/${file}"
retcode=1
fi
fi
done

rm -f "${DOWNLOAD}" "${WL_APSTA}"
rm -rf "${BROADCOM_WL}"

# otherwise can't delete things
cd /

rmdir $tmp || echo "$0: DEBUG: targeted cleaning failed" 1>&2

rm -rf $tmp
[ ${retcode} -eq 0 ] || exit ${retcode}
}

# check environment
if [ "$(stat -c %d/%i /)" != "$(stat -Lc %d/%i /proc/1/root 2>/dev/null)" ];
 then
echo "A chroot environment has been detected."
echo "Remember this firmware needs kernel >= 2.6.25."
unconditional=1
 else 
echo "No chroot environment found. Starting normal installation"
fi
 

if [ -z "$unconditional" ]; then
# check kernel version
if dpkg --compare-versions 2.6.25 gt `uname -r | cut -d- -f1`; then
echo "Kernel too old. This firmware needs >= 2.6.25!."
echo "Aborting!"
exit 0
fi

# install firmware unconditional if the corresponding debconf value is 
true
# this is usefull for live-systems or similar systems that should work 
on
# changing hardware
db_get b43-fwcutter/install-unconditional
if [ "$RET" = "true" ] ; then
unconditional=1
fi
fi

# check chip
pci=`lspci -n -d 14e4: | grep -o "14e4:[1234567890abcdef]\+"` || true

if [ -z "$pci" ]; then
echo "No known supported Broadcom 802.11 chips found."
if [ -z "$unconditional" ]; then
echo "Not installing firmware."
echo
echo "Aborting."
fi
exit 0
fi

if [ -n "$pci" ] ; then
for device in $pci; do
device_id=${device#14e4:}
case $device_id in
4301 | 4325)
legacy=1
;;
4306)
chip=`lspci -n

Bug#959002: Extra info

[Gert van de Kraats]

I do not understand why this problem is marked as fixed at
6.30.223.271-14, because this just is the version I used when I got the
problem.

I also tested with the same laptop at ubuntu 18.04
the broadcom-sta-dkms version 6.30.223.271-8ubuntu0,1 and got the same 
problem there.


At internet the message "wl driver 6.30.223.271 (r587334) failed with 
code 21" is

an old existing problem at devices  BCM4311, BCM4318.
I nowhere see a solution for this problem using broadcom-sta-dkms.

The fail with code 21 is occurring at the call of the
Broadcom-routine wlc_attach at i386/src/wl/sys/wl_linux.c line 608.
I did not see any documentation about the meaning of errorcode 21, so it
is not easy to solve the problem.

At file debian/broadcom-sta.ids some devices like 14e44312 are commented
out, because they are supported by b43.

Is my device not supported and broadcom-sta-dkms:all 6.30.223.271-14
working without problem for other devices?
In that case perhaps the installation Wiki should be updated to show the
exceptions?

Bug#959002: backports version

[Gert van de Kraats]

I used the following versions:

bullseye:
status installed broadcom-sta-dkms:all 6.30.223.271-14

buster-backports:
status installed broadcom-sta-dkms:all 6.30.223.271-14~bpo10+1

This also did not work with same errors.

At the buster-backports version I tried the command dpkg-reconfigure 
broadcom-sta-dkms , that gave same errors.


Also restarts did not help.

I have no idea this has some relation, but at April a new version of 
wireless-regdb is upgraded with lot of changes.


2020-04-18 23:30:05 upgrade wireless-regdb:all 2019.06.03-1 2019.06.03-3.

gert@debian:/lib/firmware$ ls -l regulatory*
lrwxrwxrwx 1 root root   31 Apr 29 23:32 regulatory.db -> 
/etc/alternatives/regulatory.db

-rw-r--r-- 1 root root 4248 Apr 12 20:28 regulatory.db-debian
lrwxrwxrwx 1 root root   35 Apr 29 23:32 regulatory.db.p7s -> 
/etc/alternatives/regulatory.db.p7s

-rw-r--r-- 1 root root 1225 Apr 12 20:28 regulatory.db.p7s-debian
-rw-r--r-- 1 root root 1182 Apr 12 20:28 regulatory.db.p7s-upstream
-rw-r--r-- 1 root root 4248 Apr 12 20:28 regulatory.db-upstream
gert@debian:/lib/firmware$ ls -l /etc/alternatives/regulatory*
lrwxrwxrwx 1 root root 34 Apr 29 23:32 /etc/alternatives/regulatory.db 
-> /lib/firmware/regulatory.db-debian
lrwxrwxrwx 1 root root 38 Apr 29 23:32 
/etc/alternatives/regulatory.db.p7s -> 
/lib/firmware/regulatory.db.p7s-debian

Bug#958566: Suggested patch added

[Gert van de Kraats]

Script postinst of package firmware-b43-installer is modified to load 
the classic firmware for broadcom-cards,


according to  note at 
https://wiki.archlinux.org/index.php/Broadcom_wireless#b43


Logic is added to also load the correct version, in case the firmware is 
unconditionally loaded.


New postinst and diff are attached, I hope.

I did not properly indent the postinst-file!

#!/bin/sh
set -e

#

make_env()
{
if [ -n "$latest" ]; then
VERSION="6.30.163.46"
BROADCOM_WL="broadcom-wl-${VERSION}"
WL_APSTA="${BROADCOM_WL}.wl_apsta.o"

SHA512SUM="0144894fbbb5e8ebab6c423d9bd0f3249be94f2f468a50b8bf721a3b17f1f6e57467c79e87abc8d136bfc92e701ed046885fead892e9a73efa5217d710311ae9"
else
VERSION="5.100.138"
BROADCOM_WL="broadcom-wl-${VERSION}"
WL_APSTA="${BROADCOM_WL}/linux/wl_apsta.o"

SHA512SUM="02487e76e3eca7fe97ce2ad7dc9c5d39fac82b8d5f7786cce047f9c85e2426f5b7ea085d84c7d4aae43e0fe348d603e3229211bab601726794ef633441d37a8b"
fi

DOWNLOAD="${BROADCOM_WL}.tar.bz2"

URL="https://www.lwfinger.com/b43-firmware/${DOWNLOAD}";

FIRMWARE_INSTALL_DIR="/lib/firmware"

B43="b43"
}

#
# stable sections below, not updated for firmware updates   #
#

. /usr/share/debconf/confmodule

install_firmware ()
{
make_env

tmp=$(mktemp -q -d)

cd $tmp

# use apt proxy
APT_PROXIES=$(apt-config shell \
http_proxy Acquire::http::Proxy \
https_proxy Acquire::https::Proxy \
ftp_proxy Acquire::ftp::Proxy \
)

if [ -n "$APT_PROXIES" ]; then
eval export $APT_PROXIES
fi

if ! wget --timeout=60 "${URL}"; then
echo "$0: Some problem occurred during the firmware download. Please 
check your internet connection." 1>&2
exit 1
fi
if ! sha512sum -c /dev/stdin << EOF; then
${SHA512SUM}  ${DOWNLOAD}
EOF
echo "$0: Downloaded firmware did not match known SHA512 checksum, 
aborting." 1>&2
exit 1
fi
if [ "${DOWNLOAD}" != "${WL_APSTA}" ]; then
if ! tar xvjf "${DOWNLOAD}" "${WL_APSTA}"; then
echo "$0: Unpacking firmware file failed, unable to continue 
(is /tmp full?)." 1>&2
exit 1
fi
fi
catalog="${FIRMWARE_INSTALL_DIR}/${B43}/firmware-${B43}-installer.catalog"
if [ -f "${catalog}" ]; then
echo "$0: Deleting old extracted firmware..." 1>&2
xargs -r -0 -a "${catalog}" dpkg-query -S 2>&1 1>/dev/null | sed 
-es',[^/]\+,,' | xargs -r rm --
rm "${catalog}"
fi
mkdir -p "${FIRMWARE_INSTALL_DIR}/${B43}"
retcode=0
b43-fwcutter -w "${FIRMWARE_INSTALL_DIR}" "${WL_APSTA}" | while read line
do  echo "${line}"
file="${line#Extracting }"
if [ "${file}" != "${line}" ]
thenif [ "${retcode}" -ne 0 ]
thenrm "${FIRMWARE_INSTALL_DIR}/${file}"

elif [ -z "${FIRMWARE_INSTALL_DIR}/${file}" ] || \
! printf %s/%s\\000 "${FIRMWARE_INSTALL_DIR}" "${file}" >> 
"${catalog}"
thenecho "$0: Failed during extraction of ${file} from 
${WL_APSTA}" 1>&2
echo "$0: Warning, manual removal/cleaning of 
${FIRMWARE_INSTALL_DIR}/${B43} may be needed!" 1>&2
rm "${FIRMWARE_INSTALL_DIR}/${file}"
retcode=1
fi
fi
done

rm -f "${DOWNLOAD}" "${WL_APSTA}"
rm -rf "${BROADCOM_WL}"

# otherwise can't delete things
cd /

rmdir $tmp || echo "$0: DEBUG: targeted cleaning failed" 1>&2

rm -rf $tmp
[ ${retcode} -eq 0 ] || exit ${retcode}
}

# check environment
if [ "$(stat -c %d/%i /)" != "$(stat -Lc %d/%i /proc/1/root 2>/dev/null)" ];
 then
echo "A chroot environment has been detected."
echo "Remember this firmware needs kernel >= 2.6.25."
unconditional=1
 else 
echo "No chroot environment found. Starting normal installation"
fi
 

if [ -z "$unconditonal" ]; then
# check kernel version
if dpkg --compare-versions 2.6.25 gt `uname -r | cut -d- -f1`; then
echo "Kernel too old. This firmware needs >= 2.6.25!."
echo "Aborting!"
exit 0
fi

# install firmware unconditional if the corresponding debconf value is true
# this is usefull for live-systems or similar systems that should work on
# changing hardware
db_get b43-fwcutter/install-unconditional
if [ "$RET" = "true" ] ; then
unconditional=1
fi
fi

# check chip
pci=`lspci -n -d 14e4: | grep -o "14e4:[1234567890abcdef]\+"` || true

if [ -z "$pci$unconditional" ]; then
echo "No known supported Broadcom 802.11 chips found, not installing 
firmware."
echo
echo "Aborting."
exit 0
fi

if [ -n "$pci" ] ; then
for device in $pci; do
device_id=${device#14e4:}
case $device_id in
4301 | 4325)
legacy=1
;;
4306 | 432[04])
chip=`lspci -n -d $

Bug#958566: Additional info

[Gert van de Kraats]

https://wiki.archlinux.org/index.php/Broadcom_wireless#b43

contains the next note, suggesting to use b43-firmware-classic for 
BCM4311 and other named cards.


Package b43-firmware-classic uses  old firmware version 5.100.138.


*Note:*

 * BCM4306 rev.3, BCM4311, BCM4312 and BCM4318 rev.2 have been noticed
   to experience problems with *b43-firmware*. Use b43-firmware-classic
   ^AUR for
   these cards instead.
 * BCM4331 noticed to have problems with *b43-firmware-classic*. Use
   b43-firmware ^AUR
   for this card instead.

Bug#959002: broadcom-sta-dkms: Wl driver 6.30.223.271 (r587334) failed with code 21

[Gert van de Kraats]

Package: broadcom-sta-dkms
Severity: grave
Justification: renders package unusable

Dear Maintainer,

Because I recently had trouble with Wifi after an upgrade of package
firmware-b43-installer,
I purged this package and tried to install package broadcom-sta-dkms,
according to the recently updated instruction at 
https://wiki.debian.org/wl .

Installation uses the package from bullseye/testing not from some backport.

Loading of the wl-module  fails according to the next log:
Apr 26 12:34:04 debian kernel: [   20.895977] cfg80211: Loading compiled-in
X.509 certificates for regulatory database
Apr 26 12:34:04 debian kernel: [   20.897629] cfg80211: Loaded X.509 cert
'b...@debian.org: 577e021cb980e0e820821ba7b54b4961b8b4fadf'
Apr 26 12:34:04 debian kernel: [   20.905587] cfg80211: Loaded X.509 cert
'romain.per...@gmail.com: 3abbc6ec146e09d1b6016ab9d6cf71dd233f0328'
Apr 26 12:34:04 debian kernel: [   20.907222] cfg80211: Loaded X.509 cert
'sforshee: 00b28ddf47aef9cea7'
Apr 26 12:34:04 debian kernel: [   21.247936] platform regulatory.0: 
firmware:

direct-loading firmware regulatory.db
Apr 26 12:34:04 debian kernel: [   21.347325] platform regulatory.0: 
firmware:

direct-loading firmware regulatory.db.p7s
Apr 26 12:34:04 debian kernel: [   22.420136] wl: loading out-of-tree module
taints kernel.
Apr 26 12:34:04 debian kernel: [   22.420148] wl: module license
'MIXED/Proprietary' taints kernel.
Apr 26 12:34:04 debian kernel: [   22.420149] Disabling lock debugging 
due to

kernel taint
Apr 26 12:34:04 debian kernel: [   22.431299] wl: module verification 
failed:

signature and/or required key missing - tainting kernel
Apr 26 12:34:04 debian kernel: [   22.492802] malloc in abgphy done
Apr 26 12:34:04 debian kernel: [   22.495075] malloc in abgphy done
Apr 26 12:34:04 debian kernel: [   22.495484] wl driver 6.30.223.271 
(r587334)

failed with code 21
Apr 26 12:34:04 debian kernel: [   22.495488] ERROR @wl_cfg80211_detach :
Apr 26 12:34:04 debian kernel: [   22.495489] NULL ndev->ieee80211ptr, 
unable

to deref wl

Card:
0c:00.0 Network controller [0280]: Broadcom Inc. and subsidiaries BCM4311
802.11a/b/g [14e4:4312] (rev 01)
    Subsystem: Dell Wireless 1490 Dual Band WLAN Mini-Card [1028:0007]
    Flags: bus master, fast devsel, latency 0, IRQ 17
    Memory at dfdfc000 (32-bit, non-prefetchable) [size=16K]
    Capabilities: [40] Power Management version 2
    Capabilities: [58] MSI: Enable- Count=1/1 Maskable- 64bit-
    Capabilities: [d0] Express Legacy Endpoint, MSI 00
    Capabilities: [100] Advanced Error Reporting
    Capabilities: [13c] Virtual Channel
    Kernel driver in use: b43-pci-bridge




-- System Information:
Debian Release: bullseye/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: i386 (i686)

Kernel: Linux 5.5.0-2-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 broadcom-sta-dkms depends on:
ii  dkms  2.8.1-5

Versions of packages broadcom-sta-dkms recommends:
ii  wireless-tools  30~pre9-13.1

broadcom-sta-dkms suggests no packages.

Bug#958566: Wrong package name

[Gert van de Kraats]

I think it should be a bug to package firmware-b43-installer.

Bug#958566: Additional info

[Gert van de Kraats]

It is an old problem with version 6.30.163.46.

See e.g. https://bugs.gentoo.org/541080

Bug#958566: b43-fwcutter: Wifi Broadcom at BCM4311 very slow after installing new firmware-b43-installer_019-5_all.deb

[Gert van de Kraats]

Package: b43-fwcutter
Version: 1:019-5
Severity: grave
Justification: renders package unusable

Dear Maintainer,

After the recent upgrade to package firmware-b43-installer_019-5_all wifi
connection was extremely slow causing e.g. timeouts at Firefox.
This package contains firmware version 6.30.163.46
To solve the problem I had to reinstall firmware-b43-installer_019-4_all 
with

firmware version 5.100.138.
Probably the new version is not compatible network controller BCM4311.

0c:00.0 Network controller [0280]: Broadcom Inc. and subsidiaries BCM4311
802.11a/b/g [14e4:4312] (rev 01)
    Subsystem: Dell Wireless 1490 Dual Band WLAN Mini-Card [1028:0007]
    Flags: bus master, fast devsel, latency 0, IRQ 17
    Memory at dfdfc000 (32-bit, non-prefetchable) [size=16K]
    Capabilities: [40] Power Management version 2
    Capabilities: [58] MSI: Enable- Count=1/1 Maskable- 64bit-
    Capabilities: [d0] Express Legacy Endpoint, MSI 00
    Capabilities: [100] Advanced Error Reporting
    Capabilities: [13c] Virtual Channel
    Kernel driver in use: b43-pci-bridge
    Kernel modules: ssb



-- System Information:
Debian Release: bullseye/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: i386 (i686)

Kernel: Linux 5.5.0-1-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 b43-fwcutter depends on:
ii  debconf [debconf-2.0]  1.5.73
ii  libc6  2.30-4

b43-fwcutter recommends no packages.

b43-fwcutter suggests no packages.

-- debconf information:
  b43-fwcutter/install-unconditional: true

Bug#956910: gnome-shell: System hangs with GnomeDesktop:gnome_bg_slide_show_set_property: assertion failed: (GNOME_BG_IS_SLIDE_SHOW (object))

[Gert van de Kraats]

Package: gnome-shell
Version: 3.34.4-1
Severity: critical
Justification: breaks the whole system

Dear Maintainer,

After today's upgrade the system hangs with

GnomeDesktop:ERROR:../libgnome-desktop/gnome-bg-slide-show.c:86:gnome_bg_slide_show_set_property: 
assertion failed: (GNOME_BG_IS_SLIDE_SHOW (object)).


This happens with and without wayland.

The gnome-shell errors about OpenGL and glamor and keymap are normal.

Apr 16 10:43:21 debian gnome-shell[838]: Failed to initialize 
accelerated iGPU/dGPU framebuffer sharing: No matching EGL configs
Apr 16 10:43:21 debian gnome-shell[838]: Failed to find schema: 
org.gnome.settings-daemon.plugins.xsettings
Apr 16 10:43:23 debian gnome-shell[838]: can't load 
/usr/lib/i386-linux-gnu/spa/support/libspa-support.so: 
/usr/lib/i386-linux-gnu/spa/support/libspa-support.so: cannot open 
shared object file: No such file or directory
Apr 16 10:43:24 debian gnome-shell[910]: Require OpenGL version 2.1 or 
later.

Apr 16 10:43:24 debian gnome-shell[910]: Failed to initialize glamor
Apr 16 10:43:24 debian gnome-shell[910]: Failed to initialize glamor, 
falling back to sw
Apr 16 10:43:24 debian snapd[468]: daemon.go:539: gracefully waiting for 
running hooks
Apr 16 10:43:24 debian snapd[468]: daemon.go:541: done waiting for 
running hooks
Apr 16 10:43:24 debian snapd[468]: daemon stop requested to wait for 
socket activation

Apr 16 10:43:24 debian systemd[1]: snapd.service: Succeeded.
Apr 16 10:43:27 debian dbus-daemon[753]: [session uid=117 pid=753] 
Activating via systemd: service name='org.gtk.vfs.Metadata' 
unit='gvfs-metadata.service' requested by ':1.3' (uid=117 pid=749 
comm="/usr/libexec/tracker-extract ")
Apr 16 10:43:27 debian systemd[648]: Starting Virtual filesystem 
metadata service...
Apr 16 10:43:27 debian dbus-daemon[753]: [session uid=117 pid=753] 
Successfully activated service 'org.gtk.vfs.Metadata'
Apr 16 10:43:27 debian systemd[648]: Started Virtual filesystem metadata 
service.
Apr 16 10:43:28 debian gnome-shell[922]: The XKEYBOARD keymap compiler 
(xkbcomp) reports:
Apr 16 10:43:28 debian gnome-shell[922]: > Internal error: Could not 
resolve keysym XF86FullScreen
Apr 16 10:43:28 debian gnome-shell[922]: Errors from xkbcomp are not 
fatal to the X server
Apr 16 10:43:28 debian dbus-daemon[753]: [session uid=117 pid=753] 
Activating via systemd: service name='org.a11y.Bus' 
unit='at-spi-dbus-bus.service' requested by ':1.24' (uid=117 pid=838 
comm="/usr/bin/gnome-shell ")

Apr 16 10:43:28 debian systemd[648]: Starting Accessibility services bus...
Apr 16 10:43:28 debian dbus-daemon[753]: [session uid=117 pid=753] 
Successfully activated service 'org.a11y.Bus'

Apr 16 10:43:28 debian systemd[648]: Started Accessibility services bus.
Apr 16 10:43:34 debian gnome-shell[838]: cannot register existing type 
'GnomeBGSlideShow'
Apr 16 10:43:34 debian gnome-shell[838]: cannot add private field to 
invalid (non-instantiatable) type ''

Apr 16 10:43:34 debian gnome-shell[838]: **
Apr 16 10:43:34 debian gnome-shell[838]: 
GnomeDesktop:ERROR:../libgnome-desktop/gnome-bg-slide-show.c:86:gnome_bg_slide_show_set_property: 
assertion failed: (GNOME_BG_IS_SLIDE_SHOW (object))
Apr 16 10:43:34 debian gnome-shell[838]: Bail out! 
GnomeDesktop:ERROR:../libgnome-desktop/gnome-bg-slide-show.c:86:gnome_bg_slide_show_set_property: 
assertion failed: (GNOME_BG_IS_SLIDE_SHOW (object))
Apr 16 10:43:34 debian gnome-shell[838]: == Stack trace for context 
0x1c70be0 ==
Apr 16 10:43:34 debian gnome-shell[838]: #0    1f66cf8 i 
resource:///org/gnome/shell/ui/background.js:636 (abfb7a10 @ 47)
Apr 16 10:43:34 debian gnome-shell[838]: #1    1f66c80 i 
resource:///org/gnome/shell/ui/background.js:177 (abfb2d30 @ 316)
Apr 16 10:43:34 debian gnome-shell[838]: #2    1f66c18 i 
resource:///org/gnome/shell/ui/background.js:444 (abfb7560 @ 70)
Apr 16 10:43:34 debian gnome-shell[838]: #3    1f66bb0 i 
resource:///org/gnome/shell/ui/background.js:479 (abfb76a0 @ 58)
Apr 16 10:43:34 debian gnome-shell[838]: #4    1f66b48 i 
resource:///org/gnome/shell/ui/background.js:494 (abfb76f0 @ 106)
Apr 16 10:43:34 debian gnome-shell[838]: #5    1f66ac0 i 
resource:///org/gnome/shell/ui/background.js:261 (abfb2f10 @ 501)
Apr 16 10:43:34 debian gnome-shell[838]: #6    1f66a38 i 
resource:///org/gnome/shell/ui/background.js:590 (abfb78d0 @ 426)
Apr 16 10:43:34 debian gnome-shell[838]: #7    1f669c8 i 
resource:///org/gnome/shell/ui/background.js:751 (abfb7ce0 @ 39)
Apr 16 10:43:34 debian gnome-shell[838]: #8    1f66948 i 
resource:///org/gnome/shell/ui/background.js:687 (abfb7b00 @ 269)
Apr 16 10:43:34 debian gnome-shell[838]: #9    1f668c0 i 
resource:///org/gnome/shell/ui/screenShield.js:601 (abbf4880 @ 191)
Apr 16 10:43:34 debian gnome-shell[838]: #10    1f66850 i 
resource:///org/gnome/shell/ui/screenShield.js:619 (abbf48d0 @ 181)
Apr 16 10:43:34 debian gnome-shell[838]: #11    1f667b8 i 
resource:///org/gnome/shell/ui/screenShield.js:467 (abbf45b0 @ 5

Bug#942418: libmutter-5-0: Blank screen after upgrading to bullseye, caused by failing wayland

[Gert van de Kraats]

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]: 
gnome-session-wayland@gnome-login.target: Job 
gnome-session-wayland@gnome-login.target/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