Date: Wed, 05 Apr 2017 06:04:06 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-ports-bugs@FreeBSD.org Subject: [Bug 218389] audio/pd won't run with GUI under X with shells/bash as default shell Message-ID: <bug-218389-13@https.bugs.freebsd.org/bugzilla/>
next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D218389 Bug ID: 218389 Summary: audio/pd won't run with GUI under X with shells/bash as default shell Product: Ports & Packages Version: Latest Hardware: amd64 OS: Any Status: New Severity: Affects Some People Priority: --- Component: Individual Port(s) Assignee: freebsd-ports-bugs@FreeBSD.org Reporter: gen-freebsd@bigblock.com.au CC: brittlehaus@gmail.com, ehaupt@FreeBSD.org CC: brittlehaus@gmail.com, ehaupt@FreeBSD.org [thom@sasquatch ~]$ uname -a FreeBSD sasquatch 11.0-RELEASE-p8 FreeBSD 11.0-RELEASE-p8 #0: Wed Feb 22 06:12:04 UTC 2017 root@amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC amd64 # pkg install pd [thom@sasquatch ~]$ pd priority 7 scheduling failed. priority 7 scheduling failed. priority 7 scheduling failed. priority 7 scheduling failed. priority 7 scheduling failed. priority 7 scheduling failed. priority 7 scheduling failed. priority 7 scheduling failed. priority 7 scheduling failed. priority 7 scheduling failed. priority 7 scheduling failed. priority 7 scheduling failed. priority 7 scheduling failed. priority 7 scheduling failed. priority 7 scheduling failed. priority 7 scheduling failed. priority 7 scheduling failed. priority 7 scheduling failed. priority 7 scheduling failed. priority 7 scheduling failed. priority 7 scheduling failed. priority 7 scheduling failed. bind: Address already in use Pd needs your machine to be configured with 'networking' turned on (see Pd's html doc for details.) watchdog: signaling pd... watchdog: signaling pd... watchdog: signaling pd... also nothing appears to happen when i run (in bash) [thom@sasquatch ~]$ pd -guiport 127.0.0.1:5400 [thom@sasquatch ~]$=20 No GUI appears. The audio/pd maintainer confirmed the same issue after using chsh to change= to bash from tcsh, and advised me to file this bug, adding "you need to log in with a shell that can locate pd's gui socket. I *think* this is a bug in how FreeBSD handles korn and bourne shells insta= lled from ports. I haven't tested zsh or fish. " Workaround is to use tcsh in the meantime. --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-218389-13>