Hi,
I experience today a problem with Virtualbox and DWM. I have two monitors
connected to my PC. Toggling the screen in Virtualbox (Host + Home then
View -> VirtualScreen -> HostScreenX) in full screen mode has no effect. So
Virtualbox stays on the primary screen and not switch to the second one.
I think so. XINERAMALIBS and XINERAMAFLAGS are set and passed respectively
in LIBS and CPPFLAGS in the file config.mk as it is by default. Should I do
something else ?
2013/6/11 Jacob Todd
> Did you compile dwm with xinerama enabled?
> On Jun 11, 2013 6:54 AM, "Rémy Lefevre"
6 (0x7f4b2fe33000)
libXdmcp.so.6 => /usr/lib/libXdmcp.so.6 (0x7f4b2fc2d000)
My dwm version is 6.0
2013/6/11 Chris Down
> On 11 Jun 2013 12:19, "Rémy Lefevre" wrote:
> >
> > I think so. XINERAMALIBS and XINERAMAFLAGS are set and passed
> respectively in
Bryan Bennett gmail.com> writes:
>
> Is dwm displaying a mirror of the first screen on the second? I saw
> this behavior and just resorted to using xsetroot rather than fixing
> my X config.
>
>
No, dwm is not displaying a mirror. I used xrandr --output VGA1 --left-of
LVDS1 to change that. S
Bryan Bennett gmail.com> writes:
>
> Xrandr. It was a long day...
What is the problem with Xrandr ? As it uses Xinerama protocol, it should
work without any problem.
Bryan Bennett gmail.com> writes:
>
> I meant the command line client. I encountered an issue wherein dwm
> was mirroring to both screens when I would startx. If you're getting
> one huge screen across both monitors, rather than mirroring - ignore
> me.
>
> On Wed,
Bryan Bennett gmail.com> writes:
>
> I apologize. I misread your initial mail. I remember having a similar
problem with virtual box but seem to remember that it was the result of a
mismatch between the guest additions and the virtualbox version rather than
being related to the wm. Are you sure y
Rémy Lefevre gmail.com> writes:
>
> Bryan Bennett gmail.com> writes:
>
> >
> > I apologize. I misread your initial mail. I remember having a similar
> problem with virtual box but seem to remember that it was the result of a
> mismatch between the guest add
