Final Focal on Kubuntu 20.04

[NoWorries]

This can't be stressed enough, by using proposed repos you are testing things that don't need to be tested and reporting breakages that don't need to be reported. What you do with your machine is your business but reporting the issues you face and asking for help eats up other people's time as well, time that could be productively spent elsewhere.

I did check to see if any bugs were reported using [#]muon : Depends: apt-xapian-index but it is not going to be installed[/#] but all bugs were old for example https://bugs.launchpad.net/ubuntu/+s...ex/+bug/363695. and https://bugs.launchpad.net/ubuntu/+s...dex/+bug/65583.

I am wondering if the developers were aware of the problem related to the installation of muon. I hope they are now aware of it.

From now on, as I have two systems with 20.04, I have one with proposed and the other without proposed. IF I find a problem with the proposed system, how should I go about notifying anyone of the problem?

[Snowhog]

IF I find a problem with the proposed system, how should I go about notifying anyone of the problem?

I think what kubicle and acheron are saying, is that no one (maybe pure developers?) should be using the proposed repository. Period. It exists for a specific use case, and people like us don't fall into that use case group. That's what I think.

[MoonRise]

Sorry for stealing this thread but I know those on this chain can answer.

So, I have an 18.04 system that I want to migrate to 20.04. Best way? I'd like to help in the Beta Testing if at all possible.

Thanks!

[Don B. Cilly]

Why not just get a daily build, install it to a separate partition, copy your /home to it (unless you already have it separate), see how you like it.

[claydoh]

Sorry for stealing this thread but I know those on this chain can answer.

So, I have an 18.04 system that I want to migrate to 20.04. Best way? I'd like to help in the Beta Testing if at all possible.

Thanks!

https://www.kubuntuforums.net/showth...r-Beta-testing


I don't think that upgrades are being tested just yet, though i think it will be soon, based on past history. Note that there are no upgrade testing scenarios listed on the Kubuntu page as of yet.

[GreyGeek]

Mixing parts of your old install, even IF it is only your home account, is a good way to create an unstable or problem plagued installation. My recommendation is to do the hard work of backing up your important data, doing a clean install to bare metal, and then install from the repository all the apps you need or want BEFORE restoring config files and data from your home backup. Then, after you've confirmed that your installation is running the way you want, use a backup tool to make a backup, then install the apps you use which are not in Kubuntu's standard repositories. If you are using BTRFS then a simple snapshot of @ and @home will take 5 seconds, or for ext4, Timeshift will do the back honors but it will take several minutes.

IF you only used AppImages and all of your images were inside your home account, or, all your installed apps were installed inside your home account, then installing 20.04 and not deleting /home would make sense. As it is, most apps split their installation between root, /opt, /sbin, etc., and data and other certain files, like ~/.local or ~/.config, etc... which are installed inside the home account.

tldr; summary: clean installs are always the most trouble free. IMO.

[NoWorries]

Sorry for stealing this thread but I know those on this chain can answer.

So, I have an 18.04 system that I want to migrate to 20.04. Best way? I'd like to help in the Beta Testing if at all possible.

Thanks!

Glad to hear that you are giving it a go and welcome to this thread.

As a seasoned Kubuntu participant, I assume you have a separate home partition. To be on the safe side it would be useful to copy all your /home directory and its hidden files onto an external drive which is formatted to your preferred Kubuntu file system. I made a big mistake recently when I could not copy my /home to a Kubuntu file system. I was using KDE Partition Manager and it made the owner and user root! I was able to change this back to my /home directory ownership and do the copy.

I have always installed a new system by using the manual option for disk partitioning, in the installation process, and format /root and keep the /home as is. If I strike problems on reboot, I then try locating the hidden file/files causing the problem and change names by adding _bk to the end of the file. I have always found on reboot that the system creates new versions and I then copy files that I need from my backup directory.

Hope you have success with 20.04 and find it, as many of us do, to be a great system.

[GreyGeek]

I would pretty much go with what NoWorries wrote, except that I am a fan of clean installs. I always created a single partition, "/" and let the system create /home without making it a separate partition. Then I install the applications I want. Then I do a reboot and make a backup. When that is finished I copy over the config and data file from the backup of my old /home account and adjust any setting that didn't get set up the way they were before the upgrade.

[Radcliff]

Bionic To Focal One Shot

So, I have an 18.04 system that I want to migrate to 20.04. Best way?

You should do a bootable stick of the daily ISO first, just in case. Backup important stuff.
http://cdimage.ubuntu.com/kubuntu/daily-live/current/

It's not all mirrors that support 20.04 yet. The best and fastest way is the is one below, we did it from 19.10 the very first week (Eoan). We have been tested many daily builds since then.

We have lost the installation 3 times in Proposed early in the cycle, but we define ourself as an aggressive tester.

Upgrading Bionic Beaver to Focal Fossa:

sudo sed -i 's/bionic/focal/g' /etc/apt/sources.list

sudo apt update && sudo apt -y dist-upgrade

do-release-upgrade -c

sudo do-release-upgrade

Before upgrading, do the following and redo them after upgrade:

sudo apt update && sudo apt upgrade -y

sudo apt autoremove

Clear thumbnails and cache:

rm -v -f ~/.cache/thumbnails/*/*.png ~/.thumbnails/*/*.png

rm -v -f ~/.cache/thumbnails/*/*/*.png ~/.thumbnails/*/*/*.png

sync; echo 3 | sudo tee /proc/sys/vm/drop_caches

Go luck,

[NoWorries]

From now on, as I have two systems with 20.04, I have one with proposed and the other without proposed. IF I find a problem with the proposed system, how should I go about notifying anyone of the problem?

Just for the record, my system with proposed enabled, now has muon working and I have purged Synaptic from this system.

[GreyGeek]

I did a test of installing 20.04 into a 64GB USB stick in an attempt to try out ZFS as the root fs. BUT, I couldn't find it in the list of file systems to choose from. I posted about this on Telegraph and Valorie told me that ZFS is NOT in the list of file systems to chose from and probably won't be added until some "things" are worked out.

[acheron]

I'm presently using 20.04 as my primary system, Neon is available as a second option, and find it very nice.
Because I'm a bit handicapped without the kipi plugins

They are in the archive now.

apt-get install kipi-plugins

Gwenview/Discover can't find them, as the appstream data is wrong. Currently fixing that.

[Radcliff]

Synaptic History

There were only 60 packages in Proposed today. Python3.8, office and a new Kernel update are among them.

Removing Moun in favor of Synaptic does not help.

sudo apt purge muon && sudo apt install synaptic

-Synaptic history remains empty for incoming updates, but it works normally. In the other classroom, Synaptic was written by The Hand Of God. Sucks!

-Logout, restart and shutdown is delayed. Disabling Google Services in Sync is also delayed when asked to relaunch Chrome. All present in kde 5.18.80 too.

dpkg -l|grep google
ii  google-chrome-unstable                        83.0.4093.3-1                               amd64        The web browser from Google

-Another long lasting issue on our AMD motherboard, some windows (apps) become unusable, they're disappearing top right corner. An app that opens normally must stay open to override this bug.

KSysGuard, Office, GUFW are among them. At worst, some apps won't even close: KSysGuard is the only place to kill them. This bug introduces some very large desktop stability fluctuations.

-The installer instead of scanning the HD, should have an option in the boot menu to select NVIDIA. As for Intel, this is a source of pollution for AMD. Not very hard to do.

Kernel 5.6 stable should be out in just a few hours. If it has to reach the final build, it will be in Proposed this week. It was a perfect-stable cycle here.

ls /lib/modules
5.4.0-20-generic  5.6.0-050600rc7-generic

[Radcliff]

Kernel 5.6 Stable Enabling Synaptic History

As expected, the cycle was too stable for an 8th release candidate, Kernel 5.6 has reached the stable channel.

Enabling upgrade/update to restore history in Synaptic (Commit log/Reload Package Information).

Removing RC-7 that is still first in the boot sequence in Synaptic.

Commit Log for Mon Mar 30 11:08:11 2020

Completely removed the following packages:
linux-headers-5.6.0-050600rc7
linux-headers-5.6.0-050600rc7-generic
linux-image-unsigned-5.6.0-050600rc7-generic
linux-modules-5.6.0-050600rc7-generic

Upgraded the following packages:
fuse (2.9.9-2) to 2.9.9-3
glib-networking (2.64.0-1) to 2.64.1-1
glib-networking-common (2.64.0-1) to 2.64.1-1
glib-networking-services (2.64.0-1) to 2.64.1-1
libbluray2 (1:1.1.2-2) to 1:1.2.0-1
libfuse2 (2.9.9-2) to 2.9.9-3
libgtk3-perl (0.036-2) to 0.037-1
libnspr4 (2:4.24-1) to 2:4.25-1
libvolume-key1 (0.3.12-2ubuntu2) to 0.3.12-3.1
mtools (4.0.23-3) to 4.0.24-1

Reload Package Information: Enabling Synaptic History

Commit Log for Mon Mar 30 11:12:04 2020

Upgraded the following packages:
bsdmainutils (11.1.2ubuntu2) to 11.1.2ubuntu3
ca-certificates (20190110) to 20190110ubuntu1
fonts-noto-color-emoji (0~20180810-1.1) to 0~20191119-1
libasn1-8-heimdal (7.7.0+dfsg-1) to 7.7.0+dfsg-1ubuntu1
libdvdread7 (6.0.2-2) to 6.1.0-1
libgps26 (3.20-5ubuntu1) to 3.20-6
libgssapi3-heimdal (7.7.0+dfsg-1) to 7.7.0+dfsg-1ubuntu1
libhcrypto4-heimdal (7.7.0+dfsg-1) to 7.7.0+dfsg-1ubuntu1
libheimbase1-heimdal (7.7.0+dfsg-1) to 7.7.0+dfsg-1ubuntu1
libheimntlm0-heimdal (7.7.0+dfsg-1) to 7.7.0+dfsg-1ubuntu1
libhx509-5-heimdal (7.7.0+dfsg-1) to 7.7.0+dfsg-1ubuntu1
libjbig2dec0 (0.17-1) to 0.18-1ubuntu1
libkrb5-26-heimdal (7.7.0+dfsg-1) to 7.7.0+dfsg-1ubuntu1
libpsl5 (0.20.2-2) to 0.21.0-1
libroken18-heimdal (7.7.0+dfsg-1) to 7.7.0+dfsg-1ubuntu1
libsqlite3-0 (3.31.1-3) to 3.31.1-4
libwhoopsie-preferences0 (21) to 22
libwind0-heimdal (7.7.0+dfsg-1) to 7.7.0+dfsg-1ubuntu1
libxcb-composite0 (1.13.1-5build1) to 1.14-2
libxcb-damage0 (1.13.1-5build1) to 1.14-2
libxcb-dpms0 (1.13.1-5build1) to 1.14-2
libxcb-dri2-0 (1.13.1-5build1) to 1.14-2
libxcb-dri3-0 (1.13.1-5build1) to 1.14-2
libxcb-glx0 (1.13.1-5build1) to 1.14-2
libxcb-present0 (1.13.1-5build1) to 1.14-2
libxcb-randr0 (1.13.1-5build1) to 1.14-2
libxcb-record0 (1.13.1-5build1) to 1.14-2
libxcb-render0 (1.13.1-5build1) to 1.14-2
libxcb-res0 (1.13.1-5build1) to 1.14-2
libxcb-shape0 (1.13.1-5build1) to 1.14-2
libxcb-shm0 (1.13.1-5build1) to 1.14-2
libxcb-sync1 (1.13.1-5build1) to 1.14-2
libxcb-xfixes0 (1.13.1-5build1) to 1.14-2
libxcb-xinerama0 (1.13.1-5build1) to 1.14-2
libxcb-xinput0 (1.13.1-5build1) to 1.14-2
libxcb-xkb1 (1.13.1-5build1) to 1.14-2
libxcb-xv0 (1.13.1-5build1) to 1.14-2
libxcb1 (1.13.1-5build1) to 1.14-2
pci.ids (0.0~2020.01.25-1) to 0.0~2020.03.20-1
publicsuffix (20200201.2258-1) to 20200303.0012-1
python3-entrypoints (0.3-1build1) to 0.3-2ubuntu1
python3-ptyprocess (0.6.0-1build1) to 0.6.0-1ubuntu1
whoopsie-preferences (21) to 22
xdg-utils (1.1.3-1ubuntu2) to 1.1.3-2ubuntu1
xserver-xorg-video-qxl (0.1.5-2build3) to 0.1.5-2ubuntu2

uname -a
Linux ff 5.6.0-050600-generic #202003292333 SMP Sun Mar 29 23:35:58 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux

[GreyGeek]

Oh, nooozzz!
I saw 161 packages in the pipe today, made snapshots first, and then did the apt thing. I rebooted and the desktop appeared in its usual 11 seconds time. Since I saw a python update in the list I decided to check the Minecraft launcher. IT was MISSING! What'll I do during this isolation period? I downloaded the Minecraft.deb version from the Minecraft website and attempted to install it. The attempt failed.

The following packages have unmet dependencies:
minecraft-launcher : Depends: libpango1.0-0 (>= 1.14.0) but it is not installable
E: Unable to correct problems, you have held broken packages.

Checking the control file in the package:

Package: minecraft-launcher
[B]Version: 2.1.13086[/B]
Architecture: amd64
Maintainer: Petr Mrázek <petr@mojang.com>
Description: Official Minecraft Launcher
Homepage: https://minecraft.net/
Pre-Depends: dpkg (>= 1.14.0), wget | curl, ca-certificates
Depends: default-jre, gconf-service, libasound2 (>= 1.0.23), libatk1.0-0 (>= 1.12.4), libc6 (>= 2.11), libcairo2 (>= 1.6.0), libcups2 (>= 1.4.0), libdbus-1-3 (>= 1.1.4), libexpat1 (>= 1.95.8), libfontconfig1 (>= 2.8.0), libgcc1 (>= 1:4.1.1), libgconf-2-4 (>= 2.31.1), libgdk-pixbuf2.0-0 (>= 2.22.0), libglib2.0-0 (>= 2.26.0), libgtk2.0-0, libgtk-3-0 (>= 3.18.9), libnspr4 (>= 1.8.0.10), libnss3 (>= 3.17.2),[B] libpango1.0-0 (>= 1.14.0),[/B] libstdc++6 (>= 4.8.0), libx11-6 (>= 2:1.4.99.1), libxcomposite1 (>= 1:0.3-1), libxcursor1 (>> 1.1.2), libxdamage1 (>= 1:1.1), libxext6, libxfixes3, libxi6 (>= 2:1.2.99.4), libxrandr2 (>= 2:1.2.99.3), libxrender1, libxss1, libxtst6, libx11-xcb1, libxcb1, libbz2-1.0, lsb-base (>= 4.1), xdg-utils (>= 1.0.2), wget, libcurl3 | libcurl4
Copyright: All rights reserved

The installation attempt died at libpango, but I am not going through the other packages to see if the ones already installed are the correct version number.

It looks like I'll be playing Minecraft with MultiMC and the Fabric API until the java launcher can work again.

EDIT: I forgot to mention that my WINE apps, EKG and SpaceEngine-98.exe, continued to run nicely. So did Steam. In fact, I ran Castle Story for the first time since 2017 and it displayed nicely. Previously, the polygons which made up the landscape were disassembled by a few pixels along each border, making the game unplayable.