Created attachment 1045259 [details] startx file I have over 60+ .serverauth.XXXX files in my home folder, as far I know, startx should remove those files. this is my bashrc script to login [[ -z $DISPLAY && $XDG_VTNR -eq 1 ]] && exec /usr/bin/startx and .xinitrc exec cinnamon-session
Hi, I just checked and the startx script has this: trap "rm -f '$xserverauthfile'" HUP INT QUIT ILL TRAP KILL BUS TERM And after running xinit it does: if [ x"$xserverauthfile" != x ]; then rm -f "$xserverauthfile" fi So it should always cleanup after itself, and I've just run "startx" and then exited my desktop normally and it did indeed cleanup after itself. The only scenario where it will leave a .serverauth around is when you kill -9 it, and there is nothing we can do about this. Regards, Hans
I installed Openbox along with Cinnamon and it leaks those serverauth files only with Cinnamon.
Use simply lightdm as DesktopManager. We do not support your way of using cinnamon.
Well fortunately this is not a Cinnamon bug. .serverauth.$$ files are leaked in almost every DE/WM after poweroff. Files will be cleaned if restarting X or login out.
Hi, (In reply to Duff Padmasana from comment #4) > Well fortunately this is not a Cinnamon bug. > > .serverauth.$$ files are leaked in almost every DE/WM after poweroff. > Files will be cleaned if restarting X or login out. Hmm, yes I can reproduce the problem with poweroff, I do not unserstand why though, startx has: trap "rm -f '$xserverauthfile'" HUP INT QUIT ILL TRAP KILL BUS TERM So if we do a poweroff with the session running, then I expect the startx process to see a HUP as its tty get closed. Why did you make this a dracut bug now? I do not see how this related to dracut ? It is likely related to how systemd closes / kills vt-logins when doing a poweroff. Regards, Hans
maybe related: bug 1170765
Hi, (In reply to Harald Hoyer from comment #6) > maybe related: bug 1170765 Yep, sending SIGKILL without first sending SIGTERM and or SIGHUP is pretty rude to do, and definitely sounds like the root cause of this bug, marking this one a dup. Regards, Hans *** This bug has been marked as a duplicate of bug 1170765 ***