Bug#1003091: xwayland: Xwayland uses glamor and shows black screens

[Gert van de Kraats]

I think this issued can be closed.

In fact it is a really sad story.
Problems occurred at i915 classic. Xwayland upstream didnot want to
remove the activation of ES 2.0, which totally was not working.
But they also did not want to approve merge-requests,
which solve the problems.
Then Debian was delivered without the i915 driver, because upstream
decided to stop support for it @#$.  Also gnome-shell was not working,
without an i915-driver (solved).
Finally Debian was delivered with the gallium-i915-driver. But this
driver surprisingly supports GL 2.1. And Xwayland disables glamor
at GL 2.1, because the graphics-performance is to poor.

So currently Xwayland uses the llvmpipe software driver again at
trixie (testing) and I think also at bookworm.

At the moment I use 
https://gitlab.freedesktop.org/xorg/xserver/-/merge_requests/1171 at

Xwayland, which also still is not approved. This patch activates glamor
for GL 2.1, and also uses some (fast) fallbacks.
This also needs Mesa MR
https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/25533 for i915 
gallium, which


gives errorcodes if shader is failing, instead of using a standard 
simple shader,


which  mangles the screen.

Bug#1053804: also at trixie

[Gert van de Kraats]

Same problem at Debian trixie(testing) with filezilla 3.65.0-3 :
2023-10-16T21:24:24.379086+02:00 debian systemd[1809]: Started 
app-gnome-filezilla-4525.scope - Application launched by gnome-shell.
2023-10-16T21:24:26.646156+02:00 debian kernel: [ 5791.686214] traps: 
filezilla[4525] trap invalid opcode ip:b7dc7aa3 sp:bfdb57c0 error:0 in 
libfzclient-private-3.65.0.so[b7d1b000+f9000]

Bug#1053804: code snippet

[Gert van de Kraats]

Unfortunately something went wrong with copying text, so debian/rules
is copied twice.
Also code is mangled a little bit.

This is the correct code snippet:

ifeq ($(DEB_HOST_ARCH_CPU),i386)
# Workaround GCC bug on i386
# Append -msse4.1 to CFLAGS and CXXFLAGS
    sed 's?-Wall?-Wall -msse4.1?' < src/putty/Makefile > 
src/putty/Makefile.tmp

    mv src/putty/Makefile.tmp src/putty/Makefile
endif

Bug#1053804: filezilla: Filezilla aborts with invalid opcode at i386

[Gert van de Kraats]

Package: filezilla
Version: 3.63.0-1+deb12u2
Severity: important
Tags: patch

Dear Maintainer,

Since https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1034195 is solved,
filezilla can be compiled and now is available at Debian Bookworm 12.0 
i386 32

bit.
Unfortunately it aborts with invalid opcode:

2023-10-10T00:17:58.773980+02:00 debian systemd[16997]: Started app-gnome-
filezilla-20364.scope - Application launched by gnome-shell.
2023-10-10T00:17:59.784902+02:00 debian kernel: [53450.659012] traps:
filezilla[20364] trap invalid opcode ip:b7df84c3 sp:bff7eaa0 error:0 in
libfzclient-private-3.63.0.so[b7d1a000+128000]

This is caused by compiling all source with -msse4.1.
This causes at some sources generation of instructions, that cannot be 
executed

by my current hardware and are not skipped by software tests.

In fact the compile problem is solved if only the Makefile at src/putty is
changed.

Therefore the latest change at debian/rules is deleted and replaced by
editing src/putty/Makefile at override_dh_auto_configure.
This is not nice, but at least it works.

The change can be removed again as soon as gcc release 14 is available.
See https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109504
Modified debian/rules :

#!/usr/bin/make -f
# Uncomment this to turn on verbose mode.
#export DH_VERBOSE=1

export DEB_BUILD_MAINT_OPTIONS = hardening=+all

# ifeq ($(DEB_HOST_ARCH_CPU),i386)
# Workaround GCC bug on i386
# export DEB_CFLAGS_MAINT_APPEND = -msse4.1
# export DEB_CXXFLAGS_MAINT_APPEND = -msse4.1
# endif

%:
dh $@

override_dh_autoreconf:
ifeq ($(shell dpkg-vendor --derives-from Ubuntu  echo yes),yes)
patch -p1  debian/patches/11_use-decimal-si-by-default.patch
touch debian/applied
endif
dh_autoreconf

override_dh_auto_clean:
dh_auto_clean
ifeq ($(shell dpkg-vendor --derives-from Ubuntu  echo yes),yes)
@if [ -e ./debian/applied ]; then \
patch -R -p1  debian/patches/11_use-decimal-si-by-
default.patch ; \
rm ./debian/applied ; \
fi
endif

override_dh_dwz:
: Skipping dwz, compression not beneficial on filezilla binary

override_dh_auto_configure:
dh_auto_configure -- --disable-autoupdatecheck --disable-
manualupdatecheck --with-dbus
ifeq ($(DEB_HOST_ARCH_CPU),i386)
sed s?-Wall?-Wall -msse4.1?  src/putty/Makefile 
src/putty/Makefile.tmp
mv src/putty/Makefile.tmp src/putty/Makefile
# Workaround GCC bug on i386
# export DEB_CFLAGS_MAINT_APPEND = -msse4.1
# export DEB_CXXFLAGS_MAINT_APPEND = -msse4.1
endif

override_dh_auto_install:
dh_auto_install
# Remove .la files
find debian/tmp -name *.la -delete

override_dh_installchangelogs:
# Install upstream NEWS file as changelog
dh_installchangelogs -k NEWS

override_dh_link:
# Remove doc from filezilla binary package,
# a symlink to filezilla-common is created by dh_link
rm -rf debian/filezilla/usr/share/doc/
dh_link
gert@debian:/mnt/data/srcfilezilla5/filezilla-3.63.0/debian$ vi rules
gert@debian:/mnt/data/srcfilezilla5/filezilla-3.63.0/debian$ cat rules
#!/usr/bin/make -f
# Uncomment this to turn on verbose mode.
#export DH_VERBOSE=1

export DEB_BUILD_MAINT_OPTIONS = hardening=+all

# ifeq ($(DEB_HOST_ARCH_CPU),i386)
# Workaround GCC bug on i386
# export DEB_CFLAGS_MAINT_APPEND = -msse4.1
# export DEB_CXXFLAGS_MAINT_APPEND = -msse4.1
# endif

%:
dh $@

override_dh_autoreconf:
ifeq ($(shell dpkg-vendor --derives-from Ubuntu  echo yes),yes)
patch -p1  debian/patches/11_use-decimal-si-by-default.patch
touch debian/applied
endif
dh_autoreconf

override_dh_auto_clean:
dh_auto_clean
ifeq ($(shell dpkg-vendor --derives-from Ubuntu  echo yes),yes)
@if [ -e ./debian/applied ]; then \
patch -R -p1  debian/patches/11_use-decimal-si-by-
default.patch ; \
rm ./debian/applied ; \
fi
endif

override_dh_dwz:
: Skipping dwz, compression not beneficial on filezilla binary

override_dh_auto_configure:
dh_auto_configure -- --disable-autoupdatecheck --disable-
manualupdatecheck --with-dbus
ifeq ($(DEB_HOST_ARCH_CPU),i386)
# Workaround GCC bug on i386
# Append -msse4.1 to CFLAGS and CXXFLAGS
sed s?-Wall?-Wall -msse4.1?  src/putty/Makefile 
src/putty/Makefile.tmp
mv src/putty/Makefile.tmp src/putty/Makefile
endif

override_dh_auto_install:
dh_auto_install
# Remove .la files
find debian/tmp -name *.la -delete

override_dh_installchangelogs:
# Install upstream NEWS file as changelog
dh_installchangelogs -k NEWS

override_dh_link:
# Remove doc from filezilla binary package,
# a symlink to filezilla-common is created by dh_link
rm -rf debian/filezilla/usr/share/doc/
dh_link



-- System Information:
Debian Release: 12.2
APT prefers stable-security
APT policy: (500, 'stable-security'), (500, 'stable')
Architecture: i386 (i686)

Kernel: Linux 6.1.0-13-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 filezilla depends on:
ii filezilla-common 3.63.0-1+deb12u2
ii libc6 2.36-9+deb12u3
ii 

Bug#1034195: upstream gcc bug

[Gert van de Kraats]

Phil

I made an upstream issue at GCC:

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109504 .

Perhaps you can add other packages there, that have the same problem?

Bug#1034195: Question

[Gert van de Kraats]

Hi Phil,

Thanks for soon reply.

What do you mean by upstream. I only know a ticket at filezilla, but 
this is closed.


I think this is  a regression bug at gcc 12, but I could not find a 
bugreport upstream or at Debian for gcc.


Greetings,

Gert

Bug#1034195: GCC bug

[Gert van de Kraats]

I saw the problem already is known at
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1020327
and
https://trac.filezilla-project.org/ticket/12777

I downloaded source filezilla-3.63.2.1 from filezilla website and got
the same problem as mentioned at that bug:

gcc -DHAVE_CONFIG_H   -I../../../src/putty -I../../config -DNO_GSSAPI 
-D_FILE_OFFSET_BITS=64  -fpch-preprocess  -g -O2 -Wall -MT 
libfzputtycommon_a-sshsha.o -MD -MP -MF 
.deps/libfzputtycommon_a-sshsha.Tpo -c -o libfzputtycommon_a-sshsha.o 
`test -f 'sshsha.c' || echo '../../../src/putty/'`sshsha.c

In file included from /usr/lib/gcc/i686-linux-gnu/12/include/immintrin.h:98,
 from ../../../src/putty/sshsha.c:347:
/usr/lib/gcc/i686-linux-gnu/12/include/avx512fp16intrin.h:38:9: error: 
‘_Float16’ is not supported on this target


I changed the Makefile at src/putty and added -msse4.1 to CFLAGS and
CXXFLAGS.
After this change I could compile filezilla without a problem.
Installing filezilla gave some problems because the files are not
installed at the right location, but with some symbolic links
filezilla works without a problem.
According to "cat proc/cpuinfo" my cpu supports sse and sse2.

Like Tim Kosse I think this is a gcc-12-bug, not a filezilla-bug.
I do not see any changes in this area at filezilla since previous
release filezilla-3.57.0.
If I compile sshsha.c at that release with gcc-12, I get the same error.
If I compile sshsha.c at both releases with gcc-11, I get no error.

If a pragma GCC target is activated for some source, then the
compiler should not generate an error if the build target is not
supporting this. This makes cross-compilation impossible.

In that case it is the responsibility of the programmer to assure that
this code is only executed if the specified target is available.

I think   pragma GCC target sse4.1 (locally) and -msse4.1 (globally)
should do the same thing.

Bug#1034195: filezilla: Filezilla not available anymore at i386

[Gert van de Kraats]

Source: filezilla
Version: 3.63.0-1
Severity: important

Dear Maintainer,

Recently I automatically upgraded to version 3.63.0-1.
With this version the package and binary filezilla is no longer available at
i386 architecture (32 bits).

This is also visible at the Debian package overview for filezilla.
The common filezilla are delivered. Also libfilezilla34 still is 
delivered at

i386.


-- System Information:
Debian Release: 12.0
APT prefers testing-security
APT policy: (500, 'testing-security'), (500, 'testing')
Architecture: i386 (i686)

Kernel: Linux 6.1.0-7-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

Bug#1032412: Plymouth changed

[Gert van de Kraats]

At plymouth the computation of Window.GetWidth() and Window.GetHeight()
has changed 2 years ago. It now contains the sizes of the
largest screen i.s.o. the smallest screen.
See merge-request
https://gitlab.freedesktop.org/plymouth/plymouth/-/merge_requests/121 :
"use resolution of higher res monitor for window size" .

Bug#1032412: no message at dual screen

[Gert van de Kraats]

I have the same problem at dual screen with sizes 1280 x 1024 and 1280 x 
800.


New debian-logo tries to write the message "resuming from hibernation" 
below borh screens.


This is caused by wrong computation of max height.

In my case it computes 2 * 112 + 1024, which should be only 1024.

.Problem occurs at /usr/share/plymouth/themes/emerald/emerald.script.

Next patch solves the problem for me :diff --git 
a/emerald-theme/plymouth/emerald.script 
b/emerald-theme/plymouth/emerald.script


--- a/desktop-base-12.0.5/emerald-theme/plymouth/emerald.script
+++ b/desktop-base-12.0.5_b/emerald-theme/plymouth/emerald.script
@@ -119,7 +119,8 @@ fun TextYOffset() {
 #Debug("y = " + y);

 text_height = first_line_height * 7.5;
-    min_height = window_max.height - 2 * first_line_height;
+    # subtract Window.GetY() to show info also at smallest of dual srceens
+    min_height = window_max.height - 2 * first_line_height - Window.GetY();
 #Debug("text_height=" + text_height + "; min_height=" + min_height);

 if (y + text_height > min_height)
@@ -131,8 +132,8 @@ fun TextYOffset() {

 #- Screen/window setup 
---

 # Compute screen/image ratio and scale the background accordingly
-window_max.width = Window.GetX() * 2 + Window.GetWidth();
-window_max.height = Window.GetY() * 2 + Window.GetHeight();
+window_max.width = Window.GetWidth();
+window_max.height = Window.GetHeight();
 screen_ratio = window_max.width / window_max.height;
 small_dimension = Math.Min(window_max.width, window_max.height);
 #Debug("Window.GetX():" + Window.GetX() + ", Window.GetY():" + 
Window.GetY());

Bug#1025213: Mutter issue upstream 2602

[Gert van de Kraats]

Sorry, previous message has wrong link.

Mutter issue upstream opened 
athttps://gitlab.gnome.org/GNOME/mutter/-/issues/2602 .

Bug#1025213: Issue upstream

[Gert van de Kraats]

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1025213

Bug#1025213: Mutter mr 2241

[Gert van de Kraats]

Problem is caused by mutter merge-request 2241:
https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/2241 .

Shadow buffer is only used at software rendering.
Damage history is needed at copy from shadow buffer to onscreen,
to synchronize buffers.
I will open an issue upstream.
"

Bug#1025213: Extra info

[Gert van de Kraats]

I also tried mutter 43.2-4 without the Debian patches,
specially the Support-Dynamic-triple-double-buffering.patch .
This did not solve the problem,
The only difference is that during blinking of the cursor
there is switching between 2 different (old) backgrounds i.s.o. 3.

Bug#1025213: mutter

[Gert van de Kraats]

Thank you for adding gallium i915 to mesa 22.3.2-1. Now at least the
default Debian testing release is usable at my laptop.

But the  problem stills persists, if the i915-driver is removed and
kms_swrast is used.

In fact it is a mutter-problem (43.2-4) with shadow buffering.
Problem can be best viewed by opening a Terminal-window at main
Gnome-Shell window.
After some fast flickering the screen is updated every second which is
driven by the blinking of the cursor at the terminal.
Clearly can be seen the current terminal-line is correctly updated with
blinking cursor, but with 3 different old backgrounds.
If the next minute is started the time at the top is switching between 
previous and current time.


With environment variables MUTTER_DEBUG=kms and COGL_DEBUG=clipping this
can be monitored.

The syslog shows messages
gnome-shell[6588]: Device '/dev/dri/card0' prefers shadow buffer
gnome-shell[6588]: Initialized single buffered shadow fb for VGA-1
gnome-shell[6588]: Initialized single buffered shadow fb for LVDS-1

Shadow buffering is only used at software rendering!
The problem disappears if shadow buffering is disabled at
src/backends/native/meta-kms-impl-device.c at
function should_force_shadow_fb:
return FALSE;

Function drmGetCap is called by mutter to check if the device
prefers shadow buffering.

Bug#1025213: Extra info

[Gert van de Kraats]

I installed  all mesa-packages of previous installed version 22.2.0-1.
I also installed previous installed kernel 5.19.11-1.
With these versions the problem still existed.

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#1010357: Solved

[Gert van de Kraats]

This problem is solved upstream at recent Debian version  gtk4 4.6.4+ds-3

Bug#1010357: upstream issue reported

[Gert van de Kraats]

Reported upstream at https://gitlab.gnome.org/GNOME/gtk/-/issues/4894

Bug#1010357: extra info

[Gert van de Kraats]

No problem if I use:
LIBGL_ALWAYS_SOFTWARE=1  MESA_DEBUG=1 gnome-control-center

gnome-control-center also works if I use:
MESA_GLES_VERSION_OVERRIDE=1.0 MESA_DEBUG=1 gnome-control-center

(gnome-control-center:5552): GLib-WARNING **: 10:59:38.934: GError set 
over the top of a previous GError or uninitialized memory.
This indicates a bug in someone's code. You must ensure an error is NULL 
before it's set.

The overwriting error message was: Unable to create a GL context
Gsk-Message: 10:59:38.934: Failed to realize renderer of type 
'GskGLRenderer' for surface 'GdkWaylandToplevel': No EGL configuration 
available


gnome-control-center  works without error if I use:
GSK_RENDERER=cairo MESA_DEBUG=1 gnome-control-center

The program seems to work without problems, but I sometimes get errors:

(gnome-control-center:6102): GLib-GObject-CRITICAL **: 11:43:46.650: 
g_object_unref: assertion 'G_IS_OBJECT (object)' failed


(gnome-control-center:6102): GLib-GObject-CRITICAL **: 11:43:46.651: 
g_object_unref: assertion 'G_IS_OBJECT (object)' failed



Maybe you could reproduce the problem at a more powerful graphics card by:
MESA_GLES_VERSION_OVERRIDE=2.0 MESA_DEBUG=1 gnome-control-center

Bug#1010357: Extra info

[Gert van de Kraats]

I am using a DELL Latitude D620 laptop with Core Duo inside.
It only supports i386.
lscpu
Architecture:    i686
  CPU op-mode(s):    32-bit
  Address sizes: 32 bits physical, 32 bits virtual
  Byte Order:    Little Endian
CPU(s):  2
  On-line CPU(s) list:   0,1
Vendor ID:   GenuineIntel
  BIOS Vendor ID:    Intel
  Model name:    Genuine Intel(R) CPU   T2400  @ 1.83GHz

I am running Debian Testing for a long time without this problem.
I have the impression somehow a switch is made to GTK-4.

Bug#1010357: gnome-shell: Gnome settings by gnome-control-center and other apps abort with SIGSEGV

[Gert van de Kraats]

Package: gnome-shell
Version: 42.0-4
Severity: important

Dear Maintainer,

As can be displayed by Firefox gnome-shell with wayland is using ES 2.0:
WebGL 1 Driver Renderer Intel Open Source Technology Center -- Mesa DRI
Intel(R) 945GM x86/MMX/SSE2
WebGL 1 Driver Version OpenGL ES 2.0 Mesa 21.3.8

With the current gnome-shell version 42.0-4 many/all graphical gnome apps
like gnome-clocks, baobab, gnome-character abort with segmentation failure.
Probably this is caused by using GL_HALF_FLOAT, which is not supported by ES
2.0.
The coredump shows address data is NULL.
A forced abort at _mesa_error shows it is caused by gtk-4.
At gsk/gl/gskglcommandqueue.c exist the lines:
glVertexAttribPointer (2, 4, GL_HALF_FLOAT, GL_FALSE,
and
glVertexAttribPointer (3, 4, GL_HALF_FLOAT, GL_FALSE,

gert@debian:~$ gnome-control-center
Mesa: User error: GL_INVALID_ENUM in glVertexAttribPointer(type =
GL_HALF_FLOAT)
Segmentation fault (core dumped)

Core was generated by `gnome-control-center'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0 0xa623fdf6 in run_vp (ctx=0xa4b6a010, stage=0x1594998) at
../src/mesa/tnl/t_vb_program.c:365
365 COPY_CLEAN_4V(machine->VertAttribs[attr], size, data);
[Current thread is 1 (Thread 0xaf0fc3c0 (LWP 4969))]
(gdb) bt
#0 0xa623fdf6 in run_vp (ctx=0xa4b6a010, stage=0x1594998) at
../src/mesa/tnl/t_vb_program.c:365
#1 0xa6236826 in _tnl_run_pipeline (ctx=0xa4b6a010) at
../src/mesa/tnl/t_pipeline.c:241
#2 0xa617e759 in intelRunPipeline (ctx=0xa4b6a010) at
../src/mesa/drivers/dri/i915/intel_tris.c:1087
#3 0xa6235ad7 in _tnl_draw_prims
(ctx=0xa4b6a010, arrays=0x15957c0, prim=0xbf9261dc, nr_prims=1, ib=0x0,
index_bounds_valid=1 '\001', min_index=, max_index=, num_instances=1, base_instance=0) at ../src/mesa/tnl/t_draw.c:528
#4 0xa633d09a in _mesa_draw_gallium_fallback (ctx=0xa4b6a010, 
info=0xbf926244,

drawid_offset=0, draws=0xbf926238, num_draws=1)
at ../src/mesa/main/draw.c:1016
#5 0xa633beac in _mesa_draw_arrays
(ctx=0xa4b6a010, mode=, start=, count=6,
numInstances=1, baseInstance=0)
at ../src/mesa/main/draw.c:1319
#6 0xb7575bc2 in () at /lib/i386-linux-gnu/libgtk-4.so.1
#7 0xb758f594 in () at /lib/i386-linux-gnu/libgtk-4.so.1
#8 0xb7570fa1 in () at /lib/i386-linux-gnu/libgtk-4.so.1
#9 0xb755952e in gsk_renderer_render () at /lib/i386-linux-gnu/libgtk-4.so.1
#10 0xb73d82dc in () at /lib/i386-linux-gnu/libgtk-4.so.1
#11 0xb73df3e0 in () at /lib/i386-linux-gnu/libgtk-4.so.1
#12 0xb74dae86 in () at /lib/i386-linux-gnu/libgtk-4.so.1
#13 0xb7ce0056 in () at /lib/i386-linux-gnu/libgobject-2.0.so.0
#14 0xb7cf7c01 in g_signal_emit_valist () at /lib/i386-linux-
gnu/libgobject-2.0.so.0
#15 0xb7cf8915 in g_signal_emit () at 
/lib/i386-linux-gnu/libgobject-2.0.so.0

#16 0xb750827e in () at /lib/i386-linux-gnu/libgtk-4.so.1
#17 0xb7ce0056 in () at /lib/i386-linux-gnu/libgobject-2.0.so.0
#18 0xb7cf87bc in g_signal_emit_valist () at /lib/i386-linux-
gnu/libgobject-2.0.so.0
#19 0xb7cf8915 in g_signal_emit () at 
/lib/i386-linux-gnu/libgobject-2.0.so.0

#20 0xb74f7045 in () at /lib/i386-linux-gnu/libgtk-4.so.1
#21 0xb74f7fb9 in () at /lib/i386-linux-gnu/libgtk-4.so.1
#22 0xb7bcc101 in () at /lib/i386-linux-gnu/libglib-2.0.so.0
#23 0xb7bcb4a9 in g_main_context_dispatch () at /lib/i386-linux-
gnu/libglib-2.0.so.0
#24 0xb7bcb879 in () at /lib/i386-linux-gnu/libglib-2.0.so.0
#25 0xb7bcb944 in g_main_context_iteration () at /lib/i386-linux-
gnu/libglib-2.0.so.0
#26 0xb7e0f603 in g_application_run () at 
/lib/i386-linux-gnu/libgio-2.0.so.0

#27 0x00467df9 in main ()
(gdb) f 0
#0 0xa623fdf6 in run_vp (ctx=0xa4b6a010, stage=0x1594998) at
../src/mesa/tnl/t_vb_program.c:365
365 COPY_CLEAN_4V(machine->VertAttribs[attr], size, data);
(gdb) p data
$1 = (const GLfloat *) 0x0

Forced abort at _mesa_error:
Core was generated by `gnome-control-center'.
Program terminated with signal SIGABRT, Aborted.
#0 0xb7f34559 in __kernel_vsyscall ()
[Current thread is 1 (Thread 0xaf0a33c0 (LWP 19873))]
(gdb) bt
#0 0xb7f34559 in __kernel_vsyscall ()
#1 0xb5c7e8f6 in __libc_signal_restore_set (set=0xbfc20a8c) at
../sysdeps/unix/sysv/linux/internal-signals.h:105
#2 __GI_raise (sig=) at ../sysdeps/unix/sysv/linux/raise.c:47
#3 0xb5c6730b in __GI_abort () at abort.c:79
#4 0xa59ed08d in _mesa_error (ctx=, error=,
fmtString=)
at ../src/mesa/main/errors.c:353
#5 0xa5ae81ca in validate_array_format
(ctx=0xa4210010, func=0xa62df2d1 "glVertexAttribPointer",
legalTypesMask=, sizeMin=1, sizeMax=4, size=4, type=5131,
normalized=false, integer=false, doubles=false, relativeOffset=0, 
format=6408,

attrib=, vao=)
at ../src/mesa/main/varray.c:711
#6 0xa5ae86fc in validate_array_and_format
(ctx=ctx@entry=0xa4210010, func=func@entry=0xa62df2d1
"glVertexAttribPointer", vao=, obj=,
legalTypes=, sizeMin=, sizeMax=out>,

size=, type=, stride=,
normalized=, integer=, doubles=0 '\000',
format=6408, ptr=0x10, attrib=17)
at ../src/mesa/main/varray.c:872
#7 0xa5aeb17d in _mesa_VertexAttribPointer (index=2, size=4, type=5131,
normalized=0 '\000', 

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: 

Bug#1003091: Upstream issue opened

[Gert van de Kraats]

I reported the bug upstream for Xwayland:

https://gitlab.freedesktop.org/xorg/xserver/-/issues/1288

It will be fixed.

Bug#1003091: xwayland: Xwayland uses glamor and shows black screens

[Gert van de Kraats]

Package: xwayland
Version: 2:21.1.4-1
Severity: important
Tags: upstream

Dear Maintainer,

I am using graphics:
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

It is intel gen 3 and supports GL1.4 and ES2.0.

At Debian (testing) Bookworm this recently was working without problem,
using ES2.0 hardware driver at Wayland and automatically
galamor was disabled and the llvmpipe software driver at Xwayland
wa selected, because version GL1.4 is too low.
The latest Xwayland package now tries to use ES2.0 with glamor at
Xwayland. This causes blackscreen (Java8, Chromium), xeyes and not working
es2_info end glxinfo.
Errors at startup of user session at syslog:
Jan 2 01:27:47 debian org.gnome.Shell.desktop[9925]: Supported GL version is
not sufficient (required 21, found 14)
Jan 2 01:27:47 debian org.gnome.Shell.desktop[9925]: (EE) glamor0: GL error:
GL_INVALID_VALUE in glTexImage2D(internalFormat=GL_R8)
Jan 2 01:27:47 debian org.gnome.Shell.desktop[9925]: (EE)
Jan 2 01:27:47 debian org.gnome.Shell.desktop[9925]: (EE) Backtrace:
Jan 2 01:27:47 debian dbus-daemon[528]: [system] Activating via systemd:
service name='org.freedesktop.realmd' unit='realmd.service' requested by
':1.492' (uid=117 pid=9895 comm="/usr/bin/gnome-shell ")
Jan 2 01:27:47 debian systemd[1]: Starting Realm and Domain Configuration...
Jan 2 01:27:48 debian org.gnome.Shell.desktop[9925]: (EE) 0: 
/usr/bin/Xwayland

(0x4b9000+0x161813) [0x61a813]
Jan 2 01:27:48 debian org.gnome.Shell.desktop[9925]: (EE) 1: 
/usr/bin/Xwayland

(0x4b9000+0x31596) [0x4ea596]
Jan 2 01:27:48 debian org.gnome.Shell.desktop[9925]: (EE) 2:
/usr/lib/i386-linux-gnu/dri/i915_dri.so (0xb61c4000+0x1f6175) [0xb63ba175]
Jan 2 01:27:48 debian org.gnome.Shell.desktop[9925]: (EE) 3:
/usr/lib/i386-linux-gnu/dri/i915_dri.so (0xb61c4000+0x25d5f1) [0xb64215f1]
Jan 2 01:27:48 debian org.gnome.Shell.desktop[9925]: (EE) 4:
/usr/lib/i386-linux-gnu/dri/i915_dri.so (0xb61c4000+0x31f955) [0xb64e3955]
Jan 2 01:27:48 debian org.gnome.Shell.desktop[9925]: (EE) 5:
/usr/lib/i386-linux-gnu/dri/i915_dri.so (0xb61c4000+0x320076) [0xb64e4076]
Jan 2 01:27:48 debian org.gnome.Shell.desktop[9925]: (EE) 6:
/usr/lib/i386-linux-gnu/dri/i915_dri.so (0xb61c4000+0x3225fa) [0xb64e65fa]
Jan 2 01:27:48 debian org.gnome.Shell.desktop[9925]: (EE) 7: 
/usr/bin/Xwayland

(0x4b9000+0x31758) [0x4ea758]
Jan 2 01:27:48 debian org.gnome.Shell.desktop[9925]: (EE) 8: 
/usr/bin/Xwayland

(0x4b9000+0x32d27) [0x4ebd27]
Jan 2 01:27:48 debian org.gnome.Shell.desktop[9925]: (EE) 9: 
/usr/bin/Xwayland

(0x4b9000+0x2b3cc) [0x4e43cc]
Jan 2 01:27:48 debian org.gnome.Shell.desktop[9925]: (EE) 10:
/usr/bin/Xwayland (0x4b9000+0x25eac) [0x4deeac]
Jan 2 01:27:48 debian org.gnome.Shell.desktop[9925]: (EE) 11:
/usr/bin/Xwayland (0x4b9000+0x8f759) [0x548759]
Jan 2 01:27:48 debian org.gnome.Shell.desktop[9925]: (EE) 12:
/usr/bin/Xwayland (0x4b9000+0x1f584) [0x4d8584]
Jan 2 01:27:48 debian org.gnome.Shell.desktop[9925]: (EE) 13:
/usr/bin/Xwayland (0x4b9000+0x93715) [0x54c715]
Jan 2 01:27:48 debian org.gnome.Shell.desktop[9925]: (EE) 14:
/usr/bin/Xwayland (0x4b9000+0x1ed3b) [0x4d7d3b]
Jan 2 01:27:48 debian org.gnome.Shell.desktop[9925]: (EE) 15: 
/lib/i386-linux-

gnu/libc.so.6 (__libc_start_main+0xe5) [0xb7942905]
Jan 2 01:27:48 debian org.gnome.Shell.desktop[9925]: (EE) 16:
/usr/bin/Xwayland (0x4b9000+0x1ed81) [0x4d7d81]
Jan 2 01:27:48 debian org.gnome.Shell.desktop[9925]: (EE)
Jan 2 01:27:48 debian org.gnome.Shell.desktop[9925]: glamor: Test fbo for
depth 8 incomplete. Falling back to software.
Jan 2 01:27:48 debian org.gnome.Shell.desktop[9925]: glamor: Implementation
returned 0x1908/0x8366 read format/type for depth 15, expected 
0x1908/0x8034.

Falling back to software.
Jan 2 01:27:48 debian org.gnome.Shell.desktop[9925]: glamor: Implementation
returned 0x80e1/0x1401 read format/type for depth 24, expected 
0x1908/0x1401.

Falling back to software.
Jan 2 01:27:48 debian org.gnome.Shell.desktop[9925]: glamor: Implementation
returned 0x80e1/0x1401 read format/type for depth 32, expected 
0x1908/0x1401.

Falling back to software.
Jan 2 01:27:48 debian org.gnome.Shell.desktop[9925]: (EE) glamor0: GL error:
GL_INVALID_OPERATION in glTexImage2D(format = GL_RGBA, type =
GL_UNSIGNED_INT_2_10_10_10_REV, internalformat = GL_RGB10_A2)
Jan 2 01:27:48 debian org.gnome.Shell.desktop[9925]: (EE)
Jan 2 01:27:48 debian 

Bug#1000172: upstream issue fixed

[Gert van de Kraats]

I reported the bug upstream at gnome-shell:

https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/4883

Upstream bug solved with merge-request:

https://gitlab.gnome.org/GNOME/gnome-shell/-/merge_requests/2072

https://gitlab.gnome.org/GNOME/gnome-shell/-/merge_requests/2074

Bug#999686: upstream issue

[Gert van de Kraats]

I reported the bug upstream at pipewire:

https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/1866

Bug#998368: upstream issue

[Gert van de Kraats]

I reported the bug upstream at pulseaudio:

https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/issues/1297

Bug#1000172: gnome-shell: Mouse hangs long when moving over sidepages of Show Applications page

[Gert van de Kraats]

Package: gnome-shell
Version: 41.1-1
Severity: normal
Tags: upstream

Dear Maintainer,

Problem occurs at the Show Applications page.
If the mouse moved over the slideSidePages at the left or the right of
the page with application icons, it hangs about 15 to 30 seconds,
before the arrow and a row of icons of the next page are shown.

This also occurs at the left slideSidePage of the first Applications page,
where
no arrow and icons will be showed,
and at the right slideSidePage of the last Applications page, which also
remains black.
Also switching to next-page with icons is very slow.

Problem is caused by updateFadeForNavigation, which requests fading,
which apparently is too heavy for the graphics card i915, causing 
switching to

software rendering.

Nov 7 00:34:11 debian org.gnome.Shell.desktop[16778]: ENTER FALLBACK 1:
Program
Nov 7 00:34:24 debian org.gnome.Shell.desktop[16778]: LEAVE FALLBACK Program
Nov 7 00:34:24 debian org.gnome.Shell.desktop[16778]: ENTER FALLBACK 1:
Program
Nov 7 00:34:40 debian org.gnome.Shell.desktop[16778]: LEAVE FALLBACK Program

A solution could be to bypass updateFadeForNavigation if animation is 
disabled.
No functionality is lost, mouse-movement and page-switching is very fast 
then.


Normally I use dual monitor above each other with dash at the left side 
(dash-

to-dock)

In that case you always have to pass the slideSide Page to click on an
application-icon.

Suggested, working patch:

--- gnome-shell-js_org/ui/appDisplay.js 2021-11-18 20:49:25.349628824 +0100
+++ gnome-shell-js/ui/appDisplay.js 2021-11-18 21:04:20.145982445 +0100
@@ -349,6 +349,8 @@
}

_updateFadeForNavigation() {
+ if (!St.Settings.get().enable_animations)
+ return;
const fadeMargin = new Clutter.Margin();
const rtl = this.get_text_direction() === Clutter.TextDirection.RTL;
const showingNextPage = this._pagesShown & SidePages.NEXT;


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

Kernel: Linux 5.14.0-2-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 gnome-shell depends on:
ii dconf-gsettings-backend [gsettings-backend] 0.40.0-2
ii evolution-data-server 3.42.1-1
ii gir1.2-accountsservice-1.0 0.6.55-3
ii gir1.2-atk-1.0 2.36.0-2
ii gir1.2-atspi-2.0 2.42.0-2
ii gir1.2-gcr-3 3.40.0-3+b1
ii gir1.2-gdesktopenums-3.0 41.0-2
ii gir1.2-gdkpixbuf-2.0 2.42.6+dfsg-2
ii gir1.2-gdm-1.0 41.0-3
ii gir1.2-geoclue-2.0 2.5.7-3
ii gir1.2-glib-2.0 1.70.0-2
ii gir1.2-gnomebluetooth-1.0 3.34.5-4
ii gir1.2-gnomedesktop-3.0 41.1-1
ii gir1.2-graphene-1.0 1.10.6+dfsg1-2
ii gir1.2-gstreamer-1.0 1.18.5-1
ii gir1.2-gtk-3.0 3.24.30-3
ii gir1.2-gtk-4.0 4.4.1+ds1-2
ii gir1.2-gweather-3.0 40.0-5
ii gir1.2-ibus-1.0 1.5.25-2
ii gir1.2-mutter-9 41.1-1
ii gir1.2-nm-1.0 1.32.12-1
ii gir1.2-nma-1.0 1.8.32-1
ii gir1.2-pango-1.0 1.48.10+ds1-1
ii gir1.2-polkit-1.0 0.105-31
ii gir1.2-rsvg-2.0 2.50.7+dfsg-2
ii gir1.2-soup-2.4 2.74.1-1
ii gir1.2-upowerglib-1.0 0.99.13-1
ii gir1.2-webkit2-4.0 2.34.1-1
ii gjs 1.70.0-3
ii gnome-backgrounds 41.0-1
ii gnome-settings-daemon 41.0-2
ii gnome-shell-common 41.1-1
ii gsettings-desktop-schemas 41.0-2
ii gstreamer1.0-pipewire 0.3.40-1
ii libatk-bridge2.0-0 2.38.0-2
ii libatk1.0-0 2.36.0-2
ii libc6 2.32-4
ii libcairo2 1.16.0-5
ii libecal-2.0-1 3.42.1-1
ii libedataserver-1.2-26 3.42.1-1
ii libgcr-base-3-1 3.40.0-3+b1
ii libgdk-pixbuf-2.0-0 2.42.6+dfsg-2
ii libgirepository-1.0-1 1.70.0-2
ii libgjs0g 1.70.0-3
ii libgles2 1.3.4-2+b1
ii libglib2.0-0 2.70.1-1
ii libglib2.0-bin 2.70.1-1
ii libgnome-autoar-0-0 0.4.0-1
ii libgnome-desktop-3-19 41.1-1
ii libgraphene-1.0-0 1.10.6+dfsg1-2
ii libgtk-3-0 3.24.30-3
ii libgtk-4-1 4.4.1+ds1-2
ii libical3 3.0.11-2
ii libjson-glib-1.0-0 1.6.6-1
ii libmutter-9-0 41.1-1
ii libnm0 1.32.12-1
ii libpango-1.0-0 1.48.10+ds1-1
ii libpangocairo-1.0-0 1.48.10+ds1-1
ii libpolkit-agent-1-0 0.105-31
ii libpolkit-gobject-1-0 0.105-31
ii libpulse-mainloop-glib0 15.0+dfsg1-2
ii libpulse0 15.0+dfsg1-2
ii libsecret-1-0 0.20.4-2
ii libsystemd0 249.5-2
ii libwayland-server0 1.19.0-2+b1
ii libx11-6 2:1.7.2-2+b1
ii libxfixes3 1:5.0.3-2
ii python3 3.9.7-1

Versions of packages gnome-shell recommends:
ii bolt 0.9.1-2
ii chrome-gnome-shell 10.1-5
ii gdm3 41.0-3
ii gkbd-capplet 3.26.1-1+b1
ii gnome-control-center 1:41.1-1
ii gnome-menus 3.36.0-1
ii gnome-user-docs 41.0-1
ii ibus 1.5.25-2
ii iio-sensor-proxy 3.0-2
ii switcheroo-control 2.4-3
ii unzip 6.0-26

Versions of packages gnome-shell suggests:
ii gir1.2-malcontent-0 0.10.1-1
pn gir1.2-telepathyglib-0.12 
pn gir1.2-telepathylogger-0.2 
ii gnome-shell-extension-prefs 41.1-1

Versions of packages gnome-session depends on:
ii gnome-session-bin 40.1.1-3
ii gnome-session-common 40.1.1-3
ii gnome-settings-daemon 41.0-2

Versions of packages gnome-session suggests:
ii 

Bug#999686: added suggested fix

[Gert van de Kraats]

In fact this bug is a problem at wireplumber, not at pipewire-pulse.

Program wireplumber uses config-file

/usr/share/alsa-card-profile/mixer/paths/analog-output-speaker.conf .

Like at pulseaudio the problem can be solved by commenting out thye next 
lines:


; Make sure the internal speakers are not auto-muted once the system has
speakers
[Element Auto-Mute Mode]
enumeration = select

[Option Auto-Mute Mode:Disabled]
name = analog-output-speaker

Bug#999686: pipewire-pulse: Pipewire-pulse disabling auto-mute mode

[Gert van de Kraats]

Package: pipewire-pulse
Version: 0.3.40-1
Severity: normal
Tags: upstream

Recently I installed new updates, which also installed new packages 
pipewire-

pulse and wireplumber.


2021-11-07 22:29:42 remove pipewire-media-session:i386 0.3.38-2 
2021-11-07 22:29:43 upgrade libpipewire-0.3-dev:i386 0.3.38-2 0.3.39-3
2021-11-07 22:29:45 upgrade gstreamer1.0-pipewire:i386 0.3.38-2 0.3.39-3
2021-11-07 22:29:46 upgrade libpipewire-0.3-modules:i386 0.3.38-2 0.3.39-3
2021-11-07 22:29:48 upgrade pipewire:i386 0.3.38-2 0.3.39-3
2021-11-07 22:29:49 upgrade pipewire-bin:i386 0.3.38-2 0.3.39-3
2021-11-07 22:29:51 upgrade libpipewire-0.3-0:i386 0.3.38-2 0.3.39-3
2021-11-07 22:29:53 install libwireplumber-0.4-0:i386  0.4.4-1
2021-11-07 22:29:53 install pipewire-pulse:i386  0.3.39-3
2021-11-07 22:29:54 install wireplumber:i386  0.4.4-1
2021-11-13 20:56:42 upgrade gstreamer1.0-pipewire:i386 0.3.39-3 0.3.39-4
2021-11-13 20:56:43 upgrade pipewire-pulse:i386 0.3.39-3 0.3.39-4
2021-11-13 20:56:44 upgrade pipewire-bin:i386 0.3.39-3 0.3.39-4
2021-11-13 20:56:46 upgrade libpipewire-0.3-dev:i386 0.3.39-3 0.3.39-4
2021-11-13 20:56:47 upgrade libpipewire-0.3-0:i386 0.3.39-3 0.3.39-4
2021-11-13 20:56:49 upgrade pipewire:i386 0.3.39-3 0.3.39-4
2021-11-13 20:56:50 upgrade libpipewire-0.3-modules:i386 0.3.39-3 0.3.39-4
2021-11-13 20:57:35 upgrade libpipewire-0.3-common:all 0.3.39-3 0.3.39-4
2021-11-14 14:18:59 upgrade pipewire-pulse:i386 0.3.39-4 0.3.40-1
2021-11-14 14:19:00 upgrade libpipewire-0.3-dev:i386 0.3.39-4 0.3.40-1
2021-11-14 14:19:02 upgrade gstreamer1.0-pipewire:i386 0.3.39-4 0.3.40-1
2021-11-14 14:19:02 upgrade libpipewire-0.3-modules:i386 0.3.39-4 0.3.40-1
2021-11-14 14:19:04 upgrade pipewire:i386 0.3.39-4 0.3.40-1
2021-11-14 14:19:05 upgrade pipewire-bin:i386 0.3.39-4 0.3.40-1
2021-11-14 14:19:07 upgrade libpipewire-0.3-0:i386 0.3.39-4 0.3.40-1



This caused pipewire-pulse to be used for Sound in stead of pulseaudio.

After these update(s) the internal speaker of the laptop is not going
automatically to mute, if the headphone is plugged in.

If I enable auto-mute, the internal speaker is going to mute, as wished.

As soon as I remove the headphone-plug,
auto-mute is immediately disabled at alsamixer.

If I plug-in the headphone again, the internal speaker is not going to 
mute, as

wished.

In fact this is the same bug as I reported some weeks ago at
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998368 
 concerning 
pulseaudio.
The solution suggested there for pulseaudio, does not work for 
pipewire-pulse.


AutoMute does not auto mute anymore, as it did at previous versions of
pulseaudio. You now always have to manually activate AutoMute again, before
plugging in the headphone which is not very "auto".


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

Kernel: Linux 5.14.0-2-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 pipewire-pulse depends on:
ii init-system-helpers 1.60
ii pipewire 0.3.40-1

pipewire-pulse recommends no packages.

pipewire-pulse suggests no packages.

-- no debconf information

Bug#998368: pulseaudio: Pulseaudio disabling auto-mute mode

[Gert van de Kraats]

Package: pulseaudio
Version: 15.0+dfsg1-2
Severity: normal
Tags: upstream

Dear Maintainer,

Recently I installed new updates, including pulseaudio:

2021-10-19 23:32:51 upgrade pulseaudio:i386 14.2-2 15.0+dfsg1-2
2021-10-19 23:47:37 status installed pulseaudio:i386 15.0+dfsg1-2

After these update(s) the internal speaker of the laptop is not going
automatically to mute,
if the headphone is plugged in.

If I enable auto-mute, the internal speaker is going to mute, as wished.

As soon as I remove the headphone-plug,
auto-mute is immediately disabled  at alsamixer.

If I plug-in the headphone again, the internal speaker is not going to 
mute, as

wished.

File /usr/share/pulseaudio/alsa-mixer/paths/speaker.conf contains the next
extra lines,
if I compare with version 14.2.2 :

; Make sure the internal speakers are not auto-muted once the system has
speakers
[Element Auto-Mute Mode]
enumeration = select

[Option Auto-Mute Mode:Disabled]
name = analog-output-speaker


If I comment out these lines, auto-mute is not disabled anymore by 
pulseaudio,

and Auto-Mute works as designed.

Probably this "fix" is coming from
https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/433/diffs?commit_id=19e34d8d5bb9380ed70607b3f661c26df6d4836c 


.
 It is a strange "fix" . because it completely destroys the 
functionality of

Auto-Mute.

I reported about almost the same problem at Bullseye Testing at February 
2021

with
bug https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=981572 
 .



My laptop is a simple DELL D620, without any additional audiocard.
If the internal speakers can not become  mute independent of the headphone
it cannot be used anymore at video-conference and at a shared office.


-- Package-specific info:
File '/etc/default/pulseaudio' does not exist


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

Kernel: Linux 5.14.0-2-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 pulseaudio depends on:
ii  adduser  3.118
ii  init-system-helpers  1.60
ii  libasound2   1.2.5.1-1
ii  libasound2-plugins   1.2.5-2
ii  libc6    2.32-4
ii  libcap2  1:2.44-1
ii  libdbus-1-3  1.12.20-3
ii  libfftw3-single3 3.3.8-2
ii  libgcc-s1    11.2.0-10
ii  libglib2.0-0 2.70.0-3
ii  libice6  2:1.0.10-1
ii  libltdl7 2.4.6-15
ii  liborc-0.4-0 1:0.4.32-1
ii  libpulse0    15.0+dfsg1-2
ii  libsm6   2:1.2.3-1
ii  libsndfile1  1.0.31-2
ii  libsoxr0 0.1.3-4
ii  libspeexdsp1 1.2~rc1.2-1.1
ii  libstdc++6   11.2.0-10
ii  libsystemd0  249.5-1
ii  libtdb1  1.4.3-1+b1
ii  libudev1 249.5-1
ii  libwebrtc-audio-processing1  0.3-1+b1
ii  libx11-6 2:1.7.2-2+b1
ii  libx11-xcb1  2:1.7.2-2+b1
ii  libxcb1  1.14-3
ii  libxtst6 2:1.2.3-1
ii  lsb-base 11.1.0
ii  pulseaudio-utils 15.0+dfsg1-2

Versions of packages pulseaudio recommends:
ii  dbus-user-session    1.12.20-3
ii  libpam-systemd [logind]  249.5-1
ii  rtkit    0.13-4

Versions of packages pulseaudio suggests:
pn  paprefs  
ii  pavucontrol  5.0-2
pn  pavumeter    
ii  udev 249.5-1

-- no debconf information

--===0103428592==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment; filename="client.conf"

# This file is part of PulseAudio.
#
# PulseAudio is free software; you can redistribute it and/or modify
# it under the terms of the GNU Lesser General Public License as 
published by

# the Free Software Foundation; either version 2 of the License, or
# (at your option) any later version.
#
# PulseAudio is distributed in the hope that it will be useful, but
# WITHOUT ANY WARRANTY; without even the implied warranty of
# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
# General Public License for more details.
#
# You should have received a copy of the GNU Lesser General Public License
# along with PulseAudio; if not, see .

## Configuration file for PulseAudio clients. See pulse-client.conf(5) for
## more information. Default values are commented out.  Use either ; or 
# for

## commenting.

; default-sink =

Bug#983466: Is a mesa-bug

[Gert van de Kraats]

because wayland itself needs 2 fence registers for 2 momitors  i
and X11 only 1.
A trace without using wayland shows the 15th register is used without
giving any problem:

Feb 24 20:10:59 debian systemd[1270]: Started GNOME Shell on X11.

Feb 24 20:11:29 debian gnome-shell[1505]: GK_intelClearWithBlit_fences 0 0
Feb 24 20:11:29 debian gnome-shell[1505]: GK_intelClearWithBlit_fences 1 0
Feb 24 20:11:29 debian gnome-shell[1505]: GK_intelClearWithBlit_fences 2 0
Feb 24 20:11:29 debian gnome-shell[1505]: GK_intelClearWithBlit_fences 3 0
Feb 24 20:11:29 debian gnome-shell[1505]: GK_intelClearWithBlit_fences 4 0
Feb 24 20:11:29 debian gnome-shell[1505]: GK_intelClearWithBlit_fences 5 0
Feb 24 20:11:29 debian gnome-shell[1505]: GK_intelClearWithBlit_fences 6 0
Feb 24 20:11:29 debian gnome-shell[1505]: GK_intelClearWithBlit_fences 7 0
Feb 24 20:11:29 debian gnome-shell[1505]: GK_intelClearWithBlit_fences 8 0
Feb 24 20:11:29 debian gnome-shell[1505]: GK_intelClearWithBlit_fences 9 0
Feb 24 20:11:29 debian gnome-shell[1505]: GK_intelClearWithBlit_fences 10 0
Feb 24 20:11:29 debian gnome-shell[1505]: GK_intelClearWithBlit_fences 11 0
Feb 24 20:11:29 debian gnome-shell[1505]: GK_intelClearWithBlit_fences 12 0
Feb 24 20:11:29 debian gnome-shell[1505]: GK_intelClearWithBlit_fences 13 0
Feb 24 20:11:29 debian gnome-shell[1505]: GK_intelClearWithBlit_fences 14 0
Feb 24 20:11:29 debian gnome-shell[1505]: GK_intelClearWithBlit_fences 15 0
Feb 24 20:11:29 debian gnome-shell[1505]: GK_intelClearWithBlit_fences 1 0
Feb 24 20:11:29 debian gnome-shell[1505]: GK_intelClearWithBlit_fences 2 0
Feb 24 20:11:29 debian gnome-shell[1505]: GK_intelClearWithBlit_fences 3 0
Feb 24 20:11:29 debian gnome-shell[1505]: GK_intelClearWithBlit_fences 4 0
Feb 24 20:11:29 debian gnome-shell[1505]: GK_intelClearWithBlit_fences 5 0
.

So this seems to be  a mesa bug and an exact duplicate
of https://gitlab.freedesktop.org/mesa/mesa/-/issues/790 .

Only the kernel-driver-error has changed and is misleading now.

I add the mesa-2.3.4-patch I currently use, which solves the problem.

Testing for register-overflow is done after updating the batch, If 
overflow occurs


the batch is restored to the situation before the last update, the 
buffer is flushed


and the batch again is updated with the last update.

--- a/src/mesa/drivers/dri/i915/intel_blit.c2021-01-29 19:33:19.919872300 
+0100
+++ b/src/mesa/drivers/dri/i915/intel_blit.c2021-02-27 11:52:41.779536510 
+0100
@@ -93,9 +93,10 @@
GLuint CMD, BR13, pass = 0;
int dst_y2 = dst_y + h;
int dst_x2 = dst_x + w;
-   drm_intel_bo *aper_array[3];
+   drm_intel_bo *aper_array[1];
bool dst_y_tiled = dst_tiling == I915_TILING_Y;
bool src_y_tiled = src_tiling == I915_TILING_Y;
+   int reloc_count;
BATCH_LOCALS;
 
if (dst_tiling != I915_TILING_NONE) {
@@ -109,22 +110,6 @@
if (dst_y_tiled || src_y_tiled)
   return false;
 
-   /* do space check before going any further */
-   do {
-   aper_array[0] = intel->batch.bo;
-   aper_array[1] = dst_buffer;
-   aper_array[2] = src_buffer;
-
-   if (dri_bufmgr_check_aperture_space(aper_array, 3) != 0) {
-   intel_batchbuffer_flush(intel);
-   pass++;
-   } else
-   break;
-   } while (pass < 2);
-
-   if (pass >= 2)
-  return false;
-
intel_batchbuffer_require_space(intel, 8 * 4);
DBG("%s src:buf(%p)/%d+%d %d,%d dst:buf(%p)/%d+%d %d,%d sz:%dx%d\n",
__func__,
@@ -177,15 +162,32 @@
assert(dst_x < dst_x2);
assert(dst_y < dst_y2);
 
-   BEGIN_BATCH(8);
+   do {
+   reloc_count = drm_intel_gem_bo_get_reloc_count(intel->batch.bo);
+   BEGIN_BATCH(8);
+
+   OUT_BATCH(CMD | (8 - 2));
+   OUT_BATCH(BR13 | (uint16_t)dst_pitch);
+   OUT_BATCH((dst_y << 16) | dst_x);
+   OUT_BATCH((dst_y2 << 16) | dst_x2);
+   OUT_RELOC_FENCED(dst_buffer,
+   I915_GEM_DOMAIN_RENDER, I915_GEM_DOMAIN_RENDER,
+   dst_offset);
+   /* do space check before going any further */
+   aper_array[0] = intel->batch.bo;
+   if (dri_bufmgr_check_aperture_space(aper_array, 1) != 0) {
+   drm_intel_gem_bo_clear_relocs(intel->batch.bo, reloc_count);
+   intel_batchbuffer_emit_reset(intel);
+   intel_batchbuffer_flush(intel);
+   pass++;
+   } else
+   break;
+   } while (pass < 2);
+
+   if (pass >= 2)
+   return false;
+
 
-   OUT_BATCH(CMD | (8 - 2));
-   OUT_BATCH(BR13 | (uint16_t)dst_pitch);
-   OUT_BATCH((dst_y << 16) | dst_x);
-   OUT_BATCH((dst_y2 << 16) | dst_x2);
-   OUT_RELOC_FENCED(dst_buffer,
-   I915_GEM_DOMAIN_RENDER, I915_GEM_DOMAIN_RENDER,
-   dst_offset);
OUT_BATCH((src_y << 16) | src_x);
OUT_BATCH((uint16_t)src_pitch);
OUT_RELOC_FENCED(src_buffer,
@@ -335,6 +337,8 @@
GLuint clear_depth_value, clear_depth_mask;
GLint cx, cy, cw, ch;
GLbitfield fail_mask = 0;
+   int reloc_count;
+   bool flushed;

Bug#956437: closed by Debian FTP Masters (reply to Aurélien COUDERC ) (Bug#956426: fixed in desktop-base 11.0.2)

[Gert van de Kraats]

Hello Aurelien,

Unfortunately this solution does not help.

Message is still written through word "Debian" with same color white,

and therefore unreadable.

I tested it at

    text_height = first_line_height * 7.5;
    min_height = Window.GetHeight();
    #Debug("text_height=" + text_height + "; min_height=" + min_height);


    if (y + text_height > min_height)
    y = min_height - text_height;

The script has a lot of code to accommodate screens of different size.

My screens use heigths 1024 and 800.

Plymouth shows at the smallest screen  the center part of the largest 
screen, that just fits.


The smallest screen has a vertical offset Window.GetY() to the top of 
the largest screen.


y is the offset of text to the top of the largest screen.

But min_height is the height of the smallest screen.

It must be compared with the offset to the top of the smallest screen.

This offset is  y - Window.GetY() and should be used at the compare.

The second problem is that if it does not fit, the text will be shifted 
a little bit upwards at the


middle of the large word "Debian" and become unreadalble.

Therefore it should shifetd to the first line that is visible at both 
screens.


Therfore I  think still the proposed fix is needed:


    if (y - Window.GetY() + text_height > min_height)
    # shift to top of smallest window
    y = Window.GetY() + 1;




On 3/2/21 1:06 AM, Debian Bug Tracking System wrote:

This is an automatic notification regarding your Bug report
which was filed against the desktop-base package:

#956437: plymouth: Message is unreadable at initial Debian screen on dual 
monitor

It has been closed by Debian FTP Masters  (reply to 
Aurélien COUDERC).

Their explanation is attached below along with your original report.
If this explanation is unsatisfactory and you have not received a
better one in a separate message then please contact Debian FTP 
Masters  (reply to Aurélien 
COUDERC) by
replying to this email.

Bug#983466: linux-image-5.10.0-3-686-pae: Black screen at dual monitor with warn from i915_gem_ww_ctx_backoff

[Gert van de Kraats]

Package: src:linux
Version: 5.10.13-1
Severity: normal
Tags: upstream

Dear Maintainer,

I am running Debian bullseye with wayland on dual monitor, above each 
other.

I use package dash-to-dock version 69 (newest).

At each dock there are 13 buttons defined to startup applications; each 
monitor

has it's own dock copy.
Black screen appears if button "Show Applications" to show the 
applications is

clicked the third time,
 to show the applications for the second time (the button is a toggle to
show/hide applications).
Gnome-shell is terminating with error "intel_do_flush_locked failed: 
Invalid

argument".

Problem started probably at 29-01-2021 with updates to Linux debian
5.10.0-2-686-pae, and gnome-shell/mutter to i386 3.38.3-1.
I reported a bug on dash-to-dock at https://github.com/micheleg/dash-to-
dock/issues/1383,
because there were some new errors at syslog, which only were present if 
dash-

to-dock was used.
Also the error-text "Invalid argument" suggests there is some 
application error

at the call of "intel_do_flush_locked".
Below is the syslog of the problem:

Feb 19 00:47:56 debian gnome-shell[8067]: intel_do_flush_locked failed: 
Invalid

argument
Feb 19 00:47:56 debian kernel: [22326.421460] [ cut here
]
Feb 19 00:47:56 debian kernel: [22326.421468] WARN_ON(!ww->contended)
Feb 19 00:47:56 debian kernel: [22326.421655] WARNING: CPU: 0 PID: 8067 at
drivers/gpu/drm/i915/i915_gem.c:1359 i915_gem_ww_ctx_backoff+0xaf/0xc0 
[i915]

Feb 19 00:47:56 debian kernel: [22326.421660] Modules linked in: ctr
aes_generic libaes crypto_simd cryptd ccm squashfs loop uinput binfmt_misc
snd_hda_codec_hdmi snd_hda_codec_idt snd_hda_codec_generic snd_hda_intel
snd_intel_dspcfg b43 soundwire_intel cordic soundwire_generic_allocation 
bcma

snd_soc_core dell_rbtn mac80211 snd_compress dell_laptop cfg80211
soundwire_cadence ledtrig_audio snd_hda_codec rfkill coretemp snd_hda_core
libarc4 soundwire_bus kvm_intel dell_smbios snd_hwdep kvm 
dell_wmi_descriptor

snd_pcm wmi dcdbas irqbypass iTCO_wdt dell_smm_hwmon snd_timer joydev
intel_pmc_bxt snd serio_raw iTCO_vendor_support pcspkr yenta_socket 
soundcore
pcmcia_rsrc watchdog sg evdev ac rng_core acpi_cpufreq videodev mc 
parport_pc
ppdev lp parport fuse configfs ip_tables x_tables autofs4 ext4 crc16 
mbcache

jbd2 crc32c_generic hid_generic usbhid hid sd_mod sr_mod t10_pi crc_t10dif
cdrom crct10dif_generic crct10dif_common ata_generic i915 i2c_algo_bit ssb
ata_piix mmc_core uhci_hcd drm_kms_helper libata psmouse scsi_mod
Feb 19 00:47:56 debian kernel: [22326.421879]  i2c_i801 i2c_smbus ehci_pci
pcmcia lpc_ich ehci_hcd usbcore tg3 libphy cec ptp usb_common pps_core drm
pcmcia_core button battery video
Feb 19 00:47:56 debian kernel: [22326.421929] CPU: 0 PID: 8067 Comm: gnome-
shell Not tainted 5.10.0-3-686-pae #1 Debian 5.10.13-1
Feb 19 00:47:56 debian kernel: [22326.421933] Hardware name: Dell Inc. 
Latitude

D620   /0TD761, BIOS A02 04/11/2006
Feb 19 00:47:56 debian kernel: [22326.422025] EIP:
i915_gem_ww_ctx_backoff+0xaf/0xc0 [i915]
Feb 19 00:47:56 debian kernel: [22326.422033] Code: 00 00 00 8b 43 1c 89 
da 8b
80 98 00 00 00 e8 28 41 86 e0 85 c0 74 9a eb d5 66 90 68 30 88 09 f8 68 
2d 88
09 f8 e8 60 f0 82 e0 <0f> 0b 58 5a 8d 65 f4 b8 ea ff ff ff 5b 5e 5f 5d 
c3 3e 8d

74 26 00
Feb 19 00:47:56 debian kernel: [22326.422038] EAX: 0017 EBX: 
 ECX:

f6fc2180 EDX: ffd8
Feb 19 00:47:56 debian kernel: [22326.422042] ESI:  EDI: 
f4827cd0 EBP:

f4827c74 ESP: f4827c58
Feb 19 00:47:56 debian kernel: [22326.422048] DS: 007b ES: 007b FS: 00d8 
GS:

00e0 SS: 0068 EFLAGS: 00010296
Feb 19 00:47:56 debian kernel: [22326.422053] CR0: 80050033 CR2: 
534d9e18 CR3:

2ce1a000 CR4: 06f0
Feb 19 00:47:56 debian kernel: [22326.422056] Call Trace:
Feb 19 00:47:56 debian kernel: [22326.422151]
i915_gem_do_execbuffer+0x10b9/0x1e10 [i915]
Feb 19 00:47:56 debian kernel: [22326.422163]  ?
dma_fence_signal_locked+0x40/0xd0
Feb 19 00:47:56 debian kernel: [22326.422263]
i915_gem_execbuffer2_ioctl+0xcb/0x1e0 [i915]
Feb 19 00:47:56 debian kernel: [22326.422352]  ?
i915_gem_execbuffer_ioctl+0x2d0/0x2d0 [i915]
Feb 19 00:47:56 debian kernel: [22326.422376] drm_ioctl_kernel+0x99/0xe0 
[drm]

Feb 19 00:47:56 debian kernel: [22326.422463]  ?
i915_gem_execbuffer_ioctl+0x2d0/0x2d0 [i915]
Feb 19 00:47:56 debian kernel: [22326.422486] drm_ioctl+0x21b/0x390 [drm]
Feb 19 00:47:56 debian kernel: [22326.422572]  ?
i915_gem_execbuffer_ioctl+0x2d0/0x2d0 [i915]
Feb 19 00:47:56 debian kernel: [22326.422587]  ? 
tomoyo_path_chmod+0x20/0x20
Feb 19 00:47:56 debian kernel: [22326.422592]  ? 
tomoyo_file_ioctl+0x17/0x20
Feb 19 00:47:56 debian kernel: [22326.422599]  ? 
security_file_ioctl+0x30/0x50

Feb 19 00:47:56 debian kernel: [22326.422621]  ? drm_ioctl_kernel+0xe0/0xe0
[drm]
Feb 19 00:47:56 debian kernel: [22326.422629] __ia32_sys_ioctl+0x145/0x760
Feb 19 00:47:56 debian kernel: [22326.422638]  ? 
tick_program_event+0x41/0xa0
Feb 19 00:47:56 

Bug#981572: Problem disappeared.

[Gert van de Kraats]

After recent Debian updates the problem does not exist anymore.

So I think the bug can be closed.

Gert

Bug#981572: pulseaudio: Pulseaudio disabling auto-mute mode

[Gert van de Kraats]

Package: pulseaudio
Version: 14.2-1
Severity: normal

Dear Maintainer,

Recently I installed new updates, including pulseaudio:

2021-01-29 15:55:19 upgrade pulseaudio:i386 14.0-2 14.1-1
2021-01-29 16:08:32 status installed pulseaudio:i386 14.1-1

After these update(s) the internal speaker of the laptop is not going
automatically to mute,
if the headphone is plugged in.
Also the text "headphones" under the speaker symbol ( when changing 
volume with

keyboard button), does not disappear when unplugging the headphone.

If I look at alsamixer I can see the auto-mute is disabled.
If I enable auto-mute, the internal speaker is going to mute, as wished.

As soon as I remove the headphone-plug,
auto-mute is immediately disabled again at alsamixer.

The same problem is described at
https://bbs.archlinux.org/viewtopic.php?id=253729 .
Auto-mute remains enabled if i use the suggested workaround
by commenting at etc/pulse/default.pa the cal  "load-module 
module-udev-detect"

and uncommenting the previous static loads, but this causes a lot of errors,
so it is not a workable solution.

My laptop is a simple DELL D620, without any additional audiocard.
If the internal speakers can not become  mute independent of the headphone
it cannot be used anymore at video-conference and at a shared office.

As workaround I now have to use the command:
amixer -c 0 sset "Auto-Mute Mode" Enabled

Problem is not solved by installing pulseaudio 14.2-1 from sid.

pacmd list-sinks
1 sink(s) available.
  * index: 0
    name: 
    driver: 
    flags: HARDWARE HW_MUTE_CTRL HW_VOLUME_CTRL DECIBEL_VOLUME LATENCY
DYNAMIC_LATENCY
    state: RUNNING
    suspend cause: (none)
    priority: 9039
    volume: front-left: 24762 /  38% / -25.36 dB, front-right: 24762 /
38% / -25.36 dB
    balance 0.00
    base volume: 65536 / 100% / 0.00 dB
    volume steps: 65537
    muted: no
    current latency: 20.34 ms
    max request: 4 KiB
    max rewind: 4 KiB
    monitor source: 0
    sample spec: s16le 2ch 44100Hz
    channel map: front-left,front-right
 Stereo
    used by: 2
    linked by: 2
    configured latency: 26.00 ms; range is 26.00 .. 2000.00 ms
    card: 0 
    module: 6
    properties:
    alsa.resolution_bits = "16"
    device.api = "alsa"
    device.class = "sound"
    alsa.class = "generic"
    alsa.subclass = "generic-mix"
    alsa.name = "STAC9200 Analog"
    alsa.id = "STAC9200 Analog"
    alsa.subdevice = "0"
    alsa.subdevice_name = "subdevice #0"
    alsa.device = "0"
    alsa.card = "0"
    alsa.card_name = "HDA Intel"
    alsa.long_card_name = "HDA Intel at 0xdfebc000 irq 27"
    alsa.driver_name = "snd_hda_intel"
    device.bus_path = "pci-:00:1b.0"
    sysfs.path = "/devices/pci:00/:00:1b.0/sound/card0"
    device.bus = "pci"
    device.vendor.id = "8086"
    device.vendor.name = "Intel Corporation"
    device.product.id = "27d8"
    device.product.name = "NM10/ICH7 Family High Definition 
Audio

Controller"
    device.form_factor = "internal"
    device.string = "front:0"
    device.buffering.buffer_size = "352800"
    device.buffering.fragment_size = "176400"
    device.access_mode = "mmap+timer"
    device.profile.name = "analog-stereo"
    device.profile.description = "Analog Stereo"
    device.description = "Built-in Audio Analog Stereo"
    module-udev-detect.discovered = "1"
    device.icon_name = "audio-card-pci"
    ports:
    analog-output-speaker: Speakers (priority 1, 
latency offset

0 usec, available: no)
    properties:
    device.icon_name = "audio-speakers"
    analog-output-headphones: Headphones (priority 9900, 
latency

offset 0 usec, available: yes)
    properties:
    device.icon_name = "audio-headphones"
    active port: 



-- Package-specific info:
File '/etc/default/pulseaudio' does not exist


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

Kernel: Linux 5.10.0-2-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 pulseaudio depends on:
ii  adduser  3.118
ii  init-system-helpers  1.60
ii  libasound2   1.2.4-1.1
ii  libasound2-plugins   1.2.2-2
ii 

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  

Bug#963121: Additional analysis and suggested bugfix

[Gert van de Kraats]

Problem also occurs at systemd version 245.6-2 .
Indeed I am using GNOME where the login session is managed
by systemd --user.
The problem is not concerning an ordinary user service, which is killed
by SIGKILL after 90 seconds. There is no SIGKILL-message!!
As described at the initial bug-text a restart of the user dbus may 
cause a hang at state

AUTHENTICATING during shutdown. At the log you can see
AUTHENTICATING starts at 18:10:02 and ends at 18:11:32, 90 seconds
later. State RUNNING is never reached.

Jun 15 18:10:02 debian systemd[1360]: Bus bus-api-user: changing state 
OPENING → AUTHENTICATING

Jun 15 18:11:32 debian systemd[1360]: Bus bus-api-user: changing state
AUTHENTICATING → CLOSED

In that hanging situation, as soon as the user systemd gets a SIGTERM 
from pid 1 (systemd) it will

call sd_bus_flush at libsystemd/sd-bus/sd-bus.c.
This will call bus_ensure_running, that repeats calling sd_bus_process,
that finally repeatingly calls bus_socket_process_authenticating.
This routine will cause a timeout after 90 seconds, the timeout-value is
hard coded by DEFAULT_TIMEOUT_USEC at basic/def.h .

A simple and tested patch at sd_bus_flush at libsystemd/sd-bus/sd-bus.c is
next code just before the call to bus_ensure_running:

    if ((bus->state == BUS_AUTHENTICATING) && (bus->is_user))
    return -ETIMEDOUT;

It assumes state BUS_AUTHENTICATING is not normal for an user dbus at a 
call to sd_flush.


I think this is an upstream bug!

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: 959002

[Gert van de Kraats]

Thanks for your quick reply.
So my only solution is using b43. I recently got severe performance 
problems with this,
making wifi unusable. This happened after automatically upgrading to 
package

version firmware-b43-installer_019-5 .
I reported this bug with proposed fix at
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=958566

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 @ 

Bug#956426: plymouth: Message is unreadable at initial Debian screen on dual monitor

[Gert van de Kraats]

Package: plymouth
Version: 0.9.4-2
Severity: normal

Dear Maintainer,

Default plymouth theme with name "futureprototype" is used.
I am using 2 different monitors with size 1280 x 1024 and 1280 x 800.
Message like "resuming from hibernation" is written in the middle of the 
text

"Debian" with the same color (white)
and therefore the message is unreadable. Same problem with 
progress-percentage

during a software-upgrade.

Problem is at 
/usr/share/plymouth/themes/futureprototype/futureprototype.script

at routine TextYOffset.
This routine checks if the message, including some reserved lines, fits 
at the

screen.
If not, then the message is shifted upwards until it fits.
Coding:
    if (y + text_height > min_height)
    y = min_height - text_height;

This is wrong, because y is the vertical offset of the message at the 
largest

screen
 and min_height is the height of the smallest screen.
This causes a shift of the text, although it fits at the smallest screen.
Also the shift is not correct, because it computes the vertical offset y
from the top of the smallest screen in stead of the largest screen.
Corrected code:
    if (y - Window.GetY() + text_height > min_height)
    # shift to top of smallest window
    y = Window.GetY() + 1;

The message is shifted now to the first line that is visble on both screens,
to avoid overlapping the "Debian"-text.

With the corrected test the message is not shifted anymore at the used
monitors.

This wrong code is also present at some other older plymouth scripts and 
also

at ubuntu,
but does not harm there.
~



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

Kernel: Linux 5.4.0-4-686-pae (SMP w/2 CPU cores)
Kernel taint flags: TAINT_DIE
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 plymouth depends on:
ii  init-system-helpers  1.57
ii  initramfs-tools  0.136
ii  libc6    2.30-4
ii  libdrm2  2.4.100-4
ii  libplymouth4 0.9.4-2
ii  lsb-base 11.1.0
ii  systemd  244.3-1
ii  udev 244.3-1

plymouth recommends no packages.

Versions of packages plymouth suggests:
ii  desktop-base 10.0.3
pn  plymouth-themes  

-- Configuration Files:
/etc/plymouth/plymouthd.conf changed:
[Daemon]
Theme=futureprototype


-- no debconf information

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