Reply to topic

Kde Neon upgrade to 18.04

k4ever
Registered Member
Posts
15
Karma
0

Re: Kde Neon upgrade to 18.04

Thu Aug 02, 2018 1:31 pm
acheronuk wrote:
k4ever wrote:Are we ever going to see the 18.04 upgrade for KDE Neon? It's going on 4 months.


Yes, but see:

https://jriddell.org/2018/07/26/kde-neon-bionic-update/

Read, thanks!

k4ever wrote:18.04.1 has already been released..


Nice, but that doesn't impact very much whether a Neon -> Neon upgrade is QA'd well enough to be recommended and turned on.


Some were saying that we should see the new Neon release once 18.04 received its first major bug fix..
User avatar acheronuk
KDE Developer
Posts
70
Karma
1

Re: Kde Neon upgrade to 18.04

Thu Aug 02, 2018 1:59 pm
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.
User avatar alideda
Registered Member
Posts
126
Karma
0
OS

Re: Kde Neon upgrade to 18.04

Fri Aug 10, 2018 10:50 am
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]
oysteins
Registered Member
Posts
6
Karma
0

Re: Kde Neon upgrade to 18.04

Wed Aug 22, 2018 4:53 pm
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 …'
User avatar mrbumpy409
Registered Member
Posts
11
Karma
0
OS

Re: Kde Neon upgrade to 18.04

Thu Sep 06, 2018 7:07 am
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:
Broadcast message from root@mypc (somewhere) (Wed Sep 5 23:59:16 2018):
Warning communications lost with UPS

Running "service apcupsd status" gives the following output:
Sep 05 23:44:00 mypc systemd[1]: Starting UPS power management daemon...
Sep 05 23:44:01 mypc systemd[1]: apcupsd.service: Can't open PID file /var/run/apcupsd.pid (yet?) after start: No such file or directory
Sep 05 23:44:01 mypc apcupsd[1280]: apcupsd 3.14.14 (31 May 2016) debian startup succeeded
Sep 05 23:44:01 mypc apcupsd[1280]: NIS server startup succeeded
Sep 05 23:44:01 mypc systemd[1]: Started UPS power management daemon.
Sep 05 23:45:12 mypc apcupsd[1280]: Communications with UPS lost.

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:
Starting pkgProblemResolver with broken count: 1
Starting 2 pkgProblemResolver with broken count: 1
Investigating (0) libmount1:i386 < none -> 2.31.1-0.4ubuntu3.1 @un uN Ib >
Broken libmount1:i386 Depends on libblkid1:i386 < none | 2.31.1-0.4ubuntu3.1 @un uH > (>= 2.17.2)
Considering libblkid1:i386 0 as a solution to libmount1:i386 10
Holding Back libmount1:i386 rather than change libblkid1:i386
Investigating (0) libglib2.0-0:i386 < none -> 2.56.1-2ubuntu1 @rc uN Ib >
Broken libglib2.0-0:i386 Depends on libmount1:i386 < none | 2.31.1-0.4ubuntu3.1 @un uH > (>= 2.19.1)
Considering libmount1:i386 10 as a solution to libglib2.0-0:i386 9
Holding Back libglib2.0-0:i386 rather than change libmount1:i386
Investigating (0) libgstreamer1.0-0:i386 < none -> 1.14.1-1~ubuntu18.04.1 @un uN Ib >
Broken libgstreamer1.0-0:i386 Depends on libglib2.0-0:i386 < none | 2.56.1-2ubuntu1 @rc uH > (>= 2.41.1)
Considering libglib2.0-0:i386 9 as a solution to libgstreamer1.0-0:i386 3
Holding Back libgstreamer1.0-0:i386 rather than change libglib2.0-0:i386
Investigating (0) libgstreamer-plugins-base1.0-0:i386 < none -> 1.14.1-1ubuntu1~ubuntu18.04.1 @un uN Ib >
Broken libgstreamer-plugins-base1.0-0:i386 Depends on libglib2.0-0:i386 < none | 2.56.1-2ubuntu1 @rc uH > (>= 2.40)
Considering libglib2.0-0:i386 9 as a solution to libgstreamer-plugins-base1.0-0:i386 1
Holding Back libgstreamer-plugins-base1.0-0:i386 rather than change libglib2.0-0:i386
Investigating (0) gstreamer1.0-plugins-base:i386 < none -> 1.14.1-1ubuntu1~ubuntu18.04.1 @un uN Ib >
Broken gstreamer1.0-plugins-base:i386 Depends on libglib2.0-0:i386 < none | 2.56.1-2ubuntu1 @rc uH > (>= 2.40)
Considering libglib2.0-0:i386 9 as a solution to gstreamer1.0-plugins-base:i386 1
Holding Back gstreamer1.0-plugins-base:i386 rather than change libglib2.0-0:i386
Investigating (0) wine-devel-i386:i386 < none -> 3.15.0~bionic @un uN Ib >
Broken wine-devel-i386:i386 Depends on libglib2.0-0:i386 < none | 2.56.1-2ubuntu1 @rc uH > (>= 2.12.0)
Considering libglib2.0-0:i386 9 as a solution to wine-devel-i386:i386 -1
Holding Back wine-devel-i386:i386 rather than change libglib2.0-0:i386
Investigating (1) wine-devel:amd64 < none -> 3.15.0~bionic @un uN Ib >
Broken wine-devel:amd64 Depends on wine-devel-i386:amd64 < none @un H > (= 3.15.0~bionic)
Considering wine-devel-i386:i386 -1 as a solution to wine-devel:amd64 0
Holding Back wine-devel:amd64 rather than change wine-devel-i386:amd64
Investigating (2) winehq-devel:amd64 < none -> 3.15.0~bionic @un puN Ib >
Broken winehq-devel:amd64 Depends on wine-devel:amd64 < none | 3.15.0~bionic @un uH > (= 3.15.0~bionic)
Considering wine-devel:amd64 0 as a solution to winehq-devel:amd64 9999
Reinst Failed because of libblkid1:i386
Reinst Failed because of libmount1:i386
Reinst Failed because of libglib2.0-0:i386
Reinst Failed because of wine-devel-i386:i386
Considering wine-devel:i386 -1 as a solution to winehq-devel:amd64 9999
Reinst Failed because of wine-devel-i386:i386
Done

Perhaps related, apt also throws the following error every time I check for updates:
N: Skipping acquire of configured file 'main/binary-i386/Packages' as repository 'http://archive.neon.kde.org/user bionic InRelease' doesn't support architecture 'i386'

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.
raddison
Registered Member
Posts
512
Karma
0

Re: Kde Neon upgrade to 18.04

Thu Sep 06, 2018 3:40 pm
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.


When have Google and the internet become synonyms? I google for this, I google for that ;D


Proud to be powered by Plasma
User avatar acheronuk
KDE Developer
Posts
70
Karma
1

Re: Kde Neon upgrade to 18.04

Thu Sep 06, 2018 4:00 pm
mrbumpy409 wrote: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:
N: Skipping acquire of configured file 'main/binary-i386/Packages' as repository 'http://archive.neon.kde.org/user bionic InRelease' doesn't support architecture 'i386'

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.


Because Neon doesn't build or support i386.
j8a
Registered Member
Posts
110
Karma
0
OS

Re: Kde Neon upgrade to 18.04

Thu Sep 06, 2018 5:30 pm
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,
User avatar kdeoldster
Registered Member
Posts
29
Karma
0
OS

Re: Kde Neon upgrade to 18.04

Thu Sep 06, 2018 5:48 pm
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.
aleksander
Registered Member
Posts
4
Karma
0

Re: Kde Neon upgrade to 18.04

Wed Sep 12, 2018 2:48 pm
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.
User avatar alideda
Registered Member
Posts
126
Karma
0
OS

Re: Kde Neon upgrade to 18.04

Wed Sep 12, 2018 9:38 pm
@kdeoldster,
The problem is resolved easily, needs to be deleted in the home .config pulse dir and restart the machine
livier
Registered Member
Posts
6
Karma
0

Re: Kde Neon upgrade to 18.04

Sun Dec 02, 2018 8:20 pm
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 :

Code: Select all
$ sudo pkcon refresh
[sudo] Mot de passe de ------- :
Actualisation du cache        [=========================]         
Chargement du cache           [=========================]         
Mise à jour de la liste des logiciels[=========================]         
Téléchargement des paquets  [=========================]         
Exécution                    [=========================]         
Terminé                      [=========================]         
 Activé                              http://archive.canonical.com/ubuntu xenial InRelease
 Activé                              http://ca.archive.ubuntu.com/ubuntu xenial InRelease

$ sudo pkcon update
Obtention des mises à jour   [=========================]         
Terminé                      [=========================]         
Aucune mise à jour de paquet vers une nouvelle version n'est requise.


What should I do now ?
livier
Registered Member
Posts
6
Karma
0

Re: Kde Neon upgrade to 18.04

Fri Dec 07, 2018 6:17 am
up ???

Is there anything wrong in my question ?
j8a
Registered Member
Posts
110
Karma
0
OS

Re: Kde Neon upgrade to 18.04

Fri Dec 07, 2018 8:51 pm
Hi,
Did you try the following command from the terminal console?
do-release-upgrade

Hope it help
livier
Registered Member
Posts
6
Karma
0

Re: Kde Neon upgrade to 18.04

Sat Dec 08, 2018 5:09 pm
thanks to you, yes, I just tried.
The result is disappointing, here it is.

Code: Select all
$ sudo do-release-upgrade
Recherche d'une nouvelle version d'Ubuntu
Votre version d'Ubuntu n'est plus prise en charge.
Pour plus d'informations sur la mise à jour, veuillez visiter :
http://www.ubuntu.com/releaseendoflife

Prendre :1 Signature de l'outil de mise à niveau [819 B]                                                                                           
Prendre :2 Outil de mise à niveau [1 254 kB]                                                                                                       
1 255 k o réceptionnés en 6s (103 k o/s)                                                                                                           
authentification de « bionic.tar.gz » avec « bionic.tar.gz.gpg »
extraction de 'bionic.tar.gz'

Lecture du cache

Vérification du gestionnaire de paquets
Lecture des listes de paquets… Terminé
Construction de l'arbre des dépendances       
Lecture des informations d'état… Terminé     
Prendre :1 http://security.ubuntu.com/ubuntu xenial-security InRelease [107 kB]                                                                     
Att http://archive.canonical.com/ubuntu xenial InRelease                                                                                           
Att http://ca.archive.ubuntu.com/ubuntu xenial InRelease                                                                                           
Prendre :2 http://ca.archive.ubuntu.com/ubuntu xenial-updates InRelease [109 kB]                                                                   
Prendre :3 http://archive.neon.kde.org/user xenial InRelease [34,7 kB]                                                                             
Prendre :4 http://ca.archive.ubuntu.com/ubuntu xenial-backports InRelease [107 kB]                                                                 
358 k o réceptionnés en 0s (0  o/s)                                                                                                                 
Lecture des listes de paquets… Terminé       
Construction de l'arbre des dépendances       
Lecture des informations d'état… Terminé     

Mise à jour des informations sur les dépôts
Att http://archive.canonical.com/ubuntu bionic InRelease                                                                                           
Att http://ca.archive.ubuntu.com/ubuntu bionic InRelease                                                                                           
Att http://security.ubuntu.com/ubuntu bionic-security InRelease                                                                                     
Prendre :1 http://archive.neon.kde.org/user bionic InRelease [19,0 kB]                                                                             
Att http://ca.archive.ubuntu.com/ubuntu bionic-updates InRelease                                                                                   
Att http://ca.archive.ubuntu.com/ubuntu bionic-backports InRelease                                                                                 
19,0 k o réceptionnés en 0s (0  o/s)                                                                                                               

Vérification du gestionnaire de paquets
Lecture des listes de paquets… Terminé       
Construction de l'arbre des dépendances       
Lecture des informations d'état… Terminé     

Calcul des modifications en cours

Calcul des modifications en cours

EFI System Partition (ESP) not usable

Your EFI System Partition (ESP) is not mounted at /boot/efi. Please
ensure that it is properly configured and try again.


Restauration du système dans son état d'origine

Annulation
Lecture des listes de paquets… Terminé       
Construction de l'arbre des dépendances       
Lecture des informations d'état… Terminé   


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 !

 
Reply to topic

Bookmarks



Who is online

Registered users: Baidu [Spider], Bing [Bot], Exabot [Bot], Google [Bot], rbreu, Sogou [Bot], yankoarebalo