Skip to content
This repository has been archived by the owner on Jul 1, 2024. It is now read-only.

[efl-1.22.2] Broken entrance_client UI connection issues with server, no menus, actions, etc #34

Open
wltjr opened this issue Nov 30, 2018 · 2 comments
Assignees
Labels

Comments

@wltjr
Copy link
Member

wltjr commented Nov 30, 2018

Description

When entrance starts there is no background/theme, sessions, or system actions. That usually is a sign of the client failing to connect to the server. Log output makes it seem like the client is connected, and the missing data is sent from server to client.

This is a bit suspicious in the log

ERR<19052>:ecore lib/ecore/ecore_main.c:1346 _ecore_main_fd_handler_add() Failed to add poll on fd 19 (errno = 9: Bad file descriptor)!
## Copy & Paste the below (until EOF) into a terminal, then hit Enter

If you use auto-login and then log out. The UI starts normally without this issue.

This does not occur if you start entrance under xephyr, only during normal usage.

Steps to reproduce

  1. Start entrance normally as the system login/display manager via init script or direct invocation.

System information

  • EFL 1.21.1
@wltjr wltjr added the bug label Nov 30, 2018
@wltjr wltjr self-assigned this Nov 30, 2018
@wltjr
Copy link
Member Author

wltjr commented Jun 12, 2019

Same in EFL 1.22.2, the client is failing to connect to the server and get the necessary data to populate the UI.

@wltjr wltjr pinned this issue Jun 12, 2019
@wltjr wltjr changed the title [efl-1.21.1] Broken entrance_client UI connection issues with server, no menus, actions, etc [efl-1.22.2] Broken entrance_client UI connection issues with server, no menus, actions, etc Jun 12, 2019
This was referenced Feb 2, 2020
@wltjr
Copy link
Member Author

wltjr commented Sep 26, 2023

FINALLY!!! After 5 years, this is an issue caused by daemonization... passing the -n/-nodaemon argument and just letting like start-stop-daemon do its job, gets entrance running again :) Tell your friends and enemies! Thanks much to @rastermann for taking me down the wormhole that uncovered this trivial solution.

I will be removing the daemonization code ASAP once I get a dev env and some other stuff going again.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

1 participant