Description of problem: Started dolphin-emu, it just crashes immediately. Version-Release number of selected component: dolphin-emu-5.0-7.fc25 Additional info: reporter: libreport-2.8.0 backtrace_rating: 4 cmdline: dolphin-emu crash_function: pthread_cond_wait@@GLIBC_2.3.2 executable: /usr/bin/dolphin-emu global_pid: 26206 kernel: 4.8.13-300.fc25.x86_64 pkg_fingerprint: 4089 D8F2 FDB1 9C98 pkg_vendor: Fedora Project runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 8 (3 frames) #0 pthread_cond_wait@@GLIBC_2.3.2 at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 __gthread_cond_wait at /usr/src/debug/gcc-6.2.1-20160916/obj-x86_64-redhat-linux/x86_64-redhat-linux/libstdc++-v3/include/x86_64-redhat-linux/bits/gthr-default.h:864 #2 std::condition_variable::wait at ../../../../../libstdc++-v3/src/c++11/condition_variable.cc:53
Created attachment 1235180 [details] File: backtrace
Created attachment 1235181 [details] File: cgroup
Created attachment 1235182 [details] File: core_backtrace
Created attachment 1235183 [details] File: dso_list
Created attachment 1235184 [details] File: environ
Created attachment 1235185 [details] File: limits
Created attachment 1235186 [details] File: maps
Created attachment 1235187 [details] File: mountinfo
Created attachment 1235188 [details] File: namespaces
Created attachment 1235189 [details] File: open_fds
Created attachment 1235190 [details] File: proc_pid_status
Created attachment 1235191 [details] File: var_log_messages
Workaround is to set GDK_BACKEND=x11 environment variable when running dolphin-emu. It looks like when it tries to run under Wayland it still tries to use XRandR operations, which blows up.
Noted, I will look into this, or add this workaround. Thanks!
It seems like the x11 stuff is compile time rather than runtime, so I'll have to just work around the issue by forcing x11 for now. Stay tuned, I'll push an update.
dolphin-emu-5.0-9.fc25 has been submitted as an update to Fedora 25. https://bodhi.fedoraproject.org/updates/FEDORA-2017-589fd56903
dolphin-emu-5.0-9.fc24 has been submitted as an update to Fedora 24. https://bodhi.fedoraproject.org/updates/FEDORA-2017-5f0d90c57b
dolphin-emu-5.0-9 includes this work around. I'll keep this bug open until I can get a better solution working. Since the X stuff is built in at compile time, either a patch is needed to detect at run time if the application is in X, or possibly it can be built to be more protocol agnostic.
dolphin-emu-5.0-10.fc25 has been submitted as an update to Fedora 25. https://bodhi.fedoraproject.org/updates/FEDORA-2017-e5ac3b7343
dolphin-emu-5.0-10.fc24 has been submitted as an update to Fedora 24. https://bodhi.fedoraproject.org/updates/FEDORA-2017-04d527e226
Turns out dolphin dropped Wayland support in 5.0. It maybe re-added in new releases but I would rather not maintain a large patch-set if upstream does not wish to take it. I've added a cleaner solution to force XWayland with dolphin-emu-5.0-10, which should be good enough for now. Please let me know if it works for you. I've also turned on LTO for some extra performance.
dolphin-emu-5.0-10.fc24 has been pushed to the Fedora 24 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2017-04d527e226
dolphin-emu-5.0-10.fc25 has been pushed to the Fedora 25 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2017-e5ac3b7343
dolphin-emu-5.0-10.fc24 has been pushed to the Fedora 24 stable repository. If problems still persist, please make note of it in this bug report.
dolphin-emu-5.0-10.fc25 has been pushed to the Fedora 25 stable repository. If problems still persist, please make note of it in this bug report.