Re: [GTALUG] Update borked my system

2023-03-30 Thread Lennart Sorensen via talk
On Thu, Mar 30, 2023 at 01:39:54PM -0400, Evan Leibovitch via talk wrote:
> EPILOGUE
> 
> apt -f install and apt autoremove both reported that everything was fine
> and that I was up-to-date (except for more than 20 packages "held back").
> 
> Sometimes I find Linux troubleshooting a useful mental exercise. Not this
> week.
> Downloaded the latest KDE Neon onto a USB stick.
> Backed up and re-installed without reformatting.
> All seems well though I need to bring back the apps I had.
> 
> Thanks to all who helped.

Does 'dpkg -l |grep ^h' show any packages in state hold (starting with h)?

If it does you could unfreeze them with

echo 'packagename install' | dpkg --set-selections

-- 
Len Sorensen
---
Post to this mailing list talk@gtalug.org
Unsubscribe from this mailing list https://gtalug.org/mailman/listinfo/talk


Re: [GTALUG] Update borked my system

2023-03-30 Thread Evan Leibovitch via talk
EPILOGUE

apt -f install and apt autoremove both reported that everything was fine
and that I was up-to-date (except for more than 20 packages "held back").

Sometimes I find Linux troubleshooting a useful mental exercise. Not this
week.
Downloaded the latest KDE Neon onto a USB stick.
Backed up and re-installed without reformatting.
All seems well though I need to bring back the apps I had.

Thanks to all who helped.

Evan Leibovitch, Toronto Canada
@evanleibovitch / @el56
---
Post to this mailing list talk@gtalug.org
Unsubscribe from this mailing list https://gtalug.org/mailman/listinfo/talk


Re: [GTALUG] Update borked my system

2023-03-28 Thread D. Hugh Redelmeier via talk
Have you tried
apt autoremove
?

I ask because on Fedora, when dnf whines about an update, sometimes
dnf autoremove
removes packages that are barriers to upgrading.

This is not very likely to solve your problem but it is easy to try and 
should not break things.

---
Post to this mailing list talk@gtalug.org
Unsubscribe from this mailing list https://gtalug.org/mailman/listinfo/talk


Re: [GTALUG] Update borked my system

2023-03-28 Thread Evan Leibovitch via talk
On Tue, Mar 28, 2023 at 7:51 AM Lennart Sorensen <
lsore...@csclub.uwaterloo.ca> wrote:

>
> Did you try 'apt -f install' to see if it can fix the problems?
>

No, that's first on my list to do.

I also wonder what the heck Ubuntu has done to apt, because that's not what
> apt's output is normally like.
>

This is KDE Neon, which invented 'pkcon' to act as a supposedly-superset
replacement for apt used for updating.
https://www.reddit.com/r/kde/comments/mxq3mf/what_is_pkcon_update_and_why_does_kde_neon_use_it/

- Evan
---
Post to this mailing list talk@gtalug.org
Unsubscribe from this mailing list https://gtalug.org/mailman/listinfo/talk


Re: [GTALUG] Update borked my system

2023-03-28 Thread Lennart Sorensen via talk
On Mon, Mar 27, 2023 at 04:20:12AM -0400, Evan Leibovitch via talk wrote:
> Hi all.
> 
> Wondering if anyone can help with this.
> 
> A power glitch happened while I was updating a KDE Neon system and on
> reboot all sorts of things are wonky. KDE starts up fine on bootup but
> there are no window toolbars. All apps load at the upper right of the
> screen and can't be moved because there is nothing to drag and no keyboard
> shortcuts will work.
> 
> An attempt to complete the upgrade using `pkcon update` (the KDE Neon
> version of `apt dist-upgrade`) spits out a slew of errors (attached). The
> database is not corrupt (`pkcon repair` reports no problems) but there seem
> to be major pieces either refusing to install or "held back".
> 
> Is there a command that can let me just force everything to the current
> stable release without me having to go through the whole
> install-from-usb-stick thing? There's nothing critical on that installation
> so a fresh instrall is more of a PITA than critical problem. Still, it took
> me a lot of time to set up my apps
> 
> Thanks for any help. I like KDE Neon, it's a like "Kubuntu without snaps
> but with the newest KDE".
> 
> Evan Leibovitch, Toronto Canada
> @evanleibovitch / @el56

> 
> WARNING: apt does not have a stable CLI interface. Use with caution in 
> scripts.
> 
> Reading package lists...
> Building dependency tree...
> Reading state information...
> Calculating upgrade...Starting pkgProblemResolver with broken count: 9
> Starting 2 pkgProblemResolver with broken count: 9
> Investigating (0) shim-signed:amd64 < 1.51+15.4-0ubuntu9 -> 
> 1.51.3+15.7-0ubuntu1 @ii umU Ib >
> Broken shim-signed:amd64 Depends on grub-efi-amd64-signed:amd64 < 
> 1.182~22.04.1+2.06-2ubuntu10 | 1.187.3~22.04.1+2.06-2ubuntu14.1 @ii pumH > 
> (>= 1.187.2~)
>   Considering grub-efi-amd64-signed:amd64 10201 as a solution to 
> shim-signed:amd64 5100
>   Holding Back shim-signed:amd64 rather than change 
> grub-efi-amd64-signed:amd64
> Broken shim-signed:amd64 Depends on grub-efi-arm64-signed:amd64 < none @un mH 
> > (>= 1.187.2~)
>   Or group keep for shim-signed:amd64
> Investigating (0) kwin-x11:amd64 < 
> 4:5.25.5-0xneon+22.04+jammy+release+build14 -> 
> 4:5.27.3-0xneon+22.04+jammy+release+build33 @ii umU Ib >
> Broken kwin-x11:amd64 Depends on kwin-common:amd64 < 
> 4:5.25.5-0xneon+22.04+jammy+release+build14 @ii mK Ib > (= 
> 4:5.27.3-0xneon+22.04+jammy+release+build33)
>   Considering kwin-common:amd64 11 as a solution to kwin-x11:amd64 209
>   Removing kwin-x11:amd64 rather than change kwin-common:amd64
> Investigating (0) kwin-wayland:amd64 < 
> 4:5.25.5-0xneon+22.04+jammy+release+build14 -> 
> 4:5.27.3-0xneon+22.04+jammy+release+build33 @ii umU Ib >
> Broken kwin-wayland:amd64 Depends on kwin-common:amd64 < 
> 4:5.25.5-0xneon+22.04+jammy+release+build14 @ii mK Ib > (= 
> 4:5.27.3-0xneon+22.04+jammy+release+build33)
>   Considering kwin-common:amd64 11 as a solution to kwin-wayland:amd64 103
>   Removing kwin-wayland:amd64 rather than change kwin-common:amd64
> Investigating (0) kwin-common:amd64 < 
> 4:5.25.5-0xneon+22.04+jammy+release+build14 @ii mK Ib >
> Broken kwin-common:amd64 Depends on kwin-data:amd64 < 
> 4:5.25.5-0xneon+22.04+jammy+release+build14 -> 
> 4:5.27.3-0xneon+22.04+jammy+release+build33 @ii umU Ib > (= 
> 4:5.25.5-0xneon+22.04+jammy+release+build14)
>   Considering kwin-data:amd64 0 as a solution to kwin-common:amd64 11
>   Added kwin-data:amd64 to the remove list
> Broken kwin-common:amd64 Depends on libkwineffects13:amd64 < 
> 4:5.25.5-0xneon+22.04+jammy+release+build14 -> 
> 4:5.27.3-0xneon+22.04+jammy+release+build33 @ii umU > (= 
> 4:5.25.5-0xneon+22.04+jammy+release+build14)
>   Considering libkwineffects13:amd64 -1 as a solution to kwin-common:amd64 11
>   Added libkwineffects13:amd64 to the remove list
>   Fixing kwin-common:amd64 via keep of kwin-data:amd64
>   Fixing kwin-common:amd64 via keep of libkwineffects13:amd64
> Investigating (0) libkwineffects14:amd64 < none -> 
> 4:5.27.3-0xneon+22.04+jammy+release+build33 @un uN Ib >
> Broken libkwineffects14:amd64 Breaks on libkwineffects13:amd64 < 
> 4:5.25.5-0xneon+22.04+jammy+release+build14 | 
> 4:5.27.3-0xneon+22.04+jammy+release+build33 @ii umH > (< 4:5.26.3)
>   Considering libkwineffects13:amd64 -1 as a solution to 
> libkwineffects14:amd64 8
>   Upgrading libkwineffects13:amd64 due to Breaks field in 
> libkwineffects14:amd64
>   Conflicts//Breaks against version 4:5.24.7-0ubuntu0.1 for libkwineffects13 
> but that is not InstVer, ignoring
>   Conflicts//Breaks against version 4:5.24.4-0ubuntu1 for libkwineffects13 
> but that is not InstVer, ignoring
> Investigating (0) libprocessui9:amd64 < 
> 4:5.26.5-0xneon+22.04+jammy+release+build14 -> 
> 4:5.27.3-0xneon+22.04+jammy+release+build19 @ii umU Ib >
> Broken libprocessui9:amd64 Depends on libqt5webenginecore5:amd64 < 
> 5.15.10+dfsg-3 @ii mK Ib > (>= 5.15.11+dfsg)
>   Considering libqt5webenginecore5:amd64 0 as a solution to 
> 

Re: [GTALUG] Update borked my system

2023-03-28 Thread BCLUG via talk

Bob Jonkman via talk wrote on 2023-03-27 21:06:

To drag a window without toolbars press ALT and drag the window from its 
middle.


Relatedly, Alt+Right-button-drag resizes.

Can be handy...


rb

---
Post to this mailing list talk@gtalug.org
Unsubscribe from this mailing list https://gtalug.org/mailman/listinfo/talk


Re: [GTALUG] Update borked my system

2023-03-28 Thread Evan Leibovitch via talk
Hi, Bob.

On Tue, Mar 28, 2023 at 12:08 AM Bob Jonkman via talk 
wrote:


> To drag a window without toolbars press ALT and drag the window from its
> middle.
>

First thing I tried; this has worked for me before, not this time.

IMnsHO there should be no way for programming APIs to remove vital tools
> like scrollbars, windows close and minimize buttons, and grabbers for
> resize and move...
>

As I mentioned, power glitch during an update. I'm really hesitant to blame
this on the system.

- Evan
---
Post to this mailing list talk@gtalug.org
Unsubscribe from this mailing list https://gtalug.org/mailman/listinfo/talk


Re: [GTALUG] Update borked my system

2023-03-27 Thread Bob Jonkman via talk

Hi Evan: This is not a fix, and may not even work on KDE (I'm using MATE)...

To drag a window without toolbars press ALT and drag the window from its 
middle.


I find this useful for those broken UI modal windows that can't be sized 
but are too big to fit on my netbook screen (1024x640) and so the "OK" 
and "Cancel" buttons are below the visible screen.


IMnsHO there should be no way for programming APIs to remove vital tools 
like scrollbars, windows close and minimize buttons, and grabbers for 
resize and move...


--Bob.


On 2023-03-27 04:20, Evan Leibovitch via talk wrote:

Hi all.

Wondering if anyone can help with this.

A power glitch happened while I was updating a KDE Neon system and on
reboot all sorts of things are wonky. KDE starts up fine on bootup but
there are no window toolbars. All apps load at the upper right of the
screen and can't be moved because there is nothing to drag and no keyboard
shortcuts will work.

An attempt to complete the upgrade using `pkcon update` (the KDE Neon
version of `apt dist-upgrade`) spits out a slew of errors (attached). The
database is not corrupt (`pkcon repair` reports no problems) but there seem
to be major pieces either refusing to install or "held back".

Is there a command that can let me just force everything to the current
stable release without me having to go through the whole
install-from-usb-stick thing? There's nothing critical on that installation
so a fresh instrall is more of a PITA than critical problem. Still, it took
me a lot of time to set up my apps

Thanks for any help. I like KDE Neon, it's a like "Kubuntu without snaps
but with the newest KDE".

Evan Leibovitch, Toronto Canada
@evanleibovitch / @el56


---
Post to this mailing list talk@gtalug.org
Unsubscribe from this mailing list https://gtalug.org/mailman/listinfo/talk

---
Post to this mailing list talk@gtalug.org
Unsubscribe from this mailing list https://gtalug.org/mailman/listinfo/talk


Re: [GTALUG] Update borked my system

2023-03-27 Thread BCLUG via talk


A couple thoughts, as it's getting late... I've pasted the latest 
versions available to a KDEneon distro below, ready to run.



Maybe try these (might require a --reinstall switch passed), see if 
there are fewer broken packages afterwards?:



apt install grub-efi-amd64-bin=2.06-2ubuntu14.1
apt install grub-efi-amd64-signed=1.187.3~22.04.1+2.06-2ubuntu14.1

apt install gwenview=4:22.12.3-0xneon+22.04+jammy+release+build15
apt install kdeconnect=22.12.3-0xneon+22.04+jammy+release+build22

apt install kwin-x11=4:5.27.3-0xneon+22.04+jammy+release+build33
apt install kwin-common=4:5.27.3-0xneon+22.04+jammy+release+build33
apt install kwin-data=4:5.27.3-0xneon+22.04+jammy+release+build33

apt install 
libkf5filemetadata-bin=5.104.0-0xneon+22.04+jammy+release+build15


apt install libkf5sysguard-data=4:5.27.3-0xneon+22.04+jammy+release+build19

apt install plasma-nm=4:5.27.3-0xneon+22.04+jammy+release+build20

apt install shim-signed=1.51.3+15.7-0ubuntu1

BONUS:

apt install neon-desktop=4+p22.04+trelease+git20230227.1438


## kwin-wayland
## kwin-wayland-backend-drm




---
Post to this mailing list talk@gtalug.org
Unsubscribe from this mailing list https://gtalug.org/mailman/listinfo/talk


Re: [GTALUG] Update borked my system

2023-03-27 Thread BCLUG via talk

Evan Leibovitch via talk wrote on 2023-03-27 01:20:

Is there a command that can let me just force everything to the current 
stable release without me having to go through the whole 
install-from-usb-stick thing?


I recently did a silly thing: upgraded my system Python installation via 
a PPA.


That meant that a `do-release-upgrade` took me to a version of Python 
that was slightly behind the one installed via PPA.



I had all kinds of problems, sounding similar to yours.


This post put me on the right track, allowed me to fix it quite painlessly:

https://www.reddit.com/r/Ubuntu/comments/10b9rsr/comment/j4dqhqx


Lessons learnt:

* mess with Python in a venv
* man apt-patterns
* apt mark minimize-manual


I wonder if this will produce more legible output:

apt list ?broken


rb

---
Post to this mailing list talk@gtalug.org
Unsubscribe from this mailing list https://gtalug.org/mailman/listinfo/talk


Re: [GTALUG] Update borked my system

2023-03-27 Thread BCLUG via talk

Evan Leibovitch via talk wrote on 2023-03-27 01:20:

I like KDE Neon, it's a like "Kubuntu without snaps but with the newest 
KDE".


Yeah, KDEneon is *great*.


It does have snaps however.  Never been a problem, for me at least.


Try `snap list` to see them.

I have chromium, "bare", core18, core20, cups, gnome-stuff 1 & 2, 
gtk-common-themes, and snapd in my list.



Anywho, I'm looking at your package error list, see if I can remember 
how to fix that.



rb


---
Post to this mailing list talk@gtalug.org
Unsubscribe from this mailing list https://gtalug.org/mailman/listinfo/talk


[GTALUG] Update borked my system

2023-03-27 Thread Evan Leibovitch via talk
Hi all.

Wondering if anyone can help with this.

A power glitch happened while I was updating a KDE Neon system and on
reboot all sorts of things are wonky. KDE starts up fine on bootup but
there are no window toolbars. All apps load at the upper right of the
screen and can't be moved because there is nothing to drag and no keyboard
shortcuts will work.

An attempt to complete the upgrade using `pkcon update` (the KDE Neon
version of `apt dist-upgrade`) spits out a slew of errors (attached). The
database is not corrupt (`pkcon repair` reports no problems) but there seem
to be major pieces either refusing to install or "held back".

Is there a command that can let me just force everything to the current
stable release without me having to go through the whole
install-from-usb-stick thing? There's nothing critical on that installation
so a fresh instrall is more of a PITA than critical problem. Still, it took
me a lot of time to set up my apps

Thanks for any help. I like KDE Neon, it's a like "Kubuntu without snaps
but with the newest KDE".

Evan Leibovitch, Toronto Canada
@evanleibovitch / @el56

WARNING: apt does not have a stable CLI interface. Use with caution in scripts.

Reading package lists...
Building dependency tree...
Reading state information...
Calculating upgrade...Starting pkgProblemResolver with broken count: 9
Starting 2 pkgProblemResolver with broken count: 9
Investigating (0) shim-signed:amd64 < 1.51+15.4-0ubuntu9 -> 
1.51.3+15.7-0ubuntu1 @ii umU Ib >
Broken shim-signed:amd64 Depends on grub-efi-amd64-signed:amd64 < 
1.182~22.04.1+2.06-2ubuntu10 | 1.187.3~22.04.1+2.06-2ubuntu14.1 @ii pumH > (>= 
1.187.2~)
  Considering grub-efi-amd64-signed:amd64 10201 as a solution to 
shim-signed:amd64 5100
  Holding Back shim-signed:amd64 rather than change grub-efi-amd64-signed:amd64
Broken shim-signed:amd64 Depends on grub-efi-arm64-signed:amd64 < none @un mH > 
(>= 1.187.2~)
  Or group keep for shim-signed:amd64
Investigating (0) kwin-x11:amd64 < 4:5.25.5-0xneon+22.04+jammy+release+build14 
-> 4:5.27.3-0xneon+22.04+jammy+release+build33 @ii umU Ib >
Broken kwin-x11:amd64 Depends on kwin-common:amd64 < 
4:5.25.5-0xneon+22.04+jammy+release+build14 @ii mK Ib > (= 
4:5.27.3-0xneon+22.04+jammy+release+build33)
  Considering kwin-common:amd64 11 as a solution to kwin-x11:amd64 209
  Removing kwin-x11:amd64 rather than change kwin-common:amd64
Investigating (0) kwin-wayland:amd64 < 
4:5.25.5-0xneon+22.04+jammy+release+build14 -> 
4:5.27.3-0xneon+22.04+jammy+release+build33 @ii umU Ib >
Broken kwin-wayland:amd64 Depends on kwin-common:amd64 < 
4:5.25.5-0xneon+22.04+jammy+release+build14 @ii mK Ib > (= 
4:5.27.3-0xneon+22.04+jammy+release+build33)
  Considering kwin-common:amd64 11 as a solution to kwin-wayland:amd64 103
  Removing kwin-wayland:amd64 rather than change kwin-common:amd64
Investigating (0) kwin-common:amd64 < 
4:5.25.5-0xneon+22.04+jammy+release+build14 @ii mK Ib >
Broken kwin-common:amd64 Depends on kwin-data:amd64 < 
4:5.25.5-0xneon+22.04+jammy+release+build14 -> 
4:5.27.3-0xneon+22.04+jammy+release+build33 @ii umU Ib > (= 
4:5.25.5-0xneon+22.04+jammy+release+build14)
  Considering kwin-data:amd64 0 as a solution to kwin-common:amd64 11
  Added kwin-data:amd64 to the remove list
Broken kwin-common:amd64 Depends on libkwineffects13:amd64 < 
4:5.25.5-0xneon+22.04+jammy+release+build14 -> 
4:5.27.3-0xneon+22.04+jammy+release+build33 @ii umU > (= 
4:5.25.5-0xneon+22.04+jammy+release+build14)
  Considering libkwineffects13:amd64 -1 as a solution to kwin-common:amd64 11
  Added libkwineffects13:amd64 to the remove list
  Fixing kwin-common:amd64 via keep of kwin-data:amd64
  Fixing kwin-common:amd64 via keep of libkwineffects13:amd64
Investigating (0) libkwineffects14:amd64 < none -> 
4:5.27.3-0xneon+22.04+jammy+release+build33 @un uN Ib >
Broken libkwineffects14:amd64 Breaks on libkwineffects13:amd64 < 
4:5.25.5-0xneon+22.04+jammy+release+build14 | 
4:5.27.3-0xneon+22.04+jammy+release+build33 @ii umH > (< 4:5.26.3)
  Considering libkwineffects13:amd64 -1 as a solution to libkwineffects14:amd64 
8
  Upgrading libkwineffects13:amd64 due to Breaks field in libkwineffects14:amd64
  Conflicts//Breaks against version 4:5.24.7-0ubuntu0.1 for libkwineffects13 
but that is not InstVer, ignoring
  Conflicts//Breaks against version 4:5.24.4-0ubuntu1 for libkwineffects13 but 
that is not InstVer, ignoring
Investigating (0) libprocessui9:amd64 < 
4:5.26.5-0xneon+22.04+jammy+release+build14 -> 
4:5.27.3-0xneon+22.04+jammy+release+build19 @ii umU Ib >
Broken libprocessui9:amd64 Depends on libqt5webenginecore5:amd64 < 
5.15.10+dfsg-3 @ii mK Ib > (>= 5.15.11+dfsg)
  Considering libqt5webenginecore5:amd64 0 as a solution to libprocessui9:amd64 
7
  Removing libprocessui9:amd64 rather than change libqt5webenginecore5:amd64
Investigating (0) libqt5webenginewidgets5:amd64 < 5.15.10+dfsg-3 -> 
5.15.11+dfsg-6+22.04+jammy+unstable+build52 @ii umU Ib >
Broken libqt5webenginewidgets5:amd64 Depends on