public inbox for cygwin-xfree@sourceware.org
help / color / mirror / Atom feed
From: Ken Brown <kbrown@cornell.edu>
To: cygwin-xfree@cygwin.com
Subject: Re: [ANNOUNCEMENT] Updated: xinit-1.3.4-1 (Major overhaul of X session handling)
Date: Fri, 28 Nov 2014 22:53:00 -0000 [thread overview]
Message-ID: <5478FCE9.1040209@cornell.edu> (raw)
In-Reply-To: <announce.5477E619.7090107@cygwin.com>
On 11/27/2014 10:03 PM, Yaakov Selkowitz wrote:
> * The new default startxwinrc also launches a miniature fbpanel in the
> upper left corner of the screen which contains an XDG application menu
> (the 'X' icon) for launching X applications, plus an on-demand area for
> X tray icons. After the first run, the panel and menu can be customized
> in ~/.config/fbpanel/multiwindow.
This is not working well for me. I've tested on both 32-bit and 64-bit
Cygwin with no .startxwinrc and no .[xX]* files, and I've tested on two
different computers (both running Windows 7). I started the X server
via the new start menu shortcut.
What happens is that a band appears across the bottom of the screen
(full width), hiding about 2/3 of the taskbar. This makes it impossible
to access the icons on the right side of the taskbar. Also, there's no
X icon in the upper left corner of the screen. But there is a large X
icon in the taskbar, partially visible above the band, and when I mouse
over it, I see a little window that says "X panel". Closing this window
makes the band go away. So I guess this band is the miniature fbpanel
referred to above, but it's appearing in the wrong place.
I don't see anything suspicious in XWin.0.log, but .xsession-errors
says, "fbpanel: Fatal IO error 11 (Resource temporarily unavailable) on
X server :0.". But this only appears after I've exited the server, so
maybe it's normal.
Finally, ~/.config/fbpanel/multiwindow exists but is empty.
Ken
--
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/
next prev parent reply other threads:[~2014-11-28 22:53 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-28 3:04 Yaakov Selkowitz
2014-11-28 8:45 ` Marco Atzeri
2014-11-28 11:54 ` Jon TURNEY
2014-11-28 22:53 ` Ken Brown [this message]
2014-11-30 4:02 ` Yaakov Selkowitz
2014-11-30 6:36 ` Nem W Schlecht
2014-11-30 7:45 ` Yaakov Selkowitz
2014-11-30 13:57 ` Ken Brown
2014-12-01 18:15 ` Jim Reisert AD1C
2014-12-01 18:16 ` Jim Reisert AD1C
2014-11-29 2:05 ` Nem W Schlecht
2014-11-29 2:46 ` Marco Atzeri
2014-11-29 20:19 ` Nem W Schlecht
2014-12-05 13:35 ` Jon TURNEY
2014-12-05 14:51 ` Nem W Schlecht
2014-11-30 0:18 Angelo Graziosi
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=5478FCE9.1040209@cornell.edu \
--to=kbrown@cornell.edu \
--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).