You are not logged in.
Pages: 1
Hello.
Well, I have two problems with lightdm.
The first is, that since the latest update lightdm starts X at tty1 instead of tty7.
The second is that all kind of users are listed at the login screen despite the contents of my /etc/lightdm/users.conf file. They are not above the defined uid 1000, I've listed them by their names too. Lightdm does not give one.
Anyone else experiencing this?
Last edited by scar (2013-09-11 07:25:43)
“The future has already arrived. It's just not evenly distributed yet.”
― William Gibson
Offline
See https://projects.archlinux.org/svntogit … a3469f0815 , https://projects.archlinux.org/svntogit … 86dcccb7c2 and other changes.
Which version exactly are you running?
I think this patch https://projects.archlinux.org/svntogit … a3469f0815 is responsible for starting X on vt1.
Offline
I flagged lightdm as out of date this morning as the current version is 1.7.13. It got reset - I don't know how/why?
However, the user bug you refer to is still outstanding. I fixed it by changing "[UserAccounts]" to "[UserList]"
Offline
I run lightdm 1:1.6.1-3.
You win, UI also think the same for the patches.
This behaviour can be changed by the way by changing this: "minimum-vt=1" to "minimum-vt=7".
However all systemd messages are still shown on tty1 and no login prompt is available.
“The future has already arrived. It's just not evenly distributed yet.”
― William Gibson
Offline
Thanks to Vacant - I've figured it out from Karols's post by the time you were writing it.
“The future has already arrived. It's just not evenly distributed yet.”
― William Gibson
Offline
Yeah, that bug is almost a year old, shall we buy it a birthday cake?
Seriously, my guess is the problem rarely crops up as most lightdm/ubuntu/gnome users have "account service" installed which means users.conf is never consulted.
Offline
I would be really interested in reactivating console login on tty1.
(Was that a linux trojan?)
Last edited by scar (2013-09-10 05:37:49)
“The future has already arrived. It's just not evenly distributed yet.”
― William Gibson
Offline
If you actually look in the lightdm.service file, you will find "Conflicts=getty@tty1.service". So if lightdm.service is activated and running, it will stop getty@tty1.service from activating.
This is not a bug. In fact, I would call it a feature. The rest of the ttys are auto activated on access. So for most users, there is really no point in using the resources (no matter how little) to start something that they are probably not going to see or use. So in place of the default agetty, the display-manager.service gets started.
IMO, you should leave this as is, and if you are really really concerned about having 6 TTYs, configure an additional TTY in logind.conf.
Last edited by WonderWoofy (2013-09-10 05:48:33)
Offline
You can call it a bug, a feautre or a virus too. It alters the way your box is working in an unexpected way.
I will not leave it, since I think all that Arch is about is customization, and I like it that way.
By the way, thank you for the hint.
[EDIT]
If I comment that line in lightdm.service, nothing changes. Still no tty1 !
Last edited by scar (2013-09-10 06:02:15)
“The future has already arrived. It's just not evenly distributed yet.”
― William Gibson
Offline
No. It is not a bug, and it is especially not a virus.
You can customize your machine however you please, but statements like that is just FUD.
Offline
The thing about the virus was just a joke, sorry, if it that hurted you so badly.
What I ment was that anytime something changes the working of a program, I would like to know about it. All that begun with another probem I've already solved, other users experienced it too, see: https://bbs.archlinux.org/viewtopic.php?id=169552.
By the way, login at tty1 stil not working. I've copied the service file to /etc/systemd/sytem/lightdm.service and uncommented the relevant "Conflicts=getty@tty1.service" line. Still no tty1.
If I launch manualy (systemctl start getty@tty1.service) , it launches.
[EDIT]
I think I found it. This one was missing:
/etc/systemd/system/getty.target.wants/getty@tty1.service
Otherwise the file existed on all my other boxes.
I've made a symlink to the /usr/ib/systemd/system/getty@.service and it works now.
However, I don't understand why it disappeared...
Finally, I can mark this as SOLVED
Last edited by scar (2013-09-11 07:25:25)
“The future has already arrived. It's just not evenly distributed yet.”
― William Gibson
Offline
Pages: 1