Hello,
I have KDENeon installed on my Sony VAIO laptop (Plasma 5.8.. It has been working just fine up to now. However, after performing a software update (aptitude update && aptitude upgrade) last night (a procedure that works o.k. normally!), important components don't function anymore.
E.g.:
- No more connection to my own LAN-connected server; ifconfig now ONLY shows the "lo" (localhost). Neither the Ethernet-LAN (enp2s0) nor the WLAN are shown.
- My USB-connected mouse is not recognized. The trackpad does still function.
At first I thought it might be the hardware, but - Thank God - everything works o.k. on the Mint-KDE-17.3-System and Windows-Vista, installed on the very same laptop.
So the problem is definitely due to the software upgrade.
Has anybody had the same experience? If so, what do I do now (besides re-installing everything?)
Thanks - and regards from Salzburg, Austria.

Very much so!!!
Only on the two laptops I upgraded opengl keeps crashing all the time. Apart from plasmashell 5.11.5 there also came new graphics software. E.g. mesa 17.2.4 to replace mesa 17.0.7. So first I thought that did it. But now I don't think it does anymore. I noticed that on Ubuntu Bionic all is fine. And that uses exactly the same mesa version (17.2.4). These two laptops have a different age but both use onboard graphics cards from Intel.
Plasmashell 5.11.5 doesn't make a good impression at all.

hstoellinger wrote:Hello,
I have KDENeon installed on my Sony VAIO laptop (Plasma 5.8.. It has been working just fine up to now. However, after performing a software update (aptitude update && aptitude upgrade) last night (a procedure that works o.k. normally!), important components don't function anymore.

It may be that using upgrade has left some packages not fully updated - see quote from the aptitude man-page.

"full-upgrade
Upgrades installed packages to their most recent version, removing or installing packages
as necessary. This command is less conservative than safe-upgrade and thus more likely to
perform unwanted actions. However, it is capable of upgrading packages that safe-upgrade
cannot upgrade."

My understanding is that most users would recommend always using full-upgrade every time. Before considering a re-install it would be worth considering this option.

Hello,
I performed an "aptitude full-upgrade" as you suggest. It didn't do anything. Of course I cannot do any recovery "online", seeing as I don't have any connection to the internet. By the way - no idea why the mouse doesn't function anymore either. It's sad, but I might have to go the "Mint"-way and forget about KDE -- after having been a more or less satisfied KDE-fan for at least 10 years. Obviously the latest updates to KDENeon were not tested thoroughly enough...
By the way, when I boot into recovery mode, my Ethernet-card gets recognised. I can ping hosts on the internet, but trying to do an aptitude update/upgrade does NOT work...
Thanks for any hints.

The log of yesterday's update/upgrade is as enclosed:

Code: Select all

Aptitude 0.7.4: Protokoll
Mit, 03. Jän 2018 22:48:36 +0100

  WICHTIG: Diese Log-Datei listet nur beabsichtigte Aktionen; Aktionen, die aufgrund
  von dpkg-Problemen gescheitert sind, könnten nicht fertiggestellt sein.

36 Pakete werden installiert und 2 Pakete entfernt.
43,2 MB der Festplatte werden belegt.
========================================
[ENTFERNEN, NICHT VERWENDET] libllvm4.0:amd64 1:4.0-1ubuntu1~16.04.2
[ENTFERNEN, NICHT VERWENDET] libllvm4.0:i386 1:4.0-1ubuntu1~16.04.2
[INSTALLIEREN, ABHÄNGIGKEITEN] libdrm-common:amd64 2.4.83-1~16.04.1
[INSTALLIEREN, ABHÄNGIGKEITEN] libllvm5.0:amd64 1:5.0-3~16.04.1
[INSTALLIEREN, ABHÄNGIGKEITEN] libllvm5.0:i386 1:5.0-3~16.04.1
[AKTUALISIERUNG] libdrm-amdgpu1:amd64 2.4.76-1~ubuntu16.04.1 -> 2.4.83-1~16.04.1
[AKTUALISIERUNG] libdrm-amdgpu1:i386 2.4.76-1~ubuntu16.04.1 -> 2.4.83-1~16.04.1
[AKTUALISIERUNG] libdrm-dev:amd64 2.4.76-1~ubuntu16.04.1 -> 2.4.83-1~16.04.1
[AKTUALISIERUNG] libdrm-intel1:amd64 2.4.76-1~ubuntu16.04.1 -> 2.4.83-1~16.04.1
[AKTUALISIERUNG] libdrm-intel1:i386 2.4.76-1~ubuntu16.04.1 -> 2.4.83-1~16.04.1
[AKTUALISIERUNG] libdrm-nouveau2:amd64 2.4.76-1~ubuntu16.04.1 -> 2.4.83-1~16.04.1
[AKTUALISIERUNG] libdrm-nouveau2:i386 2.4.76-1~ubuntu16.04.1 -> 2.4.83-1~16.04.1
[AKTUALISIERUNG] libdrm-radeon1:amd64 2.4.76-1~ubuntu16.04.1 -> 2.4.83-1~16.04.1
[AKTUALISIERUNG] libdrm-radeon1:i386 2.4.76-1~ubuntu16.04.1 -> 2.4.83-1~16.04.1
[AKTUALISIERUNG] libdrm2:amd64 2.4.76-1~ubuntu16.04.1 -> 2.4.83-1~16.04.1
[AKTUALISIERUNG] libdrm2:i386 2.4.76-1~ubuntu16.04.1 -> 2.4.83-1~16.04.1
[AKTUALISIERUNG] libegl1-mesa:amd64 17.0.7-0ubuntu0.16.04.2 -> 17.2.4-0ubuntu1~16.04.2
[AKTUALISIERUNG] libegl1-mesa-dev:amd64 17.0.7-0ubuntu0.16.04.2 -> 17.2.4-0ubuntu1~16.04.2
[AKTUALISIERUNG] libgbm1:amd64 17.0.7-0ubuntu0.16.04.2 -> 17.2.4-0ubuntu1~16.04.2
[AKTUALISIERUNG] libgl1-mesa-dev:amd64 17.0.7-0ubuntu0.16.04.2 -> 17.2.4-0ubuntu1~16.04.2
[AKTUALISIERUNG] libgl1-mesa-dri:amd64 17.0.7-0ubuntu0.16.04.2 -> 17.2.4-0ubuntu1~16.04.2
[AKTUALISIERUNG] libgl1-mesa-dri:i386 17.0.7-0ubuntu0.16.04.2 -> 17.2.4-0ubuntu1~16.04.2
[AKTUALISIERUNG] libgl1-mesa-glx:amd64 17.0.7-0ubuntu0.16.04.2 -> 17.2.4-0ubuntu1~16.04.2
[AKTUALISIERUNG] libgl1-mesa-glx:i386 17.0.7-0ubuntu0.16.04.2 -> 17.2.4-0ubuntu1~16.04.2
[AKTUALISIERUNG] libglapi-mesa:amd64 17.0.7-0ubuntu0.16.04.2 -> 17.2.4-0ubuntu1~16.04.2
[AKTUALISIERUNG] libglapi-mesa:i386 17.0.7-0ubuntu0.16.04.2 -> 17.2.4-0ubuntu1~16.04.2
[AKTUALISIERUNG] libgles2-mesa:amd64 17.0.7-0ubuntu0.16.04.2 -> 17.2.4-0ubuntu1~16.04.2
[AKTUALISIERUNG] libjavascriptcoregtk-4.0-18:amd64 2.18.3-0ubuntu0.16.04.1 -> 2.18.4-0ubuntu0.16.04.1
[AKTUALISIERUNG] libosmesa6:amd64 17.0.7-0ubuntu0.16.04.2 -> 17.2.4-0ubuntu1~16.04.2
[AKTUALISIERUNG] libosmesa6:i386 17.0.7-0ubuntu0.16.04.2 -> 17.2.4-0ubuntu1~16.04.2
[AKTUALISIERUNG] libwayland-egl1-mesa:amd64 17.0.7-0ubuntu0.16.04.2 -> 17.2.4-0ubuntu1~16.04.2
[AKTUALISIERUNG] libwebkit2gtk-4.0-37:amd64 2.18.3-0ubuntu0.16.04.1 -> 2.18.4-0ubuntu0.16.04.1
[AKTUALISIERUNG] libwebkit2gtk-4.0-37-gtk2:amd64 2.18.3-0ubuntu0.16.04.1 -> 2.18.4-0ubuntu0.16.04.1
[AKTUALISIERUNG] libxatracker2:amd64 17.0.7-0ubuntu0.16.04.2 -> 17.2.4-0ubuntu1~16.04.2
[AKTUALISIERUNG] mesa-common-dev:amd64 17.0.7-0ubuntu0.16.04.2 -> 17.2.4-0ubuntu1~16.04.2
[AKTUALISIERUNG] mesa-vdpau-drivers:amd64 17.0.7-0ubuntu0.16.04.2 -> 17.2.4-0ubuntu1~16.04.2
[AKTUALISIERUNG] xserver-xorg-core-hwe-16.04:amd64 2:1.19.3-1ubuntu1~16.04.4 -> 2:1.19.5-0ubuntu2~16.04.1
[AKTUALISIERUNG] xserver-xorg-legacy-hwe-16.04:amd64 2:1.19.3-1ubuntu1~16.04.4 -> 2:1.19.5-0ubuntu2~16.04.1
========================================


Try using apt instead of aptitude, to see if there is a difference.

Code: Select all

sudo apt update && sudo apt full-upgrade

aptitude, in my own personal experiences, can be too "smart" sometimes.

So start with... thanks for the hint about apt/aptitude. I have successfully performed another update/upgrade using apt...
Things seem to be working again now, after booting (by chance!) with a different kernel. I am enclosing the pertinent grub.conf entries. In short - booting using kernel 4.10.0-37 works, booting with kernel 4.10.0-42 does NOT. I don't know why, not being THAT much of a Linux nerd, but for the moment I am a happy boy!
Actually - I might still stay with KDENeon - even after THIS experience! Let's see what happens...
Regards H.S.

Code: Select all

### BEGIN /etc/grub.d/10_linux_proxy ###
menuentry "GNU/Linux, mit Linux 4.10.0-37-generic" --class ubuntu --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-4.10.0-37-generic-advanced-c14c067b-d467-4369-8ac4-7f4e2406468d' {
      recordfail
      load_video
      gfxmode $linux_gfx_mode
      insmod gzio
      if [ x$grub_platform = xxen ]; then insmod xzio; insmod lzopio; fi
      insmod part_msdos
      insmod ext2
      set root='hd0,msdos5'
      if [ x$feature_platform_search_hint = xy ]; then
        search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos5 --hint-efi=hd0,msdos5 --hint-baremetal=ahci0,msdos5  c14c067b-d467-4369-8ac4-7f4e2406468d
      else
        search --no-floppy --fs-uuid --set=root c14c067b-d467-4369-8ac4-7f4e2406468d
      fi
      echo   'Linux 4.10.0-37-generic wird geladen …'
           linux   /boot/vmlinuz-4.10.0-37-generic root=UUID=c14c067b-d467-4369-8ac4-7f4e2406468d ro  quiet splash $vt_handoff
      echo   'Initiale Ramdisk wird geladen …'
      initrd   /boot/initrd.img-4.10.0-37-generic
}
### END /etc/grub.d/10_linux_proxy ###

### BEGIN /etc/grub.d/42_custom_proxy ###
menuentry "NEON 16.04 xenial" --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-simple-c14c067b-d467-4369-8ac4-7f4e2406468d' {
   recordfail
   load_video
   gfxmode $linux_gfx_mode
   insmod gzio
   if [ x$grub_platform = xxen ]; then insmod xzio; insmod lzopio; fi
   insmod part_msdos
   insmod ext2
   set root='hd0,msdos5'
   if [ x$feature_platform_search_hint = xy ]; then
     search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos5 --hint-efi=hd0,msdos5 --hint-baremetal=ahci0,msdos5  c14c067b-d467-4369-8ac4-7f4e2406468d
   else
     search --no-floppy --fs-uuid --set=root c14c067b-d467-4369-8ac4-7f4e2406468d
   fi
           linux   /boot/vmlinuz-4.10.0-42-generic root=UUID=c14c067b-d467-4369-8ac4-7f4e2406468d ro  quiet splash $vt_handoff
   initrd   /boot/initrd.img-4.10.0-42-generic
}
menuentry "Mint17"{
   set root='(hd0,6)'
   search --no-floppy --fs-uuid --set=root a6868d77-06e7-42fd-a7b5-58dd951f65dc
   linux /vmlinuz root=UUID=a6868d77-06e7-42fd-a7b5-58dd951f65dc
   initrd /initrd.img
}
### END /etc/grub.d/42_custom_proxy ###



Hello,
Upgrade woes continue...!!!
As I mentioned before - I am reasonably happy with KDENeon. However - every once in a while, when some important updates are available, things go dreadfully wrong. Usually I cannot boot the system. The update of this Saturday morning led to a blue screen being displayed at boot time which wants me to select a user and enter the password. I can see that a valid user seems to be pre-selected, because my full name appears at the top of the box. However, nothing happens if I then enter my usual and correct password. The screen also switches to a keyboard display (weird enough with a British English layout, even though German is my selected system language!). My laptop is not touch-sensitive, so I cannot do anything at all on THAT keyboard.
To summarize - I am always somewhat worried when updating KDENeon (which I do every morning!), especially when a lot of stuff is supposedly updated. Somewhat more care might be appropriate on the quality assurance side. Any help would be greatly appreciated and NEEDED!!!
Regards from Salzburg
H. Stoellinger

Seems like my excursion into KDENeon was only a short one...

As it's been pointed out countless times, this

Code: Select all

sudo apt update && sudo apt full-upgrade

is the correct way to update Neon or any Ubuntu-based OS.

It maintains your system in organic health.

And if the system breaks, that's not user error.

Personally, I've never broken my system using this update method. Not once.

raddison wrote:As it's been pointed out countless times, this
sudo apt update && sudo apt full-upgrade
is the correct way to update Neon or any Ubuntu-based OS.

Well countless of users don't read the official FAQ .

How do I Update to the Latest Software?
KDE neon does continuous deployment of the latest KDE software which means there are nearly always new versions of our software to update to. We recommend using Plasma Discover's updater which appears in your panel:

If you prefer to use the command line you can use the pkcon command:

pkcon refresh
pkcon update
This will install all new packages and uses the same PackageKit code as Plasma Discover. Some uses of apt do not install new packages which makes it less suitable for KDE neon.

https://neon.kde.org/faq

'pkcon update' works, but sometimes the output is a bit messy on terminal.

Imo, that's the most convenient way to update Neon, which creates proper output on terminal:

1)

Code: Select all

pkcon refresh

2) Optional. Only if you want to see a list of available updates.

Code: Select all

pkcon get-updates

3)

Code: Select all

sudo pkcon update -y

btw, the same method also works great on Open Suse Leap & Tumbleweed.