Gentoo Forums
Gentoo Forums
Gentoo Forums
Quick Search: in
[solved]Enlightenment cannot start Wayland session (elogind)
View unanswered posts
View posts from last 24 hours

 
Reply to topic    Gentoo Forums Forum Index Desktop Environments
View previous topic :: View next topic  
Author Message
gorg86
Apprentice
Apprentice


Joined: 20 May 2011
Posts: 150

PostPosted: Mon Jul 27, 2020 4:20 pm    Post subject: [solved]Enlightenment cannot start Wayland session (elogind) Reply with quote

Hello :)

emerge --info: https://pastebin.com/aHiPxX1W
emerge -pv --nodeps efl enlightenment: https://pastebin.com/np0Jnega
elogind & dbus both started up, consolekit is not installed.

https://bugs.gentoo.org/726762

I got the same error,
did someone find a workaround for this bug?
This guy claims he got it running without systemd or elogind, he uses consolekit: https://www.reddit.com/r/Gentoo/comments/8021h0/installing_enlightenment_desktop/
When I start Weston without xWayland support I am able to start Enlightenment (it's functional), but the screen gets all messed up.
- Is it possible to deactivate VSync with Wayland? For some reason I got input lags in certain situations in Weston and Wayfire + if there is some load (not 100%) on the CPU both Weston and Wayfire become unusable.
- I couldn't find a way to configure my 2-screen setup, I just want to clone screen 1 to screen 2.

This happens when I start it from tty
Code:
Enlightenment cannot initialize X Connection...
LOAD WL_WL MODULE
Could not create wayland canvas
LOAD WL_X11 MODULE
X11 connect failed!
LOAD WL_DRM MODULE
ERR<4530>:ecore_drm2 ../efl-1.24.3/src/lib/ecore_drm2/ecore_drm2_device.c:602 ecore_drm2_device_open() Could not connect to input manager
## Copy & Paste the below (until EOF) into a terminal, then hit Enter

eina_btlog << EOF
/usr/lib64/libeina.so.1    0x7f7a3210a052 0x7f7a320e0000
/usr/lib64/libeina.so.1    0x7f7a3210ae31 0x7f7a320e0000
/usr/lib64/libeina.so.1    0x7f7a3210c42f 0x7f7a320e0000
/usr/lib64/libecore_drm2.so.1    0x7f7a314ca612 0x7f7a314c0000
/usr/lib64/ecore_evas/engines/drm/v-1.24/module.so    0x7f7a2d914b5d 0x7f7a2d910000
/usr/lib64/libecore_evas.so.1    0x7f7a316c9b52 0x7f7a316b0000
/usr/lib64/libecore_evas.so.1    0x7f7a316c9d63 0x7f7a316b0000
/usr/lib64/enlightenment/modules/wl_drm/linux-gnu-x86_64-0.24.1/module.so    0x7f7a2d9255c2 0x7f7a2d920000
/usr/bin/enlightenment    0x556728139b44 0x55672802b000
/usr/bin/enlightenment    0x55672809fb3e 0x55672802b000
/usr/bin/enlightenment    0x5567280741b9 0x55672802b000
/lib64/libc.so.6    0x7f7a312abe0e 0x7f7a31288000
/usr/bin/enlightenment    0x55672807485a 0x55672802b000
EOF


startup in Weston without xWayland:
Code:
Enlightenment cannot initialize X Connection...
PRECACHE: [0.00522] [/usr/share/elementary/themes/default.edj] DONE
PRECACHE: TOTAL [0.00525]
PRECACHE: SUM=cffeb2eb, READS=3045
LOAD WL_WL MODULE
unable to lock lockfile /tmp/.runtime-chund/wayland-0.lock, maybe another compositor is running
ESTART: 0.18189 [0.12446] - Compositor Init Done


Thx


Last edited by gorg86 on Tue Aug 04, 2020 12:33 pm; edited 1 time in total
Back to top
View user's profile Send private message
Juippisi
Developer
Developer


Joined: 30 Sep 2005
Posts: 494
Location: /home

PostPosted: Tue Jul 28, 2020 8:20 am    Post subject: Reply with quote

It's starting to look more and more like it's not supported with elogind anymore. Last when I tested it, it worked with elogind. I don't use wayland on my main desktop pc (elogind), but I do use it on my laptop which has systemd so wayland does work.

For some reason it always looks like a dbus issue when trying with elogind. These threads might prove out to be useful,
https://forums.gentoo.org/viewtopic-t-1116288-highlight-dbus+pam.html
https://forums.gentoo.org/viewtopic-t-1116632-highlight-dbus+pam.html

And if not, I'm afraid the elogind-wayland combination is then broken by upstream. I'd need to test this on my own elogind system, but I really hate to break my desktop for testing.
Back to top
View user's profile Send private message
gorg86
Apprentice
Apprentice


Joined: 20 May 2011
Posts: 150

PostPosted: Wed Jul 29, 2020 4:18 pm    Post subject: Reply with quote

Hm, ok.
It didn't help :(
Also found this: https://www.mail-archive.com/enlightenment-devel@lists.sourceforge.net/msg105105.html
Is it possible to get more detailed output?
Back to top
View user's profile Send private message
gorg86
Apprentice
Apprentice


Joined: 20 May 2011
Posts: 150

PostPosted: Tue Aug 04, 2020 9:37 am    Post subject: Reply with quote

Stop your grinnin' and drop your linen, I found the bug with some help of the user raster on the #e IRC channel. I managed to start a Wayland session:
File elput_login.c -> _elput_sd_init
Code:
_libsystemd = eina_module_new("libelogind-shared.so.0");

I had to replace it with this after compiling efl from git:
Code:
_libsystemd = eina_module_new("/lib64/elogind/libelogind-shared-243.7.so");


eina_module_new just can't find the file and elogind doesn't connect because of it.
This should be an easy fix I guess?
Code:
export EFL_ELOGIND_LIB=/usr/pathtofile/libelogind-xxxxx

should also work, I didn't try it yet though.
Be careful though, only one display is supported. E crashed on my machine at first when 2 displays were connected and 1 of them was off, with just one display connected or both turned on when starting from tty it doesn't crash, you still get only one screen.

edit:
raster just did some changes in the repo concerning to this issue, maybe you guys should look at it first before making some patches.

edit 2 (commit):
https://git.enlightenment.org/core/efl.git/commit/?id=ee9836c5e78a9b52a5265e6ec4156a025fb6a1a6

edit 3:
Just for the sake of completeness if somebody reads this, I tested the updated git version and it works out of the box now in Gentoo. The commit is incompatible with with the the current ebuild though (efl-1.24.3), but I posted a solution to that at the bugtracker (link in first post). The dev Raster recommends always passing the systemd parameter (not the useflag) to meson for BOTH efl and enlightenment. It works for me if I just pass it to efl and not enlightenment, I don't know if that could result in weird behavior later on if you do not do it for both (systemd doesn't have to be installed but meson still expects the libsystemd.pc file in the version used in the current enlightenment ebuild, efl doesn't need it). libsystemd.pc is not needed for efl or e in the git version.

edit 4:
The efl-1.25.0-r1 ebuild works now :)
Back to top
View user's profile Send private message
Display posts from previous:   
Reply to topic    Gentoo Forums Forum Index Desktop Environments All times are GMT
Page 1 of 1

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum