date
int64
1,220B
1,719B
question_description
stringlengths
28
29.9k
accepted_answer
stringlengths
12
26.4k
question_title
stringlengths
14
159
1,385,836,521,000
I have an application that I start only from the command line. How can I add the command (and preferably a nice logo) to Gnome's application menu?
In GNOME and other freedesktop.org-compliant desktop environments, such as KDE and Unity, applications are added to the desktop's menus or desktop shell via desktop entries, defined in text files with the .desktop extension (referred to as desktop files). The desktop environments construct menus for a user from the combined information extracted from available desktop entries. Desktop files may be created in either of two places: /usr/share/applications/ for desktop entries available to every user in the system ~/.local/share/applications/ for desktop entries available to a single user You might need to restart GNOME for the new added applications to work. Per convention, desktop files should not include spaces or international characters in their name. Each desktop file is split into groups, each starting with the group header in square brackets ([]). Each section contains a number of key, value pairs, separated by an equal sign (=). Below is a sample of desktop file: [Desktop Entry] Type=Application Encoding=UTF-8 Name=Application Name Comment=Application description Icon=/path/to/icon.xpm Exec=/path/to/application/executable Terminal=false Categories=Tags;Describing;Application Explanation [Desktop Entry] the Desktop Entry group header identifies the file as a desktop entry Type the type of the entry, valid values are Application, Link and Directory Encoding the character encoding of the desktop file Name the application name visible in menus or launchers Comment a description of the application used in tooltips Icon the icon shown for the application in menus or launchers Exec the command that is used to start the application from a shell. Terminal whether the application should be run in a terminal, valid values are true or false Categories semi-colon (;) separated list of menu categories in which the entry should be shown Command line arguments in the Exec key can be signified with the following variables: %f a single filename. %F multiple filenames. %u a single URL. %U multiple URLs. %d a single directory. Used in conjunction with %f to locate a file. %D multiple directories. Used in conjunction with %F to locate files. %n a single filename without a path. %N multiple filenames without paths. %k a URI or local filename of the location of the desktop file. %v the name of the Device entry. Note that ~ or environmental variables like $HOME are not expanded within desktop files, so any executables referenced must either be in the $PATH or referenced via their absolute path. A full Desktop Entry Specification is available at the GNOME Dev Center. Launch Scripts If the application to be launched requires certain steps to be done prior to be invoked, you can create a shell script which launches the application, and point the desktop entry to the shell script. Suppose that an application requires to be run from a certain current working directory. Create a launch script in a suitable to location (~/bin/ for instance). The script might look something like the following: #!/bin/bash pushd "/path/to/application/directory" ./application "$@" popd Set the executable bit for the script: $ chmod +x ~/bin/launch-application Then point the Exec key in the desktop entry to the launch script: Exec=/home/user/bin/launch-application
How can I add an application to the GNOME application menu?
1,385,836,521,000
I just added and modified a .desktop file in my /home/user/.local/share/applications folder. Is there any way to refresh the icon and caption in the list of applications without logging out?
You can restart the gnome-shell by pressing Alt+F2 and then typing in either "restart" or just "r" and pressing Enter. Otherwise I've noticed that it automatically refreshes .desktop files after waiting a little while.
How do I refresh Gnome 3 applications
1,385,836,521,000
I love the window snap feature of the Gnome 3 shell. However, it only allows you to maximize windows or to snap to the left or right half of the screen. Is there a way to snap to quarters of the screen? Maybe some shell extension I'm unaware of?
There are several extensions on the GNOME extensions site which can give you various modes of "snapping" your windows. One that works particularly well is gTile.     References Keyboard Shortcuts GNOME 3
Gnome Shell window snap to quarters of screen
1,385,836,521,000
There is no "Lock" option showing up in the user menu, and the standard shortcuts (Ctrl+L or Ctrl+Alt+L) don't do anything. I'm running Fedora 19 with Gnome Shell 3.8.3, and XDM 1.1.11. I'm using XDM because of broken XDMCP support in GDM - but before I upgraded to Fedora 19, I did have the lock option, even when using XDM. I've posted an answer reflecting the results of my own research. It basically says that it's not possible to have screen-lock integrated into Gnome 3.8 without running GDM. I really hope there's a better answer available though - so please add your own answer if there's any way to do this that I overlooked.
After some research, I think I've got enough information to post an answer to my own question. In Gnome Shell 3.6 and earlier, the old gnome-screensaver program was present, and if GDM was not running, gnome-screensaver would be invoked - allowing you to lock the screen. Starting in Gnome Shell 3.8 (included in Fedora 19), gnome-screensaver support has been dropped completely. This was done for three reasons: reduced code complexity coupled with the fact that the screensaver is seen as an unneeded feature, and the fact that the eventual move to Wayland will require screensaver, locking, etc. support to be in the compositor. So the only Gnome-integrated way of locking the screen is to have GDM running, which will respond to a dbus message telling it to lock the screen. Other display managers (such as XDM) have not been designed to respond to this dbus message, and so the screen cannot be locked. From this link: In old versions of gnome the command gnome-screensaver-command -l would lock your screen. As gnome-screensaver is no more in gnome 3.8 you now have to send a dbus call. I think this is then handled by GDM. $ dbus-send --type=method_call --dest=org.gnome.ScreenSaver \ /org/gnome/ScreenSaver org.gnome.ScreenSaver.Lock
How can I lock my screen in Gnome 3 without GDM?
1,385,836,521,000
In Gnome 3, moving windows with the keyboard shortcuts Meta+← and Meta+→ can be convenient. Now, I have two displays installed and would like to move windows across the displays without touching the mouse. More precisely, I would like to see what is the default behavior in Windows 7, namely four locations, left half of first screen, right half of first screen, left half of second screen, right half of second screen. Any solution involving a sequence of multiple shortcuts is also appreciated. Note that I am using only one desktop but multiple displays.
In Fedora 24 (also Ubuntu 20.04, and probably many more distros which use Gnome) the key combination SuperShift← or SuperShift→ moves windows between monitors by default. If you play with Super + Cursor Keys and then use SuperShift + Cursor Keys you should be able to move/minimise/maximise windows with ease.
How to move windows across displays in Gnome 3 with keyboard?
1,385,836,521,000
In Gnome 3.18, it was possible to change the titlebar height of all windows by changing the css in ~/.config/gtk-3.0/gtk.css as per Reduce title bar height in gnome 3 / gtk+ 3. .header-bar.default-decoration { padding-top: 0px; padding-bottom: 0px; } .header-bar.default-decoration .button.titlebutton { padding-top: 0px; padding-bottom: 0px; } /* No line below the title bar */ .ssd .titlebar { border-width: 0; box-shadow: none; } In Gnome 3.20, this appears to no longer apply to windows with a headerbar/CSD (gnome-specific buttons in the title bar), such as Nautilus (Files), Settings, Photos, Contacts, etc. The tweak still reduces the titlebar height for other applications, such as gnome-terminal and gVim. How do I reduce the height of the titlebar in gnome-programs such as Nautilus in Gnome 3.20? Update I have also tried what is suggested in this reddit thread. I tried both window.ssd and .ssd only, no dice. This works, see the answer I posted for more details window.ssd headerbar.titlebar { padding-top: 1px; padding-bottom: 1px; min-height: 0; } window.ssd headerbar.titlebar button.titlebutton { padding-top: 1px; padding-bottom: 1px; min-height: 0; } and /* shrink headebars */ headerbar { min-height: 38px; padding-left: 2px; /* same as childrens vertical margins for nicer proportions */ padding-right: 2px; } headerbar entry, headerbar spinbutton, headerbar button, headerbar separator { margin-top: 2px; /* same as headerbar side padding for nicer proportions */ margin-bottom: 2px; } /* shrink ssd titlebars */ .default-decoration { min-height: 0; /* let the entry and button drive the titlebar size */ padding: 2px } .default-decoration .titlebutton { min-height: 26px; /* tweak these two props to reduce button size */ min-width: 26px; }
Note: If you are on PopOS, there is an option to "Remove Window Titles" in the top bar menu that also controls tiling. This is what I use currently myself and it works great for only removing the superfluous non-CSD titlebars. Headerbar/CSD Actually, a section of the code that I found via reddit and posted above, namely headerbar entry, headerbar spinbutton, headerbar button, headerbar separator { margin-top: 2px; /* same as headerbar side padding for nicer proportions */ margin-bottom: 2px; } DOES modify the headerbars/CSDs. However the effect is not immediate. Even if you reload gnome, you might need to close all windows, wait a while, or log out and log back in again to see the effect. I am still not seeing any difference in the header bar when modifying the following. headerbar { min-height: 38px; padding-left: 2px; /* same as children's vertical margins for nicer proportions */ padding-right: 2px; } Standard titlebar The two sections for the normal window titlebars work as expected. .default-decoration { min-height: 0; /* let the entry and button drive the titlebar size */ padding: 2px } .default-decoration .titlebutton { min-height: 26px; /* tweak these two props to reduce button size */ min-width: 26px; } Titlebar border You can use the following to remove the titlebar border if you are running the default adwaita theme. From https://bbs.archlinux.org/viewtopic.php?id=211102 window.ssd headerbar.titlebar { border: none; background-image: linear-gradient(to bottom, shade(@theme_bg_color, 1.05), shade(@theme_bg_color, 0.99)); box-shadow: inset 0 1px shade(@theme_bg_color, 1.4); }
How to change the titlebar height in standard GTK apps and those with headerbars/CSDs on Gnome 3.20
1,385,836,521,000
I run gnome shell 3.6 and Eclipse 4.2. I installed Eclipse manually, in my /opt directory, because the Ubuntu package for Eclipse is very outdated. I've created a .desktop file for it, and placed in in ~/.local/share/applications. It looks like this: [Desktop Entry] Type=Application Name=Eclipse Comment=Eclipse Integrated Development Environment Icon=/opt/eclipse-4.2.1/icon.xpm Exec=/opt/eclipse-4.2.1/eclipse Terminal=false Categories=Development;IDE;Java; I can run Eclipse from the Activities menu; if I hit the super menu and type in "Eclipse" and run it, it starts just fine, and shows up in my launcher/sidebar/dock/whatever it's called. But if I right-click on its icon, there is no "Add to favorites" option. (I notice this is also the case if I run some very old programs, like xeyes and xcalc. it's amazing these are still distributed!) So what is it about a program that determines whether or not the "Add to favorites" option is available? if I knew and understood that, maybe it'd set me on the right path to fixing this Eclipse problem.
Found the answer elsewhere. The .desktop file needs to be named EXACTLY the same as the binary that's launching. Mine was something like eclipse_ide.desktop and the binary that runs is just "eclipse". Gnome shell does not seem to like that.
How do I add eclipse to my gnome shell favorites?
1,385,836,521,000
I noticed that some applications use the Adwaita Dark theme, while others use the light one. Is there a way to make all applications use the Dark one?
Replacing the main theme with the dark one in /usr/share/themes is not an ideal solution as each time gnome-themes is updated your theme will revert to default. It's preferable to properly configure your user account to use the dark theme, that way your settings will be preserved between updates. You can do that: Manually: create (open if already present) the following file: ~/.config/gtk-3.0/settings.ini edit like this: [Settings] gtk-application-prefer-dark-theme=1 Via gnome-tweak-tool (which essentially does the same thing as above, writing the same file): GTK2 Problem This answer is indeed the ideal and "safe" (i.e no need to replace/mod any system files) method. However, currently neither this method nor Jeff's answer works for all apps. Coz only GNOME3/GTK3 has support for the dark theme mode. As of now, there are still many apps (for example those written in GNOME2/GTK2, Qt, wxWidgets, Java, etc) which don't use GTK3 and remain on the old GTK2 theming. To make those apps dark, replacing/modding the GTK2 part($ACTIVE_THEME/gtk-2.0/gtkrc) of the currently active theme works. To know more, see the answer to "Firefox not affected by gtk theme". As GTK2 is deprecated and superseded by GTK3, all actively developed GTK2 apps are getting ported to or replaced by GTK3. Sooner or later, other toolkits like Qt, wxWidgets, etc may also implement support for GTK3. By that time, this method may become valid for all(maybe almost all) apps.
How can I use Adwaita Dark for all applications in Gnome 3?
1,385,836,521,000
GNOME 3 is not compatible with Compiz, so I cannot use the desktop zoom feature from Compiz. I googled for a long time, and it seems GNOME still does not support desktop zoom -- does it? I am using GNOME 3.2.1
To answer my own question... The Gnome3 has a zoom feature in the accessibility menu. Thanks to @fheub. If you want to use shortcut key, you can edit the shortcut key in the keyboard system settings. But my point is: the zoom feature in accessibility menu is designed for people with vision problem. Has the Gnome developer ever realize everyone may want/need such a feature regardless of the condition of their eyes? By setting the shortcut key, it is literally means the the key on your keyboard, not including your mouse. But with Compiz, I can use the mod-key + mouse scroll wheel to zoom in/out. Much more convenient.
Does GNOME 3 support desktop zoom?
1,385,836,521,000
On my Debian system I've customized my Gnome (Shell) keyboard shortcuts, via System Settings > Keyboard > Shortcuts. Where do I find the file with these settings so that I can copy the file onto a flash drive for backup and then use it to replace the keyboard shortcuts on other Gnome systems?
Gnome 3 uses DCONF to store the preferences in a single binary file: ~/.config/dconf/user. As per the Gnome docs, it is recommended to save only the settings that you need and restore them with either dconf or gsettings. However, gsettings is only able to restore the value(s) for one single key at a time (plus, the value must be quoted) and that makes it a bit awkward for this kind of task. Which leaves us with dconf. So, in this particular case, save the current settings for gnome-shell keyboard shortcuts1: dconf dump /org/gnome/shell/keybindings/ > bkp Here's a bkp sample: [/] toggle-message-tray=['<Super>m'] open-application-menu=['<Super>F1'] toggle-application-view=['<Control>F1'] focus-active-notification=['<Super>n'] toggle-recording=['<Control><Shift><Alt>r'] Load the settings on another system: dconf load /org/gnome/shell/keybindings/ < bkp 1: WM and Media Keys shortcuts belong to different schemas: /org/gnome/desktop/wm/keybindings/ /org/gnome/mutter/keybindings/ /org/gnome/mutter/wayland/keybindings/ /org/gnome/settings-daemon/plugins/media-keys/ Note that dconf only dumps non-default values so if you run e.g. dconf dump /org/gnome/desktop/wm/keybindings/ and don't get any output that means there's no custom WM shortcut defined. As a side note, dconf-editor is a tool that helps visualizing dconf settings structure, i.e. schema [:path] key value, the type and the default values of any key etc. For the record, saving the preferences with gsettings: gsettings list-recursively org.gnome.shell.keybindings > bkp bkp sample: org.gnome.shell.keybindings focus-active-notification ['<Super>n'] org.gnome.shell.keybindings open-application-menu ['<Super>F1'] org.gnome.shell.keybindings toggle-application-view ['<Super>a'] org.gnome.shell.keybindings toggle-message-tray ['<Super>m'] org.gnome.shell.keybindings toggle-recording ['<Control><Shift><Alt>r'] Now loading the preferences (as I said, for each line in the backup file you need a separate command and don't forget to quote the values): gsettings set org.gnome.shell.keybindings focus-active-notification "['<Super>n']" gsettings set org.gnome.shell.keybindings open-application-menu "['<Super>F1']" gsettings set org.gnome.shell.keybindings toggle-application-view "['<Super>a']" gsettings set org.gnome.shell.keybindings toggle-message-tray "['<Super>m']" gsettings set org.gnome.shell.keybindings toggle-recording "['<Control><Shift><Alt>r']"
Save custom keyboard shortcuts in Gnome
1,385,836,521,000
GNOME 2 allows one to either save the session automatically or manually (i.e. save the session as it looks right now). This is a nice feature because it restores the various desktop states between logins (and system restarts): which apps were open where (physically) on the desktop were they open what specific window sizes were these apps set to Looking around, I can't find the feature in GNOME 3? Did I not look hard enough?
Normally you would Alt-F2 to run gnome-session-properties, and select "Automatically remember running applications when logging out" under the Options tab. However, it is broken at the moment. There is a bug filed: https://bugzilla.gnome.org/show_bug.cgi?id=647359
How to save a GNOME 3 session
1,385,836,521,000
I am using GNOME 3.18.1 on Arch Linux 4.2.5-1-ARCH x86_64 on a Dell E6530 laptop. Since I installed this OS years ago, the power button on my laptop has always led my OS to completely power down. However, in the last few weeks this behaviour has changed, so that pressing the power button now puts my laptop into energy savings mode. I did not change my power settings. I always keep my system up to date using pacman -Syyu, however, so I suspect that an update changed this functionality. In the power settings there is no option for this. How can I restore the initial behaviour, so that pressing that button powers the system off?
That's caused by the latest gnome-settings-daemon updates... There is no such option in power settings because it was removed by the GNOME devs (the shutdown/power off action is considered "too destructive"). Bottom line: you can no longer power off your laptop by pressing the power off button. You could however add a new dconf/gsettings option (i.e.shutdown) to the settings daemon power plugin if you're willing to patch and rebuild gnome-settings-daemon: --- gnome-settings-daemon-3.18.2/data/gsd-enums.h 2015-11-10 09:07:12.000000000 -0500 +++ gnome-settings-daemon-3.18.2/data/gsd-enums.h 2015-11-11 18:43:43.240794875 -0500 @@ -114,7 +114,8 @@ { GSD_POWER_BUTTON_ACTION_NOTHING, GSD_POWER_BUTTON_ACTION_SUSPEND, - GSD_POWER_BUTTON_ACTION_HIBERNATE + GSD_POWER_BUTTON_ACTION_HIBERNATE, + GSD_POWER_BUTTON_ACTION_SHUTDOWN } GsdPowerButtonActionType; typedef enum --- gnome-settings-daemon-3.18.2/plugins/media-keys/gsd-media-keys-manager.c 2015-11-10 09:07:12.000000000 -0500 +++ gnome-settings-daemon-3.18.2/plugins/media-keys/gsd-media-keys-manager.c 2015-11-11 18:47:52.388602012 -0500 @@ -1849,6 +1849,9 @@ action_type = g_settings_get_enum (manager->priv->power_settings, "power-button-action"); switch (action_type) { + case GSD_POWER_BUTTON_ACTION_SHUTDOWN: + do_config_power_action (manager, GSD_POWER_ACTION_SHUTDOWN, in_lock_screen); + break; case GSD_POWER_BUTTON_ACTION_SUSPEND: do_config_power_action (manager, GSD_POWER_ACTION_SUSPEND, in_lock_screen); break; Once you install the patched version, a new shutdown option will be available in dconf-editor under org > gnome > settings-daemon > plugins > power > power-button-action: so select that to shutdown via power button or, if you prefer CLI, run in terminal: gsettings set org.gnome.settings-daemon.plugins.power power-button-action shutdown Sure, for the above to work you also need the right settings in /etc/systemd/logind.conf: HandlePowerKey=poweroff PowerKeyIgnoreInhibited=yes Keep in mind that pressing the power button will shutdown your system without any warning.
How to set power button to shutdown instead of suspend?
1,385,836,521,000
There are certain gsettings keys that can have multiple values (e.g. a key like verbosity could be assigned to one error, info, or debug). I want to be able to list them, but my dconf-editor (0.7.3) can't view them. Is there an existing alternative?
The newer version of dconf-editor now lists the options. In this example, if you click on debug, you'll see a list of other available values. This screenshot is of version 0.10 of the tool. A screenshoot from v0.19.3, shows options:
How do I browse for available gsettings options?
1,385,836,521,000
After the latest upgrade on Debian stretch, hitting alt+shift on my keyboard make it change layout, which breaks all my alt+shift+<anything> xbindkeys shortcuts. I have disabled all shortcuts in Settings -> Keyboard -> Input. Still the same. In Settings -> Languages, it is said that this alt+shift behaviour can be tweaked in.. Settings -> Keyboard. But alt+shift seems to be set nowhere there. Is it hardcoded? Is there a way xbindkeys can work around this?
Okay, got it: this line in my /etc/default/keyboard XKBOPTIONS="grp:alt_shift_toggle,grp_led:scroll" .. should not contain grp:alt_shift_toggle, which is the relevant xkb option according to this post. In addition, Gnome overrides xkb options according to this other post. As a consequence, this output: $ dconf read /org/gnome/desktop/input-sources/xkb-options ['grp:alt_shift_toggle','grp_led:scroll'] .. should not read grp:alt_shift_toggle on my machine either. So after I ran: dconf write /org/gnome/desktop/input-sources/xkb-options "['grp_led:scroll']" I got my good'ol behaviour back ;) I have filed this as a bug to Gnome.
Gnome 3.22: disable alt+shift keyboard layout switching
1,385,836,521,000
I used to be able to connect to my Gnome 3 desktop from a Windows machine with a VNC client. But after an upgrade (on the Linux side) a while ago, it quit working. When I attempt to connect, all I can get is a message saying "No matching security types" or "No supported authentication methods!" (depending on which client I try). In Gnome 3, I've turned on Screen Sharing under Settings > Sharing. Under that, I have Remote View on, Remote Control on, Approve All Connections on, Require Password off. I'm running Arch Linux with vino 3.8.1. On the Windows side, I've tried TigerVNC 1.0.1 & 1.2.0 and UltraVNC 1.0.9.6.2. How can I get this working?
This is actually a known and currently open bug. However, there is a very easy workaround; just issue the following command: gsettings set org.gnome.Vino require-encryption false You will now be able to connect with most vnc viewers.
How can I connect to Gnome 3 with a Windows VNC client?
1,385,836,521,000
When I install shutter to take screenshots, imagemagick sets itself as default PDF-reader and I am unable to change it. I would like to have evince as default PDF-reader. I have tried right click on a PDF document in file explorer-> Properties -> Set default application-> Evince. This does not work, imagemagick stays as default. Doing this with the file explorer opened as root works but it doesn't change the normal-user default application. Using xdg-mime does not help either. In /etc/gnome/defaults.list the default application for PDF is evince. And, when I remove imagemagick-6.q16, evince becomes the default application for opening PDFs, but shutter is removed too. Am I missing something ? Where can I change this behavior ? I have an updated version of Debian Jessie in my computer and I am using Gnome3. EDIT 1: I can replicate this behavior with different file explorers (tested with nemo and nautilus) The output of XDG_UTILS_DEBUG_LEVEL=2 xdg-mime query default application/x-pdf is Checking /home/USER/.local/share//applications/mimeapps.list Checking /usr/share/gnome/applications/defaults.list Checking /usr/local/share//applications/defaults.list Checking /usr/share//applications/defaults.list I've checked this files: In /home/USER/.local/share//applications/mimeapps.list I have a line with application/pdf=evince.desktop In /usr/share/gnome/applications/defaults.list the PDF reader is set to evince too. In /usr/local/share/applications/defaults.list there is no reference to PDFs. /usr/share/applications/defaults.list does not exist
Edit the: ~/.config/mimeapps.list, and add the line: application/pdf=evince.desktop to the [Default Applications] section. If a line for application/pdf already exists, change it instead of adding a new one. Source: This answer on AskUbuntu.
Set default pdf reader
1,385,836,521,000
Gnome Shell 3.18.5 notified me some extensions needed updating. I visited https://extensions.gnome.org/local/ from Firefox, updated the Firefox extension, and now I want to uninstall some of the Gnome extensions, for example the following one. Removable Drive Menu by fmuellner System extension A status menu for accessing and unmounting removable devices. Hovering the mouse on System extension, I read the following tooltip. System extension should be uninstalled using package manager. See about page for details. The About page says: What is System extension? How to uninstall it? System extension is installed to system-wide location (usually /usr/share/gnome-shell/extensions). Such extension may be used by any PC user, however it can be uninstalled only by system administrator (root). To uninstall system extension use your distro's package manager or ask your system administrator. I looked through Synaptic but don't see this extension. How do I remove it? These are the extensions I want to remove. Applications Menu Places Status Indicator Removable Drive Menu Workspace Indicator Pomodoro
Launch gnome-tweak-tool Search "Extensions" in right menù Select the extension and click on "Remove"
Can't uninstall Gnome Shell Extension
1,385,836,521,000
Since I installed EasyTag on my Arch Linux several other programs use EasyTag instead of Nautilus as filebrowser. For example, Firefox starts EasyTag if I click on "open containing folder". Where can I set Nautilus as my "standard file browser"?
You can define the default file browser by editing the file ~/.local/share/applications/mimeapps.list. Open this file and change the line inode/directory as follow inode/directory=nautilus.desktop; If this doesn't work, you should change the filemanager in the file /usr/share/applications/mimeinfo.cache by adding (or updating) this line inode/directory=nautilus.desktop
Set standard file browser for "open containing folder"
1,385,836,521,000
I'm running Fedora 19 (GNOME Shell 3.8.4). I have a dual monitor setup (two 1440 x 900), and I want to be able to stretch my wallpaper over the two monitors, like I was used to when using Ubuntu 12.04. I don't want different wallpapers for each workspace, nor different wallpapers for each monitor (that would be pretty cool, but falls out of scope of the question). What I want is a 2880 x 900 (or any 3.2:1 proportional image) to be shown half on one monitor, and half on the other: How I had set it on Ubuntu If I boot with my 12.04 LiveUSB, it starts in "mirror displays" mode. I have to disable display mirroring (enable extended monitors) in order to have different images on each screen: Then, I open the System Settings and on the Appearance section I can choose the background, and have several options. Chosing "span" (see the dialog on first image rightmost side) will have the background like I want it to be. How I (don't) have it on Fedora The System Setting screen doesn't have an "Appearance" icon, just a "Background" one, with no options at all. If I choose an image, it will be applied to each monitor repeatedly, like this:
Installing gnome-tweak-tool lets you customize not only the wallpaper alignment, but other absent options such as enabling / disabling minimize and maximize buttons, showing icons on the desktop, changing the shell theme and colors, changing fonts and its options (size, hinting, etc).
Wallpaper stretching over multiple monitors on Fedora 19 (Gnome 3)
1,385,836,521,000
I'm using Arch Linux + GNOME3 on desktop, and when the system starts or the user logs out, gdm displays the login screen for about 20 seconds and then turns off the display (although the computer is still running). Is it possible to disable this? I want the monitor to keep displaying the login screen "forever". I couldn't find any way to configure this.
That's because of the idle-delay setting. To change it you'll have to alter the corresponding dconf key (and do that as the gdm user): switch to a VT (e.g. Ctrl+Alt+F3), login as root and run: su - gdm -s /bin/sh to switch user to gdm. then run: export $(dbus-launch) and set idle delay to 0 (which translates to never): GSETTINGS_BACKEND=dconf gsettings set org.gnome.desktop.session idle-delay 0 run exit or hit Ctrl+D to return to root account. reboot your machine or restart the display manager: systemctl restart gdm
Disable GDM suspend on lock screen
1,385,836,521,000
I've created my own custom locales and placed them in /etc/locale.conf which successfully takes effect if I log in on a virtual console (Ctrl+Alt+F2). In my Gnome3 session those variables are not set, though. For terminal applications I could just place them in the .bashrc but that won't help me with graphical applications like Thunderbird and Pidgin. I have tried to follow these hints: Locale settings in shell initialization not used by GNOME session and even emulated the bug in Locale - ArchWiki by creating a .pam_environment file, but the locales are still those set by Gnome3. There is a configuration dialogue in the Gnome settings but it only allows to set a very limited set of predefined locale combinations and no way to customize them. The relevant files in my home directory: user@localhost:~$ ls -lah .dmrc .pam_environment .session .xsession .xsessionrc lrwxrwxrwx. 1 user user 16 12. Jun 08:57 .dmrc -> /etc/locale.conf lrwxrwxrwx. 1 user user 16 11. Jun 20:23 .pam_environment -> /etc/locale.conf lrwxrwxrwx. 1 user user 16 12. Jun 09:09 .session -> /etc/locale.conf lrwxrwxrwx. 1 user user 16 12. Jun 09:07 .xsession -> /etc/locale.conf lrwxrwxrwx. 1 user user 9 13. Jun 11:22 .xsessionrc -> .xsession -rw-rw-r--. 1 user user 66 13. Jun 11:13 .profile user@localhost:~$ cat .profile source /etc/locale.conf The contents of /etc/locale.conf: LANG="en_US.utf8" LC_TIME="de_MY.utf8" # NB: de_MY LC_MONETARY="de_DE.utf8" LC_PAPER="de_DE.utf8" LC_NAME="de_DE.utf8" LC_ADDRESS="de_DE.utf8" LC_TELEPHONE="de_DE.utf8" LC_MEASUREMENT="de_DE.utf8" LC_IDENTIFICATION="de_DE.utf8" Does anyone know how to set custom locales in Gnome3 ?
Background Information I tested the solution on Fedora 21 with GNOME Shell 3.14.4, but I believe it can be applied to other versions as well. First thing to understand is that GNOME desktop environment overrides the system-wide locale definitions and thus is not affected by /etc/locale.conf. In addition, there are might be applications that have their own locale configuration and don't use the system or GNOME settings at all. In this guide I will describe a way to customize the locale settings to your needs and GNOME and the system will be consistent from the locale perspective. Checking Current Locale Status System-wide Settings From Fedora 21 System Administrator's Guide: System-wide locale settings are stored in the /etc/locale.conf file, which is read at early boot by the systemd daemon. The locale settings configured in /etc/locale.conf are inherited by every service or user, unless individual programs or individual users override them. To see the current locale status we can run: $ localectl status System Locale: LANG=en_US.UTF-8 LC_NUMERIC=en_US.UTF-8 LC_TIME=en_US.UTF-8 LC_MONETARY=en_US.UTF-8 LC_PAPER=en_US.UTF-8 LC_MEASUREMENT=en_US.UTF-8 VC Keymap: us X11 Layout: us GNOME Settings $ gsettings get org.gnome.system.locale region 'en_US.UTF-8' GNOME has only one setting. By giving a quick look at the source code of gnome-control-center it seems that when the set_localed_locale() function is called, it sets all the following categories (LC_TIME, LC_NUMERIC, LC_MONETARY, LC_MEASUREMENT, LC_PAPER) to the same one locale defined in org.gnome.system.locale region. Mixing different locale settings seems impossible without creating a custom locale, but fortunately it's not a very complex task. Creating Custom Locale I think the easiest way to explain is by example. In my specific case I wanted to have a custom locale, primarily based on Hebrew (he_IL) but with LC_NAME, LC_MESSAGES from en_US and LC_TIME (with modified first_weekday and first_workday) from en_GB. Grabbing Locale Definition Files You should have an idea which locales you want to mix. First we need to locate the related definition files, which can be found in /usr/share/i18n/locales/. Back to my example, I needed the following: he_IL, en_US and en_GB. I set up a working folder in my home and copied the required files into it: $ cd /usr/share/i18n/locales $ mkdir -v ~/custom-locale ; cp -v he_IL en_US en_GB ~/custom-locale/ Creating a New Definition File I decided to call my locale hc_IL and took he_IL as a basis. The following lines create a new file hc_IL with the contents from he_IL and on the way replace all the occurrences of a string he_IL inside the file with hc_IL. $ cd ~/custom-locale/ $ sed 's/he_IL/hc_IL/g' he_IL > hc_IL Modifying the New Definition File Now we can customize the new locale to our needs. Open the newly created file ~/custom-locale/hc_IL with your favorite text editor. I use vim (it has proper syntax highlighting for locale definition files): $ vim ~/custom-locale/hc_IL For those who haven't chosen their favorite editor yet and vim is not their cup of tea, can use gedit :) $ gedit ~/custom-locale/hc_IL The file structure is not very complicated. Essentially, it is constructed from sections. From locale(5) man pages: The locale definition has one part for each locale category. Each part can be copied from another existing locale or can be defined from scratch. If the category should be copied, the only valid keyword in the definition is copy followed by the name of the locale which should be copied. The notion of copy is very useful. It saves time and the resulting file is clear and concise. For example, instead of copying entire sections around, you can have: LC_MESSAGES copy "en_US" END LC_MESSAGES The complete documentation on a locale definition file can be accessed via: $ man 5 locale Although, if you just want to create a custom locale, which is a mix of existing ones there's no need to understand every detail. In my case I modified the following categories and keywords: LC_IDENTIFICATION title "Custom Hebrew locale" source "mydomain.ws" address "http:////www.mydomain.ws" contact "" email "[email protected]" tel "" fax "" language "Hebrew" territory "Israel" revision "1.0" date "2015-04-21" Note: All the "category.." lines in the LC_IDENTIFICATION section have been modified during the file creation using sed. So we don't need to touch them anymore. LC_TIME I copied the complete section from en_GB and modified only the lines that indicate the first day of week and the first work day: first_weekday 1 first_workday 1 The rest of the categories I left as they are or replaced their content with the copy directive as in: LC_NAME copy "en_US" END LC_NAME That's it, the definition file is ready. Don't forget to save the file :) Compile and Copy the New Locale Compilation of the new locale is done using the following command as root or using sudo. Replace hc_IL with your locale: $ sudo localedef -c -v -i hc_IL -f UTF-8 hc_IL.UTF-8 If the compilation is successful the compiled locale data is added to the archive file /usr/lib/locale/locale-archive. Copy the new locale definition file to the locale definitions directory. Replace hc_IL with your locale: $ sudo cp -v hc_IL /usr/share/i18n/locales/ Activating the New Locale In this step we want to configure the system and GNOME to use the new locale. System-wide Settings Edit the /etc/locale.conf file as root and set every line that starts with LC_ to your new locale. For example: LANG=en_US.UTF-8 LC_NUMERIC=hc_IL.utf8 LC_TIME=hc_IL.utf8 LC_MONETARY=hc_IL.utf8 LC_PAPER=hc_IL.utf8 LC_MEASUREMENT=hc_IL.utf8 GNOME Settings To activate the new locale in GNOME run the following command. Replace hc_IL with your locale: $ gsettings set org.gnome.system.locale region "hc_IL.utf8" Validating the New Settings The last step is to validate that everything works as expected. To reload all the settings the easiest for me was to reboot. Refer to the section "Checking Current Locale Status" to check that the system configuration is correct. Use GNOME Shell and locale dependent applications (graphical and console) and check that they behave as expected with the new locale. E.g. if you customized LC_TIME you can run the date command to validate the date format: $ date +%x 21/04/15 Note: Everything was tested on Fedora 21 with GNOME 3.14. Other Linux distributions may require additional or different steps. Please comment if you find any issues with the instructions.
Set custom locales in Gnome3 (on Fedora 20)
1,385,836,521,000
I have a Lenovo Thinkpad T420 with Linux Mint 12 and gnome-shell on it. Its a Intel HD 3000 Graphics card in there. When I'm at home, I have another Screen plugged in (19" 4:3) and everything works fine (Extended Desktop), except that I would like to have the Gnome 3 Bars + Shell on the right screen. Can't figure out how to do it. Thanks in advance
Open the System Settings > Displays control applet. It's not evident - at all - but you can drag the miniature of the top black panel onto the display you want to mark as primary. Panels, activity overlay and everything will migrate on that display.
Linux Mint - Gnome Shell with dual monitor switch main screen
1,385,836,521,000
I am running Linux Mint 18.3 with Gnome 3.18 as my desktop. I have been building a loading screen for an application I have installed (Mycroft AI). I have the animation, I have it pop up on loading, i have it closing as soon as it finishes loading. What I DO NOT have is a loading screen with no title bar (what I have is in the screen shot below). As you can see, i still have the title bar. How do I remove it? The fewer apps I have to install to get this to work, the better. Thanks in advance!
Title bars / window decorations are usually specific to the window manager in use. GNOME doesn't support a built-in method to launch a window/program without decorations, unlike window managers such as Openbox. A solution that works within GTK across any window manager is to use GTK's gtk_window_set_decorated(), with more information here.
How to hide title bar for a specific window?
1,385,836,521,000
I am using a freshly installed Ubuntu-Gnome 16.04, and I want to set caps-lock to change keyboard layout (single key, not key combination). I used to have this Linux-mint, and I grew used to it. I looked into the setting manager, but there is doesn't accept caps-lock as a valid input. I also looked int gnome-tweak-tools but there I can't find the keyboard layout switching at all. Is this possible? how?
You could set the corresponding xkb option via dconf-editor. Navigate to org > gnome > desktop > input-sources and add grp:caps_toggle to your xkb-options: Note each option is enclosed in single quotes, options are separated by comma+space. On older gnome3 releases you could do that also via System Settings > Keyboard (or gnome-control-center keyboard in terminal) > Typing > Modifiers-only switch to next source to Caps Lock This was removed from recent releases (see sanmai's answer for alternatives to dconf-editor).
How to allow for caps-lock keyboard layout change
1,385,836,521,000
I'm trying to associate a custom application to a file type in GNOME 3 (FC15). In GNOME 2 one could go in the "Open with" pane of the file properties dialog and add a custom command there. The custom command edit box seems to have disappeared from the "Open with" pane in GNOME 3, so I was wondering if there is some workaround to manually assign the application. In other words, from which file/directory does GNOME pull out that application list? How do I add a custom one?
There is the answer: http://forums.fedoraforum.org/showthread.php?t=263501 I have Gnome3 and there is "Open with" pane :) You also go to proporties and there is "Open with" tab. Edit: You should look on https://bbs.archlinux.org/viewtopic.php?id=118966. Your applications should show on list, if you add a *.desktop file associated with your application to /usr/share/applications or ~.local/share/applications/ directory. Exec should like this: Exec=yourprogram %U
Default applications (GNOME 3)
1,385,836,521,000
I'm having trouble understanding the intended way of managing Gnome shell extensions. I can't find any appropriate programs in the Dash for doing that. The only way I can actually manage extensions is via extensions.gnome.org. It's impossible that this page is supposed to be the tool for managing extensions - it makes absolutely zero sense (it breaks UX, for one). Please tell me that there is a plan for a native application aimed at managing these handy extensions.
It's impossible that this page is supposed to be the tool for managing extensions - it makes absolutely zero sense Whether it makes sense or not is also a matter of opinion. But yes, that page is the main tool, read Owen Taylor's explanation. As to managing the extensions already installed on your system, you can enable/disable them via gnome-tweak-tool (or dconf-editor - GUI, or gsettings - CLI). edit: In reply to your comment: I was talking about keeping the UX consistent. When I type "exten" into the search bar, I should be able to get to some extension control point. What version of gnome-shell are you using ? On gnome-3.8.2 that is the default behaviour, typing exten in the search bar brings up gnome-tweak-tool i.e. the "local control center" for extensions, see for yourself:
How are Gnome shell extensions supposed to be managed?
1,385,836,521,000
I sometimes run into software that is not offered in .deb or .rpm but only as an executable. For example Visual Studio Code, WebStorm or Kerbal Space Programm. For this question, I will take Visual Studio Code as the point of reference. The software is offered as a zipped package. When unzipping, I'm left with a folder called VSCode-linux-x64 that contains a executable named Code. I can double click Code or point to it with my terminal like /home/user/Downloads/VSCode-linux-x64/Code to execute it. However, I would like to know if there is a proper way to install this applications. What I want to achieve is: one place where I can put all the applications/softwares that are offered in this manner (executables) terminal support (that means for example: I can write vscode from any folder in my terminal and it will automatically execute Visual Studio Code. Additional info: Desktop Environment: Gnome3 OS: Debian EDIT: I decided to give @kba the answer because his approach works better with my backup solution and besides that. Having script executing the binaries gives you the possibility to add arguments. But to be fair, @John WH Smith approach is just as good as @kba's.
To call a program by its name, shells search the directories in the $PATH environment variable. In Debian, the default $PATH for your user should include /home/YOUR-USER-NAME/bin (i.e. ~/bin). First make sure the directory ~/bin exists or create it if it does not: mkdir -p ~/bin You can symlink binaries to that directory to make it available to the shell: mkdir -p ~/bin ln -s /home/user/Downloads/VSCode-linux-x64/Code ~/bin/vscode That will allow you to run vscode on the command line or from a command launcher. Note: You can also copy binaries to the $PATH directories but that can cause problems if they depend on relative paths. In general, though, it's always preferable to properly install software using the means provided by the OS (apt-get, deb packages) or the build tools of a software project. This will ensure that dependent paths (like start scripts, man pages, configurations etc.) are set up correctly. Update: Also reflecting Thomas Dickey's comments and Faheem Mitha's answer what I usually do for software that comes as a tarball with a top-level binary and expects to be run from there: Put it in a sane location (in order of standards-compliance /opt, /usr/local or a folder in your home directory, e.g. ~/build) and create an executable script wrapper in a $PATH location (e.g. /usr/local/bin or ~/bin) that changes to that location and executes the binary: #/bin/sh cd "$HOME/build/directory" exec ./top-level-binary "$@" Since this emulates changing to that directory and executing the binary manually, it makes it easier to debug problems like non-existing relative paths.
How to install executables
1,385,836,521,000
In Network Manager, under the Identity tab, I can enter a username and password for my OpenVPN connection. I can also enter a password for the "User private key". Both password fields have the following options: Store the password only for this user Store the password for all users Ask for this password every time The password is not required If I choose to store the password ("for this user" or "for all users") where is it stored?
Go to the /etc/NetworkManager/system-connections/ directory, here all the connection details are saved. And use the cat command or any text editor as root to view the saved passwords. There should be a security related entry, like [vpn-secrets] or [wifi-security]. [wifi-security] auth-alg=open group= key-mgmt=wpa-psk pairwise= psk=sat004321 For VPN, [vpn-secrets] password=arnab002 The string after psk= is the password. I think it's the same location for all users.
Where does GNOME Network Manager store passwords?
1,385,836,521,000
Double clicking on a word in gnome terminal selects the whole word. Unfortunately, this selection doesn't include colons such that URLs aren't completely selected, e.g. with http://foo.example.org/ only //foo.example.org/ is selected. How do I configure this selection behavior such that complete URLs are selected? See also: How to configure the double click behavior in an X terminal? - the described resources aren't interpreted by Gnome Terminal gnome classic terminal mouse double click selection - the Gnome Shell Terminal profile preference dialog doesn't have this option, anymore
How much is selected on double click can be configured via adding additional character classes to the default set. That means that adding a colon and other special characters that may show up in URLs leads to double click also selecting complete URLs. This can be configured via the gnome config database. For that one has to get the id of the gnome shell profile. To get the default one: puuid=$(gsettings get org.gnome.Terminal.ProfilesList default | tr -d "'") Adding some URL related characters: gsettings set \ org.gnome.Terminal.Legacy.Profile:/org/gnome/terminal/legacy/profiles:/:$puuid/ \ word-char-exceptions '@ms "-=&#:/.?@+~_%;"' Note that: @ms denotes the maybe-string gvariant type the character class syntax matches the regex one, i.e. a-z specifies a range, where -az specified the literal 3 characters. Thus, I have explicitly put the - in the first position History: In classic Gnome Terminal versions, the profile preference dialog contained a field for configuring those additional characters. With Gnome 3, UI experts have removed this option from the dialog because they thought it was too complicated to use, though. The default was also changed after Fedora 21.
Double click selection in Gnome Terminal
1,385,836,521,000
I can't figure out what the icon between my settings and lock-screen icon in Gnome3 is supposed to do. It has two states, locked and unlocked, but it's not the lock screen. When I click it, it toggles its status.
That button locks/unlocks screen orientation on devices that can detect which way they are held - usually touchscreen devices - see Screen orientation section on the gnome wiki touchscreen page: Easy ability to temporarily disable and enable auto-rotation (rotation lock). It was introduced a couple of years ago: Add an orientation lock action button. The icon used is rotation-locked-symbolic and it's counterpart is rotation-allowed-symbolic. They're under /usr/share/icons/Adwaita/scalable/status and they're both part of the symbolic icons set. On some systems with hard disk accelerometers that button appears even if your device doesn't support screen orientation detection. If that's the case you can disable the gnome-settings-daemon plugin via gsettings: gsettings set org.gnome.settings-daemon.plugins.orientation active false
What is the icon between settings and lock-screen in Gnome3?
1,385,836,521,000
I have been banging my head against this for quite a while now. It's related to this question. I would like to find out exactly what happens when I choose to shut down my Linux box from the GUI. This seems to be poorly (if at all) documented. Ideally, I'm hoping for a DE- and OS-agnostic answer. Barring that, I'm interested in the specific case of Mandriva 2010.1 and Debian 6.x (Squeeze) and 7.0 (Wheezy) all running Gnome. (If you're paying close attention, yes that's Gnome 2 and Gnome 3) Basically, I would like to know which command/script/sequence of scripts is started when I press "Shut Down" or "Restart" so I can modify their behavior. Some forum posts I looked at suggest hacking /etc/polkit-1/* but this directory structure is only a skeleton on my Debian (Squeeze) box, for example. Can anyone help? EDIT What I have tried so far Replaced the shutdown executable with a script of my own. This doesn't work: when I press shutdown Gnome logs out without executing my script. Tried editing the Gnome 2 menu. No joy: the "Shutdown", "Log out" and "Lock Screen" options do not appear in the menu editor. Looked at /usr/share/menu, nothing helpful there. Possible avenues for the solution straceing the GUI options (is this even possible?) Looking at shutdown's source code Looking at gnome-session's source code Update As per my comments on the answer below, I have looked into polkit actions under /usr/share/polkit-1/actions/ and found (in the file org.freedesktop.consolekit.policy) an action called org.freedesktop.consolekit.system.stop-multiple-users that throws the message System policy prevents stopping the system when other users are logged in I'm thinking (due to the org.freedesktop.* naming convention) that this is some kind of signal sent to the DM via D-BUS. Moreover, this message appears when trying to shutdown graphically while other users are logged in, so the mechanism that triggers it must be the same mechanism triggered when "Shut Down" or "Power Off" is selected from the GUI. Can anyone confirm/refute? Is there a possibility of somehow intercepting this signal or modifying it?
It depends on your Display Manager! (i.e. KDM, GDM) Please bear in mind your DM runs as root! (it needs root privileges in order to run your session process as the user you log in) When you click shutdown in KDE or GNOME, your DE sends a signal to your DM to power off or restart after the session has terminated. Then, your DE tells every program to end and once all other process has terminated (or expired a timeout), the last process of your DE -- the session process -- terminates. The session process is the first process started in an X11 session. When it's killed or it terminates, the session terminates. Have you ever seen that xterm when running X without DE? That is a session process. This process is called kdeinit in KDE and gnome-session in GNOME. Once the session has terminated, control is returned to your DM (which has been waiting for the X process to end), and it checks what the DE told him to do. If it told it to power off or restart, it will do that. In other case, it will just start a new login screen in X. This is also related with problems you may have had in the past, with some DE not being able to power off or restart, just to log out, when used in combination with some other DMs. In any case, this is not so bad documented. GDM has a manual page "gdm-control(1)" of a command which allows you to tell it to shut down just like I told before (gdm-control). KDM has excellent documentation too and has a similar (a little more complex) utility named kdmctl. Shutdown and restart is possible without PolicyKit, but PolicyKit serves many purposes needed on nowadays systems like mounting disks without being root, suspend or hibernate the computer. And it neither is bad documented! Check out this if you want to know more about what is PolicyKit and how does it work: http://www.freedesktop.org/software/polkit/docs/latest/polkit.8.html
What happens when I press "Shut Down" from the GUI?
1,385,836,521,000
I have a problem with QT applications (i.e. picard or masterpdfeditor) under GNOME: their interface looks tiny. Instead, GTK application looks good. I would like a global solution which will work across all applications, not a per-application fix. I don't know exactly where the issue begin (is it a QT5 issue or a GNOME issue?) but I'd like to have a bigger interface. How can I do it? I have already tried with a trick explained here but it works partially: if I launch the apps directly from the terminal, by appending the right variable e.g. QT_SCALE_FACTOR=1.35 picard, the trick works! while if I launch them from the menu (gnome-shell), the exported variable is completely ignored. Is there a way to fix it? I have a laptop connected with an external FullHD 24" monitor. I'm on Arch Linux x86_64 and Gnome 3.28/3.30.
I had some issues getting Viber to run properly on my HiDPI display. By default Viber would be massive to the point where I had to full-screen it in order to use it. The solution was to disable automatic scaling (QT_AUTO_SCREEN_SCALE_FACTOR=0) and set a manual value (QT_SCALE_FACTOR=1.5). I modified the Exec= line in /usr/share/applications/viber.desktop to this: Exec=/usr/bin/env QT_AUTO_SCREEN_SCALE_FACTOR=0 QT_SCALE_FACTOR=1.5 /usr/bin/viber %u Now it looks perfect. Your mileage may vary based on the size of your display, you might want to set QT_SCALE_FACTOR to 2 or even more. I found it strange that I had to explicitly disable automatic scaling, as most of the answers I've found online says you have to enable it to fix your scaling issues. I guess it has become the default in newer versions of QT (?) (I know this doesn't strictly answer the asked question but I thought it'd be useful to someone.)
Scaling/HiDPI issue for QT5 applications under GNOME
1,385,836,521,000
I recently upgraded my system to GNOME 3. In previous versions of GNOME, the key combination Ctrl+Alt+D would hide all open windows and show the Desktop. This shortcut was eliminated from GNOME 3 along with the concept of a Desktop. The Desktop metaphor does, however, exist in GNOME 3 "fallback mode" (which I am using). I would like to reinstate the Ctrl+Alt+D keyboard shortcut. I know at least two ways of creating key combinations in GNOME. One is through System Settings > Keyboard > Shortcuts, and the other is through gconf-editor > apps > metacity. From either of these environments, I can pair a command with the key combination Ctrl+Alt+D. The problem is that I don't know what command will trigger a "Show Desktop" event. Could someone enlighten me?
System Settings > Keyboard > Shortcuts > Navigation > Hide all normal windows Click the second field which says Disabled and type in a key combination of choice (e.g., Ctrl+Alt+D). System restart may be required for changes to take effect.
GNOME 3 Ctrl+Alt+D (show desktop)
1,385,836,521,000
How can I trigger the screen saver manually from the command line? I'm using GNOME 3.8.4 on Fedora 19, but the solution should not necessarily be specific to this distro.
The details on how to do this were found here in this blog post titled: Locking the screen from the command line in Gnome 3.8. Manually triggering The dbus-send command can be used to send this message, in this case we're sending the "Lock" message to the screensaver. $ dbus-send --type=method_call --dest=org.gnome.ScreenSaver \ /org/gnome/ScreenSaver org.gnome.ScreenSaver.Lock Timeout Typically this same message will be sent when you've configured for this particular timeout to occur through the desktop settings. You can check the amount of idle time required before the locking will automatically get triggered, from the GNOME Control Center, Settings -> Power -> Blank Screen. You can check the value of this delay from the command line like so: $ gsettings get org.gnome.desktop.session idle-delay uint32 600 Also you can change it via the command line, or through the GNOME Control Center. $ gsettings set org.gnome.desktop.session idle-delay 300
How can I trigger the screensaver's locking feature using D-BUS from the command line?
1,385,836,521,000
I recently updated this laptop to Fedora 28 Beta and with it Gnome 3.28. Things are mostly good. But some things are weird. This is not causing problems because this is all virtual memory. But why are these daemons allocating 100+ GB of virtual memory? 0 1000 2012 1719 20 0 101649024 32904 SyS_po Sl ? 0:00 /usr/libexec/goa-daemon 0 1000 1983 1719 20 0 101704260 46416 SyS_po Sl ? 0:00 /usr/libexec/gnome-shell-calendar-server 0 1000 2210 1765 20 0 101736292 33656 SyS_po Sl+ tty2 0:00 /usr/libexec/deja-dup/deja-dup-monitor 0 1000 2452 1719 20 0 101927808 45988 SyS_po Ssl ? 0:00 /usr/libexec/evolution-addressbook-factory 0 1000 2240 1765 20 0 102007840 57328 SyS_po Sl+ tty2 0:00 /usr/libexec/evolution/evolution-alarm-notify 0 1000 2415 2288 20 0 102356528 47216 SyS_po Sl ? 0:00 /usr/libexec/evolution-calendar-factory-subprocess --factory all --bus-name org.gnome.evolution.dataserver.Subprocess.Backend.Calendarx2288x2 --own-path /org/gnome/evolution/dataserver/Subprocess/Backend/Calendar/2288/2 0 1000 2021 1719 20 0 102405692 46532 SyS_po Ssl ? 0:00 /usr/libexec/evolution-source-registry 0 1000 2288 1719 20 0 118711416 46164 SyS_po Ssl ? 0:00 /usr/libexec/evolution-calendar-factory 0 1000 2518 2452 20 0 119163652 49648 SyS_po Sl ? 0:00 /usr/libexec/evolution-addressbook-factory-subprocess --factory all --bus-name org.gnome.evolution.dataserver.Subprocess.Backend.AddressBookx2452x2 --own-path /org/gnome/evolution/dataserver/Subprocess/Backend/AddressBook/2452/2
All of these daemons use WebKit (mostly to show oauth2 login prompts), and WebKit recently introduced gigacages to isolate the heap used by their JS implementation. The allocation for a gigacage is big enough that any access to an arbitrary unsigned 32 bit offset would still land in the gigacage, resulting in these huge allocations. See this blog post for more details on gigacages: https://labs.mwrinfosecurity.com/blog/some-brief-notes-on-webkit-heap-hardening/
Many Gnome 3.28 daemons are using over 100 GB of VIRT. Why?
1,461,495,156,000
How do I change the default session I get when I log in? I'm on Debian jessie. I tried changing settings on gdm3, tried installing lightdm and following this but it's just not working. For more specificity, I'm trying to default to gnome-classic instead of gnome. I want to turn on the computer, log in as any arbitrary user, and see gnome-classic, not gnome3 (preferably I'd remove the gnome3 default session, if there's a way to do that).
On Debian, you should set the x-session-manager default command to choose your default session manager: # update-alternatives --config x-session-manager There, you can select the session manager you want GDM3 to use by default. If gnome-session-classic does not appear in the listing, try creating the link on your own. Something like the following: # update-alternatives --install /usr/bin/x-session-manager x-session-manager /usr/bin/gnome-session-classic 60 Then you should be able to select gnome-classic with update-alternatives --config x-session-manager. To customize the session managers listed by GDM, I think the only way is to go to /usr/share/xsessions and create/remove Desktop Entry files there. The format is easy to understand, but in case you need help, you can consult the Desktop Entry specification or the GNOME documentation about Desktop Entry files.
How do I change my default session?
1,461,495,156,000
I'm guessing I need to edit one of the schemas available in gsettings but I don't know which one. and when I listed all the schemas, there's just too many of them.
The key you want is favorite-apps, the schema ID is org.gnome.shell. Now to list your favorite apps you can simply run gsettings get org.gnome.shell favorite-apps or dconf read /org/gnome/shell/favorite-apps These will return an array of strings e.g. ['firefox.desktop', 'org.gnome.Terminal.desktop', 'org.gnome.Nautilus.desktop', 'org.gnome.gedit.desktop', 'gnome-calculator.desktop'] Now, to remove a value from that array you could use text processing tools like sed/awk to check if an item is in that list and remove it keeping the same format (not that trivial though definitely doable) and once you get it right just write the new settings to the database e.g. assuming you wanted to remove org.gnome.Nautilus.desktop you would run (note the double quotes): gsettings set org.gnome.shell favorite-apps "['firefox.desktop', 'org.gnome.Terminal.desktop', 'org.gnome.gedit.desktop', 'gnome-calculator.desktop']" or dconf write /org/gnome/shell/favorite-apps "['firefox.desktop', 'org.gnome.Terminal.desktop', 'org.gnome.gedit.desktop', 'gnome-calculator.desktop']" Still, it's easier to write your own utility (using gsettings API) that will accept one or more desktop file names as positional parameters and remove them from favorites; to get you started, here is a very basic example in python that accepts one param (run as script.py firefox.desktop): #!/usr/bin/env python from sys import argv from gi.repository import Gio,GLib item=argv[1] gschema = Gio.Settings('org.gnome.shell') gvalues=gschema.get_value('favorite-apps').unpack() if item in gvalues: gvalues.remove(item) gschema.set_value('favorite-apps', GLib.Variant('as', gvalues))
Gnome3+: How do I remove favorites from Dash via terminal?
1,461,495,156,000
In GNOME 3, there's a facility to assign keyboard shortcuts for applications like your default browser, default email client, default terminal etc. How do I do this for other applications?
As far as I know, there is no GUI application allowing that for gnome 3. If you have Gnome 2, you can still use the settings application from menu. The easiest ways for me is to edit settings through gconf-editor: specify your command in /apps/metacity/keybinding_commands/command_X specify your keyboard shortcut in /apps/metacity/global_keybindings/run_command_X The name of keyboard you can find using xev. X stands for number from 1 up to 12.
In GNOME 3, how does one assign keyboard shortcuts for applications besides the default applications?
1,461,495,156,000
Kernel: x86_64 Linux 4.4.5-1-ARCH GNOME: 3.20.0 I am unable to make use of the shortcut SUPER+M. What I've tried so far: assigning the shortcut to the system's email program assigning the shortcut to start a process thunderbird However, pressing it only opens the notification bar/calendar instead. Is this a bug or did I overlook something?
It doesn't work as that's one of the default gnome-shell shortcuts. So gnome-shell actually grabs it even if you set it to execute some custom action. You'll have to remove it first from the default shortcuts list - easiest way is via terminal with gsettings: gsettings set org.gnome.shell.keybindings toggle-message-tray "['<Super>v']" alternatively, if you prefer doing it via gui, fire up dconf-editor: in the left pane, navigate to org>gnome>shell>keybindings then in the right pane right click on toggle-message-tray and select customize: a new window will pop up: toggle Use default value to OFF: then edit the custom value, removing , '<Super>m' so that it reads: ['<Super>v'] then hit Apply. Restart your shell with Alt+F2 then r then Enter (or log out & log in). You should then be able to use your custom Super+M shortcut.
Cannot reassign shortcut SUPER+M under GNOME
1,461,495,156,000
I updated to the newest, 3.26.1, version of GNOME several hours ago, and I don't see the list of background applications that used to be located in the bottom-left corner of the screen, on a hidden sliding panel. The icons belonging to Audacious, VLC, Dropbox, Redshift and other applications I run in the background don't see anywhere in the screen. I opened the Tweaks app (or equivalently the gnome-tweak-tool command) looking for relevant configurations with no results. What happened to this feature, and is there a way to have one similar to it if it is gone? Source Status Icons and GNOME, Form and Function Allan Day's blog
The legacy tray was removed in 3.26 (it was a stop-gap measure, destined to be removed at some point, as explained in the corresponding bug). This is also mentioned in the release notes. To see your indicator icons, you can use an extension such as TopIcons Plus.
Where did the status icons go in GNOME 3.26.x and what can I do to bring them back?
1,461,495,156,000
I would like to bind both Super+1 and Super+Home as shortcuts to the "Switch to workspace 1" action in GNOME 3. Is there a way to do this? I think that to achieve this there would either have to be a way to assign multiple keyboard shortcuts to the same action or there would have to be a way to switch workspaces via a command-line action (which would alet me create a shortcut for it in the "custom shortcuts" section). But I'm not sure these are possible...
Yes, this is a dconf setting and the value is an array of strings which means it accepts multiple shortcuts. You can do that via dconf-editor if you navigate to /org/gnome/desktop/wm/keybindings/switch-to-workspace-1 and turn Use default value OFF then insert Custom value: ['<Super>Home', '<Super>1'] Or if you prefer CLI you can use dconf or gsettings e.g. gsettings set org.gnome.desktop.wm.keybindings switch-to-workspace-1 "['<Super>Home', '<Super>1']" Keep in mind the values must be quoted and separated by comma+space.
How can I assign redundant shortcuts for switching workspaces in GNOME 3?
1,461,495,156,000
Recently Gnome came up with a new feature of Night Light. It is really helpful. It feels too time-consuming that I need to go to settings (and then display) and activate it each time. Is there any terminal command that can simply turn on the night light feature? Manual and/or sunrise to sunset option aren't really helpful as even I don't know when I will be needing that particular feature to turn on or off. I tried to google but, found nothing related to command. Might not matter, but just in case, I am using Kali Linux. This is the feature I am talking about.
Yes, you can turn it on with gsettings set org.gnome.settings-daemon.plugins.color night-light-enabled true or dconf write /org/gnome/settings-daemon/plugins/color/night-light-enabled true Same commands with false instead of true will turn it off. If you list the keys under the org.gnome.settings-daemon.plugins.color schema you'll see that you can also configure the schedule (auto: on/off, manual: from/to) as well as the night light temperature. A very convenient way to set the latter is via the night light slider extension.
Activate Night Light option from terminal
1,461,495,156,000
I'm a long time KDE user, never seen GNOME since may be Mandrake Linux 10 something. Yesterday I took a look at GNOME Shell on Youtube and thought it may worth a look. It actually is worth, but I can't figure out one moment. I've got a shell script that used to run on my KDE Laptop installations for ages: synclient |grep -E 'TapT|RightB|EdgeScr'|awk '{print $1}'|while read item; do synclient $item=0; done synclient VertScrollDelta=-111 synclient HorizScrollDelta=1 synclient RightEdge=999999999 synclient TopEdge=0 synclient CircularScrolling=0 synclient BottomEdge=999999999 synclient RightButtonAreaLeft=9999999 synclient ClickFinger3=2 synclient HorizScrollDelta=0 synclient HorizTwoFingerScroll=0 This disables right-click, all taps, inverts scroll directions, disables horizontal scrolling and stuff. Touchpad menu nor in KDE neither in gnome doesn't allow this kind of configuration. (TBH, only Mac of all the operating systems has the gui to set up touchpad exactly like that :)). I can't figure out, how do I run this after gnome shell session starts? I've already tried this with no results: [1] % cat /home/neko/.config/autostart/script.desktop [Desktop Entry] Name="Auto stuff" GenericName="Auto startup stuff" Comment="Synclient mostly" Exec=/home/neko/bin/auto_stuff.sh Terminal=false Type=Application X-Gnome-Autostart=true Any other suggestions,please? Thank you.
You can use the program gnome-session-properties. Just execute it from your shell prompt (gnome-terminal): $ gnome-session-properties This will open a GUI where you can configure (i.e., add, edit, remove, enable and disable) startup programs. Nice and easy. Enjoy. Update: As noted by don_crissti (thanks) in the comments below, the gnome-session-properties startup programs functionality has migrated to gnome-tweak-tool since Gnome 3.12 (which btw is a great tool, but a little messier as it concentrates just too many functions). So, for versions 3.12 and above, this is the new place to look. OBS: And btw, using this method, you don't need to create a .desktop file, you can simply specify the command line of the /home/neko/bin/auto_stuff.sh script you created (or any other script or command you want).
Gnome Shell: Running shell script after session starts?
1,461,495,156,000
Today gvfsd-metadata process was running for a whole day hogging 100% of a single core of my CPU. Is there any reason for it to do it?
AFAIK gvfsd-metadata is a process that collects file metadata when you use Nautilus. If your metadata store got corrupted somehow, it might get stuck on an infinite loop. So you'll have to kill that process, and remove the metadata store. pkill gvfsd-metadata rm -rf .local/share/gvfs-metadata
Why ``gvfsd-metadata`` process is hogging 100% of a single core for a long time
1,461,495,156,000
I would like to be able to click on SSH links that look like ssh://user@servername and have a gnome-terminal open that runs SSH inside of it. After reading up on the XDG stuff I did the following: I created a shell script in $HOME/bin/ssh-terminal with the following: #!/bin/sh dest=${1#ssh://} gnome-terminal -e "ssh $dest" & This works from the command line. I created $HOME/.local/share/applications/ssh-terminal.desktop with: [Desktop Entry] Type=Application Name=SSH Terminal Exec=ssh-terminal %u Icon=utilities-terminal StartupNotify=false MimeType=x-scheme-handler/ssh; I ran update-desktop-database ~/.local/share/applications/ Now when I try to run xdg-open ssh://user@hostname I get the following error: $ xdg-open ssh://[email protected] gvfs-open: sftp://[email protected]/: error opening location: The specified location is not mounted I don't want to open it as a sftp mount and I cannot seem to find where that is set! Where do I go from here?
Writing a .desktop file is not enough. You also need to change the default setting for the mime type. You can get the current default value with xdg-mime query default x-scheme-handler/ssh and can change it with xdg-mime default ssh-terminal.desktop x-scheme-handler/ssh The corresponding configuration file could be $HOME/.config/mimeapps.list or $HOME/.local/share/applications/mimeapps.list depending on your OS version.
How to override the Gnome 3 SSH handler?
1,461,495,156,000
I am on Antergos with GNOME 3.24.3. Pressing the Super key (Windows key) opens this Activities menu/view that I don't want to use: Pressing the Super + A keys opens the menu that I want to open with just the Super key: I have attempted to set this myself by using dconf-editor to set the Activities menu to the Alt_R key (a key I never use) and the Show All Applications menu to the Super key. (The keybinding for the Activities menu is under /org/gnome/mutter/overlay-key. The keybinding for the Show All Applications menu is under /org/gnome/shell/keybindings/toggle-application-view.) However, pressing Super or Super + A does nothing now. How can I make this all work?
I configured those keys directly through Settings -> Devices -> Keyboard on Ubuntu 17.10. Under "System" section you have "Show the overview" which you can disable (by pressing backspace). And for "Show all applications" you can configure then Super.
How to set Super/Windows key to Show All Applications menu in GNOME DE?
1,461,495,156,000
I wanted to have some of the sub-folders of my home directory (like Music, Downloads,Videos) on my hard-disk-raid instead of my SSD. Therefore I deleted those folders in my home directory, recreated them on the RAID and made symlinks pointing from my home-folder to the RAID (e.g. /home/user/Music > /mnt/home-big-data/user/Music). However, the newly created folders don't have the correct meta-data-properties in Gnome 3 (wrong icon, folders won't open as Music folder, etc.). Which is the best way to remap those features to the folders on the RAID? I tried editing the /home/user/.config/user-dirs.dirs and setting XDG_DOWNLOAD_DIR="$HOME/Downloads" (according to the symlink) but it was resetted to XDG_DOWNLOAD_DIR="$HOME/" after reboot. Another thing I tried was using gvfs-set-attribute to reset the standard-icon, but this also failed. Which would be the correct way to do that?
Most likely, your user-dirs are reset to $HOME/ each time you reboot because those locations are not available on session startup when xdg-user-dirs-update is automatically run. After editing ~/.config/user-dirs.dirs a possible solution is to prevent xdg-user-dirs-update from running (and resetting your configuration at each session start up) by adding enabled=False to your user-dirs.conf: enabled=boolean When set to False, xdg-user-dirs-update will not change the XDG user dirs configuration. So to disable it only for your user account, add enabled=False to ~/.config/user-dirs.conf (this will override system-wide settings). If you want to disable it for all users add that key/value to /etc/xdg/user-dirs.conf.
user-dirs.dirs reset at start-up
1,461,495,156,000
I can't disable natural scrolling. That is, no matter whether I turn "Natural Scrolling" on or off, dragging the mouse wheel towards me scrolls up. $ gnome-shell --version GNOME Shell 3.20.4 $ cat /etc/redhat-release Fedora release 24 (Twenty Four) No matter what I set it to, if I go back to all settings and then open the "Mouse & Touchpad" settings again, the on/off state is persisted. So it seems whatever state that is setting is not used by the mouse driver.
This worked for me: gsettings set org.gnome.desktop.peripherals.mouse natural-scroll false gsettings set org.gnome.desktop.peripherals.touchpad natural-scroll false
How to *disable* natural scrolling?
1,461,495,156,000
I use awesome in a tiling mode for almost all my desktops. Since the advent of client side decorations in GTK3 some common Gnome project apps have taken to giving themselves a generous amount of padding outside of their main window border. I suspect this is for shadow effects, but it wreaks havok with the tiling system as the window sizing is done based on the padded size, not the normal window itself. Notable offenders are nautilus and gedit, but other recently updated Gnome apps all have the some behavior. How can I configure GTK and/or AwesomeWM to ignore these paddings and size the windows based on the actual window geometry? The result I want is a zero-border, zero-padding tiled layout.
Add to ~/.config/gtk-3.0/gtk.css: .window-frame { box-shadow: none; margin: 0; } (via https://bbs.archlinux.org/viewtopic.php?pid=1416334#p1416334) I had to restart X for it to take effect - SIGHUP awesome was not sufficient.
How can I remove the window padding on GTK3 apps in Awesome-WM?
1,461,495,156,000
I'm on Manjaro Gnome 3.28.3. For my situation, they do same thing, list thumbnails of all opened applications and if you press Super or Alt, Tab could help you to switch the applications. So, I want SuperTab and AltTab to do different things. Like SuperTab switch applications only on this workspace?
By default, they appear to both be assigned to “Switch applications”. They can be re-assigned using the keyboard preferences: Open the menu in the top-right-hand corner of your main screen. Click on the “Settings button”, i.e. the left-most button here: Choose “Devices” in the left-hand column: Choose “Keyboard”. This will lead you to a list of supported keyboard shortcuts, with their assigned keys; you can click on any entry to change it: The “Switch applications” entry is somewhat strange: it only shows SuperTab, but it is also assigned to AltTab and will be disabled if you re-assign the latter. However it can then be re-assigned to whatever you want. As you can see, I use SuperTab to switch applications, AltTab to switch windows, and CtrlSuperTab to switch windows inside an application. You can assign nearly any key to any of the supported shortcuts, but you can’t add new shortcuts. On my system, running GNOME 3.26, “Switch windows“ only shows windows on the current workspace: whereas “Switch applications” shows all applications across all workspaces: Note that GNOME Tweaks has an “Alternatetab” extension which can also be used to adjust the behaviour of the window switcher.
What's the difference between Super+Tab and Alt+Tab on Gnome?
1,461,495,156,000
I run Debian testing with Gnome 3.12. After installing "Workspace Grid" extension the workspace switch animation became increasingly annoying. I'm talking about that thing in the middle of the screen that appears when you use Ctrl+Alt+Arrow shortcut. It became bugged to the degree where it provides zero information, moreover, the overlay takes some time to disappear and I can't really see what's beneath it. In the evening or at night that animation just hurts my eyes (quick flash between dark overlay and light browser/IDE). How do I disable it? I'm willing to develop an extension for Gnome Shell if there is no easily available option (and the overlay is possible to disable by the means of an extension). Note: I still want all other animations, including sliding effect of workspace switching.
There's an extension called Disable Workspace Switcher Popup that does exactly what you want. Install as per the instructions on the extension homepage.
Disable workspace switch overlay effect
1,461,495,156,000
I'm running GNOME 3 on Fedora 25, which uses Wayland as opposed to Xorg. I'm having trouble finding a way to modify my mouse wheel scroll speed and touchpad scroll speed without affecting mouse/touchpad sensitivity and acceleration. My mouse wheel scrolls only one or two lines at a time, which is maddening and way too slow. My touchpad two-finger scrolling is the opposite, it is way too sensitive and I find myself scrolling way past where I want to go. After extensive Googling all I'm left with are ways to modify these settings when using Xorg, but I'm on Wayland using libinput. The GSettings GUI does not have these options separated. Any help would be greatly appreciated.
I've tried Wayland also, and switched back to xorg finally, just because of the touchpad/mouse problem. I'm afraid that xorg may still be the best solution. Libinput just doesn't provide much for touchpad/mouse calibration. This is too bad for laptops on Wayland... Though may not be of some help, here's some info on libinput. To switch to xorg on Gnome 3, you can click on the gear button and choose "gnome on xorg" when you're​ on the login screen. Here's some other info on how to calibrate with synaptics on xorg
Modify mouse wheel and touchpad two-finger scrolling speed
1,461,495,156,000
I installed telegram-desktop via Flatpak and would like to auto start the messenger when logging into Gnome 3 (or Unity as a fact). Is there a way to robustly do so?
Starting from the answer given by @intika I found a solution I like more. Instead of replicating the content of the existing desktop-file in /var/lib/flatpak/exports/share/applications/org.telegram.desktop.desktop I linked it inside my personal ~/.config/autostart/. Works like a charm :-)
How to add a Flatpak's app to Gnome 3 auto-starts?
1,461,495,156,000
I upgraded to Fedora 21, which spotlights GNOME 3.14 (plus the relevant GTK+ material). Unfortunately it seems that this particular update mangles a lot of my older themes, written for now-aging versions of GNOME 3. Where previously they may have squeaked by, they now look a little out-of-place. I don't presume to re-invent the wheel: I would be very happy to take a pre-existing CSS template (e.g. the default Adwaita 3.14 spec) and tweak it here and there to my liking; there will be no fancy flying. Imagine the hair I tore out when I peeked at /usr/share/themes/Adwaita/gtk-3.0/gtk.css: /* Adwaita is the default theme of GTK+ 3, this file is not used */ That puts me in a pickle. I lack the Google-fu to dig the documentation up about where this might be (worse, I have a gut feeling this is something implicitly obvious to GNOME people that I have been missing out on), and for some reason the GNOME developer website resists my attempts at researching their theming specification. In short, I'd like to find a virgin theme specification for GNOME 3.14, assuming one is extant. How may I do this, or how may I modify my approach?
There's only a single line in that .css file because the default theme Adwaita comes as a binary: Adwaita is a complex theme, so to keep it maintainable it's written and processed in SASS, the generated CSS is then transformed into a gresource file during gtk build and used at runtime in a non-legible or editable form. For gnome 4.* per the README: How to tweak the theme Default is a complex theme, so to keep it maintainable it's written and processed in SASS. The generated CSS is then transformed into a gresource file during gtk build and used at runtime in a non-legible or editable form. It is very likely your change will happen in the _common.scss file. That's where all the widget selectors are defined. Here's a rundown of the "supporting" stylesheets, that are unlikely to be the right place for a drive by stylesheet fix: _colors.scss - global color definitions. We keep the number of defined colors to a necessary minimum, most colors are derived from a handful of basics. It covers both the light variant and the dark variant. _colors-public.scss - SCSS colors exported through gtk to allow for 3rd party apps color mixing. _drawing.scss - drawing helper mixings/functions to allow easier definition of widget drawing under specific context. This is why Default isn't 15000 LOC. _common.scss - actual definitions of style for each widget. This is where you are likely to add/remove your changes. You can read about SASS at http://sass-lang.com/documentation/. Once you make your changes to the _common.scss file, GTK will rebuild the CSS files. Also, check the guidelines present in Default-light.scss and Default-dark.scss: // General guidelines: // - very unlikely you want to edit something else than _common.scss // - keep the number of defined colors to a minimum, use the color blending functions // if you need a subtle shade; - if you need to inverse a color function // use the @if directive to match for dark $variant In the same git directory (Default) you'll find the files _common.scss, _colors.scss, _colors-public.scss and _drawing.scss For gnome 3.*: Since the code has been included in gtk+, you can view the source files HERE. As per their readme: _colors.scss - global color definitions. We keep the number of defined colors to a necessary minimum, most colors are derived form a handful of basics. It covers both the light variant and the dark variant. _colors-public.scss - SCSS colors exported through gtk to allow for 3rd party apps color mixing. _drawing.scss - drawing helper mixings/functions to allow easier definition of widget drawing under specific context. This is why Adwaita isn't 15000 LOC. _common.scss - actual definitions of style for each widget. This is where you are likely to add/remove your changes. In the same git directory (Adwaita) you can find the _*.scss files mentioned above and the reference schemes: gtk-contained.css gtk-contained-dark.css
Where may I find a reference scheme for GNOME 3 theming (e.g. Adwaita)?
1,461,495,156,000
I'm running Fedora 27, and my university uses a network authenication portal so GNOME pops up a hotspot login screen. I would like to disable this screen, and just have it open it in firefox, because my login data is already there. How do I change this setting? I've checked the settings app and there are no settings to change it. Unless there is a better way to get past the captive portal. I saw mention of the WHISPr protocol. The captive portal my university uses is Cisco Meraki.
From the man page: CONNECTIVITY SECTION This section controls NetworkManager's optional connectivity checking functionality. This allows NetworkManager to detect whether or not the system can actually access the internet or whether it is behind a captive portal. uri The URI of a web page to periodically request when connectivity is being checked. This page should return the header "X-NetworkManager-Status" with a value of "online". Alternatively, it's body content should be set to "NetworkManager is online". The body content check can be controlled by the response option. If this option is blank or missing, connectivity checking is disabled. By default on Fedora, the package NetworkManager-config-connectivity-fedora puts that configuration into /usr/lib/NetworkManager/conf.d/20-connectivity-fedora.conf. You can simply remove that package (although this won't guarantee that it won't come back). If you just edit that file, you may find that it reappears on upgrade. So, again from the man page: If a default NetworkManager.conf is provided by your distribution's packages, you should not modify it, since your changes may get overwritten by package updates. Instead, you can add additional .conf files to the /etc/NetworkManager/conf.d directory. These will be read in order, with later files overriding earlier ones. Packages might install further configuration snippets to /usr/lib/NetworkManager/conf.d. This directory is parsed first, even before NetworkManager.conf. Scripts can also put per-boot configuration into /run/NetworkManager/conf.d. This directory is parsed second, also before NetworkManager.conf. The loading of a file /run/NetworkManager/conf.d/name.conf can be prevented by adding a file /etc/NetworkManager/conf.d/name.conf. Likewise, a file /usr/lib/NetworkManager/conf.d/name.conf can be shadowed by putting a file of the same name to either /etc/NetworkManager/conf.d or /run/NetworkManager/conf.d. So, what you need to do here is to simply sudo touch /etc/NetworkManager/conf.d/20-connectivity-fedora.conf which will create a blank file under the /etc directory, overriding the default from /usr/lib. This is a common pattern in many modern Linux applications — defaults shipped with packages go under /usr/lib, and those can be overridden in /etc.
WIFI - Disable Hotspot Login Screen
1,461,495,156,000
I am using NixOS with Gnome, and would like to set Chromium as the default browser. The 'Details' section of my settings, under 'default applications' shows the following: Both Chromium and Firefox have been installed on my system (Chromium via $ nix-env -i chromium), and yet they do not show up under the drop-down for 'Web', which shows only the one option. How can I set Chromium to be my default browser?
NixOS does not manage user-specific configuration. Full-stop. As for the browsers not being found by the configuration dialog, try installing them via /etc/nixos/configuration.nix instead of with nix-env. Tip If you install packages declaratively and imperatively you'll end up having to manage two dependency trees. One via nixos-rebuild --upgrade boot and another by nix-channel --update && nix-env -u. Meaning that if you forget either update process you'll end up with old packages installed.
How to set the default browser in NixOS?
1,461,495,156,000
What is the difference between gnome3 and gnome-shell, if any?
GNOME Shell is just one part of GNOME 3. Together with Mutter (the window manager), it is its primary user interface. The secondary interface (for hardware that can't handle the 3D workload, or for people who don't care about glitz), is Gnome Panel + Metacity (old window manager), which will basically give you the look of current GNOME 2. GNOME 3 is a whole desktop suite that includes a whole bunch of stuff like a GUI toolkit, development suites, a file manager, some utilities, some system-level daemons, and a whole bunch of apps.
Difference between Gnome3 and Gnome-shell
1,461,495,156,000
What's the correct way to restart Gnome 3 (and Xorg) under Debian 7.0 Wheezy? I've seen older documentation on how to this, but it is outdated. The ctrl+alt+backspace shortcut no longer works by default. Running sudo /etc/init.d/gdm3 restart from Gnome terminal just gives me a blank screen with blinking underscore and never properly reboots the X session.
You need to issue the command for restarting the X server from outside the X session: Switch to a virtual terminal using CTRL+ALT+Fi with i falling between 1 to 6 inclusive (2 to 7 inclusive if you're on Fedora or RHEL). Log in at the prompt Run sudo /etc/init.d/gdm3 restart or sudo service gdm3 restart Reattach to the original screen using CTRL+ALT+Fi, where i is the higher screen number of the original X session, F7 should be the default on Debian
Restarting Gnome 3 in Debian Wheezy?
1,461,495,156,000
I just switched to Fedora 22 and decided to go for Gnome3 this time instead of XFCE. I like the Thunar file manager so I downloaded it. I've had trouble setting it as the default file manager though. What I tried: I ran exo-preferred-applications. Under Utilities -> File Manager I selected Thunar. The problem: It's not acting as the default file manager. When I open my Downloads folder from my browser I still get Nautilus. Same when I click on my "Places".
You could try editing /usr/share/applications/defaults.list and changing the line inode/directory=nemo.desktop;caja.desktop;nautilus.desktop;Thunar.desktop;kde4-dolphin.desktop to inode/directory=Thunar.desktop; or some order that suits your needs.
Changing default file manager in Gnome3 (Fedora 22)
1,461,495,156,000
I am not able to login into GNOME desktop, it happened yesterday after upgrade. In login screen, if I enter my password and press ENTER I am getting login screen again. System details: linux 4.4.5-1 gnome-shell 3.20.0-3 gnome-desktop 1:3.20.1-1 gnome-session 3.20.1-1 gdm 3.20.0-1 Logs: Xorg log: http://sprunge.us/SHSh Journalctl log: http://sprunge.us/GIaM Few tips for you to help me: I am able to login in GNOME Wayland session but not with default GNOME (with xorg) I created new user (from console) but same problem occurs when this new user tries to login. output of uname -a: Linux ArchLinux 4.4.5-1-ARCH #1 SMP PREEMPT Thu Mar 10 07:38:19 CET 2016 x86_64 GNU/Linux Please ask if you need more info.
I guess the reason is /etc/profile.d/bundler-exec.sh: line 12: `bundler-installed': not a valid identifier in journalctl.log Can you provide this file?
Cannot login into GNOME, kicking me back to login screen
1,461,495,156,000
I would like to manage my ssh passwork with gnome-keyring. I am on Ubuntu 12.04.3 LTS, gnome3. I don't have root access to the system. The question is in the title indeed: gnome-keyring-daemon: insufficient process capabilities, unsecure memory might get used This worries me. What does it mean?
Since you are not root on system, the process calling gnome-keyring-daemon does not have the privileges to prevent a possible write of the sensitive cryptographic key data to the system's hard disk. What happens is that the gkd process does not have the ability to perform a CAP_IPC_LOCK to lock memory. If your filesystem supports capabilities, you can give the executable this capability with this terminal command: sudo setcap cap_ipc_lock=+ep `which gnome-keyring-daemon` Without this capability the key storage memory can not be locked, there is a chance the memory might swap out and be written to the hard disk, where it could be read by someone with either root access on the machine or physical access to the hard disk the memory swapped to. Here is the source code of the file that generates that warning: https://github.com/GNOME/gnome-keyring/blob/master/daemon/gkd-capability.c More information about memory locking: http://man7.org/linux/man-pages/man2/mlock.2.html
gnome-keyring-daemon: insufficient process capabilities, unsecure memory might get used
1,461,495,156,000
I changed the keybinding to Show the activities overview in the panel System Settings / Keyboard / Shortcuts to Shift-ESC, but the left-meta or left-windows key is still bringing it up. How do I disable that binding?
gconftool -s /apps/mutter/general/overlay_key -t string "Super_R" worked (after shell restart) for me. Instead of Super_R feel free to put name of any key which doesn't exist on your keyboard.
How do I disable the left-(meta|windows) key binding in gnome-shell
1,461,495,156,000
I'd like to make my IDE window partially transparent. I achieved this in Unity using compiz as described in the accepted answer to: How to make a window transparent in gnome. However I don't believe compiz will work for this with gnome unless I'm mistaken. There WAS a gnome extension for this but it has been abandoned and the github repo is gone. Anyone know of a way to achieve this? I'm on ubuntu 17.10
There's another extension called Glassy Gnome that works with newer versions of gnome-shell. For more details consult the included README.
Set window transparency in Gnome
1,461,495,156,000
First of all, I saw this question and all the others with similar answer and it does not seem to work for me. I use Ubuntu 19.04 and GNOME 3.32.1 I downloaded Postman (a code testing tool) and I want to be able to launch it from the dock. When I launch it from the shortcut, it appears in the dock: But when I right-click it, I cannot add it to my favorites, which usually allows me to pin an application to the dock: I also tried to add a desktop file to /usr/share/applications and ~/.local/share/applications and make it executable, and then restarting gnome, but it did nothing. Desktop file : [Desktop Entry] Type=Application Encoding=UTF-8 Name=Postman Icon=/home/[my user name]/Utilities/Postman/app/resources/assets/icon.png Exec=/home/[my user name]/Utilities/Postman/app/Postman Terminal=false Categories=Development;
Ok so I was able to add it to the dock following these steps. Add this desktop file to ~/.local/share/applications as postman.desktop: [Desktop Entry] Type=Application Name=Postman Icon=/home/[my user name]/Utilities/Postman/app/resources/app/assets/icon.png Exec=/home/[my user name]/Utilities/Postman/app/Postman Terminal=false Categories=Development; then searching for "postman" via "Activities" (it only shows up there if you already created the .desktop file) and right click it > add to favorites.
Gnome 3 : How do I create a launcher in the dock?
1,461,495,156,000
I'm using Linux Mint Debian edition and I have set Firefox as my default browser in my settings. But HTTP links in other apps like hotot and pidgin open with Chromium! Why is this happening is there any way to track the problem?
I'm going to guess the following all of those tools use XdgUtils if you type xdg-open http://google.com it'll open with Chromium and that you have the problem described in this Ubuntu forumspost So my suggested answer is: $ xdg-mime default firefox.desktop x-scheme-handler/http (and ditto for https)
My default browser is set to Firefox but links open with Chromium
1,461,495,156,000
I'm trying to use cryptdisks_start to open a LUKS device that is defined in my /etc/crypttab. Unfortunately, the command fails with the following error message: martin ~ # cryptdisks_start luks-01a2e5d8-9211-40ce-b160-d3f973d1a155 * Starting crypto disk... * luks-01a2e5d8-9211-40ce-b160-d3f973d1a155 (starting).. * luks-01a2e5d8-9211-40ce-b160-d3f973d1a155: the precheck for '/dev/disk/by-uuid/01a2e5d8-9211-40ce-b160-d3f973d1a155' failed: - The device /dev/disk/by-uuid/01a2e5d8-9211-40ce-b160-d3f973d1a155 contains a filesystem type crypto_LUKS. * luks-01a2e5d8-9211-40ce-b160-d3f973d1a155 (failed)... ...fail! A rather strange error, because of course that device has to contain a crypto_LUKS filesystem! The relevant line from /etc/crypttab, as set up by GNOME Disks: luks-01a2e5d8-9211-40ce-b160-d3f973d1a155 UUID=01a2e5d8-9211-40ce-b160-d3f973d1a155 /etc/luks-keys/luks-01a2e5d8-9211-40ce-b160-d3f973d1a155 nofail
It doesn't work because the /etc/crypttab line is missing the option keyword luks. Changing the line to this resolved the issue: luks-01a2e5d8-9211-40ce-b160-d3f973d1a155 UUID=01a2e5d8-9211-40ce-b160-d3f973d1a155 /etc/luks-keys/luks-01a2e5d8-9211-40ce-b160-d3f973d1a155 luks,nofail This is due to the fact that cryptdisks_start uses the options to determine what kind of encryption is being used so that it will use the correct command to open the device. Without the luks option, cryptdisks_start will try to open the device as a plain dm-crypt device with cryptsetup create. Luckily a sanity check prevents this, although it causes a confusing error message. Apparently the Disks tool of GNOME3 writes this incorrect line to /etc/crypttab when using the unlock icon and saving the passphrase.
cryptdisks_start: precheck failed: the device contains a filesystem type crypto_LUKS
1,461,495,156,000
I have been using Arch Linux + GNOME 3 on both my computers (notebook and desktop) for over a year now. And all the time, computers were shutting down quickly (in 3 seconds). After a recent update of all packages on both computers via Pamac, the computers now take a long time to shut down (it takes about 2 minutes to wait before shutting down). I usually shutting down the computer through the GNOME 3 graphical interface. What have I tried to do? Recently updated all packages again, but it didn't help. Used the command sudo systemctl --force --force poweroff, it helps and computers turn off quickly. Used the command sudo systemctl --force poweroff, in this case, the computer turns off in 1.5 minutes, and displays a message on the screen: systemd-shutdown[1]: Waiting for process: gnome-session-b, Xwayland, gsb-media-keys, dbus-daemon, pulseaudio, gsd-power, gnome-shell, systemd, gsd-wacom, gsd-xsettings, gsd-color. UPD: When I ran the command sudo journalctl -b -1 -e --no-pager, I found the following time gap in the log: Dec 24 18:05:28 archlinux systemd[497]: evolution-source-registry.service: Succeeded. Dec 24 18:05:28 archlinux systemd[497]: evolution-calendar-factory.service: Succeeded. Dec 24 18:05:28 archlinux systemd[497]: evolution-addressbook-factory.service: Succeeded. Dec 24 18:07:28 archlinux systemd[1]: [email protected]: State 'stop-sigterm' timed out. Killing. Dec 24 18:07:28 archlinux systemd[1]: [email protected]: Killing process 497 (systemd) with signal SIGKILL. Dec 24 18:07:28 archlinux systemd[1]: [email protected]: Killing process 1329 (dbus-daemon) with signal SIGKILL. Dec 24 18:07:28 archlinux systemd[1]: [email protected]: Main process exited, code=killed, status=9/KILL Dec 24 18:07:28 archlinux systemd[1]: [email protected]: Failed with result 'timeout'. Dec 24 18:07:28 archlinux systemd[1]: Stopped User Manager for UID 1000. UPD 2: I do not know if this is the right solution, but the solution given on this web page helped me: bbs.archlinux.org/viewtopic.php?id=261530 Run command: systemctl edit --user gnome-session-restart-dbus.service and add the following lines above ### Lines below this comment will be discarded: [Service] Slice=-.slice
How I solved my question: Found the time gap in the log by the command: sudo journalctl -b -1 -e --no-pager (the time gap in my case is 2 minutes) I typed the information obtained from the logs into a search engine and found a solution: bbs.archlinux.org/viewtopic.php?id=261530 Executed the command: systemctl edit --user gnome-session-restart-dbus.service and add the following lines above ### Lines below this comment will be discarded: [Service] Slice=-.slice
Why do my computers take a long time to shut down?
1,461,495,156,000
I recently had to change the keyboard-shortcuts after updating my system. I had to use dconf-editor to manually set the shortcut from <Super>+R to <Mod4>+R in order to get them to work (see here). This does work when I press the right super-key together with the specified alphabetic key, but it does not work when using the left super-key. Also, the gnome-shell menu is set to show up when I press just the super-key, but it only shows up when pressing the left one. I'd like to have gnome-shell accept both the left and the right super-key for the shortcut, but I don't want to remap the menu-key (which is <Super> by default).
Use xmodmap -pm to verify that both keys have the mod4 modifier associated with them. vikktakkht:686 Z$ xmodmap -pm xmodmap: up to 4 keys per modifier, (keycodes in parentheses): shift Shift_L (0x32), Shift_R (0x3e) lock Caps_Lock (0x42) control Control_L (0x25), Control_R (0x69) mod1 Alt_L (0x40), Alt_R (0x6c), Meta_L (0xcd) mod2 Num_Lock (0x4d) mod3 mod4 Super_L (0x85), Super_R (0x86), Super_L (0xce), Hyper_L (0xcf) mod5 ISO_Level3_Shift (0x5c), Mode_switch (0xcb) Note that it's not enough that it's named Super_L or Super_R; it's the modifier mapping that matters. You can use xmodmap to associate keysyms with modifiers, but if your system is at all modern (and not OS X) then it uses Xkb and you probably want to examine your Xkb configuration instead of trying to change it with xmodmap. (Look at setxkbmap and friends, although probably there is a GNOME 3 interface to it that you should use.)
keyboard shortcuts only work with left super-key
1,461,495,156,000
I am running Debian GNOME 8.0. I would like to have Numlock ON as default. So I followed the instructions on this page: https://wiki.archlinux.org/index.php/Activating_Numlock_on_Bootup#GDM replacing gdm by gdm3 for my case. This turns Numlock ON at login. But then, after login, Numlock is automatically switched OFF again, and I cannot figure out how to leave it ON. I looked at this page : Keep NumLock always on and edited my .bashrc file to add this line: xmodmap -e "keycode # = """ which works to disable Numlock key. But since Numlock is OFF when my session opens, I could not turn it ON anymore! Thus it did not solve my problem. That would be useful if my Numlock was ON by default. (I re-enabled the Numlock key). As information, I had initially installed Debian LXDE, but added GDM to switch to GNOME, and then removed and purged lxde* and lightdm*. I feel like this is the reason for my problem, since: I found on the web that LXDE switches numlock OFF as default my other computer, on which I installed Debian GNOME natively, does not have this problem. I am sure to be using GNOME since: pierre@Ockham:~$ echo $XDG_SESSION_DESKTOP gnome pierre@Ockham:~$ echo $GDMSESSION gnome pierre@Ockham:~$ echo $XDG_CURRENT_DESKTOP GNOME However, just in case lightdm would still play a role, I did try to follow the instructions on that page: http://wiki.archlinux.org/index.php/LightDM#NumLock_on_by_default and that one: http://linuxquestions.org/questions/debian-26/howto-debian-7-wheezy-lxde-auto-numlock-both-before-and-after-login-4175500323/ but it did not solve the problem. Does anybody have an idea? By the way, the /etc/xdg/ folder still contains LXDE and Openbox (which I also removed) folders: pierre@Ockham:/etc/xdg$ ls autostart libfm lxlauncher lxpanel lxsession menus openbox pcmanfm systemd user-dirs.conf user-dirs.defaults Is it normal or should I remove them? And how?
The solution was actually very simple (see @don_crissti 's comment): set the dconf key remember-numlock-state (under org > gnome > settings-daemon > peripherals > keyboard) value to true via dconf-editor or in terminal: gsettings set org.gnome.settings-daemon.peripherals.keyboard remember-numlock-state true
Remember Numlock state after login in GNOME
1,426,811,692,000
For a project I need to write and execute Ansible scripts in a Linux environment (CentOS). Though using the command line and vi is interesting, I need to use graphical file explorer and Visual Studio Code to edit files. Because the Linux VMs available to me have low memory (3GB) and run on slower CPUs, GNOME 3 for Desktop is too slow. Are there lighter GUIs in which I can run Visual Studio code?
Given your use case, and if you are this low on memory, the best choice would be to switch to a lightweight Desktop Environnement (DE), such as: XFCE Mate LXDE LXQt etc. If you are (even sort of) new to Linux, I would suggest you to stay away from Tilling Window Managers (TWM); although being extremely lightweight and powerful once configured and mastered, I do not think one of these would be a good idea given your situation. If you want to install XFCE (example): First, you need to add the Extra Packages for Enterprise Linux (EPEL) repository, as this is where you will install packages from: # yum -y install epel-release Then you can install XFCE Desktop Environment as following: # yum -y groupinstall X11 # yum -y groups install "Xfce" After a reboot, you will be able to switch to XFCE4 instead of using GNOME3 at the login screen.
Lightweight desktop environments to replace GNOME for CentOS?
1,426,811,692,000
Can it be done? I don't want to use Evolution's calendar... I want to keep using Thunderbird... I have to add some addons (like lightning) first right? My goal is to have some calendar-like on thunderbird and replace the one of Evolution.
OK, I found how to do this at How to change gnome-shell calendar default application Just execute this in a terminal!! gsettings set org.gnome.desktop.default-applications.office.calendar exec thunderbird I have tested it and it works!! (it's not exaclty what I wanted but it's a start)
How can I make the Gnome3 calendar use Thunderbird instead of Evolution?
1,426,811,692,000
I'm running a GNOME/Wayland desktop environment, with GDM, on a Debian-based distro. I normally lock the screen with Super + L . Is there a command to invoke the screen-lock from the terminal?
Yes you can do this. dbus-send --type=method_call --dest=org.gnome.ScreenSaver \ /org/gnome/ScreenSaver org.gnome.ScreenSaver.Lock From http://choffee.co.uk/thoughtsplurge/posts/2013/07/11/lock_gnome_screensaver/ via "How can I lock my screen in Gnome 3.8 without GDM?"
Can I invoke a GNOME screen-lock from the terminal? [duplicate]
1,426,811,692,000
I've created a custom script to launch VirtualBox that replaced the original script in ¸/usr/bin/¸. So running VirtualBox in a terminal launches my script. However, pressing super key and type "virtualbox" in Gnome Shell launcher brings the old original script. How can I change that behavior so that when I type virtualbox in Gnome Shell launcher my custom script runs?
Look for the file /usr/share/applications/virtualbox.desktop. On my system, it has the following contents: [Desktop Entry] Encoding=UTF-8 Version=1.0 Name=Oracle VM VirtualBox GenericName=Virtual Machine Type=Application Exec=VirtualBox %U ... Simply change the Exec part to point to your custom executable/script. See also Thomas Nyman's answer to a similar question.
Change executable reference for app icon in in GNOME 3 launcher
1,426,811,692,000
Environment: Distribution: Arch Linux Display Manager: GDM 3.16.x Dekstop Environment: Gnome 3.16 Question: How to disable the user list displayed on the login screen? Clarification: Wanted result: In effect, from the users perspective, the result: Being presented with a box that requests a username upon reaching the login screen. Not a solution: Making the given users into systemusers is not a very good solution. Preferred method of achieving the wanted result What exact packages do I need to install or disable? If not through packages then what utilities should I use to configure the needed setting? If lower-level configuration is required, what manual settings do I need to change in what files (filepaths please)?
This should work with gdm ≥ 3.12 (tested on archlinux w. gdm 3.16.1): switch to a VT (e.g. Ctrl+Alt+F3), login as root and run: su - gdm -s /bin/sh to switch user to gdm. then run: export $(dbus-launch) and: GSETTINGS_BACKEND=dconf gsettings set org.gnome.login-screen disable-user-list true run exit or hit Ctrl+D to return to root account. restart the display manager: systemctl restart gdm Reverting is pretty much the same, just change true to false @ step 2.
How to disable the user list on GDM3 login screen?
1,426,811,692,000
I'm a long-time Windows user who uses the numeric keypad with the numlock off for navigating text, highlighting it, etc. Shift + Home (7 on the numpad) selects all text till the beginning of the line. In GNOME, pressing Shift + Home on the numpad inputs 7 instead of selecting all text till the beginning of the line. Is there a way to change the behaviour of the numpad in GNOME 3 to that of the direction pad?
There's an option for it in the typing settings: open gnome-tweak-tool and in the Typing section expand Miscellaneous compatibility options and check the option "NumLock on: digits, Shift switches to arrow keys, NumLock off: always arrow keys (as in MS Windows)" Or you could use dconf-editor, navigate to org>gnome>desktop>input-sources>xkb-options and add 'numpad:microsoft' to the existing values. For a desktop-agnostic solution, you can use setxkbmap -option numpad:microsoft in your X startup files.
Change behaviour of numpad to dpad in GNOME 3
1,426,811,692,000
I get this gpg: WARNING: The GNOME keyring manager hijacked the GnuPG agent. gpg: WARNING: GnuPG will not work proberly - please configure that tool to not interfere with the GnuPG system! when I use gnupg-agent with mutt. But the warning doesn't give me clue how to resolve the issue, nor could I find the info from GNOME documentation.
It is a clash between gpg2 and gnome-keyring and the message is misleading and harmless. If you like to remove the message, execute the following command on a terminal. sed -i s/AGENT_ID/AGENX_ID/ `which gpg2` More Details can be found here
GNOME keyring manager and gnupg
1,426,811,692,000
I am running a GNOME 3 fallback desktop in Debian testing, and I removed some pulseaudio packages, for I don't need the advanced functionality. That resulted in my multimedia keys that control speaker volume to work no more. This forces me to use a mouse on the classic volume control applet to control the volume, which isn't always convenient. Here's what I get: $ acpi_listen button/volumedown VOLDN 00000080 00000000 K button/volumeup VOLUP 00000080 00000000 K note: the other Fn keys (brightness, suspend, ...) work okay
ArchWiki page provided explanations, and creating the following files worked for me: /etc/acpi/actions/volume #! /bin/sh step=5 case $1 in -) amixer set Master $step-;; +) amixer set Master $step+;; esac /etc/acpi/events/volume_down event=button/volumedown action=/etc/acpi/actions/volume - /etc/acpi/events/volume_up event=button/volumeup action=/etc/acpi/actions/volume +
Regaining usage of volume control media keys after removing pulseaudio
1,426,811,692,000
Is there a gnome 3 extension or a fedora 25 shortcut to close all opened applications in a workspace? (Closing the workspace itself by pressing an X for example). I've seen that functionality somewhere long time ago, forgot where, but it's not available in fedora by default.
The answer below was written and tested on Gnome3 / Ubuntu. Please mention if you run into issues when running it on Fedora / Gnome. Script to close all application windows on a specific workspace in Gnome The script below will close all windows on a specific workspace, with two options: When run without arguments, it closes all windows on the current workspace, e.g.: python3 /path/to/script.py when run with a specific workspace as argument, it will close all windows on that workspace, e.g.: python3 /path/to/script.py 0 will close all applications on workspace 1. Note that the first workspace has index 0 The script #!/usr/bin/env python3 import subprocess import sys arg = sys.argv[1:] def check_close(w_id): w_data = get(["xprop", "-id", w_id]) if "_NET_WM_WINDOW_TYPE_NORMAL" in w_data: subprocess.call(["wmctrl", "-ic", w]) def get(cmd): return subprocess.check_output(cmd).decode("utf-8") wlist = [l.split() for l in get(["wmctrl", "-lG"]).splitlines()] arg = arg[0] if arg else [ l.split()[0] for l in get(["wmctrl", "-d"]).splitlines() if '*' in l ][0] for w in [w[0] for w in wlist if w[1] == arg]: check_close(w) How to use The script needs wmctrl, which should be installed if it isn't on your system. Copy the script into an empty file, save it as close_wins.py Now test- rune the script from a terminal window, with the targeted workspace as argument, e.g.: python3 /path/to/close_wins.py 2 to gracefully close all windows on workspace 3 (0 = worspace 1) To close all windows on the current workspace, run it without arguments: python3 /path/to/close_wins.py If all works fine, add it to a shortcut key: choose: System Settings > "Keyboard" > "Shortcuts" > "Custom Shortcuts". Click the "+" and add the command: python3 /path/to/close_wins.py ...or run it in any other way you'd prefer. Explanation The command wmctrl -lG will give us information on the currently opened windows. The output looks like: 0x018000f9 0 135 206 650 500 jacob-System-Product-Name pscript_6.py (1,6 GB Volume /media/jacob/6C08-F637) - gedit 0x01600a09 1 283 275 724 443 jacob-System-Product-Name jacob@jacob-System-Product-Name: ~ 0x018018be 1 152 407 650 500 jacob-System-Product-Name Untitled Document 1 - gedit 0x0140008c 2 0 101 1280 960 jacob-System-Product-Name gnome - Can I have a countdown window show the time until next suspend? - Ask Ubuntu - Mozilla Firefox 0x01600a49 2 47 146 724 443 jacob-System-Product-Name jacob@jacob-System-Product-Name: ~ From the second column, we can retrieve the window's location: 0x0140008c 2 0 101 1280 960 jacob-System-Product-Name gnome - Can I have a countdown window show the time until next suspend? - Ask Ubuntu - Mozilla Firefox The 2 means the window is on workspace 3, since 0 refers to the first workspace. If the script runs with the workspace as argument, the script parses out the corresponding window- id's and subsequently closes them gracefully with the command (e.g.): wmctrl -ic 0x0140008c If the script runs without the workspace as argument, the script retrieves the current workspace from the command: wmctrl -d and subsequently uses the current workspace internally as argument.
How to close all applications in a workspace?
1,426,811,692,000
The workspace switcher popup doesn't provide previews by default. Is there any way to enable them? The Workspace List that shows up on the right when super key is pressed does have preview.
You could do that via a gnome-shell extension: workspace-switcher-popup-thumbnails Download the zip file and either use gnome-tweak-tool to install it or extract the archive and move the resulting directory to ~/.local/share/gnome-shell/extensions/gnome-shell-extension-workspace-switcher-popup-thumbnails@sustmidown.centrum.cz note the name of the extension directory (it has to match the uuid in metadata.json) then inside that directory, edit the metadata.json and replace 3.8 with your gnome-shell version, e.g. "shell-version": ["3.18.2"] save, restart both gnome-shell (Alt+F2 then r) and gnome-tweak-tool and use the latter to enable the extension:
Showing thumbnails or some kind of preview in the Gnome workspace switcher popup?
1,426,811,692,000
Currently I'm using i3 window manager (but I guess that this applies to other non-standard window managers as well). Whenever I run nautilus it also starts a full screen desktop, which I have to close. Possible solution is to start nautilus with: nautilus --browser --no-desktop, which solves this problem only partially, as sometimes nautilus is launched automatically by other applications and in this case it would be launched without --browser --no-desktop options. Is there any gnome3 config option that allows me to suppress desktop launching?
Yes, there is a dconf value that controls this. Run the following command to disable drawing of the desktop by Nautilus: gsettings set org.gnome.desktop.background show-desktop-icons false Source: https://askubuntu.com/a/237984/81372
Launching nautilus file browser launches gnome desktop, how to suppress it
1,426,811,692,000
In my ~/.bashrc and ~/.profile I have some variables set to some filepaths: export MY_VAR1="/path/to/somewhere" In my ~/bin/ (which is added to my PATH) I have a few scripts that rely on those variables being set. If I run those commands from the terminal, they work as expected. However, if I try to double click on a script in Nautilus and run it, it runs as if those variables were not set. Same thing happens if I add one of the scripts to Gnome's "Startup Applications" using the GUI utility or if I add them to the Gnome menu using the "Main Menu" GUI utility. I would've thought that since I included these variables in my ~/.profile, which is run at login that gnome and nautilus and processes spawned by them would have access to those variables. Both Gnome and Nautilus are run under my login user. All my scripts in ~/bin have the bash shebang at the top. I am new to bash scripting, sorry if I am missing something obvious. I am using Debian Wheezy and Gnome3.
That is because a starting X session never reads your ~/.bashrc and ~/.profile. Usually, the desktop manager is started as root or its own user from an init script. The resulting process usually has the environment of the init process when it hits the desktop manager starting script. (I will not talk about less established init implementations at this point.) After login it spawns a child process, which inherits just that environment. The child process drops privileges to your uid and runs /etc/X11/Xsession, which usually simply runs all the scripts in /etc/X11/Xsession.d. These scripts usually either set environment variables, or, specifically modify the invocation of the desktop environment. In that directory you may find a file like 40x11-common_xsessionrc on Debian systems, which sources your ~/.xsessionrc. The last file in /etc/X11/Xsession.d will start your desktop environment. All your GUI processes will be spawned from this process, thus inherit the environment set up through /etc/X11/Xsession.d and consequently your ~/.xsessionrc. ~/.xsessionrc is a script file, which may source ~/.bashrc but that's really bad style, because then your DE sources it, the terminal process inherits that environment and then bash sources ~/.bashrc again, which may have unwanted side effects. However, it is totally acceptible to have a ~/.myenvironmentvariables, which contains stricly (environment) variable definitions and is sourced by ~/.bashrc and ~/.xsessionrc. If you do that, all your processes will inherit the variables specified in ~/.myenvironmentvariables, especially the shell scripts you double click in Nautilus.
Bash scripts ran from from gnome/nautilus don't have environment variables
1,426,811,692,000
Is there any tool to set appearance for GNOME Debian 7.2.0? I feel title bar is too thick and font is too big. I'm just leaving Ubuntu for Debian, so I'm not so familiar with it.
There are several things you can do to improve the title bars in GNOME 3. 1. padding The setting for the padding is controlled in this metacity XML file, /usr/share/themes/Adwaita/metacity-1/metacity-theme-3.xml. Open a terminal window $ sudo sed -i "/title_vertical_pad/s/value=\"[0-9]\{1,2\}\"/value=\"0\"/g" \ /usr/share/themes/Adwaita/metacity-1/metacity-theme-3.xml Hit Alt+F2 type restart hit Enter Example before           after           2. gnome-tweak-tool This tool allows you to customize the font that should be used for the title bar. $ gnome-tweak-tool screenshot              3. dconf-editor You can also change it using dconf-editor. $ dconf-editor Then navigate the hierarchy like so: org > gnome > desktop > wm > preferences :: titlebar-font screenshot                 4. gsettings You can use the get and set commands to gsettings to find out what title bar info is being used. get setings $ gsettings get org.gnome.desktop.wm.preferences titlebar-font 'Cantarell Bold 8' set settings $ gsettings set org.gnome.desktop.wm.preferences titlebar-font 'Cantarell Bold 10 $ References Gnome 3 Massive Title Bar How to resize font size on window title bar on gnome?
Can I set appearance for GNOME Debian?
1,426,811,692,000
I am seeing a horrible battery life with Fedora 15 (lovelock) with Gnome Shell 3 on my laptop. I keep the screen brightness, back light pretty low. I still get about 1 hr 50 minutes battery life out of it after a full charge while just browsing. I also got a brand new battery from lenovo but no luck. I tried the workaround mentioned here — booting with pcie_aspm=force — but that did not help any. It is a Lenovo T420s with a 6 cell battery. The kernel version is 2.6.40-4.fc15.x86_64 and CPU is Intel® Core™ i5-2540M CPU @ 2.60GHz. Kernel config can be found here. Is this pretty much what everyone else is seeing? Is it something with Fedora 15? Should I downgrade to Fedora 14? Are there any specific packages I can remove to make the battery life better? I think I should be able to get around 3 to 4 hours with a 6 cell battery - less than 2 hours sounds very low. Here are paste bin links to power top wakeup stats and tunables stats. FYI - I found this link to be an excellent source for tips on reducing power usage. I am going to follow some of the advices posted there.
The program powertop should help you identify the problem. $ sudo yum -y install powertop $ sudo powertop Look at the various output, and then arrow-key over to the rightmost "tab", Tunables. Look at the things which are "bad", and press enter to fix them. Also, on the first Overview screen, look for any egregiously bad processes that might be causing wake-ups.
How can I improve battery life in Fedora 15?
1,426,811,692,000
I'm using Arch Linux with Gnome 3.6 installed. There are several users on this PC with their own accounts. We used to use just switch user button instead of logging out. So almost always several users are logged in in our PC with their own set of running apps and etc. I want to switch to Awesome and I want to save this. I want to be able to switch from my Awesome session to other user Gnome session without logout from my session. I want to use gnome-screen saver as screen saver in my Awesome WM session. And that's all. It is only 2 things that I want to save from Gnome. Is it possible? What is the best practice for setting such things up?
I am using Fedora linux. Most people in our household use Gnome3 but I use Xmonad (which is similar to awesome, but better). This is no problem, as I have Xscreensaver running. When Xscreensaver is started and saving the screen and you move the mouse, there are two options below the password entry field: New Login and OK. The last is for accepting the password to unlock the screensaver. The other one starts GDM on a new VT. All of this worked out of the box. I just installed Fedora, then Xmonad and Xscreensaver. And I’ve set the option to lock the screen if Xscreensaver saves the screen. Because otherwise you don’t have the option for a new login but just quit the screensaver on mousemovement. Maybe this is similarly easy to configure in Arch linux. Or maybe you could just crib from Fedora (or from a Fedora forum or ask.fedoraproject.org). I did not try if this works with Gnome-Screensaver somehow. But Xscreensaver anyway fits better to Xmonad.
One PC, several users, Gnome 3 and Awesome. How to easy switch users via GDM
1,426,811,692,000
In Wikipedia is written that Gnome Shell in Gnome 3 uses Mutter window manager. But ps x | grep mutter shows that Mutter is not running. Moreover I had experience with working Gnome Shell before I installed Mutter. Does Gnome Shell really use Mutter? Which WM are used and which can be used with Gnome Shell?
Yes, mutter is used by gnome-shell but it's used as a library. The mutter binary is just a tiny program that links against libmutter. You could try like this: lsof | grep mutter
Does Gnome Shell use Mutter?
1,426,811,692,000
The website https://extensions.gnome.org is supposed to be the main tool for installing and managing GNOME shell extensions. How do I enable it on NixOS 18.03? When I accessed that website with Firefox on GNOME 3, I got the following information: To control GNOME Shell extensions using this site you must install GNOME Shell integration that consists of two parts: browser extension and native host messaging application. Click here to install browser extension. See wiki page for native host connector installation instructions. So I've added pkgs.chrome-gnome-shell and pkgs.gnome3.gnome-shell-extensions to environment.systemPackages in /etc/nixos/configuration.nix, rebuilt, rebooted and installed the "GNOME Shell integration" Firefox extension offered by https://extensions.gnome.org. With that, https://extensions.gnome.org displays the error message Although GNOME Shell integration extension is running, native host connector is not detected. Refer documentation for instructions about installing connector. What am I missing?
As the longDescription for chrome-gnome-shell says, you'll have to set a specific gnome3 and a specific firefox option. To do so, include the following in /etc/nixos/configuration.nix and rebuild: nixpkgs.config.firefox.enableGnomeExtensions = true; services.gnome3.chrome-gnome-shell.enable = true; (Unfortunately, these options aren't listed on https://nixos.org/nixos/options.html) You don't have to explicitly list chrome-gnome-shell and gnome3.gnome-shell-extensions as system packages, as they will be pulled in as dependencies. The "GNOME Shell integration" Firefox extension will still have to be installed by the user through Firefox, though, as you did.
How can I install GNOME shell extensions from extensions.gnome.org through Firefox on NixOS?
1,426,811,692,000
When searching for files, I often prefer using locate (because of the speed). However, I end up opening a terminal just for that purpose and then closing it again. Not a big problem for me, but my girlfriend often forgets command names. Is there a way to have Nautilus to use mlocate for searching? Ideally, I'd love to have the results displayed separately (because a file in locatedb may no longer exist), but I'm ok if it doesn't. Failing that, is there some GUI to locate?
I've not seen a way to incorporate these results into Nautilus, but there are GUIs for search in mlocate's database. The one that I'm most familiar with is called catfish. It's generally in most of the standard distros' repos. The main website is here, titled: Catfish is a versatile file searching tool.. The project's Launchpad site is another additional resource if needed. excerpt from website Catfish is a search GUI powered by locate and find behind the scenes, with autocompletion from Zeitgeist and locate. The advanced options allow filtering by date and file type. The interface is intentionally lightweight and simple, using only GTK+. Example Search                            Results      Advanced filtering      References GTK Frontend for locate
Is there a way to have Nautilus include mlocate in the results?
1,426,811,692,000
Minimize, Maximize, Close icons are missing in my GNOME desktop of Kali Linux. However, when I click in the place they are supposed to be, they do what they are supposed to do. Weirdly, Firefox is only missing the maximize icon! This may have been caused when I tried to install xserver-xorg-input-synaptics. This apparently removed kali-desktop-gnome but I could use gnome even after running the installing synaptics. Anyway, I installed kali-desktop-gnome again (which automatically removed xserver-xorg-input-synaptics but the issue is still here. PS: I would also like to know if it is possible to install xserver-xorg-input-synaptics without removing gnome because I want to enable my touchpad tap to click (synclient tapbutton1=1) in xfce too. Edit: Minimize and Maximize options are already enabled in Gnome Tweaks. Added as per requested by @iaeiou.
Had same problem on arch. Simply reinstalled gnome-shell and updated.
Minimize, Maximize, Close icons not showing in GNOME
1,426,811,692,000
I'm used to Gnome 2 in Debian and Fedora. But recently I've been using Gnome 3 and Gnome-shell (3.0.2). Today I noticed I wasn't able to find the About Gnome dialog. It's been helpful in the past to pull it up to see what version of Gnome I'm running, and see some attribution information. So, questions: Where does the About Gnome dialog live in Gnome 3 / Gnome-shell? If it has been removed, was this a Gnome decision, or my distro (fedora)? Are there relevant software license requirements about attribution that is user-facing?
System settings > System > System info (or Details on some distros). On all distros, in terminal: gnome-control-center info As far as I understand from Gnome's IRC channel, it is an upstream decision.
Where is the "About Gnome" dialog in gnome-shell?
1,426,811,692,000
Every time I boot my PC Ubuntu keeps dropping me to TTY 1 where I have to log in and then do sudo lightdm start just to log in again, which is very annoying I have already tried removing and re-adding it to update-rc.d update-rc.d lightdm defaults but it just does not work. Anyone got an idea which logfiles to check or what to do get it working again? I use Mint 12 with Gnome3.
This is how I fixed this problem: first you need to stop lightdm if it's running sudo service lightdm stop then you need to x server to create a fresh xorg.conf, I did this by renaming my old one sudo mv /etc/X11/xorg.conf /etc/X11/xorg.old then I deleted my current drivers sudo aptitude remove --purge nvidia-current IMPORTANT if you had or have drivers from the Nvidia site then you need to uninstall them as well. That means you will have to download them again if you dont have the .run file anymore and then do [nvidia-installer] --uninstall where nvidia-installer is the installer you just downloaded. then you properly install the current drivers sudo aptitude install nvidia-current the next step would be to type startx and hope for Gnome2 (or the default window manager of your distribution) to come up which worked for me. The reason for this error seemed to be some kind of conflict with X11 and the Nvidia drivers. While on boot time I got the error that the Nvidia Kernel module could not be loaded, I still was able to start lightdm once I was in TTY1. The cause for this might have been that I previously had the 290 version of the Nvidia drivers installed and then downgraded to nvidia-current (280) via aptitude which might caused some leftovers to remain and conflict with the older drivers (290 vs 280). Note that you will have to reconfigure your desktop environment after applying these steps. If you don't get a graphics accelerated UI (ie Gnome3, Unity 3D) run sudo nvidia-xconfig
Lightdm won't start automatically on boot
1,473,066,700,000
I have a script that starts my vagrant machine, opens up multiple terminals and connects to the vagrant machine via ssh in every newly opened terminal. My problem is that I need about five terminals, and I don't want to type in the password for each terminal manually. Is there a way to get prompted for the password only once in the main terminal, and use the same password for the ssh command? #!/bin/bash cd /home/kkri/public_html/freitag/vagrant vagrant up for run in $(seq 1 $1) do gnome-terminal --window-with-profile=dark -e "ssh vagrant@localhost -p 2222" --$ done gnome-terminal --window-with-profile=git clear echo "~~~ Have fun! ~~~"
In general (ignoring vagrant or other system-specific details) your best bet is to set up authentication with SSH keys, and run ssh-agent. Then open the ssh sessions with something like: # load the key to the agent with a 10 s timeout # this asks for the key passphrase ssh-add -t10 ~/.ssh/id_rsa for x in 1 2 3 ; do ssh .... done Or, if you can't use keys, you could rig something up with sshpass. read -p "Enter password: " -s SSHPASS ; echo for x in 1 2 3 ; do sshpass -e ssh ... done unset SSHPASS Though with the terminal in the middle, this would leave the password set in the terminal's environment. To work around that, you could save the password temporarily in a file: read -p "Enter password: " -s SSHPASS ; echo PWFILE=~/.ssh/secret_password cat <<< "$SSHPASS" > "$PWFILE" unset SSHPASS for x in 1 2 3 ; do sshpass -f "$PWFILE" ssh ... done shred --remove "$PWFILE" This still isn't optimal since there's a chance the password hits the disk, so keys would be better.
How to type in password for multiple windows?
1,473,066,700,000
I cannot find where I can set keyboard shortcut for switching languages. Update: New problem: I cannot set Alt+Shift combination for that.
I don't use Cinnamon so this might not work for you, but in vanilla Gnome 3.6 you could do this either via terminal: gsettings set org.gnome.settings-daemon.peripherals.keyboard input-sources-switcher alt-shift-l or via dconf-editor, navigating to org > gnome > settings-daemon > peripherals > keyboard and entering alt-shift-l as a value for the input-sources-switcher key: In Gnome 3.8 they have re-added this feature to Settings > Keyboard > Shortcuts, via an additional section called Typing:
Gnome3/cinnamon set keyboard shortcut
1,473,066,700,000
In Xfce, we can hold the Alt key, and use the left mouse button to move the window, or use the right mouse button to resize the window. Similarly, in elementary OS there is the Super key, but in GNOME, how do you set the Super key to drag or resize window?
Run GNOME Tweaks, go to the “Windows” section, and choose your favourite action key next to the “Window Action Key” entry: Pressing the action key will allow you to move windows (using the main mouse button) and resize them (using the middle mouse button).
In GNOME, how to move and resize window using one hotkey like Xfce (Alt) or elementary OS (Super)?
1,473,066,700,000
I've built the entire Xserver from git for testing proposes using the build.sh provided by freedesktop.org as the easier method to compile all modules against the git tree, and installed under the /opt/xorg path. The problem is that I can't find how gdm decides from where to load the Xserver and related binaries. I've read on the X.org site the section: 'Actually running the conformance tests', but the scripts/helpers that I could use returns a 404. Although I know where the Xorg executable is and its links, I'm not sure that will be enough to make everything work as expected, as I want to test the Xserver built and installed in the custom path. I'm using Debian 7.0 and GDM 3.4.1. Any other method could be used too?
Answer in 2 words: The location of Xserver for GDM is hard-coded at compile time in configure.ac, line 1199 in X_SERVER variable and can't be configured. So, may be you could play with symlinks, linking /usr/bin/Xorg (or, less probably /usr/bin/X, see this) to your build of Xserver. Details: I have a Debian 7, too and here's my process tree: |-gdm3-+-gdm-simple-slav-+-Xorg | | |-gdm-session-wor-+-gnome-session-+-bluetooth-apple---{bluetooth-apple} | | | | |-evolution-alarm---2*[{evolution-alarm}] | | | | |-gdu-notificatio | | | | |-gnome-fallback----2*[{gnome-fallback-}] | | | | |-gnome-panel-+-gnome-terminal-+-bash | | | | | | |-bash---vi | | | | | | |-bash-+-less | | | | | | | `-pstree | | | | | | |-gnome-pty-helpe | | | | | | `-3*[{gnome-terminal}] | | | | | |-iceweasel-+-plugin-containe-+-4*[gtk-gnash] | | | | | | | `-{plugin-containe} | | | | | | `-31*[{iceweasel}] | | | | | |-pidgin | | | | | `-3*[{gnome-panel}] | | | | |-gnome-screensav---2*[{gnome-screensav}] | | | | |-gnome-settings----2*[{gnome-settings-}] | | | | |-gnome-sound-app---{gnome-sound-app} | | | | |-metacity---3*[{metacity}] | | | | |-nm-applet---{nm-applet} | | | | |-notification-da---{notification-da} | | | | |-polkit-gnome-au---{polkit-gnome-au} | | | | |-ssh-agent | | | | |-tracker-miner-f---2*[{tracker-miner-f}] | | | | |-tracker-store---6*[{tracker-store}] | | | | `-3*[{gnome-session}] | | | `-2*[{gdm-session-wor}] | | `-{gdm-simple-slav} | `-{gdm3} So, Xorg is started via gdm-simple-slave. Definitly, /etc/gdm/Init/Default has nothing to do with starting Xserver, as it was said here and here. There were some indications, that it's impossible to configure, how X is started from gdm. I decided to go for source codes, which are pretty well structured. So: Go to the source codes, there is a daemon folder, which contains an INTERNALS file, explaining the structure of code. There you can read: ** GdmServer A class, used by the slave, that manages running a local X Server. So, the file we need is https://git.gnome.org/browse/gdm/tree/daemon/gdm-server.c There are several nested functions, responsible for calling X server and creating its command line arguments. The function directly responsible for running X server process is gdm_server_spawn, which spawns the X in the line 694 with glib's g_spawn_async_with_pipes. So, we're to find out, how its argv is formed. Well, in 2 words it's line 293 and we need the value of X_SERVER macro (unless you're using RedHat's systemd instead of sysVinit, but you aren't :)). Alas, this macro is seemingly formed in configure.ac, line 1199 and is hard-coded. So, it seems that the best option is to place a symlink to your build of Xserver to one of those locations.
How to make gdm3 start X installed in a different path (or running X from a personalized path)?
1,473,066,700,000
I have read all over the Internet about changing text files or running commands to change my wm but none of them work. I have looked all around the gnome lock screen for a button allowing me to change my wm but I could find none. I have installed and uninstalled i3 multiple times but I cannot get it to run. Is anyone able to help?
The best way to get i3 installed and running from a Gnome3 Desktop is, first to install i3: apt-get install i3 Other packages may also be useful: apt-get install feh xautolock xbacklight Then, in the gdm3 after selecting a user, just choose the i3 desktop. My advice is to keep as much from your GNOME desktop. For this, just add the following in your ~/.config/i3/config file: # audio controls bindsym XF86AudioRaiseVolume exec --no-startup-id pactl set-sink-volume 1 +5% bindsym XF86AudioLowerVolume exec --no-startup-id pactl set-sink-volume 1 -5% bindsym XF86AudioMute exec --no-startup-id pactl set-sink-mute 1 toggle # screen brightness controls bindsym XF86MonBrightnessUp exec xbacklight -inc 10 bindsym XF86MonBrightnessDown exec xbacklight -dec 10 # screenlock bindsym Control+Mod1+l exec gnome-screensaver-command -l # custom settings exec --no-startup-id gnome-session # GNOME session exec --no-startup-id gnome-settings-daemon # GNOME desktop settings exec --no-startup-id gnome-screensaver # GNOME screensaver exec --no-startup-id xautolock -time 10 -locker 'gnome-screensaver-command -l' # background image exec --no-startup-id feh --bg-fill /path/to/background.png
How do I change from gnome to i3 Debian 8
1,473,066,700,000
I'm trying out the secondary monitor with portrait layout, and I want to disable subpixel font antialiasing. I have both turned it off to "Grayscale" in gnome-tweak-tool and created a symlink to 10-no-sub-pixel.conf: /etc/fonts/conf.d $ ll total 8 lrwxrwxrwx 1 root root 34 Apr 9 10:37 10-no-sub-pixel.conf -> ../conf.avail/10-no-sub-pixel.conf lrwxrwxrwx 1 root root 39 Apr 9 10:50 11-lcdfilter-default.conf -> ../conf.avail/11-lcdfilter-default.conf lrwxrwxrwx 1 root root 39 Dec 11 22:51 20-fix-globaladvance.conf -> ../conf.avail/20-fix-globaladvance.conf lrwxrwxrwx 1 root root 39 Dec 11 22:51 20-unhint-small-vera.conf -> ../conf.avail/20-unhint-small-vera.conf lrwxrwxrwx 1 root root 36 Dec 11 22:51 30-metric-aliases.conf -> ../conf.avail/30-metric-aliases.conf lrwxrwxrwx 1 root root 33 Dec 11 22:51 30-urw-aliases.conf -> ../conf.avail/30-urw-aliases.conf lrwxrwxrwx 1 root root 30 Dec 11 22:51 40-nonlatin.conf -> ../conf.avail/40-nonlatin.conf lrwxrwxrwx 1 root root 27 Dec 11 22:51 45-latin.conf -> ../conf.avail/45-latin.conf lrwxrwxrwx 1 root root 31 Dec 11 22:51 49-sansserif.conf -> ../conf.avail/49-sansserif.conf lrwxrwxrwx 1 root root 37 May 18 2011 50-enable-terminus.conf -> ../conf.avail/50-enable-terminus.conf lrwxrwxrwx 1 root root 26 Dec 11 22:51 50-user.conf -> ../conf.avail/50-user.conf lrwxrwxrwx 1 root root 27 Dec 11 22:51 51-local.conf -> ../conf.avail/51-local.conf lrwxrwxrwx 1 root root 27 Dec 11 22:51 60-latin.conf -> ../conf.avail/60-latin.conf lrwxrwxrwx 1 root root 38 Mar 28 2012 65-droid-sans-fonts.conf -> ../conf.avail/65-droid-sans-fonts.conf lrwxrwxrwx 1 root root 35 Dec 11 22:51 65-fonts-persian.conf -> ../conf.avail/65-fonts-persian.conf lrwxrwxrwx 1 root root 30 Dec 11 22:51 65-nonlatin.conf -> ../conf.avail/65-nonlatin.conf lrwxrwxrwx 1 root root 29 Dec 11 22:51 69-unifont.conf -> ../conf.avail/69-unifont.conf lrwxrwxrwx 1 root root 41 Jan 4 11:14 70-yes-bitmaps.conf -> /etc/fonts/conf.avail/70-yes-bitmaps.conf lrwxrwxrwx 1 root root 31 Dec 11 22:51 80-delicious.conf -> ../conf.avail/80-delicious.conf lrwxrwxrwx 1 root root 31 Dec 11 22:51 90-synthetic.conf -> ../conf.avail/90-synthetic.conf -rw-r--r-- 1 root root 366 Sep 27 2011 99pdftoopvp.conf -rw-r--r-- 1 root root 959 Jun 28 2011 README But the fonts still get antialiased to RGB: Edit: Here's xrdb -query output: ~ $ xrdb -query *background: #002b36 *color0: #073642 *color1: #dc322f *color10: #586e75 *color11: #657b83 *color12: #839496 *color13: #268bd2 *color14: #93a1a1 *color15: #fdf6e3 *color2: #b58900 *color3: #cb4b16 *color4: #2aa198 *color5: #6c71c4 *color6: #859900 *color7: #eee8d5 *color8: #002b36 *color9: #d30102 *cursorColor: #93a1a1 *customization: -color *fadeColor: #002b36 *fading: 40 *foreground: #657b83 *pointerColorBackground: #586e75 *pointerColorForeground: #93a1a1 Xft.antialias: 1 Xft.dpi: 96 Xft.hinting: 1 Xft.hintstyle: hintmedium Xft.rgba: none
This should work without the need to symlink 10-no-sub-pixel.conf. If xrdb -query confirms that your settings are OK: Xft.rgba: none then most likely a hidden config file (like fonts.conf) overrides your settings. Possible locations: ~/.config/fontconfig/fonts.conf ~/.config/fonts.conf ~/.fonts.conf
Turning off subpixel antialiasing in Gnome 3 on Debian
1,473,066,700,000
I have a problem adjusting my laptop's brightness. This is a hardware problem but I can solve it with ccsm, but other programs do not work for me, e.g., xgamma, etc. Now I am running Fedora 15 and Gnome3 I cannot use compiz: is there another solution?
OK, I found a way to solve this problem on Acer with Fedora 15 (thanks to Fedora forums and answers here): Update the BIOS to the lastest version. Edit /etc/Xorg/xorg.conf to add the following line under Section "Device": Option "RegistryDwords" "EnableBrightnessControl=1" Edit /boot/grub/grub.conf to add the parameters acpi_backlight=vendor acpi_osi=Linux on the kernel command line (at the end of the line that looks like linux /vmlinuz root=/dev/sda1 ro). Reboot.
My laptop cannot adjust brightness
1,473,066,700,000
What are the benefits to running awesome as my window manager in Gnome 3? I am interested in identifying what features/functionality gnome3+awesome provides that can not be easily (if not identical) replicated running awesome all by itself.
Gnome provides services (such as Gnome keyring, GConf, PolicyKit integration, etc.) that some programs use as well as additional features like theme application and application autostarting. If you use programs that make use of those services and you don't have Gnome, you may miss out on some functionality. Depending on what you use, it might be critical, or you might never miss it.
What are the benefits of running Gnome 3 + awesome compared with awesome alone?
1,473,066,700,000
I am running Debian Stretch 9.1 with GNOME 3 as the desktop environment and GDM for session management. I tried GNOME on Wayland from GDM (gear icon) and it works very well. I would now like to configure an autologin to GNOME on Wayland. I am able to log into GNOME on Wayland by default without autologin. I am able to autologin but only on GNOME on X. The latter is my current configuration. Any pointers would be very much appreciated. What didn't work After reading Q&As from other distros I tried adding the following to /etc/gdm3/daemon.conf in the daemon section (one at a time). None of these options works. DefaultSessions does not appear to be an option in /usr/share/gdm/gdm.schemas. DefaultSession=gnome-wayland.desktop DefaultSession=gnome-wayland DefaultSession=/usr/share/wayland-sessions/gnome-wayland.desktop System info $ cat /var/lib/AccountsService/users/marc [User] Language=en_US.UTF-8 XSession=gnome-wayland SystemAccount=false $ ls /usr/share/xsessions/ gnome-classic.desktop gnome.desktop $ ls /usr/share/wayland-sessions/ gnome-wayland.desktop $ cat /etc/gdm3/daemon.conf [daemon] AutomaticLoginEnable = true AutomaticLogin = marc The contents of /usr/share/xsessions/gnome.desktop and /usr/share/wayland-sessions/gnome-wayland.desktop only differ in the Name parameter. The other parameters (except Comment) are as follows. Exec=gnome-session TryExec=gnome-session Icon= Type=Application DesktopNames=GNOME
The configuration is correct. Autologin should log a user into their previous session, it is not a parameter. However there is a bug in gdm3 which prevents it from working as expected. Debian: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=851754 GNOME (upstream): https://bugzilla.gnome.org/show_bug.cgi?id=781825 The bug is fixed upstream: https://bugzilla.gnome.org/attachment.cgi?id=350650&action=diff. It is released in GNOME 3.25.3, but Stretch is at 3.22.3. Fortunately the patch applies cleanly on 3.22.3. I built a patched gdm3. Instructions: https://github.com/marcv81/stretch-builder/tree/gdm3 Binaries: https://github.com/marcv81/stretch-builder/releases/tag/gdm3_3.22.3-3fix1 The patched packages do fix the bug indeed. I can autologin with GNOME on Wayland without any configuration change.
Debian Stretch: How do I make Wayland the default?
1,473,066,700,000
OS: GNOME 3.30.2 on Debian GNU/Linux 10 (64-bit) My laptop has no output from the HDMI port. The monitor shows "NO INPUT DETECTED". Previously I had Kubuntu installed and before that I had windows 10, Both worked fine, which means this is not a hardware issue. I have tried: Using the package "ARandR" to scan for new displays. Plugging in different monitors and HDMI cords. Booting the machine with the display plugged in. SPECS: LAPTOP: Acer Nitro 7 (AN715-51) GPU: GeForce GTX 1650 CPU: Intel Core i7-9750H Output of xrandr: Screen 0: minimum 320 x 200, current 1920 x 1080, maximum 8192 x 8192 eDP-1 connected primary 1920x1080+0+0 (normal left inverted right x axis y axis) 344mm x 193mm 1920x1080 60.01*+ 60.01 59.97 59.96 59.93 1680x1050 59.95 59.88 1600x1024 60.17 1400x1050 59.98 1600x900 59.99 59.94 59.95 59.82 1280x1024 60.02 1440x900 59.89 1400x900 59.96 59.88 1280x960 60.00 1440x810 60.00 59.97 1368x768 59.88 59.85 1360x768 59.80 59.96 1280x800 59.99 59.97 59.81 59.91 1152x864 60.00 1280x720 60.00 59.99 59.86 59.74 1024x768 60.04 60.00 960x720 60.00 928x696 60.05 896x672 60.01 1024x576 59.95 59.96 59.90 59.82 960x600 59.93 60.00 960x540 59.96 59.99 59.63 59.82 800x600 60.00 60.32 56.25 840x525 60.01 59.88 864x486 59.92 59.57 800x512 60.17 700x525 59.98 800x450 59.95 59.82 640x512 60.02 720x450 59.89 700x450 59.96 59.88 640x480 60.00 59.94 720x405 59.51 58.99 684x384 59.88 59.85 680x384 59.80 59.96 640x400 59.88 59.98 576x432 60.06 640x360 59.86 59.83 59.84 59.32 512x384 60.00 512x288 60.00 59.92 480x270 59.63 59.82 400x300 60.32 56.34 432x243 59.92 59.57 320x240 60.05 360x202 59.51 59.13 320x180 59.84 59.32 Output of xrandr --listproviders: Providers: number : 1 Provider 0: id: 0x43 cap: 0xf, Source Output, Sink Output, Source Offload, Sink Offload crtcs: 3 outputs: 1 associated providers: 0 name:modesetting Output of lspci -nn | grep VGA: 00:02.0 VGA compatible controller [0300]: Intel Corporation UHD Graphics 630 (Mobile) [8086:3e9b] 01:00.0 VGA compatible controller [0300]: NVIDIA Corporation Device [10de:1f91] (rev a1) Output of aplay -l: card 0: PCH [HDA Intel PCH], device 0: ALC255 Analog [ALC255 Analog] Subdevices: 0/1 Subdevice #0: subdevice #0 Output of lshw -c video: *-display description: VGA compatible controller product: NVIDIA Corporation vendor: NVIDIA Corporation physical id: 0 bus info: pci@0000:01:00.0 version: a1 width: 64 bits clock: 33MHz capabilities: pm msi pciexpress vga_controller bus_master cap_list rom configuration: driver=nvidia latency=0 resources: irq:154 memory:a3000000-a3ffffff memory:90000000-9fffffff memory:a0000000-a1ffffff ioport:5000(size=128) memory:a4000000-a407ffff *-display description: VGA compatible controller product: Intel Corporation vendor: Intel Corporation physical id: 2 bus info: pci@0000:00:02.0 version: 00 width: 64 bits clock: 33MHz capabilities: pciexpress msi pm vga_controller bus_master cap_list rom configuration: driver=i915 latency=0 resources: irq:128 memory:a2000000-a2ffffff memory:b0000000-bfffffff ioport:6000(size=64) memory:c0000-dffff
You have a laptop with two GPUs, using Nvidia's "Optimus" technology. The low-power CPU-integrated Intel iGPU is physically wired to output to the laptop's internal display, while the HDMI output is wired to the more powerful Nvidia discrete GPU. The device ID 10de:1f91 indicates the Nvidia GPU is GeForce GTX 1650 Mobile / Max-Q. The Nvidia codename for that GPU is TU117M. The laptop may or may not have the capability of switching the outputs between GPUs; if such a capability exists, vga_switcheroo is the name of the kernel feature that can control it. You would then need to have a driver for the Nvidia GPU installed (either the free nouveau or Nvidia's proprietary driver; since the Nvidia GPU model is pretty new, the support for it in nouveau is still very much work-in-progress), then trigger the switch to Nvidia before starting up the X server. If there is no output switching capability (known as "muxless Optimus"), then you would need to pass the rendered image from the active GPU to the other one in order to use all the outputs. With the drivers (and any required firmware) for both the GPUs installed, the xrandr --listproviders should list two providers instead of one, and then you could use xrandr --setprovideroutputsource <other GPU> <active GPU> to make the outputs of the other GPU available for the active GPU. Unfortunately, the Nvidia proprietary driver seems to be able to participate in this sharing only in the role of the active GPU, so when using that driver, you might want to keep two different X server configurations to be used as appropriate. One configuration would be for using with external displays (and probably with power adapter plugged in too) with the Nvidia GPU as the active one, feeding data through the iGPU for the laptop's internal display The other configuration would be appropriate when using battery power and don't need maximum GPU performance: in this configuration, you would use the Intel iGPU as the active one, and might want to entirely shut down the Nvidia GPU to save power (achievable with the bumblebee package). If you want some select programs to have more GPU performance, you could use the primus package to use the Nvidia GPU with no physical screen attached to render graphics, and then pass the results to the Intel iGPU for display. With Kubuntu, you probably were asked about using proprietary drivers on installation and answered "yes", so it probably set up one of the configurations described above for you. But Debian tends to be more strict about principles of Open Source software, so using proprietary drivers is not quite so seamless. Generally, the combination of the stable release of Debian (currently Buster) and the latest-and-greatest Nvidia GPU tends not to be the easy way to happy results, because the Debian-packaged versions of Nvidia's proprietary drivers tend to lag behind Nvidia's own releases: currently the driver version in the non-free section of Debian 10 is 418.116, and the minimum version required to support GeForce GTX 1650 Mobile seems to be 430. However, the buster-backports repository has version 440 available. To use it, you'll need to add the backports repository to your APT configuration. In short, add this line to /etc/apt/sources.list file: deb http://deb.debian.org/debian buster-backports non-free Then run apt-get update as root. Now your regular package management tools should have the backports repository available, and you could use apt-get -t buster-backports install nvidia-driver to install a new enough version of the Nvidia proprietary driver to support your GPU.
Debian 10 [Buster]: HDMI Input Not detected