Hot answers tagged

2

It sounds as if you want pseudocolor, which isn't well supported anymore. A thread on Xorg a few years ago pointed out a problem with the feature, but concluded by suggesting that it could work with a vesa driver. Alternatively, a discussion on a Raspberry Pi forum suggested using Xephyr (a nested X server) in which one could run a client. Further reading: ...


2

xdotool(1) can do that. To rename whatever window you click next: xdotool selectwindow set_window --name "new name" To find a window based on its current name, then rename it: xdotool search --name "old name" set_window --name "new name" However, this won't last for any application (such as Firefox) that keeps updating its own name. The way to ...


1

You are not far wrong with that --transformation! The point is that you not only want to shift the screen to the right, but also you need to shrink it by half in the horizontal axis. To do so lets refer to the xrandr manual where we read: --transform a,b,c,d,e,f,g,h,i (...) In other words, the device coordinates (x' y') of the transformed ...


1

I found the answer. I updated ~/.config/monitors.xml and looked for VGA1 which is my TV and set up correct width and height (1408x792) and after a restart the configuration was applied successfully.


1

If you are using systemd you can find your current layout with localectl status which might print something like System Locale: LANG=en_US.UTF-8 VC Keymap: us X11 Layout: us X11 Model: pc104 X11 Options: caps:capslock Use these values when setting a new layout [model [variant [options]]], eg: sudo localectl set-x11-keymap ...


1

The log tells you what you should do about it: GPU hangs can indicate a bug anywhere in the entire gfx stack, including userspace. Please file a new bug report on bugs.freedesktop.org against DRI -> DRM/Intel drm/i915 developers can then reassign to the right component if it's not a kernel issue. The gpu crash dump is required to analyze gpu ...


1

Presumably, you know about xset dpms which provides power management of the display, and brightd which does progressive backlight changes, but if these don't suffice you can detect movement once you are in idle mode by using xinput as follows. List the input devices with simply xinput and find the ids of the mouse and keyboard you want to listen to. In my ...


1

You can try using dbus. Specifically, use dbus-send to invoke the GetSessionIdleTime method on org.freedesktop.ScreenSaver: dbus-send --session --dest=org.freedesktop.ScreenSaver --type=method_call --print-reply=literal /ScreenSaver org.freedesktop.ScreenSaver.GetSessionIdleTime This will print out 4 spaces, then "uint32", then the number of milliseconds ...



Only top voted, non community-wiki answers of a minimum length are eligible