I have fresh installed archlinux with xfce session and lxdm as display manager. Archlinux is installed on an external ssd conected to my profossional laptop which have an internal drive with two ntfs partition. This laptop is multi-user used.
My problems started when I've tried to mount the ntfs partition from thunar, I was receiving this message :
Failed to mount << Volume 163GB >> Not authorized to perform operation.
So I have installed gnome-polkit and on the first attemp I was thinking that evreything was working well. I received an window with the prompt to enter my password and the partition was well mount.
The problem is that if I open a second xfce session with a second user, if this user try to mount the partition from no thunar there's no window... and if I come back to the first opened session, the prompt window is there, waiting for the password!
What is very strange, even if there is more than one xfce session opened, the commande loginctl return only one session (example from the accont "stephanie" with xfce session opened after "sebastien"):
[stephanie@Vulpus ~]$ loginctl SESSION UID USER SEAT 1 1000 sebastien seat0 1 sessions listed. [stephanie@Vulpus ~]$
same thing as root :
[root@Vulpus stephanie]# loginctl SESSION UID USER SEAT 1 1000 sebastien seat0 1 sessions listed. [root@Vulpus stephanie]#
By the way, if I open some sessions in a standard consoles I'm able to see these sessions :
[root@Vulpus sebastien]# exit exit [sebastien@Vulpus ~]$ loginctl SESSION UID USER SEAT 1 1001 stephanie seat0 2 1000 sebastien seat0 3 1001 stephanie seat0 3 sessions listed. [sebastien@Vulpus ~]$
So here is my question, how can i launch properly the xfce session from logind point of view?
Last edited by lesebas (2013-08-01 11:31:20)
Hello I've tried lightm... loginctl works fine, it seems the problem comes from lxdm. Does anyone can confirm the bug?
Last edited by lesebas (2013-08-13 21:03:04)
This issue has been around here for some time... after all, editing the pam file does not seem to solve it completely.
Hello the bug is confirmed :
But it seams there's no simple solution by now. I've reported it to upstream :
Wait and see
Bug fixed in the last version, you can try the git...
Last edited by lesebas (2013-09-12 21:16:31)