You are not logged in.
My i3 conkybar goes from working fine to only one word showing. When I reset i3 it comes back up.
Any idea why this is happening ?
My configurations are here :
Life is pleasant. Death is peaceful. It's the transition that's troublesome. Isaac Asimov - / -
Offline
Check your files on pastebin, they are not what they should be, there are 2 config files, where at least one of them should be a conky config I think.
The conky file available doesn't use JSON, is it supposed to or not?, but first check the pastebin files.
Offline
Thank You for the reply. Good point I do not have the second config listed on paste bin. I highlighted below the key configs ( as far as I know )
Any thoughts would be appreciated ![]()
i3 config --> Refers to json bar -->
bar {
status_command /media/N-Space/home/joe/.conky-i3bar
mode dock
position bottom
workspace_buttons no
tray_output none #secondary
output DVI-I-1
colors {
background #0C2A3B
statusline #87041E
########################## border # back ## text ##################################################
focused_workspace #F0720C #2C82B0 #ffffff
active_workspace #F0720C #ffffff #1733A3
inactive_workspace #ffffff #6D8780 #ffffff
urgent_workspace #1733A3 #87041E #f4e615
}Interim Config -->
#!/bin/sh
# Send the header so that i3bar knows we want to use JSON:
echo '{ "version": 1 }'
# Begin the endless array.
echo '['
# We send an empty first array of blocks to make the loop simpler:
echo '[],'
# Now send blocks with information forever:
exec conky -c /media/N-Space/home/joe/Conky/Conky.conf/conkyrc.barConfig for the bar itself -->
out_to_x no
own_window no
out_to_console yes
background no
max_text_width 0
# Update interval in seconds
update_interval 0.5
# This is the number of times Conky will update before quitting.
# Set to zero to run forever.
total_run_times 0
# Shortens units to a single character (kiB->k, GiB->G, etc.). Default is off.
short_units yes
# How strict should if_up be when testing an interface for being up?
# The value is one of up, link or address, to check for the interface
# being solely up, being up and having link or being up, having link
# and an assigned IP address.
#if_up_strictness address
# Add spaces to keep things from moving about? This only affects certain objects.
# use_spacer should have an argument of left, right, or none
use_spacer left
# Force UTF8? note that UTF8 support required XFT
override_utf8_locale no
# number of cpu samples to average
# set to 1 to disable averaging
cpu_avg_samples 6
# Stuff after 'TEXT' will be formatted on screen
TEXT
# JSON for i3bar
[
{"full_text" : " Tunes: " , "color" : "\#00CDFF"},
{ "full_text" : "${if_mpd_playing}♪ ${mpd_artist} ♪ ->${endif}" , "color" : "\#36c941" } ,
{ "full_text" : "${if_mpd_playing}${mpd_title} ${endif}" , "color" : "\#E6D32E" },
{"full_text" : "Vol:" , "color" : "\#FFFFFF"},
{ "full_text" : "- ${exec amixer get Master | egrep -o "[0-9]+%" | head -1 | egrep -o "[0-9]*"}% -" , "color" : "\#36c941"},
{"full_text" : " -------- " , "color" : "\#FFFFFF"},
{"full_text" : " System: " , "color" : "\#36c941"},
{"full_text" : "CPU ${cpu cpu0}%${hwmon 0 temp 1}C" , "color" :
${if_match ${hwmon 0 temp 1}<60}"\#00CDFF"${else}"\ff0000"${endif} },
{ "full_text" : "RAM ${memperc}%" , "color" :
${if_match ${memperc}<90}"\#00ff00"${else}"\#ff0000"${endif} },
{"full_text" : "Net: -- ${upspeed eth0} -- Up" , "color" : "\#FFF300"},
{"full_text" : "Net: -- ${downspeed eth0} -- Dn" , "color" : "\#00ff00"},
{"full_text" : " -------- " , "color" : "\#FFFFFF"},
{ "full_text" : "${time %d/%m/%Y %H:%M}" , "color" : "\#00CDFF" },
{"full_text" : " -------- " , "color" : "\#FFFFFF"}], Life is pleasant. Death is peaceful. It's the transition that's troublesome. Isaac Asimov - / -
Offline
I am trying your config right now, and it seems to be working fine, though I only used the conky part and pasted in mine.
So, probably conky is okay. Maybe it's because you call conky from within the i3WM config, and not a loose file.
Have a look at my i3 files on GitHub, maybe it helps you, the way I did it.
Offline
Thanks for your response and help. I spent some time digging through your account. It appears you call the conky files outside of the bar function. I tried and was not working for me. You also appear to have more configuration files involved than in my system.
It appears by your listing is more complex. My set up works but around every 30-40 minutes it needs to be refreshed.
I am confused ..... I thought there was three key files.
/home/user/.i3/config -- Main Configuration file -- direct to json file
/home/user/.conky-i3bar -- json file
/home/user/conky-config-file -- The actual bar file.Any further thoughts ?
Life is pleasant. Death is peaceful. It's the transition that's troublesome. Isaac Asimov - / -
Offline
Maybe it seems to be more complex,but I guess you don't need all the files I listed there. Some are around cause they were default, and some you could use too instead of ones I used.
So, I have only conkyrc-i3 & conkyrc-w at the moment, and the one that matters is conkyrc-i3.
Yes, the way you show it, it's supposed to work.
The JSON script looks okay, and so do your conky and config.
Offline
The other day I moved a bunch of crap around in my zshrc. Well, actually I stripped a bunch of stuff, and put things in the proper places, like ~/.zshenv and ~/.zprofile instead of having it all in my zshrc. Things looked great, it was working well and then there was an update, along with it a new kernel. So I rebooted. i3 started, and boy did my i3bar look totally f*cked up.
So I evaluated the things that changed. I was going to downgrade packages, but then I thought maybe I should just try to files I modified first. I moved the new files (zshenv and zprofile) out of the way, and did a $mod+Shift+r to restart i3. Magically the i3bar returned to normal. So moving the things back I realized it was my ~/.zshenv. So I started commenting things out and it turned out to be my tty colors (or rather jasonwryan's tty colors… he's got real purdy colors). So moving those back into my zshrc and all is fine.
It should be noted that I use startx to start i3. So this is likely why this was affecting my i3bar, as it is being launched from an environment where that stuff had been sourced. But it didn't make a lick of sense to me why it would be okay in the zshrc and not the zshenv…
Anyway, the point of this story is that I have found that some really random and odd things can affect that JSON conky bar. So you might need to look in places you didn't really expect. I was just lucky I knew precisely what had changed.
So have you made any changes that might have caused this? Or I guess I should start with the question of whether or not this has ever worked correctly. Then if it hasn't, has anything changed?
Offline
Hmmz, I didn't know JSON was so 'sensitve', but I guess tath is with all mis configured configs/dots, they can break or f*ck other programs too.
That file '.zshenv' is made for paths, for external programs, I don't use it myself right now, but there is a nice piece on sourceforge about that.
Don't you have a backup lying around?, then add parts one by one to see what breaks things, starting with an empty i3 config, than add everything, shouldn't take that long either.
I always backup before I try a new config, so I can put all back if it really went bad, never really needed, but you never know,
Offline
Thanks for everyone's input. This issue has always been their since my install. I have become a enthusiast of modifying my environment for a bit so my
~.Xdefaults
~.bashrc
~.i3/config as well as the
4 conky windows / bars
I run have received quite a few updates over the past few months but the same behavior is their.
I get the sense it will be like go through a bowl of spaghetti trying to find the one strand..... :-(
.......mod + r .....not that hard though .......hmmmm...
Life is pleasant. Death is peaceful. It's the transition that's troublesome. Isaac Asimov - / -
Offline
Yes, it may be good practice, to walk trough all of these, comparing with the wiki, for rightness sake.
Maybe there are still commands in your configs, or old pieces not working anymore.
This I would do in your position.
WonderWoofy is right yeah, that faulty configs in one can screw another...
Offline
You didn't answer my question of whether or not this behavior is a new development or if it has always been kind of wonky this way.
@qinohe,
I don't know that it is JSON in particular. But I did do a test with my regular i3bar/i3status setup that i still have ready to go, and it worked just fine with the tty colors in the .zshenv. So it could be conky combined with JSON, it could be conky combined with i3bar, who knows…
Also, the zshenv can be used for the PATH variable, but it is really (as its name suggests) for setting up the environment of your shell. So typically this would include environemnt variables, like LC_COLLATE=c or BROWSER=/usr/bin/dwb or EDITOR=/usr/bin/vim etc.
To me, the colors of the TTY (since there is no TTY config file like .Xresources or an $XDG_CONFIG_HOME) are considered part of the environment. So what really confuses the shit out of me is that when I move the same block of text from the .zshenv ro the .zprofile or the .zshrc, it works fine. <-Perplexed…
Offline
It has always been there.
Thanks for everyone's input. This issue has always been their since my install. I have become a enthusiast of modifying my environment for a bit so my
~.Xdefaults
~.bashrc
~.i3/config as well as the
4 conky windows / barsI run have received quite a few updates over the past few months but the same behavior is their.
I get the sense it will be like go through a bowl of spaghetti trying to find the one strand..... :-(
.......mod + r .....not that hard though .......hmmmm...
Life is pleasant. Death is peaceful. It's the transition that's troublesome. Isaac Asimov - / -
Offline
@WonderWoofy, he says that it has been wonky a long time, post #9
Yeah, I guess te things you name are what it's for, but not colors, even if they are environmental variables, and worked for you in some situation.
I mean it's not default to put it there, I get a feeling you sometimes use the screwdriver, to yam a nail in the wall
, although, I agree to some point, " you use the tools where you need them for, not what they're made for"
Last edited by qinohe (2013-08-25 16:02:59)
Offline
@jv2122,
Sorry I missed that part. So if this has always been the case, might I ask what is the one word that is displayed. In the picture you provided in the first post it would seem that that is your i3bar/conky working as it should. When setting up my network section to use the ${if_up} statement, I noticed that when I formatted something ever so slightly wrong, it would freak out on me and then show only up to where the IP address should have been, cutting the rest off. So maybe whatever is after that first word is where the configuration is screwy.
I noticed that the first thing in your conky config is actually an if statement. So I wonder if you might enjoy a bit more consistency if you tried taking that part out (just for debugging). Have you tried shifting your conky config around and whatnot to see if you can make the behavior change in that way?
@qinohe,
I try to do things what I deem sane and correct. But if I don't know for certain what the correct way to do something is, I will just use whatever works while I try to figure it out. This was one of those cases, as that same section had been happily living in my zshrc for some time. So this was really just a case in which I was actually trying to put things in the right places.
I had actually just uninstalled grml-zsh-config in order to actually implement my own environment. So this is why I was shifting things around, as suddenly I had a bit mor to actually include in my configs.
Offline
@jv2112,Looking at your config again, you can't make things work like you do right now, you're screwing with conky's rules.
If you want to make the Up/Down part work, you really need to consider something like this, hope this helps.
{"full_text":"Net--","color":"\#888888"},\
{"full_text":"${downspeed eth0}","color":"\#00ff00"},\
{"full_text":"--Down","color":"\#888888"},\
{"full_text":"Net--","color":"\#888888"},\
{"full_text":"${upspeed eth0}","color":"\#FFF300"},\
{"full_text":"--Up","color":"\#888888"},\@WonderWoofy, You're absolutely right about trying what works, it can be a daunting quest, to make things work. I was kidding a little too, since you mostly manage to solve you're issues I think!
Now I almost always create the config from scratch, so I now what is there, and I learn how to address the tool in a relative short time/
So tools like grml-zsh-config, wich I never used, mostly stay unnoticed, cause I don't look for them in the first place.
I run zsh for about a year now, I like it very much so far.
Offline
Updated per bot of the suggestions. Got my fingers crossed.
Thanks for the help.
[
{"full_text" : " Tunes: " , "color" : "\#00CDFF"},
{ "full_text" : "♪ ${mpd_artist} ♪ -->" , "color" : "\#36c941" } ,
{ "full_text" : "${mpd_title}" , "color" : "\#E6D32E" } ,
{"full_text" : "Vol:" , "color" : "\#FFFFFF"},
{ "full_text" : "- ${exec amixer get Master | egrep -o "[0-9]+%" | head -1 | egrep -o "[0-9]*"}% -" , "color" : "\#36c941"},
{"full_text" : " -------- " , "color" : "\#FFFFFF"},
{"full_text" : " System: " , "color" : "\#36c941"},
{ "full_text" : "CPU ${cpu cpu0}%${hwmon 0 temp 1}C" , "color" : "\#00CDFF" } ,
{ "full_text" : "RAM ${memperc}%" , "color" : "\#00ff00"},
{"full_text":"Net:","color":"\#FFF300"},\
{"full_text":"${downspeed eth0}","color":"\#FFF300"},\
{"full_text":"-->Down","color":"\#FFF300"},\
{"full_text":"Net:","color":"\#00FF00"},\
{"full_text":"${upspeed eth0}","color":"\#00ff00"},\
{"full_text":"-->Up","color":"\#00ff00"},\
{"full_text" : " -------- " , "color" : "\#FFFFFF"},
{ "full_text" : "${time %d/%m/%Y %H:%M}" , "color" : "\#00CDFF" },
{"full_text" : " -------- " , "color" : "\#FFFFFF"}], Life is pleasant. Death is peaceful. It's the transition that's troublesome. Isaac Asimov - / -
Offline
After my attempt to simplify the conky script there is still no change :-(
Thanks for the efforts though. mod-R is my friend..
Life is pleasant. Death is peaceful. It's the transition that's troublesome. Isaac Asimov - / -
Offline
Hmmm, you're (simplified) conky is still running here, without problems.
I guess there is no faulty part in the JSON piece. Like I suggested earlier in this thread, it may be worth checking other configs for mis configurations.
There could be other things screwing you're conky,
Offline
Agreed qinohe. I'll have to add to the to do list when I have some time. Off to work for the week.
Thanks again.
Life is pleasant. Death is peaceful. It's the transition that's troublesome. Isaac Asimov - / -
Offline