You are not logged in.
I'm seeing a bug in openbox (started directly ie no gnome/kde etc) when toggling decorations where the menu gets replaced by the decorations for some terminals eg lxterminal roxterm etc etc. I made some snaphots to illustrate the issue here.
Initially the terminal looks like this
after toggling it looks like
after re-decorating it looks like this
any ideas what causes this? I'm certainly seeing it in lexterminal and roxterm, but perhaps they sher some underlying code.
Offline
After checking I find that roxterm and vte were both upgraded recently. I downgraded roxterm to roxterm-1.21.4-1-i686.pkg.tar.xz and the problem disappears. It seems that the bug appears between roxterm-1.21.4-1-i686.pkg.tar.xz & roxterm-1.22.1-1-i686.pkg.tar.xz which is the latest package. I have a vague memory that this problem has been in lxterminal for a while. I did check that the problem is not in vte as upgrading that and vte-common does not cause a problem.
Is there any way to find the source for the earlier package to see what changed?
Offline
If you mean the package source, you can search for roxterm in the "Packages" section of the webpage, and then you'll find the SVN entries on the right side. Like this:
http://www.archlinux.org/packages/?sort … =&limit=50
zʇıɹɟʇıɹʞsuɐs AUR || Cycling in Budapest with a helmet camera || Revised log levels proposal: "FYI" "WTF" and "OMG" (John Barnette)
Offline
Duh, I did that eventually
looked at some diffs from the upstream and could not see anything obvious so I have re-posted the issue up there at sf.net.
Offline
I thought I would try and figure out where the bug entered the system, but when I try to use git bisect I find that I need to bootstrap the autoconf files as it seems that arch roxterm is built from the a tar.gz which already contains configure, config.sub etc etc. I tried running something called bootstrap.sh and it seemed to work, but then arch fails with missing files during the package build. Is there any way to get debian style stuff up and running from git?
Offline
After consultation with the author and a couple of bisections he located the issue and the bug is now squashed in roxterm 1.22.2
Offline