Happy Inspection of Hippo Kubuntu 21.04

[NoWorries]

I just realized that Radcliff started a thread on 21.04 but with the wrong name.

I have downloaded the iso's for the 4th and 5th of November and both did that same by just progressing to the Desktop with an error message stating;
[#]The installer encountered an unrecoverable error. A desktop session will now be run so that you may investigate the problem or try installation again.[/#]

I was able to get the desktop and got the KSystemLog

6 Nov 2020 06:19:17    org.kde.KScreen         Primary: false
6 Nov 2020 06:19:17    org.kde.KScreen    kscreen.xrandr: Output 184 : connected = true , enabled = true
6 Nov 2020 06:19:17    org.kde.KScreen    kscreen.xrandr: XRandROutput 184 update
6 Nov 2020 06:19:17    org.kde.KScreen         m_connected: 0
6 Nov 2020 06:19:17    org.kde.KScreen         m_crtc XRandRCrtc(0x55a056b72090)
6 Nov 2020 06:19:17    org.kde.KScreen         CRTC: 182
6 Nov 2020 06:19:17    org.kde.KScreen         MODE: 186
6 Nov 2020 06:19:17    org.kde.KScreen         Connection: 0
6 Nov 2020 06:19:17    org.kde.KScreen         Primary: false
6 Nov 2020 06:19:17    org.kde.KScreen    kscreen.xrandr: Output 184 : connected = true , enabled = true
6 Nov 2020 06:19:17    org.kde.KScreen    kscreen.xrandr: XRandROutput 66 update
6 Nov 2020 06:19:17    org.kde.KScreen         m_connected: 0
6 Nov 2020 06:19:17    org.kde.KScreen         m_crtc XRandRCrtc(0x55a056b723d0)
6 Nov 2020 06:19:17    org.kde.KScreen         CRTC: 63
6 Nov 2020 06:19:17    org.kde.KScreen         MODE: 69
6 Nov 2020 06:19:17    org.kde.KScreen         Connection: 0
6 Nov 2020 06:19:17    org.kde.KScreen         Primary: true
6 Nov 2020 06:19:17    org.kde.KScreen    kscreen.xrandr: Output 66 : connected = true , enabled = true
6 Nov 2020 06:19:17    org.kde.KScreen    kscreen.xrandr: XRandROutput 67 update
6 Nov 2020 06:19:17    org.kde.KScreen         m_connected: 1
6 Nov 2020 06:19:17    org.kde.KScreen         m_crtc QObject(0x0)
6 Nov 2020 06:19:17    org.kde.KScreen         CRTC: 0
6 Nov 2020 06:19:17    org.kde.KScreen         MODE: 0
6 Nov 2020 06:19:17    org.kde.KScreen         Connection: 1
6 Nov 2020 06:19:17    org.kde.KScreen         Primary: false
6 Nov 2020 06:19:17    org.kde.KScreen    kscreen.xrandr: Output 67 : connected = false , enabled = false
6 Nov 2020 06:19:18    org.kde.KScreen    kscreen.xrandr: Emitting configChanged()
6 Nov 2020 06:19:19    dbus-daemon    [session uid=999 pid=1734] Successfully activated service 'org.freedesktop.Notifications'
6 Nov 2020 06:19:19    dbus-daemon    [session uid=999 pid=1734] Activating service name='org.kde.KSplash' requested by ':1.200' (uid=999 pid=2979 comm="/usr/bin/plasmashell " label="unconfined")
6 Nov 2020 06:19:52    systemd    Created slice app.slice.
6 Nov 2020 06:19:52    systemd    Started app-org.kde.ksystemlog-85c2cb94b275452db2278d6c11cd346f.scope.
6 Nov 2020 06:19:52    sudo     kubuntu : TTY=pts/1 ; PWD=/home/kubuntu ; USER=root ; COMMAND=/usr/lib/x86_64-linux-gnu/libexec/kf5/kdesu_stub -
6 Nov 2020 06:19:52    sudo    pam_unix(sudo:session): session opened for user root by (uid=0)
6 Nov 2020 06:19:52    sudo     kubuntu : TTY=pts/2 ; PWD=/home/kubuntu ; USER=root ; COMMAND=/usr/lib/x86_64-linux-gnu/libexec/kf5/kdesu_stub -
6 Nov 2020 06:19:52    sudo    pam_unix(sudo:session): session opened for user root by (uid=0)
6 Nov 2020 06:19:52    dbus-daemon    [session uid=0 pid=3175] AppArmor D-Bus mediation is enabled
6 Nov 2020 06:20:19    org.kde.KSplash    org.kde.knotifications: WaitForName: Service was not registered within timeout
6 Nov 2020 06:20:19    dbus-daemon    [session uid=999 pid=1734] Activated service 'org.kde.KSplash' failed: Process org.kde.KSplash exited with status 1

So once this problem has been fixed, I look forward to happily test Hippo. I expect that it will initially be very similar to Groovy, but will soon diverge.

[NoWorries]

So that I don't spend time downloading 2.9GiB hirsute-desktop-amd64.iso files that fail to install, could someone in the know please advise when the problems mentioned in my initial post are fixed?

Thank you in anticipation.

[claydoh]

Simply wait a few days to a week. It's way to early imnsho. Ubuntu is still setting up the builds and getting things in order.

Again imnsho until your can find 21.04 packages on packages.ubuntu.com playing with HH is rather useless. I'd suggest waiting till the either Ubuntu officially opens it for development or , more preferably, kubuntu themselves begin work on things after this.

Having said that Kubuntu devs are not chatty on mailing be lists about what is going on so my process was to check for plasma related packages in the HH archives and look for new versions.

Sent from my LM-V600 using Tapatalk

[claydoh]

Also in the past anything much over 2gb in size was often 'bad' or would have issues.


If you don't already use it look at using zsync as it will only download the differences between the builds, if you use the image from the "current" directory.

https://help.ubuntu.com/community/ZsyncCdImage

This will save gobs of gb [emoji16]

Sent from my LM-V600 using Tapatalk

[NoWorries]

Thanks very much for the clarification. Before I put the question of how long to wait, I was planning to try again after a week. This week will be rather busy for our family, so a break will be great and after that, I hope to be able to happily inspect Hippo.

[claydoh]

https://discourse.ubuntu.com/t/hirsu...schedule/18539

Things have barely started, imnsho waiting till early or mid December is (historically, in my experience) a better time to begin checking things out. new features or experiments start later, as does Kubuntu development.


But using zsync will 100% save many many gb of iso downloads, for sure.

[Radcliff]

Nov 5th ISO is unusable here too with the same error (Rufus 3.12). The server was very slow at transferring data.

Hirsute Hanimal did exist a few days when Hippo was undecided. Ubuntu even made an ISO on Oct 27th.

[jlittle]

But using zsync will save many many gb of iso downloads...

+1

When I've done this, with the iso changing daily, the update is usually 1 to 5%. In other words, the download usually starts at 95 to 99% complete.

Unless you want to test the whole burning process, if you're testing daily, using iso booting, in a VM or direct to storage, saves lots of time too. Typically, I'd run a script with the zsync command, then boot into the new daily iso, where it's been downloaded, in a few minutes. If I test it by doing an installation, in about 10 to 15 minutes.

[NoWorries]

I would certainly give claydoh's suggestion for the zsync approach a +1 as well.

I must say that this is the first time I have encountered daily-builds that don't let you install.

So to see what progress is being made on a day by day basis, I store the Info Centre and record the Muon Package Manager installed and available packages.

The current Info Centre is:

Muon for the past two days has 1951 installed but the number of available changed from 61,541 to 61,552.

So progress is steadily being made as shown by these numbers which unfortunately do not show which of the may packages have been upgraded.

[acheron]

Plasma 5.20.3 is now landing in 21.04. HOWEVER, if you upgrade right now you may see a broken kwin/shell, because some parts of plasma are delayed hitting the release pocket due to a backlog in automated testing. Hopefully this will resolve before the end of today.

[acheron]

Plasma 5.20 should be good now.

[NoWorries]

Looking great and certainly very different to Groovy, ie KDE Plasma 5.19.5 > 5.20.3 and QT 5.14.2 > 5.15.1.

I look forward to the time when we can all install Hippo as it is now just over 3 week since the release of Groovy. By comparison, Groovy could be installed 1 week after Focal was released.

[NoWorries]

Well I have now successfully install 21.04 on my Sacrificial Laptop. I now have the following system information.



The way I did it was to start a console session using the 21.04 desktop from the startup usb and entered "ubiquity" and this started the installation. Prior to doing this, as I was stopped at the initial desktop and could not proceed, I got Muon and installed all the pre-released updates.

So now I have Hippo running and am using it for this post. So as you can image, I am very happy with its current state of development.

I have also tried Wayland and it is much improved. My favourite applications all work as they should. The main problem at this stage is that it does not recognize my external monitor.

The window title at the top does not show the name because of the font size. Also, the control at the top right edge is not all together clear but it is useable. Considering the early stage of development it is very commendable to see the progress being made.

[NoWorries]

Following my successful installation of Hippo, I have now found that the approach I previously used no longer works. So to me, it seems that this method has been Snookered by the developers.

The error message that I get when I enter ubiquity is:

/usr/bin/ubiquity:74: Depreciation Warning: The imp module is depreciated in favour of importlib;  
see the module's documentation for alternative uses

I used importlib in Muon and installed all the modules that were listed. That made no difference

I would like to hear from anyone who knows how to solve this problem.

[jlittle]

The deprecation is only a warning. It occurs with groovy.