RE: New installation of Cygwin64: xinit.sh exit code 3
>> Should have added: the file /var/log/setup.log shows no detail beyond
>> 2023/10/21 09:29:46 running: G:\console64\bin\bash.exe --norc --noprofile
>> "/etc/postinstall/xinit.sh"
>> 2023/10/21 09:29:49 abnormal exit: exit code=3
>>
>> -Original Message-
>>
>> I made a new installation of Cygwin 64 on a new USB stick, including the
>> package xinit.
>> (I use setup -P followed by a longish but far from complete list of required
>> packages ..,..,xinit,..,..)
>> At this first use of setup I got a single error message:
>>Package: _/xinit xinit.sh exit code 3
>> At 2nd and all subsequent uses of setup (i.e. as update) I get the slightly
>> altered error message:
>>Package: _/Unknown package xinit.sh exit code 3
>> In practice, any usage of xinit (e.g. to launch xterm) seems to work
>> perfectly well, but the repeated
>> error message at any update transaction (including when empty) is
>> disconcerting.
>> I have not tried an explicit command "bash (or dash)
>> /etc/postinstall/xinit.sh" as - even if this worked -
>> I would prefer to canvass opinion on this minor glitch.
>> All the same - the glitch is recent, despite being minor .. ..
> What filesystem is the drive formatted as: NTFS, ExFAT, FAT32, or other?
> Try rerunning the xinit postinstall script as follows and report the failing
> command(s) and error messages:
> $ CYGWINFORALL=-A /bin/sh -vx /etc/postinstall/xinit.sh
Thank you!
1. The identical error msg occurs on all of NTFS, FAT32, exFAT file systems.
2. The output from your test command is identical on all file systems,
3. The failing commands are the two separate "case .. mkdir .. mkshortcut"
sequences that occur
at the end of the xinit.sh script, with consequent error notification as
follows:
case $(uname -s) in *-WOW*) wow64=" (32-bit)" ;; esac
+ case $(uname -s) in
++ uname -s
/usr/bin/mkdir -p "$(/usr/bin/cygpath $CYGWINFORALL -P)/Cygwin-X${wow64}"
++ /usr/bin/cygpath -A -P
+ /usr/bin/mkdir -p '/cygdrive/c/ProgramData/Microsoft/Windows/Start
Menu/Programs/Cygwin-X'
/usr/bin/mkshortcut $CYGWINFORALL -P -w / -i /usr/bin/xwin-xdg-menu.exe -n
"Cygwin-X${wow64}/XWin Server" -a "--quote /usr/bin/bash.exe
-l -c \"cd; exec /usr/bin/startxwin\"" /usr/bin/run.exe
+ /usr/bin/mkshortcut -A -P -w / -i /usr/bin/xwin-xdg-menu.exe -n
'Cygwin-X/XWin Server' -a '--quote /usr/bin/bash.exe
-l -c "cd; exec /usr/bin/startxwin"' /usr/bin/run.exe
mkshortcut: Saving "/cygdrive/c/ProgramData/Microsoft/Windows/Start
Menu/Programs/Cygwin-X/XWin Server.lnk" failed;
does the target directory exist?
case $(uname -s) in *-WOW*) wow64=" (32-bit)" ;; esac
+ case $(uname -s) in
++ uname -s
/usr/bin/mkdir -p "$(/usr/bin/cygpath $CYGWINFORALL -P)/Cygwin-X${wow64}"
++ /usr/bin/cygpath -A -P
+ /usr/bin/mkdir -p '/cygdrive/c/ProgramData/Microsoft/Windows/Start
Menu/Programs/Cygwin-X'
/usr/bin/mkshortcut $CYGWINFORALL -P -w / -i /usr/bin/XWin.exe -n
"Cygwin-X${wow64}/User script" -a "--quote /usr/bin/bash.exe
-l -c \"cd; XSESSION_ICON= exec /usr/bin/startx /etc/X11/xinit/Xsession
xinit-compat\"" /usr/bin/run.exe
+ /usr/bin/mkshortcut -A -P -w / -i /usr/bin/XWin.exe -n 'Cygwin-X/User script'
-a '--quote /usr/bin/bash.exe
-l -c "cd; XSESSION_ICON= exec /usr/bin/startx /etc/X11/xinit/Xsession
xinit-compat"' /usr/bin/run.exe
mkshortcut: Saving "/cygdrive/c/ProgramData/Microsoft/Windows/Start
Menu/Programs/Cygwin-X/User script.lnk" failed;
does the target directory exist?
When I used Explorer to visit C:\ProgramData\Microsoft\Windows\Start
Menu\Cygwin-X I was told:
"You don't currently have permission to access this folder"
and clicking on Continue to get access I was told:
"You have been denied permission to access this folder"
There was then offered an option to edit Permissions which I didn't feel like
pursuing.
(I am the Administrator on my own standalone Windows machine. The denial of
access to Cygwin-X feels odd.
PS I also have Cygwin32 installed and running. I _am_ permitted access to the
equivalent folder Cygwin-X (32-bit).)
--
Problem reports: https://cygwin.com/problems.html
FAQ: https://cygwin.com/faq/
Documentation:https://cygwin.com/docs.html
Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple
Cygwin |chroot()| "bad" - but what should replace it ? / was: Re: process substitution to create a virtual file doesn't work in chroot environment
On Mon, Aug 28, 2023 at 10:50 AM Corinna Vinschen via Cygwin wrote: > On Aug 27 18:13, Cary Lewis via Cygwin wrote: [snip > The chroot implementation is old, bad, and deprecated. I was going > to rip it out entirely for I don't know how often already, but there > was always somebody asking to keep it. Given that it never did what > chroot is intended, don't use it. What should replace it if you rip it out ? And why is the implemenation "bad" ? Bye, Roland -- __ . . __ (o.\ \/ /.o) roland.ma...@nrubsig.org \__\/\/__/ MPEG specialist, C&&JAVA&&Sun&&Unix programmer /O /==\ O\ TEL +49 641 3992797 (;O/ \/ \O;) -- Problem reports: https://cygwin.com/problems.html FAQ: https://cygwin.com/faq/ Documentation:https://cygwin.com/docs.html Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple
Re: New installation of Cygwin64: xinit.sh exit code 3
On 2023-10-21 04:52, Fergus Daly via Cygwin wrote: Should have added: the file /var/log/setup.log shows no detail beyond 2023/10/21 09:29:46 running: G:\console64\bin\bash.exe --norc --noprofile "/etc/postinstall/xinit.sh" 2023/10/21 09:29:49 abnormal exit: exit code=3 -Original Message- I made a new installation of Cygwin 64 on a new USB stick, including the package xinit. (I use setup -P followed by a longish but far from complete list of required packages ..,..,xinit,..,..) At this first use of setup I got a single error message: Package: _/xinit xinit.sh exit code 3 At 2nd and all subsequent uses of setup (i.e. as update) I get the slightly altered error message: Package: _/Unknown package xinit.sh exit code 3 In practice, any usage of xinit (e.g. to launch xterm) seems to work perfectly well, but the repeated error message at any update transaction (including when empty) is disconcerting. I have not tried an explicit command "bash (or dash) /etc/postinstall/xinit.sh" as - even if this worked - I would prefer to canvass opinion on this minor glitch. All the same - the glitch is recent, despite being minor .. .. What filesystem is the drive formatted as: NTFS, ExFAT, FAT32, or other? Try rerunning the xinit postinstall script as follows and report the failing command(s) and error messages: $ CYGWINFORALL=-A /bin/sh -vx /etc/postinstall/xinit.sh -- Take care. Thanks, Brian Inglis Calgary, Alberta, Canada La perfection est atteinte Perfection is achieved non pas lorsqu'il n'y a plus rien à ajouter not when there is no more to add mais lorsqu'il n'y a plus rien à retirer but when there is no more to cut -- Antoine de Saint-Exupéry -- Problem reports: https://cygwin.com/problems.html FAQ: https://cygwin.com/faq/ Documentation:https://cygwin.com/docs.html Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple
RE: New installation of Cygwin64: xinit.sh exit code 3
Should have added: the file /var/log/setup.log shows no detail beyond 2023/10/21 09:29:46 running: G:\console64\bin\bash.exe --norc --noprofile "/etc/postinstall/xinit.sh" 2023/10/21 09:29:49 abnormal exit: exit code=3 -Original Message- I made a new installation of Cygwin 64 on a new USB stick, including the package xinit. (I use setup -P followed by a longish but far from complete list of required packages ..,..,xinit,..,..) At this first use of setup I got a single error message: Package: _/xinit xinit.sh exit code 3 At 2nd and all subsequent uses of setup (i.e. as update) I get the slightly altered error message: Package: _/Unknown package xinit.sh exit code 3 In practice, any usage of xinit (e.g. to launch xterm) seems to work perfectly well, but the repeated error message at any update transaction (including when empty) is disconcerting. I have not tried an explicit command "bash (or dash) /etc/postinstall/xinit.sh" as - even if this worked - I would prefer to canvass opinion on this minor glitch. All the same - the glitch is recent, despite being minor .. .. -- Problem reports: https://cygwin.com/problems.html FAQ: https://cygwin.com/faq/ Documentation:https://cygwin.com/docs.html Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple
New installation of Cygwin64: xinit.sh exit code 3
I made a new installation of Cygwin 64 on a new USB stick, including the package xinit. (I use setup -P followed by a longish but far from complete list of required packages ..,..,xinit,..,..) At this first use of setup I got a single error message: Package: _/xinit xinit.sh exit code 3 At 2nd and all subsequent uses of setup (i.e. as update) I get the slightly altered error message: Package: _/Unknown package xinit.sh exit code 3 In practice, any usage of xinit (e.g. to launch xterm) seems to work perfectly well, but the repeated error message at any update transaction (including when empty) is disconcerting. I have not tried an explicit command "bash (or dash) /etc/postinstall/xinit.sh" as - even if this worked - I would prefer to canvass opinion on this minor glitch. All the same - the glitch is recent, despite being minor .. .. -- Problem reports: https://cygwin.com/problems.html FAQ: https://cygwin.com/faq/ Documentation:https://cygwin.com/docs.html Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple
Re: Cygwin/X - *bizarre discovery* doorknock like behaviour for new windows
Hi, On 20/10/2023 12:40 pm, Shaddy Baddah via Cygwin wrote: On 20/10/2023 11:50 am, Shaddy Baddah via Cygwin wrote: What I am seeing is that for Cygwin/X, in multi-window mode (and it just occurred to me it would be helpful to check the behaviour in rooted(? manual page terminology) mode. I'll follow-up on this)... in multi-window mode (Xwin -multiwindow), when I try to open an X window for any given app, it is not displayed on the first run. For completeness, rooted mode does not have this issue. Also, a further note, once reproduced, further reproductions may require exiting XWin, and restarting it. I've found a bizarre, and to me, a hilarious, reason for this behaviour. So my assertion that it happens once per app is wrong. It happens only on the very first run of an X11 app on a newly started Xwin server. I guess I noticed this when I ran different X11 apps as the first run app against the Xwin server, and drew that longbow. Apologies for any confusion. But it still happens that very first time. *And* the app is actually displayed. Bizarely though, it is trapped within the confines of the ConEmu (https://conemu.github.io/) command session Xwin was started under. So if that ConEmu session is not at the front of the visible stack, you have no idea the app has been displayed/rendered. I haven't looked, but I speculate ConEmu, which is feature rich, has some feature that makes it act as a "rooted" X window? It feels like a reach though... the other theory is that something with it's DLL injection perhaps. I'll look at that separate from Cygwin/X though. I have tried using regular Windows command prompt, and this doesn't happen. Nor with the Windows (Metro) Terminal app. Again, sorry for any confusion this has caused. -- Regards, Shaddy -- Problem reports: https://cygwin.com/problems.html FAQ: https://cygwin.com/faq/ Documentation:https://cygwin.com/docs.html Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple
