Tag Info

New answers tagged

0

You need to go to extentions.gnome.org - I have to use firefox not Chrome. NetSpeed is here Click the On / Off slider, so it goes on and it will be installed: Then press Alt+F2 and type r then press enter. It should be in the top panel.


0

The problem in y our Gnome version > 3.14. They offer a link about this and how to override this problem, so I Quoted from I'm using GNOME 3. Why can't I install extensions? If you are using GNOME 3.4 or newer and installation still doesn't work, check to make sure that the "GNOME Shell Integration" plugin is installed and enabled in your browser ...


0

You can try Pressing windows(button next to left ctrl) + L which also locks the computer. It works for me, hopefully help you as well.


1

You could use the GSettings configuration tool. Open a terminal and fire this command: gsettings set org.gnome.settings-daemon.plugins.media-keys screensaver "<Ctrl><Alt>l" The default value is <Super>l


0

The option has been renamed to "Icons on Desktop". Flip this to off to find your background as set by Nitrogen.


0

If you're using an Nvidia card go to Nvidia settings (from terminal: nvidia-settings ) and then in X Screen -> Antialiasing Settings uncheck "Enable FXAA". After restarting gnome it should work correctly.


0

I too had this error although I encountered it after a week of flawless OpenVPN usage. I found an obscure idea to restart the dbus service in Ubuntu. sudo service dbus restart It might be wise to concat another command to this command to restart your GUI since a power button reboot was necessary for me after I executed this command


1

You can set the Keyboard Shourtcut for locking the screen and other operation in the keyboard settings:


0

TL;DR There is no way to use the border of a window. You can only use the title bar. Open a terminal an use this command: gsettings set org.gnome.desktop.wm.preferences action-double-click-titlebar toggle-maximize-vertically Check the settings with: gsettings get org.gnome.desktop.wm.preferences action-double-click-titlebar Or you can try the other ...


0

Not for the border, but for the titlebar. gnome-tweak-tool will let you do this: https://apps.ubuntu.com/cat/applications/gnome-tweak-tool/


0

You will have this error if using XRDP. You need to login directly to Xwindow from KVM.


2

It's a bug. Therefore a simple hack: sudo rm -f /usr/share/dbus-1/services/org.freedesktop.Telepathy.Client.AbiCollab.service This file is created by abiword-common. Source


1

TL;DR The way is a little bit tricky: You can reload and so influence the order the extensions. Use this command and replace <Extension_UUID> with the UUID of the extension, don't use the ID: gdbus call --session --dest org.gnome.Shell --object-path /org/gnome/Shell --method <Extension_UUID> But I have found that sometimes the extension must ...


1

The Shell Theme option in GNOME Tweak Tool needs the User Shell Themes extension, as the mouse-over pop-up says: The extension is available at https://extensions.gnome.org/extension/19/user-themes/, or by installing gnome-shell-extensions: sudo apt-get install gnome-shell-extensions If you installed it manually, instead of using the GNOME Shell plugin ...


1

I had this same problem (It didn't always happen) and found that it's somehow related to my graphics driver. The way to solve it was to, at startup time, stay at the login screen for about 45 seconds to a minute. Something "clicks" in X.org that allows it to go into the high graphics mode and load the nice looking theme. I posted the related question over ...


0

This happens from time to time if the system detects devices like a touchscreen input but doesnt overlay ot to the given display but interprets it as an extra Display. If this is your problem - you should see a second Display in thr screen settings that could be turned off or be setup as a mirror to get rid of the "wide screen"


0

After fiddling and reading around a bit, I found a solution. It turned out the locale file was empty (the problem was the "region", rather than the "language" part), so I edited it: sudo gedit /etc/default/locale and added this to the file: LANG=en_US.UTF-8 LANGUAGE="en_US:en" LC_CTYPE="en_US.UTF-8" LC_NUMERIC="en_US.UTF-8" LC_TIME="en_US.UTF-8" ...


0

Digged more for the problem so yes its a .desktop entry problem After i edited : vim /usr/share/applications/google-chrome.desktop On the end of each config group [Desktop Entry] [NewWindow Shortcut Group] [NewIncognito Shortcut Group] Added this: ## Custom StartupWMClass=Google-chrome-stable


1

You can have a theme misconfiguration. Try this: Go to the gear cog that is on the top-right corner on the screen. Select System Settings from the menu. On the system settings, click on Appearance In the bottom-right of this window, you have a theme selector. If Ambiance is selected, select another theme. You may need to wait a few seconds until the new ...


0

I checked with my Fedora 21 install where I have Gnome 3.14.2 and it doesn't seem to be possible to set your desired value: [btegge@za21 ~]$ gsettings set org.gnome.desktop.interface scaling-factor 1.2 invalid character in number: 1.2 ^ [btegge@za21 ~]$ gsettings set org.gnome.desktop.interface scaling-factor 1,2 expected end of input: 1,2 ^ My ...


1

I have upgraded to Gnome 3.16.1 and I am no longer having this problem. I'm guessing it was fixed by this change: ======================================== gtk+ ======================================== Overview of changes in GTK+ 3.16.2 ================================== * Bug fixes: [...] 747689 [...] GtkApplication: Prevent more crashes ...


0

A partial solution, via @RCF-U14.04, is to set keyboard accelerators from the settings dialog for move to workspace 1/2/3/4


1

I believe that it's the difference between calibration and characterization profiles described here: What's the difference between calibration and characterization? More info here: Missing information for whole-screen color correction? Unfortunately, many vendor-supplied ICC profiles do not include the information required for whole-screen color ...


6

This right here is an easy fix. All you have to do is go to the software center and install Ubuntu tweak. Open that up and go to "Tweaks" Go to "Theme" In there, change the Gtk theme to whatever you like. That should fix it up no problem


3

Found an easy fix xrandr --output DVI-D-0 --mode 1920x1080 --rate 144


0

The problem appears to only happen with the i386 version of Google Chrome on a 64-bit Ubuntu system. The hint that it was a 32-bit vs 64-bit problem was that installing the :i386 version of certain packages made some errors go away. I was able to get Chrome working again by installing the 64-bit version: $ sudo aptitude install google-chrome-stable The ...


1

This was a bug in Ubuntu 14.10. Chromium was slow in graphics rendring. There is a workaround Run following command in terminal sudo xdiagnose and disable bootloader graphics, VESA framebuffer driver and PAT. See, If it works for you. for more information about this bug you can follow this link


0

You can configure your input method with im-config (start as user). Set it to none and it go away.


0

The easiest way is to use alt+F2 the type 'r' and enter. This re-starts gnome-shell in the least destructive way. Then go to System Settings keyboard click on the shortcuts tab and verify that your shortcuts are there. Any you have defined are in the custom shortcuts section. If not there, set them up again, close system settings and try each of your ...


2

I've found in the past that stringing the commands together in that manner causes issues if one of them have a "hiccup". For example, if your command is similar to this: sudo apt-get install 1 2 3 4 then, if there's an error on program 3, 4 will not install. Keeping them separate on each line fixes this issue. if there's an error, the script continues ...


1

The first part of my answer: For GTK theme error: Unable to locate theme engine in module_path: "pixmap" sudo apt-get install gtk2-engines-pixbuf:i386


1

In the beginning the necessary warning that this is a version that is in development. You can install the latest version of GNOME with two PPAs: sudo add-apt-repository ppa:gnome3-team/gnome3-staging sudo add-apt-repository ppa:gnome3-team/gnome3 Update the repostories sudo apt-get update And upgrade your system sudo apt-get upgrade To revert the ...


1

Welcome to Linux! :) You can safely omit the two dashes in list and all other actions such as get and set. The program's behavior will stay the same and i find it more comfortable to write. Finally, a quick tip: read very carefully every output you get from your machine and read a lot of man pages, especially when you are unsure about the sintax of certain ...


1

Virtual Console ctrl + alt + f1 Is a virtual console, accessed when the Ubuntu OS is loaded. (ctrl + alt + f7 to return to GUI Ubuntu) Recovery Mode - Terminal Have you tried recovery mode? When the boot options screen appears: Advanced options > ***** (recovery mode) Accessing recovery mode This will allow you to access the terminal as root, and ...


1

There might be many reasons for this problem, but it can typically be fixed by re-configuring your themes. You can start by tweaking the theme in unity-control-center and making sure it is set to Ambience. If it is, try switching the theme to a different one and back. You can also try reinstalling the themes as suggested in this answer: ...


1

1.Try to reinstall NotifyOSD sudo apt-get --reinstall install libnotify-bin notify-osd Then restart. 2.Installing Battstat Applet gives you a warning on top of all windows like this:- http://techrax.tk/wp-content/uploads/2015/05/critical_message.png To install it, do:- add-apt-repository ppa:iaz/battery-status apt-get update apt-get install ...


0

For 1st one, Try This For 2nd one, Seems like Greeter Has Been Overidden. Try to do:- sudo nano /etc/lightdm/lightdm.conf And Find a line that looks like greeter-session=xxxx to greeter-session=unity-greeter And Press F2 to save it.


0

The "problem" is with your graphics stack. Your graphics card does not support 3d, so llvmpipe makes use of your cpu (rather then your gpu). You have 2 options: Replace the graphics card. Use an alternate desktop. I have a similar card and prefer KDE, but you can try xfce, lxde, enlightenment, fluxbox ... See http://www.mesa3d.org/llvmpipe.html


0

Disable Ibus from System Settings >> Language > Input Method>"Change it from ibus to none. After that, do a killall ibus-daemon in terminal.


-3

sudo apt-add-repository ppa:gnome3-team/gnome3 sudo apt-add-repository ppa:gnome3-team/gnome3-staging sudo apt-add-repository ppa:ricotz/testing sudo apt-get update sudo apt-get dist-upgrade


2

Let's start by identifying exactly what file is causing the issue - something like $ find /usr/share -iname '*schema*' | grep gedit /usr/share/glib-2.0/schemas/org.gnome.gedit.plugins.time.gschema.xml /usr/share/glib-2.0/schemas/org.gnome.gedit.gschema.xml /usr/share/glib-2.0/schemas/org.gnome.gedit.plugins.pythonconsole.gschema.xml ...


1

Have you tryed use software-center and install tweak tool, and you run tweak tool and set the window and icons to something else, and it should look better then grey, and you should install gnome system settings, and there you can also set settings, and it might work fine this way.


0

Welcome to the world of Linux :) Now, if I understand correctly, you just mis-typed the command. Take note that it is xsetwacom --list devices (note the two minus symbols and "list devices" has a space in between). Reading your question, you might want to look up how to set a keyboard shortcut to toggle between touch on and touch off. I believe that ...


-1

If you wrote the application, you could just put a timeout on the notifications: notify-send -t 5000 "Title" "Details" If not, the only way I know of would be to restart the gnome desktop. You can do it by pushing Alt + F2, type "r" then Enter. But if you want to do it via command line: killall -3 gnome-shell Unfortunately the kill gnome option will ...


1

From this post at Linux Mint Community: "Gnome isn't extremely compatible with Linux Mint. It works but other operating systems probably work better. Ubuntu 14.04 for example. You can even download a gnome version for it. http://ubuntugnome.org/ Another operating system that is gnome-based is Fedora. Also, I haven't managed to install extensions ...


0

The latest Gnome 3 you can get on 14.04 is 3.14. In order to do that, you should add staging and testing ppa: sudo add-apt-repository ppa:gnome3-team/gnome3-staging sudo add-apt-repository ppa:ricotz/testing sudo apt-get update sudo apt-get install gnome


0

I've solved using synaptic. I've reinstalled the package gnome-session-bin and the system is running ok


1

I have the same problems after add xorg-edgers and upgrade all. I fixed it by follow command: sudo apt-get install --reinstall libgl1-mesa-glx libgl1-mesa-dri xserver-xorg-core xserver-xorg-video-nouveau Hope that will solve you problems.


0

Unfortunately, as mysteriously as the problem began, so did it end. I was forced to use Unity for a couple weeks, performed a few standard updates with apt-get, and then when I tested gnome-shell again, it worked.


0

I'm not sure exactly what I did to get lightdm to successfully start a session for me except maybe allowing anyone (not just consoles) to connect to the xserver. The gnome-shell desktop still doesn't appear when I login through lightdm while it does when using startx.



Top 50 recent answers are included