Neon/BionicUpgrades/Testing

From KDE Community Wiki
Revision as of 02:05, 19 August 2018 by Lengau (talk | contribs)

Please add your test results:

  • Name
    • Date
    • What edition of KDE Neon did you have installed?
    • Is your compuer booting with BIOS or UEFI?
    • Is secureboot enabled?
    • Success or problems?
    • Comments
  • Boudewijn Rempt
    • 19-06-2018
    • KDE neon 15.12
    • UEFI
    • Yes
    • Success
    • No Problems
  • Kenny D
    • 19-06-2018
    • KDE neon User
    • UEFI
    • No
    • Partial Success
    • Bionic it seems deprecated encrypted homes so you won't be able to login graphically after upgrading, installing encryptfs-utils semi fixes this however it is apparently not very reliable now
    • 27-06-27: not found any issues with encrypted home yet everything seems to be working ok so far
    • 29-06-2018: now noticed this error in dmesg on each boot, still seems to mount home ok though, anyone else seeing this?
      • [ 33.378048] Could not find key with description: [01521d6d47952845]
      • [ 33.378067] process_request_key_err: No key
      • [ 33.378068] Could not find valid key in user session keyring for sig specified in mount option: [01521d6d47952845]
      • [ 33.378089] One or more global auth toks could not properly register; rc = [-2]
      • [ 33.378089] Error parsing options; rc = [-2]
    • 28-06-2018: also just to note that release is currently broken, so if you haven't updated since yesterday you might want to avoid doing so for a bit
    • 29-06-2018: bionic usable again
    • 25-07-2018: switched over from release to user with no problems
  • Clay Weber
    • 25-6-2018
    • KDE Neon User
    • UEFI
    • NO
    • Upgrade installed succcessfully
    • Same problem as Kenny D above - I have an encrypted /home- Could not login to desktop, installing ecrypts-utils fixed the issue. No other issues found
  • Louis Weddall
    • 2018-06-25
    • KDE Neon User Edition 5.13
    • UEFI
    • No
    • Upgrade installed successfully
    • Xenial repositories are disabled, yet still listed in Discover, which could cause some confusion.
  • René Fritz
    • 2018-06-28
    • KDE Neon Developer Stable Edition
    • Bios
    • No
    • Upgrade installed successfully
    • no problems, except that in /etc/lsb-release is DISTRIB_ID=neon (again) instead of DISTRIB_ID=Ubuntu which breaks adding a ppa with add-apt-repository
  • Jakeir
    • 2018-06-28
    • Neon User Edition - KDE 5.13.1
    • UEFI
    • YES
    • Upgrade successful
    • updating packages after upgrade caused the same issues as seen by Kenny D with encryptfs-util and 'Could not find valid key in user session keyring for sig specified in mount option' - Currently unusable.
      • 2018-07-01 - completed another apt upgrade and reboot previous issues all resolved.
  • Lukas N
    • 2018-06-30
    • Neon User Edition
    • UEFI
    • No
    • Upgrade successful
    • btrfs-progs (formerly btrfs-tools?) was not installed.
  • Kostiantyn Rybnikov
    • 2018-07-05
    • Neon User Edition
    • BIOS
    • Secureboot not enabled
    • Problems
    • After upgrade finished and asked me to reboot I am seeing "Could not start kdeinit5. Check your installation" and nothing works. Photo: https:// photos.app.goo.gl/nw9G7iUeBEjx6BQg9
  • Thibaut FRANCOIS
    • 2018-07-07
    • Neon User Edition
    • UEFI
    • Secureboot not enabled
    • Problems
      • In the boot's beginning, I had the message "error, no symbol table". Fixed : I rebuilded grub on /etc/sdb and not /etc/sda, sda is my windows partition
      • Like René, in /etc/lsb-release is DISTRIB_ID=neon (again) instead of DISTRIB_ID=Ubuntu which breaks adding a ppa with add-apt-repository
      • After upgrade and the reboot I am seeing "Could not start kdeinit5. Check your installation". Fixed: I purged the nvidia driver with apt (sudo apt-get remove --purge nvidia-*) , and install nvidia-390 (sudo apt install nvidia-390) from oibaf/graphics-drivers/ppa (maybe the repository "graphics-drivers" would be sufficient, I don't know)
      • Firefox and chromium didn't launch : "libwayland-egl.so.1: cannot open shared object file: No such file or directory." Fixed: with "sudo apt-get install libwayland-egl1" (this library replace the libwayland-egl1-mesa)
  • David B
    • 2018-07-16
    • KDE Neon User Edition 5.13
    • BIOS
    • No secure boot
    • Successfully upgraded without issues
    • Comments
      • After upgrade system appears to be running KDE Neon Developers Edition
  • Brian W
    • 7/20/2018
    • Fresh install of of Neon LTS 5.12 (on Virtualbox guest)
    • BIOS
    • No secure boot
    • Successfully upgraded; no errors.
    • Comments
      • DISTRIB_ID in /etc/lsb-release is set for "neon". KDE Neon Developers Edition was installed instead of the LTS.
  • Kenny D 2
    • 2018-07-25
    • KDE Neon User Edition 5.13
    • BIOS
    • No secure boot
    • Successfully upgraded without issues, encrypted home still worked after upgrade
  • Kenny D 3
    • 2018-07-25
    • KDE Neon User Edition 5.13
    • BIOS
    • No secure boot
    • Successfully upgraded without issues
  • XYQuadrat
    • 2018-07-28
    • KDE Neon Developer Edition
    • BIOS
    • No secure boot
    • Success, needed to re-enable the neon PPA's and edit /etc/lsb-release to resolve dependency issues - that's it
    • Thanks for your hard work :)
  • Kenny D 4
    • 2018-07-29
    • KDE Neon User Edition 5.13
    • UEFI
    • Insecure boot
    • Couldn't login after upgrade due to missing ecryptfs-utils, has something changed in the last few days?
  • Ivan Safonov
    • 2018-08-04
    • bionic-early-access 20180804-0922-amd64.iso
    • UEFI
    • secureboot is disabled
    • Touchpad is not working, external mouse cursor moving too slow
    • Laptop Dell Latitude 7490. Fixed by removing /usr/share/X11/xorg.conf.d/41-evdev.conf link from neon-settings package.
  • Lengau
    • Date: 2018-08-18
    • What edition of KDE Neon did you have installed? KDE neon User Edition 5.13
    • Is your compuer booting with BIOS or UEFI? UEFI
    • Is secureboot enabled? No
    • Success or problems? [Desktop computer] Had to manually fix Nvidia drivers due to using ~graphics-drivers PPA. Everything else seems to be functional so far.
    • Comments