Solarized Linux - Comment Page: 1

I like very much Ethan Schoonover Solarized color palette. So I decided write a guide, howto get Solarized colors to most commonly used Linux terminals (Gnome-Terminal, Konsole, XFCE Terminal, Mate-Terminal), Text editors (Gedit, Vim) and IDEs (Eclipse, NetBeans). These are not my projects, so the greatest honor belongs, of course, these projects owners and Ethan Schoonover. 1. Install Needed Tools (git, mercurial, 7-zip) 2. Create and Change to Solarized Directory 3. Solarized Terminals 3.1 Solarized Gnome-Terminal 3.2 Solarized Konsole 3.3 Solarized Terminal (XFCE Terminal) 3.4 Solarized Mate-Terminal 4. Solarized Editors 4.1 Solarized Gedit 4.2 Solarized Vim 5....

55 comments on “Solarized Linux - Comment Page: 1

1 2 3
    1. i got the following error:_ :( when i type gnome-terminal-colors-solarized/set_dark.sh same for *_light.sh

      (gconftool-2:3501): GConf-WARNING **: Client failed to connect to the D-BUS daemon:
      Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
      Error setting value: No D-BUS daemon running

      (gconftool-2:3502): GConf-WARNING **: Client failed to connect to the D-BUS daemon:
      Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
      Error setting value: No D-BUS daemon running

      (gconftool-2:3504): GConf-WARNING **: Client failed to connect to the D-BUS daemon:
      Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
      Error setting value: No D-BUS daemon running

      (gconftool-2:3506): GConf-WARNING **: Client failed to connect to the D-BUS daemon:
      Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
      Error setting value: No D-BUS daemon running

      (gconftool-2:3508): GConf-WARNING **: Client failed to connect to the D-BUS daemon:
      Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
      Error setting value: No D-BUS daemon running

      (gconftool-2:3509): GConf-WARNING **: Client failed to connect to the D-BUS daemon:
      Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
      Error setting value: No D-BUS daemon running

      Reply
      • Hi arshperrst,

        Could you tell more about your system, what os and version you are running?

        And did you run this command when Gnome-Desktop is running on Gnome-Terminal?

        You can post also output of following commands:

        
        uname -a
        
        lsb_release -a
        
        gnome-terminal --version
        
        gnome-shell --version
        
        env |grep -i dbus
        
        Reply
    2. Thank you!!!!! It finally got these amazing colors. Thanks

      Reply
    3. Hello , and thanks for the guide.I have the same errors as arshperrst.

      Linux 3.4.0-sabayon #1 SMP …2012 x86_64 AMD Athlon(tm) 64 X2 Dual Core Processor 4200+ AuthenticAMD GNU/Linux

      lsb_release -a -> command not found

      GNOME 3.4.1.1
      GNOME Shell 3.4.1

      DBUS_SESSION_BUS_ADDRESS=unix:abstract=/tmp/dbus-…7,guid=…..fbe

      Thanks

      Reply
    4. Well, i found the solution to the above problem.

      You must write ” su – ” and then the “gnome-terminal-colors-solarized/set_light.sh”

      But , i can’t apply this to the terminal.I go to Configuration->Profile->Colors
      but there,at the themes ,it has only “Tango,linux console,Xterm,Rxvt,adjust”.

      What can i do?

      Reply
    5. here is my output :-

      [[email protected] mercy]# uname -a
      Linux redhat 3.5.4-1.fc17.i686 #1 SMP Mon Sep 17 15:41:12 UTC 2012 i686 i686 i386 GNU/Linux
      [[email protected] mercy]# lsb_release -a
      bash: lsb_release: command not found…
      [[email protected] mercy]# lsb_release
      bash: lsb_release: command not found…
      [[email protected] mercy]# gnome-terminal –version
      GNOME Terminal 3.4.1.1
      [[email protected] mercy]# env |grep -i dbus
      DBUS_SESSION_BUS_ADDRESS=unix:abstract=/tmp/dbus-irqZK3Gz72,guid=5c24c9e8c1a665d78551972700000033

      Reply
    6. Hi George and arshperrst,

      I just tested this Gnome-Terminal part and it works normally with GNOME Shell 3.4.2 and GNOME Terminal 3.4.1.1.

      And you don’t need be root user to set normal user terminal colors. And terminal colors change to Solarized instantly after you run script you don’t have to go to Configuration -> Profile -> Colors.

      Then back to your real problem:
      Error setting value: No D-BUS daemon running

      Still looks like that you don’t have D-BUS deamon running. Could you both post output of following commands:

      
      ps aux |grep -i dbus
      
      env |grep -i desktop
      
      Reply
    7. Hello,
      so ,i need to update to gnome shell 3.4.2?

      The output
      ps aux |grep -i dbus
      103 8265 …. ? Ss 10:36 0:00 /usr/bin/dbus-daemon –system
      geo 11368 …. ? S 10:39 0:00 /usr/bin/dbus-launch –exit-with-session /usr/bin/ssh-agent — gnome-session
      geo 11369 …..? Ss 10:39 0:00 /usr/bin/dbus-daemon –fork –print-pid 5 –print-address 7 –session
      geo 12521 ….2 pts/0 S+ 10:42 0:00 grep –colour=auto -i dbus

      env |grep -i desktop
      DESKTOP_SESSION=gnome
      GNOME_DESKTOP_SESSION_ID=this-is-deprecated

      Reply
      • Hello,

        Gnome Shell 3.4.2 is not needed. I just tested this also on CentOS Gnome-Terminal 2.31.3 and it works normally.

        Your dbus-daemon is running normally. So could you post full error message when you run following command as normal user (geo)?

        
        gnome-terminal-colors-solarized/set_light.sh
        

        You can also try following command and check errors:

        
        gnome-terminal-colors-solarized/install.sh
        

        Both scripts do the same thing, but if you use install.sh then you can select Gnome-Terminal profile also.

        Could you also post output of following command:

        
        gconftool-2 -v
        
        Reply
    8. gnome-terminal-colors-solarized/set_light.sh
      -bash: gnome-terminal-colors-solarized/set_light.sh: No such file or folder

      gnome-terminal-colors-solarized/install.sh
      -bash: gnome-terminal-colors-solarized/install.sh: No such file or folder

      gconftool-2 -v
      3.2.5

      Thanks!

      Reply
      • Hi George,

        You have run first commands just there where you clone gnome-terminal-colors-solarized.git repo or use full paths, like:

        
        /path/to/gnome-terminal-colors-solarized/set_light.sh
        
        Reply
    9. Hello,

      if i run as normal user “cd ~/solarized” it says “no such file or directory.
      Only as root i can have access to ~/solarized.And there (as root) it gives me no message when i run the command you say.

      Thanks

      Reply
      • So do you created ~/solarized directory as root user?

        Create ~/solarized directory as normal user, clone git repo and then run gnome-terminal-colors-solarized/set_light.sh?

        Reply
    10. Oh!!I missed that!I thought it was as root!
      Ok,it works fine now!

      (If i delete the ~/solarized (as root) it will clean also the clone git from there?(from root))?

      Reply
      • Excellent! :)

        Yes you can delete /root/solarized and it will clean also cloned git repo. This script only change terminal colors so even if you delete ~/solarized directory from normal user dir, you won’t lose colors from terminal until you change terminal colors manually. If you change colors manually and want restore Solarized terminal colors again, then you need set_light.sh or set_dark.sh scripts next time. :)

        Reply
    11. […] If !1 0′s Solarizer walkthroughs – this site is rapidly becoming one of my default go-tos. […]

      Reply
    12. Wow, dude. This is an amazing compilation for Solarized-happy folks. Thanks a million!

      Reply
    13. [email protected]:~$ gnome-terminal-colors-solarized/set_dark.sh
      Default is not a valid profile

      What am I doing wrong?

      Reply
      • Hi FibSaSk,

        If you check Gnome-Terminal Edit -> Profiles… what you see?

        Reply
        • Ah, embarassing newbie mistake from my part. Installed it easily on gnome-terminal, but I want to install it on xfce terminal. Any way to do that?
          There’s no Edit -> Profiles in this one.

          Reply
        • Hi JR,

          I got the same error as FibSaSk.

          I can see the default profile when I check Gnome-Terminal Edit->Profiles. Actually I want to change the color scheme in RHEL, which has a very old version of gnome terminal(2.16.0). I tried every possible ways I could find on the Internet but failed. Hope you could see this message and help me. Thanks.

          Reply
    14. Thanks a lot for posting this how-to. I added the vim, Gnome terminal and GEdit Solarized profiles without issue in Linux Mint Cinnamon 15.

      Reply
    15. I found that the xterm recipe didn’t work on Fedora 19. It seems that the profiles now have GUIDs, eg:


      $ dconf list /org/gnome/terminal/legacy/profiles:/ | grep ^: | sed 's/\///g'
      :b1dcc9dd-5262-4d8d-a863-c897e6d979b9
      :99949086-171d-4a19-a04d-679697f23ec7

      So, I used this to set one of the profiles to the dark colours:


      gnome-terminal-colors-solarized/set_dark.sh :b1dcc9dd-5262-4d8d-a863-c897e6d979b9

      Reply
      • Thanks Robin,

        You are totally right and thanks for solving this also.

        Actually looks like that, install.sh script works too. I will update this guide.

        Reply
1 2 3

Leave a Reply to Watzefak Cancel reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.

Close