Created attachment 364786 [details] emerge --info List of users in LightDM chooser contains bitcoin user. Despite that the issue is manifested in LightDM I suspect that it is not the one to blame. It might be something wrong with bitcoin user or accountservice. Either way that user should not be listed amongst standard users that can log-in to X session. $ emerge -pv lightdm accountsservice bitcoind ... [ebuild R ] sys-apps/accountsservice-0.6.34 USE="introspection -doc -systemd -vala" 0 kB [ebuild R ] net-p2p/bitcoind-0.8.5 USE="bash-completion ipv6 logrotate -examples -upnp" 0 kB [ebuild R ~] x11-misc/lightdm-1.8.5 USE="gtk introspection qt4 -kde (-razor)" 0 kB
(In reply to Robert Cernansky from comment #0) > Created attachment 364786 [details] > emerge --info > > List of users in LightDM chooser contains bitcoin user. Despite that the > issue is manifested in LightDM I suspect that it is not the one to blame. > It might be something wrong with bitcoin user or accountservice. Either way > that user should not be listed amongst standard users that can log-in to X > session. > > $ emerge -pv lightdm accountsservice bitcoind > ... > [ebuild R ] sys-apps/accountsservice-0.6.34 USE="introspection -doc > -systemd -vala" 0 kB > [ebuild R ] net-p2p/bitcoind-0.8.5 USE="bash-completion ipv6 logrotate > -examples -upnp" 0 kB > [ebuild R ~] x11-misc/lightdm-1.8.5 USE="gtk introspection qt4 -kde > (-razor)" 0 kB I don't see what in bitcoind is doing this. Why do you suspect lightdm is not to blame?
(In reply to Anthony Basile from comment #1) > Why do you suspect lightdm is not to blame? It is just my feeling. There are many system users on my machine but none of them is shown in LightDM, only bitcoin. It is unlikely that LightDM would pick a single system user of all those and show it alongside standard users. It seems more likely that bitcoin user is wrongly added by bitcoind ebuild in some way. I know nothing about accountservice. Only that the LightDM uses it to get users. So maybe something wrong might be there.
Hidden users in the LightDM chooser are defined in /etc/lightdm/users.conf. You need to add users you do not want to see in there. However, if the bitcoind user was created with a UID lower than 1000 then it would not show by default. This seems to be the more elegant solution because it will avoid lazy users who don't RTFM to file similar bugs in the future.
(In reply to Denis Dupeyron from comment #3) > Hidden users in the LightDM chooser are defined in /etc/lightdm/users.conf. > You need to add users you do not want to see in there. That of course I've done 2 years ago, but as you imply below it is not the right solution. > However, if the bitcoind user was created with a UID lower than 1000 then it > would not show by default. This seems to be the more elegant solution $ id bitcoin uid=115(bitcoin) gid=101(bitcoin) groups=101(bitcoin)
(In reply to Róbert Čerňanský from comment #4) > > However, if the bitcoind user was created with a UID lower than 1000 then it > > would not show by default. This seems to be the more elegant solution > > $ id bitcoin > > uid=115(bitcoin) gid=101(bitcoin) groups=101(bitcoin) Sounds like a bug somewhere else. How do I pass this bug back to triage?
[00:50:37] <DarthGandalf> if you switched bitcoin to acct-user/* already, just mark as obsolete
