Created attachment 668433 [details] The .xsession-errors user's log file Description of problem: the GNOME Session/Gnome Shell crashes after a few seconds on login with the "Something went wrong..." splash when the printer server configured in /etc/cups/client.conf is not reachable. Version-Release number of selected component (if applicable): 3.4.2-4.fc17 How reproducible: Steps to Reproduce: 1. Edit/create the /etc/cups/client.conf to point to a enterprise-wide printer server instead of localhost: $ cat >> /etc/cups/client.conf<<EOF ServerName printserver.some.doma.in EOF 2. Restart 3. Login with GNOME Session Actual results: The Gnome Session fails to start with the "Something went wrong" splash and the "Log out" button Expected results: The session should start normally with some non-fatal warning about the timeout on the printer server connection. Additional info: The exact message on .xsession-errors is: (gnome-settings-daemon:3237): print-notifications-plugin-DEBUG: Connection to CUPS server 'printserver.some.doma.in' failed.
Hi, this can be fixed by backporting these commits from g-s-d-3.6: http://git.gnome.org/browse/gnome-settings-daemon/commit/?id=4dd2bc1f5ba76663710285d4d9c17172682af56e&h=gnome-3-6 http://git.gnome.org/browse/gnome-settings-daemon/commit/?id=5f1df8fc7767b9d5967bbbe988346f22995a6285&h=gnome-3-6 http://git.gnome.org/browse/gnome-settings-daemon/commit/?id=f2da010bb2423ff8d797306d7b0bdcd6f33c93f8&h=gnome-3-6 This bug is also present in Fedora 16. Bastien, can I prepare update for this for Fedora 16 and Fedora 17 and push it? Marek
This message is a reminder that Fedora 17 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 17. 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 '17'. 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 17'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 17 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 to Fedora 17's end of life. 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.
This bug is fixed in Fedora 18. So it can be closed as "Fixed". Thanks.
Fedora 17 changed to end-of-life (EOL) status on 2013-07-30. Fedora 17 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.