X-Recipient: archive-cygwin AT delorie DOT com X-SWARE-Spam-Status: No, hits=-0.7 required=5.0 tests=BAYES_50,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,FREEMAIL_FROM,KHOP_THREADED,RCVD_IN_DNSWL_NONE,RCVD_IN_HOSTKARMA_YE,TW_GT,UNPARSEABLE_RELAY X-Spam-Check-By: sourceware.org X-Yahoo-SMTP: 8_xiA3OswBAlZA2mm58U4Jx14yQ2ZlO8BEdW4Dr6tlpwWw-- From: "Brian S. Wilson" To: References: <20120929193527 DOT M64303 AT ds DOT net> <5067C99F DOT 60108 AT gmail DOT com> <20120930131238 DOT M10095 AT ds DOT net> <20121001120725 DOT M34953 AT ds DOT net> <20121001142414 DOT M8007 AT ds DOT net> <20121003111101 DOT M13208 AT ds DOT net> Subject: RE: gnome and hicolor exit code 127 for /usr/bin .vs. /bin Date: Fri, 5 Oct 2012 16:13:10 -0400 Message-ID: <972EEFF84AA34684A3A02402217705B5@ncc1701> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit In-Reply-To: <20121003111101.M13208@ds.net> Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com I am going to make the assumption that someone is working the bug with /usr/bin/gtk-update-icon-cache not creating the icon-theme.cache file and reporting the 127 (file not found error). Since I've heard nothing else about this, I'm also assuming that no one needs any further information to debug this issue. > > > > >>> I have been doing setup updates for a few weeks with the error shown in the following paragraph. > > > > >>> > > > > >>> Package: Unknown package > > > > >>> gnome-icon-theme.sh exit code 127 > > > > >>> hicolor-icon-theme.sh exit code 127 > > > > >>> > > > > >>>> snip <<< > > > > the scripts are not incorrect. They works for almost everyone, > > > > but there is a unknown glitch on you machine, > > > > eventually it is only a "false" return error that fools setup.exe. > > > > > > Before I do the alternate installation suggested, is there anything > > > I may do to help debug the "unknown glitch". It is very consistent > > > on my Windows XP Pro > > > (SP3) system (3.33 GHz, 4 GB memory). If there is some log file, or > > > other diagnostic I could run while executing setup? > > > > I've done a little more testing and the 127 return code is coming > > from the "/usr/bin/gtk-update-icon-cache --force > > /usr/share/icons/..." command line in the scripts. I get the 127 > > error message even if I run this command from the command line. > > This call is supposed to update the icon cache file with the latest > > entries. The icon-theme.cache file does exist for both the hicolor > > and gnome directories. It appears that gtk-update-icon-cache does > > not return a zero exit code; but I don't see any reason for the 127 > > (file not found) error. > > The line should read "The icon-theme.cache file does not exist for > both the hicolor and gnome directories." This command is supposed > to create the cache file and it does not appear to be working. > I've just done an update from the Georgia Tech mirror and am now seeing a message saying the perl manpages have a corrupt local copy and should be deleted. I deleted my local copy, but can't download a new copy. I switched to the Virginia Tech mirror and was able to download the man pages, but also got a new file not found error as shown in the following paragraph. Apparently there is a new package set needed for some of the packages I've already installed. Package: gnubg gnubg.sh exit code 127 Package: Unknown package gnome-icon-theme.sh exit code 127 hicolor-icon-theme.sh exit code 127 I did the same investigation and found the gnubg.sh script has the line "/usr/bin/gtk-update-icon-cache --force /usr/share/icons/hicolor" which returns the 127 error and does not create the icon-theme.cache file. The gtk-update- icon-cache executable does not appear to work as documented. Please treat this as a bug report. I would be happy to assist with further debugging, but will need guidance as to what would be most useful. -- 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