Looks like the regression was introduced when trying to fix a problem
with the mouse going into space outside of the display, when you have
two displays of different sizes joined together. Here's the bug I think
Bryce referred to, and it looks like that broke panning.
*** This bug is a duplicate of bug 881046 ***
https://bugs.launchpad.net/bugs/881046
hlb: Marking as dupe of bug 881046 which is confirmed, assigned, and has
an upstream bug.
** This bug has been marked a duplicate of bug 881046
Panning in a virtual monitor is not possible after upgrade
Confirmed on Kubuntu oneiric.
** Tags added: kubuntu panning xrandr
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to libxrandr in Ubuntu.
https://bugs.launchpad.net/bugs/878454
Title:
--scale and --panning options do not resize the mouse area
Fundamental issue at X Server level
** Package changed: compiz (Ubuntu) = xorg (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/866065
Title:
Cursor limited after XRANDR with option
*** This bug is a duplicate of bug 881046 ***
https://bugs.launchpad.net/bugs/881046
Marking as duplicate of #881046 which has links to the upstream bugs and
is confirmed and assigned. This is a bug in xserver upstream and will
affect compiz, GNOME, Unity, KDE, Kubuntu and probably XFCE /
Bug 881046 is about the same xrandr panning and scaling issue in general
- it's not just an Intel server problem.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-intel in Ubuntu.
https://bugs.launchpad.net/bugs/877878
Title:
For clarity - is this fixed in Lucid's kernel? Or is there still farther
to go? I'd like to help you keep a lid on Intel-driver-bashing in the
forum when Lucid is out, but can't figure out if you're expecting this
to work or not.
--
[i945gm] (Needs kernel 2.6.32) DRI2 swapbuffers and page
Jerry, think Bryce realises that, he's saying can we have a hang bug
reported seperately, get that fixed, and then come back to this bug.
Does that make sense?
Alternate theory meanwhile: kernel 31-RC8 hangs on boot for me, 6 and 7
were fine. So if you've moved forward to a later RC since your
*** This bug is a duplicate of bug 376092 ***
https://bugs.launchpad.net/bugs/376092
Bryce: Yep, I think this is now effectively a dupe, and I'd forgotten
this only affected EXA. Thanks, another one off the list!
--
High load average, disk read, no apparent reason - 2.6.28-11
*** This bug is a duplicate of bug 376092 ***
https://bugs.launchpad.net/bugs/376092
Bryce: Yep, I think this is now effectively a dupe, and I'd forgotten
this only affected UXA. Thanks, another one off the list!
--
High load average, disk read, no apparent reason - 2.6.28-11
Been looking through changelogs for the version Bob Manners and I have
been going through... I can see there are several memory leaks that
might have been the culprit that have been fixed recently, or that had
been fixed in drivers way in advance of what I was running.
Bob: your bug, but suggest
I ran your patched kernel for quite some time and it was perfectly
stable. I moved X on to xorg-edgers version because I was curious about
a few other bugs...
I've just been looking into going back a few versions and doing the
testing as you suggest. However my .28 kernel is now
There were lots of changes to this area of DRM in 2.6.30rc7 and rc8 -
could be worth trying this kernel and seeing if the problem goes away?
If it does I don't think it will be too hard to identify the exact
changes which fixed it...
--
High load average, disk read, no apparent reason -
OK. Can't try the current (20090603) xorg-edgers build for performance
because it just plain won't run games, but I believe this is a known
problem.
Meanwhile, on the latest Jaunty proposed versions UXA is about half the
speed of EXA on a couple of games. Which bug are you using to track UXA
There absoutely are freeze bugs in UXA and EXA both in the default
Jaunty configuration, so we need an SRU of some type, even if it's a bug
that affects performance.
The good news is that a whole bunch of them are fixed, either in kernel
updates or in updates in -proposed - so with a little time
15 matches
Mail list logo
