Upgrade to 17.04 gnome-flashback issue

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
28 messages Options
12
Reply | Threaded
Open this post in threaded view
|

Upgrade to 17.04 gnome-flashback issue

NoOp-4
Yesterday I upgraded one of my 16.04 systems to 17.04. I primarily only
run gnome-flashback (metacity) as my desktop, but also have GNOME,
Gnome-classic and Ubuntu installed. Using lightdm I can sucessfully log
into and maintain a desktop with:

GNOME
GNOME Classic

When I log into the following, I got the desktop for about 3-4 seconds &
then blank screen with flashing cursor:

GNOME-Flashback (Compiz)
GNOME-Flashback (Metacity)
GNOME on Wayland

I can Ctrl-Alt|F1 and log in without issue.

I installed gdm3 and set the greeter login to gdm instead of lightdm and
can now login w/o issue to GNOME on Wayland, GNOME, GNOME Classic.

I Created another user for testing, and that user can login, load and use:
GNOME
GNOME Classic
GNOME-Flashback (Compiz)
GNOME-Flashback (Metacity)
GNOME on Wayland
so the issue must be in my regular profile. Any suggestions on what I
should remove/add/check in my regular profile to get gnome-flashback
working again?

Note: all packages are updated, and the issue occured with or without
ppa's enabled.


--
ubuntu-users mailing list
[hidden email]
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-users
Reply | Threaded
Open this post in threaded view
|

Re: Upgrade to 17.04 gnome-flashback issue

Ralf Mardorf-2
On Sat, 28 Oct 2017 18:06:28 -0700, NoOp wrote:
>Note: all packages are updated, and the issue occured with or without
>ppa's enabled.

Once third party software is installed, disabling a PPA gains
absolutely nothing. You probably want to point out, with or without
third party software installed?


--
ubuntu-users mailing list
[hidden email]
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-users
Reply | Threaded
Open this post in threaded view
|

Re: Upgrade to 17.04 gnome-flashback issue

NoOp-4
On 10/28/17 9:21 PM, Ralf Mardorf wrote:
> On Sat, 28 Oct 2017 18:06:28 -0700, NoOp wrote:
>>Note: all packages are updated, and the issue occured with or without
>>ppa's enabled.
>
> Once third party software is installed, disabling a PPA gains
> absolutely nothing. You probably want to point out, with or without
> third party software installed?
>
>

3rd party software PPA's are disabled on upgrade, so all 16.04 PPA
packages remain 16.04 following the 17.04 upgrade. Renabling, updating,
and upgrading to 17.04 versions made no difference - was my point


--
ubuntu-users mailing list
[hidden email]
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-users
Reply | Threaded
Open this post in threaded view
|

Re: Upgrade to 17.04 gnome-flashback issue

Ralf Mardorf-2
On Sat, 28 Oct 2017 22:00:18 -0700, NoOp wrote:
>3rd party software PPA's are disabled on upgrade, so all 16.04 PPA
>packages remain 16.04 following the 17.04 upgrade. Renabling, updating,
>and upgrading to 17.04 versions made no difference - was my point

It depends on the used PPA, if already installed third party software
has got impact on official packages or not. It even depends on the
PPA's packages, if they are upgraded or not, e.g. if a package is
available by a PPA and by official packages or not by official packages.

The issue you experience might have nothing to do with the used PPAs,
but actually your install is a tainted install. That there's no
difference with or without PPAs enabled means nothing at all.


--
ubuntu-users mailing list
[hidden email]
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-users
Reply | Threaded
Open this post in threaded view
|

Re: Upgrade to 17.04 gnome-flashback issue

NoOp-4
On 10/28/17 10:19 PM, Ralf Mardorf wrote:

> On Sat, 28 Oct 2017 22:00:18 -0700, NoOp wrote:
>>3rd party software PPA's are disabled on upgrade, so all 16.04 PPA
>>packages remain 16.04 following the 17.04 upgrade. Renabling, updating,
>>and upgrading to 17.04 versions made no difference - was my point
>
> It depends on the used PPA, if already installed third party software
> has got impact on official packages or not. It even depends on the
> PPA's packages, if they are upgraded or not, e.g. if a package is
> available by a PPA and by official packages or not by official packages.
>
> The issue you experience might have nothing to do with the used PPAs,
> but actually your install is a tainted install. That there's no
> difference with or without PPAs enabled means nothing at all.
>
>

Sorry, I'm not in the mood to entertain you further on whether my adding
information about the PPAs was correct or not. If/when you care to offer
valid suggestions regarding my original question maybe we'll continue...
until then I'll consider this discussion finished.




--
ubuntu-users mailing list
[hidden email]
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-users
Reply | Threaded
Open this post in threaded view
|

Re: Upgrade to 17.04 gnome-flashback issue

ubuntu-users mailing list
In reply to this post by Ralf Mardorf-2
29 October 2017  at 6:19, Ralf Mardorf wrote:
Re: Upgrade to 17.04 gnome-flashbac (at least in part)

>It depends on the used PPA, if already installed third party software
>has got impact on official packages or not. It even depends on the
>PPA's packages, if they are upgraded or not, e.g. if a package is
>available by a PPA and by official packages or not by official packages.

>The issue you experience might have nothing to do with the used PPAs,
>but actually your install is a tainted install. That there's no
>difference with or without PPAs enabled means nothing at all.

Nieve question, if one (test) user can run and the main user can't, are PPA's
likely issues?

--
ubuntu-users mailing list
[hidden email]
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-users
Reply | Threaded
Open this post in threaded view
|

Re: Upgrade to 17.04 gnome-flashback issue

Colin Law
In reply to this post by NoOp-4


On 29 Oct 2017 1:09 a.m., "NoOp" <[hidden email]> wrote:
Yesterday I upgraded one of my 16.04 systems to 17.04.

Would it be worthwhile going to 17.10? Presumably that is where you are going anyway and it might make a difference. It could be a config dependent bug that is only seen with certain user config.

To some extent Ralf is right in that ideally one should use ppa-purge before upgrade in order to uninstall the ppa packages and restore the standard ones. However I think it most unlikely that this is a factor here.

Colin

I primarily only
run gnome-flashback (metacity) as my desktop, but also have GNOME,
Gnome-classic and Ubuntu installed. Using lightdm I can sucessfully log
into and maintain a desktop with:

GNOME
GNOME Classic

When I log into the following, I got the desktop for about 3-4 seconds &
then blank screen with flashing cursor:

GNOME-Flashback (Compiz)
GNOME-Flashback (Metacity)
GNOME on Wayland

I can Ctrl-Alt|F1 and log in without issue.

I installed gdm3 and set the greeter login to gdm instead of lightdm and
can now login w/o issue to GNOME on Wayland, GNOME, GNOME Classic.

I Created another user for testing, and that user can login, load and use:
GNOME
GNOME Classic
GNOME-Flashback (Compiz)
GNOME-Flashback (Metacity)
GNOME on Wayland
so the issue must be in my regular profile. Any suggestions on what I
should remove/add/check in my regular profile to get gnome-flashback
working again?

Note: all packages are updated, and the issue occured with or without
ppa's enabled.


--
ubuntu-users mailing list
[hidden email]
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-users


--
ubuntu-users mailing list
[hidden email]
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-users
Reply | Threaded
Open this post in threaded view
|

Re: Upgrade to 17.04 gnome-flashback issue

Oliver Grawert
In reply to this post by NoOp-4
hi,
Am Samstag, den 28.10.2017, 22:50 -0700 schrieb NoOp:
> ...
> Sorry, I'm not in the mood to entertain you further on whether my
> adding
> information about the PPAs was correct or not. If/when you care to
> offer
> valid suggestions regarding my original question maybe we'll
> continue...
> until then I'll consider this discussion finished.
>

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)

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

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
--
ubuntu-users mailing list
[hidden email]
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-users

signature.asc (188 bytes) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: Upgrade to 17.04 gnome-flashback issue

Liam Proven
In reply to this post by NoOp-4
On 29 October 2017 at 02:06, NoOp <[hidden email]> wrote:
> Yesterday I upgraded one of my 16.04 systems to 17.04.

Why update the current supported LTS release to an obsolete unsupported release?

> I primarily only
> run gnome-flashback (metacity) as my desktop,

If you want the legacy desktop experience, there are better choices
than GNOME. Maté is an obvious one, or Cinnamon. They are intended to
provide a start-menu-and-taskbar Windows-style desktop. GNOME Shell
isn't and bodges it.

> but also have GNOME,
> Gnome-classic and Ubuntu installed.

Do you mean Unity? Ubuntu is the OS they are all running on.

That is a complex mixture. It is less likely to upgrade cleanly and
successfully.

If you have a separate /home partition, as you should, then you'd be
better off doing a clean reinstall with Maté.

--
Liam Proven • Profile: https://about.me/liamproven
Email: [hidden email] • Google Mail/Talk/Plus: [hidden email]
Twitter/Facebook/Flickr: lproven • Skype/LinkedIn/AIM/Yahoo: liamproven
UK: +44 7939-087884 • ČR/WhatsApp/Telegram/Signal: +420 702 829 053

--
ubuntu-users mailing list
[hidden email]
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-users
Reply | Threaded
Open this post in threaded view
|

Re: Upgrade to 17.04 gnome-flashback issue

Colin Law
On 29 October 2017 at 15:38, Liam Proven <[hidden email]> wrote:
>
> Why update the current supported LTS release to an obsolete unsupported release?

17.04 is actually supported till Jan 2018 [1]

>
> If you have a separate /home partition, as you should, then you'd be
> better off doing a clean reinstall with Maté.

It is not necessary to have a separate home partition to re-install
without overwriting /home. On the what to do dialog when installing,
select Something Else, select the existing '/' partition and tell it
to use it as '/' and *not* to reformat. Then it will install the new
OS there but leave /home as it is.  Needless to say you should back
everything important up before doing that.

Colin

[1] https://wiki.ubuntu.com/Releases

--
ubuntu-users mailing list
[hidden email]
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-users
Reply | Threaded
Open this post in threaded view
|

Re: Upgrade to 17.04 gnome-flashback issue

Liam Proven
On 29 October 2017 at 16:48, Colin Law <[hidden email]> wrote:
> On 29 October 2017 at 15:38, Liam Proven <[hidden email]> wrote:
>>
>> Why update the current supported LTS release to an obsolete unsupported release?
>
> 17.04 is actually supported till Jan 2018 [1]

I defer.

/Nearly/ obsolete. :-)


> It is not necessary to have a separate home partition to re-install
> without overwriting /home. On the what to do dialog when installing,
> select Something Else, select the existing '/' partition and tell it
> to use it as '/' and *not* to reformat. Then it will install the new
> OS there but leave /home as it is.  Needless to say you should back
> everything important up before doing that.

True. I've tried it. It's scary but it works.

But you can't dual-boot that way.

--
Liam Proven • Profile: https://about.me/liamproven
Email: [hidden email] • Google Mail/Talk/Plus: [hidden email]
Twitter/Facebook/Flickr: lproven • Skype/LinkedIn/AIM/Yahoo: liamproven
UK: +44 7939-087884 • ČR/WhatsApp/Telegram/Signal: +420 702 829 053

--
ubuntu-users mailing list
[hidden email]
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-users
Reply | Threaded
Open this post in threaded view
|

Re: Upgrade to 17.04 gnome-flashback issue

Colin Law
On 29 October 2017 at 16:23, Liam Proven <[hidden email]> wrote:

> On 29 October 2017 at 16:48, Colin Law <[hidden email]> wrote:
>> On 29 October 2017 at 15:38, Liam Proven <[hidden email]> wrote:
>>>
>>> Why update the current supported LTS release to an obsolete unsupported release?
>>
>> 17.04 is actually supported till Jan 2018 [1]
>
> I defer.
>
> /Nearly/ obsolete. :-)
>
>
>> It is not necessary to have a separate home partition to re-install
>> without overwriting /home. On the what to do dialog when installing,
>> select Something Else, select the existing '/' partition and tell it
>> to use it as '/' and *not* to reformat. Then it will install the new
>> OS there but leave /home as it is.  Needless to say you should back
>> everything important up before doing that.
>
> True. I've tried it. It's scary but it works.
>
> But you can't dual-boot that way.

True, if you want the same home folder in both boots.
Actually not entirely true, you could link /home in one boot to /home
in the other.

Colin

--
ubuntu-users mailing list
[hidden email]
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-users
Reply | Threaded
Open this post in threaded view
|

Re: Upgrade to 17.04 gnome-flashback issue

Liam Proven
On 29 October 2017 at 17:30, Colin Law <[hidden email]> wrote:
>
> True, if you want the same home folder in both boots.
> Actually not entirely true, you could link /home in one boot to /home
> in the other.

OK, I hadn't thought of that. Might work. Tricky to do though.

--
Liam Proven • Profile: https://about.me/liamproven
Email: [hidden email] • Google Mail/Talk/Plus: [hidden email]
Twitter/Facebook/Flickr: lproven • Skype/LinkedIn/AIM/Yahoo: liamproven
UK: +44 7939-087884 • ČR/WhatsApp/Telegram/Signal: +420 702 829 053

--
ubuntu-users mailing list
[hidden email]
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-users
Reply | Threaded
Open this post in threaded view
|

Re: Upgrade to 17.04 gnome-flashback issue

Colin Law
On 29 October 2017 at 16:44, Liam Proven <[hidden email]> wrote:
> On 29 October 2017 at 17:30, Colin Law <[hidden email]> wrote:
>>
>> True, if you want the same home folder in both boots.
>> Actually not entirely true, you could link /home in one boot to /home
>> in the other.
>
> OK, I hadn't thought of that. Might work. Tricky to do though.

I wasn't suggesting it was necessarily a good idea, just pointing out
the possibility.

Colin

--
ubuntu-users mailing list
[hidden email]
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-users
Reply | Threaded
Open this post in threaded view
|

Re: Upgrade to 17.04 gnome-flashback issue

Ralf Mardorf-2
On Sun, 29 Oct 2017 16:51:42 +0000, Colin Law wrote:

>On 29 October 2017 at 16:44, Liam Proven <[hidden email]> wrote:
>> On 29 October 2017 at 17:30, Colin Law <[hidden email]> wrote:  
>>>
>>> True, if you want the same home folder in both boots.
>>> Actually not entirely true, you could link /home in one boot
>>> to /home in the other.  
>>
>> OK, I hadn't thought of that. Might work. Tricky to do though.  
>
>I wasn't suggesting it was necessarily a good idea, just pointing out
>the possibility.

JFTR if /home shouldn't have it's own partition, it's possible to bind
it. I'm doing this for /boot to avoid chainloading, since I prefer the
syslinux boot loader:

[weremouse@moonstudio ~]$ tail -1 /etc/fstab
/mnt/archlinux/.boot/ubuntu_moonstudio/boot /boot          none   bind              0 0
[weremouse@moonstudio ~]$ lsb_release -d
Description: Ubuntu 16.04.3 LTS


--
ubuntu-users mailing list
[hidden email]
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-users
Reply | Threaded
Open this post in threaded view
|

Re: hidden boot ? (was: Upgrade to 17.04 gnome-flashback issue)

Oliver Grawert
hi,
Am Sonntag, den 29.10.2017, 19:23 +0100 schrieb Ralf Mardorf:

>  I'm doing this for /boot to avoid chainloading, since I prefer
> the
> syslinux boot loader:
>
> [weremouse@moonstudio ~]$ tail -1 /etc/fstab
> /mnt/archlinux/.boot/ubuntu_moonstudio/boot
> /boot          none   bind              0 0
> [weremouse@moonstudio ~]$ lsb_release -d
> Description: Ubuntu 16.04.3 LTS
>
>
just out of interest, is boot actually hidden in arch ( as /.boot/ ) ? 
or is that just your personal special setup ?

ciao
        oli
--
ubuntu-users mailing list
[hidden email]
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-users

signature.asc (188 bytes) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: hidden boot ? (was: Upgrade to 17.04 gnome-flashback issue)

Ralf Mardorf-2
On Mon, 30 Oct 2017 13:15:49 +0100, Oliver Grawert wrote:

>hi,
>Am Sonntag, den 29.10.2017, 19:23 +0100 schrieb Ralf Mardorf:
>>  I'm doing this for /boot to avoid chainloading, since I prefer
>> the
>> syslinux boot loader:
>>
>> [weremouse@moonstudio ~]$ tail -1 /etc/fstab
>> /mnt/archlinux/.boot/ubuntu_moonstudio/boot
>> /boot          none   bind              0 0
>> [weremouse@moonstudio ~]$ lsb_release -d
>> Description: Ubuntu 16.04.3 LTS
>>
>>  
>just out of interest, is boot actually hidden in arch ( as /.boot/ ) ? 
>or is that just your personal special setup ?

Hi,

Arch Linux follows FHS. The Arch kernels, as well as the syslinux
bootloader files are located in /boot [1]. Other than grub, syslinux
needs to chainload or to have the kernels of different distros in one
root directory. For this reason the kernels of a vintage Suse, a
vintage Ubuntu and Ubuntu 16.04 are in the hidden /.boot, so I could
backup the Arch install using the asterisk to bachup all, excepted of
the kernels of other distros.

[1]
[rocketmouse@archlinux ~]$ ls -l /boot/
total 163712
-rw-r--r-- 1 root root 26714283 Oct 30 12:08 initramfs-linux-fallback.img
-rw-r--r-- 1 root root  9939644 Oct 30 12:08 initramfs-linux.img
-rw-r--r-- 1 root root 26520961 Oct 30 12:07 initramfs-linux-rt-cornflower-fallback.img
-rw-r--r-- 1 root root  9914761 Oct 30 12:07 initramfs-linux-rt-cornflower.img
-rw-r--r-- 1 root root 26601774 Oct 30 12:07 initramfs-linux-rt-fallback.img
-rw-r--r-- 1 root root  9923022 Oct 30 12:07 initramfs-linux-rt.img
-rw-r--r-- 1 root root 26510867 Oct 30 12:07 initramfs-linux-rt-pussytoes-fallback.img
-rw-r--r-- 1 root root  9914166 Oct 30 12:07 initramfs-linux-rt-pussytoes.img
drwxr-xr-x 2 root root     4096 Oct 20 05:04 syslinux
-rw-r--r-- 1 root root  5502736 Oct 22 09:09 vmlinuz-linux
-rw-r--r-- 1 root root  5416720 Oct 28 08:05 vmlinuz-linux-rt
-rw-r--r-- 1 root root  5327120 Oct 18 07:00 vmlinuz-linux-rt-cornflower
-rw-r--r-- 1 root root  5327120 Oct 12 21:24 vmlinuz-linux-rt-pussytoes

[2]
[rocketmouse@archlinux ~]$ ls -l /.boot/
total 12
drwxr-xr-x 3 root root 4096 Feb 16  2017 suse11.2
drwxr-xr-x 3 root root 4096 Oct 11 06:33 ubuntu_moonstudio
drwxr-xr-x 3 root root 4096 Feb 16  2017 ubuntu_q
[rocketmouse@archlinux ~]$ grep LINUX /boot/syslinux/syslinux.cfg
    LINUX /.boot/ubuntu_moonstudio/boot/memtest86+.bin
    LINUX ../vmlinuz-linux
    LINUX ../vmlinuz-linux-rt-pussytoes
    LINUX ../vmlinuz-linux-rt-cornflower
    LINUX ../vmlinuz-linux-rt
    LINUX ../vmlinuz-linux
    LINUX /.boot/ubuntu_moonstudio/boot/vmlinuz-lowlatency
    LINUX /.boot/ubuntu_q/boot/vmlinuz-3.6.5-rt14
    LINUX /.boot/suse11.2/boot/vmlinuz-2.6.31.6-rt19

For example:

[rocketmouse@archlinux ~]$ ls -l /.boot/ubuntu_moonstudio/boot/vmlinuz-*
-rw------- 1 root root 7135968 Sep 19 23:34 /.boot/ubuntu_moonstudio/boot/vmlinuz-4.4.0-97-lowlatency
lrwxrwxrwx 1 root root      27 Oct 11 06:33 /.boot/ubuntu_moonstudio/boot/vmlinuz-lowlatency -> vmlinuz-4.4.0-97-lowlatency

Regards,
Ralf


--
ubuntu-users mailing list
[hidden email]
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-users
Reply | Threaded
Open this post in threaded view
|

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

NoOp-4
In reply to this post by Oliver Grawert
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.





--
ubuntu-users mailing list
[hidden email]
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-users
Reply | Threaded
Open this post in threaded view
|

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

Ralf Mardorf-2
On Mon, 30 Oct 2017 16:47:04 -0700, NoOp wrote:
>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

I wouldn't call it "usual", the word "unusual" fits perfect.


--
ubuntu-users mailing list
[hidden email]
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-users
Reply | Threaded
Open this post in threaded view
|

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

Liam Proven
On 31 October 2017 at 05:48, Ralf Mardorf <[hidden email]> wrote:

> I wouldn't call it "usual", the word "unusual" fits perfect.

This.

Ubuntu's upgrader is very tolerant & puts up with an amazing amount of sh*t.

For years, Mint & Fedora didn't allow upgrades at all. Debian etc.
were always far more niche & didn't have to tolerate so much tweaking.

I've found it very reliable. More so than Windows. The only thing is
if you replace bits of the OS -- e.g. I used to install Nemo & have it
control my desktop. That caused problems, so now, I don't. I just
install it and open it when I need it. Problems, gone.

--
Liam Proven • Profile: https://about.me/liamproven
Email: [hidden email] • Google Mail/Talk/Plus: [hidden email]
Twitter/Facebook/Flickr: lproven • Skype/LinkedIn/AIM/Yahoo: liamproven
UK: +44 7939-087884 • ČR/WhatsApp/Telegram/Signal: +420 702 829 053

--
ubuntu-users mailing list
[hidden email]
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-users
12