error banner popped up: Oh oh ... Something went wrong ...

[JD]

FC16, just run a full update.
Rebooted (with latest kernel).

I got the error banner for the first time during boot, but just before 
the gdm greeting banner:

Oh, oh. Something went wrong ....etc.

Found that someone has opened a bug about this with redhat bugzilla: 819340
back in May of this year (2012).

No one has responded to this bug.

Anyone else seen this error message?

[Reindl Harald]

Am 26.08.2012 02:41, schrieb Joe Zeff:
>  On 08/25/2012 04:28 PM, JD wrote:
> > The way the apps are stacked so deeply upon lib after lib, by the time
> > the failure
> > is returned to the calling app, the app has no ide what happened. The
> > high library
> > stack is very likely to blame.
>  
>  So?  Each lib that detects an error should log it instead of just returning with an error
> status-code.  Yes, I know
>  that this sometimes means eight or ten lines in the log for one issue, but something like
> that makes it easy to
>  spot.  As is, there doesn't seem to be any reliable way to track things back to the
> root cause. 
which would mean on a public sevrer with high traffic and a error
in any possibly not important library a SELF-DOS by filling
up your filesystem and kill your SAN with IO

[JD]

On 08/25/2012 06:41 PM, Joe Zeff wrote:
>  On 08/25/2012 04:28 PM, JD wrote:
> > The way the apps are stacked so deeply upon lib after lib, by the time
> > the failure
> > is returned to the calling app, the app has no ide what happened. The
> > high library
> > stack is very likely to blame.
>
>  So?  Each lib that detects an error should log it instead of just 
>  returning with an error status-code.  Yes, I know that this sometimes 
>  means eight or ten lines in the log for one issue, but something like 
>  that makes it easy to spot.  As is, there doesn't seem to be any 
>  reliable way to track things back to the root cause. 
Yes, that is right. But heck
... much of this freeware was coded without 
the foresight of such deeply stacked calls.
So, I would say I excuse them just because it is hard to foresee all the 
possible side effects when so many different
libraries call upon each other to accomplish one func call by the top 
level app. Logging errors is a good thing, but
it has to be done so that they are all in one log file and the user can 
trace it back from the deepest call all the way
to the app and it's pid (which may be dead and gone by then).

All in all, I find it totally amazing that it all works as well as it 
does, instead of falling to pieces :)

Cheers,

JD

[Joe Zeff]

On 08/25/2012 04:28 PM, JD wrote:
>  The way the apps are stacked so deeply upon lib after lib, by the
> time
>  the failure
>  is returned to the calling app, the app has no ide what happened. The
>  high library
>  stack is very likely to blame. 
So?  Each lib that detects an error should log it instead of just 
returning with an error status-code.  Yes, I know that this sometimes 
means eight or ten lines in the log for one issue, but something like 
that makes it easy to spot.  As is, there doesn't seem to be any 
reliable way to track things back to the root cause.

[JD]

On 08/25/2012 04:00 PM, M A Young wrote:
>  On Sat, 25 Aug 2012, JD wrote:
>
> > FC16, just run a full update.
> > Rebooted (with latest kernel).
> >
> > I got the error banner for the first time during boot, but just 
> > before the gdm greeting banner:
> >
> > Oh, oh. Something went wrong ....etc.
> >
> > Found that someone has opened a bug about this with redhat bugzilla: 
> > 819340
> > back in May of this year (2012).
>
>  That is a rather useless generic error message (from gnome-shell I 
>  think) which doesn't give you a clue as to what actually went wrong, 
>  so the bug report you found could be a for completely different 
>  problem. Try logging in at a text console (which you can get to by 
>  pressing ctrl-alt-Function key, eg. ctrl-alt-F3) and checking logs 
>  such as /var/log/gdm or /var/log/Xorg.0.log to see if they give some 
>  clue as to what the problem actually is.
>
>      Michael Young 
Thanx. No file in /var/log/ and sudirs thereof contained any hint
of the 
error.

The bug I found was talking about the same experience and the OP did mention
the gnome shell.

[Joe Zeff]

On 08/25/2012 03:00 PM, M A Young wrote:
>  That is a rather useless generic error message (from gnome-shell I
>  think) which doesn't give you a clue as to what actually went wrong, so
>  the bug report you found could be a for completely different problem. 
And, AIUI, there's no clear way to get any further information about 
what happened or how to correct it.  IMAO, whoever decided that it was a 
good idea to use such a useless error message should be taken out and 
shot.  Never mind waiting until sunrise, just taken out and shot![1]

[1]Anybody who can tell me where I got that line from gets a $25 dollar 
gift certificate for the Hidalgo Trading Company.[2]
[2]Hint, hint, hint!

[JD]

On 08/25/2012 04:11 PM, Joe Zeff wrote:
>  On 08/25/2012 03:00 PM, M A Young wrote:
> >
> > That is a rather useless generic error message (from gnome-shell I
> > think) which doesn't give you a clue as to what actually went wrong, so
> > the bug report you found could be a for completely different problem.
>
>  And, AIUI, there's no clear way to get any further information about 
>  what happened or how to correct it.  IMAO, whoever decided that it was 
>  a good idea to use such a useless error message should be taken out 
>  and shot.  Never mind waiting until sunrise, just taken out and shot![1]
>
>  [1]Anybody who can tell me where I got that line from gets a $25 
>  dollar gift certificate for the Hidalgo Trading Company.[2]
>  [2]Hint, hint, hint! 
  :) :)
The way the apps are stacked so deeply upon lib after lib, by the time 
the failure
is returned to the calling app, the app has no ide what happened. The 
high library
stack is very likely to blame.

[M A Young]

On Sat, 25 Aug 2012, JD wrote:

>  FC16, just run a full update.
>  Rebooted (with latest kernel).
>
>  I got the error banner for the first time during boot, but just before the 
>  gdm greeting banner:
>
>  Oh, oh. Something went wrong ....etc.
>
>  Found that someone has opened a bug about this with redhat bugzilla: 819340
>  back in May of this year (2012). 
That is a rather useless generic error message (from gnome-shell I think) 
which doesn't give you a clue as to what actually went wrong, so the bug 
report you found could be a for completely different problem. Try logging 
in at a text console (which you can get to by pressing ctrl-alt-Function 
key, eg. ctrl-alt-F3) and checking logs such as /var/log/gdm or 
/var/log/Xorg.0.log to see if they give some clue as to what the problem 
actually is.

 	Michael Young