Your message dated Thu, 17 Sep 2026 15:19:00 +0200
with message-id <[email protected]>
and subject line Closing bug: XWayland: Won't startup session with my specific
GNOME configuration
has caused the Debian Bug report #965099,
regarding XWayland: Won't startup session with my specific GNOME configuration
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
965099: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=965099
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: xwayland
Version: 2:1.20.8-2
Severity: normal
Dear Maintainer,
* What led up to the situation?
Updated the system
* What exactly did you do (or not do) that was effective (or
ineffective)?
apt -u dist-upgrade
* What was the outcome of this action?
GNOME does not start any longer with my own GNOME configuration. Using
GNOME on Xorg from the GDM3 login manager works fine, other account with not
much changed GNOME settings do work also
* What outcome did you expect instead?
Running GNOME on Wayland
currently in Debian/testing I want to report the following problem/bug:
I have a good one year old GNOME configuration for my own user account I am
using on this system.
I can't login to XWayland using GNOME (on Wayland) using the GDM3 login
manager. After the password got accepted it loads services like tracker fine,
but then halts and also the mouse pointer gets to an hold.
I can login to two other accounts to this system with GNOME on XWayland fine,
but those have a not much changed GNOME default configuration.
I can also login with that GNOME configuration of my own user account to GNOME
on Xorg fine.
I have no clue why it won't work, I tried to monitor the logs with journalctl
-f but I couldn't find anything suspicious.
Maybe you can try to login to GNOME on XWayland using an user account with used
and changed config files.
Yours sincereley,
Adrian Kieß
-- System Information:
Debian Release: bullseye/sid
APT prefers testing
APT policy: (990, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 5.7.0-1-amd64 (SMP w/4 CPU threads)
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages xwayland depends on:
ii libaudit1 1:2.8.5-3+b1
ii libbsd0 0.10.0-1
ii libc6 2.30-8
ii libdrm2 2.4.102-1
ii libepoxy0 1.5.4-1
ii libgbm1 20.1.2-1
ii libgcrypt20 1.8.5-5
ii libgl1 1.3.1-1
ii libpixman-1-0 0.36.0-1
ii libselinux1 3.0-1+b3
ii libsystemd0 245.6-2
ii libunwind8 1.2.1-9
ii libwayland-client0 1.18.0-1
ii libxau6 1:1.0.8-1+b2
ii libxdmcp6 1:1.1.2-3
ii libxfont2 1:2.0.3-1
ii libxshmfence1 1.3-1
ii xserver-common 2:1.20.8-2
xwayland recommends no packages.
xwayland suggests no packages.
-- no debconf information
--- End Message ---
--- Begin Message ---
Closing bug: XWayland: Won't startup session with my specific GNOME
configuration
--- End Message ---
