Description of problem: Every time after turning on zoom gnome-shell immediately crashes with "Oh, no! ...." with an only option to terminate a session. Just to make matters more interesting every subsequent attempt to log in after such crash ends up with some scattered bits and pieces of graphics on a desktop and non-functional mouse and a keyboard making a recovery into a puzzle. Nothing in .xsession-errors. Apparently the following fragments from logs are related: ..... gnome-session[9537]: Window manager warning: Log level 16: Couldn't register with accessibility bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. gnome-session[9537]: Window manager warning: Log level 6: AT-SPI: COuldn't connect to accessibility bus. Is at-spi-bus-launcher running? kernel: traps: gnome-shell[9628] trap int3 ip:31b3a504e9 sp:7fff1b409b60 error:0 gnome-session[9537]: (gnome-settings-daemon:9557): GnomeDesktop-WARNING **: Failed to acquire idle monitor proxy: GDBus.Error:org.freedesktop.DBus.Error.NoReply: Message did not receive a reply (timeout by message bus) Yes, at-spi-bus-launcher is running and clearly visible in a processes table. It is apparently launched by lightdm which I am using here for a display-manager.service. Experiments on two independent user accounts had exactly the same outcome. Version-Release number of selected component (if applicable): gnome-shell-3.10.2.1-3.fc20.x86_64 dconf-0.18.0-2.fc20.x86_64 lightdm-1.8.5-2.fc20.x86_64 How reproducible: always Steps to Reproduce: 1. Just to turn zoom on (I used 1.2 magnification for these tests). Expected results: gnome-shell does not go south because it does not like something in a configuration it wrote and leaving a user without at least minimum of functionality. Additional info: Zoom in gnome-shell used to work before switching from F18 to F20. There is nothing obvious in gsettings output which would allow to turn that zoom off so recovery is not obvious. Due to so many times repeated elsewhere a gros design mistake configuration data are stored in a binary form and one has to _guess_ that ~/.config/dconf/user is buggered. So one either has to restore that from backups, if such exist, or remove it entirely and loose all customizations recorded unfortunately in this one opaque basket. BTW - I tried turning on zoom after logging in with an old ~/.config/dconf/user and with this file initially removed. Results were exactly the same. See also bug 1051559 which appears to describe a related problem for RHEL 7.
I am also having the same issue under Fedora 20 gnome 3.12 and I cannot log in to my computer. Even when I removed the config file on ~/.config/dconf/user nothing was fixed. I don't want to reinstall anyone knows a workaround or something?
(In reply to Demetris Lambrou from comment #1) > I am also having the same issue under Fedora 20 gnome 3.12 and I cannot log > in to my computer. Even when I removed the config file on > ~/.config/dconf/user nothing was fixed. I don't want to reinstall anyone > knows a workaround or something? This doesn't fix the issue with the magnifier, but at least lets you log into your device again by turning off the magnifier: When you're seeing the graphical login screen, switch to a regular terminal (ie. press ctrl+alt+F2) and log in with your user name and password there. Then manually disable the magnifier: dbus-launch gsettings set org.gnome.desktop.a11y.applications screen-magnifier-enabled false Once this is done, you can switch back to the regular GUI-login page (ie. press ctrl+alt+F1) and log in as you normally would.
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.