Just updated a fairly recent was-working two-months-old 64-bit cygwin install.
(Asus X102BA, Win 8.1 - just a little AMD netbook.)
XFree86 now failing with the below. Ideas? thanks.
(--) Windows reports only 2 mouse buttons, defaulting to -emulate3buttons
(II) xorg.conf is not supported
(II) Se
I see the same issue, and it looks like this is because I have an
empty (commented-out) ~/.startxwinrc
Removing this file causes X to open and start an xterm, probably
because it broke several of the new rules in
https://cygwin.com/ml/cygwin-xfree/2014-11/msg00029.html :
* User-defined ~/.startxwi
I can't seem to make this work from a clean install. I am using
Cygwin 1.7.34 (the latest one with the GID/UID changes). Xwin starts
briefly, then dies. Here are the contents .xsession-errors:
$ cat .xsession-errors
Warning: Missing charsets in String to FontSet conversion
0 [main] fbpane
> $ cat .xsession-errors
> Warning: Missing charsets in String to FontSet conversion
> 0 [main] fbpanel 6172 child_info_fork::abort:
> C:\Cygwin\bin\cyggtk-x11-2.0-0.dll: Loaded to different address:
> parent(0x8D) != child(0x97)
> Can't open profile multiwindow - /home/reisert/.confi
Can somebody help me overcome this error? What am I missing this time?
Last time I tried to build X was 2 months ago and it was 1.16.1-1,
which was built just fine. Thanks for your help.
make[5]: Entering directory
'/usr/src/xorg-server-1.16.2-1
On 12/1/2014 8:35 AM, Tim Kingman wrote:
I see the same issue, and it looks like this is because I have an
empty (commented-out) ~/.startxwinrc
Removing this file causes X to open and start an xterm, probably
because it broke several of the new rules in
https://cygwin.com/ml/cygwin-xfree/2014-11
On Mon, Dec 1, 2014 at 3:32 PM, Mark Hansen wrote:
> On 12/1/2014 8:35 AM, Tim Kingman wrote:
>>
>> *snip*
>> my .bashrc calls startxwin
>> to make sure I always have an X server running ( per
>> http://stackoverflow.com/a/9301966 )
>> *snip*
>>
>> I'll keep playing with this to see if I can come
This is an obvious source-header discrepancy. The source
file(auto-generated anyway) doesn't seem to be changed recently, while
the header file(glext.h) has a timestamp of Nov 16 now. So it looks
like only the header file got advanced here. Looking at the
announcements, it should be the Mesa update
> (Resending because qmail can't handle mime)
I don't have a ~/.startxwinrc file, because the account home directory was
created without one.
Creating one, making it executable, adding commands to it makes no difference -
the X server launches (--muiltiwindow or not) and then decides to shut d