[DC LoCo] Latest misadventures with Precise

jerry w jerrywone at gmail.com
Sun Jan 29 11:30:22 UTC 2012


Another thing that I'm "breaking"...

Nanny.Tap (Parental Controls with EduBuntu
and System Tap?  Python 2.7? on some Init booting script?)
will not boot all the way...

I removed SystemTap with Synaptic but still having the problem
Ever since, Synaptic doesn't find anything Nanny nor
SystemTap related to delete.  (It's breaking it, and I don't
have to have it, why not delete / remove it?)

Possibly related, I was not getting a graphical boot,
SuperBlock had "a time in the future, but the same day",
FSCK fixed it, each boot, when I asked
on recovery or similar and then a screenrc?
or something detecting graphical hardware
for XOrg from like 5-8 days now, struggled with it for a while...

I had this convoluted manual process to get to anything graphical
like web based mail to report this issue to others
and ask for help/ suggestions...

LXDE was broken,
and I disturbingly found Lubuntu is Gnome3 based
when I tried to remove Gnome3
according to a LinuxNewBorn.BlogSpot.com entry
(PPA-Purge Gnome3Team or similar command listed
in that 11.xx based article doesn't work on mine)
but somehow reinstalling Lubuntu / LXDE stuff
did give me back my LXDE booting,
though I can't seem to graphically login
to my normal account (screen flashes
to the Nanny Tap console boot screen issue and stops there
going back to prompt for login...)...
when it used to boot flashing for 56 times or so
(XOrg mode checking?)  Now, Guest account works
from graphical login so that is an improvement!
and I can still go out to control-alt-F1 with a console
to apt-get update upgrade
for latest improvements).

I'm figuratively Bleeding Out Here on the Edge,
and should know better than to write emails
to knowledgeable people at 5 or 6 am,
when tired, but still struggling.

I'm not positive what happened, updates broke stuff?,
I fell from a bike with the machine in a messenger bag
on Tuesday but it worked fine later that night...,
so I can't figure out what caused it.
Maybe CMOS type battery going
on This Old EeePC?

Or some confusing combination of lots of things...


-- 
Jerry W



More information about the Ubuntu-us-dc mailing list