7 Aug
2014
7 Aug
'14
4:57 a.m.
Hi, On Thu, Aug 07, 2014 at 07:44:12AM +0000, Antonio Bibiano wrote:
Hi, I incurred in the same problem!
I also have had the same problem (on both a real computer and a VirtualBox VM). [...]
My solution is to start xmonad using a small script:
My workaround has been to run "xfce4-panel --restart" after logging in (which was an improvement over killing xmonad/xfwm4/xmonad --replace). Starting xmonad with a delay at least has the advantage that it's an automated bodge, so I may do that for now, thanks. :-) Regards, Chris