This may have already been addressed and in my tendency to ignore pd list traffic I missed the explanation, but here is what is going on.
I am running a fairly fresh install of Fedora 26. I downloaded the source to Pd, installed alsa-lib-devel and tk (for wish), then built pd using makefile.gnu. Everything works when I start pd without super user privileges, except priority 92 scheduling is denied me. When I start pd using sudo, pd doesn't start and I get the following errors on the command prompt:
sudo ./pd
No protocol specified No protocol specified application-specific initialization failed: couldn't connect to display ":0.0"
These messages are not particularly helpful for me. Anybody know what is wrong?
Cheers,
David
On 2018-01-09 06:37, David Medine wrote:
This may have already been addressed and in my tendency to ignore pd list traffic I missed the explanation, but here is what is going on.
I am running a fairly fresh install of Fedora 26. I downloaded the source to Pd, installed alsa-lib-devel and tk (for wish), then built pd using makefile.gnu.
i'm not sure whether makefile.gnu is actually still used by anybody (including miller). the suggested way is to use autotools. $ ./autgen.sh && ./configure && make
Everything works when I start pd without super user privileges, except priority 92 scheduling is denied me.
add your user to the "audio" group and add the following to a file like /etc/security/limits.d/audio.conf
@audio - rtprio 95 @audio - memlock unlimited
When I start pd using sudo,
oh my, thou shalt never run random applications as root. moreso, thou shalt not run GUI applications as root.
btw, why do you think that you *must* have realtime priorities? do youget dropouts when running without?
pd doesn't start and I get the following errors on the command prompt:
sudo ./pd
No protocol specified No protocol specified application-specific initialization failed: couldn't connect to display ":0.0"
These messages are not particularly helpful for me. Anybody know what is wrong?
Pd you cannot connect to the X server (the display server).
does it work for other applications?
the standard test used to be xclock (sudo xclock), but i'm not sure
whether it is installed on your system.
searching the web, i found a few suggestions how to solve the problem (not fedora specific):
https://askubuntu.com/questions/175611/ https://forums.opensuse.org/showthread.php/405624-sudo-doesnt-open-X-program...
but to re-iterate: you should never run Pd as root. instead, allow your user to request realtime priviliges.
fgbmadr IOhannes
aha. I was simply (mistakenly) under the impression that one had to have super user priv to get the rt priority. I didn't know that running programs as root was so verboten.
I'm not getting dropouts, I simply wanted to have all the goodies if need be.
On 1/9/2018 9:49 AM, IOhannes m zmoelnig wrote:
On 2018-01-09 06:37, David Medine wrote:
This may have already been addressed and in my tendency to ignore pd list traffic I missed the explanation, but here is what is going on.
I am running a fairly fresh install of Fedora 26. I downloaded the source to Pd, installed alsa-lib-devel and tk (for wish), then built pd using makefile.gnu.
i'm not sure whether makefile.gnu is actually still used by anybody (including miller). the suggested way is to use autotools. $ ./autgen.sh && ./configure && make
Everything works when I start pd without super user privileges, except priority 92 scheduling is denied me.
add your user to the "audio" group and add the following to a file like /etc/security/limits.d/audio.conf
@audio - rtprio 95 @audio - memlock unlimited
When I start pd using sudo,
oh my, thou shalt never run random applications as root. moreso, thou shalt not run GUI applications as root.
btw, why do you think that you *must* have realtime priorities? do youget dropouts when running without?
pd doesn't start and I get the following errors on the command prompt:
sudo ./pd
No protocol specified No protocol specified application-specific initialization failed: couldn't connect to display ":0.0"
These messages are not particularly helpful for me. Anybody know what is wrong?
Pd you cannot connect to the X server (the display server).
does it work for other applications? the standard test used to be xclock (
sudo xclock), but i'm not sure whether it is installed on your system.searching the web, i found a few suggestions how to solve the problem (not fedora specific):
https://askubuntu.com/questions/175611/ https://forums.opensuse.org/showthread.php/405624-sudo-doesnt-open-X-program...
but to re-iterate: you should never run Pd as root. instead, allow your user to request realtime priviliges.
fgbmadr IOhannes
Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management -> https://lists.puredata.info/listinfo/pd-list
Yes, FYI I'm still using makefile.gnu. It takes about 25% as long to do the job as the automake thing does, and when it fails I can usually figure out why.
I'll probably keep that possibliity alive as long as I can. cheers Miller
On Tue, Jan 09, 2018 at 09:49:17AM +0100, IOhannes m zmoelnig wrote:
On 2018-01-09 06:37, David Medine wrote:
This may have already been addressed and in my tendency to ignore pd list traffic I missed the explanation, but here is what is going on.
I am running a fairly fresh install of Fedora 26. I downloaded the source to Pd, installed alsa-lib-devel and tk (for wish), then built pd using makefile.gnu.
i'm not sure whether makefile.gnu is actually still used by anybody (including miller). the suggested way is to use autotools. $ ./autgen.sh && ./configure && make
[rest of msg deleted]
On 01/09/2018 06:17 PM, Miller Puckette wrote:
Yes, FYI I'm still using makefile.gnu. It takes about 25% as long to do the job as the automake thing does, and when it fails I can usually figure out why.
I'll probably keep that possibliity alive as long as I can.
thanks for the clarification. i thought you were using autotools, because that's what's documented in the release checklist (linux/README.txt)
gfasrdm IOhannes
you need to add yourself to the @audio group and set your security limits
google it
Patrick Pagano B.S, M.F.A
Assistant Professor in Residence
Digital Media & Design
Web & Interactive Technologies
University of Connecticut, Stamford
(352)-226-2016
From: Pd-list pd-list-bounces@lists.iem.at on behalf of David Medine dmedine@ucsd.edu Sent: Tuesday, January 9, 2018 12:37:56 AM To: pd-list@lists.iem.at Subject: [PD] pd-0.48.1 trouble getting started
This may have already been addressed and in my tendency to ignore pd list traffic I missed the explanation, but here is what is going on.
I am running a fairly fresh install of Fedora 26. I downloaded the source to Pd, installed alsa-lib-devel and tk (for wish), then built pd using makefile.gnu. Everything works when I start pd without super user privileges, except priority 92 scheduling is denied me. When I start pd using sudo, pd doesn't start and I get the following errors on the command prompt:
sudo ./pd
No protocol specified No protocol specified application-specific initialization failed: couldn't connect to display ":0.0"
These messages are not particularly helpful for me. Anybody know what is wrong?
Cheers,
David
Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management -> https://lists.puredata.info/listinfo/pd-list
-
David Medine -
IOhannes m zmoelnig -
IOhannes m zmölnig
-
Miller Puckette -
Pagano, Patrick