search

Obsidian-StudiosInc / entrance

General purpose Display Manager built on the Enlightenment Foundation Libraries (EFL)
GNU General Public License v3.0
23 stars 10 forks source link

pulseaudio stops working after re-login. #47

Open triantares opened 4 years ago

triantares commented 4 years ago

Description

When logging out from a DE and logging in again, pulseaudio fails to restart. On restarting "entrance" with "killall -HUP entrance" pulseaudio functions as it should.

This is on Elive 3.8.11 amd64 (Buster based) running either E16 or E23.

subscribers: @Thanatermesis

wltjr commented 4 years ago

Hi, thanks for the report. I can confirm that upon logout, pulseaudio is still running. I will have to look into that issue.

TheTechRobo commented 3 years ago

I have the similar issue. I left my Elive Beta with E24 manually installed box on for a while, normally after that long a time I have a guru meditation, instead I got kicked back to entrance (E24 probably crashed without handling the exception) and I relogged in. I have no audio, PulseAudio volume control is stuck on "establishing connection to PulseAudio". I have not tried restarting entrance yet. (VOlume control in E24 not functioning either)

Bit annoying that Enlightenment crashed because I don't know if I had unsaved stuff or not in Audacity (confirmed: I didnt), but not an Entrance fault.

UPDATE: Audio now works after restarting entrance. Here is a pastebin of the log AFTER I killed entrance and re logged in - i forgot to take one before. https://thetechrobo.github.io/entrance.fullLog (its extension is fullLog because I had two copied into my home)

UPDATE 2: Im starting to think it's because Enlightenment crashed and so pulseaudio didn't get shut down correctly.

TheTechRobo commented 3 years ago

Nope, it's not because Enlightenment crashed - it's because of me just relogging in. Very strange.

Thanatermesis commented 3 years ago

Maybe entrance just booted too early and some "systemd" services needed to be loaded previously?

You can try to delay the boot of entrance like in the "timer" answer of this thread: https://unix.stackexchange.com/questions/397853/how-to-set-a-systemd-unit-to-start-after-loading-the-desktop or play with systemd configurations in some ways to verify if this is the issue (reload systemd configurations are needed to take effect)

wltjr commented 3 years ago

No, I am pretty sure there is some disconnect between the session and pulse audio, similar to issue #45. I believe, I need to register the session with logind/elogind. I think that is what is affecting both pulse audio and system actions in the other issue.