From: Marco Atzeri <marco.atzeri@gmail.com>
To: cygwin@cygwin.com
Subject: Re: cygwin x11 doesn't start after windows 10 upgrade
Date: Sun, 14 Jun 2020 19:49:13 +0200 [thread overview]
Message-ID: <65b25545-1a7e-7fe8-57f6-d1e46002c8f3@gmail.com> (raw)
In-Reply-To: <upzclfkpbp9o.fsf@dod.no>
On 14.06.2020 18:12, Steinar Bang wrote:
>>>>>> "Henry S. Thompson via Cygwin" <cygwin@cygwin.com>:
>
>> Steinar Bang writes:
>> [troubles with XWin]
>
>> Have a look at what Windows shows as the processes that are running.
>
>> I've had intermittent problems with XWin processes running without
>> actually showing any windows. You can see process information either
>> with a special tool such as ProcExp or with the builtin Windows task
>> manager, via Control-Alt-Delete.
>
>> If you find XWin processes, let us know.
>
> There were no XWin processes in the "Processes" tab of the task manager.
>
> I couldn't see any XWin processes in sysinternals procexp64 either. And
> search for "xwin" in procexp gave no matches.
>
I guess we have only two methods to further going down
1) checking with strace if it is crashing during any system call
strace -o XWin.strace /usr/bin/XWin :0 -multiwindow -auth
XWin.strace should contain some hints, hopefully
2) use the gdb debugger, but it will require the installation of
several debuginfo packages
Regards
Marco
next prev parent reply other threads:[~2020-06-14 17:49 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-11 15:57 Steinar Bang
2020-06-13 6:30 ` Marco Atzeri
2020-06-13 9:30 ` Steinar Bang
2020-06-13 11:22 ` Marco Atzeri
2020-06-13 12:00 ` Steinar Bang
2020-06-13 13:22 ` Marco Atzeri
2020-06-13 15:48 ` Steinar Bang
2020-06-13 16:44 ` Steinar Bang
2020-06-13 20:37 ` Andrey Repin
2020-06-13 9:35 ` Steinar Bang
2020-06-13 9:55 ` Steinar Bang
2020-06-13 11:31 ` Marco Atzeri
2020-06-13 12:03 ` Steinar Bang
2020-06-13 12:09 ` Steinar Bang
2020-06-13 13:14 ` Holger, Vodafone
2020-06-13 13:29 ` Marco Atzeri
2020-06-13 9:04 ` Steinar Bang
2020-06-13 21:15 ` Jon Turney
2020-06-14 10:44 ` Steinar Bang
2020-06-14 11:18 ` Henry S. Thompson
2020-06-14 16:12 ` Steinar Bang
2020-06-14 17:49 ` Marco Atzeri [this message]
2020-06-14 21:45 ` Steinar Bang
2020-06-14 22:21 ` Holger, Vodafone
2020-06-15 12:17 ` Holger, Vodafone
2020-06-15 12:57 ` Holger, Vodafone
2020-06-16 4:22 ` Brian Inglis
2020-08-02 20:25 ` Steinar Bang
2020-08-02 21:00 ` Eliot Moss
2020-08-04 12:01 ` Steinar Bang
2020-08-04 13:12 ` Hamish McIntyre-Bhatty
2020-08-04 16:55 ` ASSI
2020-06-16 4:59 ` ASSI
2020-07-02 15:01 ` Steinar Bang
2020-07-02 22:12 ` Holger, Vodafone
2020-06-16 11:46 ` Holger, Vodafone
2020-06-26 9:15 ` Holger, Vodafone
2020-07-02 14:42 ` Steinar Bang
2020-06-14 6:18 ` Marco Atzeri
2020-06-14 10:38 ` Steinar Bang
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=65b25545-1a7e-7fe8-57f6-d1e46002c8f3@gmail.com \
--to=marco.atzeri@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).