After few login/logouts you can notice that amount of running pam-panel-icon and pam-timestamps processes, grows up.These comes from the usermode package.Anyways this can be noticed only under xfce. Sometimes there is a start race condition between stuff from /autostart and from saved last session. Simple fix would be to blacklist for session saving apps that are cast from /autostart.
Created attachment 2126 Running session
[tpg@localhost ~]$ ps aux | grep "pam-panel-icon" | wc -l 14 [tpg@localhost ~]$ uptime 01:18:28 up 10:14, 4 users, load average: 1.45, 1.12, 1.20 [tpg@localhost ~]$ ps aux | grep "pam_timestamp_check" | wc -l 14
Uh, if you have something saved in the session and in autostart, it's gonna get started more than once. That's just how it is. Pick one method of starting it, not both.
as per last comment of brian, issue does not exist.
Wait a minute... issue DOES exist! For example: i created new user, log in and i set "Restart Style" for pam-panel-icon to never, didn't hit the button save session nor auto save session checkbox is ticked, and after a logout/login, "Restart Style" is set back to "if running". If i log in and log out few times, let's say 2 or 3 i got two pam-panel-icon prcesses. This does NOT occurs under KDE/GNOME.
(In reply to comment #5) > Wait a minute... issue DOES exist! Maybe, maybe not. > created new user, log in and i set "Restart Style" for > pam-panel-icon to never, didn't hit the button save session nor auto save > session checkbox is ticked, and after a logout/login, "Restart Style" is set > back to "if running". Yeah, that's normal. When an app connects to the session manager, it's free to set its restart style to whatever it wants. Nothing I can do about that. > This does NOT occurs under KDE/GNOME. Well, then please provide a patch to fix this. I don't care enough to install Mandriva to figure this out.
Reassign to xfce-bugs@xfce.org.
-- GitLab Migration Automatic Message -- This bug has been migrated to xfce.org's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.xfce.org/xfce/xfce4-session/-/issues/2. Please create an account or use an existing account on one of our supported OAuth providers. If you want to fork to submit patches and merge requests please continue reading here: https://docs.xfce.org/contribute/dev/git/start#gitlab_forks_and_merge_requests Also feel free to reach out to us on the mailing list https://mail.xfce.org/mailman/listinfo/xfce4-dev