[LAU] no realtime priority possible with wdm/openbox

[Thomas Kuther]

On Sa, 15.11.08 15:47 Atte Andrê Jensen <atte.jensen at gmail.com> wrote:

> Hi
> 
> I have a cpu-hog problem with my debian/lenny and someone suggested
> it might be caused by gnome. So I installed wdm (instead of gdm) and 
> openbox to completely bypass any gnome stuff.
> 
> However when I log in from wdm to openbox I cannot start jack with 
> realtime priority, I get this in the messages window of qjackctl:
> 
> 15:45:00.693 Patchbay deactivated.
> 15:45:00.695 Statistics reset.
> 15:45:00.705 JACK is starting...
> 15:45:00.706 /usr/bin/jackd -R -P80 -dalsa -dhw:1 -r44100 -p256 -n3 -s
> 15:45:00.723 ALSA connection graph change.
> jackd 0.109.2
> 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 System V SHM support.
> cannot use real-time scheduling (FIFO at priority 10) [for thread 
> -1209067856, from thread -1209067856] (1: Operation not permitted)
> cannot create engine
> 15:45:00.750 JACK was started with PID=14293.
> 15:45:00.763 JACK was stopped successfully.
> 15:45:00.763 Post-shutdown script...
> 15:45:00.764 killall jackd
> 15:45:00.909 ALSA connection change.
> jackd: no process killed
> 15:45:01.170 Post-shutdown script terminated with exit status=256.
> 15:45:02.913 Could not connect to JACK server as client. - Overall 
> operation failed. - Unable to connect to server. Please check the 
> messages window for more info.
> 
> Esp the "cannot use real-time scheduling (FIFO at priority 10) [for 
> thread -1209067856, from thread -1209067856] (1: Operation not 
> permitted)" seems to nail the problem.
> 
> What should I do to make it possible to start jack with realtime 
> priorities and why does it have anything to do with gnome? I've been 
> using this combo (wdm/openbox) in the past with no problem...
> 
> -- 
> Atte
> 

Hi Atte,

make sure that WDM uses PAM correctly on login.
If it does, maybe its pam service definition file misses

a) something like
    session    include      system-auth
or b)
    session    required    pam_limits.so

There should be something like /etc/pam.d/wdm - and the preferred way
is to include system-auth


HTH,
Thomas
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 197 bytes
Desc: not available
Url : http://lists.linuxaudio.org/pipermail/linux-audio-user/attachments/20081115/3362fe0e/attachment.pgp