Re: Unable to view pdf files

2019-10-11 Thread Brian Inglis
On 2019-10-11 17:15, Blair, Charles E III wrote:
>I have not been able to view pdf files, trying:
> (1) midori only offers applications for djvu, jpg,
> and dvi files.
> (2) ghostscript was listed as already installed, but
> gv file.pdf yields "command not found," and "man gv"
> and "man ghostcript" also don't work.  Neither did
> re-installing.
> (3) When I am running emacs and open file.pdf, I get
> a display of code.  If I try C-c C-c to switch on
> DocView, I am told this is undefined.

Install package xpdf to get xpdfreader or package qpdfview to get qpdfview.
Both are offered from Open With... in PCManFM.
I find xpdfreader a bit closer to what you'd expect, but both work without
problems.
You can also install package gv (ghostview), but it has no X desktop menu
integration, and you have to manually launch this, optionally with (a) filename
argument(s).

-- 
Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada

This email may be disturbing to some readers as it contains
too much technical detail. Reader discretion is advised.

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



Unable to view pdf files

2019-10-11 Thread Blair, Charles E III
   I have not been able to view pdf files, trying:
   
(1) midori only offers applications for djvu, jpg,
and dvi files.

(2) ghostscript was listed as already installed, but
gv file.pdf yields "command not found," and "man gv"
and "man ghostcript" also don't work.  Neither did
re-installing.

(3) When I am running emacs and open file.pdf, I get
a display of code.  If I try C-c C-c to switch on
DocView, I am told this is undefined.

--
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] cygwin 3.1.0-0.7 (TEST)

2019-10-11 Thread Ken Brown
The following packages have been uploaded to the Cygwin distribution
as test releases:

* cygwin-3.1.0-0.7
* cygwin-devel-3.1.0-0.7
* cygwin-doc-3.1.0-0.7

This release comes with a couple of new features and quite a few
bug fixes.

The most interesting changes:

- A revamp of the old FIFO code.  It should now be possible to open
  FIFOs multiple times for writing, something the old code failed on.
  Courtesy Ken Brown.

- Support the new pseudo console in PTY. Pseudo console is a new feature
  in Windows 10 1809, which provides console APIs on virtual terminal.
  With this patch, native console applications can work in Cygwin PTYs.
  Courtesy Takashi Yano.

There have been a couple more bug fixes in the PTY code since
cygwin-3.1.0-0.6.  Please test!

===

What's new:
---

- Add 24 bit color support using xterm compatibility mode in Windows 10
  1703 or later.  Add fake 24 bit color support for legacy console,
  which uses the nearest color from 16 system colors.

- Support pseudo console in PTY. Pseudo console is a new feature
  in Windows 10 1809, which provides console APIs on virtual
  terminal. With this patch, native console applications can work
  in PTYs such as mintty, ssh, gnu screen or tmux.

- New APIs: sched_getaffinity, sched_setaffinity, pthread_getaffinity_np,
  pthread_setaffinity_np, plus CPU_SET macros.

- New APIs: dbm_clearerr, dbm_close, dbm_delete, dbm_dirfno, dbm_error,
  dbm_fetch, dbm_firstkey, dbm_nextkey, dbm_open, dbm_store.


What changed:
-

- FIFOs can now be opened multiple times for writing.
  Addresses: https://cygwin.com/ml/cygwin/2015-03/msg00047.html
 https://cygwin.com/ml/cygwin/2015-12/msg00311.html

- If a SA_SIGINFO signal handler changes the ucontext_t pointed to by
  the third parameter, follow it after returning from the handler.

- Eliminate a header file name collision with  on case
  insensitive filesystems by reverting  back to .

- Allow times(2) to have a NULL argument, as on Linux.
  Addresses: https://cygwin.com/ml/cygwin/2019-09/msg00141.html

- Improve /proc/cpuinfo output and align more closely with Linux.


Bug Fixes
-

- Fix select() on console in canonical mode.  Return after one line is
  completed, instead of when only one key is typed.

- Make console I/O functions thread-safe.

- Define missing MSG_EOR.  It's unsupported by the underlying Winsock
  layer so using it in send(2), sendto(2), or sendmsg(2) will return -1
  with errno set to EOPNOTSUPP and recvmsg(2) will never return it.

- Fix a timerfd deadlock.
  Addresses: https://cygwin.com/ml/cygwin/2019-06/msg00096.html

- Fix sigpending() incorrectly returning signals for unrelated threads.
  Addresses: https://cygwin.com/ml/cygwin/2019-07/msg00051.html

- Fix a hang when opening a FIFO with O_PATH.
  Addresses: https://cygwin.com/ml/cygwin-developers/2019-06/msg1.html

- Don't append ".lnk" when renaming a socket file.
  Addresses: https://cygwin.com/ml/cygwin/2019-07/msg00139.html

- Make tcsetpgrp() return -1 if its argument is negative.
  Addresses: https://cygwin.com/ml/cygwin/2019-07/msg00166.html

- Avoid mistakenly moving a process under debugger control into the
  process group of the debugger.
  Addresses a problem visible in GDB 8.1.1, related to
  https://cygwin.com/ml/cygwin/2019-07/msg00166.html

- Return ENOEXEC from execve for arbitrary files only if the files are
  executable.
  Addresses: https://cygwin.com/ml/cygwin/2019-08/msg00054.html

- Fix off-by-one in environment evaluation leading to an abort.
  Addresses: https://cygwin.com/ml/cygwin-patches/2019-q3/msg00069.html

- Make output of /proc/[PID]/stat consistent with getpriority().
  Addresses: https://cygwin.com/ml/cygwin/2019-08/msg00082.html

- 64 bit only: Avoid collisions between memory maps created with shmat
  and Windows datastructures during fork.
  Addresses: https://cygwin.com/ml/cygwin/2019-08/msg00107.html

- Make rmdir fail if its argument is a symlink.
  Addresses: https://cygwin.com/ml/cygwin/2019-09/msg00221.html

- Fix an assertion failure on an invalid path.
  Addresses: https://cygwin.com/ml/cygwin/2019-09/msg00228.html

- If the argument to mkdir(2) or rmdir(2) is 'x:\', don't strip the
  trailing backslash.
  Addresses: https://cygwin.com/ml/cygwin/2019-08/msg00334.html

===


Have fun,

Ken Brown, on behalf of Corinna

--
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: why is mintty trying to connect to google through my browser

2019-10-11 Thread Thomas Wolff




Am 11.10.2019 um 20:33 schrieb LMH:

Hello,

I had an odd thing happen today. I opened a cygwin terminal to do something and 
got a
firewall alert that mintty was attempting to inject network traffic. I did a
temporary deny because there is no reason for mintty to make a connection based 
on
what I was doing and I have never seen that alert before (or I would have a 
firewall
rule already). That alert doesn't say where the connection would be made to if 
the
injection was allowed.

This temporary block seemed to break my seamonkey connection. My firewall log 
is full
of entries about blocked connections for seamonkey and the reason given is
"restricted parent process c:\cygwin\bin\mintty". I did not launch seamonkey 
using
mintty, so I have no idea why the firewall would see mintty as the parent 
process.
All of the seamonkey attempted connections to my email server were also blocked 
for
the same reason. When I closed the terminal, everything  went back to normal.

It seems like mintty tried to inject some network traffic to the seamonkey 
process
and for some reason, blocking this injection caused the firewall to block all 
traffic
from seamonkey.

Why would mintty try to inject network traffic to another process at startup? 
If it
needed ot connect for some reason, why would mintty try to make that connection
through another application instead of just making the connection itself?
It does neither of that. Mintty only ever accesses the network if you 
open the Options dialog.
It occasionally looks up the current mintty version for an indication 
that you could update (disable with CheckVersionUpdate=0), and it 
downloads contents if you drag a URL onto the Theme configuration field 
(also planned for the Bell Wave file) or click on the "Color Scheme 
Designer" button.

I deleted any firewall rules for mintty and started the terminal again, but 
that does
not reproduce the situation at the moment.
This, and the fact that your system claimed mintty to be the parent of 
Seamonkey, suggests that something is or was utterly broken on your system.


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: why is mintty trying to connect to google through my browser

2019-10-11 Thread René Berber
On 10/11/2019 1:33 PM, LMH wrote:

[snip]
> I opened a cygwin terminal to do something and got a
> firewall alert that mintty was attempting to inject network traffic.
[snip]

Perhaps the .bashrc/.bash_profile/etc. script runs something that does that.
-- 
R.Berber


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



why is mintty trying to connect to google through my browser

2019-10-11 Thread LMH
Hello,

I had an odd thing happen today. I opened a cygwin terminal to do something and 
got a
firewall alert that mintty was attempting to inject network traffic. I did a
temporary deny because there is no reason for mintty to make a connection based 
on
what I was doing and I have never seen that alert before (or I would have a 
firewall
rule already). That alert doesn't say where the connection would be made to if 
the
injection was allowed.

This temporary block seemed to break my seamonkey connection. My firewall log 
is full
of entries about blocked connections for seamonkey and the reason given is
"restricted parent process c:\cygwin\bin\mintty". I did not launch seamonkey 
using
mintty, so I have no idea why the firewall would see mintty as the parent 
process.
All of the seamonkey attempted connections to my email server were also blocked 
for
the same reason. When I closed the terminal, everything  went back to normal.

It seems like mintty tried to inject some network traffic to the seamonkey 
process
and for some reason, blocking this injection caused the firewall to block all 
traffic
from seamonkey.

Why would mintty try to inject network traffic to another process at startup? 
If it
needed ot connect for some reason, why would mintty try to make that connection
through another application instead of just making the connection itself?

I deleted any firewall rules for mintty and started the terminal again, but 
that does
not reproduce the situation at the moment.

I believe this is cygwin 2.3.1.

LMH

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



Power and Energy Professionals

2019-10-11 Thread Anna Davis
Hi,

Would you be interested in Power and Energy Industry Contact List 2019?

The list covers renewable Industry, distributed energy Industry, digital
technology Industry, operations & maintenance Industry, engineering
Industry, environmental issues Industry, all fuels, and workforce
development Industry.

Here are few companies from the list: Associated Electric Cooperative Inc,
Consolidated Electric Cooperative Inc, Duke Energy, Graywolf Industrial and
more.

Let me know you preferred target audience and I will get back to you with
samples and other details.

Target Industry ___
Target Job titles__
Target location to sell? _ 

Looking forward to continued success with you!

Best Regards,
Anna Davis | Demand Generation| B2bprolist


If you don't wish to receive our newsletters, reply back with "UN-SUBSCRIBE"
in subject line.

 

 


--
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] cygwin 3.1.0-0.6 (TEST)

2019-10-11 Thread Takashi Yano
Hi Michael,

On Thu, 10 Oct 2019 12:43:56 +0200
Michael Haubenwallner wrote:
> I'm encountering another strange behaviour I do not remember to have seen 
> before:
> 
> Using ssh from some Linux xterm into the Cygwin sshd running on Server 2019
> does clear the current terminal content as if /usr/bin/clear was executed.

This is intentional behaviour.

The pseudo console has its own screen buffer behind, and redraws
the screen based on the screen buffer at undetermined timing.
The screen buffer is empty at the beginning, so the screen should
be cleared at the opening of the pty so that the real screen and
the screen buffer are synchronozed.

The clear screen is prevented when TERM=dumb, so you can see what
happens if clear screen is not done by following steps.

1)  Execute ls or ps to draw something to screen.
2) env TERM=dumb ssh 
3) Execute cmd.exe.

-- 
Takashi Yano 

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



openssh-server cannot handle certain Windows 10 account names

2019-10-11 Thread agent
I am running 12 Cygwin installations, all on Windows 10 and all with 
openssh-server.
Wheneven the computer and the account names are identical (for good or 
bad reasons) ssh access fails. Workaround: modify the computer name to 
somethng else.

Regards,
FMF

Cygwin Configuration Diagnostics
Current System Time: Fri Oct 11 07:55:58 2019

Windows 10 Professional Ver 10.0 Build 18362 

Running in Terminal Service session

Path:	C:\cygwin64\usr\local\bin
	C:\cygwin64\bin
	C:\Windows\system32
	C:\Windows
	C:\Windows\System32\Wbem
	C:\Windows\System32\WindowsPowerShell\v1.0
	C:\Windows\System32\OpenSSH
	C:\Program Files\PuTTY
	C:\Users\wbiat\AppData\Local\Microsoft\WindowsApps

Output from C:\cygwin64\bin\id.exe
UID: 197609(wbiat)  GID: 197609(wbiat)
=197609(wbiat)  401408(Mittlere Verbindlichkeitsstufe)
545(Benutzer)   14(INTERAKTIVE REMOTEANMELDUNG)
4(INTERAKTIV)   11(Authentifizierte Benutzer)
15(Diese Organisation)  68473(microsoftaccount+wbia...@aha.ovh)
113(Lokales Konto)  4095(CurrentSession)
66048(LOKAL)262180(Cloudkontoauthentifizierung)

SysDir: C:\Windows\system32
WinDir: C:\Windows

USER = 'wbiat'
PWD = '/home/wbiat'
HOME = '/home/wbiat'

USERDOMAIN = 'WBIAT12A'
OS = 'Windows_NT'
COMMONPROGRAMFILES = 'C:\Program Files\Common Files'
PROCESSOR_LEVEL = '22'
PSModulePath = 'C:\Program Files\WindowsPowerShell\Modules;C:\Windows\system32\WindowsPowerShell\v1.0\Modules'
CommonProgramW6432 = 'C:\Program Files\Common Files'
CommonProgramFiles(x86) = 'C:\Program Files (x86)\Common Files'
LANG = 'de_DE.UTF-8'
TZ = 'Europe/Berlin'
HOSTNAME = 'WBIAT12A'
PUBLIC = 'C:\Users\Public'
OLDPWD = '/home/wbiat'
USERNAME = 'wbiat'
LOGONSERVER = '\\WBIAT12A'
PROCESSOR_ARCHITECTURE = 'AMD64'
CLIENTNAME = 'BLESK'
LOCALAPPDATA = 'C:\Users\wbiat\AppData\Local'
COMPUTERNAME = 'WBIAT12A'
!:: = '::\'
SYSTEMDRIVE = 'C:'
USERPROFILE = 'C:\Users\wbiat'
PATHEXT = '.COM;.EXE;.BAT;.CMD;.VBS;.VBE;.JS;.JSE;.WSF;.WSH;.MSC'
SYSTEMROOT = 'C:\Windows'
USERDOMAIN_ROAMINGPROFILE = 'WBIAT12A'
PROCESSOR_IDENTIFIER = 'AMD64 Family 22 Model 0 Stepping 1, AuthenticAMD'
OneDriveConsumer = 'C:\Users\wbiat\OneDrive'
TMP = '/tmp'
OneDrive = 'C:\Users\wbiat\OneDrive'
PROCESSOR_REVISION = '0001'
PROFILEREAD = 'true'
NUMBER_OF_PROCESSORS = '4'
ProgramW6432 = 'C:\Program Files'
COMSPEC = 'C:\Windows\system32\cmd.exe'
APPDATA = 'C:\Users\wbiat\AppData\Roaming'
SHELL = '/bin/bash'
TERM = 'xterm'
WINDIR = 'C:\Windows'
ProgramData = 'C:\ProgramData'
SHLVL = '1'
MINTTY_SHORTCUT = '/cygdrive/c/Users/wbiat/AppData/Roaming/Microsoft/Internet Explorer/Quick Launch/User Pinned/TaskBar/Cygwin64 Terminal.lnk'
PRINTER = 'Microsoft Print to PDF'
PROGRAMFILES = 'C:\Program Files'
ALLUSERSPROFILE = 'C:\ProgramData'
TEMP = '/tmp'
DriverData = 'C:\Windows\System32\Drivers\DriverData'
SESSIONNAME = 'RDP-Tcp#3'
ProgramFiles(x86) = 'C:\Program Files (x86)'
PS1 = '\[\e]0;\w\a\]\n\[\e[32m\]\u@\h \[\e[33m\]\w\[\e[0m\]\n\$ '
HOMEDRIVE = 'C:'
INFOPATH = '/usr/local/info:/usr/share/info:/usr/info'
HOMEPATH = '\Users\wbiat'
ORIGINAL_PATH = '/cygdrive/c/Windows/system32:/cygdrive/c/Windows:/cygdrive/c/Windows/System32/Wbem:/cygdrive/c/Windows/System32/WindowsPowerShell/v1.0:/cygdrive/c/Windows/System32/OpenSSH:/cygdrive/c/Program Files/PuTTY:/cygdrive/c/Users/wbiat/AppData/Local/Microsoft/WindowsApps'
EXECIGNORE = '*.dll'
_ = '/usr/bin/cygcheck'

HKEY_CURRENT_USER\Software\Cygwin
HKEY_CURRENT_USER\Software\Cygwin\Installations
  (default) = '\??\C:\cygwin64'
HKEY_LOCAL_MACHINE\SOFTWARE\Cygwin
HKEY_LOCAL_MACHINE\SOFTWARE\Cygwin\Installations
  (default) = '\??\C:\cygwin64'
HKEY_LOCAL_MACHINE\SOFTWARE\Cygwin\setup
  (default) = 'C:\cygwin64'

obcaseinsensitive set to 1

Cygwin installations found in the registry:
  System: Key: e022582115c10879 Path: C:\cygwin64
  User:   Key: e022582115c10879 Path: C:\cygwin64

c:  hd  NTFS457225Mb   8% CP CS UN PA FCQU  

C:\cygwin64  /  system  binary,auto
C:\cygwin64\bin  /usr/bin   system  binary,auto
C:\cygwin64\lib  /usr/lib   system  binary,auto
cygdrive prefix  /cygdrive  userbinary,posix=0,auto

Found: C:\cygwin64\bin\awk
 -> C:\cygwin64\bin\gawk.exe
Found: C:\cygwin64\bin\bash.exe
Found: C:\cygwin64\bin\cat.exe
Found: C:\cygwin64\bin\cp.exe
Not Found: cpp (good!)
Found: C:\cygwin64\bin\crontab.exe
Found: C:\cygwin64\bin\find.exe
Found: C:\Windows\system32\find.exe
Warning: C:\cygwin64\bin\find.exe hides C:\Windows\system32\find.exe
Not Found: gcc
Not Found: gdb
Found: C:\cygwin64\bin\grep.exe
Found: C:\cygwin64\bin\kill.exe
Not Found: ld
Found: C:\cygwin64\bin\ls.exe
Not Found: make
Found: C:\cygwin64\bin\mv.exe
Not Found: patch
Not Found: perl
Found: C:\cygwin64\bin\rm.exe
Found: C:\cygwin64\bin\sed.exe
Found: C:\cygwin64\bin\ssh.exe
Found: C:\Windows\System32\OpenSSH\ssh.exe
Warning: C:\cygwin64\bin\ssh.exe hides C:\Windows\System32\OpenSSH\ssh.exe
Found: C:\cygwi