Stop "dbus." startx, update/upgrade errors?

[Fritz Hudnut]

I have added my issue to bug report # 1059254  "Lightdm fails to start
session" which has been marked as "invalid" . . . but I used it anyway, as
right now it is lightdm that is failing to start a GUI session.

F

On Sun, Nov 30, 2014 at 10:02 AM, Fritz Hudnut <este.el.paz at gmail.com>
wrote:

>
>
> From: Israel <israeldahl at gmail.com>
>> To: lubuntu-users at lists.ubuntu.com
>> Subject: Re: Stop "dbus." startx, or self sabotage?
>> Message-ID: <5478B45B.6070706 at gmail.com>
>> Content-Type: text/plain; charset="windows-1252"
>>
>> Hi again Fritz,
>> The other solution I use a lot for these types of issues is to move my
>> ~/.config directory to a backup
>> mv ~/.config ~/configOLD (or whatever name you like)
>> you can also move the .cache directory in the same way...
>> then copy things back that you need (like mozilla folder)
>> Hope this helps :)
>>
>
> @Israel:
>
> Frying pan, meet fire . . . I tried all those suggestions, except mv
> .cache . . . got into recovery and did the dpkg and fsck and the update etc
> . . . seeing errors "could not resolve 'ports.ubuntu'" I thought maybe the
> network connection is busted . . . ran the enable networking mode . . . saw
> something about "dbus" . . . "numerous "cannot add port tty/tty P20" lines
> . . . .
>
> running fsck:  dev/sda 4: Ionodes that were part of a corrupted orphan
> linked list found" "run fsck manually (w/o -a or -p options)" . . . [have
> not run fsck manually yet, if I knew how to]
> This list of errors ended with "skipping mounting / since Plymouth is not
> available"
>
> So, numerous issues seem to have been found . . . typing this in Guest
> session . . . obviously the network is "connected" . . . trying to log in
> to my user account just results in Catch-22 cycle of log in windows . . .
> .  Thinking about the history, since I'm using an newer apple keyboard I
> need to hit "fn" before the keyboard commands will work, so I don't think I
> inadvertently executed a command that did this, I'm under the possible
> belief that update/upgrade added something that caused a problem with the
> system??  Final clue???  In the pre-splash along with the i2s error is the
> radeon errors, "unable to find BIOS ROM"???  but again, able to get to log
> in window, or log in as Guest?
>
> F
>
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.ubuntu.com/archives/lubuntu-users/attachments/20141201/f5a64670/attachment.html>