what do you think is the reason? also the offsets can be fixed, but the border issue is getting downright weird.
Printable View
what do you think is the reason? also the offsets can be fixed, but the border issue is getting downright weird.
I have the same doubts as stinkeye regarding screen resolution - why would that make a difference?
offset, voffset and goto work with "pixels" - as long as the conky window is within your resolution size it should work the same. And, like Stinkeye, I have a lot of conkys from others that work just fine, even when I changed my monitor - 1280x1024 for 1920x1080.
Generic conky calls: ie: ${nodename}, ${cpubar cpu1 20,200} et al that are common to all machines should display just fine.
Did you leave everything, the same other than M/OS I see?
Font size? - forget that, I see they are the same and monofur as well.
As for the borders ... they work here.
Yes, I use LUA for a background here, I commented it out for you.
mounted.lua is just above TEXT not being used here ... might add it though.
The conky I gave you was designed as a "Disk Activity" conky, I added the Network stuff from my daily run conky seen on the right:
I used the conky as is. Just changed the mount point addresses (/media/5 to /media/OS)
@ sbjaved
Yea, after comparinmg the images ... I figures it was just the mount point you changed, but it shows it not only "graphs" that are affected, but "bars" as well. :frown:
This one is a #-o and [-o< situation
@ sbjaved - forget the 12.10 idea. That's a bust.
@ stinkeye - WOW! The plot thickens. It has to be a desktop thing of which I do not have. Debian - SID - OpenBox - tint2 panel.
Have no idea what to say.Code:02 May 13 | 13:22:01 ~
$ s11
System: Host: sector11 Kernel: 3.8-8.dmz.1-liquorix-amd64 x86_64 (64 bit) Desktop: Openbox 3.5.0 Distro: VSIDO
Machine: Mobo: ECS model: MCP61M-M3 version: 7.0 Bios: American Megatrends version: 080015 date: 11/03/2010
CPU: Triple core AMD Athlon II X3 450 (-MCP-) cache: 1536 KB flags: (lm nx sse sse2 sse3 sse4a svm)
Clock Speeds: 1: 3214.528 MHz 2: 3214.528 MHz 3: 3214.528 MHz
Graphics: Card: NVIDIA GT218 [GeForce 210] X.Org: 1.12.4 driver: nvidia Resolution: 1920x1080@60.0hz
GLX Renderer: GeForce 210/PCIe/SSE2 GLX Version: 3.3.0 NVIDIA 313.30
Audio: Card-1: NVIDIA MCP61 High Definition Audio driver: snd_hda_intel Sound: ALSA ver: k3.8-8.dmz.1-liquorix-amd64
Card-2: NVIDIA High Definition Audio Controller driver: snd_hda_intel
Network: Card: NVIDIA MCP61 Ethernet driver: forcedeth
IF: eth0 state: up speed: 100 Mbps duplex: full mac: <filter>
Drives: HDD Total Size: 250.1GB (25.7% used) 1: id: /dev/sda model: WDC_WD2500AAJS size: 250.1GB
Partition: ID: / size: 15G used: 7.3G (53%) fs: ext4 ID: /home size: 15G used: 6.7G (48%) fs: ext4
ID: swap-1 size: 4.29GB used: 0.00GB (0%) fs: swap
Sensors: System Temperatures: cpu: 39.0C mobo: 33.0C gpu: 42C
Fan Speeds (in rpm): cpu: 1910 fan-2: 0 fan-3: 0
Info: Processes: 136 Uptime: 5:02 Memory: 538.1/5962.3MB Client: Shell (bash) inxi: 1.8.45
02 May 13 | 13:23:06 ~
$ conky --version
Conky 1.9.0 compiled Fri May 11 15:54:00 UTC 2012 for Linux 2.6.32-5-amd64 (x86_64)
Compiled in features:
System config file: /etc/conky/conky.conf
Package library path: /usr/lib/conky
X11:
* Xdamage extension
* XDBE (double buffer extension)
* Xft
* ARGB visual
Music detection:
* Audacious
* MPD
* MOC
* XMMS2
General:
* math
* hddtemp
* portmon
* Curl
* RSS
* Weather (METAR)
* Weather (XOAP)
* wireless
* support for IBM/Lenovo notebooks
* nvidia
* eve-online
* config-output
* Imlib2
* apcupsd
* iostats
* ncurses
* Lua
Lua bindings:
* Cairo
* Imlib2
02 May 13 | 13:26:28 ~
$
Is it possible to get horizontal network bar with conky for current up/down speeds that shows current speed and you can set top speeds for upload/download? If it is i would appreciate the code.
Something like simple CPU usage bar but for network speed.
Maybe these by wlourf: Bargraph widget
I found:
http://conky.sourceforge.net/variables.html
Variable execbar and it might work if i would try it but AFAIK it's better to avoid "exec" variables in conky. I will rather use numerical representation because of that.