Tag Info

New answers tagged

1

2 shots: 1. Perhaps login as root is denied (that's the default setting on many systems and it is pretty reasonable). Did you tried with a different user? 2. Did you try sshing with ssh -Y?


0

@xenoterracide's solution is ok if the AutoAddDevice option is enabled in the ServerLayout of your xorg.conf. If not (especially in multiseat X configurations), you need to insert the XkbOptions line into the InputDevice section describing your keyboard. For example: Section "InputDevice" Identifier "keyboard-vmware" Driver "evdev" Option ...


1

I had the same question/problem. Alt-LeftArrow and Alt-RightArrow didn't do anything for me. They just printed ^[[C and ^[[D on the screen. Mine ended up being Ctrl-Alt-F3. It varied depending on number of ttys that were configured in /etc/ttys. I had 2 uncommented ttys, so it was Ctrl-Alt-F3. When I uncommented another tty, it became Ctrl-Alt-F4.


1

Only scaling wont help. I have yoga 2 pro with resolution 3200x1800 and external FHD monitor. In my case i use xrandr panning option: xrandr --output eDP1 --auto --output HDMI1 --auto --panning 3840x2160+3200+0 --scale 2x2 --right-of eDP1 Basically if your hidpi monitor is AxB pixels and your regular monitor is CxD and you are scaling by [ExF], the ...


0

After researching, I found out that this is a fundamental limitation of the X11 protocol. Specifically, the data type used to represent a keycode is a byte, which limits values to between 8 to 255 (+8 bias). It's an issue that's intended to be resolved in the X12 protocol (see Resource Limits). One workaround is to remap the keycode into the valid range ...


0

I can't provide the information you requested in a comment, so here goes: Hardware $ sudo lshw -C system bedroom-gentoo description: Desktop Computer product: M68M-S2P () vendor: Gigabyte Technology Co., Ltd. width: 64 bits capabilities: smbios-2.4 dmi-2.4 vsyscall32 configuration: boot=normal chassis=desktop ...


3

Reset the user by moving everything in /home/faultyuser to a backup directory like this: mkdir /home/faultyuser/BACKUP mv /home/faultyuser/* /home/faultyuser/BACKUP mv /home/faultyuser/.* /home/faultyuser/BACKUP cp -v /etc/skel/.[a-z]* /home/faultyuser/ chown faultyuser:faultyuser /home/faultyuser/.* and try to login. When this works, move all you need ...


1

I'm sorry, but this moment, the r128 is no longer supported by ATi (it's supported in Debian Squeeze, which is still under maintenance but very outdated). However, you can enable some hardware acceleration by using the open source driver xserver-xorg-video-r128 plus the non-free firmware r100_cp.bin contained in firmware-linux-nonfree package.


0

I realize this is late coming but: Checking the select box offered the easiest most succinct resolution in my situation. Ubuntu did not require and had it automatically selected so while it was confusing, it was also easily resolved. You may have to configure synclient but more than likely you can alleviate the issue with a few pokes around your ...


1

As has been mentioned, it's fairly straightforward to determine the kernel driver in use, but without the Xorg logs, it's a little more tricky to determine which userland X server driver is being used. For systems that have it, glxinfo can be used (although that will only give you general device information, not the actual driver name). glxinfo | grep ...


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 ...


1

I've solved. I looked the log: backup framebuffer data, that it means that it changes framebuffer. I've thinked: "The framebuffer doesn't work maybe?". So I have try to change framebuffer using this: https://wiki.archlinux.org/index.php/Uvesafb and now it works. And I think this is also the only way, for ATI proprietary drivers, to really change TTY ...


1

ATI drivers are terrible on Linux. Try other driver versions, x and kernel too. Eventually it will work, but don't expect radeon to be stable at all. Everybody I know get continous X crashes or some artefacts, and performance is not better too.


1

Well, thanks to @Basile's comment, I learned a lot and came up with following working sample: #!/usr/bin/python3 import Xlib import Xlib.display disp = Xlib.display.Display() root = disp.screen().root NET_WM_NAME = disp.intern_atom('_NET_WM_NAME') NET_ACTIVE_WINDOW = disp.intern_atom('_NET_ACTIVE_WINDOW') ...


0

Looking to xinput --list as suggested by Alexander Barakin shown that my gamepad isn't handled by Xorg. Games directly communicate with /dev/input/js* so Xorg doesn't know any activity through gamepad. Possible solutions: wrapper scripts around commands that xset -dpms s off; COMMAND; xset +dpms s on detecting X properties, like class/resource pattern ...


0

If you have strace, and it is not setuid to root, then strace -e '!all' program_name [argument(s)] should work.  strace(1) says (under BUGS): Programs that use the setuid bit do not have effective user ID privileges while being traced. because it would be a security problem if a non-privileged user could trace a setuid program (because tracing lets ...


0

Before opening your dvi file, try running: export DISPLAY=:0.0


0

lspci -k will show devices and modules loaded for them. You can grep it for the specific device you are looking for, such as 'VGA' lspci -k|grep -A2 VGA



Top 50 recent answers are included