![]() Registered Member ![]()
|
Some were saying that we should see the new Neon release once 18.04 received its first major bug fix.. |
![]() KDE Developer ![]()
|
It will end up that way it seems, but it's not dependant on it.
The state of the Neon user repo and iso is the overriding concern. |
![]() Registered Member ![]()
|
I still have a problem with localization, does not accept localization into my native language. Does this manually made version of git-stable somehow translate into the legal user test version. I made a live USB with legal test user iso, how much I see bionic sources.lista is reduced compared to xenial, neon.list has no limit [arch = amd64]
|
![]() Registered Member ![]()
|
I had a major problem after the upgrade: The package 'ecryptfs-utils' had been removed, so I had to reinstall it from a non-encrypted user account before I could log in to my default, encrypted, user account.
Also, the boot process is noticeably longer. It gets stuck for ~30 seconds while displaying the message 'Begin: Running /scripts/local-pre-mount …' |
![]() Registered Member ![]()
|
My upgrade to 18.04 was successful, except for two issues:
1. Every time I login, I get the following notification, which also shows up in my Yakuake terminal:
Running "service apcupsd status" gives the following output:
I haven't touched my UPS setup, and I can't figure out what would have changed to cause communication issues with the device. 2. I can't install "winehq-devel" from the Wine PPA due to dependency issues. It seems that the newer version of libblkid1 in the Neon repository might be to blame? It appears that apt chokes on trying to install libblkid1:i386:
Perhaps related, apt also throws the following error every time I check for updates:
Unfortunately, Google has been of little help trying to get to the bottom of either of these issues. I'll investigate more later, but right now it is 2 am and my brain is fried. |
![]() Registered Member ![]()
|
When have Google and the internet become synonyms? I google for this, I google for that ![]()
Proud to be powered by Plasma
|
![]() KDE Developer ![]()
|
Because Neon doesn't build or support i386. |
![]() Registered Member ![]()
|
Hi,
Now you could upgrade from 16.04 to 18.04 testing following the instructions posted here: https://blog.neon.kde.org/index.php/201 ... r-testing/ Regards, |
![]() Registered Member ![]()
|
Tried the upgrade yesterday and everything seemed to go well until the system restarted. I was left with no audio devices recognized and no way to repair it. Luckily I had made an image of the Xenial system using Clonezilla (just in case) and restored using it. While I am indeed looking forward to the Bionic base I think once it is released as "stable" I will do a fresh install. Thanks for all the hard work but I am still in "wait until stable" mode.
|
![]() Registered Member ![]()
|
18.04 here.
→is this normal? i think it's related to update: https://i.imgur.com/0yZPNAX.png (49 processes called like this + 48 „python 3” (gives me 100% cpu at boot)) →commands like sudo hdparm -B 254 /dev/sda don't have any effect after upgrade. before it worked fine, now is completely ignored. (sry if it's not neon related) →i also had problems with wifi (adapter name changed to some long name instead of wlan0) so it stopped working at boot (had to enable manually). there were more minor issues with systemd related stuff, but i took them down before realized it's worth mentioning here. |
![]() Registered Member ![]()
|
@kdeoldster,
The problem is resolved easily, needs to be deleted in the home .config pulse dir and restart the machine |
![]() Registered Member ![]()
|
It is difficult here ...
I began like here : https://community.kde.org/Neon/BionicUpgrades I saw the release note as in 4) Do not remember why I was not ready, no more time for that this day, wanted to check a backup or whaterver, I cliked on Cancel. I Hoped it would be easy to come back at this point on the wright moment. I did no saw how, the days have passed, and once, at startup I had the opportunity to see the notification on 3) Unfortunately during the process a problem of disk space appeared. Some more chekings, I solved that by growing partition. I am steel on xenial today, and still want to go to bionic. I do not know How to make 3) and 4) appear again. Trying the command line it gives : I unactivate all in /etc/apt/sources.list.d/ (expept neon) and then :
What should I do now ? |
![]() Registered Member ![]()
|
|
![]() Registered Member ![]()
|
Hi,
Did you try the following command from the terminal console? do-release-upgrade Hope it help |
![]() Registered Member ![]()
|
thanks to you, yes, I just tried.
The result is disappointing, here it is.
I had to go by this way too : https://askubuntu.com/questions/1008974 ... not-usable It is on process now, hope it'll be right and finish well ! |
Registered users: Bing [Bot], claydoh, Google [Bot], rblackwell, Yahoo [Bot]