Hot answers tagged


Accessing the X server requires two things: The $DISPLAY variable pointing to the correct display (usually :0) Proper authentication information The authentication information can be explicitly specified via $XAUTHORITY, and defaults to ~/.Xauthority otherwise. If $DISPLAY and $XAUTHORITY is set for your user, sudo will set them for the new shell, too, ...


Short of muting the sound entirely or disconnecting your headphones, there is no system-wide setting for events which will be followed by all applications. In your case especially, since you’re using Nautilus on a KDE system, you’ll run into issues since Nautilus won’t follow your desktop’s configured behaviour. Nautilus uses GNOME’s settings. If you have ...


Just force the pointer to skip pixels, here's how: First list input devices: $ xinput list ⎡ Virtual core pointer id=2 [master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4 [slave pointer (2)] ...


Does Ctrl+Alt work? Found it mentioned in a bug tracker, but I can't test it myself as I don't use KDE.


I do not know what sound KDE does, but if you mean system beep, just disable loading of the pcspkr module. As root do: rmmod pcspkr ; echo "blacklist pcspkr" >>/etc/modprobe.d/blacklist.conf


I had the same question as you but for a normal user. Let's say I want to start firefox using the user account foo. I'm logged in as bar: [bar@localhost ~]$ sudo -u foo -H firefox Sadly that command failed with the same error as in the question (i.e. no protocol specified & cannot open display) My solution was to simply add the user foo to the list of ...


The problem is somewhat similar to accessing the X display and finding the location of the X cookie file. (Also, refer to these questions if you want to launch a GUI program on the user's display.) Dbus stores the session address in a file in ~/.dbus/session-bus. The name of the file is $machine_id-$display_number, where $machine_id is a randomly generated ...


You could either try using user:live as username:password combination or adding live-config to the boot options (as suggested here: ) which should log you in automatically.


The following has been copied verbatim from an answer that @Luke posted on Ask Ubuntu. I am posting it as a community wiki answer so the information can be on this site as well. KDE has not built this into its control center yet, but you can use xinput from the command line. First, run xinput list to find the device number of your mouse: $ xinput list ⎡ ...


Have a look at the file $HOME/.local/share/applications/defaults.list There is a section [Default Applications] to specify the programs for particular mime types. You can add for example: application/x-debian-package=gdebi.desktop The .desktop files can be found in /usr/share/applications/ or you can create your own files under $HOME/.local/share/...


try kwin --replace or DISPLAY=:0 kwin --replace if you're not in X. Source


This (and much much more) can be done in advanced settings of KDE's window manager KWin. You can get to it if you right click on window titlebar and select Advanced > Special Application Settings (or Special Window Settings if you would like to apply only to specific window and not all windows of this app). Then on the Size and Position tab you can force it ...


In KDE 4.11 (but should work for previous versions too) Go to: settings -> configure -> Appearance -> layout -> check "show message preview panel next to the message list"


(I am looking into the relation of GNOME and X. I'd like to share some of my understandings. I will present it in a logical way as much as I can.) 1. What is GUI composed of? Below is an illustration of the basic components of a GUI. The key component is the display server. There are several display servers available. Such as: X11 (mostly for *nix) ...


First, LIBGL_ALWAYS_INDIRECT is a flag related to the Mesa 3D client-side OpenGL implementation ( It won't work with binary drivers from other vendors (e.g. NVIDIA). Second, to answer your question directly, last I looked at the Mesa code the flag works like this: Pre ~2008 when Mesa was working with an indirect X server (e.g. you did ssh -X or ...


openSUSE is a quite KDE centric Linux distribution. See more in this wiki entry:


That dot is to stick window visible on all workspaces.


As implied here, edit ~/.config/kwinrc, adding the following lines to the bottom. [ModifierOnlyShortcuts] Meta= Then restart kwin with kwin_x11 --replace & disown.


You can just remove the wallet instead. Next time a new password will be asked. cd $(kde4-config --localprefix)share/apps/kwallet mv kdewallet.kwl kdewallet.kwl.bak (if your wallet is called kdewallet.kwl)


This information is documented in the okular documentation. As alxs mentioned, a method supported for a while now is to save the PDF document as an archive, which creates a .okular file. Saving the annotations directly in the PDF is quite recent, and from the documentation this option is only available from version 0.15. With such a recent version, using ...


Go to System Settings → Window Behaviour → Window Rules. Click on the ‘New…’ button. Add a description like ‘maximise everything on start’. Go to the ‘Size & Position’ tab, then enable the checkboxes for ‘Maximised horizontally’ and ‘Maximised vertically’. For each of them, set the drop-down to ‘Apply Initially’, and the radio button to ‘Yes’. Click ‘OK’,...


EDIT: I just got tapping working on my Debian AlpsPS/2 touichpad with synclient: synclient TapButton1=1 I am not an expert on this but found an old synaptics.conf file that I was using on a different laptop: Section "InputClass" Identifier "touchpad catchall" MatchIsTouchpad "on" MatchDevicePath "/dev/input/event*" Option "...


You can either Specify the display to be used on the command line, by adding -display :0.0 or Set up the environment variable in root's login script (one of .bashrc, .profile, .bash_profile ...). export DISPLAY=:0.0 You can check whether it's set, $ env |grep DISPLAY DISPLAY=:0.0 To open up your display for all users from all hosts as your normal ...


At least from Meld 3.16.4 support different color schemes. See Meld > Preferences: (possibly this change was introduced in earlier versions) Note: It is also possible to force a specific theme for Meld by CLI: GTK_THEME=Adwaita:dark meld


Power management -> advanced settings -> Lock screen on resume. EDIT: In new Plasma vesrions, it's in System settings -> Desktop Behaviour -> Screen locking. Quick tip: In the systemsettings screen, there is an useful dialong in which you can search for "lock", it'll highlight the relevant icons.


Since plasma5's modularization the config files are not saved in a single folder anymore. You will find different files in ~/.config (typically ending with .rc) and some other parts in ~/.local (e.g. plasma themes). The plasmoids are saved in "~/.config/plasma-org.kde.plasma.desktop-appletsrc". It also saves the folder view desktop and the kickoff launcher....


You were bitten by a nasty bug in dash which caused /bin/sh to be removed. This has since been fixed, which is why another apt update and apt full-upgrade fixed it (after restoring /bin/sh to point to bash presumably, your comments aren’t clear about that).


You can define your own table for the Compose key: create a file called .XCompose in your home directory. You'll need to define the whole table (you can't just add your definitions to the system default, you have to copy the system default into your file if you want it). You'll find the system default table in /usr/share/X11/locale/en_US.UTF-8/Compose on ...

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