[SOLVED] Some Neon observations

[Teunis]

Two days ago I downloaded the Neon User iso and last night I tried to install it on an external (USB3) SSD.
First I used the already exiting three partitions that had Kubuntu 12.04 on them.

The installation went fine, I booted it and used the konsole with apt to update/upgrade.
This had a bit of a problem in that it was impossible to get through the grub update, I just could not sellect the partition to install grub.
I did a manual update-grub and rebooted.
No luck, the thing got stuck very early on in Grub.

I did a second install now I set the whole 64Gb disk as a Reiser device, this and a third attempt failed to reboot...

Just now I got the thing working, again as a Reiser formatted system but this time I selected English (US) as system language, not my usual Dutch...

Also, I did the first update through the included Discoverer package manager which is better then what I am used to on my daily 16.04 but is still inferior to regular Muon or Synaptic.

In the System Settings I am missing an option to select nVidia, the present Nouveau driver does not support my Dell monitor with 2560x1440 pixels very well.
The package manager shows no nVidia drivers.

I'd be grateful for a tip re. installing nVidia.

[Snowhog]

Tip: Don't use Discover -- EVER!

Install (from the command line) muon and start using it instead. Discover (still) sucks (it was never intended to be; and isn't; a full package manager.)

[vinnywright]

Hay @Teunis ,,,,,,,long time no see your typeset ,,,,,LOL

I am having trouble undrstanding this part of your post

The installation went fine, I booted it and used the konsole with apt to update/upgrade.
This had a bit of a problem in that it was impossible to get through the grub update, I just could not sellect the partition to install grub.
I did a manual update-grub and rebooted.
No luck, the thing got stuck very early on in Grub.

you say the installation went fine (this is where grub gets installed) why did you feel the need to reinstall it?

it's an external drive ,,,,,are you going through the bios to select it as the boot device?

as to the nvidia thing ,,,this is strange as it should be in the repo ,,,,,,but I allways add

#graphics drivers (nvidia)
deb http://ppa.launchpad.net/graphics-drivers/ppa/ubuntu/ xenial main

to my sources.list

neon is based on the ubuntu-xenial base

VINNY

[vinnywright]

Tip: Don't use Discover -- EVER!

Install (from the command line) muon and start using it instead. Discover (still) sucks (it was never intended to be; and isn't; a full package manager.)

+1 on that

VINNY

[Teunis]

A good to hear both your inputs re. Discover.
For a moment I thought it might have some essential differences to the command line or Muon.

About the problem setting the Grub device, this is using apt from the CLI in Konsole.
During the installation proper I could select the correct partition, no problem.

The problem came during the subsequent apt-driven update & upgrade.
When the upgrade process reached the point to update grub I got a screen with three options, those were the drives present on this laptop, two internal and the one external SSD.
First off, the colours presented made it near impossible to see where the cursor was, two almost identical shades of red (Coral/Vermilion)).
Second, when I did select the external SSD it would not check it and revert to the primary SSD with my daily installation, something I did not want to overwrite.

I was able to reboot based on the original kernel and do a manual grub update but a subsequent boot stalled very early on.

Anyhow, right now I have a working system (on Reiser!) albeit I'll have to look into the nVidia issue, the System Settings menu in 16.04 offers a utility to check for available hardware drivers, I have not seen similar in the neon System Settings.

Vinny, well spotted I did not post much on this site, the main reason is probably I'm very busy with work, the second is that 16.04 works so well on this Lenovo laptop. About work, thanks to Harvey I have some time off, last Tuesday I was to fly to Houston to help out with the development of new equipment...

[Teunis]

Using the CLI I installed Muon proper.
Then I requested a check for updates and clicked the Full Upgrade button.

The result is not what I want...


A further CLI request for an upgrade did upgrade three packages without trying to remove a bunch of others.

Now I seem to remember Muon and Apt use different lists of the installed packages.

Then I thought usually I don't use upgrade but dist-upgrade.
That really suggested to remove most of the desktop!

teunis@teunis-verbatim:~$ sudo apt dist-upgrade
Reading package lists... Done
Building dependency tree       
Reading state information... Done
Starting pkgProblemResolver with broken count: 3
Starting 2 pkgProblemResolver with broken count: 3
Investigating (0) libqalculate6 [ amd64 ] < none -> 0.9.10-1+16.04+xenial+build10 > ( libs )
Broken libqalculate6:amd64 Breaks on libqalculate5v5 [ amd64 ] < 0.9.7-9.1 > ( universe/libs )
Considering libqalculate5v5:amd64 -1 as a solution to libqalculate6:amd64 7
Added libqalculate5v5:amd64 to the remove list
Fixing libqalculate6:amd64 via remove of libqalculate5v5:amd64
Investigating (0) libzip5 [ amd64 ] < none -> 1.2.0-0neon+16.04+xenial+build18 > ( libs )
Broken libzip5:amd64 Breaks on libzip4 [ amd64 ] < 1.0.1-0ubuntu1 > ( universe/libs ) (< 1:1.0.1)
Considering libzip4:amd64 1 as a solution to libzip5:amd64 1
Holding Back libzip5:amd64 rather than change libzip4:amd64
Investigating  (0) ark [ amd64 ] < 4:17.04.2+p16.04+git20170611.0605-0 ->  4:17.08.0+p16.04+git20170901.1039-0 > ( utils )
Broken ark:amd64 Depends on libzip5 [ amd64 ] < none -> 1.2.0-0neon+16.04+xenial+build18 > ( libs )
Considering libzip5:amd64 1 as a solution to ark:amd64 1
Holding Back ark:amd64 rather than change libzip5:amd64
Investigating (0) libqalculate6-data [ amd64 ] < none -> 0.9.10-1+16.04+xenial+build10 > ( libs )
Broken libqalculate6-data:amd64 Breaks on libqalculate5-data [ amd64 ] < 0.9.7-9.1 > ( universe/libs )
Considering libqalculate5-data:amd64 0 as a solution to libqalculate6-data:amd64 0
Holding Back libqalculate6-data:amd64 rather than change libqalculate5-data:amd64
Investigating (1) libqalculate6 [ amd64 ] < none -> 0.9.10-1+16.04+xenial+build10 > ( libs )
Broken libqalculate6:amd64 Depends on libqalculate6-data [ amd64 ] < none -> 0.9.10-1+16.04+xenial+build10 > ( libs )
Considering libqalculate6-data:amd64 0 as a solution to libqalculate6:amd64 7
Holding Back libqalculate6:amd64 rather than change libqalculate6-data:amd64
Try to Re-Instate (1) ark:amd64
Investigating  (2) plasma-workspace [ amd64 ] < 4:5.10.1+p16.04+git20170610.0324-0  -> 4:5.10.5+p16.04+git20170901.0108-0 > ( kde )
Broken plasma-workspace:amd64 Depends on libqalculate6 [ amd64 ] < none -> 0.9.10-1+16.04+xenial+build10 > ( libs )
Considering libqalculate6:amd64 7 as a solution to plasma-workspace:amd64 18
Removing plasma-workspace:amd64 rather than change libqalculate6:amd64
Investigating (2) kdeconnect [ amd64 ] < 1.0.3+p16.04+git20170814.0320-0 > ( kde )
Broken  kdeconnect:amd64 Depends on plasma-workspace [ amd64 ] <  4:5.10.1+p16.04+git20170610.0324-0 ->  4:5.10.5+p16.04+git20170901.0108-0 > ( kde )
Considering plasma-workspace:amd64 18 as a solution to kdeconnect:amd64 5
Removing kdeconnect:amd64 rather than change plasma-workspace:amd64
Investigating (2) libkf5purpose-bin [ amd64 ] < 1.1+p16.04+git20170707.0319-0 > ( libs )
Broken libkf5purpose-bin:amd64 Depends on kdeconnect [ amd64 ] < 1.0.3+p16.04+git20170814.0320-0 > ( kde )
Considering kdeconnect:amd64 18 as a solution to libkf5purpose-bin:amd64 5
Removing libkf5purpose-bin:amd64 rather than change kdeconnect:amd64
Investigating (2) sddm-theme-breeze [ amd64 ] < 4:5.10.5+p16.04+git20170901.0108-0 > ( kde )
Broken  sddm-theme-breeze:amd64 Depends on plasma-workspace [ amd64 ] <  4:5.10.1+p16.04+git20170610.0324-0 ->  4:5.10.5+p16.04+git20170901.0108-0 > ( kde )
Considering plasma-workspace:amd64 18 as a solution to sddm-theme-breeze:amd64 3
Removing sddm-theme-breeze:amd64 rather than change plasma-workspace:amd64
Investigating (2) kinfocenter [ amd64 ] < 4:5.10.5+p16.04+git20170828.1152-0 > ( kde )
Broken  kinfocenter:amd64 Depends on plasma-workspace [ amd64 ] <  4:5.10.1+p16.04+git20170610.0324-0 ->  4:5.10.5+p16.04+git20170901.0108-0 > ( kde )
Considering plasma-workspace:amd64 18 as a solution to kinfocenter:amd64 3
Removing kinfocenter:amd64 rather than change plasma-workspace:amd64
Investigating (2) plasma-desktop [ amd64 ] < 4:5.10.5+p16.04+git20170901.0244-0 > ( kde )
Broken  plasma-desktop:amd64 Depends on plasma-workspace [ amd64 ] <  4:5.10.1+p16.04+git20170610.0324-0 ->  4:5.10.5+p16.04+git20170901.0108-0 > ( kde )
Considering plasma-workspace:amd64 18 as a solution to plasma-desktop:amd64 1
Removing plasma-desktop:amd64 rather than change plasma-workspace:amd64
Investigating (2) plasma-widgets-addons [ amd64 ] < 4:5.10.5+p16.04+git20170828.0505-0 > ( kde )
Broken  plasma-widgets-addons:amd64 Depends on plasma-workspace [ amd64 ] <  4:5.10.1+p16.04+git20170610.0324-0 ->  4:5.10.5+p16.04+git20170901.0108-0 > ( kde )
Considering plasma-workspace:amd64 18 as a solution to plasma-widgets-addons:amd64 1
Removing plasma-widgets-addons:amd64 rather than change plasma-workspace:amd64
Investigating  (2) plasma-workspace-wayland [ amd64 ] <  4:5.10.1+p16.04+git20170610.0324-0 ->  4:5.10.5+p16.04+git20170901.0108-0 > ( kde )
Broken  plasma-workspace-wayland:amd64 Depends on plasma-workspace [ amd64 ]  < 4:5.10.1+p16.04+git20170610.0324-0 ->  4:5.10.5+p16.04+git20170901.0108-0 > ( kde ) (=  4:5.10.5+p16.04+git20170901.0108-0)
Considering plasma-workspace:amd64 18 as a solution to plasma-workspace-wayland:amd64 1
Removing plasma-workspace-wayland:amd64 rather than change plasma-workspace:amd64
Investigating (2) neon-desktop [ amd64 ] < 4+p16.04+git20170825.1126 > ( metapackages )
Broken neon-desktop:amd64 Depends on kinfocenter [ amd64 ] < 4:5.10.5+p16.04+git20170828.1152-0 > ( kde )
Considering kinfocenter:amd64 18 as a solution to neon-desktop:amd64 0
Removing neon-desktop:amd64 rather than change kinfocenter:amd64
Investigating (3) qml-module-org-kde-purpose [ amd64 ] < 1.1+p16.04+git20170707.0319-0 > ( libs )
Broken qml-module-org-kde-purpose:amd64 Depends on kdeconnect [ amd64 ] < 1.0.3+p16.04+git20170814.0320-0 > ( kde )
Considering kdeconnect:amd64 18 as a solution to qml-module-org-kde-purpose:amd64 7
Removing qml-module-org-kde-purpose:amd64 rather than change kdeconnect:amd64
Done
Calculating upgrade... Done
The following packages were automatically installed and are no longer required:
 discover discover-data fonts-noto fonts-noto-cjk fonts-noto-mono  fonts-noto-unhinted grub-theme-breeze gtk2-engines-pixbuf  gtk3-engines-breeze
ieee-data kaccounts-providers  kde-style-qtcurve-qt4 kde-style-qtcurve-qt5 kded5 kgamma5  libaccounts-glib0 libaccounts-qt5-1 libcln6 libdiscover2
libdmtx0a  libexiv2-14 libfakekey0 libgps22 libibus-1.0-5 libkaccounts1  libkf5emoticons-bin libkf5emoticons-data libkf5emoticons5
 libkf5holidays-data libkf5holidays5 libkf5jsembed-data libkf5jsembed5  libkf5people-data libkf5people5 libkf5peoplebackend5  libkf5peoplewidgets5
libkf5prison5 libkf5xmlrpcclient-data  libkf5xmlrpcclient5 libkfontinst5 libkfontinstui5 libllvm3.8  libmircommon5 libpam-kwallet5 libpcre16-3
 libplasma-geolocation-interface5 libprotobuf9v5 libqalculate5-data  libqrencode3 libqt5clucene5 libqt5concurrent5 libqt5designer5
 libqt5designercomponents5 libqt5help5 libqtcurve-utils2 libscim8v5  libsignon-plugins-common1 libsignon-qt5-1 libsrtp0 libtaskmanager6  libuv1
libweather-ion7 libxcb-record0 muon-notifier nodejs  nodejs-legacy pam-kwallet-init plasma-desktop-data plasma-integration  qdbus-qt5
qml-module-org-kde-activities qml-module-org-kde-extensionplugin qml-module-org-kde-kholidays qml-module-org-kde-kwindowsystem
 qml-module-org-kde-solid qml-module-qt-labs-settings  qml-module-qtwebkit qml-module-ubuntu-onlineaccounts  qtdeclarative5-qtquick2-plugin
qttools5-dev-tools sddm signon-plugin-oauth2 sni-qt socat sshfs
Use 'sudo apt autoremove' to remove them.
The following packages will be REMOVED:
kdeconnect kinfocenter libkf5purpose-bin libqalculate5v5 neon-desktop plasma-desktop plasma-widgets-addons plasma-workspace
plasma-workspace-wayland qml-module-org-kde-purpose sddm-theme-breeze
The following packages have been kept back:
ark
0 upgraded, 0 newly installed, 11 to remove and 1 not upgraded.
After this operation, 60,0 MB disk space will be freed.
Do you want to continue? [Y/n]

No, I don't want to continue...

[Teunis]

Oh yeah,

Adding a source to Muon returns this pop up:


Discover does not have a working option to add a source.

[chimak111]

Both attachments posted by Teunis, 7146 and 7147, don't work for me. Do they work for others?

[vinnywright]

Both attachments posted by Teunis, 7146 and 7147, don't work for me. Do they work for others?

no

VINNY

[dequire]

Discover is good at what it does. As mentioned above - it is not, nor was intended to be, a package manager. It's a software store that also handles updates. Within the scope of what it is, it's a really good application, and a good software store and system updater.

From KDE Userbase:

What Discover is

Discover is intended for users and distros where the terminal isn't the optimal solution for installation of apps and add-ons or updates. Where we want something intuitive and simple to use and above all safe to use.

We've all been there, someone has copy pasted commands from some website and suddenly they destroyed their entire installation. From a users perspective, especially a new user or a casual user this is disastrous and they will not be able to easily discern where the fault is: this shady website or your distro.

With Discover the focus is to empower the user to browse, test, install apps and update her installation without fear of disastrous misspellings and where trust is given, not taken.

What Discover isn't

Discover may be much but it is not an experts application for minute control of repos. It is not a replacement intended to compete with the terminal for experienced expert users. Our goal has been to focus clearer on a certain set of users where an application such as this is not only needed, but critical to their usage. To do this we have excluded other user groups entirely from the application goals. This doesn't mean they can't use Discover just that their specific use cases may not be perfectly covered.

Discover is not perfectly "child safe". It will never be something with which you can force the hand of the user, we believe in empowerment and try to guide the user through safe choices, but never force her into an action. Do not expect Discover to remove those options from your users.

Not trying to nit-pick here. Just want new Neon users to be more aware of what's what. It's also worth noting that in the case of Neon, in addition to being a type of "software store", it is recommended from the devs that discover be used for Neon system updates / upgrades for the following reason: It does not use Apt.

From the Neon Blog:

New FAQ added to KDE neon FAQ.

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.

Not trying to change anyone's opinion of Discover, just trying to make sure we are looking at it in the light for which it is intended

[Teunis]

Thanks for the explanation re. Discover.
It might be good at it's intended use yet not everyone has such a narrow user case, things like Synaptic and the later Muon versions are vastly more transparent and flexible.

Good to know it does use a different routine for updates, it looks like my use of apt has damaged the 'store' that Muon is using.

I still have to find another way to install/ enable the needed nVidia driver, it seems that is not part of Discover's limited options.

About the screen shots I wanted to include, originally they showed up on my screen but have now been replaced by dead links.
Another try:

[oldgeek]

I use Discover mainly for updates, but also for user opinions on certain software packages I haven't yet downloaded. It's much less buggy than before, though not entirely bug-free (which software is?). I also use Synaptic or Muon when I know what I want to install. I'm obviously not wedded to the command line--in fact, I don't use it often but may learn to do so some day. So all three programs suit the different needs I have. But Synaptic is probably the one I prefer the most.

[claydoh]

Thanks for the explanation re. Discover.
It might be good at it's intended use yet not everyone has such a narrow user case, things like Synaptic and the later Muon versions are vastly more transparent and flexible.

Good to know it does use a different routine for updates, it looks like my use of apt has damaged the 'store' that Muon is using.

I still have to find another way to install/ enable the needed nVidia driver, it seems that is not part of Discover's limited options.

About the screen shots I wanted to include, originally they showed up on my screen but have now been replaced by dead links.
Another try:
[ATTACH=CONFIG]7148[/ATTACH]

[ATTACH=CONFIG]7149[/ATTACH]

You can install the package software-properties-kde , which is the applet Kubuntu uses to configure software sources. It is a Debian/Ubuntu piece of software, and not an official KDE thing, so it is not part of Neon but is in the Ubuntu repos. Else you can configure sources from Discover.

the software-properties-kde applet also replaces synaptic's generic sources editor with its much more useful, *buntu specific one, so it is handy to have. It can be run standalone as well.

[vinnywright]

Using the CLI I installed Muon proper.
Then I requested a check for updates and clicked the Full Upgrade button.

The result is not what I want...

[ATTACH=CONFIG]7146[/ATTACH]
A further CLI request for an upgrade did upgrade three packages without trying to remove a bunch of others.

Now I seem to remember Muon and Apt use different lists of the installed packages.

Then I thought usually I don't use upgrade but dist-upgrade.
That really suggested to remove most of the desktop!

teunis@teunis-verbatim:~$ sudo apt dist-upgrade
Reading package lists... Done
Building dependency tree       
Reading state information... Done
Starting pkgProblemResolver with broken count: 3
Starting 2 pkgProblemResolver with broken count: 3
Investigating (0) libqalculate6 [ amd64 ] < none -> 0.9.10-1+16.04+xenial+build10 > ( libs )
Broken libqalculate6:amd64 Breaks on libqalculate5v5 [ amd64 ] < 0.9.7-9.1 > ( universe/libs )
Considering libqalculate5v5:amd64 -1 as a solution to libqalculate6:amd64 7
Added libqalculate5v5:amd64 to the remove list
Fixing libqalculate6:amd64 via remove of libqalculate5v5:amd64
Investigating (0) libzip5 [ amd64 ] < none -> 1.2.0-0neon+16.04+xenial+build18 > ( libs )
Broken libzip5:amd64 Breaks on libzip4 [ amd64 ] < 1.0.1-0ubuntu1 > ( universe/libs ) (< 1:1.0.1)
Considering libzip4:amd64 1 as a solution to libzip5:amd64 1
Holding Back libzip5:amd64 rather than change libzip4:amd64
Investigating  (0) ark [ amd64 ] < 4:17.04.2+p16.04+git20170611.0605-0 ->  4:17.08.0+p16.04+git20170901.1039-0 > ( utils )
Broken ark:amd64 Depends on libzip5 [ amd64 ] < none -> 1.2.0-0neon+16.04+xenial+build18 > ( libs )
Considering libzip5:amd64 1 as a solution to ark:amd64 1
Holding Back ark:amd64 rather than change libzip5:amd64
Investigating (0) libqalculate6-data [ amd64 ] < none -> 0.9.10-1+16.04+xenial+build10 > ( libs )
Broken libqalculate6-data:amd64 Breaks on libqalculate5-data [ amd64 ] < 0.9.7-9.1 > ( universe/libs )
Considering libqalculate5-data:amd64 0 as a solution to libqalculate6-data:amd64 0
Holding Back libqalculate6-data:amd64 rather than change libqalculate5-data:amd64
Investigating (1) libqalculate6 [ amd64 ] < none -> 0.9.10-1+16.04+xenial+build10 > ( libs )
Broken libqalculate6:amd64 Depends on libqalculate6-data [ amd64 ] < none -> 0.9.10-1+16.04+xenial+build10 > ( libs )
Considering libqalculate6-data:amd64 0 as a solution to libqalculate6:amd64 7
Holding Back libqalculate6:amd64 rather than change libqalculate6-data:amd64
Try to Re-Instate (1) ark:amd64
Investigating  (2) plasma-workspace [ amd64 ] < 4:5.10.1+p16.04+git20170610.0324-0  -> 4:5.10.5+p16.04+git20170901.0108-0 > ( kde )
Broken plasma-workspace:amd64 Depends on libqalculate6 [ amd64 ] < none -> 0.9.10-1+16.04+xenial+build10 > ( libs )
Considering libqalculate6:amd64 7 as a solution to plasma-workspace:amd64 18
Removing plasma-workspace:amd64 rather than change libqalculate6:amd64
Investigating (2) kdeconnect [ amd64 ] < 1.0.3+p16.04+git20170814.0320-0 > ( kde )
Broken  kdeconnect:amd64 Depends on plasma-workspace [ amd64 ] <  4:5.10.1+p16.04+git20170610.0324-0 ->  4:5.10.5+p16.04+git20170901.0108-0 > ( kde )
Considering plasma-workspace:amd64 18 as a solution to kdeconnect:amd64 5
Removing kdeconnect:amd64 rather than change plasma-workspace:amd64
Investigating (2) libkf5purpose-bin [ amd64 ] < 1.1+p16.04+git20170707.0319-0 > ( libs )
Broken libkf5purpose-bin:amd64 Depends on kdeconnect [ amd64 ] < 1.0.3+p16.04+git20170814.0320-0 > ( kde )
Considering kdeconnect:amd64 18 as a solution to libkf5purpose-bin:amd64 5
Removing libkf5purpose-bin:amd64 rather than change kdeconnect:amd64
Investigating (2) sddm-theme-breeze [ amd64 ] < 4:5.10.5+p16.04+git20170901.0108-0 > ( kde )
Broken  sddm-theme-breeze:amd64 Depends on plasma-workspace [ amd64 ] <  4:5.10.1+p16.04+git20170610.0324-0 ->  4:5.10.5+p16.04+git20170901.0108-0 > ( kde )
Considering plasma-workspace:amd64 18 as a solution to sddm-theme-breeze:amd64 3
Removing sddm-theme-breeze:amd64 rather than change plasma-workspace:amd64
Investigating (2) kinfocenter [ amd64 ] < 4:5.10.5+p16.04+git20170828.1152-0 > ( kde )
Broken  kinfocenter:amd64 Depends on plasma-workspace [ amd64 ] <  4:5.10.1+p16.04+git20170610.0324-0 ->  4:5.10.5+p16.04+git20170901.0108-0 > ( kde )
Considering plasma-workspace:amd64 18 as a solution to kinfocenter:amd64 3
Removing kinfocenter:amd64 rather than change plasma-workspace:amd64
Investigating (2) plasma-desktop [ amd64 ] < 4:5.10.5+p16.04+git20170901.0244-0 > ( kde )
Broken  plasma-desktop:amd64 Depends on plasma-workspace [ amd64 ] <  4:5.10.1+p16.04+git20170610.0324-0 ->  4:5.10.5+p16.04+git20170901.0108-0 > ( kde )
Considering plasma-workspace:amd64 18 as a solution to plasma-desktop:amd64 1
Removing plasma-desktop:amd64 rather than change plasma-workspace:amd64
Investigating (2) plasma-widgets-addons [ amd64 ] < 4:5.10.5+p16.04+git20170828.0505-0 > ( kde )
Broken  plasma-widgets-addons:amd64 Depends on plasma-workspace [ amd64 ] <  4:5.10.1+p16.04+git20170610.0324-0 ->  4:5.10.5+p16.04+git20170901.0108-0 > ( kde )
Considering plasma-workspace:amd64 18 as a solution to plasma-widgets-addons:amd64 1
Removing plasma-widgets-addons:amd64 rather than change plasma-workspace:amd64
Investigating  (2) plasma-workspace-wayland [ amd64 ] <  4:5.10.1+p16.04+git20170610.0324-0 ->  4:5.10.5+p16.04+git20170901.0108-0 > ( kde )
Broken  plasma-workspace-wayland:amd64 Depends on plasma-workspace [ amd64 ]  < 4:5.10.1+p16.04+git20170610.0324-0 ->  4:5.10.5+p16.04+git20170901.0108-0 > ( kde ) (=  4:5.10.5+p16.04+git20170901.0108-0)
Considering plasma-workspace:amd64 18 as a solution to plasma-workspace-wayland:amd64 1
Removing plasma-workspace-wayland:amd64 rather than change plasma-workspace:amd64
Investigating (2) neon-desktop [ amd64 ] < 4+p16.04+git20170825.1126 > ( metapackages )
Broken neon-desktop:amd64 Depends on kinfocenter [ amd64 ] < 4:5.10.5+p16.04+git20170828.1152-0 > ( kde )
Considering kinfocenter:amd64 18 as a solution to neon-desktop:amd64 0
Removing neon-desktop:amd64 rather than change kinfocenter:amd64
Investigating (3) qml-module-org-kde-purpose [ amd64 ] < 1.1+p16.04+git20170707.0319-0 > ( libs )
Broken qml-module-org-kde-purpose:amd64 Depends on kdeconnect [ amd64 ] < 1.0.3+p16.04+git20170814.0320-0 > ( kde )
Considering kdeconnect:amd64 18 as a solution to qml-module-org-kde-purpose:amd64 7
Removing qml-module-org-kde-purpose:amd64 rather than change kdeconnect:amd64
Done
Calculating upgrade... Done
The following packages were automatically installed and are no longer required:
discover discover-data fonts-noto fonts-noto-cjk fonts-noto-mono  fonts-noto-unhinted grub-theme-breeze gtk2-engines-pixbuf  gtk3-engines-breeze
ieee-data kaccounts-providers  kde-style-qtcurve-qt4 kde-style-qtcurve-qt5 kded5 kgamma5  libaccounts-glib0 libaccounts-qt5-1 libcln6 libdiscover2
libdmtx0a  libexiv2-14 libfakekey0 libgps22 libibus-1.0-5 libkaccounts1  libkf5emoticons-bin libkf5emoticons-data libkf5emoticons5
libkf5holidays-data libkf5holidays5 libkf5jsembed-data libkf5jsembed5  libkf5people-data libkf5people5 libkf5peoplebackend5  libkf5peoplewidgets5
libkf5prison5 libkf5xmlrpcclient-data  libkf5xmlrpcclient5 libkfontinst5 libkfontinstui5 libllvm3.8  libmircommon5 libpam-kwallet5 libpcre16-3
libplasma-geolocation-interface5 libprotobuf9v5 libqalculate5-data  libqrencode3 libqt5clucene5 libqt5concurrent5 libqt5designer5
libqt5designercomponents5 libqt5help5 libqtcurve-utils2 libscim8v5  libsignon-plugins-common1 libsignon-qt5-1 libsrtp0 libtaskmanager6  libuv1
libweather-ion7 libxcb-record0 muon-notifier nodejs  nodejs-legacy pam-kwallet-init plasma-desktop-data plasma-integration  qdbus-qt5
qml-module-org-kde-activities qml-module-org-kde-extensionplugin qml-module-org-kde-kholidays qml-module-org-kde-kwindowsystem
qml-module-org-kde-solid qml-module-qt-labs-settings  qml-module-qtwebkit qml-module-ubuntu-onlineaccounts  qtdeclarative5-qtquick2-plugin
qttools5-dev-tools sddm signon-plugin-oauth2 sni-qt socat sshfs
Use 'sudo apt autoremove' to remove them.
The following packages will be REMOVED:
kdeconnect kinfocenter libkf5purpose-bin libqalculate5v5 neon-desktop plasma-desktop plasma-widgets-addons plasma-workspace
plasma-workspace-wayland qml-module-org-kde-purpose sddm-theme-breeze
The following packages have been kept back:
ark
0 upgraded, 0 newly installed, 11 to remove and 1 not upgraded.
After this operation, 60,0 MB disk space will be freed.
Do you want to continue? [Y/n]

No, I don't want to continue...

you have a sereous problem with your packages ,,,,,,,I do not know what , I do not know what you have been trying .

I would first try a (if you have not "cleaned" the package cache)

sudo dpkg --configure -a

this will finish (if it was interrupted for some reason) configuring packages from the cache .

then a

sudo apt-get -f install

then check once again what a

sudo apt-get update && sudo apt-get  dist-upgrade

is going to do ..

as to the nvidia thing ,,,,the driver tool was not included in system settings I think because it quit working and no one has fixed it yet.

the CLI tool dose still work

vinny@vinny-Bonobo-Extreme:~$ ubuntu-drivers devices
== cpu-microcode.py ==
driver   : intel-microcode - distro non-free

== /sys/devices/pci0000:00/0000:00:01.0/0000:01:00.0 ==
vendor   : NVIDIA Corporation
model    : GK104M [GeForce GTX 860M]
modalias : pci:v000010DEd0000119Asv00001558sd00000376bc03sc00i00
driver   : nvidia-384 - third-party free recommended
driver   : nvidia-375 - third-party free
driver   : nvidia-378 - third-party free
driver   : nvidia-381 - third-party free
driver   : nvidia-340 - third-party free
driver   : xserver-xorg-video-nouveau - distro free builtin

in this exampel ,,,if I chose the autoinstall option ,,,,,

Available commands:
  devices: Show all devices which need drivers, and which packages apply to them.
  debug: Print all available information and debug data about drivers.
  autoinstall: Install drivers that are appropriate for automatic installation.
  list: Show all driver packages which apply to the current system.

it would install the ones showen if only one or the ones marked "recomended" if more than one.

you can use "apt" to search and see if any nvidia drivers are being seen by the system as is with

apt search nvidia-3

this will show all packages that start with "nvidia-3" ,,,,,,,,,,if you see a driver (like nvidia-381) that you want it is sufichent to just

sudo apt install nvidia-381

and it will pull in whatever elce it neads .

BUT do fix the packag problem you have befor trying to install anything .

VINNY

[claydoh]

Discover is good at what it does. As mentioned above - it is not, nor was intended to be, a package manager. It's a software store that also handles updates. Within the scope of what it is, it's a really good application, and a good software store and system updater.

From KDE Userbase:

What Discover is

Discover is intended for users and distros where the terminal isn't the optimal solution for installation of apps and add-ons or updates. Where we want something intuitive and simple to use and above all safe to use.

We've all been there, someone has copy pasted commands from some website and suddenly they destroyed their entire installation. From a users perspective, especially a new user or a casual user this is disastrous and they will not be able to easily discern where the fault is: this shady website or your distro.

With Discover the focus is to empower the user to browse, test, install apps and update her installation without fear of disastrous misspellings and where trust is given, not taken.

What Discover isn't

Discover may be much but it is not an experts application for minute control of repos. It is not a replacement intended to compete with the terminal for experienced expert users. Our goal has been to focus clearer on a certain set of users where an application such as this is not only needed, but critical to their usage. To do this we have excluded other user groups entirely from the application goals. This doesn't mean they can't use Discover just that their specific use cases may not be perfectly covered.

Discover is not perfectly "child safe". It will never be something with which you can force the hand of the user, we believe in empowerment and try to guide the user through safe choices, but never force her into an action. Do not expect Discover to remove those options from your users.

Not trying to nit-pick here. Just want new Neon users to be more aware of what's what. It's also worth noting that in the case of Neon, in addition to being a type of "software store", it is recommended from the devs that discover be used for Neon system updates / upgrades for the following reason: It does not use Apt.

From the Neon Blog:

New FAQ added to KDE neon FAQ.

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.

Not trying to change anyone's opinion of Discover, just trying to make sure we are looking at it in the light for which it is intended

+42

To add to the preferred use of Discover or pkcon to update Neon, the reason for this was the very common issue of new, non-Ubuntu users coming to Neon and using apt update over apt full-upgrade or apt-get dist-upgrade to update their systems, and not always getting all new packages installed. Using apt does not hurt things over using Discover/pkcon , and vice-versa, so there should be no issue using one over the other.

pkcon is nothing new, just the commandline version of what PackageKit does in the background.
http://manpages.ubuntu.com/manpages/...1/pkcon.1.html
Packagekit is used by other distros and has support for a number of different packaging systems.