<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">On 11/30/2014 12:02 PM, Fritz Hudnut
wrote:<br>
</div>
<blockquote
cite="mid:CAG62idDZKytwuSP1b0e4jOi262-jeukCdMC_oKn0XmxidmQSjg@mail.gmail.com"
type="cite">
<div dir="ltr">
<div class="gmail_extra"><br>
<div class="gmail_quote"><br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
<div id=":17i" class="a3s" style="overflow:hidden">
From: Israel <<a moz-do-not-send="true"
href="mailto:israeldahl@gmail.com">israeldahl@gmail.com</a>><br>
To: <a moz-do-not-send="true"
href="mailto:lubuntu-users@lists.ubuntu.com">lubuntu-users@lists.ubuntu.com</a><br>
Subject: Re: Stop "dbus." startx, or self sabotage?<br>
Message-ID: <<a moz-do-not-send="true"
href="mailto:5478B45B.6070706@gmail.com">5478B45B.6070706@gmail.com</a>><br>
Content-Type: text/plain; charset="windows-1252"<br>
<br>
Hi again Fritz,<br>
The other solution I use a lot for these types of issues
is to move my<br>
~/.config directory to a backup<br>
mv ~/.config ~/configOLD (or whatever name you like)<br>
you can also move the .cache directory in the same
way...<br>
then copy things back that you need (like mozilla
folder)<br>
Hope this helps :)</div>
</blockquote>
<div><br>
</div>
<div>@Israel:<br>
<br>
</div>
<div>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 . . . .<br>
<br>
</div>
<div>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]<br>
</div>
<div>This list of errors ended with "skipping mounting /
since Plymouth is not available"<br>
<br>
</div>
<div>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?<br>
<br>
</div>
<div>F<br>
</div>
<div> <br>
</div>
</div>
<br>
<br>
</div>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
</blockquote>
Hi Fritz,<br>
There may be another configuration file that needs to be moved. You
can try moving<br>
~/.dbus and see if that helps.<br>
You can also run sudo dpkg-reconfigure dbus if you want to try to
reconfigure it again.<br>
<br>
Unfortunately I have found that configuration files can pose a large
problem sometimes when upgrading.<br>
<br>
Oh, and I think unable to find BIOS ROM should be fairly normal,
since PPC doesn't use BIOS it uses Openfirmware. So it is an error,
but one that is expected from a non-BIOS machine, or at least that
is my opinion.<br>
<br>
My suspicion is that you are correct, the upgrade changed something
and now the configurations you have conflict with the new versions.
There may be some option that has changed.<br>
<br>
give those a try and see what you come up with.<br>
<pre class="moz-signature" cols="72">--
Regards</pre>
</body>
</html>