ubuntu-x-swat team mailing list archive

[David Putney <665313@xxxxxxxxxxxxxxxxxx>]

Hi,

I'm sorry to say that the computer I had the issue with was just retired
last week.  I did have the problem the whole time I had that computer, and I
did notice recently that there was another application where I could see a
sign of the problem, but I can't remember what it was.  I gave up on this
bug because I could see that I was the only one who had any interest in it.

Thank you for asking about it.

-Dave


On Wed, Apr 27, 2011 at 7:18 PM, bugbot <665313@xxxxxxxxxxxxxxxxxx> wrote:

> Hey David,
>
>
> Thanks for your interest in Ubuntu.
>
> Thanks for testing maverick during its development period.
> Unfortunately it looks like this bug report didn't get attention during
> the maverick development period.  But I see there's not been more
> comments on the bug since the release, which makes me wonder if this is
> still an issue for you?
>
> If you've not seen this issue since maverick's release yourself, it may
> have been solved by kernel or X or other updates that occurred late in
> the release; if so, would you mind please closing the bug for us?  Go to
> the URL mentioned in this bug report, click the yellow icon(s) in the
> status column and set to 'Fix Released'.
>
> If you no longer have the hardware needed to reproduce the problem, or
> otherwise feel the bug no longer needs tracked in Launchpad, you can set
> the status to 'Invalid'.
>
> If you are the original reporter and still have this issue, just reply
> to this email saying so.  (Or set the bug status to Confirmed.)  If you
> are able to re-test this against 11.04 Natty Narwhal (our current
> development focus) and find the issue still affects Natty, please also
> run 'apport-collect <bug-number>' while running natty, which will add
> fresh logs and debug data, and flag it for the Ubuntu-X development team
> to look at.
>
> --
> You received this bug notification because you are a direct subscriber
> of the bug.
> https://bugs.launchpad.net/bugs/665313
>
> Title:
>   corrupted test in emacs mouse select with 2 displays
>
> Status in “xserver-xorg-video-intel” package in Ubuntu:
>  New
>
> Bug description:
>  Binary package hint: xorg
>
>  Since the libdrm fix (619663?) was downloaded to my laptop yesterday,
>  I switched my monitor config from top/bottom to side-by-side.  It
>  appears that if I have the secondary display enabled, I now end up
>  with corrupted text in emacs, my primary editor.  I can reproduce the
>  corrupted text when I do a mouse selection (as shown in the pictures I
>  will attach).  I can also see corrupted text when I type, or when I
>  paste text into the buffer.  If I disable the second monitor, I can't
>  reproduce the problem.
>
>  I haven't seen the problem in other applications yet, so maybe this is
>  an emacs issue instead.
>
>  ProblemType: Bug
>  DistroRelease: Ubuntu 10.10
>  Package: xorg 1:7.5+6ubuntu3
>  ProcVersionSignature: Ubuntu 2.6.35-22.35-generic 2.6.35.4
>  Uname: Linux 2.6.35-22-generic i686
>  Architecture: i386
>  DRM.card0.DVI.D.1:
>   status: disconnected
>   enabled: disabled
>   dpms: Off
>   modes:
>   edid-base64:
>  DRM.card0.LVDS.1:
>   status: connected
>   enabled: enabled
>   dpms: On
>   modes: 1280x800
>   edid-base64:
> AP///////wAyDAAAAAAAAAAQAQOAHhN4CgiFlVhTjCgjUFQAAAABAQEBAQEBAQEBAQEBAQEBvBsAoFAgFzAwIDYAML4QAAAYvBsAoFAgFzAwIDYAML4QAAAAAAAA/gBZWTI2NQExNDFXWDEKAAAA/gAdKzVAXHeg6AEBCiAgAH0=
>  DRM.card0.VGA.1:
>   status: connected
>   enabled: enabled
>   dpms: Off
>   modes: 1280x1024 1280x1024 1152x864 1024x768 1024x768 800x600 800x600
> 640x480 640x480 720x400
>   edid-base64:
> AP///////wAQrCSgVTEzMxYRAQNoJh547u6Ro1RMmSYPUFSlSwBxT4GAAQEBAQEBAQEBAQEBMCoAmFEAKkAwcBMAeC0RAAAeAAAA/wBXSDMyMDc1VjMzMVUKAAAA/ABERUxMIEUxOTdGUAogAAAA/QA4Sx9QDgAKICAgICAgAKM=
>  Date: Fri Oct 22 15:37:25 2010
>  InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release i386 (20091028.5)
>  MachineType: Dell Inc. Latitude D620
>  PccardctlIdent:
>   Socket 0:
>     no product info available
>  PccardctlStatus:
>   Socket 0:
>     no card
>  ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.35-22-generic
> root=UUID=a395f838-d053-423a-bd15-6684edd5e503 ro quiet splash
>  ProcEnviron:
>   SHELL=/bin/bash
>   LANG=en_US.utf8
>  SourcePackage: xorg
>  Symptom: display
>  dmi.bios.date: 04/03/2007
>  dmi.bios.vendor: Dell Inc.
>  dmi.bios.version: A08
>  dmi.board.vendor: Dell Inc.
>  dmi.chassis.type: 8
>  dmi.chassis.vendor: Dell Inc.
>  dmi.modalias:
> dmi:bvnDellInc.:bvrA08:bd04/03/2007:svnDellInc.:pnLatitudeD620:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct8:cvr:
>  dmi.product.name: Latitude D620
>  dmi.sys.vendor: Dell Inc.
>  system:
>   distro:             Ubuntu
>   codename:           maverick
>   architecture:       i686
>   kernel:             2.6.35-22-generic
>
> To unsubscribe from this bug, go to:
>
> https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/665313/+subscribe
>

-- 
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/665313

Title:
  corrupted test in emacs mouse select with 2 displays