You are not logged in.
Pages: 1
Question:
When I'm in OpenBox my conky's are transparent.
When I am in KDE, they are not.
Why?
Last edited by Temetka (2015-11-11 04:36:16)
The meaning of life is to just be alive. It is so plain and so obvious
and so simple. And yet everybody rushes aroound in a great panic
as if it were necessary to achieve something beyond themselves.
- Alan Watts
Offline
KDE controls the desktop background whereas openbox just displays the root window (nitrogen draws to this in BL).
Useful link:
https://wiki.archlinux.org/index.php/Co … e_with_KDE
EDIT: Sorry hhh...
:8
Last edited by Head_on_a_Stick (2015-11-07 15:25:27)
Offline
Moving to Help & Support (Other).
No, he can't sleep on the floor. What do you think I'm yelling for?!!!
Offline
Hopefully Sector11 will chime in soon. He's very knowledgeable about conky stuff.
Offline
own_window yes
own_window_transparent yes
##############################################
# Compositing and desktop environment tips:
# Conky can play strangely when used with
# different compositors. I have found the
# following to work well, but your mileage
# may vary. Comment/uncomment to suit.
# I have highlighted what i believe suitable
# for the major distros.
##############################################
## no compositor, no desktop manager (e.g. plain openbox)
# own_window_type override
# own_window_argb_visual no
## xcompmgr, but no desktopmanager
#own_window_type override
#own_window_argb_visual yes
## UBUNTU, LINUX MINT CINNAMON
## desktop manager with compositing (e.g. unity)
#own_window_type desktop
#own_window_argb_visual yes
## LUBUNTU, XUBUNTU, LINUX MINT MATE
## desktop manager without compositing (e.g. lxde, xfce)
own_window_type override
own_window_argb_visual no
###############################################
# own_window_hints undecorated,below,sticky,skip_taskbar,skip_pager
this used to be part of the default conky in crunchbang, i have since adapted it a little.
have you tried the settings for UBUNTU?
Offline
When I'm in OpenBox my conky's are transparent.
When I am in KDE, they are not.
Why?
When using the pseudo-transparency, a black background appears because KDE the background image is not writing in the root window, but a level above.
The remedy, for example the pakets:
feh >>.autostart
feh --bg-scale /home/temetka/picture.jpg
or
piv >>.conkyrc
${exec /usr/bin/qiv --root /home/temetka/picture.png}
I hope you understand my english ...
Offline
I solved it by adding ARGB values in.
# Use pseudo transparency with own_window?
own_window_transparent yes
own_window_argb_visual yes
own_window_argb_value 255
The meaning of life is to just be alive. It is so plain and so obvious
and so simple. And yet everybody rushes aroound in a great panic
as if it were necessary to achieve something beyond themselves.
- Alan Watts
Offline
When using the pseudo-transparency, a black background appears because KDE the background image is not writing in the root window, but a level above.
correct.
The remedy, for example the pakets:
feh >>.autostartfeh --bg-scale /home/temetka/picture.jpg
this only works if picture.jpg is the same that kde uses.
but why not just use real transparency instead?
or
piv >>.conkyrc${exec /usr/bin/qiv --root /home/temetka/picture.png}
same question as above, plus: overkill.
this sets the background each & every time conky updates. about once a second.
Offline
Pages: 1