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

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

Bug#1053804: also at trixie

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

Bug#1053804: code snippet

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

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

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

Bug#1034195: upstream gcc bug

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

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

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

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

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

Bug#1032412: Plymouth changed

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

Bug#1032412: no message at dual screen

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.

Bug#1025213: Mutter issue upstream 2602

Sorry, previous message has wrong link. Mutter issue upstream opened athttps://gitlab.gnome.org/GNOME/mutter/-/issues/2602 .

Bug#1025213: Issue upstream

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

Bug#1025213: Mutter mr 2241

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

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

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

Bug#1025213: Extra info

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

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

Bug#1025213: i915g

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

Bug#1025213: Extra info

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

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

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

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

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.

Bug#1010357: Solved

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

Bug#1010357: upstream issue reported

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

Bug#1010357: extra info

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

Bug#1010357: Extra info

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)

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

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

Bug#1008907: backtrace

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

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

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

Bug#1003091: Upstream issue opened

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

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

Bug#1000172: upstream issue fixed

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

I reported the bug upstream at pipewire: https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/1866

Bug#998368: upstream issue

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

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

Bug#999686: added suggested fix

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

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

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

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

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

Bug#983466: Is a mesa-bug

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

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

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 +

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

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

Bug#981572: Problem disappeared.

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

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

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

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'

Bug#963121: Additional analysis and suggested bugfix

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

Bug#958566: Minor comment

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

Bug#958566: Improved patch added.

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

Bug#959002: 959002

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

Bug#959002: Extra info

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

Bug#959002: backports version

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

Bug#958566: Suggested patch added

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.

Bug#958566: Additional info

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

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

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

Bug#958566: Wrong package name

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

Bug#958566: Additional info

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

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

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

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:

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

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

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

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