public inbox for cygwin-xfree@sourceware.org
help / color / mirror / Atom feed
From: <l.wood@surrey.ac.uk>
To: <cygwin-xfree@cygwin.com>
Subject: Re: X no longer spawning windows after update
Date: Sat, 25 Jul 2015 08:00:00 -0000	[thread overview]
Message-ID: <DB4PR06MB457DFA34062C50850AFA103AD800@DB4PR06MB457.eurprd06.prod.outlook.com> (raw)
In-Reply-To: <55B237E2.5050504@dronecode.org.uk>

so the X graphic that started appearing floating in the top left corner of a screen, but no longer does, had some sort of menu associated with it? Who knew?

Yes, new notification bar icon (occasionally two?) has xterm option in pop up menu in pop up window of all notification icons, of which there are alas many. How to restore old launch-an-xterm-at-x-launch behaviour?

Think it would be good if the Cygwin installer threw vital changes to behaviour in packages (like the one referenced below) in face to click through before doing installs. If it's a deliberate change, document it in the installer loading in package-specific readmes so that user accepts the change before discovery and being launched into the unknown,

'Detected two mouse buttons, so emulating three' / 'Detected more than two mouse buttons, so assuming three are available' seems easy enough.
________________________________________
From: Jon TURNEY <jon.turney@dronecode.org.uk>
Sent: Friday, 24 July 2015 11:04:34 PM
To: cygwin-xfree@cygwin.com
Cc: Wood L  Dr (Electronic Eng)
Subject: Re: X no longer spawning windows after update

On 24/07/2015 01:27, l.wood@surrey.ac.uk wrote:
> Updated cygwin 32-bit with installer, now X no longer spawning
> windows or terminal on launch. Just seems to hang after running
> startxwin. Is there anything obvious in the log below?

I think what you are seeing is the deliberate change described in the
last bullet point of [1]

The log you provide looks normal.

[1] https://cygwin.com/ml/cygwin-announce/2015-07/msg00013.html

> (--) 8 mouse buttons found
> (eight mouse buttons? on a three-button mouse?)

The value logged here comes from GetSystemMetrics(SM_CMOUSEBUTTONS)

Some USB mice seem to report incorrect values.  I'm guessing this is
something like the maximum number of buttons the microcontroller inside
can support, rather than the number which are actually physically present.

This value is only used to see if it's not 2, in which case
-emulate3buttons is enabled by default.

I'm not sure what can be done about this, except perhaps changing
"found" to "reported" :D

--
Jon TURNEY
Volunteer Cygwin/X X Server maintainer

--
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:[~2015-07-25  8:00 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-24  0:27 l.wood
2015-07-24 13:04 ` Jon TURNEY
2015-07-25  8:00   ` l.wood [this message]
2015-07-25 12:40     ` Ken Brown

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=DB4PR06MB457DFA34062C50850AFA103AD800@DB4PR06MB457.eurprd06.prod.outlook.com \
    --to=l.wood@surrey.ac.uk \
    --cc=cygwin-xfree@cygwin.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).