Description of problem: I just tried to login and it crashed and sent me back to lightdm. Version-Release number of selected component: gnome-session-3.13.3-2.fc21 Additional info: reporter: libreport-2.2.3 backtrace_rating: 4 cmdline: gnome-session crash_function: g_settings_schema_get_value executable: /usr/bin/gnome-session kernel: 3.16.2-300.fc21.x86_64 runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #2 g_settings_schema_get_value at gsettingsschema.c:951 #3 g_settings_schema_key_init at gsettingsschema.c:1148 #4 g_settings_get_value at gsettings.c:1091 #5 g_settings_get_boolean at gsettings.c:1904 #6 setup_gsettings_condition_monitor at gsm-autostart-app.c:362 #7 setup_condition_monitor at gsm-autostart-app.c:550 #8 load_desktop_file at gsm-autostart-app.c:661 #9 gsm_autostart_app_initable_init at gsm-autostart-app.c:1374 #10 g_initable_new_valist at ginitable.c:228 #11 g_initable_new at ginitable.c:146
Created attachment 935661 [details] File: backtrace
Created attachment 935662 [details] File: cgroup
Created attachment 935663 [details] File: core_backtrace
Created attachment 935664 [details] File: dso_list
Created attachment 935665 [details] File: environ
Created attachment 935666 [details] File: limits
Created attachment 935667 [details] File: maps
Created attachment 935668 [details] File: open_fds
Created attachment 935669 [details] File: proc_pid_status
Created attachment 935670 [details] File: var_log_messages
From the attached backtrace in comment 1, I saw that thread 1 was trying to load /home/jmbastia/.config/autostart/vino-server.desktop. I moved that file out of the autostart directory and now Gnome starts. How could this autostart file cause a crash?
Created attachment 938868 [details] vino-server.desktop autostart file The problematic autostart vino-server.desktop file
I see the vino-server.desktop file has a line: AutostartCondition=GSettings org.gnome.Vino enabled And the backtrace shows it was trying to read this value when it crashed: g_settings_schema_get_value It probably crashed because it does not exist: [jmbastia@firefly ~]$ gsettings get org.gnome.Vino enabled No such key 'enabled' [jmbastia@firefly ~]$ gsettings list-recursively org.gnome.Vino org.gnome.Vino notify-on-connect true org.gnome.Vino alternative-port uint16 5900 org.gnome.Vino disable-background false org.gnome.Vino use-alternative-port false org.gnome.Vino icon-visibility 'client' org.gnome.Vino use-upnp false org.gnome.Vino view-only false org.gnome.Vino prompt-enabled true org.gnome.Vino disable-xdamage false org.gnome.Vino authentication-methods ['none'] org.gnome.Vino network-interface '' org.gnome.Vino require-encryption true org.gnome.Vino mailto '' org.gnome.Vino lock-screen-on-disconnect false org.gnome.Vino vnc-password 'keyring'
the key was removed in https://git.gnome.org/browse/vino/commit/?id=18be3c5546172bce551b65d60ec2c931bc451398 together with the autostart file. Maybe gnome-session should be robust against autostart conditions referring to non-existing keys.
This message is a reminder that Fedora 21 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 21. 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 '21'. 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 21 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 21 changed to end-of-life (EOL) status on 2015-12-01. Fedora 21 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.