how to access and display apps that I've launched

[Ken Brown]

On 7/24/2017 6:08 PM, Ian Lambert via cygwin wrote:
> This time I ran "rebase-trigger full", did full shutdown/restart, then ran setup.

And are you sure there were no Cygwin processes running?  This could 
happen even after shutdown/restart if you have any Cygwin services that 
start automatically.

> and some rebase-related touch error messages in setup.log.full:
> 
>   2017/07/24 17:24:08 running: E:\cygwin64-3\bin\dash.exe "/etc/postinstall/0p_000_autorebase.dash"
> Note: _autorebase will do a full rebase the next time setup is run.
> removing /var/cache/rebase/rebase_pkg
> creating empty /var/cache/rebase/rebase_pkg
> touch: setting times of '/var/cache/rebase/rebase_pkg': Invalid argument
> Updating package information in /var/cache/rebase/rebase_pkg.
> removing /var/cache/rebase/rebase_lst
> creating empty /var/cache/rebase/rebase_lst
> touch: setting times of '/var/cache/rebase/rebase_lst': Invalid argument
> Updating rebase information for installed executables in /var/cache/rebase/rebase_exe.
> removing /var/cache/rebase/rebase_dyn
> creating empty /var/cache/rebase/rebase_dyn
> touch: setting times of '/var/cache/rebase/rebase_dyn': Invalid argument
> Looking for dynamic language modules/libraries in:
>    /usr/lib/R/site-library
>    /usr/lib/php/20151012
>    /usr/lib/python2.7/site-packages
>    /usr/lib/python3.6/site-packages
> Updating rebase information for dynamic language modules/libraries /var/cache/rebase/rebase_dyn.
> removing /var/cache/rebase/rebase_user
> creating empty /var/cache/rebase/rebase_user
> touch: setting times of '/var/cache/rebase/rebase_user': Invalid argument
> Updating rebase information for user-defined dynamic objects /var/cache/rebase/rebase_user.
> removing /var/cache/rebase/rebase_user_exe
> creating empty /var/cache/rebase/rebase_user_exe
> touch: setting times of '/var/cache/rebase/rebase_user_exe': Invalid argument

I have no idea what would cause such error messages.  Achim, have you 
ever seen this?

>    0 [main] nautilus 3240 child_info_fork::abort: E:\cygwin64-3\bin\cygpangocairo-1.0-0.dll: Loaded to different address: parent(0x3F0000) != child(0x2F0000)
>        0 [main] nautilus 3396 child_info_fork::abort: E:\cygwin64-3\bin\cygpangocairo-1.0-0.dll: Loaded to different address: parent(0x3F0000) != child(0x2F0000)
>        0 [main] nautilus 5840 child_info_fork::abort: E:\cygwin64-3\bin\cygpangocairo-1.0-0.dll: Loaded to different address: parent(0x3F0000) != child(0x400000)

This kind of fork error can be very stubborn.  The best long-term 
solution is to switch to 64-bit Cygwin if you can.  If you absolutely 
have to stick to 32-bit, try to limit the number of DLLs that are installed.

Ken

--
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