Hide Forgot
Description of problem: having a weird problem in F16 with gnome-shell: Restarting the gnome-shell with "alt+f2" and "r" consecutively at most twice, the gnome session dies with the well known F16 message: "Oh no! Something has gone wrong. A problem has occured and the system can't recover. Please log out and try again". Found the following lines in /var/log/messages: .......... .......... Oct 26 16:13:14 eule gnome-session[1977]: WARNING: Application 'gnome-shell.desktop' killed by signal Oct 26 16:13:15 eule dbus[933]: [system] Activating via systemd: service name='org.bluez' unit='dbus-org.bluez.service' Oct 26 16:13:15 eule dbus-daemon[933]: dbus[933]: [system] Activating via systemd: service name='org.bluez' unit='dbus-org.bluez.service' Oct 26 16:13:15 eule dbus[933]: [system] Activation via systemd failed for unit 'dbus-org.bluez.service': Unit dbus-org.bluez.service failed to load: No such file or directory. See system logs and 'systemctl status dbus-org.bluez.service' for details. Oct 26 16:13:15 eule dbus-daemon[933]: dbus[933]: [system] Activation via systemd failed for unit 'dbus-org.bluez.service': Unit dbus-org.bluez.service failed to load: No such file or directory. See system logs and 'systemctl status dbus-org.bluez.service' for details. Oct 26 16:13:15 eule dbus[933]: [system] Activating via systemd: service name='org.bluez' unit='dbus-org.bluez.service' Oct 26 16:13:15 eule dbus-daemon[933]: dbus[933]: [system] Activating via systemd: service name='org.bluez' unit='dbus-org.bluez.service' Oct 26 16:13:15 eule dbus[933]: [system] Activation via systemd failed for unit 'dbus-org.bluez.service': Unit dbus-org.bluez.service failed to load: No such file or directory. See system logs and 'systemctl status dbus-org.bluez.service' for details. Oct 26 16:13:15 eule dbus-daemon[933]: dbus[933]: [system] Activation via systemd failed for unit 'dbus-org.bluez.service': Unit dbus-org.bluez.service failed to load: No such file or directory. See system logs and 'systemctl status dbus-org.bluez.service' for details. Oct 26 16:13:55 eule gnome-session[1977]: WARNING: App 'gnome-shell.desktop' respawning too quickly Oct 26 16:13:56 eule dbus[933]: [system] Activating via systemd: service name='org.bluez' unit='dbus-org.bluez.service' Oct 26 16:13:56 eule dbus-daemon[933]: dbus[933]: [system] Activating via systemd: service name='org.bluez' unit='dbus-org.bluez.service' Oct 26 16:13:56 eule dbus[933]: [system] Activation via systemd failed for unit 'dbus-org.bluez.service': Unit dbus-org.bluez.service failed to load: No such file or directory. See system logs and 'systemctl status dbus-org.bluez.service' for details. Oct 26 16:13:56 eule dbus-daemon[933]: dbus[933]: [system] Activation via systemd failed for unit 'dbus-org.bluez.service': Unit dbus-org.bluez.service failed to load: No such file or directory. See system logs and 'systemctl status dbus-org.bluez.service' for details. Oct 26 16:13:56 eule dbus[933]: [system] Activating via systemd: service name='org.bluez' unit='dbus-org.bluez.service' Oct 26 16:13:56 eule dbus-daemon[933]: dbus[933]: [system] Activating via systemd: service name='org.bluez' unit='dbus-org.bluez.service' Oct 26 16:13:56 eule dbus[933]: [system] Activation via systemd failed for unit 'dbus-org.bluez.service': Unit dbus-org.bluez.service failed to load: No such file or directory. See system logs and 'systemctl status dbus-org.bluez.service' for details. Oct 26 16:13:56 eule dbus-daemon[933]: dbus[933]: [system] Activation via systemd failed for unit 'dbus-org.bluez.service': Unit dbus-org.bluez.service failed to load: No such file or directory. See system logs and 'systemctl status dbus-org.bluez.service' for details. Oct 26 16:13:58 eule systemd-logind[904]: Removed session 4. Oct 26 16:13:59 eule systemd-logind[904]: New session 6 of user gdm. Oct 26 16:13:59 eule systemd-logind[904]: Linked /tmp/.X11-unix/X0 to /run/user/gdm/X11/display. Oct 26 16:13:59 eule gnome-session[3022]: DEBUG(+): Enabling debugging .......... .......... Version-Release number of selected component (if applicable): gnome-shell-3.2.1-1.fc16.x86_64 How reproducible: always Steps to Reproduce: 1.Login into a gnome session 2.Twice: alt+f2 and "r" 3. Actual results: See description Expected results: session resumes Additional info:
I, too, am seeing this on a fresh install of FC16 on an MSI Megabook notebook (x86_64). Can only run in run level 3 as gnome is unstable. Exactly same oh no message if startx manually or attempt to start into graphical.target for run level 5. What if you don't use bluetooth? TIA, Henry
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: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
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.