After logout or restart: Albert has not been quit graciously!

[wechsler42]

Environent

Operating system: Lubuntu 16.04 LTS
Desktop environment: standard Lubuntu DE
Albert version: 0.8.9
Source: ppa:nilarimogard/webupd8

Steps to reproduce

1. Install Albert
2. Configure it
3. Logout of the Lubuntu session via Logout button in the Lubuntu Menu
4. Login again
5. Start Albert
6. Alert box appears: Albert has not been quit graciously! This means your settings and data have not been saved. If you did not kill albert yourself, albert most likely crashed. Please report this on github. Do you want to ignore this warnings in future?

Expected behaviour

Albert behaves like it does when I kill the process in the terminal. Moreover changes in the Albert settings are saved.

Actual behaviour

The alert box appaers and changes in the Albert settings are not saved.

[ManuelSchneid3r]

Are you sure you used the logout button when this happened? This might hint that the application really crashed. Is /var/crash empty?

If yes, try to find out how lxde terminates it applications. Linux distributions and desktop sessions are one of the most annoying things I had to handle since I develop albert. Most of them kill applications by SIGKILL, when you dont use the session process to terminate itself. SIGKILL does not allow to react on the termination of the process. This is ridiculous. Think of resource management. Try to find out the graceful way to stop the lxde session and please report it, for use in the system extension. For gnome e.g. this is gnome-session-quit.

[wechsler42]

Thanks for the quick reply.
Regarding your questions:

1. In order to log out of the Lubuntu/LXDE session, I used the default menu based way:
   click on the "Start" menu, click "Logout" and when the menu pops up click on "logout" again.
2. yes /var/crash is empty.
3. Perhaps there is some info here towards session logout in LXDE: https://github.com/lxde/lxsession (see Readme). A perhaps similar question "LXDE: gracefully logout instead of killing all running applications" was discussed here: http://askubuntu.com/questions/397606/lxde-gracefully-logout-instead-of-killing-all-running-applications and here http://unix.stackexchange.com/questions/170029/command-to-log-out-of-lxde-directly

I hope this helps to track down the issue.

[13k]

I can also confirm this happening. Restarting on Ubuntu/Unity also makes albert complain about this and it doesn't save any changed settings.

It doesn't seem to be crashing. Contents of my /var/crash:

$ grep '^ExecutablePath' /var/crash/*
/var/crash/_usr_bin_glances.1000.crash:ExecutablePath: /usr/bin/glances
/var/crash/_usr_bin_vim.gtk3.1000.crash:ExecutablePath: /usr/bin/vim.gtk3

[13k]

Ok, nevermind, I tested with gnome-session-quit and it worked. Then I tried to change settings / directly reboot (Menu / Shutdown / Restart) and it also worked. I couldn't reproduce this again.

I don't know if this has any influence, but one thing that I did differently between reboots was to add Albert to Startup Applications ($HOME/.config/autostart/albert.desktop). I'm not sure if gnome session is aware of this and gracefully stops these apps instead of killing them but other apps it kills them instantly.

[ManuelSchneid3r]

@wechsler42 Could you please check, if albert is a childprocess of the lxsession?

[wechsler42]

Yes, it seems to me that albert is a child process of the lxsession:
PID lxsession is 969:
~$ pstree -p 969 | grep "albert"
lxsession(969)-+-lxpanel(1081)-+-albert(3134)---{QXcbEventReader}(3135)

[LordGaav]

I can also confirm this happens under Ubuntu 14.04 and Unity. I'm seeing this behaviour when suspending the laptop. After resuming, the process is gone and after restarting Albert I get the same "has not quit graciously" message. Shutting down Ubuntu normally does not cause this issue.

[ManuelSchneid3r]

I opened a collective issue #197 for termination / serialization problems on unix. If you want to track it make sure you watch it. Please continue any discussion related to this problem in #197.