On 11/15/2011 07:50 PM, Jim Cromie wrote:
> On Tue, Nov 15, 2011 at 7:46 PM, Joe Zeff wrote:
>> On 11/15/2011 06:30 PM, Jim Cromie wrote:
>>> "somethings gone wrong, . contact administator"
>>
>> There's only one way to deal with programmers who think that's an
>> appropriate error message: gi
On Tue, Nov 15, 2011 at 7:46 PM, Joe Zeff wrote:
> On 11/15/2011 06:30 PM, Jim Cromie wrote:
>> "somethings gone wrong, . contact administator"
>
> There's only one way to deal with programmers who think that's an
> appropriate error message: give their GPS coordinates to OADS
> (http://www.im
Hi Jim,
I had the same issue with my 64bit machine (my 32 bit machine work
perfectly). I ended up following the instructions about removing
directories described at
http://www.linuxquestions.org/questions/fedora-35/fedora-16-oh-no-something-has-gone-wrong-912796/and
my machine is now up an runnin
On 11/15/2011 06:30 PM, Jim Cromie wrote:
> "somethings gone wrong, . contact administator"
There's only one way to deal with programmers who think that's an
appropriate error message: give their GPS coordinates to OADS
(http://www.impsec.org/~jhardin/OADS/anvil_chorus.html).
Grovelling thr
I just upgraded my 64bit box to F-16 using preupgrade, and the
graphical login is busted.
It displays the nice bathyscath (deep sea) screen for a second,
then goes black with a sad computer face |:-(| saying non-specifically
"somethings gone wrong, . contact administator"
Box boots ok to run
