public inbox for cygwin-xfree@sourceware.org
help / color / mirror / Atom feed
From: Jon TURNEY <jon.turney@dronecode.org.uk>
To: cygwin-xfree@cygwin.com
Cc: gp1865@att.com
Subject: Re: FW: xorg-server 1.13.1-1: problems with xterm
Date: Fri, 08 Feb 2013 18:15:00 -0000	[thread overview]
Message-ID: <511540B1.6080300@dronecode.org.uk> (raw)
In-Reply-To: <397AD605DAD9254D9D2FFE207111E6442ADC760F@MOKSCY3MSGUSR9D.ITServices.sbc.com>

On 06/02/2013 17:18, PRIKHODKO, GEORGE wrote:
> After upgrading xorg-server and xorg-server-common packages from 1.13.0-1
> to 1.13.1-1 version, xterm stopped responding to mouse events. I can select
> a text in a xterm window, but I cannot paste in it using middle button;
> holding Ctrl button and pressing one of mouse buttons doesn't bring 'Main
> Options' or 'VT Fonts' menus. After rolling back to 1.13.0-1 version
> everything works as I expect.
> 
> I have four computers WIndows XP, Vista, 7 and 8, and run XWin in 
> multi-window mode:
> 
> XWin -ac -clipboard -emulate3buttons -lesspointer -multiwindow
> 
> All four computers show the same symptoms.

It's really not necessary write 3 emails about this, and certainly doesn't get
you a reply any faster.

I can't reproduce this problem.

Are you using a 3-button mouse? Does removing -emulate3buttons help?

Is this a local xterm process, or one on a remote computer you are connecting to?

Is it only xterm which doesn't respond to mouse buttons or are other programs
affected?

> A couple of days ago a new version of xorg-server, 1.13.2-1, came out. It
> still has same problem and it is impossible to return to 1.13.0-1 from
> setup.exe after installing 1.13.2-1 version.

Yes, it is an unfortunate deficiency of setup that only 1 previous version is
allowed.

If you still have the downloaded package, you should be able to downgrade to
1.13.0-1 using the "Install from local directory" option in setup.

> Could you tell me whether I am doing something wrong or it is a bug? Is
> there a workaround? Where can I find sources of the packages?

This sounds like a bug, although I hope someone else would have mentioned it
if it was widespread.

Detailed and possibly accurate instructions for obtaining the source code can
be found in the Contributor's Guide at [1]

[1] http://x.cygwin.com/docs/cg/

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://x.cygwin.com/docs/
FAQ:                   http://x.cygwin.com/docs/faq/


  reply	other threads:[~2013-02-08 18:15 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20130204180522.L8CD2.196982.root@hrndva-web22-z01>
2013-02-06 17:19 ` PRIKHODKO, GEORGE
2013-02-08 18:15   ` Jon TURNEY [this message]
2013-02-10 12:45     ` Ken Brown
2013-02-10 18:37       ` Jon TURNEY
2013-02-10 19:51         ` Ken Brown
2013-02-11 17:01     ` PRIKHODKO, GEORGE

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=511540B1.6080300@dronecode.org.uk \
    --to=jon.turney@dronecode.org.uk \
    --cc=cygwin-xfree@cygwin.com \
    --cc=gp1865@att.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).