[Resolved] Re: Upgrade to 17.04 gnome-flashback issue

[NoOp]

On 10/29/17 2:12 AM, Oliver Grawert wrote:
...
> 
> just a side-note, to properly get rid of PPAs you want:
> 
> sudo apt install ppa-purge
> sudo ppa-purge -purge <nameofppa>
> sudo apt update # (to update the package lists)

Thanks Oli, I'm very familiar with ppa-purge.

> 
> though technically update-manager or do-release-upgrade should do
> exactly the same to ensure system integrity after the upgrade.

I've never known either to 'purge' a ppa following an upgrade. I've only
noticed the do-release-upgrade 'disable' any 3rd party PPA's prior to
performing the upgrade, and leaving them in that state when complete ala
/etc/apt/sources.list.d:

deb http://ppa.launchpad.net/unit193/encryption/ubuntu zesty main #
disabled on upgrade to zesty
deb-src http://ppa.launchpad.net/unit193/encryption/ubuntu xenial main
etc.

Note that the package software has not been purged:
$ apt policy veracrypt
veracrypt:
  Installed: 1.21-0vanir1~16.04
  Candidate: 1.21-0vanir1~16.04
  Version table:
 *** 1.21-0vanir1~16.04 500
        500 http://ppa.launchpad.net/unit193/encryption/ubuntu
xenial/main amd64 Packages
        100 /var/lib/dpkg/status

I've always gone back in an check the PPA to see if the author has
upgraded to the upgrade release, if not I can then decide to either run
with the existing version, or ppa-purge and remove entirely.

> 
> you never know what a PPA owner did ... i.e. he could have a patched
> system lib in there that has a higher version than the target system
> you are upgrading to, so that lib would never be upgraded and make the
> system unstable.
> 
> if update-manager/do-release-upgrade didn't remove the PPAs and PPA
> packages, i think there is a bug somewhere in the update-manager code
> ...
> 
> ciao
> 	oli
> 

My sincere regards for the delay in responding to all... I was called
away for the weekend & didn't have access to the machine during that time.

1. The issue wasn't PPA related at all - it was a profile issue (as
mentioned in my original post that the additional user I created had no
issues with gnome-flashback). I can't recall now what I changed, but the
profile started working again just fine after I deleted some .cache and
old tmp & other clutter (the profile has been around since Hardy)

2. I then took Colin's advise and upgraded to 17.10... at first it was
the usual Ubuntu 'everything's broken' nonsense, but several recovery
dpkg attempts & recovery root dpkg etc finally put things back on track
& all is running fine now with the exception of missing the previous
desktop background & some icons on the top panel - all of which can be
replaced by backup config's or putting them back manually. Anyway,
thanks to all that responded.

Note: I've not yet booted into my other desktops that came along with
17.10: GNOME, GNOME on Xorg, Ubuntu, Ubuntu on Xorg - I'll try those later.