Screen workspaces not working on new Ubuntu 8.04 amd64 install

I was using Xmonad quite successfully on Slackware 12 and 12.1. However, we were recently forced to switch to 64-bit Ubuntu 8.04 at work. Under Slackware I was able to have a separate workspace on my left and right monitors. With Hardy I have a single workspace that spans both monitors. I've even gone so far as using the same xorg.conf on both and the hand-built Xmonad I was using under Slackware, yet the behavior persists. Comparing the xdpyinfo output and the xorg.0.logs the only major difference that I see is Hardy has DRI working and a few newer versions of some X modules. I am at a loss as to what could cause this. But it makes Xmonad useless to me and I'm dying in Gnome. Please help.

this is a known issue... https://bugs.launchpad.net/ubuntu/+source/xmonad/+bug/203594 I've tried getting it fixed by recompiling packages from here to kingdom come, but I haven't gotten it working yet. it's unfortunate, since it was one of the primary reasons I moved to xmonad in the first place. Adr3nal D0S wrote:
I was using Xmonad quite successfully on Slackware 12 and 12.1. However, we were recently forced to switch to 64-bit Ubuntu 8.04 at work. Under Slackware I was able to have a separate workspace on my left and right monitors. With Hardy I have a single workspace that spans both monitors. I've even gone so far as using the same xorg.conf on both and the hand-built Xmonad I was using under Slackware, yet the behavior persists. Comparing the xdpyinfo output and the xorg.0.logs the only major difference that I see is Hardy has DRI working and a few newer versions of some X modules.
I am at a loss as to what could cause this. But it makes Xmonad useless to me and I'm dying in Gnome.
Please help. _______________________________________________ xmonad mailing list xmonad@haskell.org http://www.haskell.org/mailman/listinfo/xmonad

On Wed, Jun 25, 2008 at 7:29 AM, Chris Sanner
this is a known issue...
https://bugs.launchpad.net/ubuntu/+source/xmonad/+bug/203594
Thanks, after looking at that, apparently it is an upstream bug from Debian due to lack of Xinerama support in the Haskell X11 libraries. So, since a few simple recompiles did not seem to correct the issue... I found a temporary solution that works. The Slackware Xmonad package is a simple .tgz, I unarchived it, removed the extraneous install directory, built a 32-bit libgmp for my 64-bit Ubuntu and am now happily running the Slackware version of Xmonad on Hardy Heron.

adr3nald0s:
On Wed, Jun 25, 2008 at 7:29 AM, Chris Sanner
wrote: this is a known issue...
https://bugs.launchpad.net/ubuntu/+source/xmonad/+bug/203594
Thanks, after looking at that, apparently it is an upstream bug from Debian due to lack of Xinerama support in the Haskell X11 libraries. So, since a few simple recompiles did not seem to correct the issue...
I found a temporary solution that works. The Slackware Xmonad package is a simple .tgz, I unarchived it, removed the extraneous install directory, built a 32-bit libgmp for my 64-bit Ubuntu and am now happily running the Slackware version of Xmonad on Hardy Heron.
A firm solution is to build the X11 package afresh for you system, which will enable Xinerama, assuming you have Xinerama headers installed. -- Don
participants (3)
-
Adr3nal D0S
-
Chris Sanner
-
Don Stewart