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ß

Unless there's specific evidence pointing to Xwayland, e.g. in the output of

 journalctl -b0 --user-unit=gnome-shell-wayland.service

this is more likely an issue in a GNOME component, e.g. libmutter-6-0 or
gnome-shell.

Hello Michel,

thank you for your quick reply.

Here is the output of your jounalctl command:

root@g6 /client/libvirt/images
 # journalctl -b0 --user-unit=gnome-shell-wayland.service
-- Logs begin at Mon 2020-05-25 11:58:36 CEST, end at Thu 2020-07-16
11:46:00 CEST. --
-- No entries --

It is empty.

I guess I'd then wait for a new gnome-shell or libmutter entering
Debian/testing.

Maybe you can forward the issue to the maintainers of the above
packages.

Thank you very much for your help.

With many greetings,

Adrian Kieß
-- 
With many greetings from Leipzig, Germany.
Adrian Immanuel Kieß

Gothaer Straße 34
D-04155 Leipzig

📪 — < adrian@kiess.onl >


echo "g6.lan.dac uptime: " && /usr/bin/uptime

Dear Michel,

I actually found out why XWayland won't start with my specific
configuration.

I have keychain in my .zprofile and I am using the Z-shell.

Keychain was configured in the way to ask for the SSH password
resulting in a command input prompt waiting when the Z-shell for the
user gets executed.

The command causing the trouble was:

keychain --ignore-missing --nocolor --nogui --quiet --agents ssh id_rsa

I changed it, by adding --noask, to:

keychain --noask --ignore-missing --nocolor --nogui --quiet --agents
ssh id_rsa

Now Xwayland with gnome-session is loading up fine again!

Thank you very much for your help.

Yours sincerely,

Adrian

В Чт, 16/07/2020 в 11:42 +0200, Michel Dänzer пишет:
-- 
With many greetings from Leipzig, Germany.
Adrian Immanuel Kieß

Gothaer Straße 34
D-04155 Leipzig

📪 — < adrian@kiess.onl >


echo "g6.lan.dac uptime: " && /usr/bin/uptime

Hello,

I had exactly the same symptomps, not being able to login, with black screen
and pointer frozen, only with a specific user account (while the other one on
the same machine was working fine).

In my case, I tracked down the issue to an XDG autostart entry launching Franz
(a multi-provider IM client). Once disabled the autostart entry I've been able
to log in again. Manually launching Franz works fine.

I could not find anything useful in logs, beside some "Cannot connect to
XWayland" message. Maybe it could be some race condition.

I hope this additional report can help somehow. Regards
--
Alessio Gaeta