This bug was fixed in the package gnome-session - 3.33.90-2ubuntu1
---------------
gnome-session (3.33.90-2ubuntu1) eoan; urgency=medium
* Merge with Debian, remaining changes:
- debian/control.in:
+ Recommend session-migration
+ Move xwayland dependency to gnome-session and make gnome-session
Arch: any
+ Split gnome-startup-applications to a separate binary package so
that it can be uninstalled without breaking the system
+ Add unity-session
- Split ubuntu-session out of gnome-session.
- Add upstart user session and systemd user session:
debian/data, debian/gnome-session-bin.user-session.upstart
- debian/gnome-session-bin.postinst, debian/gnome-session-bin.prerm:
Moved registering gnome-session binary as a session manager to
gnome-session-bin package
- Add gnome-session-wayland transitional package
- don't install gnome-mimeapps.list (installed by desktop-file-utils in
Ubuntu):
debian/gnome-session-common.dirs, gnome-session-common.install,
gnome-session-common.maintscript, gnome-session-common.postinst
- debian/patches/103_kill_the_fail_whale.patch:
+ Kill the Fail Whale as it tends to be more annoying than helpful
- debian/patches/22_support_autostart_delay.patch:
+ Bugzilla patch to support adding a delay to autostart apps, using
a "X-GNOME-Autostart-Delay" key in the desktop file
- debian/patches/50_ubuntu_sessions.patch:
+ Add ubuntu session tweaks
- debian/patches/51_remove_session_saving_from_gui.patch:
+ Add GNOME_SESSION_SAVE environment variable for people wanting to
use the save session still, knowing that it can break your system
if used unwisely
- debian/patches/53_add_sessionmigration.patch:
+ launch session-migration if present at the start of the session.
This sync tool runns different session migration scripts that can be
provided in various desktop packages.
- debian/patches/95_dbus_request_shutdown.patch:
+ Add "RequestShutdown" and "RequestReboot" DBus methods to allow
other applications to shutdown or reboot the machine via the session
manager.
- debian/patches/ignore_gsettings_region.patch:
+ Ignore the "region" gsettings value - users' setting of LC_*
variables saved in ~/.pam_environment.
- debian/patches/revert_remove_gnome_session_properties.patch:
+ Don't merge translations into gnome-session-properties.desktop
- debian/ubuntu-settings-migrate-to-defaults.18.10.1.py:
+ Migrate users using old default ubuntu-settings to current ones
* ubuntu-sessions.patch: Refresh
gnome-session (3.33.90-2) experimental; urgency=medium
* rules, gnome-.desktop.in.in-Pass-systemd.patch: Build with
-Dsystemd_session=enable. Build gnome-session with
-Dsystemd_session=enable (instead of =default). This means that sessions
need to pass `--systemd` to launch using systemd.
gnome-session (3.33.90-1ubuntu1) eoan; urgency=medium
* Merge with Debian, remaining changes:
- debian/control.in:
+ Recommend session-migration
+ Move xwayland dependency to gnome-session and make gnome-session
Arch: any
+ Split gnome-startup-applications to a separate binary package so
that it can be uninstalled without breaking the system
+ Add unity-session
- Split ubuntu-session out of gnome-session.
- Add upstart user session and systemd user session:
debian/data, debian/gnome-session-bin.user-session.upstart
- debian/gnome-session-bin.postinst, debian/gnome-session-bin.prerm:
Moved registering gnome-session binary as a session manager to
gnome-session-bin package
- Add gnome-session-wayland transitional package
- don't install gnome-mimeapps.list (installed by desktop-file-utils in
Ubuntu):
debian/gnome-session-common.dirs, gnome-session-common.install,
gnome-session-common.maintscript, gnome-session-common.postinst
- debian/patches/103_kill_the_fail_whale.patch:
+ Kill the Fail Whale as it tends to be more annoying than helpful
- debian/patches/22_support_autostart_delay.patch:
+ Bugzilla patch to support adding a delay to autostart apps, using
a "X-GNOME-Autostart-Delay" key in the desktop file
- debian/patches/50_ubuntu_sessions.patch:
+ Add ubuntu session tweaks
- debian/patches/51_remove_session_saving_from_gui.patch:
+ Add GNOME_SESSION_SAVE environment variable for people wanting to
use the save session still, knowing that it can break your system
if used unwisely
- debian/patches/53_add_sessionmigration.patch:
+ launch session-migration if present at the start of the session.
This sync tool runns different session migration scripts that can be
provided in various desktop packages.
- debian/patches/95_dbus_request_shutdown.patch:
+ Add "RequestShutdown" and "RequestReboot" DBus methods to allow
other applications to shutdown or reboot the machine via the session
manager.
- debian/patches/ignore_gsettings_region.patch:
+ Ignore the "region" gsettings value - users' setting of LC_*
variables saved in ~/.pam_environment.
- debian/patches/revert_remove_gnome_session_properties.patch:
+ Don't merge translations into gnome-session-properties.desktop
- debian/ubuntu-settings-migrate-to-defaults.18.10.1.py:
+ Migrate users using old default ubuntu-settings to current ones
* ubuntu-sessions.patch: Add X-GDM-SessionRegisters=true to our.desktop
files. Following a change from upstream we need to register with GDM when
logging in, so that it knows when to shut itself down. (LP: #1798790)
* debian/patches/*: Rebase. Adjust the Ubuntu session to account for dropped
components
* Drop our downstream gnome-session upstart override and service. We have
this upstream now (and upstart is gone)
gnome-session (3.33.90-1) experimental; urgency=medium
* New upstream release
+ Add support to manage the session using the systemd user instance. A new
systemd_session build time option is added to enable/disable the support
and set it as the default (disable/enable/default). Right now the
support is enabled by default.
- For Debian this means that we are now (in experimental, currently!)
requiring systemd for GNOME sessions.
+ Update session definitions to match new gnome-settings-daemon
+ don't show logout button in fail whale when not logged in
+ handle apps exiting abruptly at log out better
* debian/rules: Disable systemd session support on !linux
* control: Bump gnome-shell/gnome-settings-daemon/gdm requirements.
For the systemd --user support, ensure that people have all the
components involved at 3.33.90.
* Install systemd units into gnome-session-bin. They are needed by
`/usr/bin/gnome-session` itself.
* util-Blacklist-some-session-specific-variables.patch: Take from MR. Don't
upload some session specific variables into the D-Bus and systemd
environments, otherwise some things will get the wrong idea about what
session they're running in.
gnome-session (3.33.4-1) experimental; urgency=medium
* debian/watch: Find unstable versions too
* New upstream release
+ advertize support for GDM's session registration API
+ fix idle detection
+ fix warning in log spew with dbus activated services
-- Iain Lane <iain.l...@canonical.com> Sat, 24 Aug 2019 08:55:06 +0100
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-session in Ubuntu.
https://bugs.launchpad.net/bugs/1798790
Title:
Ubuntu login screen sometimes doesn't appear on a single GPU Nvidia
system (and setting WaylandEnable=false fixes it)
Status in gdm:
Fix Released
Status in gdm3 package in Ubuntu:
Fix Released
Status in gnome-session package in Ubuntu:
Fix Released
Status in gnome-shell package in Ubuntu:
Fix Released
Status in mutter package in Ubuntu:
Invalid
Status in gdm3 source package in Eoan:
Fix Released
Status in gnome-session source package in Eoan:
Fix Released
Status in gnome-shell source package in Eoan:
Fix Released
Status in mutter source package in Eoan:
Invalid
Bug description:
https://gitlab.gnome.org/GNOME/gdm/issues/483
formerly https://gitlab.gnome.org/GNOME/gdm/issues/435
---
The boot process hangs with the last message being "started bpfilter".
There is unusual Network activity during that time. The light of the
WiFi adapter is blinking a lot.
I am not sure the problem is with the gdm3 package. As a matter of
fact, I would remove it and let someone more experienced to set it.
I'm afraid I might break something, though.
The specific steps or actions you took that caused you to encounter the
problem: 1. Boot Ubuntu 18.10 with the Nvidia proprietary drivers
installed.
The behavior you expected: I expected Ubuntu 18.10 to boot normally.
The behavior you actually encountered: The computer gets stuck in a
command-like environment with the last message being "started
bpfilter". You can't type any commands.
I have found that uninstalling the Nvidia proprietary drivers by going
into recovery mode fixes the issue.
Booting with the earlier kernel doesn't fix the issue. Installing the
earlier v.340 driver also doesn't fix the issue.
This (https://askubuntu.com/questions/1032639/ubuntu-18-04-stuck-in-
boot-after-starting-gnome-display-manager-on-intel-graphic) seems
relevant. This is where I found the "solution".
To manage notifications about this bug go to:
https://bugs.launchpad.net/gdm/+bug/1798790/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
