SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Openbox (and IceWM) is an excellent WM. Does anyone know if it works well with these new high-resolution monitors? I don't have one yet but 4k looks to be the way things are going.
I cannot say for sure about those newer monitors, but here is IceWM running on Slackware64 displayed on an LG 22" monitor. The conky system monitor is in transparent mode, and I would like to mention that on my system the critical line in .conkyrc to make that happen is:
"own_window no".
Unless that is set to NO, the line "own_window_transparent yes" will not result in transparency. If "own_window" is set to YES it creates a solid window which color can be modified, but no transparency. This may differ on other systems, and I mention it because other discussions I've seen on this issue spoke of other settings, but not this one.
Hi Cabbie
Running Plasma 5 is opposite. If I set "own_window no" my screen goes all black except for the panel bar. It appears conky also crashes so changing back to "yes" is not enough. I have to restart conky... at least on Plasma 5 with KWin compositing.
FWIW this is my version of that section which does have perfect transparency, although some change, very possibly one I made, resulted in Alt-Left Mouse Drag no longer moving it around.
Code:
# Create own window instead of using desktop (required in nautilus)
own_window yes
own_window_type normal
own_window_transparent yes
own_window_hints undecorated,below,skip_taskbar
background no
own_window_argb_visual yes
own_window_argb_value 85 ##decrease for darker
maximum_width 720
Hi Cabbie
Running Plasma 5 is opposite. If I set "own_window no" my screen goes all black except for the panel bar. It appears conky also crashes so changing back to "yes" is not enough. I have to restart conky... at least on Plasma 5 with KWin compositing.
FWIW this is my version of that section which does have perfect transparency, although some change, very possibly one I made, resulted in Alt-Left Mouse Drag no longer moving it around.
Code:
# Create own window instead of using desktop (required in nautilus)
own_window yes
own_window_type normal
own_window_transparent yes
own_window_hints undecorated,below,skip_taskbar
background no
own_window_argb_visual yes
own_window_argb_value 85 ##decrease for darker
maximum_width 720
Hi enorbet,
That's interesting because I have "own_window no" and "background yes", just the opposite to yours.
I guess it all depends what you're running. Pays to keep notes over time, eh?
Have a good one.
That's interesting because I have "own_window no" and "background yes", just the opposite to yours.
I guess it all depends what you're running. Pays to keep notes over time, eh?
Have a good one.
That IS interesting! I tried switching both and there is some difference. After the screen goes black, in about a minute the desktop comes back but conky has crashed. When I try to restart conky (from cli so I can see errors) I get
Code:
conky: drawing to double buffer
conky: forked to background, pid is 9577
enorbet@homebase20:~$
X Error of failed request: BadMatch (invalid parameter attributes)
Major opcode of failed request: 130 (MIT-SHM)
Minor opcode of failed request: 3 (X_ShmPutImage)
Serial number of failed request: 442
Current serial number in output stream: 443
When I revert to my normal conky launches fine, without screen ever going black, and if I do it from CLI it launches at "conky: drawing to double buffer".
I guess I'm just too newb at LUA to figure out why.
That IS interesting! I tried switching both and there is some difference. After the screen goes black, in about a minute the desktop comes back but conky has crashed. When I try to restart conky (from cli so I can see errors) I get
Code:
conky: drawing to double buffer
conky: forked to background, pid is 9577
enorbet@homebase20:~$
X Error of failed request: BadMatch (invalid parameter attributes)
Major opcode of failed request: 130 (MIT-SHM)
Minor opcode of failed request: 3 (X_ShmPutImage)
Serial number of failed request: 442
Current serial number in output stream: 443
When I revert to my normal conky launches fine, without screen ever going black, and if I do it from CLI it launches at "conky: drawing to double buffer".
I guess I'm just too newb at LUA to figure out why.
That IS interesting! I tried switching both and there is some difference. After the screen goes black, in about a minute the desktop comes back but conky has crashed. When I try to restart conky (from cli so I can see errors) I get
Code:
conky: drawing to double buffer
conky: forked to background, pid is 9577
enorbet@homebase20:~$
X Error of failed request: BadMatch (invalid parameter attributes)
Major opcode of failed request: 130 (MIT-SHM)
Minor opcode of failed request: 3 (X_ShmPutImage)
Serial number of failed request: 442
Current serial number in output stream: 443
When I revert to my normal conky launches fine, without screen ever going black, and if I do it from CLI it launches at "conky: drawing to double buffer".
I guess I'm just too newb at LUA to figure out why.
Hi enorbet,
So, thing is our .conkyrc files are different in many more ways than just those two lines. For example your "maximum width" is set at 700 where mine is only 400. Still, all works for you when you change just the two... so I can't explain it. However just for comparison you can examine the conkyrc file I'm attaching. As you will see from the comment section it is adapted from "Neon Cipher" who also modified the original from # Copyright (c) 2004, Hannu Saransaari and Lauri Hakkarainen. But it's GPL so we are free to distribute/modify.
BTW I don't know if it is nvidia drivers but conky looks the same in Fluxbox and Xfce as it does in Plasma. There are some sort of oddities because I had to set width to 700 or fonts would drift off the right edge, which makes no sense to me whatsoever. I just played until it looked right.
BTW I don't know if it is nvidia drivers but conky looks the same in Fluxbox and Xfce as it does in Plasma. There are some sort of oddities because I had to set width to 700 or fonts would drift off the right edge, which makes no sense to me whatsoever. I just played until it looked right.
Hey! as an aside, thank you for introducing me to the "cut" command! (in your conkyrc)
I see it does things I thought only awk could do. Very handy for scripts.
Suppose this is something everybody else already knew ... lol
Cheers
Oh... you are using the old config which is deprecated years ago...
Are you up for an upgrade (1.10.8)? If so, I can try convert it to the newest one and try it out.
I've rarely been a "if it ain't broke don't fix it" guy. I'm a tinkerer so yeah I'm game especially since I am actually using conky v 1.10.8. Odd the old config works at all!
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.