Description of problem: Install from Fedora-15-Beta-x86_64-Live-Desktop.iso 15 May 2011. Login to gnome shell successfully. Update to the latest packages. Next shutdown. Today try to login to gnome-shell and got screen X11 graphics page with a "sad monitor" icon and the message "On no! SSomething has gone wrong. A problem has occured and the system can't recover. Please log out and try again." Version-Release number of selected component (if applicable): gdm-3.0.0-3.fc15-x86_64 This is not 693502 bug. I have gnome-menus-3.0.1-1.fc15-x86_64 installed How reproducible: try to login Steps to Reproduce: 1.login 2. 3. Actual results: Full-screen X11 graphics with "sad monitor" and "Oh no! Something has gone wrong. A problem has occured and the system can't recover. Please log out and try again." Expected results: login into the gnome environment Additional info:
Created attachment 499183 [details] /var/log/messages for affected system
Created attachment 499184 [details] /var/log/Xorg.0.log from the affected assistem
Created attachment 499185 [details] .xsession-errors from user's dir
I am having the same problem. After the installation of the Fedora-15-Beta-x86_64 all is fine, but when I change the desktop background to a solid color then the problem appeared. I change my home directory, reboot, and I get my Gnome3 desktop with the initial background back and everything is working fine, again changing to a solid background and: "Oh no! Something has gone wrong. A problem has occured and the system can't recover. Please log out and try again." I have gnome-menus-3.0.1-1.fc15.x86_64 and gnome-shell-3.0.1-4.fc15.x86_64 installed with yum update.
It appears that the crash is happening in Gconf2, but I haven't had a chance to poke at it with gdb.
I am having a near similar problem. I have a fresh install of Fc15 from the newly released i386 iso on a Dell 8250 with 1.2 g memory. There were no difficulties identified during the install. I have not been able to login with the use of gnome. When I try to login I get the same message as above : Full-screen X11 graphics with "sad monitor" and "Oh no! Something has gone wrong. A problem has occured and the system can't recover. Please log out and try again." When I try to log out and log back in I get the same message. I have been unable to login with the use of gnome. I can login by means of kde.
I found the GConf2 crash -- gsettings-data-convert was aborting with the error message GLib-GIO-ERROR **: Settings schema 'org.gnome.packagekit' does not contain a key named 'watch-active-transactions' Removing the offending line in /usr/share/GConf2/gsettings/org.gnome.packagekit.gschema.migrate solved that particular problem. Not sure if this particular crash is truly related though.
Ok, I think I solved the real problem. The GConf2 thing wasn't the main issue. It seems that compiz was still being auto-started. It's possible that cairo-dock was interfering as well. Removing both from the user autostart directory solved the problem for me.
Tristan, Your observations are interesting. On my system the /home/$user/.gconf/autostart directories are not even being created. So whatever my problem might be, it is must be happening before the autostart directory is created at first login with genome.
I decided to do another clean install on the same machine and obtained the same results. I also created a live cd and have received the same results when it boots. The monitor I am using is a Prineton 72e with a resolution of 1,280 x 1,024. I am suspicious that there may be a problem with Fedora 15 recognize the resolution of this monitor, but I am uncertain. I have not been able to figure out how to manually set the resolution without going through a gnome gui, kde works fine.
I switched monitors from the Princeton to a Dell E2011H without a change in symptomatology. I am at a loss at this point of knowing what to try to change next.
My system has been running for over a week, then I got this error. My only solution until gnome fix is released was: yum install kdebase yum install @kde-desktop and login using KDE... at least I didn't have to reinstall or lose anything! (except for gnome).
The above worked enough for me to very I had not lost my a$$. Then I: yum erase @kde-desktop yum install @gnome-desktop (still error) yum erase @gnome-desktop rm -rf /etc/xdg/autostart/* rm -rf ~/.gnome2 rm -rf ~/.gconf rm -rf ~/.gconfd yum install @gnome-desktop reboot now, everything is working where I was 5 hours ago when this started. All my apps are still here, all my development VMs, etc. * Hope this helps anyone else who all of a sudden gets "Oh No!" Ozz
I encountered the same error after upgrading from F13 to F15 (using the preupgrade tool); however, the scenario may be a bit different. In my scenario, I have a dual monitor configuration. After logging in, the right monitor would immediately display: "Oh no! Something has gone wrong. A problem has occured and the system can't recover. Please log out and try again."; however, the left monitor was still operational. If I opened a terminal using the left monitor and selected it, the message would go away; however, if I minimized it, the message came back. I performed the following: rm -rf ~/.gnome2 rm -rf ~/.gconf rm -rf ~/.gconfd logged out/in The message is no longer appearing on the right screen. If the error message returns, will post an update to the bugzilla.
Ozz, I followed your game plan and did the following : yum erase @gnome-desktop rm -rf /etc/xdg/autostart/* rm -rf ~/.gnome2 rm -rf ~/.gconf rm -rf ~/.gconfd yum install @gnome-desktop reboot Unfortunately, This did not fix my problem; I still have the "Oh No" message Greg
I too have discovered by trial and error that removing .gnome2/.gconf/.gconfd fixes the problem. I'm trying to narrow it down to something specific but it looks like this particular issue can be related to user configuration since I have the issue periodically, but the other users on the system do not. And I *just* encountered this problem on another system immediately after installing a few gnome-shell extensions (using yum) and running gnome tweak tool to make a few tweaks to the configs.
Steven, Do you have any idea which extensions or what aspects of the gnome tweak tool may have caused the problem. I am have not been able to access gnome3 at all on my system. Greg
FWIW, I'm having this problem when connecting to fedora 15 using NoMachine free NX from a Mac OS X 10.6.8 system.
I think it is the Places gnome-shell-extension. Since removing that I haven't had the problem once. I had the same issue on two desktops and one laptop, and all are behaving (except for the occasional gnome shell lockup) now that the Places extension has been removed.
This same problem; rm ~/config/autostart/fusion-icon.desktop helped; I've left there only awn.desktop(avant window navigator). Now I can log into my account. Maybe compiz is really responsible for some cases of this bug(or maybe compiz is the only one cause?)
I'm on fedora15. I can find no Places gnome-shell-extension. I don't have a ~/config dir. Nor do I have a file named fusion-icon.desktop anywhere on my system.
Doesn't help me to rm -rf .gnome2 .gconf .gconfd
My mistake - ~/.config, not ~/config.
I have no ~/.config/autostart/ dir.
I have also read that this is related to some video hardware. In my case it is related to the places extension, since I just re-installed it and tried to restart gnome-shell (alt+F2 'r' Enter) and the window manager froze, no borders or decorations showed up. I switched to vt2 (Ctrl+Alt+F2 and logged in as root and saved my .xsession-errors file and noticed this, which looks suspicious. I removed Places again and all was back to normal, ** Message: applet now removed from the notification area gnome-shell-calendar-server[29178]: Got HUP on stdin - exiting JS ERROR: !!! Exception was: Error: Argument 'actor' (type interface) may not be null JS ERROR: !!! lineNumber = '0' JS ERROR: !!! fileName = 'gjs_throw' JS ERROR: !!! stack = '("Argument 'actor' (type interface) may not be null")@gjs_throw:0 (null,[object Object])@/usr/share/gnome-shell/js/ui/popupMenu.js:128 ()@/usr/share/gnome-shell/extensions/places-menu.org/extension.js:75 ()@/usr/share/gnome-shell/extensions/places-menu.org/extension.js:35 PlacesMenu()@/usr/share/gnome-shell/extensions/places-menu.org/extension.js:20 ()@/usr/share/gnome-shell/js/ui/panel.js:1051 start()@/usr/share/gnome-shell/js/ui/main.js:204 @<main>:1 ' JS ERROR: !!! message = 'Argument 'actor' (type interface) may not be null' Window manager warning: Log level 32: Execution of main.js threw exception: Error: Argument 'actor' (type interface) may not be null gnome-shell-calendar-server[29449]: Got HUP on stdin - exiting
extensions.js:75 is in the function _createBookmarks, 73 this.bookmarkItems[bookmarkid] = new PopupMenu.PopupMenuItem(_(this.bookmarks[bookmarkid].name)); 74 let icon = this.bookmarks[bookmarkid].iconFactory(PLACE_ICON_SIZE); 75 this.bookmarkItems[bookmarkid].addActor(icon, { align: St.Align.END}); 76 this.bookmarkItems[bookmarkid].place = this.bookmarks[bookmarkid]; 77 this._bookmarksSection.addMenuItem(this.bookmarkItems[bookmarkid]); 78 this.bookmarkItems[bookmarkid].connect('activate', function(actor,event) { actor.place.launch(); }); so it seems to be related to the call to addActor, possible the value of the icon being passed to it.
After a new kernel 2.6.38.8-35.fc15.i686.PAE was updated on my F15 system I was able to login via gnome3. I was getting ready to remove gnome-places and tried to login after an update, and made it. Gnome3 seems to have at times an extremely slow response rate to 'clicked selections' but at least I can login to the gnome3 desktop.
Happens on my wife's, my son's, and my computer. Not tried on my work computer yet. These machines are upgraded many times from a long way back (Fedora 11 or earlier), all now running XFCE. Is there some odd situation where upgrades have left something Gnome 3 does not like?
Gnome 3 worked reliably on all four computers till about 30 September. All have all updates applied. Mine has non-proprietary amd video drivers; my wife and son have proprietary amd drivers on their iMac 27".
Upgraded from yum using preupgrade. multiple problems getting F16 to run then, it did. I don't know why, I guess it got tired of my restarting it repeatedly. I have made some videos of the problem and posted them here http://www.youtube.com/playlist?list=PL04C00B1F699A7C56 When I go to root the keyboard switches to Dvorak which makes it tough as my Dvorak typing skills are low. How can I get my F16 machine to run properly?
having this issue on a fresh F16. Accidently reported this as a new bug. https://bugzilla.redhat.com/show_bug.cgi?id=770877 please report it as duplicate.
Had the problem before and it appeared fixed by removing and re-installing gnome-color-manager. Everything worked for a little but it just came back, I removed gnome-shell-extension-places-menu-3.4.0-1.fc17.noarch as that was mentioned earlier in this ticket and that appears to have solved it.
Getting this on F17 beta, but even before the login window appears. Maybe a new bug is due for this. However, in any case: this "error message" is just stupid. "something is not working, please contact your sysadmin" are these dreadful and totally unhelpful messages on MS Windows. There are so many processes involved in generating the X11 login window, at least printing out the name of the error log would help here.
Workaround (at least for me): yum remove gnome-shell Now the Xorg login window appears and login succeeds.
Can we change this bug report to F17?
(In reply to comment #36) > Can we change this bug report to F17? This bug mixes together 5-10 unrelated issues including resolved issues, gnome-settings-daemon issues, GL driver issues, and so forth. If you are hitting a failure screen with Fedora 17, please file a separate bug with as much detail as possible about it. Thanks!
hmm might need to send in the clones indeed. regarding comment#37: https://bugzilla.redhat.com/show_bug.cgi?id=820095 RFE: add detail to the 'Oh no! Something has gone wrong' error message
Seems like this error has something to do with firefox or xulrunner as i updated my firefox 4 to firefox 12 this error came to my screen like a devil. so i downgrade my last update by doing yum history undo yum_id which installed thunderbird and updated firefox and everything works fine now :)
Just want to tell you that updating x86 fedora architecture to latest also results sameas x86_64 in my toshiba C665 Laptop. above workaround worked for me in x86 arch
This message is a notice that Fedora 15 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 15. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At this time, all open bugs with a Fedora 'version' of '15' have been closed as WONTFIX. (Please note: Our normal process is to give advanced warning of this occurring, but we forgot to do that. A thousand apologies.) Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, feel free to reopen this bug and simply change the 'version' to a later Fedora version. Bug Reporter: Thank you for reporting this issue and we are sorry that we were unable to fix it before Fedora 15 reached 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" (top right of this page) 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: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Still happening. For me, when using a cirrus logic vga based system, and opening control-center to select a different display. I know these are all different errors, but I would like this bug to emphasize: - The window just covers up everything - The message gives no diagnostic whatsoever - The user has no way of further diagnosing the problem because there is no cause listed, not even a package or binary that crashed and caused this. As such, we see this bug has a large list of likely unrelated bug reports, all because it is brushed under the carpet with this useless 'oh no' window.
Created attachment 885794 [details] /var/log/gdm/:0-greeter.log The content is identical either after booting the system ( this time w/o Oh no) or after starting xinit .. gnome-session ( including Oh no).
Additional Comment to Comment 43. It still happens with Fedora 20. Graphics driver is either nouveau or ATI. During boot, before the three color Fedora progress bar is being displayed the bottom right screen is corrupted (small collored tiles) The display is 1920x1080. Emergency help: open tty (Strg+Alt+F2), login, xinit -- :1, start-kde. Debug help: open tty (Strg+Alt+F2), login, xinit -- :2, strace gnome-session. Content of /var/log/gdm/:0-greeter.log pls. see previous comment
(In reply to H.-P. Sorge from comment #43) > Created attachment 885794 [details] > /var/log/gdm/:0-greeter.log > > The content is identical either after booting the system ( this time w/o Oh > no) > or after starting xinit .. gnome-session ( including Oh no). Please ignore this attachment - I missed to check the date - it's from an older bug.
(In reply to H.-P. Sorge from comment #44) > Additional Comment to Comment 43. > > It still happens with Fedora 20. Graphics driver is either nouveau or ATI. > > During boot, before the three color Fedora progress bar is being displayed > the bottom right screen is corrupted (small collored tiles) > The display is 1920x1080. > > Emergency help: open tty (Strg+Alt+F2), login, xinit -- :1, start-kde. > > Debug help: open tty (Strg+Alt+F2), login, xinit -- :2, strace > gnome-session. > > ------------------------------------------------------------------------ > Content of /var/log/gdm/:0-greeter.log pls. see previous comment Please ignore this reference to Comment 43.
I have to apologize for the buggy report before - This one seems to give some better insight. From a terminal session let's see what /var/log/messages catches.. [hps@localhost ~]$ date ; gnome-session; date So 13. Apr 11:13:16 CEST 2014 # First timestamp.... Oh no! ... . Hit RETURN So 13. Apr 11:13:17 CEST 2014 # Second timestamp ---------------- check /var/log/messages [hps@localhost ~]$ su -l Passwort: [root@localhost ~]# less /var/log/messages SNIP ..... Apr 13 11:13:16 localhost gnome-session: gnome-session[6593]: WARNING: Unable to find required component 'gnome-panel' Apr 13 11:13:16 localhost gnome-session[6593]: WARNING: Unable to find required component 'gnome-panel' Apr 13 11:13:16 localhost gnome-session: Entering running state ... ESNIP ------------------------------------- strange OK - fair - it is really not installed. I did a yum reinstall gmome* before - some missing dependencies? --------------------------------------So try again: [root@localhost ~]# yum install gnome-panel-* Geladene Plugins: langpacks, refresh-packagekit Abhängigkeiten werden aufgelöst --> Transaktionsprüfung wird ausgeführt ---> Paket gnome-panel-control.x86_64 0:3.5.2-2.fc20 markiert, um installiert zu werden --> Abhängigkeit openbox = 3.5.2-2.fc20 wird für Paket gnome-panel-control-3.5.2-2.fc20.x86_64 verarbeitet --> Abhängigkeit gnome-panel wird für Paket gnome-panel-control-3.5.2-2.fc20.x86_64 verarbeitet --> Transaktionsprüfung wird ausgeführt ---> Paket gnome-panel-control.x86_64 0:3.5.2-2.fc20 markiert, um installiert zu werden --> Abhängigkeit gnome-panel wird für Paket gnome-panel-control-3.5.2-2.fc20.x86_64 verarbeitet ---> Paket openbox.x86_64 0:3.5.2-2.fc20 markiert, um installiert zu werden --> Abhängigkeit openbox-libs(x86-64) = 3.5.2-2.fc20 wird für Paket openbox-3.5.2-2.fc20.x86_64 verarbeitet --> Abhängigkeit libobt.so.2()(64bit) wird für Paket openbox-3.5.2-2.fc20.x86_64 verarbeitet --> Abhängigkeit libobrender.so.29()(64bit) wird für Paket openbox-3.5.2-2.fc20.x86_64 verarbeitet --> Transaktionsprüfung wird ausgeführt ---> Paket gnome-panel-control.x86_64 0:3.5.2-2.fc20 markiert, um installiert zu werden --> Abhängigkeit gnome-panel wird für Paket gnome-panel-control-3.5.2-2.fc20.x86_64 verarbeitet ---> Paket openbox-libs.x86_64 0:3.5.2-2.fc20 markiert, um installiert zu werden --> Abhängigkeitsauflösung beendet Fehler: Paket: gnome-panel-control-3.5.2-2.fc20.x86_64 (fedora) Benötigt: gnome-panel Sie können versuchen, mit --skip-broken das Problem zu umgehen. Sie könnten Folgendes versuchen: rpm -Va --nofiles --nodigest -------------------------- TO BAD There is no gnome-pannel I hope it helps to resolve this Oh no!
This message is a reminder that Fedora 20 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 20. 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 EOL if it remains open with a Fedora 'version' of '20'. 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. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 20 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 change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. 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.
Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 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. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.