Testing unity-session in 18.04

Screenshot from 2017-10-24 18-17-01

nor on my intel box.

ventrical@ventrical-MS-7850:~$ inxi -Fxz
System:    Host: ventrical-MS-7850 Kernel: 4.13.0-16-generic x86_64
           bits: 64 gcc: 7.2.0
           Desktop: Gnome 3.26.1 (Gtk 3.22.24-0ubuntu1) Distro: Ubuntu 17.10
Machine:   Device: desktop Mobo: MSI model: B85-G41 PC Mate(MS-7850) v: 1.0 serial: N/A
           BIOS: American Megatrends v: V2.8 date: 07/17/2014
CPU:       Dual core Intel Pentium G3240 (-MCP-) 
           arch: Haswell rev.3 cache: 3072 KB
           flags: (lm nx sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx) bmips: 12398
           clock speeds: max: 3100 MHz 1: 3099 MHz 2: 3099 MHz
Graphics:  Card: Intel Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller
           bus-ID: 00:02.0
           Display Server: x11 (X.Org 1.19.5 )
           drivers: modesetting (unloaded: fbdev,vesa)
           Resolution: 1440x900@59.89hz
           OpenGL: renderer: Mesa DRI Intel Haswell Desktop
           version: 4.5 Mesa 17.2.2 Direct Render: Yes
Audio:     Card-1 Intel 8 Series/C220 Series High Def. Audio Controller
           driver: snd_hda_intel bus-ID: 00:1b.0
           Card-2 Intel Xeon E3-1200 v3/4th Gen Core Processor HD Audio Controller
           driver: snd_hda_intel bus-ID: 00:03.0
           Sound: Advanced Linux Sound Architecture v: k4.13.0-16-generic
Network:   Card: Realtek RTL8111/8168/8411 PCIE Gigabit Ethernet Controller
           driver: r8169 v: 2.3LK-NAPI port: e000 bus-ID: 02:00.0
           IF: enp2s0 state: up speed: 100 Mbps duplex: full mac: <filter>
Drives:    HDD Total Size: 120.0GB (22.0% used)
           ID-1: /dev/sda model: KINGSTON_SV300S3 size: 120.0GB
Partition: ID-1: / size: 52G used: 22G (45%) fs: ext4 dev: /dev/sda6
           ID-2: swap-1 size: 3.21GB used: 0.00GB (0%)
           fs: swap dev: /dev/sda5
RAID:      No RAID devices: /proc/mdstat, md_mod kernel module present
Sensors:   System Temperatures: cpu: 29.8C mobo: 27.8C
           Fan Speeds (in rpm): cpu: N/A
Info:      Processes: 209 Uptime: 5 min Memory: 1065.8/3811.1MB
           Init: systemd runlevel: 5 Gcc sys: N/A
           Client: Shell (bash 4.4.121) inxi: 2.3.37 
ventrical@ventrical-MS-7850:~$ 

Thanks. The related tracking bug is: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1727168

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.
Screenshot from 2017-10-25 06-22-41

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.

Hi biky,

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 :slight_smile:

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

then:

sudo apt-get update && sudo apt-get dist-upgrade
then:

sudo apt-get update
sudo apt-get upgrade

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 :slight_smile: lots of fun. so hold on till I update the wiki :slight_smile:

Software-Properties-Gtk doesn’t work

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
BaseURI: http://ports.ubuntu.com/ubuntu-ports/
MatchURI: ports.ubuntu.com/ubuntu-ports
BaseURI-amd64: http://archive.ubuntu.com/ubuntu
MatchURI-amd64: archive.ubuntu.com/ubuntu
BaseURI-i386: http://archive.ubuntu.com/ubuntu
MatchURI-i386: archive.ubuntu.com/ubuntu
MirrorsFile-amd64: Ubuntu.mirrors
MirrorsFile-i386: Ubuntu.mirrors
Description: Ubuntu 17.10 ‘bionic beaver’
Component: main
CompDescription: Officially supported
CompDescriptionLong: Canonical-supported free and open-source software
Component: universe
CompDescription: Community-maintained
CompDescriptionLong: Community-maintained free and open-source software
Component: restricted
CompDescription: Non-free drivers
CompDescriptionLong: Proprietary drivers for devices
Component: multiverse
ParentComponent: universe
CompDescription: Restricted software
CompDescriptionLong: Software restricted by copyright or legal issues

Suite: bionic
ParentSuite: bionic
RepositoryType: deb-src
BaseURI: http://archive.ubuntu.com/ubuntu/
MatchURI: archive.ubuntu.com/ubuntu|ports.ubuntu.com/ubuntu-ports
Description: Ubuntu 17.10 ‘bionic beaver’

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.

Suite: bionic-security
ParentSuite: bionic
RepositoryType: deb
BaseURI: http://ports.ubuntu.com/ubuntu-ports/
MatchURI: ports.ubuntu.com/ubuntu-ports
BaseURI-amd64: http://security.ubuntu.com/ubuntu/
MatchURI-amd64: archive.ubuntu.com/ubuntu|security.ubuntu.com
BaseURI-i386: http://security.ubuntu.com/ubuntu/
MatchURI-i386: archive.ubuntu.com/ubuntu|security.ubuntu.com
Description: Important security updates

Suite: bionic-security
ParentSuite:bionic
RepositoryType: deb-src
BaseURI: http://archive.ubuntu.com/ubuntu/
MatchURI: archive.ubuntu.com/ubuntu|ports.ubuntu.com/ubuntu-ports|security.ubuntu.com
Description: Important security updates

Suite: bionic-updates
ParentSuite: bionic
RepositoryType: deb
Description: Recommended updates

Suite:bionic-updates
ParentSuite: bionic
RepositoryType: deb-src
BaseURI: http://archive.ubuntu.com/ubuntu/
MatchURI: archive.ubuntu.com/ubuntu|ports.ubuntu.com/ubuntu-ports
Description: Recommended updates

Suite: bionic-proposed
ParentSuite: bionic
RepositoryType: deb
Description: Pre-released updates

Suite: bionic-proposed
ParentSuite: bionic
RepositoryType: deb-src
BaseURI: http://archive.ubuntu.com/ubuntu/
MatchURI: archive.ubuntu.com/ubuntu|ports.ubuntu.com/ubuntu-ports
Description: Pre-released updates

Suite: bionic-backports
ParentSuite: bionic
RepositoryType: deb
Description: Unsupported updates

Suite: bionic-backports
ParentSuite: bionic
RepositoryType: deb-src
BaseURI: http://archive.ubuntu.com/ubuntu/
MatchURI: archive.ubuntu.com/ubuntu|ports.ubuntu.com/ubuntu-ports
Description: Unsupported updates

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.

Regrads,
Biky

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. Thank you for your explanation. My point is that we might have to accept something more lean and economic and make that work if we can.

Regards…

Please send me link to new topic.

nevermind. I seen bug report

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.
Screenshot from 2017-10-26 08-11-00
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 :smiley:

We are trying out a new method. Seem things have changed a bit… or you can wait for the update (just keep update/upgrading)

sudo sed -i 's/artful/bionic/g' /etc/apt/sources.list
sudo sed -i 's/artful/bionic/g' /usr/share/python-apt/templates/Ubuntu.info
sudo apt-get update
sudo apt-get upgrade
sudo reboot

so since you have your sources.list you can try just this:

sudo sed -i 's/artful/bionic/g' /usr/share/python-apt/templates/Ubuntu.info
sudo apt-get update
sudo apt-get upgrade
sudo reboot

regards…

I also encourage testers to visit here or join here for more help on early adopter testing and bug reporting. https://ubuntuforums.org/forumdisplay.php?f=427

Regards…

Now there is also a Unity7-Testing.iso based on Ubuntu 18.04 Development Branch at Sourceforge, together with Unity7 based on 17.10
https://sourceforge.net/projects/unity7sl/files/

Hi Biky,

Here is a link to a very good work-a-round. You may no thave todo what I suggested on your current install. I am still working on wiki update;)

https://ubuntuforums.org/showthread.php?t=2359108&p=13703481#post13703481

Hi Chanath,

Yes … I had created my own Unity.ISO based on 17.10 as I know you did. I will just keep updating and keep a watchful eye. :wink:
regards…

Thanks!
Now Nautilus looks more like Ubuntuish!Nautilus

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

then:

sudo apt-get update && sudo apt-get dist-upgrade
then:

sudo apt-get update
sudo apt-get upgrade

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 :slight_smile: lots of fun. so hold on till I update the wiki :slight_smile:

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 :slight_smile:
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) :wink:

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 :slight_smile:
thanks for being an early adopter.

Regards…

1 Like

Hello,

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.