From: "Jason A. Donenfeld" <Jason@zx2c4.com>
To: Alexey Ivanov <alexey.ivanes@gmail.com>,
Alexander Neumann <an2048@googlemail.com>
Cc: WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: Wireguard for Windows tray menu problem
Date: Wed, 17 Jul 2019 22:51:31 +0200 [thread overview]
Message-ID: <CAHmME9oRe5L1w0O6sgoEG1CpMaVX2gwnCcLrhBn5_7SW0ix_Rg@mail.gmail.com> (raw)
In-Reply-To: <CAJcUPC4W67nNOMWDW27m_fnNNYMvrkXr5Zi1AGNn_6miJ1=iPg@mail.gmail.com>
Hi Alexey,
Cool bug and thanks for the reproduction steps. I see the same thing
you are. I love bugs like these. Will investigate. I've also added it
to our Windows TODO:
https://docs.google.com/document/d/1-jlULsy1uDun-b4ow3RvnNQJU5K_pAv87sqDAfK66Kk/edit?ts=5cd97371
Jason
On Wed, Jul 17, 2019 at 10:39 PM Alexey Ivanov <alexey.ivanes@gmail.com> wrote:
>
> Hello.
>
> Here is a bug when wireguard's gui tray menu opened.
> Sometimes when menu created behind taskbar (known windows bug) you can't open Windows Start menu by pressing WIN button or click on Start.
>
> Steps to reproduce:
> 1. Press WIN
> 2. Right-click Wireguard tray icon
> 3. Press WIN again, 50/50 Windows start won't open.
> 4. Click Windows Start it won't open, but it should.
>
> Also wireguard's menu when its created behind taskbar won't even close itself when you click somewhere else on desktop, only way to close it now its select any menu item like "about" or exit.
_______________________________________________
WireGuard mailing list
WireGuard@lists.zx2c4.com
https://lists.zx2c4.com/mailman/listinfo/wireguard
prev parent reply other threads:[~2019-07-17 20:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-12 4:02 Alexey Ivanov
2019-07-17 20:51 ` Jason A. Donenfeld [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=CAHmME9oRe5L1w0O6sgoEG1CpMaVX2gwnCcLrhBn5_7SW0ix_Rg@mail.gmail.com \
--to=jason@zx2c4.com \
--cc=alexey.ivanes@gmail.com \
--cc=an2048@googlemail.com \
--cc=wireguard@lists.zx2c4.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 NNTP newsgroup(s).