Difference between revisions of "Talk:Automatic login to virtual console"

From ArchWiki
Jump to: navigation, search
('With systemd' section does not work for me: fix indentation. replied. closed.)
(Killing X: new section)
(5 intermediate revisions by 2 users not shown)
Line 1: Line 1:
== Service Type ==
== Killing X ==
You were probably expecting for talk about the merge request but that's not what you're getting here.
I changed the [[Automatic_login_to_virtual_console#With_systemd|#With systemd]] section's service {{ic|Type}} to {{ic|simple}} (the default) to drastically speed up the boot. I went from 12.4 seconds to 7.2 once I figured out what it was.
I don't have any problems with X automatically restarting after I kill it. I have autologin configured and then I start X using {{ic|startx}}. Maybe this user is running a graphical display manager or a default target of {{ic|graphical.target}}?<br>
-- [[User:Jstjohn|Jstjohn]] ([[User talk:Jstjohn|talk]]) 21:51, 20 December 2012 (UTC)
And no, this is not a hack to simply skip all the other stuff you'd wanna boot with. Even the default display manager services and the (unrecommended) [[Systemd#Using_service_file|xinit method]] were much faster, which is why I started to look for what was wrong with this (_recommended_) one. --[[User:Det|Det]] ([[User talk:Det|talk]]) 21:31, 26 July 2012 (UTC)
:'''Issues with {{ic|logind}} and {{ic|systemctl}} shutdown/reboot'''
:Using this command should result in the system shutting down if only 1 user is currently logged in, but combined with this method for automatically logging in, it will refuse with {{ic|"Failed to issue method call: Access denied"}}. The {{ic|journalctl}} log files get butchered on my system so all I can see is something about dbus getting rejected. --[[User:Earnest|Earnest]] ([[User talk:Earnest|talk]]) 22:34, 27 July 2012 (UTC)
::Hmh. I have no idea what that means. I just tried starting X as root on another console and launching dolphin with {{ic|dbus-launch}} (of which I have no idea whether it's relevant or not) and I still could shutdown my system from my regular user account.
::But so is the {{ic|1=Type=idle}} method equally fast for you when compared to a display manager or the xinit method? Because if it's not, then why would you want to use that anyway? --[[User:Det|Det]] ([[User talk:Det|talk]]) 10:34, 28 July 2012 (UTC)
:::This whole situation may have something to do with not using {{ic|dbus-launch}}, but there are still some inconsistencies with that theory. I haven't given it much thought or testing as it's not a hindrance for me personally, but may affect others. As my testing has been limited I've not submitted a bug report, but for what it's worth here are some basic steps to reproduce:
:::1) Use the {{ic|autologin@.service}}
:::2) Launch a basic Xsession with {{ic|$ xinit $WM}}
:::3) Open a terminal and run {{ic|$ systemctl poweroff}}. Get ''"Access Denied"''.
:::4) Drop to another tty, login as a regular user and run the command again. Works (but not as intended).
:::As for {{ic|1=Type=idle}} vs. {{ic|1=Type=simple}}, I have personally not noticed a difference between the two on spinning media, it may have a notable difference on SSD that I'm unaware of. --[[User:Earnest|Earnest]] ([[User talk:Earnest|talk]]) 08:13, 30 July 2012 (UTC)
::::{{ic|systemctl}} must like me very much. Here's what I'm getting with {{ic|$ xinit openbox}}:
{{hc|$ systemctl poweroff|
<nowiki>==== AUTHENTICATING FOR org.freedesktop.login1.power-off ===</nowiki> ''(sic)''
Authentication is required for powering off the system.
Authenticating as: ,,, (det)
::::This happens even with the stock -ARCH kernel that _doesn't_ support {{ic|AUDIT_LOGINUID_IMMUTABLE}}.
::::By the way, for signatures you can just use the Wiki feature <nowiki>"--~~~~"</nowiki> (also as a button in the toolbar), instead of manually typing them. --[[User:Det|Det]] ([[User talk:Det|talk]]) 10:20, 30 July 2012 (UTC)
== <s>'With systemd' section does not work for me</s> ==
I explicitly followed the instructions in the "With systemd" section, and automatic log-in does not work for me on boot. If I try to enable the service, I get an error stating that the file already exists. When I start the service, it just kills any existing X server running on that TTY and drops me to an automatically logged-in console, and then loops through this auto-log-in -> log off -> auto-log-in loop that makes that TTY unusable. I switched to a different TTY and set {{ic|1=Restart=no}}, which gets rid of the looping issue. I am still unable to automatically log in to a TTY after booting, which is the whole point of my adventure into this.<br>-- [[User:Jstjohn|Jstjohn]] ([[User talk:Jstjohn|talk]]) 00:09, 18 September 2012 (UTC)
*I was able to fix this issue by simply disabling the default getty@tty1.service file.
: # systemctl disable getty@tty1.service
: # systemctl enable autologin@tty1.service
:Everything else in the wiki section was followed as is.
:-- [[User:Spychalski|Spychalski]] ([[User talk:Spychalski|talk]]) 01:08, 20 September 2012 (UTC)
*That fixed the issue for me as well. I'll update the wiki with this. Thanks!
:-- [[User:Jstjohn|Jstjohn]] ([[User talk:Jstjohn|talk]]) 15:03, 20 September 2012 (UTC)

Revision as of 21:51, 20 December 2012

Killing X

I don't have any problems with X automatically restarting after I kill it. I have autologin configured and then I start X using startx. Maybe this user is running a graphical display manager or a default target of graphical.target?
-- Jstjohn (talk) 21:51, 20 December 2012 (UTC)