Stop "dbus." startx, update/upgrade errors?
Israel
israeldahl at gmail.com
Mon Dec 1 13:17:52 UTC 2014
On 11/30/2014 12:02 PM, Fritz Hudnut wrote:
>
>
> From: Israel <israeldahl at gmail.com <mailto:israeldahl at gmail.com>>
> To: lubuntu-users at lists.ubuntu.com
> <mailto:lubuntu-users at lists.ubuntu.com>
> Subject: Re: Stop "dbus." startx, or self sabotage?
> Message-ID: <5478B45B.6070706 at gmail.com
> <mailto: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
>
>
>
>
>
Hi Fritz,
There may be another configuration file that needs to be moved. You can
try moving
~/.dbus and see if that helps.
You can also run sudo dpkg-reconfigure dbus if you want to try to
reconfigure it again.
Unfortunately I have found that configuration files can pose a large
problem sometimes when upgrading.
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.
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.
give those a try and see what you come up with.
--
Regards
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.ubuntu.com/archives/lubuntu-users/attachments/20141201/394f10b1/attachment.html>
More information about the Lubuntu-users
mailing list