sudo apt-get install lightdm
Thats it. If you have gdm3 installed it will ask you to choose. I remove gdm3 first then install lightdm.
unity-session is a shell in the universe. It is like...
Type: Posts; User: ventrical; Keyword(s):
sudo apt-get install lightdm
Thats it. If you have gdm3 installed it will ask you to choose. I remove gdm3 first then install lightdm.
unity-session is a shell in the universe. It is like...
unity-session shell is in the universe and is loaded on Bionic beaver amd64.iso using lightdm and boots just fine. You said we could discuss unity-session, not Ubuntu Development Version. so my reply...
It works very well on the unity-session with lightdm.
regards..
:)
I went ahead and hard installed to hdd and the UEFI/Intel_spi thingy is gone.
I'm going to try kubuntu just fo fun:) see if it will barf for me too :)
Regards..
Testing the bionic-desktop from Jan. 11/18 in live on Intel machine and still get "flash" verbose Firmware/Intel bug on bootup of USB.
Just seen/current .ISO is now Jan. 12/18
Regards
One install still has the <intel<-spi verbose error spill, even after updating the microcode..<but they are all working well otherwise in UEFi.
Upgraded second install of bionic-desktop and got the same kernel error.
Adding boot menu entry for EFI firmware configuration
done
Setting up linux-signed-image-4.13.0-25-generic (4.13.0-25.29)...
Re-initiated secureboot/ and used;
bootx64.efi
No verbose errors.
Oldfred suggested I remove the harddrive and put it back in:
So I did and nothing happened. It just booted normally with the Intel_spi, UEFI verbose warnings. but the three installs were all...
Failed to mention that took place on one of those affected Intel_spi UEFI/BIOS infectable devices. I had wiped the UEFI and reverted to legacy .. so that may explain it?
It didnt work but disabling UEFI and enable legacy worked just fine.
Anything to be concerned about?
Setting up linux-signed-image-4.13.0-25-generic (4.13.0-25.29) ...
warning: file-aligned section .text extends beyond end of file
warning: checksum areas are...
Thanks... I also thought the workaround was a security issue also. Problem solved for now.
I thought that only worked for synaptic..
thanks..
regards..
Restored the xenial desktop but now have the dreaded llvmpipe.
Huh?
No.. I'm serious... what do we use as a firewall for18.04 with wayland.
That seems to be one of the cases.
gufw still not working in wayland. (now a critical bug) Is wayland to be void of a firewall or do we just run ufw from terminal.
https://bugs.launchpad.net/ubuntu/+source/gui-ufw/+bug/1713238
@Knoob,
Since it appears that the BIOS bug has migrated to Bionic do you have any idea if the Bionic dailies will be patched also?
Regards..
My point being is that the BIOS UEFI bug from artful is now migrated to Bionic? and it's a xenial breaker?
regards...
Look at the screenshot in this post here: https://ubuntuforums.org/showthread.php?t=2380665&page=3&p=13726611#post13726611
That was from the bionic current jan. 01/01 with gnome3. I started it up...
Installing the bionic daily from Jan . 01/01/18 ISO will break 16.04 in UEFI mode while doing a 'alongside' installation. At this point , 16.04 is unrecoverable but Bionic will boot gnome-wayland.
...
@mac4man,
I moved the nemo based iso to the folder/nemo-iso.
Will the ppa be active up and to the end of the 18.04 cycle? It is such a good fit for that shell. I would like to do another...
Have you buy chance installed another FM?
Can you try ..
sudo apt-get remove nautilus
logoff, then
Please install..
sudo apt-get install inxi
then enter into terminal.