Version-Release number of selected component: vino-3.15.90-1.fc22 Additional info: reporter: libreport-2.3.0 backtrace_rating: 4 cmdline: /usr/libexec/vino-server crash_function: _g_log_abort executable: /usr/libexec/vino-server kernel: 3.20.0-0.rc0.git6.1.fc22.x86_64 runlevel: N 5 type: CCpp uid: 8086 Truncated backtrace: Thread no. 1 (1 frames) #0 _g_log_abort at gmessages.c:315
Created attachment 993471 [details] File: backtrace
Created attachment 993472 [details] File: cgroup
Created attachment 993473 [details] File: core_backtrace
Created attachment 993474 [details] File: dso_list
Created attachment 993475 [details] File: environ
Created attachment 993476 [details] File: limits
Created attachment 993477 [details] File: maps
Created attachment 993478 [details] File: open_fds
Created attachment 993479 [details] File: proc_pid_status
Created attachment 993480 [details] File: var_log_messages
This is a crash (rather than just a warning) because G_DEBUG=fatal-warnings is in your environment, which is pretty questionable.
vino-3.15.90-2.fc22 has been submitted as an update for Fedora 22. https://admin.fedoraproject.org/updates/vino-3.15.90-2.fc22
Package vino-3.15.90-2.fc22: * should fix your issue, * was pushed to the Fedora 22 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing vino-3.15.90-2.fc22' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2015-2557/vino-3.15.90-2.fc22 then log in and leave karma (feedback).
vino-3.15.90-2.fc22 has been pushed to the Fedora 22 stable repository. If problems still persist, please make note of it in this bug report.