From: Jon Turney <jon.turney@dronecode.org.uk>
To: sciguy <sciguy@vex.net>
Cc: cygwin@cygwin.com
Subject: Re: LXDE rears its ugly head :-)
Date: Mon, 26 Feb 2024 13:16:18 +0000 [thread overview]
Message-ID: <12d654b5-43d1-4800-88cb-7a8bbd44fe25@dronecode.org.uk> (raw)
In-Reply-To: <d0df4a70f7f742488ecc7e8518a5cb3a@vex.net>
On 24/02/2024 23:31, sciguy via Cygwin wrote:
> Hello
>
> I am using Cygwin-X on Windows 10. It is a version from around 2020 or
> so. The window managers (I have a few that I have installed) seem to
> work, but it appears that LXDE likes to cover the toolbars and menubars,
> especially when GNOME is supposed to be running. Even if I "log off" of
> LXDE (which doesn't have any effect on GNOME), the LXDE toolbar, after a
> few minutes, covers the native GNOME toolbar.
Can you perhaps explain how you are starting the session where you see
this problem?
It should only be possible to have one window manager running at a time
on a given X display, so I'm not quite sure what you are describing here.
> In fact, the GNOME toolbar can be exposed, but like a game of
> peek-a-boo, the LXDE toolbar reappears when my mouse moves close to it.
> It also shows up under KDE (which doesn't seem to have a working
> toolbar). If I run fluxbox, there is no LXDE running.
>
> Is there supposed to be a reason why a LXDE toolbar has to appear in a
> non-LXDE window manager? Is there somewhere where I can turn off this
> setting (assuming that's all there is).
I assume this is something in the Xsession init scripts (which are
unfortunately complex) which is launching the "toolbar" unconditionally.
Unless you want to dive into those, uninstalling the package which
provides the unwanted program might be the way to go.
I'm afraid all the "Desktop Environments" we currently ship are rather
old and unmaintained. Somewhere in my vast backlog of stuff, I'd like
to (a) remove the heavyweight ones i.e. GNOME and KDE, and (b) update
the others which are actually used by someone. But that seems
increasingly unlikely to happen.
prev parent reply other threads:[~2024-02-26 13:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-24 23:31 sciguy
2024-02-26 13:16 ` Jon Turney [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=12d654b5-43d1-4800-88cb-7a8bbd44fe25@dronecode.org.uk \
--to=jon.turney@dronecode.org.uk \
--cc=cygwin@cygwin.com \
--cc=sciguy@vex.net \
/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).