You are not logged in.
Hello,
Its a week that i can't light up my keyboard led because "xset led 3" or "xset led named "Scroll_Lock" doesn't work, and console doesn't show up nothing...
When i run these commands with sudo, console return:
No protocol specified
xset: unable to open display ":0"
Someone can help me to fix this little problem?
Last edited by twyK (2016-10-17 17:48:37)
Offline
Well, to run it as root, try sudo bash -c "DISPLAY=:0 xset led 3"
Not sure if it will help with the underlying problem.
Edit: Oh, and welcome to Arch Linux
Last edited by ewaller (2016-10-17 15:55:43)
Nothing is too wonderful to be true, if it be consistent with the laws of nature -- Michael Faraday
Sometimes it is the people no one can imagine anything of who do the things no one can imagine. -- Alan Turing
---
How to Ask Questions the Smart Way
Offline
Well, to run it as root, try sudo bash -c "DISPLAY=:0 xset led 3"
Not sure if it will help with the underlying problem.
It gave me the same error
EDIT: I need the led's on the keyboard turn on
Edit: Oh, and welcome to Arch Linux
I'm already using Arch for 1 month, loving it, thanks you ^.^
Last edited by twyK (2016-10-17 16:27:58)
Offline
Opps, sorry. This is an Xauthority thing.
Try:
sudo bash -c "XAUTHORITY=$(ls -1 /home/*/.Xauthority | head -n 1 ) xset led 3"
I think that will work
Nothing is too wonderful to be true, if it be consistent with the laws of nature -- Michael Faraday
Sometimes it is the people no one can imagine anything of who do the things no one can imagine. -- Alan Turing
---
How to Ask Questions the Smart Way
Offline
Opps, sorry. This is an Xauthority thing.
Try:sudo bash -c "XAUTHORITY=$(ls -1 /home/*/.Xauthority | head -n 1 ) xset led 3"
I think that will work
Now i get:
Invalid MIT-MAGIC-COOKIE-1 keyxset: unable to open display ":0"
Last edited by twyK (2016-10-17 16:39:22)
Offline
Forget about doing this as root, won't work (easily with sudo) and must not be required.
What's the output of "xset q | grep LED" resp. does "xset -led 3; sleep 1; xset led 3" get you somewhere?
And please post ~/.local/share/xorg/Xorg.*.log
Offline
Forget about doing this as root, won't work (easily with sudo) and must not be required.
What's the output of "xset q | grep LED" resp. does "xset -led 3; sleep 1; xset led 3" get you somewhere?
The output is:
grep: LED resp. does xset: File or directory does not exists
grep: 3: File or directory does not exists
And please post ~/.local/share/xorg/Xorg.*.log
Offline
Maybe try
xset q | grep LED
and also
xset -led 3; sleep 1; xset led 3
Welcome to linux.
Offline
Maybe try
xset q | grep LED
Output:
auto repeat: on key click percent: 0 LED mask: 00000006
and also
xset -led 3; sleep 1; xset led 3
Nothing happened
Welcome to linux.
Thanks you xD
Offline
Looking at the xorg logs, also the output of
xinput
and try to unplug the headset.
Offline
LED mask: 00000006
This means the scroll lock led is considered active by the system (and numlock)
Offline
LED mask: 00000006
This means the scroll lock led is considered active by the system (and numlock)
I tried also to turn on the keyboard LED on GRUB and it works correctly...
So how i can do? >.<
Offline
Offline
Ops, didn't see that.
xinput output:
⎡ Virtual core pointer id=2 [master pointer (3)]
⎜ ↳ Virtual core XTEST pointer id=4 [slave pointer (2)]
⎜ ↳ xwayland-pointer:13 id=6 [slave pointer (2)]
⎣ Virtual core keyboard id=3 [master keyboard (2)]
↳ Virtual core XTEST keyboard id=5 [slave keyboard (3)]
↳ xwayland-keyboard:13 id=7 [slave keyboard (3)]
Now i try to unplug the headset
EDIT: Un-plugging the headset don't change anything
Last edited by twyK (2016-10-17 17:19:26)
Offline
Do you run gnome on wayland?
Offline
Do you run gnome on wayland?
I dont know what is wayland, but i have gnome
Offline
wayland is an alternative display server and presently the default for gnome. You'll have to select gnome on X11 or similar on login.
At least it's not much of a surprise that xset cannot effectively control your keyboard on wayland.
Offline
wayland is an alternative display server and presently the default for gnome. You'll have to select gnome on X11 or similar on login.
At least it's not much of a surprise that xset cannot effectively control your keyboard on wayland.
I dont have similiar choice on gnome login, how i can switch manually?
Offline
yes you have, see https://bbs.archlinux.org/viewtopic.php … 9#p1661709
Offline
yes you have, see https://bbs.archlinux.org/viewtopic.php … 9#p1661709
Thanks you, i'll try this right now
Offline
*Headdesk* No wonder my stuff was hosed.
Nothing is too wonderful to be true, if it be consistent with the laws of nature -- Michael Faraday
Sometimes it is the people no one can imagine anything of who do the things no one can imagine. -- Alan Turing
---
How to Ask Questions the Smart Way
Offline
I'd say that Arch should revert the default against upstream.
It's premature and fucks with every noob while developers (which require it) will be able to find it.
If there was at least a big fat warning or a fixed wallpaper with every login....
Also there maybe should be a sticky in the forum: "before you post, do you run gnome on wayland?" because everything that's more involved with X11 will behave oddly for sure.
Offline
It Works!
*Headdesk* No wonder my stuff was hosed.
Ahaha thanks to you too, now you can close!
Offline
You can. Edit your original post, prepend [SOLVED] to the title and maybe append "(on wayland)" or some such.
Offline
You can. Edit your original post, prepend [SOLVED] to the title and maybe append "(on wayland)" or some such.
Done! Thanks You another time!
Offline