Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > comp.os.linux.advocacy > #376299 > unrolled thread

Ubuntu update failure

Back to article view | Back to comp.os.linux.advocacy

Contents

  Ubuntu update failure Desk Rabbit <me@example.com> - 2016-10-13 17:04 +0100
    Re: Ubuntu update failure Desk Rabbit <me@example.com> - 2016-10-13 17:15 +0100
      Re: Ubuntu update failure "Octavian W. Lagrange" <olagrang@perch.invalid> - 2016-10-14 12:47 +0000
        Re: Ubuntu update failure Desk Rabbit <me@example.com> - 2016-10-14 14:28 +0100
          Re: Ubuntu update failure Jim Polaski <jpolaski@linuxmail.org> - 2016-10-14 13:33 +0000
            Re: Ubuntu update failure Desk Rabbit <me@example.com> - 2016-10-14 14:49 +0100
              Re: Ubuntu update failure Jim Polaski <jpolaski@linuxmail.org> - 2016-10-14 13:53 +0000
                Re: Ubuntu update failure Desk Rabbit <me@example.com> - 2016-10-17 21:34 +0100
                  Re: Ubuntu update failure Jim Polaski <jpolaski@linuxmail.org> - 2016-10-17 21:54 +0000
                    Re: Ubuntu update failure Desk Rabbit <me@example.com> - 2016-10-18 09:45 +0100
                      Re: Ubuntu update failure Jim Polaski <jpolaski@linuxmail.org> - 2016-10-18 12:18 +0000
                      Re: Ubuntu update failure deplorable owl <owl@rooftop.invalid> - 2016-10-18 13:06 +0000
                        Re: Ubuntu update failure Desk Rabbit <me@example.com> - 2016-10-18 14:29 +0100
                          Re: Ubuntu update failure deplorable owl <owl@rooftop.invalid> - 2016-10-18 15:29 +0000
                            Re: Ubuntu update failure Desk Rabbit <me@example.com> - 2016-10-19 12:53 +0100
                    Re: Ubuntu update failure Desk Rabbit <me@example.com> - 2016-10-18 14:31 +0100
                      Re: Ubuntu update failure Jim Polaski <jpolaski@linuxmail.org> - 2016-10-18 16:27 +0000
                        Re: Ubuntu update failure Peter Köhlmann <peter-koehlmann@t-online.de> - 2016-10-18 18:38 +0200
                          Re: Ubuntu update failure chrisv <chrisv@nospam.invalid> - 2016-10-18 12:49 -0500
                          Re: Ubuntu update failure Chris Ahlstrom <OFeem1987@teleworm.us> - 2016-10-18 19:14 -0400
                            Re: Ubuntu update failure Jim Polaski <jpolaski@linuxmail.org> - 2016-10-19 00:18 +0000
                            Re: Ubuntu update failure Desk Rabbit <me@example.com> - 2016-10-19 13:07 +0100
                          Re: Ubuntu update failure Desk Rabbit <me@example.com> - 2016-10-19 13:02 +0100
                          Re: Ubuntu update failure ronb <ronb02NOSPAM@gmail.com> - 2016-10-19 17:24 +0000
                            Re: Ubuntu update failure Jim Polaski <jpolaski@linuxmail.org> - 2016-10-19 19:07 +0000
                        Re: Ubuntu update failure Desk Rabbit <me@example.com> - 2016-10-19 13:01 +0100
                          Re: Ubuntu update failure Peter Köhlmann <peter-koehlmann@t-online.de> - 2016-10-19 14:21 +0200
                            Re: Ubuntu update failure Desk Rabbit <me@example.com> - 2016-10-19 14:25 +0100
                            Re: Ubuntu update failure Chris Ahlstrom <OFeem1987@teleworm.us> - 2016-10-19 10:56 -0400
                            Re: Ubuntu update failure Marek Novotny <marek.novotny@marspolar.com> - 2016-10-19 11:20 -0400
    Re: Ubuntu update failure Desk Rabbit <me@example.com> - 2016-10-14 12:18 +0100
      Re: Ubuntu update failure Peter Köhlmann <peter-koehlmann@t-online.de> - 2016-10-14 13:38 +0200
        Re: Ubuntu update failure Jim Polaski <jpolaski@linuxmail.org> - 2016-10-14 12:28 +0000
        Re: Ubuntu update failure Desk Rabbit <me@example.com> - 2016-10-14 14:16 +0100
          Re: Ubuntu update failure Jim Polaski <jpolaski@linuxmail.org> - 2016-10-14 13:20 +0000
      Re: Ubuntu update failure Jim Polaski <jpolaski@linuxmail.org> - 2016-10-14 12:26 +0000
    Re: Ubuntu update failure fr314159@gmail.com - 2016-10-14 06:37 -0700
      Re: Ubuntu update failure Jim Polaski <jpolaski@linuxmail.org> - 2016-10-14 13:39 +0000
        Re: Ubuntu update failure Desk Rabbit <me@example.com> - 2016-10-14 14:47 +0100
    Re: Ubuntu update failure Marti van Lin <ml2mst@dontevenbother.invalid> - 2016-10-17 00:01 +0200

Page 1 of 2  [1] 2  Next page →

#376299 — Ubuntu update failure

So our dashboard announced that that an update was available 14.04 --> 16.04

It failed with "The required dependency 'apt (>= 1.0.1ubuntu2.13)' is
not installed."

Here we go again, a simple job made difficult, thanks Desktop Linux. It
would be too simple to install the missing dependency yourself wouldn't it?

[toc] | [next] | [standalone]

#376301

On 13/10/2016 17:04, Desk Rabbit wrote:
> So our dashboard announced that that an update was available 14.04 --> 16.04
> 
> It failed with "The required dependency 'apt (>= 1.0.1ubuntu2.13)' is
> not installed."
> 
> Here we go again, a simple job made difficult, thanks Desktop Linux. It
> would be too simple to install the missing dependency yourself wouldn't it?
> 

A quick scan of the Ubuntu forums show this as a common problem with
lots of solutions that don't work. I was contemplating switching this
old PC for a Windows on a stick PC, might just bring that project forward.

[toc] | [prev] | [next] | [standalone]

#376368

Desk Rabbit <me@example.com> wrote:
> On 13/10/2016 17:04, Desk Rabbit wrote:
>> So our dashboard announced that that an update was available 14.04 --> 16.04
>> 
>> It failed with "The required dependency 'apt (>= 1.0.1ubuntu2.13)' is
>> not installed."
>> 
>> Here we go again, a simple job made difficult, thanks Desktop Linux. It
>> would be too simple to install the missing dependency yourself wouldn't it?
>> 
> 
> A quick scan of the Ubuntu forums show this as a common problem with
> lots of solutions that don't work. I was contemplating switching this
> old PC for a Windows on a stick PC, might just bring that project forward.
> 

Did the solution of being at the latest point release of 14.04 before
upgrading not work? 

[toc] | [prev] | [next] | [standalone]

#376375

On 14/10/2016 13:47, Octavian W. Lagrange wrote:
> Desk Rabbit <me@example.com> wrote:
>> On 13/10/2016 17:04, Desk Rabbit wrote:
>>> So our dashboard announced that that an update was available 14.04 --> 16.04
>>>
>>> It failed with "The required dependency 'apt (>= 1.0.1ubuntu2.13)' is
>>> not installed."
>>>
>>> Here we go again, a simple job made difficult, thanks Desktop Linux. It
>>> would be too simple to install the missing dependency yourself wouldn't it?
>>>
>>
>> A quick scan of the Ubuntu forums show this as a common problem with
>> lots of solutions that don't work. I was contemplating switching this
>> old PC for a Windows on a stick PC, might just bring that project forward.
>>
> 
> Did the solution of being at the latest point release of 14.04 before
> upgrading not work? 
> 

It should be up to date as I regularly update it but it looks like there
is a problem. Currently I'm:

DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=14.04
DISTRIB_CODENAME=trusty
DISTRIB_DESCRIPTION="Ubuntu 14.04.2 LTS"

When I run "sudo apt-get update" it fails with an error:

W: There is no public key available for the following key IDs:
1397BC53640DB551
W: Failed to fetch
http://dl.google.com/linux/chrome/deb/dists/stable/Release  Unable to
find expected entry 'main/binary-i386/Packages' in Release file (Wrong
sources.list entry or malformed file)

E: Some index files failed to download. They have been ignored, or old
ones used instead.


So then I run sudo apt-key adv --keyserver keyserver.ubuntu.com
--recv-keys 1397BC53640DB551

I'm left with:
W: Failed to fetch
http://dl.google.com/linux/chrome/deb/dists/stable/Release  Unable to
find expected entry 'main/binary-i386/Packages' in Release file (Wrong
sources.list entry or malformed file)

E: Some index files failed to download. They have been ignored, or old
ones used instead.


What a fucking mess and wasting so much time. Looks like Chrome is
prevent the OS from being upgraded. WTF? Seriously WTF?

The only solution I've found so far that seems to have any chance of
working is to backup the data, wipe and install 16.04 as a fresh
install. Wow! Imagine if that was a Windows resolution, the Linux loons
would have a field day but when it's a Linux solution, that's OK.

[toc] | [prev] | [next] | [standalone]

#376376

On 2016-10-14, Desk Rabbit <me@example.com> wrote:
> On 14/10/2016 13:47, Octavian W. Lagrange wrote:
>> Desk Rabbit <me@example.com> wrote:
>>> On 13/10/2016 17:04, Desk Rabbit wrote:
>>>> So our dashboard announced that that an update was available 14.04 --> 16.04
>>>>
>>>> It failed with "The required dependency 'apt (>= 1.0.1ubuntu2.13)' is
>>>> not installed."
>>>>
>>>> Here we go again, a simple job made difficult, thanks Desktop Linux. It
>>>> would be too simple to install the missing dependency yourself wouldn't it?
>>>>
>>>
>>> A quick scan of the Ubuntu forums show this as a common problem with
>>> lots of solutions that don't work. I was contemplating switching this
>>> old PC for a Windows on a stick PC, might just bring that project forward.
>>>
>> 
>> Did the solution of being at the latest point release of 14.04 before
>> upgrading not work? 
>> 
>
> It should be up to date as I regularly update it but it looks like there
> is a problem. Currently I'm:
>
> DISTRIB_ID=Ubuntu
> DISTRIB_RELEASE=14.04
> DISTRIB_CODENAME=trusty
> DISTRIB_DESCRIPTION="Ubuntu 14.04.2 LTS"
>
> When I run "sudo apt-get update" it fails with an error:
>
> W: There is no public key available for the following key IDs:
> 1397BC53640DB551
> W: Failed to fetch
> http://dl.google.com/linux/chrome/deb/dists/stable/Release  Unable to
> find expected entry 'main/binary-i386/Packages' in Release file (Wrong
> sources.list entry or malformed file)
>
> E: Some index files failed to download. They have been ignored, or old
> ones used instead.
>
>
> So then I run sudo apt-key adv --keyserver keyserver.ubuntu.com
> --recv-keys 1397BC53640DB551
>
> I'm left with:
> W: Failed to fetch
> http://dl.google.com/linux/chrome/deb/dists/stable/Release  Unable to
> find expected entry 'main/binary-i386/Packages' in Release file (Wrong
> sources.list entry or malformed file)
>
> E: Some index files failed to download. They have been ignored, or old
> ones used instead.
>
>
> What a fucking mess and wasting so much time. Looks like Chrome is
> prevent the OS from being upgraded. WTF? Seriously WTF?
>
> The only solution I've found so far that seems to have any chance of
> working is to backup the data, wipe and install 16.04 as a fresh
> install. Wow! Imagine if that was a Windows resolution, the Linux loons
> would have a field day but when it's a Linux solution, that's OK.

What's Canonical's policy for jumping 2 major levels?
Is it even officially supported?

[toc] | [prev] | [next] | [standalone]

#376381

On 14/10/2016 14:33, Jim Polaski wrote:
> On 2016-10-14, Desk Rabbit <me@example.com> wrote:
>> On 14/10/2016 13:47, Octavian W. Lagrange wrote:
>>> Desk Rabbit <me@example.com> wrote:
>>>> On 13/10/2016 17:04, Desk Rabbit wrote:
>>>>> So our dashboard announced that that an update was available 14.04 --> 16.04
>>>>>
>>>>> It failed with "The required dependency 'apt (>= 1.0.1ubuntu2.13)' is
>>>>> not installed."
>>>>>
>>>>> Here we go again, a simple job made difficult, thanks Desktop Linux. It
>>>>> would be too simple to install the missing dependency yourself wouldn't it?
>>>>>
>>>>
>>>> A quick scan of the Ubuntu forums show this as a common problem with
>>>> lots of solutions that don't work. I was contemplating switching this
>>>> old PC for a Windows on a stick PC, might just bring that project forward.
>>>>
>>>
>>> Did the solution of being at the latest point release of 14.04 before
>>> upgrading not work? 
>>>
>>
>> It should be up to date as I regularly update it but it looks like there
>> is a problem. Currently I'm:
>>
>> DISTRIB_ID=Ubuntu
>> DISTRIB_RELEASE=14.04
>> DISTRIB_CODENAME=trusty
>> DISTRIB_DESCRIPTION="Ubuntu 14.04.2 LTS"
>>
>> When I run "sudo apt-get update" it fails with an error:
>>
>> W: There is no public key available for the following key IDs:
>> 1397BC53640DB551
>> W: Failed to fetch
>> http://dl.google.com/linux/chrome/deb/dists/stable/Release  Unable to
>> find expected entry 'main/binary-i386/Packages' in Release file (Wrong
>> sources.list entry or malformed file)
>>
>> E: Some index files failed to download. They have been ignored, or old
>> ones used instead.
>>
>>
>> So then I run sudo apt-key adv --keyserver keyserver.ubuntu.com
>> --recv-keys 1397BC53640DB551
>>
>> I'm left with:
>> W: Failed to fetch
>> http://dl.google.com/linux/chrome/deb/dists/stable/Release  Unable to
>> find expected entry 'main/binary-i386/Packages' in Release file (Wrong
>> sources.list entry or malformed file)
>>
>> E: Some index files failed to download. They have been ignored, or old
>> ones used instead.
>>
>>
>> What a fucking mess and wasting so much time. Looks like Chrome is
>> prevent the OS from being upgraded. WTF? Seriously WTF?
>>
>> The only solution I've found so far that seems to have any chance of
>> working is to backup the data, wipe and install 16.04 as a fresh
>> install. Wow! Imagine if that was a Windows resolution, the Linux loons
>> would have a field day but when it's a Linux solution, that's OK.
> 
> What's Canonical's policy for jumping 2 major levels?
> Is it even officially supported?
> 

No idea but I think I've found the issue now. In "Software & Updates"
manager, "Important security updates" and "Recommended updates" was not
checked. It's now updating to the latest point release. Hopefully I'll
be able to do the upgrade after it's finished.

[toc] | [prev] | [next] | [standalone]

#376383

On 2016-10-14, Desk Rabbit <me@example.com> wrote:
> On 14/10/2016 14:33, Jim Polaski wrote:
>> On 2016-10-14, Desk Rabbit <me@example.com> wrote:
>>> On 14/10/2016 13:47, Octavian W. Lagrange wrote:
>>>> Desk Rabbit <me@example.com> wrote:
>>>>> On 13/10/2016 17:04, Desk Rabbit wrote:
>>>>>> So our dashboard announced that that an update was available 14.04 --> 16.04
>>>>>>
>>>>>> It failed with "The required dependency 'apt (>= 1.0.1ubuntu2.13)' is
>>>>>> not installed."
>>>>>>
>>>>>> Here we go again, a simple job made difficult, thanks Desktop Linux. It
>>>>>> would be too simple to install the missing dependency yourself wouldn't it?
>>>>>>
>>>>>
>>>>> A quick scan of the Ubuntu forums show this as a common problem with
>>>>> lots of solutions that don't work. I was contemplating switching this
>>>>> old PC for a Windows on a stick PC, might just bring that project forward.
>>>>>
>>>>
>>>> Did the solution of being at the latest point release of 14.04 before
>>>> upgrading not work? 
>>>>
>>>
>>> It should be up to date as I regularly update it but it looks like there
>>> is a problem. Currently I'm:
>>>
>>> DISTRIB_ID=Ubuntu
>>> DISTRIB_RELEASE=14.04
>>> DISTRIB_CODENAME=trusty
>>> DISTRIB_DESCRIPTION="Ubuntu 14.04.2 LTS"
>>>
>>> When I run "sudo apt-get update" it fails with an error:
>>>
>>> W: There is no public key available for the following key IDs:
>>> 1397BC53640DB551
>>> W: Failed to fetch
>>> http://dl.google.com/linux/chrome/deb/dists/stable/Release  Unable to
>>> find expected entry 'main/binary-i386/Packages' in Release file (Wrong
>>> sources.list entry or malformed file)
>>>
>>> E: Some index files failed to download. They have been ignored, or old
>>> ones used instead.
>>>
>>>
>>> So then I run sudo apt-key adv --keyserver keyserver.ubuntu.com
>>> --recv-keys 1397BC53640DB551
>>>
>>> I'm left with:
>>> W: Failed to fetch
>>> http://dl.google.com/linux/chrome/deb/dists/stable/Release  Unable to
>>> find expected entry 'main/binary-i386/Packages' in Release file (Wrong
>>> sources.list entry or malformed file)
>>>
>>> E: Some index files failed to download. They have been ignored, or old
>>> ones used instead.
>>>
>>>
>>> What a fucking mess and wasting so much time. Looks like Chrome is
>>> prevent the OS from being upgraded. WTF? Seriously WTF?
>>>
>>> The only solution I've found so far that seems to have any chance of
>>> working is to backup the data, wipe and install 16.04 as a fresh
>>> install. Wow! Imagine if that was a Windows resolution, the Linux loons
>>> would have a field day but when it's a Linux solution, that's OK.
>> 
>> What's Canonical's policy for jumping 2 major levels?
>> Is it even officially supported?
>> 
>
> No idea but I think I've found the issue now. In "Software & Updates"
> manager, "Important security updates" and "Recommended updates" was not
> checked. It's now updating to the latest point release. Hopefully I'll
> be able to do the upgrade after it's finished.

Sounds good. If it works and you have the time please share with the 
Ubuntu community so other Linux users can benefit from your trouble 
shooting.

[toc] | [prev] | [next] | [standalone]

#376548

On 14/10/2016 14:53, Jim Polaski wrote:
> On 2016-10-14, Desk Rabbit <me@example.com> wrote:
>> On 14/10/2016 14:33, Jim Polaski wrote:
>>> On 2016-10-14, Desk Rabbit <me@example.com> wrote:
>>>> On 14/10/2016 13:47, Octavian W. Lagrange wrote:
>>>>> Desk Rabbit <me@example.com> wrote:
>>>>>> On 13/10/2016 17:04, Desk Rabbit wrote:
>>>>>>> So our dashboard announced that that an update was available 14.04 --> 16.04
>>>>>>>
>>>>>>> It failed with "The required dependency 'apt (>= 1.0.1ubuntu2.13)' is
>>>>>>> not installed."
>>>>>>>
>>>>>>> Here we go again, a simple job made difficult, thanks Desktop Linux. It
>>>>>>> would be too simple to install the missing dependency yourself wouldn't it?
>>>>>>>
>>>>>>
>>>>>> A quick scan of the Ubuntu forums show this as a common problem with
>>>>>> lots of solutions that don't work. I was contemplating switching this
>>>>>> old PC for a Windows on a stick PC, might just bring that project forward.
>>>>>>
>>>>>
>>>>> Did the solution of being at the latest point release of 14.04 before
>>>>> upgrading not work? 
>>>>>
>>>>
>>>> It should be up to date as I regularly update it but it looks like there
>>>> is a problem. Currently I'm:
>>>>
>>>> DISTRIB_ID=Ubuntu
>>>> DISTRIB_RELEASE=14.04
>>>> DISTRIB_CODENAME=trusty
>>>> DISTRIB_DESCRIPTION="Ubuntu 14.04.2 LTS"
>>>>
>>>> When I run "sudo apt-get update" it fails with an error:
>>>>
>>>> W: There is no public key available for the following key IDs:
>>>> 1397BC53640DB551
>>>> W: Failed to fetch
>>>> http://dl.google.com/linux/chrome/deb/dists/stable/Release  Unable to
>>>> find expected entry 'main/binary-i386/Packages' in Release file (Wrong
>>>> sources.list entry or malformed file)
>>>>
>>>> E: Some index files failed to download. They have been ignored, or old
>>>> ones used instead.
>>>>
>>>>
>>>> So then I run sudo apt-key adv --keyserver keyserver.ubuntu.com
>>>> --recv-keys 1397BC53640DB551
>>>>
>>>> I'm left with:
>>>> W: Failed to fetch
>>>> http://dl.google.com/linux/chrome/deb/dists/stable/Release  Unable to
>>>> find expected entry 'main/binary-i386/Packages' in Release file (Wrong
>>>> sources.list entry or malformed file)
>>>>
>>>> E: Some index files failed to download. They have been ignored, or old
>>>> ones used instead.
>>>>
>>>>
>>>> What a fucking mess and wasting so much time. Looks like Chrome is
>>>> prevent the OS from being upgraded. WTF? Seriously WTF?
>>>>
>>>> The only solution I've found so far that seems to have any chance of
>>>> working is to backup the data, wipe and install 16.04 as a fresh
>>>> install. Wow! Imagine if that was a Windows resolution, the Linux loons
>>>> would have a field day but when it's a Linux solution, that's OK.
>>>
>>> What's Canonical's policy for jumping 2 major levels?
>>> Is it even officially supported?
>>>
>>
>> No idea but I think I've found the issue now. In "Software & Updates"
>> manager, "Important security updates" and "Recommended updates" was not
>> checked. It's now updating to the latest point release. Hopefully I'll
>> be able to do the upgrade after it's finished.
> 
> Sounds good. If it works and you have the time please share with the 
> Ubuntu community so other Linux users can benefit from your trouble 
> shooting.
> 

Yup it worked. The resulting update then took most of the day and kept
wanting to overwrite config files I'd modified. After it finished and
rebooted my Dashing dashboard refused to run. Ruby had been updated so I
had to basically re-install it all, not a biggie but having done that
none of my widgets worked because the update had completely removed PHP
and all the addons such as curl and xml support. Why? FFS! WHY!

[toc] | [prev] | [next] | [standalone]

#376555

On 2016-10-17, Desk Rabbit <me@example.com> wrote:
> On 14/10/2016 14:53, Jim Polaski wrote:
>> On 2016-10-14, Desk Rabbit <me@example.com> wrote:
>>> On 14/10/2016 14:33, Jim Polaski wrote:
>>>> On 2016-10-14, Desk Rabbit <me@example.com> wrote:
>>>>> On 14/10/2016 13:47, Octavian W. Lagrange wrote:
>>>>>> Desk Rabbit <me@example.com> wrote:
>>>>>>> On 13/10/2016 17:04, Desk Rabbit wrote:
>>>>>>>> So our dashboard announced that that an update was available 14.04 --> 16.04
>>>>>>>>
>>>>>>>> It failed with "The required dependency 'apt (>= 1.0.1ubuntu2.13)' is
>>>>>>>> not installed."
>>>>>>>>
>>>>>>>> Here we go again, a simple job made difficult, thanks Desktop Linux. It
>>>>>>>> would be too simple to install the missing dependency yourself wouldn't it?
>>>>>>>>
>>>>>>>
>>>>>>> A quick scan of the Ubuntu forums show this as a common problem with
>>>>>>> lots of solutions that don't work. I was contemplating switching this
>>>>>>> old PC for a Windows on a stick PC, might just bring that project forward.
>>>>>>>
>>>>>>
>>>>>> Did the solution of being at the latest point release of 14.04 before
>>>>>> upgrading not work? 
>>>>>>
>>>>>
>>>>> It should be up to date as I regularly update it but it looks like there
>>>>> is a problem. Currently I'm:
>>>>>
>>>>> DISTRIB_ID=Ubuntu
>>>>> DISTRIB_RELEASE=14.04
>>>>> DISTRIB_CODENAME=trusty
>>>>> DISTRIB_DESCRIPTION="Ubuntu 14.04.2 LTS"
>>>>>
>>>>> When I run "sudo apt-get update" it fails with an error:
>>>>>
>>>>> W: There is no public key available for the following key IDs:
>>>>> 1397BC53640DB551
>>>>> W: Failed to fetch
>>>>> http://dl.google.com/linux/chrome/deb/dists/stable/Release  Unable to
>>>>> find expected entry 'main/binary-i386/Packages' in Release file (Wrong
>>>>> sources.list entry or malformed file)
>>>>>
>>>>> E: Some index files failed to download. They have been ignored, or old
>>>>> ones used instead.
>>>>>
>>>>>
>>>>> So then I run sudo apt-key adv --keyserver keyserver.ubuntu.com
>>>>> --recv-keys 1397BC53640DB551
>>>>>
>>>>> I'm left with:
>>>>> W: Failed to fetch
>>>>> http://dl.google.com/linux/chrome/deb/dists/stable/Release  Unable to
>>>>> find expected entry 'main/binary-i386/Packages' in Release file (Wrong
>>>>> sources.list entry or malformed file)
>>>>>
>>>>> E: Some index files failed to download. They have been ignored, or old
>>>>> ones used instead.
>>>>>
>>>>>
>>>>> What a fucking mess and wasting so much time. Looks like Chrome is
>>>>> prevent the OS from being upgraded. WTF? Seriously WTF?
>>>>>
>>>>> The only solution I've found so far that seems to have any chance of
>>>>> working is to backup the data, wipe and install 16.04 as a fresh
>>>>> install. Wow! Imagine if that was a Windows resolution, the Linux loons
>>>>> would have a field day but when it's a Linux solution, that's OK.
>>>>
>>>> What's Canonical's policy for jumping 2 major levels?
>>>> Is it even officially supported?
>>>>
>>>
>>> No idea but I think I've found the issue now. In "Software & Updates"
>>> manager, "Important security updates" and "Recommended updates" was not
>>> checked. It's now updating to the latest point release. Hopefully I'll
>>> be able to do the upgrade after it's finished.
>> 
>> Sounds good. If it works and you have the time please share with the 
>> Ubuntu community so other Linux users can benefit from your trouble 
>> shooting.
>> 
>
> Yup it worked. The resulting update then took most of the day and kept
> wanting to overwrite config files I'd modified. After it finished and
> rebooted my Dashing dashboard refused to run. Ruby had been updated so I
> had to basically re-install it all, not a biggie but having done that
> none of my widgets worked because the update had completely removed PHP
> and all the addons such as curl and xml support. Why? FFS! WHY!

You are /way/ over my head!
Glad it worked. I usually save my /home and fresh install as my track 
record with major version upgrades hasn't been that great. I mostly use 
Linux to learn and tinker with so it's not like there is anything I am 
afraid of losing.
That's what I like about Linux. I screw it up then I learn all kinds of 
stuff fixing it !

[toc] | [prev] | [next] | [standalone]

#376583

On 17/10/2016 22:54, Jim Polaski wrote:
> On 2016-10-17, Desk Rabbit <me@example.com> wrote:
>> On 14/10/2016 14:53, Jim Polaski wrote:
>>> On 2016-10-14, Desk Rabbit <me@example.com> wrote:
>>>> On 14/10/2016 14:33, Jim Polaski wrote:
>>>>> On 2016-10-14, Desk Rabbit <me@example.com> wrote:
>>>>>> On 14/10/2016 13:47, Octavian W. Lagrange wrote:
>>>>>>> Desk Rabbit <me@example.com> wrote:
>>>>>>>> On 13/10/2016 17:04, Desk Rabbit wrote:
>>>>>>>>> So our dashboard announced that that an update was available 14.04 --> 16.04
>>>>>>>>>
>>>>>>>>> It failed with "The required dependency 'apt (>= 1.0.1ubuntu2.13)' is
>>>>>>>>> not installed."
>>>>>>>>>
>>>>>>>>> Here we go again, a simple job made difficult, thanks Desktop Linux. It
>>>>>>>>> would be too simple to install the missing dependency yourself wouldn't it?
>>>>>>>>>
>>>>>>>>
>>>>>>>> A quick scan of the Ubuntu forums show this as a common problem with
>>>>>>>> lots of solutions that don't work. I was contemplating switching this
>>>>>>>> old PC for a Windows on a stick PC, might just bring that project forward.
>>>>>>>>
>>>>>>>
>>>>>>> Did the solution of being at the latest point release of 14.04 before
>>>>>>> upgrading not work? 
>>>>>>>
>>>>>>
>>>>>> It should be up to date as I regularly update it but it looks like there
>>>>>> is a problem. Currently I'm:
>>>>>>
>>>>>> DISTRIB_ID=Ubuntu
>>>>>> DISTRIB_RELEASE=14.04
>>>>>> DISTRIB_CODENAME=trusty
>>>>>> DISTRIB_DESCRIPTION="Ubuntu 14.04.2 LTS"
>>>>>>
>>>>>> When I run "sudo apt-get update" it fails with an error:
>>>>>>
>>>>>> W: There is no public key available for the following key IDs:
>>>>>> 1397BC53640DB551
>>>>>> W: Failed to fetch
>>>>>> http://dl.google.com/linux/chrome/deb/dists/stable/Release  Unable to
>>>>>> find expected entry 'main/binary-i386/Packages' in Release file (Wrong
>>>>>> sources.list entry or malformed file)
>>>>>>
>>>>>> E: Some index files failed to download. They have been ignored, or old
>>>>>> ones used instead.
>>>>>>
>>>>>>
>>>>>> So then I run sudo apt-key adv --keyserver keyserver.ubuntu.com
>>>>>> --recv-keys 1397BC53640DB551
>>>>>>
>>>>>> I'm left with:
>>>>>> W: Failed to fetch
>>>>>> http://dl.google.com/linux/chrome/deb/dists/stable/Release  Unable to
>>>>>> find expected entry 'main/binary-i386/Packages' in Release file (Wrong
>>>>>> sources.list entry or malformed file)
>>>>>>
>>>>>> E: Some index files failed to download. They have been ignored, or old
>>>>>> ones used instead.
>>>>>>
>>>>>>
>>>>>> What a fucking mess and wasting so much time. Looks like Chrome is
>>>>>> prevent the OS from being upgraded. WTF? Seriously WTF?
>>>>>>
>>>>>> The only solution I've found so far that seems to have any chance of
>>>>>> working is to backup the data, wipe and install 16.04 as a fresh
>>>>>> install. Wow! Imagine if that was a Windows resolution, the Linux loons
>>>>>> would have a field day but when it's a Linux solution, that's OK.
>>>>>
>>>>> What's Canonical's policy for jumping 2 major levels?
>>>>> Is it even officially supported?
>>>>>
>>>>
>>>> No idea but I think I've found the issue now. In "Software & Updates"
>>>> manager, "Important security updates" and "Recommended updates" was not
>>>> checked. It's now updating to the latest point release. Hopefully I'll
>>>> be able to do the upgrade after it's finished.
>>>
>>> Sounds good. If it works and you have the time please share with the 
>>> Ubuntu community so other Linux users can benefit from your trouble 
>>> shooting.
>>>
>>
>> Yup it worked. The resulting update then took most of the day and kept
>> wanting to overwrite config files I'd modified. After it finished and
>> rebooted my Dashing dashboard refused to run. Ruby had been updated so I
>> had to basically re-install it all, not a biggie but having done that
>> none of my widgets worked because the update had completely removed PHP
>> and all the addons such as curl and xml support. Why? FFS! WHY!
> 
> You are /way/ over my head!
> Glad it worked. I usually save my /home and fresh install as my track 
> record with major version upgrades hasn't been that great. I mostly use 
> Linux to learn and tinker with so it's not like there is anything I am 
> afraid of losing.
> That's what I like about Linux. I screw it up then I learn all kinds of 
> stuff fixing it !
> 

This mornings surprise is that although the system time is fine, the
clock widget is displaying a random time. More time wasted.....

[toc] | [prev] | [next] | [standalone]

#376592

On 2016-10-18, Desk Rabbit <me@example.com> wrote:
> On 17/10/2016 22:54, Jim Polaski wrote:
>> On 2016-10-17, Desk Rabbit <me@example.com> wrote:
>>> On 14/10/2016 14:53, Jim Polaski wrote:
>>>> On 2016-10-14, Desk Rabbit <me@example.com> wrote:
>>>>> On 14/10/2016 14:33, Jim Polaski wrote:
>>>>>> On 2016-10-14, Desk Rabbit <me@example.com> wrote:
>>>>>>> On 14/10/2016 13:47, Octavian W. Lagrange wrote:
>>>>>>>> Desk Rabbit <me@example.com> wrote:
>>>>>>>>> On 13/10/2016 17:04, Desk Rabbit wrote:
>>>>>>>>>> So our dashboard announced that that an update was available 14.04 --> 16.04
>>>>>>>>>>
>>>>>>>>>> It failed with "The required dependency 'apt (>= 1.0.1ubuntu2.13)' is
>>>>>>>>>> not installed."
>>>>>>>>>>
>>>>>>>>>> Here we go again, a simple job made difficult, thanks Desktop Linux. It
>>>>>>>>>> would be too simple to install the missing dependency yourself wouldn't it?
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>> A quick scan of the Ubuntu forums show this as a common problem with
>>>>>>>>> lots of solutions that don't work. I was contemplating switching this
>>>>>>>>> old PC for a Windows on a stick PC, might just bring that project forward.
>>>>>>>>>
>>>>>>>>
>>>>>>>> Did the solution of being at the latest point release of 14.04 before
>>>>>>>> upgrading not work? 
>>>>>>>>
>>>>>>>
>>>>>>> It should be up to date as I regularly update it but it looks like there
>>>>>>> is a problem. Currently I'm:
>>>>>>>
>>>>>>> DISTRIB_ID=Ubuntu
>>>>>>> DISTRIB_RELEASE=14.04
>>>>>>> DISTRIB_CODENAME=trusty
>>>>>>> DISTRIB_DESCRIPTION="Ubuntu 14.04.2 LTS"
>>>>>>>
>>>>>>> When I run "sudo apt-get update" it fails with an error:
>>>>>>>
>>>>>>> W: There is no public key available for the following key IDs:
>>>>>>> 1397BC53640DB551
>>>>>>> W: Failed to fetch
>>>>>>> http://dl.google.com/linux/chrome/deb/dists/stable/Release  Unable to
>>>>>>> find expected entry 'main/binary-i386/Packages' in Release file (Wrong
>>>>>>> sources.list entry or malformed file)
>>>>>>>
>>>>>>> E: Some index files failed to download. They have been ignored, or old
>>>>>>> ones used instead.
>>>>>>>
>>>>>>>
>>>>>>> So then I run sudo apt-key adv --keyserver keyserver.ubuntu.com
>>>>>>> --recv-keys 1397BC53640DB551
>>>>>>>
>>>>>>> I'm left with:
>>>>>>> W: Failed to fetch
>>>>>>> http://dl.google.com/linux/chrome/deb/dists/stable/Release  Unable to
>>>>>>> find expected entry 'main/binary-i386/Packages' in Release file (Wrong
>>>>>>> sources.list entry or malformed file)
>>>>>>>
>>>>>>> E: Some index files failed to download. They have been ignored, or old
>>>>>>> ones used instead.
>>>>>>>
>>>>>>>
>>>>>>> What a fucking mess and wasting so much time. Looks like Chrome is
>>>>>>> prevent the OS from being upgraded. WTF? Seriously WTF?
>>>>>>>
>>>>>>> The only solution I've found so far that seems to have any chance of
>>>>>>> working is to backup the data, wipe and install 16.04 as a fresh
>>>>>>> install. Wow! Imagine if that was a Windows resolution, the Linux loons
>>>>>>> would have a field day but when it's a Linux solution, that's OK.
>>>>>>
>>>>>> What's Canonical's policy for jumping 2 major levels?
>>>>>> Is it even officially supported?
>>>>>>
>>>>>
>>>>> No idea but I think I've found the issue now. In "Software & Updates"
>>>>> manager, "Important security updates" and "Recommended updates" was not
>>>>> checked. It's now updating to the latest point release. Hopefully I'll
>>>>> be able to do the upgrade after it's finished.
>>>>
>>>> Sounds good. If it works and you have the time please share with the 
>>>> Ubuntu community so other Linux users can benefit from your trouble 
>>>> shooting.
>>>>
>>>
>>> Yup it worked. The resulting update then took most of the day and kept
>>> wanting to overwrite config files I'd modified. After it finished and
>>> rebooted my Dashing dashboard refused to run. Ruby had been updated so I
>>> had to basically re-install it all, not a biggie but having done that
>>> none of my widgets worked because the update had completely removed PHP
>>> and all the addons such as curl and xml support. Why? FFS! WHY!
>> 
>> You are /way/ over my head!
>> Glad it worked. I usually save my /home and fresh install as my track 
>> record with major version upgrades hasn't been that great. I mostly use 
>> Linux to learn and tinker with so it's not like there is anything I am 
>> afraid of losing.
>> That's what I like about Linux. I screw it up then I learn all kinds of 
>> stuff fixing it !
>> 
>
> This mornings surprise is that although the system time is fine, the
> clock widget is displaying a random time. More time wasted.....

Think of how bored you would be running Windows :)

[toc] | [prev] | [next] | [standalone]

#376606

Desk Rabbit <me@example.com> wrote:
> On 17/10/2016 22:54, Jim Polaski wrote:
>> On 2016-10-17, Desk Rabbit <me@example.com> wrote:
>>> On 14/10/2016 14:53, Jim Polaski wrote:
>>>> On 2016-10-14, Desk Rabbit <me@example.com> wrote:
>>>>> On 14/10/2016 14:33, Jim Polaski wrote:
>>>>>> On 2016-10-14, Desk Rabbit <me@example.com> wrote:
>>>>>>> On 14/10/2016 13:47, Octavian W. Lagrange wrote:
>>>>>>>> Desk Rabbit <me@example.com> wrote:
>>>>>>>>> On 13/10/2016 17:04, Desk Rabbit wrote:
>>>>>>>>>> So our dashboard announced that that an update was available 14.04 --> 16.04
>>>>>>>>>>
>>>>>>>>>> It failed with "The required dependency 'apt (>= 1.0.1ubuntu2.13)' is
>>>>>>>>>> not installed."
>>>>>>>>>>
>>>>>>>>>> Here we go again, a simple job made difficult, thanks Desktop Linux. It
>>>>>>>>>> would be too simple to install the missing dependency yourself wouldn't it?
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>> A quick scan of the Ubuntu forums show this as a common problem with
>>>>>>>>> lots of solutions that don't work. I was contemplating switching this
>>>>>>>>> old PC for a Windows on a stick PC, might just bring that project forward.
>>>>>>>>>
>>>>>>>>
>>>>>>>> Did the solution of being at the latest point release of 14.04 before
>>>>>>>> upgrading not work? 
>>>>>>>>
>>>>>>>
>>>>>>> It should be up to date as I regularly update it but it looks like there
>>>>>>> is a problem. Currently I'm:
>>>>>>>
>>>>>>> DISTRIB_ID=Ubuntu
>>>>>>> DISTRIB_RELEASE=14.04
>>>>>>> DISTRIB_CODENAME=trusty
>>>>>>> DISTRIB_DESCRIPTION="Ubuntu 14.04.2 LTS"
>>>>>>>
>>>>>>> When I run "sudo apt-get update" it fails with an error:
>>>>>>>
>>>>>>> W: There is no public key available for the following key IDs:
>>>>>>> 1397BC53640DB551
>>>>>>> W: Failed to fetch
>>>>>>> http://dl.google.com/linux/chrome/deb/dists/stable/Release  Unable to
>>>>>>> find expected entry 'main/binary-i386/Packages' in Release file (Wrong
>>>>>>> sources.list entry or malformed file)
>>>>>>>
>>>>>>> E: Some index files failed to download. They have been ignored, or old
>>>>>>> ones used instead.
>>>>>>>
>>>>>>>
>>>>>>> So then I run sudo apt-key adv --keyserver keyserver.ubuntu.com
>>>>>>> --recv-keys 1397BC53640DB551
>>>>>>>
>>>>>>> I'm left with:
>>>>>>> W: Failed to fetch
>>>>>>> http://dl.google.com/linux/chrome/deb/dists/stable/Release  Unable to
>>>>>>> find expected entry 'main/binary-i386/Packages' in Release file (Wrong
>>>>>>> sources.list entry or malformed file)
>>>>>>>
>>>>>>> E: Some index files failed to download. They have been ignored, or old
>>>>>>> ones used instead.
>>>>>>>
>>>>>>>
>>>>>>> What a fucking mess and wasting so much time. Looks like Chrome is
>>>>>>> prevent the OS from being upgraded. WTF? Seriously WTF?
>>>>>>>
>>>>>>> The only solution I've found so far that seems to have any chance of
>>>>>>> working is to backup the data, wipe and install 16.04 as a fresh
>>>>>>> install. Wow! Imagine if that was a Windows resolution, the Linux loons
>>>>>>> would have a field day but when it's a Linux solution, that's OK.
>>>>>>
>>>>>> What's Canonical's policy for jumping 2 major levels?
>>>>>> Is it even officially supported?
>>>>>>
>>>>>
>>>>> No idea but I think I've found the issue now. In "Software & Updates"
>>>>> manager, "Important security updates" and "Recommended updates" was not
>>>>> checked. It's now updating to the latest point release. Hopefully I'll
>>>>> be able to do the upgrade after it's finished.
>>>>
>>>> Sounds good. If it works and you have the time please share with the 
>>>> Ubuntu community so other Linux users can benefit from your trouble 
>>>> shooting.
>>>>
>>>
>>> Yup it worked. The resulting update then took most of the day and kept
>>> wanting to overwrite config files I'd modified. After it finished and
>>> rebooted my Dashing dashboard refused to run. Ruby had been updated so I
>>> had to basically re-install it all, not a biggie but having done that
>>> none of my widgets worked because the update had completely removed PHP
>>> and all the addons such as curl and xml support. Why? FFS! WHY!
>> 
>> You are /way/ over my head!
>> Glad it worked. I usually save my /home and fresh install as my track 
>> record with major version upgrades hasn't been that great. I mostly use 
>> Linux to learn and tinker with so it's not like there is anything I am 
>> afraid of losing.
>> That's what I like about Linux. I screw it up then I learn all kinds of 
>> stuff fixing it !
>> 
> 
> This mornings surprise is that although the system time is fine, the
> clock widget is displaying a random time. More time wasted.....

LOL.  Can't you do anything right?
Why are you even upgrading one LTS to another after only two years?
Why run an LTS at all if you're going to be upgrading that often?
Ubuntu 14.04 doesn't EOL until April 2019.

[toc] | [prev] | [next] | [standalone]

#376607

On 18/10/2016 14:06, deplorable owl wrote:
> Desk Rabbit <me@example.com> wrote:
>> On 17/10/2016 22:54, Jim Polaski wrote:
>>> On 2016-10-17, Desk Rabbit <me@example.com> wrote:
>>>> On 14/10/2016 14:53, Jim Polaski wrote:
>>>>> On 2016-10-14, Desk Rabbit <me@example.com> wrote:
>>>>>> On 14/10/2016 14:33, Jim Polaski wrote:
>>>>>>> On 2016-10-14, Desk Rabbit <me@example.com> wrote:
>>>>>>>> On 14/10/2016 13:47, Octavian W. Lagrange wrote:
>>>>>>>>> Desk Rabbit <me@example.com> wrote:
>>>>>>>>>> On 13/10/2016 17:04, Desk Rabbit wrote:
>>>>>>>>>>> So our dashboard announced that that an update was available 14.04 --> 16.04
>>>>>>>>>>>
>>>>>>>>>>> It failed with "The required dependency 'apt (>= 1.0.1ubuntu2.13)' is
>>>>>>>>>>> not installed."
>>>>>>>>>>>
>>>>>>>>>>> Here we go again, a simple job made difficult, thanks Desktop Linux. It
>>>>>>>>>>> would be too simple to install the missing dependency yourself wouldn't it?
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> A quick scan of the Ubuntu forums show this as a common problem with
>>>>>>>>>> lots of solutions that don't work. I was contemplating switching this
>>>>>>>>>> old PC for a Windows on a stick PC, might just bring that project forward.
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>> Did the solution of being at the latest point release of 14.04 before
>>>>>>>>> upgrading not work? 
>>>>>>>>>
>>>>>>>>
>>>>>>>> It should be up to date as I regularly update it but it looks like there
>>>>>>>> is a problem. Currently I'm:
>>>>>>>>
>>>>>>>> DISTRIB_ID=Ubuntu
>>>>>>>> DISTRIB_RELEASE=14.04
>>>>>>>> DISTRIB_CODENAME=trusty
>>>>>>>> DISTRIB_DESCRIPTION="Ubuntu 14.04.2 LTS"
>>>>>>>>
>>>>>>>> When I run "sudo apt-get update" it fails with an error:
>>>>>>>>
>>>>>>>> W: There is no public key available for the following key IDs:
>>>>>>>> 1397BC53640DB551
>>>>>>>> W: Failed to fetch
>>>>>>>> http://dl.google.com/linux/chrome/deb/dists/stable/Release  Unable to
>>>>>>>> find expected entry 'main/binary-i386/Packages' in Release file (Wrong
>>>>>>>> sources.list entry or malformed file)
>>>>>>>>
>>>>>>>> E: Some index files failed to download. They have been ignored, or old
>>>>>>>> ones used instead.
>>>>>>>>
>>>>>>>>
>>>>>>>> So then I run sudo apt-key adv --keyserver keyserver.ubuntu.com
>>>>>>>> --recv-keys 1397BC53640DB551
>>>>>>>>
>>>>>>>> I'm left with:
>>>>>>>> W: Failed to fetch
>>>>>>>> http://dl.google.com/linux/chrome/deb/dists/stable/Release  Unable to
>>>>>>>> find expected entry 'main/binary-i386/Packages' in Release file (Wrong
>>>>>>>> sources.list entry or malformed file)
>>>>>>>>
>>>>>>>> E: Some index files failed to download. They have been ignored, or old
>>>>>>>> ones used instead.
>>>>>>>>
>>>>>>>>
>>>>>>>> What a fucking mess and wasting so much time. Looks like Chrome is
>>>>>>>> prevent the OS from being upgraded. WTF? Seriously WTF?
>>>>>>>>
>>>>>>>> The only solution I've found so far that seems to have any chance of
>>>>>>>> working is to backup the data, wipe and install 16.04 as a fresh
>>>>>>>> install. Wow! Imagine if that was a Windows resolution, the Linux loons
>>>>>>>> would have a field day but when it's a Linux solution, that's OK.
>>>>>>>
>>>>>>> What's Canonical's policy for jumping 2 major levels?
>>>>>>> Is it even officially supported?
>>>>>>>
>>>>>>
>>>>>> No idea but I think I've found the issue now. In "Software & Updates"
>>>>>> manager, "Important security updates" and "Recommended updates" was not
>>>>>> checked. It's now updating to the latest point release. Hopefully I'll
>>>>>> be able to do the upgrade after it's finished.
>>>>>
>>>>> Sounds good. If it works and you have the time please share with the 
>>>>> Ubuntu community so other Linux users can benefit from your trouble 
>>>>> shooting.
>>>>>
>>>>
>>>> Yup it worked. The resulting update then took most of the day and kept
>>>> wanting to overwrite config files I'd modified. After it finished and
>>>> rebooted my Dashing dashboard refused to run. Ruby had been updated so I
>>>> had to basically re-install it all, not a biggie but having done that
>>>> none of my widgets worked because the update had completely removed PHP
>>>> and all the addons such as curl and xml support. Why? FFS! WHY!
>>>
>>> You are /way/ over my head!
>>> Glad it worked. I usually save my /home and fresh install as my track 
>>> record with major version upgrades hasn't been that great. I mostly use 
>>> Linux to learn and tinker with so it's not like there is anything I am 
>>> afraid of losing.
>>> That's what I like about Linux. I screw it up then I learn all kinds of 
>>> stuff fixing it !
>>>
>>
>> This mornings surprise is that although the system time is fine, the
>> clock widget is displaying a random time. More time wasted.....
> 
> LOL.  Can't you do anything right?
> Why are you even upgrading one LTS to another after only two years?
> Why run an LTS at all if you're going to be upgrading that often?
> Ubuntu 14.04 doesn't EOL until April 2019.
> 

I upgraded because the system offered the upgrade and upgrades are
usually pretty important to do. However after this debacle I am going to
move Dashing on to a headless Linux box and run the display from a
Windows Stick PC in kiosk mode.

[toc] | [prev] | [next] | [standalone]

#376628

Desk Rabbit <me@example.com> wrote:
> On 18/10/2016 14:06, deplorable owl wrote:
>> Desk Rabbit <me@example.com> wrote:
>>> On 17/10/2016 22:54, Jim Polaski wrote:
>>>> On 2016-10-17, Desk Rabbit <me@example.com> wrote:
>>>>> On 14/10/2016 14:53, Jim Polaski wrote:
>>>>>> On 2016-10-14, Desk Rabbit <me@example.com> wrote:
>>>>>>> On 14/10/2016 14:33, Jim Polaski wrote:
>>>>>>>> On 2016-10-14, Desk Rabbit <me@example.com> wrote:
>>>>>>>>> On 14/10/2016 13:47, Octavian W. Lagrange wrote:
>>>>>>>>>> Desk Rabbit <me@example.com> wrote:
>>>>>>>>>>> On 13/10/2016 17:04, Desk Rabbit wrote:
>>>>>>>>>>>> So our dashboard announced that that an update was available 14.04 --> 16.04
>>>>>>>>>>>>
>>>>>>>>>>>> It failed with "The required dependency 'apt (>= 1.0.1ubuntu2.13)' is
>>>>>>>>>>>> not installed."
>>>>>>>>>>>>
>>>>>>>>>>>> Here we go again, a simple job made difficult, thanks Desktop Linux. It
>>>>>>>>>>>> would be too simple to install the missing dependency yourself wouldn't it?
>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> A quick scan of the Ubuntu forums show this as a common problem with
>>>>>>>>>>> lots of solutions that don't work. I was contemplating switching this
>>>>>>>>>>> old PC for a Windows on a stick PC, might just bring that project forward.
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> Did the solution of being at the latest point release of 14.04 before
>>>>>>>>>> upgrading not work? 
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>> It should be up to date as I regularly update it but it looks like there
>>>>>>>>> is a problem. Currently I'm:
>>>>>>>>>
>>>>>>>>> DISTRIB_ID=Ubuntu
>>>>>>>>> DISTRIB_RELEASE=14.04
>>>>>>>>> DISTRIB_CODENAME=trusty
>>>>>>>>> DISTRIB_DESCRIPTION="Ubuntu 14.04.2 LTS"
>>>>>>>>>
>>>>>>>>> When I run "sudo apt-get update" it fails with an error:
>>>>>>>>>
>>>>>>>>> W: There is no public key available for the following key IDs:
>>>>>>>>> 1397BC53640DB551
>>>>>>>>> W: Failed to fetch
>>>>>>>>> http://dl.google.com/linux/chrome/deb/dists/stable/Release  Unable to
>>>>>>>>> find expected entry 'main/binary-i386/Packages' in Release file (Wrong
>>>>>>>>> sources.list entry or malformed file)
>>>>>>>>>
>>>>>>>>> E: Some index files failed to download. They have been ignored, or old
>>>>>>>>> ones used instead.
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> So then I run sudo apt-key adv --keyserver keyserver.ubuntu.com
>>>>>>>>> --recv-keys 1397BC53640DB551
>>>>>>>>>
>>>>>>>>> I'm left with:
>>>>>>>>> W: Failed to fetch
>>>>>>>>> http://dl.google.com/linux/chrome/deb/dists/stable/Release  Unable to
>>>>>>>>> find expected entry 'main/binary-i386/Packages' in Release file (Wrong
>>>>>>>>> sources.list entry or malformed file)
>>>>>>>>>
>>>>>>>>> E: Some index files failed to download. They have been ignored, or old
>>>>>>>>> ones used instead.
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> What a fucking mess and wasting so much time. Looks like Chrome is
>>>>>>>>> prevent the OS from being upgraded. WTF? Seriously WTF?
>>>>>>>>>
>>>>>>>>> The only solution I've found so far that seems to have any chance of
>>>>>>>>> working is to backup the data, wipe and install 16.04 as a fresh
>>>>>>>>> install. Wow! Imagine if that was a Windows resolution, the Linux loons
>>>>>>>>> would have a field day but when it's a Linux solution, that's OK.
>>>>>>>>
>>>>>>>> What's Canonical's policy for jumping 2 major levels?
>>>>>>>> Is it even officially supported?
>>>>>>>>
>>>>>>>
>>>>>>> No idea but I think I've found the issue now. In "Software & Updates"
>>>>>>> manager, "Important security updates" and "Recommended updates" was not
>>>>>>> checked. It's now updating to the latest point release. Hopefully I'll
>>>>>>> be able to do the upgrade after it's finished.
>>>>>>
>>>>>> Sounds good. If it works and you have the time please share with the 
>>>>>> Ubuntu community so other Linux users can benefit from your trouble 
>>>>>> shooting.
>>>>>>
>>>>>
>>>>> Yup it worked. The resulting update then took most of the day and kept
>>>>> wanting to overwrite config files I'd modified. After it finished and
>>>>> rebooted my Dashing dashboard refused to run. Ruby had been updated so I
>>>>> had to basically re-install it all, not a biggie but having done that
>>>>> none of my widgets worked because the update had completely removed PHP
>>>>> and all the addons such as curl and xml support. Why? FFS! WHY!
>>>>
>>>> You are /way/ over my head!
>>>> Glad it worked. I usually save my /home and fresh install as my track 
>>>> record with major version upgrades hasn't been that great. I mostly use 
>>>> Linux to learn and tinker with so it's not like there is anything I am 
>>>> afraid of losing.
>>>> That's what I like about Linux. I screw it up then I learn all kinds of 
>>>> stuff fixing it !
>>>>
>>>
>>> This mornings surprise is that although the system time is fine, the
>>> clock widget is displaying a random time. More time wasted.....
>> 
>> LOL.  Can't you do anything right?
>> Why are you even upgrading one LTS to another after only two years?
>> Why run an LTS at all if you're going to be upgrading that often?
>> Ubuntu 14.04 doesn't EOL until April 2019.
>> 
> 
> I upgraded because the system offered the upgrade and upgrades are
> usually pretty important to do. However after this debacle I am going to
> move Dashing on to a headless Linux box and run the display from a
> Windows Stick PC in kiosk mode.

I've never used Dashing, but it appears to be no longer maintained and
was forked.  Maybe that caused some of the problems.  Why do you need
the Windows PC kiosk?  Can't your people just connect to the dashboard
from wherever they are?

[toc] | [prev] | [next] | [standalone]

#376696

On 18/10/2016 16:29, deplorable owl wrote:
> Desk Rabbit <me@example.com> wrote:
>> On 18/10/2016 14:06, deplorable owl wrote:
>>> Desk Rabbit <me@example.com> wrote:
>>>> On 17/10/2016 22:54, Jim Polaski wrote:
>>>>> On 2016-10-17, Desk Rabbit <me@example.com> wrote:
>>>>>> On 14/10/2016 14:53, Jim Polaski wrote:
>>>>>>> On 2016-10-14, Desk Rabbit <me@example.com> wrote:
>>>>>>>> On 14/10/2016 14:33, Jim Polaski wrote:
>>>>>>>>> On 2016-10-14, Desk Rabbit <me@example.com> wrote:
>>>>>>>>>> On 14/10/2016 13:47, Octavian W. Lagrange wrote:
>>>>>>>>>>> Desk Rabbit <me@example.com> wrote:
>>>>>>>>>>>> On 13/10/2016 17:04, Desk Rabbit wrote:
>>>>>>>>>>>>> So our dashboard announced that that an update was available 14.04 --> 16.04
>>>>>>>>>>>>>
>>>>>>>>>>>>> It failed with "The required dependency 'apt (>= 1.0.1ubuntu2.13)' is
>>>>>>>>>>>>> not installed."
>>>>>>>>>>>>>
>>>>>>>>>>>>> Here we go again, a simple job made difficult, thanks Desktop Linux. It
>>>>>>>>>>>>> would be too simple to install the missing dependency yourself wouldn't it?
>>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> A quick scan of the Ubuntu forums show this as a common problem with
>>>>>>>>>>>> lots of solutions that don't work. I was contemplating switching this
>>>>>>>>>>>> old PC for a Windows on a stick PC, might just bring that project forward.
>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> Did the solution of being at the latest point release of 14.04 before
>>>>>>>>>>> upgrading not work? 
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> It should be up to date as I regularly update it but it looks like there
>>>>>>>>>> is a problem. Currently I'm:
>>>>>>>>>>
>>>>>>>>>> DISTRIB_ID=Ubuntu
>>>>>>>>>> DISTRIB_RELEASE=14.04
>>>>>>>>>> DISTRIB_CODENAME=trusty
>>>>>>>>>> DISTRIB_DESCRIPTION="Ubuntu 14.04.2 LTS"
>>>>>>>>>>
>>>>>>>>>> When I run "sudo apt-get update" it fails with an error:
>>>>>>>>>>
>>>>>>>>>> W: There is no public key available for the following key IDs:
>>>>>>>>>> 1397BC53640DB551
>>>>>>>>>> W: Failed to fetch
>>>>>>>>>> http://dl.google.com/linux/chrome/deb/dists/stable/Release  Unable to
>>>>>>>>>> find expected entry 'main/binary-i386/Packages' in Release file (Wrong
>>>>>>>>>> sources.list entry or malformed file)
>>>>>>>>>>
>>>>>>>>>> E: Some index files failed to download. They have been ignored, or old
>>>>>>>>>> ones used instead.
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> So then I run sudo apt-key adv --keyserver keyserver.ubuntu.com
>>>>>>>>>> --recv-keys 1397BC53640DB551
>>>>>>>>>>
>>>>>>>>>> I'm left with:
>>>>>>>>>> W: Failed to fetch
>>>>>>>>>> http://dl.google.com/linux/chrome/deb/dists/stable/Release  Unable to
>>>>>>>>>> find expected entry 'main/binary-i386/Packages' in Release file (Wrong
>>>>>>>>>> sources.list entry or malformed file)
>>>>>>>>>>
>>>>>>>>>> E: Some index files failed to download. They have been ignored, or old
>>>>>>>>>> ones used instead.
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> What a fucking mess and wasting so much time. Looks like Chrome is
>>>>>>>>>> prevent the OS from being upgraded. WTF? Seriously WTF?
>>>>>>>>>>
>>>>>>>>>> The only solution I've found so far that seems to have any chance of
>>>>>>>>>> working is to backup the data, wipe and install 16.04 as a fresh
>>>>>>>>>> install. Wow! Imagine if that was a Windows resolution, the Linux loons
>>>>>>>>>> would have a field day but when it's a Linux solution, that's OK.
>>>>>>>>>
>>>>>>>>> What's Canonical's policy for jumping 2 major levels?
>>>>>>>>> Is it even officially supported?
>>>>>>>>>
>>>>>>>>
>>>>>>>> No idea but I think I've found the issue now. In "Software & Updates"
>>>>>>>> manager, "Important security updates" and "Recommended updates" was not
>>>>>>>> checked. It's now updating to the latest point release. Hopefully I'll
>>>>>>>> be able to do the upgrade after it's finished.
>>>>>>>
>>>>>>> Sounds good. If it works and you have the time please share with the 
>>>>>>> Ubuntu community so other Linux users can benefit from your trouble 
>>>>>>> shooting.
>>>>>>>
>>>>>>
>>>>>> Yup it worked. The resulting update then took most of the day and kept
>>>>>> wanting to overwrite config files I'd modified. After it finished and
>>>>>> rebooted my Dashing dashboard refused to run. Ruby had been updated so I
>>>>>> had to basically re-install it all, not a biggie but having done that
>>>>>> none of my widgets worked because the update had completely removed PHP
>>>>>> and all the addons such as curl and xml support. Why? FFS! WHY!
>>>>>
>>>>> You are /way/ over my head!
>>>>> Glad it worked. I usually save my /home and fresh install as my track 
>>>>> record with major version upgrades hasn't been that great. I mostly use 
>>>>> Linux to learn and tinker with so it's not like there is anything I am 
>>>>> afraid of losing.
>>>>> That's what I like about Linux. I screw it up then I learn all kinds of 
>>>>> stuff fixing it !
>>>>>
>>>>
>>>> This mornings surprise is that although the system time is fine, the
>>>> clock widget is displaying a random time. More time wasted.....
>>>
>>> LOL.  Can't you do anything right?
>>> Why are you even upgrading one LTS to another after only two years?
>>> Why run an LTS at all if you're going to be upgrading that often?
>>> Ubuntu 14.04 doesn't EOL until April 2019.
>>>
>>
>> I upgraded because the system offered the upgrade and upgrades are
>> usually pretty important to do. However after this debacle I am going to
>> move Dashing on to a headless Linux box and run the display from a
>> Windows Stick PC in kiosk mode.
> 
> I've never used Dashing, but it appears to be no longer maintained and
> was forked.  Maybe that caused some of the problems.  Why do you need
> the Windows PC kiosk?  Can't your people just connect to the dashboard
> from wherever they are?
> 

Dashing is fine, it was the complete loss of PHP and the upgrade of Ruby
that caused most of the problems.

It's a large display in the office, much more visible than relying on
people to run web browsers. One of the widgets for example will go red
the second a server goes off line, it's highly visible and contributes
to our excellent response and fix times - Most faults are fixed within 4
hours. Last week we fixed within 3 hours.

[toc] | [prev] | [next] | [standalone]

#376608

On 17/10/2016 22:54, Jim Polaski wrote:
> On 2016-10-17, Desk Rabbit <me@example.com> wrote:
>> On 14/10/2016 14:53, Jim Polaski wrote:
>>> On 2016-10-14, Desk Rabbit <me@example.com> wrote:
>>>> On 14/10/2016 14:33, Jim Polaski wrote:
>>>>> On 2016-10-14, Desk Rabbit <me@example.com> wrote:
>>>>>> On 14/10/2016 13:47, Octavian W. Lagrange wrote:
>>>>>>> Desk Rabbit <me@example.com> wrote:
>>>>>>>> On 13/10/2016 17:04, Desk Rabbit wrote:
>>>>>>>>> So our dashboard announced that that an update was available 14.04 --> 16.04
>>>>>>>>>
>>>>>>>>> It failed with "The required dependency 'apt (>= 1.0.1ubuntu2.13)' is
>>>>>>>>> not installed."
>>>>>>>>>
>>>>>>>>> Here we go again, a simple job made difficult, thanks Desktop Linux. It
>>>>>>>>> would be too simple to install the missing dependency yourself wouldn't it?
>>>>>>>>>
>>>>>>>>
>>>>>>>> A quick scan of the Ubuntu forums show this as a common problem with
>>>>>>>> lots of solutions that don't work. I was contemplating switching this
>>>>>>>> old PC for a Windows on a stick PC, might just bring that project forward.
>>>>>>>>
>>>>>>>
>>>>>>> Did the solution of being at the latest point release of 14.04 before
>>>>>>> upgrading not work? 
>>>>>>>
>>>>>>
>>>>>> It should be up to date as I regularly update it but it looks like there
>>>>>> is a problem. Currently I'm:
>>>>>>
>>>>>> DISTRIB_ID=Ubuntu
>>>>>> DISTRIB_RELEASE=14.04
>>>>>> DISTRIB_CODENAME=trusty
>>>>>> DISTRIB_DESCRIPTION="Ubuntu 14.04.2 LTS"
>>>>>>
>>>>>> When I run "sudo apt-get update" it fails with an error:
>>>>>>
>>>>>> W: There is no public key available for the following key IDs:
>>>>>> 1397BC53640DB551
>>>>>> W: Failed to fetch
>>>>>> http://dl.google.com/linux/chrome/deb/dists/stable/Release  Unable to
>>>>>> find expected entry 'main/binary-i386/Packages' in Release file (Wrong
>>>>>> sources.list entry or malformed file)
>>>>>>
>>>>>> E: Some index files failed to download. They have been ignored, or old
>>>>>> ones used instead.
>>>>>>
>>>>>>
>>>>>> So then I run sudo apt-key adv --keyserver keyserver.ubuntu.com
>>>>>> --recv-keys 1397BC53640DB551
>>>>>>
>>>>>> I'm left with:
>>>>>> W: Failed to fetch
>>>>>> http://dl.google.com/linux/chrome/deb/dists/stable/Release  Unable to
>>>>>> find expected entry 'main/binary-i386/Packages' in Release file (Wrong
>>>>>> sources.list entry or malformed file)
>>>>>>
>>>>>> E: Some index files failed to download. They have been ignored, or old
>>>>>> ones used instead.
>>>>>>
>>>>>>
>>>>>> What a fucking mess and wasting so much time. Looks like Chrome is
>>>>>> prevent the OS from being upgraded. WTF? Seriously WTF?
>>>>>>
>>>>>> The only solution I've found so far that seems to have any chance of
>>>>>> working is to backup the data, wipe and install 16.04 as a fresh
>>>>>> install. Wow! Imagine if that was a Windows resolution, the Linux loons
>>>>>> would have a field day but when it's a Linux solution, that's OK.
>>>>>
>>>>> What's Canonical's policy for jumping 2 major levels?
>>>>> Is it even officially supported?
>>>>>
>>>>
>>>> No idea but I think I've found the issue now. In "Software & Updates"
>>>> manager, "Important security updates" and "Recommended updates" was not
>>>> checked. It's now updating to the latest point release. Hopefully I'll
>>>> be able to do the upgrade after it's finished.
>>>
>>> Sounds good. If it works and you have the time please share with the 
>>> Ubuntu community so other Linux users can benefit from your trouble 
>>> shooting.
>>>
>>
>> Yup it worked. The resulting update then took most of the day and kept
>> wanting to overwrite config files I'd modified. After it finished and
>> rebooted my Dashing dashboard refused to run. Ruby had been updated so I
>> had to basically re-install it all, not a biggie but having done that
>> none of my widgets worked because the update had completely removed PHP
>> and all the addons such as curl and xml support. Why? FFS! WHY!
> 
> You are /way/ over my head!

Thanks, unlike many of the so-called advocates in here I do more with
Linux than play on it in a basement. This particular system does real
work in my business as it displays real-time information to the techs so
they know how many open tickets we have and offline servers etc.

[toc] | [prev] | [next] | [standalone]

#376640

On 2016-10-18, Desk Rabbit <me@example.com> wrote:
> On 17/10/2016 22:54, Jim Polaski wrote:
>> On 2016-10-17, Desk Rabbit <me@example.com> wrote:
>>> On 14/10/2016 14:53, Jim Polaski wrote:
>>>> On 2016-10-14, Desk Rabbit <me@example.com> wrote:
>>>>> On 14/10/2016 14:33, Jim Polaski wrote:
>>>>>> On 2016-10-14, Desk Rabbit <me@example.com> wrote:
>>>>>>> On 14/10/2016 13:47, Octavian W. Lagrange wrote:
>>>>>>>> Desk Rabbit <me@example.com> wrote:
>>>>>>>>> On 13/10/2016 17:04, Desk Rabbit wrote:
>>>>>>>>>> So our dashboard announced that that an update was available 14.04 --> 16.04
>>>>>>>>>>
>>>>>>>>>> It failed with "The required dependency 'apt (>= 1.0.1ubuntu2.13)' is
>>>>>>>>>> not installed."
>>>>>>>>>>
>>>>>>>>>> Here we go again, a simple job made difficult, thanks Desktop Linux. It
>>>>>>>>>> would be too simple to install the missing dependency yourself wouldn't it?
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>> A quick scan of the Ubuntu forums show this as a common problem with
>>>>>>>>> lots of solutions that don't work. I was contemplating switching this
>>>>>>>>> old PC for a Windows on a stick PC, might just bring that project forward.
>>>>>>>>>
>>>>>>>>
>>>>>>>> Did the solution of being at the latest point release of 14.04 before
>>>>>>>> upgrading not work? 
>>>>>>>>
>>>>>>>
>>>>>>> It should be up to date as I regularly update it but it looks like there
>>>>>>> is a problem. Currently I'm:
>>>>>>>
>>>>>>> DISTRIB_ID=Ubuntu
>>>>>>> DISTRIB_RELEASE=14.04
>>>>>>> DISTRIB_CODENAME=trusty
>>>>>>> DISTRIB_DESCRIPTION="Ubuntu 14.04.2 LTS"
>>>>>>>
>>>>>>> When I run "sudo apt-get update" it fails with an error:
>>>>>>>
>>>>>>> W: There is no public key available for the following key IDs:
>>>>>>> 1397BC53640DB551
>>>>>>> W: Failed to fetch
>>>>>>> http://dl.google.com/linux/chrome/deb/dists/stable/Release  Unable to
>>>>>>> find expected entry 'main/binary-i386/Packages' in Release file (Wrong
>>>>>>> sources.list entry or malformed file)
>>>>>>>
>>>>>>> E: Some index files failed to download. They have been ignored, or old
>>>>>>> ones used instead.
>>>>>>>
>>>>>>>
>>>>>>> So then I run sudo apt-key adv --keyserver keyserver.ubuntu.com
>>>>>>> --recv-keys 1397BC53640DB551
>>>>>>>
>>>>>>> I'm left with:
>>>>>>> W: Failed to fetch
>>>>>>> http://dl.google.com/linux/chrome/deb/dists/stable/Release  Unable to
>>>>>>> find expected entry 'main/binary-i386/Packages' in Release file (Wrong
>>>>>>> sources.list entry or malformed file)
>>>>>>>
>>>>>>> E: Some index files failed to download. They have been ignored, or old
>>>>>>> ones used instead.
>>>>>>>
>>>>>>>
>>>>>>> What a fucking mess and wasting so much time. Looks like Chrome is
>>>>>>> prevent the OS from being upgraded. WTF? Seriously WTF?
>>>>>>>
>>>>>>> The only solution I've found so far that seems to have any chance of
>>>>>>> working is to backup the data, wipe and install 16.04 as a fresh
>>>>>>> install. Wow! Imagine if that was a Windows resolution, the Linux loons
>>>>>>> would have a field day but when it's a Linux solution, that's OK.
>>>>>>
>>>>>> What's Canonical's policy for jumping 2 major levels?
>>>>>> Is it even officially supported?
>>>>>>
>>>>>
>>>>> No idea but I think I've found the issue now. In "Software & Updates"
>>>>> manager, "Important security updates" and "Recommended updates" was not
>>>>> checked. It's now updating to the latest point release. Hopefully I'll
>>>>> be able to do the upgrade after it's finished.
>>>>
>>>> Sounds good. If it works and you have the time please share with the 
>>>> Ubuntu community so other Linux users can benefit from your trouble 
>>>> shooting.
>>>>
>>>
>>> Yup it worked. The resulting update then took most of the day and kept
>>> wanting to overwrite config files I'd modified. After it finished and
>>> rebooted my Dashing dashboard refused to run. Ruby had been updated so I
>>> had to basically re-install it all, not a biggie but having done that
>>> none of my widgets worked because the update had completely removed PHP
>>> and all the addons such as curl and xml support. Why? FFS! WHY!
>> 
>> You are /way/ over my head!
>
> Thanks, unlike many of the so-called advocates in here I do more with
> Linux than play on it in a basement. This particular system does real
> work in my business as it displays real-time information to the techs so
> they know how many open tickets we have and offline servers etc.

I get the impression that most of the Linux advocates in COLA don't work 
with Linux during their day jobs.

[toc] | [prev] | [next] | [standalone]

#376645

Jim Polaski wrote:

> On 2016-10-18, Desk Rabbit <me@example.com> wrote:
>> On 17/10/2016 22:54, Jim Polaski wrote:
>>> On 2016-10-17, Desk Rabbit <me@example.com> wrote:
>>>> On 14/10/2016 14:53, Jim Polaski wrote:
>>>>> On 2016-10-14, Desk Rabbit <me@example.com> wrote:
>>>>>> On 14/10/2016 14:33, Jim Polaski wrote:
>>>>>>> On 2016-10-14, Desk Rabbit <me@example.com> wrote:
>>>>>>>> On 14/10/2016 13:47, Octavian W. Lagrange wrote:
>>>>>>>>> Desk Rabbit <me@example.com> wrote:
>>>>>>>>>> On 13/10/2016 17:04, Desk Rabbit wrote:
>>>>>>>>>>> So our dashboard announced that that an update was available
>>>>>>>>>>> 14.04 --> 16.04
>>>>>>>>>>>
>>>>>>>>>>> It failed with "The required dependency 'apt (>=
>>>>>>>>>>> 1.0.1ubuntu2.13)' is not installed."
>>>>>>>>>>>
>>>>>>>>>>> Here we go again, a simple job made difficult, thanks Desktop
>>>>>>>>>>> Linux. It would be too simple to install the missing dependency
>>>>>>>>>>> yourself wouldn't it?
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> A quick scan of the Ubuntu forums show this as a common problem
>>>>>>>>>> with lots of solutions that don't work. I was contemplating
>>>>>>>>>> switching this old PC for a Windows on a stick PC, might just
>>>>>>>>>> bring that project forward.
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>> Did the solution of being at the latest point release of 14.04
>>>>>>>>> before upgrading not work?
>>>>>>>>>
>>>>>>>>
>>>>>>>> It should be up to date as I regularly update it but it looks like
>>>>>>>> there is a problem. Currently I'm:
>>>>>>>>
>>>>>>>> DISTRIB_ID=Ubuntu
>>>>>>>> DISTRIB_RELEASE=14.04
>>>>>>>> DISTRIB_CODENAME=trusty
>>>>>>>> DISTRIB_DESCRIPTION="Ubuntu 14.04.2 LTS"
>>>>>>>>
>>>>>>>> When I run "sudo apt-get update" it fails with an error:
>>>>>>>>
>>>>>>>> W: There is no public key available for the following key IDs:
>>>>>>>> 1397BC53640DB551
>>>>>>>> W: Failed to fetch
>>>>>>>> http://dl.google.com/linux/chrome/deb/dists/stable/Release  Unable
>>>>>>>> to find expected entry 'main/binary-i386/Packages' in Release file
>>>>>>>> (Wrong sources.list entry or malformed file)
>>>>>>>>
>>>>>>>> E: Some index files failed to download. They have been ignored, or
>>>>>>>> old ones used instead.
>>>>>>>>
>>>>>>>>
>>>>>>>> So then I run sudo apt-key adv --keyserver keyserver.ubuntu.com
>>>>>>>> --recv-keys 1397BC53640DB551
>>>>>>>>
>>>>>>>> I'm left with:
>>>>>>>> W: Failed to fetch
>>>>>>>> http://dl.google.com/linux/chrome/deb/dists/stable/Release  Unable
>>>>>>>> to find expected entry 'main/binary-i386/Packages' in Release file
>>>>>>>> (Wrong sources.list entry or malformed file)
>>>>>>>>
>>>>>>>> E: Some index files failed to download. They have been ignored, or
>>>>>>>> old ones used instead.
>>>>>>>>
>>>>>>>>
>>>>>>>> What a fucking mess and wasting so much time. Looks like Chrome is
>>>>>>>> prevent the OS from being upgraded. WTF? Seriously WTF?
>>>>>>>>
>>>>>>>> The only solution I've found so far that seems to have any chance
>>>>>>>> of working is to backup the data, wipe and install 16.04 as a fresh
>>>>>>>> install. Wow! Imagine if that was a Windows resolution, the Linux
>>>>>>>> loons would have a field day but when it's a Linux solution, that's
>>>>>>>> OK.
>>>>>>>
>>>>>>> What's Canonical's policy for jumping 2 major levels?
>>>>>>> Is it even officially supported?
>>>>>>>
>>>>>>
>>>>>> No idea but I think I've found the issue now. In "Software & Updates"
>>>>>> manager, "Important security updates" and "Recommended updates" was
>>>>>> not checked. It's now updating to the latest point release. Hopefully
>>>>>> I'll be able to do the upgrade after it's finished.
>>>>>
>>>>> Sounds good. If it works and you have the time please share with the
>>>>> Ubuntu community so other Linux users can benefit from your trouble
>>>>> shooting.
>>>>>
>>>>
>>>> Yup it worked. The resulting update then took most of the day and kept
>>>> wanting to overwrite config files I'd modified. After it finished and
>>>> rebooted my Dashing dashboard refused to run. Ruby had been updated so
>>>> I had to basically re-install it all, not a biggie but having done that
>>>> none of my widgets worked because the update had completely removed PHP
>>>> and all the addons such as curl and xml support. Why? FFS! WHY!
>>> 
>>> You are /way/ over my head!
>>
>> Thanks, unlike many of the so-called advocates in here I do more with
>> Linux than play on it in a basement. This particular system does real
>> work in my business as it displays real-time information to the techs so
>> they know how many open tickets we have and offline servers etc.
> 
> I get the impression that most of the Linux advocates in COLA don't work
> with Linux during their day jobs.

While lying filth like "Desk Rabbit" don't work with linux ever

[toc] | [prev] | [next] | [standalone]

#376650

Peter Köhlmann wrote:

> "Jim" trolled:
>> 
>> I get the impression that most of the Linux advocates in COLA don't work
>> with Linux during their day jobs.

I get the impression that many, if not most, of us do.  I know that I
do, even though my main office PC is WinDOS.

> While lying filth like "Desk Rabbit" don't work with linux ever

I get the impression that no one who matters cares what "Jim" claims
to think.

-- 
"So simple... just write your own maps app, create your own app-store
and build your own ecosystem like Amazon was forced to do."  -
Ezekreep, whining that if you want to use the Free Android operating
system, but want your own app-store and ecosystem apart from Google's,
you have to create and build your own app-store and ecosystem.

[toc] | [prev] | [next] | [standalone]

#376684

Peter Köhlmann wrote this copyrighted missive and expects royalties:

> Jim Polaski wrote:
>> 
>> I get the impression that most of the Linux advocates in COLA don't work
>> with Linux during their day jobs.
>
> While lying filth like "Desk Rabbit" don't work with linux ever

I use Linux pretty much all day long.  The IT restrictions are so onerous
on Windows that there's no way I would run a native Windows system on its
network.

-- 
Q:	Do you know what the death rate around here is?
A:	One per person.

[toc] | [prev] | [next] | [standalone]

Page 1 of 2  [1] 2  Next page →

Back to top | Article view | comp.os.linux.advocacy

csiph-web