search

oxen-io / session-desktop

Session Desktop - Onion routing based messenger
https://getsession.org
GNU General Public License v3.0
1.44k stars 186 forks source link

[BUG] session freaks out xorg dwm app package (low priority) #3112

Open iceyrazor opened 1 month ago

iceyrazor commented 1 month ago

Code of conduct

Self-training on how to write a bug report

Is there an existing issue for this?

Current Behavior

fix below low priority

when i start session on my setup. it works fine. however when i start it through terminal and & disown it and close the terminal. it freezes my whole setup and spawns a ton of empty windows.

this cant just be a electron thing as i use discord and it works fine.

this stops if i instead do session-deskop-linux-x86_64-1.12.3.AppImage > /dev/null & disown or any file

Expected Behavior

for the session app image to be able to be opened and disowed and the terminal closing without infinate windows spawning and my pc freezing.

Steps To Reproduce

use dwm and its requirements along with xorg. use the app package. run session-deskop-linux-x86_64-1.12.3.AppImage & disown

Desktop Version

v1.12.3

Anything else?

Linux 6.9.1-arch1-2

if this allready was an issue i couldnt find it

https://github.com/oxen-io/session-desktop/assets/25697194/2c3a4c65-b3c5-408e-8c81-f5f1705e469b

AL-Session commented 21 hours ago

I've been able to replicate a functionally similar issue on the latest Arch (kernel 6.9.7-Arch-1, bash 5.2.026-2) but using gdm on X11 rather than dwm. If I launch session from a terminal via ./session-desktop-linux-x86_64-1.12.4.AppImage & disown and then close the terminal the window manager locks up and I'm forced to reboot.

However, if I launch via the following: nohup ./session-desktop-linux-x86_64-1.12.4.AppImage & then I'm able to close the terminal and session-desktop remains active and responsive, and there are no window manager issues.

Could you give that a try and see how you get on?

As this is more of a workaround than a fix (assuming that it works for you!), do you know if the disown method worked previously but has recently stopped working perhaps?

iceyrazor commented 21 hours ago

I've been able to replicate a functionally similar issue on the latest Arch (kernel 6.9.7-Arch-1, bash 5.2.026-2) but using gdm on X11 rather than dwm. If I launch session from a terminal via ./session-desktop-linux-x86_64-1.12.4.AppImage & disown and then close the terminal the window manager locks up and I'm forced to reboot.

However, if I launch via the following: nohup ./session-desktop-linux-x86_64-1.12.4.AppImage & then I'm able to close the terminal and session-desktop remains active and responsive, and there are no window manager issues.

Could you give that a try and see how you get on?

As this is more of a workaround than a fix (assuming that it works for you!), do you know if the disown method worked previously but has recently stopped working perhaps?

i only just started using session on linux so i dont think so.

no the workaround you listed nohup ./session-desktop-linux-x86_64-1.12.4.AppImage & still closes session when i close the terminal that started it,

the workaround session-deskop-linux-x86_64-1.12.3.AppImage > /dev/null & disown works fine for me.

Bilb commented 20 hours ago

Hey @iceyrazor this could be an AppImage issue rather than a session issue, as seen here https://stackoverflow.com/questions/66573324/unable-to-properly-disown-appimage

Can you try what that guy suggests and let me know if that also fixes your issue? i.e. setsid -f <session AppImage path>

Just trying to know what works so we can maybe find a proper fix.

iceyrazor commented 19 hours ago

Hey @iceyrazor this could be an AppImage issue rather than a session issue, as seen here https://stackoverflow.com/questions/66573324/unable-to-properly-disown-appimage

Can you try what that guy suggests and let me know if that also fixes your issue? i.e. setsid -f <session AppImage path>

Just trying to know what works so we can maybe find a proper fix.

no such command setsid.

AL-Session commented 19 hours ago

no such command setsid.

You'll need to install util-linux:

pacman -Qo setsid
/usr/bin/setsid is owned by util-linux 2.40.1-1
iceyrazor commented 19 hours ago

no such command setsid.

You'll need to install util-linux:

pacman -Qo setsid
/usr/bin/setsid is owned by util-linux 2.40.1-1

fin i was running a mc server >:( lol.

no it still did the same thing that happened in the video. this app image is 1.12.4.

i was able to kill it off in a seperate tty. dwm crashed though. and lightdm kicked in and restarted it.