Your message dated Wed, 17 Feb 2021 14:22:29 +0100
with message-id <20210217132229.irzeg2iz5n4sk...@fatal.se>
and subject line Re: gdm3: Gdm3 comes to invoke gdm-x-session at the
beginning of the user session
has caused the Debian Bug report #972852,
regarding gdm3: Gdm3 comes to invoke gdm-x-session at the beginning of the
user session
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 ow...@bugs.debian.org
immediately.)
--
972852: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=972852
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gdm3
Version: 3.38.1-2
Severity: grave
Dear Maintainer,
After I upgraded my Debian box using the command of "apt upgrade" on
17th Oct 2020, I always get an "Oops! A problem occurred!" screen after
login.
According to system logs, I seem gdm3 come to invoke gdm-x-session
always at the beginning of the user session, even though gdm3 is
running in Wayland on the login screen. Therefore gnome-shell of the
user session seems to fail.
Does anyone fix this problem?
Thanks,
Takahide Nojima
-- System Information:
Debian Release: bullseye/sid
APT prefers unstable-debug
APT policy: (500, 'unstable-debug'), (500, 'unstable'), (500,
'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 5.9.0-1-amd64 (SMP w/4 CPU threads)
Locale: LANG=ja_JP.UTF-8, LC_CTYPE=ja_JP.UTF-8 (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 gdm3 depends on:
ii accountsservice 0.6.55-3
ii adduser 3.118
ii dbus 1.12.20-1
ii dconf-cli 0.38.0-1
ii dconf-gsettings-backend 0.38.0-1
ii debconf [debconf-2.0] 1.5.74
ii gir1.2-gdm-1.0 3.38.1-2
ii gnome-session-bin 3.38.0-2
ii gnome-session-common 3.38.0-2
ii gnome-settings-daemon 3.38.0-2
ii gnome-shell 3.38.1-1
ii gnome-terminal [x-terminal-emulator] 3.38.0-1
ii gsettings-desktop-schemas 3.38.0-2
ii libaccountsservice0 0.6.55-3
ii libaudit1 1:2.8.5-3.1
ii libc6 2.31-4
ii libcanberra-gtk3-0 0.30-7
ii libcanberra0 0.30-7
ii libgdk-pixbuf2.0-0 2.40.0+dfsg-5
ii libgdm1 3.38.1-2
ii libglib2.0-0 2.66.1-2
ii libglib2.0-bin 2.66.1-2
ii libgtk-3-0 3.24.23-2
ii libkeyutils1 1.6.1-2
ii libpam-modules 1.3.1-5
ii libpam-runtime 1.3.1-5
ii libpam-systemd 246.6-2
ii libpam0g 1.3.1-5
ii librsvg2-common 2.50.1+dfsg-1
ii libselinux1 3.1-2+b1
ii libsystemd0 246.6-2
ii libx11-6 2:1.6.12-1
ii libxau6 1:1.0.8-1+b2
ii libxcb1 1.14-2
ii libxdmcp6 1:1.1.2-3
ii lsb-base 11.1.0
ii policykit-1 0.105-29
ii procps 2:3.3.16-5
ii ucf 3.0043
ii x11-common 1:7.7+21
ii x11-xserver-utils 7.7+8
Versions of packages gdm3 recommends:
ii at-spi2-core 2.38.0-2
ii desktop-base 10.0.3
ii x11-xkb-utils 7.7+5
ii xserver-xephyr 2:1.20.9-2
ii xserver-xorg 1:7.7+21
ii zenity 3.32.0-6
Versions of packages gdm3 suggests:
ii gnome-orca 3.38.0-1
pn libpam-fprintd <none>
ii libpam-gnome-keyring 3.36.0-1
-- debconf information:
gdm3/daemon_name: /usr/sbin/gdm3
* shared/default-x-display-manager: gdm3
--- End Message ---
--- Begin Message ---
Hello,
On Sun, Oct 25, 2020 at 05:32:41PM +0900, nozzy123no...@gmail.com wrote:
> Package: gdm3
> Version: 3.38.1-2
> Severity: grave
>
> Dear Maintainer,
> After I upgraded my Debian box using the command of "apt upgrade" on
> 17th Oct 2020, I always get an "Oops! A problem occurred!" screen after
> login.
Thats bad!
>
> According to system logs, I seem gdm3 come to invoke gdm-x-session
> always at the beginning of the user session, even though gdm3 is
> running in Wayland on the login screen. Therefore gnome-shell of the
> user session seems to fail.
gdm(3) can run in either wayland or Xorg mode, and can then launch
both wayland or X sessions. This is as expected.
>
> Does anyone fix this problem?
There's absolutely no information to go on in this bug report to be
able to tell what problem you ran into, so sorry to say it but no.
This seems more like a support request rather than a bug report and
unfortunatly the bug tracking system is not a good way to get support.
If you still have this problem please try any of the publicly available
support forums where someone can likely help guide you into the
direction of finding out what the problem is and then how to adress it.
Regards,
Andreas Henriksson
--- End Message ---
