Tag Info

New answers tagged

3

FocusOut event, serial 37, synthetic NO, window 0x4c00001, mode NotifyGrab, detail NotifyAncestor FocusIn event, serial 37, synthetic NO, window 0x4c00001, mode NotifyUngrab, detail NotifyAncestor What happened when you pressed A with Shift held is a passive grab: there's an X client which has exclusive control over this key combination, and ...


1

This is kind of crude, but why not just blacklist the atkbd driver. echo blacklist atkbd > /etc/modprobe.d/no-atkbd.conf You'll probably need to rebuild your initrd to make sure it gets blacklisted very early on in the boot process.


-1

Run the command in the terminal: xinput list It get you list of devices. Than you can disable some of them by id: xinput set-prop 10 "Device Enabled" 0


0

Check the setleds command, see if you can turn the led light on. In any case, it seems to me that this is bug. I would file a bug in their bugzilla, but Fedora 19 is end of life so I'm not sure if that possible.


0

tmux and xterm in Fullscreen mode with awesome-wm and vimperator browser add-on for vim-like keyboard shortcuts and many other extras. By the way, awesome-wm is very light-weight that comes with nine (9) "desktops" by default; an upgrade from your 4. To get the terminal in awesome-wm, just hit "Super/Windows-key/Mod4"+Enter. Switching desktops is done ...


2

For the desktop environment, I would advise a DWM-based tool like DWM, awesome, or i3. Get used to a terminal multiplexer like screen or tmux. For the text editor, obviously emacs or vim. For your web browser, try vimperator, or use a plugin for firefox/chromium (VimFX or Vimium for a vim-like experience). There may be others using emacs style.


1

The bios can be entered by using the Del key on the keyboard. The folowing quote is from the official user manual which can be foud here: The firmware chip on the motherboard stores the Setup utility. When you start up the computer, the system provides you with the opportunity to run this program. Press "Del" during the Power-On Self-Test (POST) ...


0

I had the same issue on my ubuntu 14.04 machine. The problem might be the default usbhid driver prevents your driver to function properly. That may be the reason why the probe is not getting invoked on hotplug. Try removing usbhid module. Check for udev rules defined by your distro, that autoloads the default usbhid driver module on hotplug even if you ...


0

It's going to be pretty hard to give a solid answer without just taking shots in the dark, but since this is happening on separate hardware and software, this may have something to do with any programs which run cross-platform which have settings and run via an interpreter or similar. For example the collection of extensions you run in Firefox or a ...


0

The most direct way would be reading event devices exposed in /dev/input/. Read the kernel document on Linux input subsystem, from which you could learn how to manipulate those devices in C. There're several packages for you to quickly test your input devices. For example you can use the following tools after apt-get install input-utils on Ubuntu. ...


1

(I noticed a complaint that kbdrate might have a max limitation. Not sure how true it still is). I use xset r rate 250 60 to accomplish speedups to my liking. I happen to put that in my ~/.i3/config (for i3wm) but I used to have it working in my ~/.xinitrc for startx to pick up. The xset invocation should apply to everything running in X. (I’d be curious ...


1

A solution for X11 is described in the post by @Jav. Remapping the keys in the Linux console: read the docs: man 5 keymaps dump the current mappings to a file with dumpkeys run showkey to find the keycodes for the keys you want to remap change the relevant entries in the file produced by dumpkeys install the new mappings with loadkeys. Steps 2., 3., and ...


1

I suggest you use xmodmap which works only with X. In a file (for example: ~/.Xmodmap), write something like this: keycode 0x63 = Up keycode 0x69 = Down You just have to execute xmodmap ~/.Xmodmap to enable your new configuration. Here you will find a list of all the keycode and to what key they correspond.


0

I've had this problem before as well w/ a bluetooth keyboard. It was infuriating because I only ever connected it twice: the first time it worked fine, but, a month later, on the second occasion, only some keys worked and those that did only came out as numbers. Of course, in my case, I had a little extra motivation to find the cause because I knew it could ...


0

I ran into the same problem installing OpenBSD 5.7 on a Jetway barebones box (JBC375F3AW-2930-B, but this probably applies to most or all models). The fix was to go into the BIOS setup program, and on the "Advanced" screen, set the "OS Selection" item to "Android".



Top 50 recent answers are included