On Sat, Jan 21, 2017 at 06:56:33AM -0500, Jeremy Bicha wrote:
> On 21 January 2017 at 06:50, SteveA wrote:
> > It sure did, got bit by that yesterday. In the meantime, 'startx' should
> > work, did for me.
>
> You saw that this bug is fixed now, right?
>
Yes indeed. 😌
--
Ubuntu-GNOME mailing l
On 21 January 2017 at 06:50, SteveA wrote:
> It sure did, got bit by that yesterday. In the meantime, 'startx' should
> work, did for me.
You saw that this bug is fixed now, right?
> Are those 2 lines above a mistype? ...launchpad??
Yes, I'm making all sorts of typos in this thread! :(
Thanks,
On Thu, Jan 19, 2017 at 11:09:53PM -0500, Jeremy Bicha wrote:
> If you are testing Ubuntu 17.04 "zesty" (still in Alpha), do not
> upgrade gnome-shell because 3.22.2-2ubuntu1 will break gdm. [1]
It sure did, got bit by that yesterday. In the meantime, 'startx' should
work, did for me.
> Thanks,
>
On 20/01/2017 20:40, Jeremy Bicha wrote:
On 20 January 2017 at 04:09, Jeremy Bicha wrote:
If you are testing Ubuntu 17.04 "zesty" (still in Alpha), do not
upgrade gnome-shell because 3.22.2-2ubuntu1 will break gdm. [1]
The gnome-shell issue is fixed in 3.22.2-3ubuntu1
sudo apt-mark hold gn
On 20 January 2017 at 04:09, Jeremy Bicha wrote:
> If you are testing Ubuntu 17.04 "zesty" (still in Alpha), do not
> upgrade gnome-shell because 3.22.2-2ubuntu1 will break gdm. [1]
The gnome-shell issue is fixed in 3.22.2-3ubuntu1
sudo apt-mark hold gnome-shell
sudo apt-mark hold gnome-shell-co
If you are testing Ubuntu 17.04 "zesty" (still in Alpha), do not
upgrade gnome-shell because 3.22.2-2ubuntu1 will break gdm. [1]
Since unattended-upgrades install all updates automatically [2], I
recommend you run the following commands until this issue is fixed:
sudo apt-mark hold gnome-shell
su
