Description of problem: Any time I try to start evince. I use XFCE. Version-Release number of selected component: evince-3.10.3-1.fc20 Additional info: reporter: libreport-2.1.11 backtrace_rating: 4 cmdline: evince 'Red Hat_mutual_nondisclosure_agreement_2013-1.pdf' crash_function: g_settings_set_property executable: /usr/bin/evince kernel: 3.12.7-300.fc20.x86_64 runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #2 g_settings_set_property at gsettings.c:492 #3 object_set_property at gobject.c:1366 #4 g_object_new_internal at gobject.c:1779 #5 g_object_new_valist at gobject.c:2002 #7 g_settings_new at gsettings.c:864 #8 ev_window_ensure_settings at ev-window.c:1443 #9 ev_window_init at ev-window.c:7555 #10 g_type_create_instance at gtype.c:1868 #11 g_object_new_internal at gobject.c:1746 #12 g_object_new_valist at gobject.c:2002
Created attachment 851542 [details] File: backtrace
Created attachment 851543 [details] File: cgroup
Created attachment 851544 [details] File: core_backtrace
Created attachment 851545 [details] File: dso_list
Created attachment 851546 [details] File: environ
Created attachment 851547 [details] File: limits
Created attachment 851548 [details] File: maps
Created attachment 851549 [details] File: open_fds
Created attachment 851550 [details] File: proc_pid_status
Created attachment 851551 [details] File: var_log_messages
Running the following command as root resolved the problem: glib-compile-schemas /usr/share/glib-2.0/schemas/
Another user experienced a similar problem: Launching evince results in this strange error; (evince:30825): GLib-GIO-ERROR **: No GSettings schemas are installed on the system reporter: libreport-2.2.0 backtrace_rating: 4 cmdline: evince crash_function: g_settings_set_property executable: /usr/bin/evince kernel: 3.13.6-200.fc20.x86_64 package: evince-3.10.3-1.fc20 reason: evince killed by SIGTRAP runlevel: N 5 type: CCpp uid: 0
(In reply to Peter Czanik from comment #11) > Running the following command as root resolved the problem: > > glib-compile-schemas /usr/share/glib-2.0/schemas/ Tried this fix -- didn't work. Same error message. Regards Pascal
Found the issue. I recently merged a .profile from a machine where I was using some kind of "Linux From Scratch" approach, with XDG_DATA_DIRS=$HOME/usr/share Setting it to XDG_DATA_DIRS=$HOME/usr/share:/usr/share solved the problem. This seems to indicate that evince should have some kind of fallback mechanism in case it does not find its schema. Regards Pascal
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.