Re: issues with startxwin not loading x windows
On 18/08/2016 20:37, michael messina wrote: I recently switched from a windows 7 laptop to windows 10 at work here; I had cygwin 64 working with metacity as my preferred frontend for x windows with no problems. Inexplicably on the 16th it ceased functioning. I attempted a reinstall and instead, now I get is a black popup momentarily, then nothing happens. Enclosed are various log files/etc. I cannot unfortunately give my cygcheck.out without giving away a lot of internal corporate information so that was redacted since it's absolutely necessary. That said, all of the various packages said 'ok' for them. I've had my trend micro office scan administrator add my pc's C:\cygwin64 folder to the exceptions section of the configuration. Also scanned the hard drive/FS for filesystem on windows; nothing found. I cannot boot into safe mode because of bitlocker. So enclosed is my redacted cygcheck.out; my xsessions.error file from 8/16, my xwin.0 file, and a copy of the gdb output. Interestingly when I try to do a strace on it, I just get 'segmentation fault' as the output. Output log file is empty. I'm baffled here and being mostly pure linux, I kind of live and die by my cygwin instance. Any thoughts here? Please note neither opening the terminal and typing any variation of startxwin, xwin, startx, or using any start menu icons for x windows will produce anything but the described result of nothing happening Though at least from a terminal window I get some output before it refuses to start like this: the problem is Micro Trend: https://cygwin.com/ml/cygwin/2016-08/msg00228.html -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: /dev/ptmx fails with Azure accounts
Am 18.08.2016 um 11:35 schrieb Corinna Vinschen: On Aug 16 17:45, Corinna Vinschen wrote: On Aug 16 11:27, rm...@aboutgolf.com wrote: Hi Corinna On Tuesday, August 16, 2016 05:12, "Corinna Vinschen" said: Hi Russell, This is as bad as I feared. Apart from the username and the Windows home dir, there are no other information which could be fetched by the usual means. Quite apart from the fact that there are no means to *store* this information somewhere, other than creating an explicit /etc/passwd and matching /etc/group entry. But, anyway, I prepared some code for the Cygwin DLL to handle these accounts even if no /etc/passwd and /etc/group entries are present. It still needs some work, though, and for that I'd ask you to perform a last test. [...] Unknown+User@Lenovo-PC /cygdrive/c/cygwin64 $ gcc -W azure-check5.c -l Netapi32 -o azure-check5 Unknown+User@Lenovo-PC /cygdrive/c/cygwin64 $ ./azure-check5 Sid: S-1-12-1-2043906341-1249388050-2635137163-399631282 Dom\Name: AzureAD\RussellMora Reverse Sid (RussellMora): S-1-12-1-2043906341-1249388050-2635137163-399631282 Reverse Sid (AzureAD\RussellMora): S-1-12-1-2043906341-1249388050-2635137163-399631282 Good to know, thank you. Give me a bit and I'll come up with a Cygwin DLL for testing. FTR, this has been kinked out off-list. The resulting patch is in git master now. Sounds great. Would it be an option to release this fix in a 2.5.3 version to have a final XP release for all users? Thomas -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: Is there a newer syslog-ng in the works?
On 08/18/2016 03:39 AM, Corinna Vinschen wrote: > On Aug 17 16:09, Matthew Hatch wrote: >> Hi, >> >> I've noticed that syslog-ng hasn't received much attention in cygwin >> and is several years out of date (3.2.5). As such, it is missing some >> features that are useful and pretty standard today in most syslog >> daemons (ie: support for multi-line messages). Is there any chance of >> getting an updated version (say, 3.7+) built and released? > > All versions after 3.2 don't work on Cygwin anymore because the > syslog-ng developers introduced a module loader mechanism incompatible > with Cygwin. > > Updating to a newer version requires considerable porting effort. > > If somebody has fun to take over syslog-ng maintainership and work > with upstream on a modernised Cygwin port, please feel free. Thanks for the response! If recent versions of syslog-ng are no longer suitable for Cygwin, would it make sense to dump it in favor of rsyslogd, provided it doesn't also have similar issues with porting? I'm no developer and wouldn't be the one to take up such a project, but I'm just curious. -- Matthew Hatch On Thu, Aug 18, 2016 at 3:39 AM, Corinna Vinschen wrote: > On Aug 17 16:09, Matthew Hatch wrote: >> Hi, >> >> I've noticed that syslog-ng hasn't received much attention in cygwin >> and is several years out of date (3.2.5). As such, it is missing some >> features that are useful and pretty standard today in most syslog >> daemons (ie: support for multi-line messages). Is there any chance of >> getting an updated version (say, 3.7+) built and released? > > All versions after 3.2 don't work on Cygwin anymore because the > syslog-ng developers introduced a module loader mechanism incompatible > with Cygwin. > > Updating to a newer version requires considerable porting effort. > > If somebody has fun to take over syslog-ng maintainership and work > with upstream on a modernised Cygwin port, please feel free. > > > Corinna > > -- > Corinna Vinschen Please, send mails regarding Cygwin to > Cygwin Maintainer cygwin AT cygwin DOT com > Red Hat -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: Where do I download test releases?
On 18/08/2016 18:15, Francis Litterio wrote: I see announcement with "TEST RELEASE" in the subject. Are these the same as the snapshots available at https://cygwin.com/snapshots/ ? I suspect not, because there are fewer snapshots than test release announcements. If test releases are not snapshots, where can I download them? Thanks in advance. -- Fran using the same setup. At the "Select Packages" window, you need to select on the upper right the button "Exp" while default is "Curr" to enable the test version of available packages. Regards Marco -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Where do I download test releases?
I see announcement with "TEST RELEASE" in the subject. Are these the same as the snapshots available at https://cygwin.com/snapshots/ ? I suspect not, because there are fewer snapshots than test release announcements. If test releases are not snapshots, where can I download them? Thanks in advance. -- Fran -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: [ANNOUNCEMENT] Updated: mingw64-*-gcc-5.4.0-2 (x86/x86_64)
On 8/18/2016 20:08, Tony Kelman wrote: >> Sadly I seem to get similar-looking access violations even after rebuilding >> 5.4.0-2 from the -src cygport with the patch for GCC bug 66655 added. So >> maybe some other change is also needed to get this working, hopefully one >> that is included in GCC 6. I'll have to test a cross-compilation from >> opensuse where they already have mingw-w64 GCC 6 packaged and see if things >> are in a better shape there. > > I also get a segfault when I cross-compile with GCC 6.1 from opensuse 13.2 > (needs wine to run this particular bootstrap build step), so this looks > like it's something else. To be sure, could you test the small ipa-ra.tgz > test case from the top of https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66655 > with your build? It runs correctly with my build where I've applied the > patch, but the larger Julia+LLVM case doesn't work. So this is something > new, and/or https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68601 wasn't > actually a duplicate of 66655. Will continue investigating. > > -Tony > > The -2 build already includes the patch on the 66655 link. signature.asc Description: OpenPGP digital signature
Re: [ANNOUNCEMENT] Updated: mingw64-*-gcc-5.4.0-2 (x86/x86_64)
> Sadly I seem to get similar-looking access violations even after rebuilding > 5.4.0-2 from the -src cygport with the patch for GCC bug 66655 added. So > maybe some other change is also needed to get this working, hopefully one > that is included in GCC 6. I'll have to test a cross-compilation from > opensuse where they already have mingw-w64 GCC 6 packaged and see if things > are in a better shape there. I also get a segfault when I cross-compile with GCC 6.1 from opensuse 13.2 (needs wine to run this particular bootstrap build step), so this looks like it's something else. To be sure, could you test the small ipa-ra.tgz test case from the top of https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66655 with your build? It runs correctly with my build where I've applied the patch, but the larger Julia+LLVM case doesn't work. So this is something new, and/or https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68601 wasn't actually a duplicate of 66655. Will continue investigating. -Tony -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
[ANNOUNCEMENT] Updated [x86]: {aalib/libaa1/aalib-devel}-1.4rc5-13: An ascii art library
Hi New versions of 'aalib/libaa1/aalib-devel' have been uploaded to a server near you. o Build for cygwin 2.5.2 with gcc-5.4.0 o removed /usr/lib/libaa.la file -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
[ANNOUNCEMENT] Updated: {gd/libgd3/libgd-devel}-2.2.3-1: A library for the dynamic creation of images by programmers
Hi New versions of 'gd/libgd3/libgd-devel' have been uploaded to a server near you. o Build for cygwin 2.5.2 with gcc-5.4.0 o Update to latest upstream release gd NEWS: o https://libgd.github.io/category/news.html -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: [ANNOUNCEMENT] Updated: mingw64-*-gcc-5.4.0-2 (x86/x86_64)
>> How long does building the cross-compiler from your cygport take, usually? >> I could try that and let you know if just applying the patch from >> >> https://gcc.gnu.org/viewcvs/gcc/trunk/gcc/config/i386/winnt.c?r1=232828&r2=232827&pathrev=232828 >> would fix matters. Not sure how many other packaging changes you'd need >> to go from 5.4.0 to 6.1.0. (And 6.2 should be coming shortly.) > > > Usually a 5-6 hours per target, but my machine is underpowered, testing > would be much appreciated. Sadly I seem to get similar-looking access violations even after rebuilding 5.4.0-2 from the -src cygport with the patch for GCC bug 66655 added. So maybe some other change is also needed to get this working, hopefully one that is included in GCC 6. I'll have to test a cross-compilation from opensuse where they already have mingw-w64 GCC 6 packaged and see if things are in a better shape there. -Tony -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: Is there a newer syslog-ng in the works?
On Aug 17 16:09, Matthew Hatch wrote: > Hi, > > I've noticed that syslog-ng hasn't received much attention in cygwin > and is several years out of date (3.2.5). As such, it is missing some > features that are useful and pretty standard today in most syslog > daemons (ie: support for multi-line messages). Is there any chance of > getting an updated version (say, 3.7+) built and released? All versions after 3.2 don't work on Cygwin anymore because the syslog-ng developers introduced a module loader mechanism incompatible with Cygwin. Updating to a newer version requires considerable porting effort. If somebody has fun to take over syslog-ng maintainership and work with upstream on a modernised Cygwin port, please feel free. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Maintainer cygwin AT cygwin DOT com Red Hat signature.asc Description: PGP signature
Re: /dev/ptmx fails with Azure accounts
On Aug 16 17:45, Corinna Vinschen wrote: > On Aug 16 11:27, rm...@aboutgolf.com wrote: > > Hi Corinna > > > > On Tuesday, August 16, 2016 05:12, "Corinna Vinschen" > > said: > > > > > Hi Russell, > > > > > > This is as bad as I feared. Apart from the username and the Windows > > > home dir, there are no other information which could be fetched by > > > the usual means. Quite apart from the fact that there are no means to > > > *store* this information somewhere, other than creating an explicit > > > /etc/passwd and matching /etc/group entry. > > > > > > But, anyway, I prepared some code for the Cygwin DLL to handle these > > > accounts even if no /etc/passwd and /etc/group entries are present. It > > > still needs some work, though, and for that I'd ask you to perform a > > > last test. > > > [...] > > Unknown+User@Lenovo-PC /cygdrive/c/cygwin64 > > $ gcc -W azure-check5.c -l Netapi32 -o azure-check5 > > > > Unknown+User@Lenovo-PC /cygdrive/c/cygwin64 > > $ ./azure-check5 > > Sid: S-1-12-1-2043906341-1249388050-2635137163-399631282 > > Dom\Name: AzureAD\RussellMora > > Reverse Sid (RussellMora): > > S-1-12-1-2043906341-1249388050-2635137163-399631282 > > Reverse Sid (AzureAD\RussellMora): > > S-1-12-1-2043906341-1249388050-2635137163-399631282 > > Good to know, thank you. Give me a bit and I'll come up with a Cygwin > DLL for testing. FTR, this has been kinked out off-list. The resulting patch is in git master now. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Maintainer cygwin AT cygwin DOT com Red Hat signature.asc Description: PGP signature
Re: [ANNOUNCEMENT] Updated: mingw64-*-gcc-5.4.0-2 (x86/x86_64)
On 8/18/2016 08:19, Tony Kelman wrote: >> Normally, new versions will first show up for cygwin native gcc before >> being handed down to the cross compilers. I'll see about doing a test >> version. > > How long does building the cross-compiler from your cygport take, usually? > I could try that and let you know if just applying the patch from > https://gcc.gnu.org/viewcvs/gcc/trunk/gcc/config/i386/winnt.c?r1=232828&r2=232827&pathrev=232828 > would fix matters. Not sure how many other packaging changes you'd need > to go from 5.4.0 to 6.1.0. (And 6.2 should be coming shortly.) > Usually a 5-6 hours per target, but my machine is underpowered, testing would be much appreciated. signature.asc Description: OpenPGP digital signature
