failed upgrade from 12.04 to 14.04

William Frick frickwg at gmail.com
Fri Oct 17 15:49:05 UTC 2014


Truly hope all is well ... my 14.04 still has some issues where 12.04
worked and 14.04 doesn't .... check all your apps and network connections.


On Fri, Oct 17, 2014 at 10:32 AM, Doug Stewart <doug.dastew at gmail.com>
wrote:

> Just putting some closure to this discussion.
> I finally did a backup and then installed a new version of 14.04
> All is well now.
> Thanks to all the helped.
> Doug
>
> On Fri, Aug 29, 2014 at 2:40 PM, Doug Stewart <doug.dastew at gmail.com>
> wrote:
>
>>
>>
>>
>> On Thu, Aug 28, 2014 at 6:21 PM, Doug Stewart <doug.dastew at gmail.com>
>> wrote:
>>
>>>
>>>
>>>
>>> On Thu, Aug 28, 2014 at 5:32 PM, Stephen M. Webb <
>>> stephen.webb at canonical.com> wrote:
>>>
>>>> On 08/28/2014 03:57 PM, Doug Stewart wrote:
>>>> >
>>>> > ~/.xsession-errors   says there is an error. I would like to write
>>>> the file to a memory stick and then bring it to
>>>> > this comp. so that I can show the error in the email -- But!! how do
>>>> I find the memory stick, from the command
>>>> > prompt????????
>>>> >
>>>> > If I can find where the memory stick is then I can copy the file to
>>>> it etc.
>>>>
>>>> If it's automounted, it will be under /media (eg. /media/5683-A928).
>>>>
>>>> If it's not automounted, you'd need to check the name of the raw block
>>>> device (like /dev/hdb) and mount it using a
>>>> command like 'sudo mount /dev/hdb1 -o rw /media/disk'.  Hopefully it's
>>>> automounted.  Automunting was invented for a
>>>> good reason.
>>>>
>>>> You could probably also use 'pastebinit' from the command line if you
>>>> install the pastebinit package.  That will copy
>>>> the file to a paste site and tell you the URL, which you can copy down
>>>> and type in.
>>>>
>>>> --
>>>>
>>>
>>>
>>>
>>>
>>> I had to
>>>
>>> mkdir /media/mmdisk
>>> sudo mount /dev/sdg1 -o rw /media/disk'
>>>
>>> and then cp it
>>>
>>> here it is
>>>
>>> X Error of failed request:  BadRequest (invalid request code or no such
>>> operation)
>>>   Major opcode of failed request:  155 (GLX)
>>>   Minor opcode of failed request:  19 (X_GLXQueryServerString)
>>>   Serial number of failed request:  22
>>>   Current serial number in output stream:  22
>>> openConnection: connect: No such file or directory
>>> cannot connect to brltty at :0
>>> Script for ibus started at run_im.
>>> Script for auto started at run_im.
>>> Script for default started at run_im.
>>> init: at-spi2-registryd main process ended, respawning
>>> init: at-spi2-registryd main process ended, respawning
>>> init: at-spi2-registryd main process ended, respawning
>>> init: at-spi2-registryd main process ended, respawning
>>> init: at-spi2-registryd main process ended, respawning
>>> init: at-spi2-registryd main process ended, respawning
>>> init: at-spi2-registryd main process ended, respawning
>>> init: at-spi2-registryd main process ended, respawning
>>> init: at-spi2-registryd main process ended, respawning
>>> init: at-spi2-registryd main process ended, respawning
>>> init: at-spi2-registryd respawning too fast, stopped
>>>
>>>
>>
>>
>>
>> what should I do now????
>>
>>> doug S.
>>>
>>> --
>>> DAS[image: Certificate for 206392]
>>>
>>>  <https://linuxcounter.net/user/206392.html>
>>>
>>
>>
>>
>> --
>> DAS[image: Certificate for 206392]
>>
>> <https://linuxcounter.net/user/206392.html>
>>
>
>
>
> --
> DAS[image: Certificate for 206392]
>
> <https://linuxcounter.net/user/206392.html>
>
> --
> ubuntu-ca mailing list
> ubuntu-ca at lists.ubuntu.com
> https://lists.ubuntu.com/mailman/listinfo/ubuntu-ca
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.ubuntu.com/archives/ubuntu-ca/attachments/20141017/dcc67f20/attachment.html>


More information about the ubuntu-ca mailing list