I was reading content on tracking bug. Not sure what you mean by âtraditonal nautilusâ I assume you mean like the nautilus we used on 16.04. PCMFM works like traditional nautilus only , thing is , options are on the header bar.
I will keep using VMs, but I can grab an old Dell Latitude D630 or D610 and start testing on bare metal if I must.
By the way, @dale-f-beaudoin if you donât know already (Iâm pretty sure you do), the codename has been announced, the next LTS of Ubuntu is 18.04 Bionic Beaver.
Yes ⊠it is always good to have bare metal test because often times a VM will not always set up environment variables as bare metal would.
And Yes, Bionic Beaver it is
ventrical@ventrical-MS-7850:~$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu Bionic Beaver (development branch)
Release: 18.04
Codename: bionic
ventrical@ventrical-MS-7850:~$
A Dell D630 should give you a decent install of 17.10 xorg and if it is Intel graphics ⊠maybe even wayland option also. You should start with fresh install of 17.10 and then upgrade to Bionic from there.
How to Upgrade to Bionic:
Go to terminal after you have booted into fresh install and:
sudo sed -i âs/artful/bionic/gâ /etc/apt/sources.list
Your will have to go into software&updates and enable all the repositories to get updates.
An after you update repos then Software&Updates will not work becasue software-properties-gtk which you will then have to edit the ubuntu.info file lots of fun. so hold on till I update the wiki
After running the above command, especially very early in the development cycle could stop Software & Updates (software-properties-gtk) from running. To solve the problem, insert the following text in /usr/share/python-apt/templates/Ubuntu.info:
Suite: bionic
RepositoryType: deb
MatchName: .*
BaseURI: cdrom:[Ubuntu.*17.10
MatchURI: cdrom:[Ubuntu.*17.10
Description: Cdrom with Ubuntu 17.10 âbionic beaverâ
Available: False
Component: main
CompDescription: Officially supported
Component: restricted
CompDescription: Restricted copyright
Suite: bionic
Official: false
RepositoryType: deb
BaseURI: http://archive.canonical.com
MatchURI: archive.canonical.com
Description: Canonical Partners
Component: partner
CompDescription: Software packaged by Canonical for their partners
CompDescriptionLong: This software is not part of Ubuntu.
Suite: bionic
Official: false
RepositoryType: deb
BaseURI: http://extras.ubuntu.com
MatchURI: extras.ubuntu.com
Description: Independent
Component: main
CompDescription: Provided by third-party software developers
CompDescriptionLong: Software offered by third party developers.
Roger, I will do it tomorrow, both on a VM and a Dell D630. Not sure if its old Intel HD graphics will be supported for Wayland, but it should at least run in non-lowGFX mode.
Not sure what you mean by âtraditonal nautilusâ I assume you mean like the nautilus we used on 16.04
Yes. Or rather how it was exactly in 17.04.
PCMFM works like traditional nautilus only , thing is , options are on the header bar.
FCMFM doesnât use gtk-headerbar. It uses toolbar+titlebar (like gimp, synaptic). Technically we can use any file-manager. But itâs the integration which is important.
Nautilus draws the desktop, icons on desktop and tied up with wallpaper which is related to gnome-settings-daemon. This, in turn, related to Unity control center (Settings-> Appearance â Wallpaper)âŠEverything is tied up with one another. So if we choose to use different file manager we have to change code for each of these components. And this is not an easy task.
Atm, I am concentrating on fixing which are broken.
Nautilus will work even without my patch. But people who uses LIM in Unity (& I think itâs very popular feature) wonât be too happy because LIM simply canât work without no-csd patch.
But there is a discussion going in Canonical desktop teamâŠthey want to remove all the headerbar patches from every gnome apps which is a bad news for us. Thatâs why I am starting a new thread in desktop category how we can have best of the both world.
Ok, did a fresh install of 17.10 and I have been greeted by Ubuntu Wayland session, as seen in >pic related. I did not know this D630 had a quadro GPU, while in Windows I only used the Intel HD graphics in it.
I then proceeded to login into x session. Then I:
sudo apt install unity-session notify-osd gtk3-nocsd
Then I restart, login into Unity-session, updated to 18.04 and now Software and Updates is broken as predicted. I did add that text into ubuntu. info using nano, didnât seem to help. I will wait until you finish the wiki
Your will have to go into software&updates and enable all the repositories to get updates.
An after you update repos then Software&Updates will not work becasue software-properties-gtk which you will then have to edit the ubuntu.info file lots of fun. so hold on till I update the wiki
Today I reinstalled 17.10 on the D630. After:
sudo sed -i âs/artful/bionic/gâ /etc/apt/sources.list
and
sudo apt-get update
I went to Software&Updates to enable all repositories, and after that I then I proceeded to
sudo apt update
sudo apt dist-upgrade
sudo apt update
sudo apt upgrade
sudo reboot
I think I should be ok now (I guess) and I suggest everybody does the same when upgrading to Bionic
Thanks for your update biky
It used to take a while for the Ubuntu.info file to get updated so we had this other proven method we used at ubuntuforums which was provided by the team there for early adopters (which of course still works- which you have proven)
So now you can just keep update/upgrade and if you have launchpad you can file bugs but if you have specific bug to file you should open an new thread in quality of the bug you have filed. If you do not use launchpad you can open a new thread in quality and attempt to describe the behaviour and post screen shots . I have several installations on several different machines and I always keep in mind that I have to test gnome3 with wayland which will be the new default but it is not prerequisite that we all have to do this and so you can just test unity-session which is why we are here
thanks for being an early adopter.
Is it preferable to test âunity-sessionâ under primary Ubuntu 17.10 flavour or we can equaly use one of those ISOâs with âcleanâ Unity installation ?
I even conducted some quick basic test (with stopwatch) of boot time for both of them. It seems that âunity-sessionâ as an add-on under original 17.10 is a little bit slower to boot than original âubuntu-sessionâ under wayland. The same goes for âubuntu-sessionâ under Xorg.
But⊠boot time of previously mentioned âcleanâ Unity ISOâs is as quick as original âubuntu-sessionâ under Wayland. A difference is not that significant (maybe 15%) but can lead to some conclusions.
