Broken Packages

[NoWorries]

Looks like that while I slept last night you were going hammer and tongs to sort out MoonRise problems. I must confess that when I strike such situations as a black screen, I use alt+ctrl+F1 to login to a terminal mode. On my system I am connected to the internet via Ethernet and I then check the update status with

sudo apt update; sudo apt full-upgrade

I then fix anything outstanding and if I am still getting a black screen, I then do drastic things like

sudo apt purge nvidia*

[MoonRise]

I didn't mean to hijack this thread. Appreciate that help. @ NoWorries: I agree on the alt-ctl-F1 measure but no updates were appearing. What was the eye opener was running journalctl. Seeing the GL error for SDDM sparked my memory on the video driver update. I really didn't equate my problem to that originally until seeing that.

So, back on the original thread. Has you problem cleared up?

[NoWorries]

I didn't mean to hijack this thread. ....... So, back on the original thread. Has you problem cleared up?

That's OK by me and I didn't loose any sleep over it.

I am still having the original problem that I reported as it has not gone away. I am beginning to wonder if I am the only one experiencing this problem?

I did run "journalctl" and the output went for many pages and I could not get any useful information from it and you did well to sort out you problem with it.

[vinnywright]

For several days now I have been getting a list of packages that are broken. I have checked the ones that are to be updated and if I did, half my desktop would be gone. What I get is:

:~$ sudo apt full-upgrade
Reading package lists... Done
Building dependency tree... 50%
Building dependency tree       
Reading state information... Done
Starting pkgProblemResolver with broken count: 4
Starting 2 pkgProblemResolver with broken count: 4
Investigating (0) libkf5notifications5 [ amd64 ] < 5.27.0+p16.04+git20161015.0215-0 -> 5.27.0+p16.04+git20161102.1347-0 > ( libs )
Broken libkf5notifications5:amd64 Depends on libkf5notifications-data [ amd64 ] < 5.27.0+p16.04+git20161015.0215-0 -> 5.27.0+p16.04+git20161102.1347-0 > ( libs ) (= 5.27.0+p16.04+git20161015.0215-0)
  Considering libkf5notifications-data:amd64 34 as a solution to libkf5notifications5:amd64 151
  Added libkf5notifications-data:amd64 to the remove list
  Fixing libkf5notifications5:amd64 via keep of libkf5notifications-data:amd64
Investigating (0) libkf5wallet5 [ amd64 ] < 5.27.0+p16.04+git20161011.0609-0 -> 5.27.0+p16.04+git20161102.1415-0 > ( libs )
Broken libkf5wallet5:amd64 Depends on libkf5wallet-data [ amd64 ] < 5.27.0+p16.04+git20161011.0609-0 -> 5.27.0+p16.04+git20161102.1415-0 > ( libs ) (= 5.27.0+p16.04+git20161011.0609-0)
  Considering libkf5wallet-data:amd64 14 as a solution to libkf5wallet5:amd64 88
  Added libkf5wallet-data:amd64 to the remove list
  Fixing libkf5wallet5:amd64 via keep of libkf5wallet-data:amd64
 Try to Re-Instate (0) libkf5notifications-data:amd64
Investigating (0) libkf5notifyconfig5 [ amd64 ] < 5.27.0+p16.04+git20161011.0712-0 -> 5.27.0+p16.04+git20161102.1529-0 > ( libs )
Broken libkf5notifyconfig5:amd64 Depends on libkf5notifyconfig-data [ amd64 ] < 5.27.0+p16.04+git20161011.0712-0 -> 5.27.0+p16.04+git20161102.1529-0 > ( libs ) (= 5.27.0+p16.04+git20161011.0712-0)
  Considering libkf5notifyconfig-data:amd64 9 as a solution to libkf5notifyconfig5:amd64 28
  Added libkf5notifyconfig-data:amd64 to the remove list
  Fixing libkf5notifyconfig5:amd64 via keep of libkf5notifyconfig-data:amd64
 Try to Re-Instate (0) libkf5wallet-data:amd64
 Try to Re-Instate (0) libkf5notifyconfig-data:amd64
Investigating (0) libkf5khtml5 [ amd64 ] < 5.27.0+p16.04+git20161011.0724-0 -> 5.27.0+p16.04+git20161102.1541-0 > ( libs )
Broken libkf5khtml5:amd64 Depends on libkf5khtml-data [ amd64 ] < 5.27.0+p16.04+git20161011.0724-0 -> 5.27.0+p16.04+git20161102.1541-0 > ( libs ) (= 5.27.0+p16.04+git20161011.0724-0)
  Considering libkf5khtml-data:amd64 2 as a solution to libkf5khtml5:amd64 8
  Added libkf5khtml-data:amd64 to the remove list
  Fixing libkf5khtml5:amd64 via keep of libkf5khtml-data:amd64
 Try to Re-Instate (0) libkf5khtml-data:amd64
Done
Calculating upgrade... Done
The following packages were automatically installed and are no longer required:
  libcuda1-361 nvidia-opencl-icd-361
Use 'sudo apt autoremove' to remove them.
The following packages have been kept back:
  libkf5khtml-data libkf5notifications-data libkf5notifyconfig-data libkf5wallet-data
0 to upgrade, 0 to newly install, 0 to remove and 4 not to upgrade.

Is there a way to resolve this problem?

humm ,,,I dont get the errors , but have the same held packages

vinny@vinny-Bonobo-Extreme:~$ sudo apt full-upgrade
[sudo] password for vinny: 
Reading package lists... Done
Building dependency tree       
Reading state information... Done
Calculating upgrade... Done
The following packages have been kept back:
  libkf5khtml-data libkf5notifications-data libkf5notifications-dev libkf5notifyconfig-data libkf5wallet-data
0 upgraded, 0 newly installed, 0 to remove and 5 not upgraded.
vinny@vinny-Bonobo-Extreme:~$

you did do a

sudo apt update

first right.

VINNY

[GreyGeek]

Interesting. Notice the package names on my KDE Neon User Edition.

[NoWorries]

you did do a

sudo apt update

first right.

VINNY

Yes, I always at the start of my morning session do

sudo apt update; sudo apt full-upgrade

I also have an identical list as you have of packages that are held back.

[NoWorries]

Interesting. Notice the package names on my KDE Neon User Edition.

[ATTACH=CONFIG]6789[/ATTACH]

I just did an identical search with Synaptic and get


Which is quite different. Unfortunately I will have to leave now and will get back in a couple of hours to try and sort this out.

[vinnywright]

Hummm and quite different from mine as well ,,,,,,,,,,,,

my guess is

NoWorries is on /dev/unstabel

I am on /dev/stable

and GG is on user

,,,,,,am I correct

vinny@vinny-Bonobo-Extreme:~$ [COLOR=#ff0000]cat /etc/apt/sources.list | grep neon[/COLOR]
deb http://archive.neon.kde.org/stable/ xenial main 
# deb-src http://archive.neon.kde.org/stable/ xenial main

what show thee


VINNY

[GreyGeek]

I am on user


Sent from my iPhone using Tapatalk

[vinnywright]

I am on user


Sent from my iPhone using Tapatalk

so I'm correct on 1 of 2 so far LOL

let me ask this ,,,,,,,,,are your krunners broken as well ,,,,,,,mine crashes as soon as trying to use it .




VINNY

[GreyGeek]

so I'm correct on 1 of 2 so far LOL

let me ask this ,,,,,,,,,are your krunners broken as well ,,,,,,,mine crashes as soon as trying to use it .

VINNY

Nope,works fine!

[NoWorries]

I find this very puzzling as when I enter the command that you did, I get

:~$ cat /etc/apt/sources.list | grep neon
# deb cdrom:[neon devstable _Xenial_ - Build amd64 LIVE Binary 20161005-10:56]/ xenial universe restricted multiverse main

I also have the following from Synaptic Repositories



This shows that I am using the Stable option. I have two laptops which behave in the same way and I used:

http://files.kde.org/neon/images/neo...1047-amd64.iso

To install neon. I did this after paying with the unstable and having troubles, so I did a fresh install with this iso.

[vinnywright]

I find this very puzzling as when I enter the command that you did, I get

:~$ cat /etc/apt/sources.list | grep neon
# deb cdrom:[neon devstable _Xenial_ - Build amd64 LIVE Binary 20161005-10:56]/ xenial universe restricted multiverse main

I also have the following from Synaptic Repositories

[ATTACH=CONFIG]6794[/ATTACH]

This shows that I am using the Stable option. I have two laptops which behave in the same way and I used:

http://files.kde.org/neon/images/neo...1047-amd64.iso

To install neon. I did this after paying with the unstable and having troubles, so I did a fresh install with this iso.

O you have backports turned on .

so "grep" seams to have stopped at the first one (neon) it found ,but should not have,,,,,,, or it's in sources.list.d .

synaptic dose not have it's own Repositories ,,,,but is showing the combined reading of /etc/apt/sources.list and the content of /ext/apt/sources.list.d

what caught my eye was that your Neon source line reads "deb http://archive.neon.kde.org/dev/stable/ xenial main" and mine
"deb http://archive.neon.kde.org/stable/ xenial main" but resolve to the same place.

VINNY

[NoWorries]

Thanks for your insight into my problem. I did uncheck the backports option and edited the neon.list file to be the same as yours but those changes made no difference.

I am beginning to wonder if the damage done by having the backports enabled is the reason for my problems. If so, does this mean a re-install to fix this problem?

[NoWorries]

Just completed a re-install on the Laptop used by my Wife and it still has the same problem as before with broken packages.

So the problem can be in one of two places,

1. package errors or,
2. something amiss in the hidden directories in my home partition.

I am reminded by a posting by Wizard, ie

I would suggest just waiting. I've seen pretty much the same thing in Debian Unstable for the last couple of days except that my installation also offers to remove dolphin.

Let it go for a couple more days or until apt stops offering to remove half your system

So how long to wait?