CAP LOCK is not working in the newest version of bunsenlabs

sexynsmartjenny · 2018-01-13 04:32:59

Hi, I just installed the newest version of bunsenlabs, and I realized that the CAP LOCK is no longer working. It used to work fine in the older verison, but since now is 2018, so I reformatted my pc and installed the newest version and that is when it stopped working. I googled around and couldn't find a solution. Does anyone else have this problem or is it just me?

Last edited by sexynsmartjenny (2018-01-30 03:57:40)

tknomanzr · 2018-01-13 07:08:23

It is disabled by default. To enable it, edit ~/.config/openbox/autostart and comment the entry out.

sexynsmartjenny · 2018-01-13 16:48:45

Okay so I opened autostart and I see ## Disable CapsLock

and I just remove the ##?
Edit: never mind I got it. Thanks

Last edited by sexynsmartjenny (2018-01-13 16:55:24)

sexynsmartjenny · 2018-01-30 03:58:34

tknomanzr wrote:

It is disabled by default. To enable it, edit ~/.config/openbox/autostart and comment the entry out.

Hi, I'm sorry to bother you again, so I simply deleted the line that said Disable CapsLock and it worked for a while, but now my capslock is disabled once again. What did I do wrong?

Head_on_a_Stick · 2018-01-30 09:09:09

Have you checked the openbox autostart file for that pesky syndaemon line?

EDIT: if you're using Helium-dev then this will remove the `syndaemon` command from your system entirely and stop this from ever happening again:

sudo apt install xserver-xorg-input-{libinput,synaptics-}

^ And if that doesn't fix things then your caps lock key is broken

Last edited by Head_on_a_Stick (2018-01-30 09:12:04)

sexynsmartjenny · 2018-02-01 22:37:09

Head_on_a_Stick wrote:

Have you checked the openbox autostart file for that pesky syndaemon line?
EDIT: if you're using Helium-dev then this will remove the `syndaemon` command from your system entirely and stop this from ever happening again:
sudo apt install xserver-xorg-input-{libinput,synaptics-}
^ And if that doesn't fix things then your caps lock key is broken

it says

: Unable to locate package xserver-xorg-input-libinput

sexynsmartjenny · 2018-02-01 22:39:32

in the autostart file, this is the line with syndaemon

## Disable touchpad while typing
syndaemon -i .5 -K -t -R -d &

Head_on_a_Stick · 2018-02-02 07:10:41

sexynsmartjenny wrote:

it says

: Unable to locate package xserver-xorg-input-libinput

Sorry, I thought you were using helium-dev but you quite clearly stated otherwise, there is no libinput package for Hydrogen/Deuterium.

sexynsmartjenny wrote:

in the autostart file, this is the line with syndaemon

Yes, that's the line you need to remove (or comment out).

I am confused though because you must have removed that line to fix this problem originally so why is it back now?

tknomanzr · 2018-02-02 16:10:41

I had her remove/comment out the capslock entry.

sexynsmartjenny · 2018-02-02 23:09:05

Head_on_a_Stick wrote:

sexynsmartjenny wrote:
it says
: Unable to locate package xserver-xorg-input-libinput
Sorry, I thought you were using helium-dev but you quite clearly stated otherwise, there is no libinput package for Hydrogen/Deuterium.
sexynsmartjenny wrote:
in the autostart file, this is the line with syndaemon
Yes, that's the line you need to remove (or comment out).
I am confused though because you must have removed that line to fix this problem originally so why is it back now?

I removed the line with syndaemon completely and it's still not working

Head_on_a_Stick · 2018-02-03 10:30:33

Are you sure that the caps lock key is not broken?

Please post the output of:

pgrep -a syndaemon

sexynsmartjenny · 2018-02-03 16:22:44

Head_on_a_Stick wrote:

Are you sure that the caps lock key is not broken?
Please post the output of:
pgrep -a syndaemon

When I enter the code you give me, Nothing shows up.

Head_on_a_Stick · 2018-02-03 17:45:38

^ That means that `syndaemon` is not running and so cannot be disabling your caps lock key.

Hardware failure is a distinct possibility here, can you eliminate that?

sexynsmartjenny · 2018-02-03 22:29:34

Head_on_a_Stick wrote:

^ That means that `syndaemon` is not running and so cannot be disabling your caps lock key.
Hardware failure is a distinct possibility here, can you eliminate that?

yes, I most definitely know for sure that it's not a hardware issue. The CAP LOCK key worked fine until I reformatted my laptop and upgraded to the newest version of bunsenlab.

Head_on_a_Stick · 2018-02-03 22:43:31

If you try another "live" ISO image, does the caps lock key work in that?

In the BunsenLabs desktop, please run this command

xev

Then press the caps lock key and post anything that appears in the terminal afterwards.

Does this make the key work?

sudo pkill syndaemon

Please also post the full output of:

grep -v '^#\|^$' ~/.config/openbox/autostart

Thanks!

sexynsmartjenny · 2018-02-04 01:48:07

this is what happened after I run the command xev

Outer window is 0x4800001, inner window is 0x4800002

PropertyNotify event, serial 8, synthetic NO, window 0x4800001,
    atom 0x27 (WM_NAME), time 2907655, state PropertyNewValue

PropertyNotify event, serial 9, synthetic NO, window 0x4800001,
    atom 0x22 (WM_COMMAND), time 2907655, state PropertyNewValue

PropertyNotify event, serial 10, synthetic NO, window 0x4800001,
    atom 0x28 (WM_NORMAL_HINTS), time 2907655, state PropertyNewValue

CreateNotify event, serial 11, synthetic NO, window 0x4800001,
    parent 0x4800001, window 0x4800002, (10,10), width 50, height 50
border_width 4, override NO

PropertyNotify event, serial 14, synthetic NO, window 0x4800001,
    atom 0x156 (WM_PROTOCOLS), time 2907656, state PropertyNewValue

MapNotify event, serial 15, synthetic NO, window 0x4800001,
    event 0x4800001, window 0x4800002, override NO

PropertyNotify event, serial 18, synthetic NO, window 0x4800001,
    atom 0x1ae (_NET_WM_VISIBLE_NAME), time 2907657, state PropertyNewValue

PropertyNotify event, serial 18, synthetic NO, window 0x4800001,
    atom 0x1af (_NET_WM_VISIBLE_ICON_NAME), time 2907658, state PropertyNewValue

PropertyNotify event, serial 18, synthetic NO, window 0x4800001,
    atom 0x1cf (_OB_APP_ROLE), time 2907658, state PropertyNewValue

PropertyNotify event, serial 18, synthetic NO, window 0x4800001,
    atom 0x1d1 (_OB_APP_NAME), time 2907658, state PropertyNewValue

PropertyNotify event, serial 18, synthetic NO, window 0x4800001,
    atom 0x1d2 (_OB_APP_CLASS), time 2907658, state PropertyNewValue

PropertyNotify event, serial 18, synthetic NO, window 0x4800001,
    atom 0x1d3 (_OB_APP_GROUP_NAME), time 2907658, state PropertyNewValue

PropertyNotify event, serial 18, synthetic NO, window 0x4800001,
    atom 0x1d4 (_OB_APP_GROUP_CLASS), time 2907658, state PropertyNewValue

PropertyNotify event, serial 18, synthetic NO, window 0x4800001,
    atom 0x1d0 (_OB_APP_TITLE), time 2907658, state PropertyNewValue

PropertyNotify event, serial 18, synthetic NO, window 0x4800001,
    atom 0x1d5 (_OB_APP_TYPE), time 2907658, state PropertyNewValue

PropertyNotify event, serial 18, synthetic NO, window 0x4800001,
    atom 0x15f (_NET_WM_ICON), time 2907659, state PropertyNewValue

ReparentNotify event, serial 18, synthetic NO, window 0x4800001,
    event 0x4800001, window 0x4800001, parent 0x1401b68,
    (0,0), override NO

PropertyNotify event, serial 18, synthetic NO, window 0x4800001,
    atom 0x164 (_NET_WM_STATE), time 2907660, state PropertyNewValue

ConfigureNotify event, serial 18, synthetic NO, window 0x4800001,
    event 0x4800001, window 0x4800001, (0,0), width 178, height 178,
    border_width 0, above 0x1401b94, override NO

ConfigureNotify event, serial 18, synthetic NO, window 0x4800001,
    event 0x4800001, window 0x4800001, (1,20), width 178, height 178,
    border_width 0, above 0x1401b94, override NO

PropertyNotify event, serial 18, synthetic NO, window 0x4800001,
    atom 0x15b (_NET_FRAME_EXTENTS), time 2907661, state PropertyNewValue

PropertyNotify event, serial 18, synthetic NO, window 0x4800001,
    atom 0x1b5 (_KDE_NET_WM_FRAME_STRUT), time 2907661, state PropertyNewValue

PropertyNotify event, serial 20, synthetic NO, window 0x4800001,
    atom 0x1b3 (_NET_WM_ALLOWED_ACTIONS), time 2907664, state PropertyNewValue

ConfigureNotify event, serial 20, synthetic YES, window 0x4800001,
    event 0x4800001, window 0x4800001, (1844,317), width 178, height 178,
    border_width 2, above 0x0, override NO

PropertyNotify event, serial 20, synthetic NO, window 0x4800001,
    atom 0x15e (_NET_WM_DESKTOP), time 2907664, state PropertyNewValue

MapNotify event, serial 30, synthetic NO, window 0x4800001,
    event 0x4800001, window 0x4800001, override NO

VisibilityNotify event, serial 30, synthetic NO, window 0x4800001,
    state VisibilityUnobscured

Expose event, serial 30, synthetic NO, window 0x4800001,
    (0,0), width 178, height 10, count 3

Expose event, serial 30, synthetic NO, window 0x4800001,
    (0,10), width 10, height 58, count 2

Expose event, serial 30, synthetic NO, window 0x4800001,
    (68,10), width 110, height 58, count 1

Expose event, serial 30, synthetic NO, window 0x4800001,
    (0,68), width 178, height 110, count 0

PropertyNotify event, serial 30, synthetic NO, window 0x4800001,
    atom 0x18e (WM_STATE), time 2907683, state PropertyNewValue

FocusIn event, serial 31, synthetic NO, window 0x4800001,
    mode NotifyNormal, detail NotifyNonlinear

KeymapNotify event, serial 31, synthetic NO, window 0x0,
    keys:  39  0   0   0   16  0   0   0   0   0   0   0   0   0   0   0   
           0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   

KeyRelease event, serial 31, synthetic NO, window 0x4800001,
    root 0x93, subw 0x0, time 2907720, (-1430,-73), root:(416,246),
    state 0x0, keycode 36 (keysym 0xff0d, Return), same_screen YES,
"   XLookupString gives 1 bytes: (0d) "
    XFilterEvent returns: False

PropertyNotify event, serial 31, synthetic NO, window 0x4800001,
    atom 0x1b2 (_NET_WM_ICON_GEOMETRY), time 2907725, state PropertyNewValue

KeyPress event, serial 48, synthetic NO, window 0x4800001,
    root 0x93, subw 0x0, time 2911927, (-1430,-73), root:(416,246),
    state 0x0, keycode 66 (keysym 0xffe3, Control_L), same_screen YES,
    XKeysymToKeycode returns keycode: 37
    XLookupString gives 0 bytes: 
    XmbLookupString gives 0 bytes: 
    XFilterEvent returns: False

KeyRelease event, serial 48, synthetic NO, window 0x4800001,
    root 0x93, subw 0x0, time 2912071, (-1430,-73), root:(416,246),
    state 0x4, keycode 66 (keysym 0xffe3, Control_L), same_screen YES,
    XKeysymToKeycode returns keycode: 37
    XLookupString gives 0 bytes: 
    XFilterEvent returns: False

FocusOut event, serial 48, synthetic NO, window 0x4800001,
    mode NotifyNormal, detail NotifyNonlinear

And no sudo pkill syndaemon doesnt seem to do anything either.

And here is the output of my autostart

grep -v '^#\|^$' ~/.config/openbox/autostart
xset b off
xset r rate 250 25
setxkbmap -option ctrl:nocaps
synclient VertEdgeScroll=1 HorizEdgeScroll=1 TapButton1=1 2>/dev/null
/usr/lib/policykit-1-gnome/polkit-gnome-authentication-agent-1 &
nitrogen --restore
bl-compositor --start
bl-tint2-session
bl-start-pulseaudio-x11
volumeicon &
bl-conky-session --autostart &
clipit &
(sleep 10; bl-welcome --firstrun) &
/home/jennifersuzuki/Documents/screens.sh

Head_on_a_Stick · 2018-02-04 11:24:32

sexynsmartjenny wrote:

this is what happened after I run the command xev

That looks to me as if the key is broken, there is no output corresponding to that address

Can you test in the "live" environment?

Probably best to use a non-BunsenLabs ISO (if you have one available) because I can't remember if the caps lock key is disabled in our live session :8

#1 2018-01-13 04:32:59

CAP LOCK is not working in the newest version of bunsenlabs

#2 2018-01-13 07:08:23

Re: CAP LOCK is not working in the newest version of bunsenlabs

#3 2018-01-13 16:48:45

Re: CAP LOCK is not working in the newest version of bunsenlabs

#4 2018-01-30 03:58:34

Re: CAP LOCK is not working in the newest version of bunsenlabs

#5 2018-01-30 09:09:09

Re: CAP LOCK is not working in the newest version of bunsenlabs

#6 2018-02-01 22:37:09

Re: CAP LOCK is not working in the newest version of bunsenlabs

#7 2018-02-01 22:39:32

Re: CAP LOCK is not working in the newest version of bunsenlabs

#8 2018-02-02 07:10:41

Re: CAP LOCK is not working in the newest version of bunsenlabs

#9 2018-02-02 16:10:41

Re: CAP LOCK is not working in the newest version of bunsenlabs

#10 2018-02-02 23:09:05

Re: CAP LOCK is not working in the newest version of bunsenlabs

#11 2018-02-03 10:30:33

Re: CAP LOCK is not working in the newest version of bunsenlabs

#12 2018-02-03 16:22:44

Re: CAP LOCK is not working in the newest version of bunsenlabs

#13 2018-02-03 17:45:38

Re: CAP LOCK is not working in the newest version of bunsenlabs

#14 2018-02-03 22:29:34

Re: CAP LOCK is not working in the newest version of bunsenlabs

#15 2018-02-03 22:43:31

Re: CAP LOCK is not working in the newest version of bunsenlabs

#16 2018-02-04 01:48:07

Re: CAP LOCK is not working in the newest version of bunsenlabs

#17 2018-02-04 11:24:32

Re: CAP LOCK is not working in the newest version of bunsenlabs

Board footer