You are not logged in.
I'm using Openbox & Tint2 (double config - one panel at the bottom with tasks, tray and so on, another at the top - this one displaying only launchers) on my PC with Intel graphics. It does not happen always, but quite often, after I boot into my Arch, I see Tint2 with no transparency at all (I mean: the background is completely black). Usually restarting (killing) Tint2 helps and after that I get transparent panels.
Here are both of my config files:
http://wklej.org/id/1577983/
http://wklej.org/id/1577984/
Can anyone tell me at least how do I figure out what is going on? I have been using the same config files on my old laptop with Radeon graphics and I did not experience anything like that there. This PC is quite new and sometimes I get transparency, sometimes not.
BTW, Yes, I know about compositing managers, but I would like to avoid unnecessary stuff when possible. On my old laptop, Tint2 worked well without xcompmgr/compton running.
Last edited by Hwiparam (2014-12-28 15:51:10)
Offline
If you run tint2 without a compositor, it will only provide "fake" transparency -- it just re-draws the underlying wallpaper over the panel.
In your case whatever you use to set the wallpaper has probably not finished by the time tint2 is started, hence the black background.
We really need to see your ~/.xinitrc and ~/.config/openbox/autostart to see what's going on.
Jin, Jîyan, Azadî
Offline
~/.xinitrc:
#!/bin/sh
. .bash_profile &
exec openbox-session~/.config/openbox/autostart:
sh ~/.fehbg &
xmodmap "~/.Xmodmap" &
xrdb -load ~/.Xdefaults &
xrdb -load ~/.Xresources &
setxkbmap pl &
gvolwheel &
xscreensaver &
source ~/.bash_profile &
export _JAVA_OPTIONS='-Dawt.useSystemAAFontSettings=full'
# Detection of insertion of an optical disk
if ! pgrep -lf "udisks-daemon: polling /dev/sr0"; then
udisks --poll-for-media /dev/sr0
fi
udisksvm -a &
mpd &
copyq &
tint2 &
tint2 -c /home/noname/.config/tint2/tint2rc.top &
neap &
conky &The "sh ~/.fehbg &" line in autostart is needed for the wallpaper to be set at startup. As seen, it should be executed before tint2 starts, so I'm not sure it's an issue with feh. Of course I may be wrong, but I have exactly the same configuration on my old laptop, where the problem does not occur.
Offline
As written it may not execute before tint2. Remove the & from the end of the fehbg line. Also there is absolutely no reason to source bash_profile in either of those files: it has already been read before xinitrc, then when in the autostart, it has been read twice before you read it again.
Your xrdb commands also don't make much sense. The first one ends up having no effect. There is no need to background these either.
"UNIX is simple and coherent" - Dennis Ritchie; "GNU's Not Unix" - Richard Stallman
Offline
Well, I removed the "&" from the "sh ~/.fehbg &" so now it's "sh ~/.fehbg". I also moved that line from ~/.config/openbox/autostart to ~/.xinitrc in order to be sure it finishes before ~/.config/openbox/autostart is started. Seems to do the job, at least so far, thanks.
EDIT: But I still have no idea, why on Earth I did not experience that on my previous machine... ![]()
Last edited by Hwiparam (2014-12-28 15:48:18)
Offline
Perhaps your previous machine was faster, or slower, or running in a full moon. When you background everything, there is no way to determine which process will finish first. If you don't background it, then it must finish before the next command runs - so moving that command to xinitrc served no purpose (but also does no harm).
"UNIX is simple and coherent" - Dennis Ritchie; "GNU's Not Unix" - Richard Stallman
Offline