I recently noticed that in KDE Neon User Edition, the os-release information got overwritten by an update to the Ubuntu package base-files, i.e:

$ cat /etc/os-release
NAME="Ubuntu"
VERSION="18.04.1 LTS (Bionic Beaver)"
ID=ubuntu
ID_LIKE=debian
PRETTY_NAME="Ubuntu 18.04.1 LTS"
VERSION_ID="18.04"
HOME_URL="https://www.ubuntu.com/"
SUPPORT_URL="https://help.ubuntu.com/"
BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/"
PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy"
VERSION_CODENAME=bionic
UBUNTU_CODENAME=bionic

Does anyone know what happened to the latest bionic user edition build (2018-08-23) ?

According to OpenQA (https://build.neon.kde.org/view/openqa%20%E2%9B%91/job/openqa_bionic_useredition_installation/), the installation test failed. However i could install it properly on virtualbox 5.2.18.

It still seems to be there:

https://files.kde.org/neon/images/bioni ... n/current/

catweazel wrote:[code]System: Host: AX370 Kernel: 4.15.0-30-lowlatency x86_64 bits: 64 compiler: gcc v: 7.3.0
Brilliant. Not a single hiccup. Thank you to everyone who put in so much hard work.

Just a quick update. I've now been running this for 16 days as my daily driver and it's been major problem free. The only things I've had trouble with are:

1) Discover seems to hang on updates and I have to pkill it, then it runs ok on the next execution. I don't believe this is a problem with the base.

2) Kpat game solver goes into a multi-threaded storm of CPU use while playing Klondike. I also don't believe this to be a problem with the base, and that it was introduced in a recent update.

All in all, an excellent user experience.

I just installed Bionic on a second computer, my laptop, replacing the 5.12.5 LTS. I Installed all my programs, and everything is running very smooth and no glitches to report. I just hope I don’t run into any issue with Dropbox syncing after November 7, 2018! They’re saying I need to move the Dropbox folder to an EXT4 drive.
Dropbox supports encryption systems, such as LUKS, but not Ecrypfts. I encrypted the hard drive through the system encryption, so I’m assuming it is Luks, and therefore I should be okay?
Job well done Neon team. Thank you.

I've been dual booting the user edition & LTS user edition for over a week now. Must say , great job.
My only observations now are these.
The LTS edition seems slightly more responsive than the user edition.
Also both editions after login are fairly slow to connect to WiFi. The LTS edition takes about 10 Seconds. Previous edition was immediate.

I'm using User Edition with Plasma rolling and I can't complain.

I confirm what "catweazel" posted. Discover hangs during update. I I've never noticed that before, because I never use Discover for updating the system. I always use the terminal. There was one update today, and I tried to use Discover, and it didn't work as it was hanging, so I used the terminal and updated successfully.

Installer crashed while I was using the manual partitioning. I had just deleted and recreated a ext4 partition and it crashed. Unable to submit error report.

neon-useredition-20180823-0538-amd64.iso

Code: Select all

Traceback (most recent call last):
  File "/usr/lib/ubiquity/ubiquity/frontend/kde_components/PartitionModel.py", line 66, in setData
    item.partman_column_format_toggled(value.toBool())
AttributeError: 'int' object has no attribute 'toBool'

Screenshot: https://i.imgur.com/QvYiyGE.png

EDIT: Two more things
1) I'm not sure if this is intended or not, but Konsole doesn't have any graphic styling applied to it by default. Just the default color profile. It's been a good year+ since I've used Neon so I can't remember if it had any default styling out of the box.
2) No calculator tool is provided in the user edition. I believe it should

First problem since last (and only) post. The following is a reconstruction and not a copy and paste from terminal output:

pkcon refresh
pkcon get-updates
pkcon update -y

All was going swimmingly. I was doing something else then went back to the terminal and saw that the process had ended and I was back at the prompt.
The process had ceased with a message similar to this:

Code: Select all

(72%) The daemon crashed mid-transaction!

Anybody else get this?
Do you know how to recover from it?

cheers

scrawfuela wrote:Anybody else get this?
Do you know how to recover from it?

Yes, seems it is packagekit falling over itself trying to update it's own packages.

If you now try to do anything with pkcon or apt, you will likely see this message:

E: dpkg was interrupted, you must manually run 'sudo dpkg --configure -a' to correct the problem.

Do that on the command line, and the new packagekit packages should get finished setting up, after which all should in theory be fine.

scrawfuela wrote:

Code: Select all

(72%) The daemon crashed mid-transaction!

Reported as:

https://bugs.launchpad.net/ubuntu/+sour ... ug/1790613

Yes, seems it is packagekit falling over itself trying to update it's own packages.

If you now try to do anything with pkcon or apt, you will likely see this message:

E: dpkg was interrupted, you must manually run 'sudo dpkg --configure -a' to correct the problem.

Do that on the command line, and the new packagekit packages should get finished setting up, after which all should in theory be fine.

Did that just now and all is well - so the theory is good
Thanks for that and for posting a bug report.

cheers

Thanks for the heads-up

https://bugs.launchpad.net/ubuntu/+sour ... ug/1790613

Unfortunate. That's why I don't use PackageKit.

Alternative: use APT. sudo apt update followed by sudo apt full-upgrade