Jack wierdness

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Just downloaded some updates in Suse 10.1 and now Jack won't start with
the output message
10:15:09.194 Startup script...
10:15:09.197 artsshell -q terminate
unix_connect: can't connect to server
(unix:/tmp/ksocket-jonty/Hardcore101.site-3927-45230e26)
10:15:09.697 Startup script terminated with exit status=256.
10:15:09.700 JACK is starting...
10:15:09.701 jackd -R -p128 -dalsa -dhw:0 -r44100 -p512 -n2
10:15:09.734 JACK was started with PID=5500 (0x157c).
jackd 0.102.20
Copyright 2001-2005 Paul Davis and others.
jackd comes with ABSOLUTELY NO WARRANTY
This is free software, and you are welcome to redistribute it
under certain conditions; see the file COPYING for details
JACK compiled with POSIX SHM support.
cannot use real-time scheduling (FIFO at priority 10) [for thread
-1210202448, from thread -1210202448] (1: Operation not permitted)
cannot create engine
10:15:09.742 JACK was stopped successfully.
10:15:11.828 Could not connect to JACK server as client. Please check the
messages window for more info.

I don't understand this. The only thing I think it could be is "cannot use
real-time scheduling (FIFO at priority 10) [for thread
-1210202448, from thread -1210202448] (1: Operation not permitted)" but I
have no idea how to do it. Having googled the best I found was to reboot.

I checked if it ran as root, which it did. Which device do I have to
change persmissions of to get ti to run as user again, and why on earth
would an update change who is allowed to start it? It's worked as user up
until now!

Many thanks in advance.
God Bless
Jonty



[Index of Archives]     [Linux Sound]     [ALSA Users]     [Pulse Audio]     [ALSA Devel]     [Sox Users]     [Linux Media]     [Kernel]     [Photo Sharing]     [Gimp]     [Yosemite News]     [Linux Media]

  Powered by Linux