Description of problem: What I did: 1. as myself I ran empathy (with link-local account on) 2. lock screen 3. log in as xguest (frokm xguest package) 4. set up link-local xmpp for xguest 5. send message from xguest to the first user Version-Release number of selected component: telepathy-salut-0.8.1-2.fc19 Additional info: reporter: libreport-2.1.5 backtrace_rating: 4 cmdline: /usr/libexec/telepathy-salut crash_function: dconf_shm_open executable: /usr/libexec/telepathy-salut kernel: 3.9.6-301.fc19.x86_64 runlevel: N 5 uid: 1001 Truncated backtrace: Thread no. 1 (10 frames) #2 dconf_shm_open at dconf-shm.c:63 #3 dconf_engine_source_user_reopen at dconf-engine-source-user.c:76 #4 dconf_engine_source_refresh at dconf-engine-source.c:57 #5 dconf_engine_acquire_sources at dconf-engine.c:201 #6 dconf_engine_get_state at dconf-engine.c:311 #7 dconf_engine_watch_fast at dconf-engine.c:762 #9 g_object_new_valist at gobject.c:1836 #11 g_settings_new at gsettings.c:869 #12 g_proxy_resolver_gnome_init at gproxyresolvergnome.c:157 #13 g_type_create_instance at gtype.c:1917
Created attachment 764727 [details] File: backtrace
Created attachment 764728 [details] File: cgroup
Created attachment 764729 [details] File: core_backtrace
Created attachment 764730 [details] File: dso_list
Created attachment 764731 [details] File: environ
Created attachment 764732 [details] File: limits
Created attachment 764733 [details] File: maps
Created attachment 764734 [details] File: open_fds
Created attachment 764735 [details] File: proc_pid_status
Created attachment 764736 [details] File: var_log_messages
nothing, except connecting and disconnecting, the network where I am is quite flaky, so I may have changed ip. reporter: libreport-2.1.5 backtrace_rating: 4 cmdline: /usr/libexec/telepathy-salut crash_function: dconf_shm_open executable: /usr/libexec/telepathy-salut kernel: 3.9.9-301.fc19.x86_64 package: telepathy-salut-0.8.1-2.fc19 reason: Process /usr/libexec/telepathy-salut was killed by signal 5 (SIGTRAP) runlevel: N 5 uid: 500
This message is a notice that Fedora 19 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 19. It is Fedora's policy to close all bug reports from releases that are no longer maintained. Approximately 4 (four) weeks from now this bug will be closed as EOL if it remains open with a Fedora 'version' of '19'. 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 19 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 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 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.