This forum has been archived. All content is frozen. Please use KDE Discuss instead.

KDE neon rebease on Ubuntu 22.04 Now Available

Tags: update issues update issues update issues
(comma "," separated)
asiantuntia
Registered Member
Posts
1
Karma
0
I cant even install the update. It says:
"Checking for a new neon release
Please install all available updates for your release before upgrading."

"sudo pkcon update" has no updates

Running "sudo pkcon upgrade-system" it says:

Getting system upgrades [ ] (0%)
(pkcon:115372): GLib-CRITICAL **: 14:24:45.393: g_variant_new_string: assertion 'string != NULL' failed
[=========================]
Finished [=========================]
Getting system upgrades [ ] (0%)
(pkcon:115372): GLib-CRITICAL **: 14:24:45.401: g_variant_new_string: assertion 'string != NULL' failed
[=========================]
Finished [=========================]
Fatal error: UpgradeSystem not supported by backend

Discovery finds no updates
jwt873
Registered Member
Posts
35
Karma
0
My only bug was with some hard drives.

I had a three drives with just one partition called EXT, NTSF, and Movies. After the update, the old names remained, but the drives were re-assigned as EXT1, NTSF1 and Movies1. No big deal.. I had to modify a few shortcuts and a backup script.

Below was my /media/~ after the upgrade.

Code: Select all
drwx------  2 root root  4096 Oct 24 09:11 EXT/
drwxrwxrwx  8 jim  jim   4096 Nov  5  2018 EXT1/
drwx------  2 root root  4096 Oct 24 09:12 Movies/
drwxrwxrwx  1 jim  jim  20480 Feb 22  2022 Movies1/
drwxr-xr-x  2 root root  4096 Oct 24 09:11 NTFS/
drwxrwxrwx  1 jim  jim   4096 Nov 21  2017 NTFS1/
jim@linux:/media/jim$
User avatar
Mace68
Registered Member
Posts
23
Karma
0
OS
I need to do a clean install instead of updating. Is there a guide on the best way to do that while retaining most, if not all, of my settings (including main system settings)?
lnxusr
Registered Member
Posts
13
Karma
0
OS
Mace68 wrote:I need to do a clean install instead of updating. Is there a guide on the best way to do that while retaining most, if not all, of my settings (including main system settings)?


Just save everything in your home directory. The best way to do that is to keep /home on a separate partition, or better yet, its own drive.


KDE neon 5.26 Plasma: 5.26.0, Frameworks: 5.99.0, Qt: 5.15.6, Kernel: 5.15.0-52-generic (64-bit), X11 on Ryzen 7 3800X and AMD Radeon RX 5600 XT
duns
Registered Member
Posts
78
Karma
0
OS
same problem as lnxusr (same messages): no way to upgrade :-\
User avatar
boospy007
Registered Member
Posts
237
Karma
0
OS
KDE NEON Installer for optimisation updated:
https://git.osit.cc/public-projects/kde-neon-installer

Have Fun :)
lnxusr
Registered Member
Posts
13
Karma
0
OS
boospy007 wrote:KDE NEON Installer for optimisation updated:
https://git.osit.cc/public-projects/kde-neon-installer

Have Fun :)


That link times out for me.


KDE neon 5.26 Plasma: 5.26.0, Frameworks: 5.99.0, Qt: 5.15.6, Kernel: 5.15.0-52-generic (64-bit), X11 on Ryzen 7 3800X and AMD Radeon RX 5600 XT
User avatar
boospy007
Registered Member
Posts
237
Karma
0
OS
lnxusr wrote:
boospy007 wrote:KDE NEON Installer for optimisation updated:
https://git.osit.cc/public-projects/kde-neon-installer

Have Fun :)


That link times out for me.


Thanks for your feedback. Geoblocker was active. Can you test it again, please?
lnxusr
Registered Member
Posts
13
Karma
0
OS
boospy007 wrote:
lnxusr wrote:
boospy007 wrote:KDE NEON Installer for optimisation updated:
https://git.osit.cc/public-projects/kde-neon-installer

Have Fun :)


That link times out for me.


Thanks for your feedback. Geoblocker was active. Can you test it again, please?


Working now.


KDE neon 5.26 Plasma: 5.26.0, Frameworks: 5.99.0, Qt: 5.15.6, Kernel: 5.15.0-52-generic (64-bit), X11 on Ryzen 7 3800X and AMD Radeon RX 5600 XT
grooveman
Registered Member
Posts
54
Karma
0
Still not working for me... I've been beating my head agains this for days now... something has changed in the way networking is done that is affecting my vms... they cannot connect to the network. I have my bridge set up, I have my tap device, and I've tried every permutation of network configuration I could find in all my googlings... I have tried virtio and e1000 emulation...

Is there any documentation on the changes made to either the networking and/or the way qemu handles its ties to a tap/bridge device?
grooveman
Registered Member
Posts
54
Karma
0
I still do no know why bridge/tap issues persist under this version of Ubuntu base...

But I got around the problem by using a macvtap device in my qemu vm instead of a traditional bridge/tap device. My Windows vm would not let go of the old mac address (which was weird) until I booted into safe mode, then it finally let it go, and took the vtap mac address. Since this is the only thing I was using a tap/bridge for on this system, i can live with this.

Hope it helps if someone else bumps into the same issue.
Drizzt321
Registered Member
Posts
29
Karma
0
I can't update, says I need to install all available updates first. Unfortunately I can't get them all to install. I keep getting this:

Code: Select all
# pkcon update
Getting updates               [=========================]         
Finished                      [=========================]         
Loading cache                 [=========================]         
Testing changes               [=========================]         
Finished                      [                         ] (0%) 
The following packages have to be updated:
 grub-theme-breeze-5.26.0-0xneon+20.04+focal+release+build52.amd64      Breeze theme for Grub 2
Proceed with changes? [N/y] y

                              [=========================]         
Updating packages             [=========================]         
Loading cache                 [=========================]         
Running                       [=========================]         
Finished                      [=========================]         
Fatal error: Error while installing package: unable to make backup link of './boot/grub/themes/breeze/progress_bar2_c.png' before installing new version
mewcrazy
Registered Member
Posts
9
Karma
0
I received new updates today. Are they good to install? Seems like they come from the jammy package. I already tried updating them all, but it threw me an error:

Image
User avatar
daret
Registered Member
Posts
21
Karma
0
Sentinel wrote:Failed:
installed grub-efi-amd64-signed package post-installation script subprocess returned error exit status 32
installed grub-efi-amd64-signed package post-installation script subprocess returned error exit status 32


Upgrade script aborted at the end of installation phase.


Try to run
Code: Select all
sudo dpkg --configure -a
User avatar
boospy007
Registered Member
Posts
237
Karma
0
OS
Upgrade ok, but libssl1.1 can't be removed because dependence problem.

Code: Select all
apt remove libssl1.1         
Paketlisten werden gelesen… Fertig
Abhängigkeitsbaum wird aufgebaut… Fertig
Statusinformationen werden eingelesen… Fertig
Starting pkgProblemResolver with broken count: 1
Starting 2 pkgProblemResolver with broken count: 1
Investigating (0) libruby2.7:amd64 < 2.7.0-5ubuntu1.7 @ii K Ib >
Broken libruby2.7:amd64 Hängt ab von on libssl1.1:amd64 < 1.1.1f-1ubuntu2.16 @ii pR > (>= 1.1.1)
  Considering libssl1.1:amd64 10000 as a solution to libruby2.7:amd64 -1
  Removing libruby2.7:amd64 rather than change libssl1.1:amd64
Investigating (1) ruby-xmlrpc:amd64 < 0.3.2-1ubuntu0.1 @ii K Ib >
Broken ruby-xmlrpc:amd64 Hängt ab von on ruby-webrick:amd64 < none | 1.7.0-3 @un uH >
  Considering ruby-webrick:amd64 1 as a solution to ruby-xmlrpc:amd64 3
  Added ruby-webrick:amd64 to the remove list
  Fixing ruby-xmlrpc:amd64 via keep of ruby-webrick:amd64
Investigating (2) ruby-xmlrpc:amd64 < 0.3.2-1ubuntu0.1 @ii K Ib >
Broken ruby-xmlrpc:amd64 Hängt ab von on ruby-webrick:amd64 < none | 1.7.0-3 @un uH >
  Considering ruby-webrick:amd64 1 as a solution to ruby-xmlrpc:amd64 3
  Added ruby-webrick:amd64 to the remove list
  Fixing ruby-xmlrpc:amd64 via keep of ruby-webrick:amd64
Investigating (3) ruby-xmlrpc:amd64 < 0.3.2-1ubuntu0.1 @ii K Ib >
Broken ruby-xmlrpc:amd64 Hängt ab von on ruby-webrick:amd64 < none | 1.7.0-3 @un uH >
  Considering ruby-webrick:amd64 3 as a solution to ruby-xmlrpc:amd64 3
  Removing ruby-xmlrpc:amd64 rather than change ruby-webrick:amd64
Investigating (3) libruby3.0:amd64 < 3.0.2-7ubuntu2.1 @ii K Ib >
Broken libruby3.0:amd64 Hängt ab von on ruby-xmlrpc:amd64 < 0.3.2-1ubuntu0.1 @ii R > (>= 0.3.0~)
  Considering ruby-xmlrpc:amd64 3 as a solution to libruby3.0:amd64 2
  Removing libruby3.0:amd64 rather than change ruby-xmlrpc:amd64
Investigating (4) ruby3.0:amd64 < 3.0.2-7ubuntu2.1 @ii K Ib >
Broken ruby3.0:amd64 Hängt ab von on libruby3.0:amd64 < 3.0.2-7ubuntu2.1 @ii R > (>= 3.0.0~preview1)
  Considering libruby3.0:amd64 3 as a solution to ruby3.0:amd64 5
  Added libruby3.0:amd64 to the remove list
  Fixing ruby3.0:amd64 via keep of libruby3.0:amd64
Investigating (4) libruby3.0:amd64 < 3.0.2-7ubuntu2.1 @ii K Ib >
Broken libruby3.0:amd64 Hängt ab von on ruby-xmlrpc:amd64 < 0.3.2-1ubuntu0.1 @ii R > (>= 0.3.0~)
  Considering ruby-xmlrpc:amd64 3 as a solution to libruby3.0:amd64 5
  Added ruby-xmlrpc:amd64 to the remove list
  Fixing libruby3.0:amd64 via keep of ruby-xmlrpc:amd64
Investigating (5) ruby-xmlrpc:amd64 < 0.3.2-1ubuntu0.1 @ii K Ib >
Broken ruby-xmlrpc:amd64 Hängt ab von on ruby-webrick:amd64 < none | 1.7.0-3 @un uH >
  Considering ruby-webrick:amd64 3 as a solution to ruby-xmlrpc:amd64 5
  Added ruby-webrick:amd64 to the remove list
  Fixing ruby-xmlrpc:amd64 via keep of ruby-webrick:amd64
Investigating (6) ruby-xmlrpc:amd64 < 0.3.2-1ubuntu0.1 @ii K Ib >
Broken ruby-xmlrpc:amd64 Hängt ab von on ruby-webrick:amd64 < none | 1.7.0-3 @un uH >
  Considering ruby-webrick:amd64 5 as a solution to ruby-xmlrpc:amd64 5
  Removing ruby-xmlrpc:amd64 rather than change ruby-webrick:amd64
Investigating (6) libruby3.0:amd64 < 3.0.2-7ubuntu2.1 @ii K Ib >
Broken libruby3.0:amd64 Hängt ab von on ruby-xmlrpc:amd64 < 0.3.2-1ubuntu0.1 @ii R > (>= 0.3.0~)
  Considering ruby-xmlrpc:amd64 5 as a solution to libruby3.0:amd64 5
  Removing libruby3.0:amd64 rather than change ruby-xmlrpc:amd64
Investigating (7) ruby3.0:amd64 < 3.0.2-7ubuntu2.1 @ii K Ib >
Broken ruby3.0:amd64 Hängt ab von on libruby3.0:amd64 < 3.0.2-7ubuntu2.1 @ii R > (>= 3.0.0~preview1)
  Considering libruby3.0:amd64 5 as a solution to ruby3.0:amd64 5
  Removing ruby3.0:amd64 rather than change libruby3.0:amd64
Investigating (8) ruby:amd64 < 1:3.0~exp1 @ii K Ib >
Broken ruby:amd64 Hängt ab von on ruby3.0:amd64 < 3.0.2-7ubuntu2.1 @ii R >
  Considering ruby3.0:amd64 5 as a solution to ruby:amd64 112
  Added ruby3.0:amd64 to the remove list
  Fixing ruby:amd64 via keep of ruby3.0:amd64
Investigating (8) ruby3.0:amd64 < 3.0.2-7ubuntu2.1 @ii K Ib >
Broken ruby3.0:amd64 Hängt ab von on libruby3.0:amd64 < 3.0.2-7ubuntu2.1 @ii R > (>= 3.0.0~preview1)
  Considering libruby3.0:amd64 5 as a solution to ruby3.0:amd64 112
  Added libruby3.0:amd64 to the remove list
  Fixing ruby3.0:amd64 via keep of libruby3.0:amd64
Investigating (8) libruby3.0:amd64 < 3.0.2-7ubuntu2.1 @ii K Ib >
Broken libruby3.0:amd64 Hängt ab von on ruby-xmlrpc:amd64 < 0.3.2-1ubuntu0.1 @ii R > (>= 0.3.0~)
  Considering ruby-xmlrpc:amd64 5 as a solution to libruby3.0:amd64 112
  Added ruby-xmlrpc:amd64 to the remove list
  Fixing libruby3.0:amd64 via keep of ruby-xmlrpc:amd64
Investigating (9) ruby-xmlrpc:amd64 < 0.3.2-1ubuntu0.1 @ii K Ib >
Broken ruby-xmlrpc:amd64 Hängt ab von on ruby-webrick:amd64 < none | 1.7.0-3 @un uH >
  Considering ruby-webrick:amd64 5 as a solution to ruby-xmlrpc:amd64 112
  Added ruby-webrick:amd64 to the remove list
  Fixing ruby-xmlrpc:amd64 via keep of ruby-webrick:amd64
Investigating (10) ruby-xmlrpc:amd64 < 0.3.2-1ubuntu0.1 @ii K Ib >
Broken ruby-xmlrpc:amd64 Hängt ab von on ruby-webrick:amd64 < none | 1.7.0-3 @un uH >
  Considering ruby-webrick:amd64 112 as a solution to ruby-xmlrpc:amd64 112
  Removing ruby-xmlrpc:amd64 rather than change ruby-webrick:amd64
Investigating (10) libruby3.0:amd64 < 3.0.2-7ubuntu2.1 @ii K Ib >
Broken libruby3.0:amd64 Hängt ab von on ruby-xmlrpc:amd64 < 0.3.2-1ubuntu0.1 @ii R > (>= 0.3.0~)
  Considering ruby-xmlrpc:amd64 112 as a solution to libruby3.0:amd64 112
  Removing libruby3.0:amd64 rather than change ruby-xmlrpc:amd64
Investigating (11) ruby3.0:amd64 < 3.0.2-7ubuntu2.1 @ii K Ib >
Broken ruby3.0:amd64 Hängt ab von on libruby3.0:amd64 < 3.0.2-7ubuntu2.1 @ii R > (>= 3.0.0~preview1)
  Considering libruby3.0:amd64 112 as a solution to ruby3.0:amd64 112
  Removing ruby3.0:amd64 rather than change libruby3.0:amd64
Investigating (12) ruby:amd64 < 1:3.0~exp1 @ii K Ib >
Broken ruby:amd64 Hängt ab von on ruby3.0:amd64 < 3.0.2-7ubuntu2.1 @ii R >
  Considering ruby3.0:amd64 112 as a solution to ruby:amd64 112
  Removing ruby:amd64 rather than change ruby3.0:amd64
Investigating (12) ruby-rubygems:amd64 < 3.3.5-2 @ii K Ib >
Broken ruby-rubygems:amd64 Hängt ab von on ruby:any:any < none @un H >
  Considering ruby:i386 -1 as a solution to ruby-rubygems:amd64 5
  Added ruby:i386 to the remove list
  Fixing ruby-rubygems:amd64 via keep of ruby:i386
Investigating (12) rake:amd64 < 13.0.6-2 @ii K Ib >
Broken rake:amd64 Hängt ab von on ruby:any:any < none @un H >
  Considering ruby:i386 5 as a solution to rake:amd64 3
  Removing rake:amd64 rather than change ruby:any:any
Investigating (13) neon-settings-2:amd64 < 0.4+p22.04+trelease+git20221101.1210 @ii K Ib >
Broken neon-settings-2:amd64 Hängt ab von on ruby:amd64 < 1:3.0~exp1 @ii R >
  Considering ruby:amd64 112 as a solution to neon-settings-2:amd64 5306
  Added ruby:amd64 to the remove list
  Fixing neon-settings-2:amd64 via keep of ruby:amd64
Investigating (13) ruby:amd64 < 1:3.0~exp1 @ii K Ib >
Broken ruby:amd64 Hängt ab von on ruby3.0:amd64 < 3.0.2-7ubuntu2.1 @ii R >
  Considering ruby3.0:amd64 112 as a solution to ruby:amd64 5306
  Added ruby3.0:amd64 to the remove list
  Fixing ruby:amd64 via keep of ruby3.0:amd64
Investigating (13) ruby3.0:amd64 < 3.0.2-7ubuntu2.1 @ii K Ib >
Broken ruby3.0:amd64 Hängt ab von on libruby3.0:amd64 < 3.0.2-7ubuntu2.1 @ii R > (>= 3.0.0~preview1)
  Considering libruby3.0:amd64 112 as a solution to ruby3.0:amd64 5306
  Added libruby3.0:amd64 to the remove list
  Fixing ruby3.0:amd64 via keep of libruby3.0:amd64
Investigating (13) libruby3.0:amd64 < 3.0.2-7ubuntu2.1 @ii K Ib >
Broken libruby3.0:amd64 Hängt ab von on rake:amd64 < 13.0.6-2 @ii R > (>= 10.4.2)
  Considering rake:amd64 5 as a solution to libruby3.0:amd64 5306
  Added rake:amd64 to the remove list
Broken libruby3.0:amd64 Hängt ab von on ruby-xmlrpc:amd64 < 0.3.2-1ubuntu0.1 @ii R > (>= 0.3.0~)
  Considering ruby-xmlrpc:amd64 112 as a solution to libruby3.0:amd64 5306
  Added ruby-xmlrpc:amd64 to the remove list
  Fixing libruby3.0:amd64 via keep of rake:amd64
  Fixing libruby3.0:amd64 via keep of ruby-xmlrpc:amd64
Investigating (14) ruby-xmlrpc:amd64 < 0.3.2-1ubuntu0.1 @ii K Ib >
Broken ruby-xmlrpc:amd64 Hängt ab von on ruby-webrick:amd64 < none | 1.7.0-3 @un uH >
  Considering ruby-webrick:amd64 112 as a solution to ruby-xmlrpc:amd64 5306
  Added ruby-webrick:amd64 to the remove list
  Fixing ruby-xmlrpc:amd64 via keep of ruby-webrick:amd64
Investigating (15) ruby-xmlrpc:amd64 < 0.3.2-1ubuntu0.1 @ii K Ib >
Broken ruby-xmlrpc:amd64 Hängt ab von on ruby-webrick:amd64 < none | 1.7.0-3 @un uH >
  Considering ruby-webrick:amd64 5306 as a solution to ruby-xmlrpc:amd64 5306
  Removing ruby-xmlrpc:amd64 rather than change ruby-webrick:amd64
Investigating (15) libruby3.0:amd64 < 3.0.2-7ubuntu2.1 @ii K Ib >
Broken libruby3.0:amd64 Hängt ab von on ruby-xmlrpc:amd64 < 0.3.2-1ubuntu0.1 @ii R > (>= 0.3.0~)
  Considering ruby-xmlrpc:amd64 5306 as a solution to libruby3.0:amd64 5306
  Removing libruby3.0:amd64 rather than change ruby-xmlrpc:amd64
Investigating (16) ruby3.0:amd64 < 3.0.2-7ubuntu2.1 @ii K Ib >
Broken ruby3.0:amd64 Hängt ab von on libruby3.0:amd64 < 3.0.2-7ubuntu2.1 @ii R > (>= 3.0.0~preview1)
  Considering libruby3.0:amd64 5306 as a solution to ruby3.0:amd64 5306
  Removing ruby3.0:amd64 rather than change libruby3.0:amd64
Investigating (17) ruby:amd64 < 1:3.0~exp1 @ii K Ib >
Broken ruby:amd64 Hängt ab von on ruby3.0:amd64 < 3.0.2-7ubuntu2.1 @ii R >
  Considering ruby3.0:amd64 5306 as a solution to ruby:amd64 5306
  Removing ruby:amd64 rather than change ruby3.0:amd64
Investigating (17) ruby-rubygems:amd64 < 3.3.5-2 @ii K Ib >
Broken ruby-rubygems:amd64 Hängt ab von on ruby:any:any < none @un H >
  Considering ruby:i386 5 as a solution to ruby-rubygems:amd64 5
  Removing ruby-rubygems:amd64 rather than change ruby:any:any
Investigating (17) rake:amd64 < 13.0.6-2 @ii K Ib >
Broken rake:amd64 Hängt ab von on ruby:any:any < none @un H >
  Considering ruby:i386 5 as a solution to rake:amd64 5306
  Added ruby:i386 to the remove list
  Fixing rake:amd64 via keep of ruby:i386
Investigating (18) neon-settings-2:amd64 < 0.4+p22.04+trelease+git20221101.1210 @ii K Ib >
Broken neon-settings-2:amd64 Hängt ab von on ruby:amd64 < 1:3.0~exp1 @ii R >
  Considering ruby:amd64 5306 as a solution to neon-settings-2:amd64 5306
  Removing neon-settings-2:amd64 rather than change ruby:amd64
Investigating (18) rake:amd64 < 13.0.6-2 @ii K Ib >
Broken rake:amd64 Hängt ab von on ruby:any:any < none @un H >
  Considering ruby:i386 5306 as a solution to rake:amd64 5306
  Removing rake:amd64 rather than change ruby:any:any
Investigating (19) neon-settings-2:amd64 < 0.4+p22.04+trelease+git20221101.1210 @ii K Ib >
Broken neon-settings-2:amd64 Hängt ab von on ruby:amd64 < 1:3.0~exp1 @ii R >
  Considering ruby:amd64 5306 as a solution to neon-settings-2:amd64 5306
  Removing neon-settings-2:amd64 rather than change ruby:amd64
Done
Einige Pakete konnten nicht installiert werden. Das kann bedeuten, dass
Sie eine unmögliche Situation angefordert haben oder, wenn Sie die
Unstable-Distribution verwenden, dass einige erforderliche Pakete noch
nicht erstellt wurden oder Incoming noch nicht verlassen haben.
Die folgenden Informationen helfen Ihnen vielleicht, die Situation zu lösen:

Die folgenden Pakete haben unerfüllte Abhängigkeiten:
 neon-settings-2 : Hängt ab von: ruby soll aber nicht installiert werden
E: Fehler: Unterbrechungen durch pkgProblemResolver::Resolve hervorgerufen; dies könnte durch zurückgehaltene Pakete verursacht worden sein.

I have already updated 7 Neon System. The same behaviour everywhere.


Bookmarks



Who is online

Registered users: Bing [Bot], claydoh, Google [Bot], rblackwell, Sogou [Bot]