You are not logged in.
Hello.
I'm using Fluxbox on Xorg. I have two monitors and for more than one year my setup has been this in ~/.xinitrc:
#!/bin/sh
if [ -d /etc/X11/xinit/xinitrc.d ]; then
for f in /etc/X11/xinit/xinitrc.d/*; do
[ -x "$f" ] && . "$f"
done
unset f
fi
xrandr --output DVI-0 --mode 1920x1080 --pos 0x0 --output DVI-1 --mode 1680x1050 --pos 1920x0
exec startfluxboxNow, I just upgraded my packages (fluxbox and some xorg-* packages were upgraded, like xorg-server, as well as xf86-video-ati) and, although the dual monitor setup works, it seems like each monitor is not recognized individually. My Fluxbox toolbar spans on both monitors horizontally (whereas it used to reside on the left one) and when I maximize a window, it's maximized on both monitors (whereas it used to be maximized on one monitor only, the closest).
Before reverting the upgrade, anybody knows why this is happening?
Thanks,
Phil
Last edited by eepp (2014-07-07 00:55:04)
Offline
I'm having the exact same problem, although I don't have any xrandr commands in my start up files. And I'm on nvidia.
Last night I've reverted the upgrade and that made the problem go away. I did not have time yet to narrow down which package is causing it though. (In my case 78 packages were upgraded.) I checked the commit messages on some of the packages that I thought would be the likely suspects, but all of those said something like "mtree rebuild", which I was told in the IRC should not change any functionality.
I hope to have some more time to look into this tonight, but I'm really curious what is causing this.
Offline
I was having this problem as well - downgraded to fluxbox 1.3.5-2 and it's fixed.
Offline
Yep, the downgrade to fluxbox 1.3.5-2 did it for me too. I had a quick look at the diff between -2 and -3 and didn't find anything relevant, but I should invest more time.
I sent an email to the packager about this and I'm still waiting for a reponse.
Thanks for confirming I'm not alone guys! Perhaps a fluxbox package bug should be reported now that I know it's not only me.
Last edited by eepp (2014-07-06 08:25:03)
Offline
Yup, I can confirm that. It's the fluxbox package.
I've enabled logging. Here's the full log of 1.3.5-3:
------------------------------------------
Log File: /tmp/fluxlog
Fluxbox version: 1.3.5
GIT Revision: this_is_tar_ball_build
Compiled: Jul 4 2014 20:54:40
Compiler: GCC
Compiler version: 4.9.0 20140604 (prerelease)
Defaults:
menu: /usr/share/fluxbox/menu
style: /usr/share/fluxbox/styles/bloe
keys: /usr/share/fluxbox/keys
init: /usr/share/fluxbox/init
nls: /usr/share/fluxbox/nls
Compiled options (- => disabled):
-BIDI
-DEBUG
EWMH
IMLIB2
NLS
REMEMBER
RENDER
-SHAPE
SLIT
SYSTEMTRAY
TOOLBAR
-RANDR
XFT
-XINERAMA
XMB
XPMNotice the -RANDR and -XINERAMA lines? I bet that is what's causing this.
For completeness here is the log from 1.3.5-2:
------------------------------------------
Log File: /tmp/fluxlog
Fluxbox version: 1.3.5
GIT Revision: this_is_tar_ball_build
Compiled: Apr 4 2013 00:27:22
Compiler: GCC
Compiler version: 4.8.0
Defaults:
menu: /usr/share/fluxbox/menu
style: /usr/share/fluxbox/styles/bloe
keys: /usr/share/fluxbox/keys
init: /usr/share/fluxbox/init
nls: /usr/share/fluxbox/nls
Compiled options (- => disabled):
BIDI
-DEBUG
EWMH
IMLIB2
NLS
REMEMBER
RENDER
SHAPE
SLIT
SYSTEMTRAY
TOOLBAR
RANDR1.2
XFT
XINERAMA
XMB
XPMI need to run now, but I'd say a bug report would indeed be appropriate here. If nobody gets to that earlier I'll see if I can submit one tonight.
Thanks guys.
Offline
just opened a bug report here: https://bugs.archlinux.org/task/41113
I hope it is fine, it is my first time reporting a bug
Offline
silvrax, this makes perfect sense. Thanks for investigating this. The funny thing is that 1.3.5-2 and 1.3.5-3 both use the same source (Fluxbox 1.3.5). And now, building 1.3.5-2 fails, because of something fixed in the 1.3.5-3 PKGCONFIG. Seems like an imlib2 bug: https://bugs.archlinux.org/task/39345?dev=355.
Seems like --enable-xrandr is not the default in the tarball version, but it is now on the current Git master.
manoet, thanks for the bug report.
Offline
should be fixed in fluxbox-1.3.5-4
Offline
confirmed. It works fine now.
Thank you, both for the fix and for the speed
Offline
Thanks Snowman for the quick fix, I can confirm it resolved the dual head issue I was having.
One thing I noticed though when comparing the fluxbox log of 1.3.5-4 with the original 1.3.5-2 is that in the latest version BIDI is now disabled. I'm not entirely sure what that is though or if it could cause issues. I haven't seen any problems yet, but just thought I'd point that out.
Again, thanks for dealing with this issue!
Offline
Yep thanks Éric!
Offline