Hi, Am Dienstag, den 18.03.2008, 17:15 -0700 schrieb Andrew Sackville-West:
I tried recompiling all this stuff to no avail. Specifically, I've rebuilt the debian source packages for x11, xmonad and xmonad-contrib and also *removed* those and built the versions from hackage. Everything seems to work just fine except xinerama. I suspect there may be breakage deeper into the system somewhere. libxinerama-dev has also been upgraded, I may have to try downgrading that and rebuilding again.
Just checking back: The problem is also present when building xmonad from cabal, independant from the debian packages?
Do you have x11proto-xinerama-dev installed? What is the output of the configure step when configuring haskell-x11?
this all may be a red-herring... it *appears* that my local xmonad wasn't getting updated because I hadn't changed it or touched it. It's not conclusive as I *had* made some changes to it, but the whole process has gotten so confusing now that I can't confirm either way exactly what happened. Regardless, I am now getting functioning xinerama running the official debian packages.
Sorry to ask for details again: Are you getting xinerama with the unmodified official debian packages or with the debian packages locally re-build?
Is it possible that having a custom ~/.xmonad/xmonad.hs that wasn't changed across updates could cause xinerama to fail because ~/.xmonad/xmonad-i386-linux doesn't get rebuilt?
Quite possible, happens to me all the time :-) Greetings, Joachim -- Joachim "nomeata" Breitner Debian Developer nomeata@debian.org | ICQ# 74513189 | GPG-Keyid: 4743206C JID: nomeata@joachim-breitner.de | http://people.debian.org/~nomeata