You are not logged in.
Good Morning Everyone,
following the most recent upgrade to GNOME 3.38, I thought that I should once more revisit the topic of running Wayland instead of X11. My current config looks as follows:
AMD Ryzen 7 1700 CPU
nVidia 1080 GTX GPU (nvidia-drm.modeset=1)
Kernel 5.9.1 and GNOME 3.38.1
gdm
I can start the GNOME session without any issues, and most applications (Firefox, Chrome, Terminal, Filezilla, Nautilus, Darktable, GIMP, ...) work as normal. Only Evolution refuses to start. Running it from the command line, I get
(evolution-alarm-notify:1645): GLib-GIO-WARNING **: 07:37:55.605: Your application did not unregister from D-Bus before destruction. Consider using g_application_run().
evolution: ../egl-wayland/src/wayland-thread.c:87: wlExternalApiLock: Assertion »!"failed to lock pthread mutex"« not fulfilled.
(The message about evolution-alarm-notify will also show when running under X11, but it doesn't prevent Evolution from opening.)
Has anybody experienced the same? I am really wondering why only Evolution has issues, while all other applications I tested work fine, so if you have any input, please post.
Cheers,
Smoerrebroed
Last edited by Smoerrebroed (2020-10-27 09:00:31)
Offline
Check if there's another evolution process running in the background, if it's there, kill it and start running it again..
https://gitlab.gnome.org/GNOME/glib/-/issues/1857 might interest you as well.
Offline
As stated, the warning from evolution-alarm-notify will always come up, so I daresay it doesn't have anything to do with Evolution not starting under Wayland. This also happens right after starting my GNOME session, so I presume that there are no other instances of Evolution running (which I confirmed using ps). Any other ideas?
Offline
run Evolution from a terminal with strace and filter out your personal/private settings before paste output in pastebin.com.
# pacman -S strace
$ strace evolution 2>tracelog &
Last edited by solskog (2020-10-21 07:38:59)
Offline
Phew, this resulted in 2.3 MB worth of logs ... Here are roughly the last 200 K. If you need more, please let me know.
TIA!
Smoerrebroed
Offline
openat(AT_FDCWD, "/usr/lib/libnvidia-egl-wayland.so.1", O_RDONLY|O_CLOEXEC) = 42
...
write(2, "evolution: ../egl-wayland/src/wa"..., 134evolution: ../egl-wayland/src/wayland-thread.c:87: wlExternalApiLock: Zusicherung »!"failed to lock pthread mutex"« nicht erfüllt.) = 134
Pls set LANG=en_US.UTF-8 next time.
$ LANG=en_US.UTF-8 strace COMMAND
This maybe related to this issue
https://github.com.cnpmjs.org/NVIDIA/eg … /issues/27
There is a patch to fix this issue at Aug 14, 2020, but not included in arch extra/egl-wayland 1.1.5-1 yet. You can compile it from upstream source. And if this patch actually solve your problem, Someone could ask archlinux package maintainer to update egl-wayland package.
https://github.com/NVIDIA/egl-wayland.
I have tested on Nvidia with nouveau driver, Evolution started without any issue, but open source driver use a different source tree.
If you can provide some coredump info that would be useful
man coredumpctl
# coredumpctl info evolution
Last edited by solskog (2020-10-22 23:51:45)
Offline
Bingo! I just rebuilt egl-wayland 1.1.5 including the patch, and after installation I can now start Evolution under Wayland as well. Great stuff! Thanks a lot for your help. I'll try to inform the package maintainer.
Do you still need a coredump? (I guess not.)
Cheers,
Smoerrebroed
Offline
I didn't receive a response to my email, but the package has been updated to include the latest patch now. Works!
Offline