Description of problem: On an Acer AOD250 Netbook, F-16 Alpha Gnome LIVE fails displaying "Oh no! Something has done wrong" at login.
Version-Release number of selected component (if applicable):F-16-Alpha
Steps to Reproduce:Boot up
Additional info:Tried from USB CD drive and USB flash drive, same results
Just tried this on an Acer Travelmate with Celeron processor as compared to the Atom processor in the netbooks. Same results.
can you be more specific as to what 'at login' means ?
Are you able to log in, but then starting the session fails ?
Or do you see the error screen before you ever get a chance to log in ?
In any case, please attach the .xsession-errors file that is left behind in your home directory.
(In reply to comment #2)
> can you be more specific as to what 'at login' means ?
> Are you able to log in, but then starting the session fails ?
> Or do you see the error screen before you ever get a chance to log in ?
> In any case, please attach the .xsession-errors file that is left behind in
> your home directory.
System boots from CD.
Bootup proceeds to desktop screen of jules verne submarine with mouse pointer working.
Instead of the login window, I see an unhappy monitor face with the text "Oh no! Something has done wrong" with "A problem has occurred and the system can't recover" and "Please logout and try again" followed by a Logout button.
So I never see the Login screen.
I tried an ALT-F2 and received a small popup window that says command not found when trying to look at .xsessions-error or anything else.
Can you suggest anything else?
Created attachment 521780 [details]
I have a similar issue, I get through the login, then it I get the "oh no".
This is an i5 t520 stinkpad, i think with the intel video.. I hadnt really gotten that far.. im still on grub issues. :)
If you type single in grub screen it doesnt put you into a login/rescue shell. Is this a grub issue? (it says starting but it must be attaching to the serial console or something..)
The I switched the runlevel3, rebooted, and am attaching the xsession-errors. BTW the file upload utility doesnt like the . in .xsession-errors.
I ran startx as a normal user and I don't accelerated video. It puts me into fallback mode. However it works.. even as I type this, unless I try Flash in the browser then it is slow to the point where im not even sure it works and it hangs the machine.
It happened after I updated either yesterday or the day before. Then I reinstalled the system, updated it, and it reappeared.
However up until that time at least this piece worked perfectly.
Same thing on Toshiba satellite. Only happens with gnome session, others ok
I was able to get around by init 3 and startx as root and didnt have any problems so not sure what is triggering this.
Just tested Fedora 16 Beta and this is fixed.
This message is a reminder that Fedora 16 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 16. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora
'version' of '16'.
Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version prior to Fedora 16's end of life.
Bug Reporter: Thank you for reporting this issue and we are sorry that
we may not be able to fix it before Fedora 16 is end of life. If you
would still like to see this bug fixed and are able to reproduce it
against a later version of Fedora, you are encouraged to click on
"Clone This Bug" and open it against that version of Fedora.
Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.
The process we are following is described here:
Fedora 16 changed to end-of-life (EOL) status on 2013-02-12. Fedora 16 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.
If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version.
Thank you for reporting this bug and we are sorry it could not be fixed.