[Desktop-packages] [Bug 1762391] Re: pam_group.so is not evaluated by gnome-terminal

There is also a Gnome bug for this at https://gitlab.gnome.org/GNOME/gdm/issues/393# -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/1762391 Title: pam_group.so is not evaluated

[Desktop-packages] [Bug 1762391] Re: pam_group.so is not evaluated by gnome-terminal

I am also using this feature and all previous versions of Ubuntu worked fine with this configuration. However with Bionic the GDM logins no longer add these local groups. Only no graphical logins like su, sudo, ssh, etc... add the appropriate local groups as per the /etc/security/group.conf. This

[Desktop-packages] [Bug 986991] Re: Hostname left to "ubuntu-0" in Bluetooth settings after install from live cd

Restarting bluetooth does set it back to ubuntu-0 again. So it seems a fix would be to put that into the bluetooth startup process perhaps. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launc

[Desktop-packages] [Bug 986991] Re: Hostname left to "ubuntu-0" in Bluetooth settings after install from live cd

OK well that worked on the command line but not in the rc.local :( -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/986991 Title: Hostname left to "ubuntu-0" in Bluetooth s

[Desktop-packages] [Bug 986991] Re: Hostname left to "ubuntu-0" in Bluetooth settings after install from live cd

As a work around, I have done the following. I added the following into rc.local hciconfig hci0 name $HOSTNAME -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/986991 Titl