From: Derby Pride <thederbypride@gmail.com>
To: cygwin@cygwin.com
Subject: Re: Possible issue with Firefox (38.0.1) running on X Server 1.17.2
Date: Wed, 05 Aug 2015 09:12:00 -0000 [thread overview]
Message-ID: <CAHkMg9FPkZ1Vt+oZVJ+ZeJfpUMmpVySikaxU=QPdHwwcA+5evg@mail.gmail.com> (raw)
In-Reply-To: <55C0F6CB.6050102@dronecode.org.uk>
Thanks for your reply Jon. I'm happy to report that I tried the 32-bit
version of your updated XWin.exe which worked perfectly.
On 4 August 2015 at 18:30, Jon TURNEY <jon.turney@dronecode.org.uk> wrote:
> On 03/08/2015 16:43, Derby Pride wrote:
>>
>> I have recently upgraded Cygwin/X which upped the version of X Server
>> up to 1.17.2 (sorry, I didn't note the version that I was previously
>> using). I now enter the following into the Cygwin terminal:
>>
>> export DISPLAY=:0.0
>> XWin -multiwindow -clipboard -listen tcp &
>> xhost +
>>
>> On my remote machine (a virtual RHEL5.2) I give the following commands:
>>
>> export DISPLAY=%server_ip%:0.0
>> firefox &
>>
>> Firefox launches successfully on my server machine. However, the
>> maximize button is disabled (all other buttons are present and
>> enabled). Resizing the window by dragging the edges works as expected
>> but there appears to be no way to maximize (double clicking the title
>> bar does not work either).
>
>
> Thanks for reporting this issue.
>
> I can reproduce this on a Centos 5 VM.
>
> This is interesting. The firefox window has a WM_NORMAL_HINTS which
> specifies a maximum size of 32767x32767.
>
> Currently, the maximize control on the window frame is supposed to be
> disabled if a maximum size is specified at all, but it looks like that
> wasn't quite working correctly until recently.
>
> I've adjusted the logic a little bit so that the maximize control is not
> disabled if a maximum size is specified, but it's larger (in both
> dimensions) than the Windows virtual desktop size (as then maximization will
> not exceed the maximum size specified)
>
> I've built a snapshot with this change. Perhaps you could try that and see
> if it improves things for you?
>
> ftp://cygwin.com/pub/cygwinx/x86/XWin.20150804-git-862bf7a8412567ae.exe.bz2
> ftp://cygwin.com/pub/cygwinx/x86_64/XWin.20150804-git-862bf7a8412567ae.exe.bz2
>
> --
> Jon TURNEY
> Volunteer Cygwin/X X Server maintainer
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
prev parent reply other threads:[~2015-08-05 9:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-03 15:43 Derby Pride
2015-08-04 17:31 ` Jon TURNEY
2015-08-05 9:12 ` Derby Pride [this message]
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='CAHkMg9FPkZ1Vt+oZVJ+ZeJfpUMmpVySikaxU=QPdHwwcA+5evg@mail.gmail.com' \
--to=thederbypride@gmail.com \
--cc=cygwin@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).