Tag Info

New answers tagged

0

The problem is that your image is scaled down to fit the configured icon size for that label. The configured size is a square, while the icon is not, so it's heavily padded. It should work after you configure the icon size to be of a similar shape rectangle, ideally the same size; The name of the icons size property for that menu icon is ...


1

Assuming you use Bash, put the same thing in both ~/.bashrc and ~/.bash_profile. That's what I had to do, at least. Assuming you're using fink, and by all indications of how you've set everything up, it looks like you do.


0

Premilinary note: you shouldn't use the obsolete xmodmap command, but XKB (xkbcomp). Then you can change the settings from your ~/.xsession script. Personally I have: setxkbmap -types local -print | \ sed -e '/xkb_symbols/s/"[[:space:]]/+local&/' > $HOME/.xkb/keymap/custom xkbcomp -w0 -I$HOME/.xkb -R$HOME/.xkb keymap/custom $DISPLAY in my ...


2

on ~/.config/openbox/lxde-rc.xml you can add some keybends to make a program to start when you press it. <keybind key="C-A-L"> <action name="Execute"> <command>xscreensaver-command -lock</command> </action> </keybind> Just read what @goldilocks added. :) ...


2

I can't test this, because I don't have a right Win, but you can check out System Settings > Hardware > Input Devices > Keyboard > Layouts > Shortcuts for Switching Layout > 3rd level shortcuts. This will open up Advanced > Key to choose 3rd level. Select Right Win.


1

kbdrate From the man page of kbdrate: Using kbdrate without any options will reset the repeat rate to 10.9 characters per second (cps) and the delay to 250 milliseconds (ms) for Intel- and M68K-based systems. So the behavior you're experiencing is as expected. You may want to adjust the delay from the problem you've stated. Try kbdrate -d 500 for ...


0

I agree with Keith, above - you likely have installed two different nvidia drivers over time. My suggested remedy would be: ensure you've updated to the most recent kernel for your distribution ensure you have installed kernel headers and any other dependent packages required for nvidia kernel module compilation reboot (to your latest kernel) install the ...


2

Michael Homer and Guido van Steen have shown ways to kill all windows. This wouldn't kill background processes, if there are any. It wouldn't kill crashed programs whose window has gone but that are still executing without a user interface. So you may prefer to kill the processes instead. You can run kill -9 -1 as a non-root user to kill all the processes ...


2

The simplest approach uses xdotool: xdotool search "" windowkill %@ xdotool search "" lists every window. windowkill %@ kills every one of them; %@ refers to all the results of the previous search. You may prefer to use the --maxdepth 1 option to search to limit the windows selected to top-level windows.


1

this works at least for kde and xfce (gnome not tested, but it might work as well): 1) install wmctrl 2) then create a script called close_windows.sh: # close all open windows gracefully without closing the Desktop environment WIN_IDs=$(wmctrl -l | grep -vwE "Desktop$|xfce4-panel$" | cut -f1 -d' ') for i in $WIN_IDs; do wmctrl -ic "$i"; done # Keep ...


1

Mine did this too, sometimes. Everything would start doing unexpected things; mashing the meta keys a few times corrected the problem. It turns out I had a rubbish keyboard. Are you sure you don't have an actual sticky key? It doesn't have to look stuck. Sometimes it just seems to miss the key-up event.


1

There isn't a way to do that as part of X itself, but there is the "screen for X" tool xpra. Xpra: allows you to run X11 programs, usually on a remote host, direct their display to your local machine, and then to disconnect from these programs and reconnect from the same or another machine, without losing any state. It works quite well and with no ...


0

Technically, you can run an X server on Android. For a bare X11 server, see Play store: X Server for example. That could help with very special needs, like showing a plot window on fixed screen position with no window manager for example. You could run a full xsession on that display of course, but I think that is not too useful in most general cases. ...


4

You can actually do this with xclip. The secret is the -t option, which refers you to the ICCCM Section 2.6.2. Which I confess I don't blame you for failing to read... Anyway, an example, I have just right-clicked your avatar in Chromium and selected "Copy Image": See what targets are available: $ xclip -selection clipboard -t TARGETS -o TARGETS ...


2

The other two values are for ISO_Level3_Shift and ISO_Level3_Shift+Shift (ISO_Level3_Shift generally corresponds to the AltGr key).


1

Still having some (I think unrelated) issues with XKB myself, but I do have a Hyper modifier mapped, and I believe the relevant settings are these: compat: virtual_modifiers Shift,Control,Meta,Super,Hyper,AltGr; interpret Hyper_R { action = SetMods(modifiers=Mod4); }; symbols: modifier_map Mod4 { <DELE> }; // Hyper key <DELE> { ...


0

I wrote the following script to check for idle and update the session idle status with systemd-logind accordingly. (Normally this would be done by the session manager, but I don't run one.) This lets systemd put the system to sleep automatically (based on IdleAction and IdleActionSec in /etc/systemd/logind.conf), with consideration of both X11 and ssh logins ...


1

Well I couldn't test all the options, but it seems that xrandr has a left to right and top to bottom orientation. Here's a screenshot of my monitors to help understand better: When I run xrandr on my Terminal, this is what I get: Screen 0: minimum 320 x 200, current 3046 x 1050, maximum 32767 x 32767 LVDS1 connected 1366x768+0+282 (normal left inverted ...


3

What you refer to as a windowing system is more commonly referred to as a display server. The differences between display servers are well documented. But, the difference between a display server and a window manager is in the job that they perform. A display server handles displaying graphical applications and relaying input and output from graphical ...


1

Yes, the "Ring" needs the names of the programs which will be included in it. But, assuming all windows you have also yield an icon, you can navigate over the Icon Manager by programming keys (I use Shift, Alt or Ctrl and F9, F10 and F11 to move left, right or down and F12 to deiconize the Icon Manager if it gets iconized. This will work whether the window ...


0

This was changed in October 2012 during/after the migration to systemd/logind. According to a bug report, running the X server on a different tty than the active consolekit session caused things to break because the session on (for example) TTY7 would not be authenticated . Without logind, one could use ck-launch-session in ~/.xinitrc to get a new session ...


0

You may try the sux command: sux user2 sux will handle the $DISPLAY stuff for you. You may need to install it with: sudo apt-get install sux under Debian/Ubuntu.


0

I don’t think this is possible, because there can always only be one window that receives input from mice and keyboards, i.e. one window that has the focus. But you can run the program you want to automate in a separate X-server. So do X :1 & export DISPLAY=:1 myprogram & xdotool … This way you can also use the whole screen. The downside to this ...


0

Running su - erases almost all environment variables. GUI applications need two environment variables to know how to connect to the GUI environment: DISPLAY and XAUTHORITY. See Open a window on a remote X display (why "Cannot open display")? for a more detailed explanation. The command su - retains DISPLAY but not XAUTHORITY. So your GUI ...


0

I have now figured out that the stuck pixel is caused by Citrix. It's some kind of bug in the way Citrix interacts with X I guess.


1

I do have a dead pixel on my screen that can disappear by gently pressing the screen or by rebooting perhaps it is a dead pixel. Try to find if it is a dead pixel. You can set the screen to a lower resolution. If the spot is bigger the problem is a display bug. If the size didn't change, your screen has a "dead pixel" You can also boot another Linux ...


1

It is really unclear with your question's current state. I believe you have to export the display. export DISPLAY='IP:0.0' See the answer here. Check the server's sshd_config (normally /etc/ssh/sshd_config), and make sure the X11Forwarding option is enabled with the line X11Forwarding yes If X11Forwarding is not specified, the default is no.


3

GUI applications under Linux require that a X server be available to drive a system's displays/monitors. Part of the responsibility of the X server is to accept/deny connections from applications that require access to the display/monitor. In your case you're running PuTTY on Windows so there is no X server to provide access for these GUI applications, so ...


0

You need to install X server on your windows PC to be able to see the output. Here is a link for one of the X Server software. after installing this then you can set your DISPLAY option to output to your windows PC example to set the display option : export DISPLAY=${XSERVER}:0.0


1

You said: "Now it's unable to open a PDF document in putty". Was it ever able to open the pdf file in the first place, or you are trying this for the first time? As per the error, I can see that you don't have a valid display. Run the following commands to see if you have an X server (and proper display) running: ps -e | grep X echo $DISPLAY If no ...


0

Rather than loosing 5 seconds to sleep why not put the Bluetooth disable to your xrandr script that runs with auto-start?



Top 50 recent answers are included