Difference between revisions of "Talk:Activating Numlock on Bootup"

From ArchWiki
Jump to: navigation, search
(systemd service -> AUR Package: Remove cllosed discussion.)
(Extending getty@.service)
(One intermediate revision by one other user not shown)
Line 6: Line 6:
 
Maybe we should put a warning at least?
 
Maybe we should put a warning at least?
  
 +
:Same here. I had more luck with {{ic|ExecStartPre}} instead of {{ic|ExecStartPost}}, though I don't know if that has other side effects. --[[User:Norfanin|Norfanin]] ([[User talk:Norfanin|talk]]) 12:16, 16 November 2013 (UTC)
  
== .sh extension ==
+
== <s> .sh extension </s> ==
 
as of KDE. script workaround as described didn't work for me.  
 
as of KDE. script workaround as described didn't work for me.  
 
adding .sh extension and pre-kde startup did the trick  
 
adding .sh extension and pre-kde startup did the trick  
 
--[[User:Josephk|Josephk]] ([[User talk:Josephk|talk]]) 16:58, 23 February 2013 (UTC)
 
--[[User:Josephk|Josephk]] ([[User talk:Josephk|talk]]) 16:58, 23 February 2013 (UTC)
 +
: Page updated. Thanks. -- [[User:Fengchao|Fengchao]] ([[User talk:Fengchao|talk]]) 12:55, 11 November 2013 (UTC)

Revision as of 12:16, 16 November 2013

Extending getty@.service

For many months I used this method, and it caused huge instability problems that I couldn't track down... Putting that service in exactly as described causes VTs to flicker and go black and unresponsive about half of the time.

Maybe we should put a warning at least?

Same here. I had more luck with ExecStartPre instead of ExecStartPost, though I don't know if that has other side effects. --Norfanin (talk) 12:16, 16 November 2013 (UTC)

.sh extension

as of KDE. script workaround as described didn't work for me. adding .sh extension and pre-kde startup did the trick --Josephk (talk) 16:58, 23 February 2013 (UTC)

Page updated. Thanks. -- Fengchao (talk) 12:55, 11 November 2013 (UTC)