On 24/07/2015 15:14, Jim Reisert AD1C wrote:
This seems to be the real error, when I try to start an xterm from the xdg menu:
executing 'xterm', pid 11044
pid 11044 exited with status b
What is status b?
Status 11, but in hexadecimal :)
I'm not sure this is a valid exit status, which is perp
This seems to be the real error, when I try to start an xterm from the xdg menu:
executing 'xterm', pid 11044
pid 11044 exited with status b
What is status b?
And the results of trying to view the log file (same error status)
executing 'xterm -title '/cygdrive/D/Home/.xsession-errors' -e less
On Fri, Jul 24, 2015 at 6:40 AM, Jon TURNEY wrote:
> If you can reproduce this problem, you could always examine the
> ~/.xsession-errors file directly.
Here it is. There "Can't create dir" messages have been there all
along. The ones regarding "Failed to connect to socket" may be the
problem.
On 20/07/2015 06:06, Jim Reisert AD1C wrote:
I installed Windows 10 over the weekend ("RTM" release 10240, 64-bit,
Pro). Cygwin, X server and XDG were working fine until sometime
Sunday afternoon. Suddenly, I could not launch xterms, but still
could from the old Xwin icon in the system notifica
One somewhat unrelated thing I'd like to add: Once the 'X' icon
appears, it takes another good 20 seconds or so for the xdg menu icon
to appear. I have no idea what's causing that.
--
Jim Reisert AD1C, , http://www.ad1c.us
--
Problem reports: http://cygwin.com/problems.html
FAQ:
I installed Windows 10 over the weekend ("RTM" release 10240, 64-bit,
Pro). Cygwin, X server and XDG were working fine until sometime
Sunday afternoon. Suddenly, I could not launch xterms, but still
could from the old Xwin icon in the system notification area. Nothing
works from XDG (other than
6 matches
Mail list logo
