You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
On several occasion the GUI has locked up and become unresponsive. On most recent occasion this was when switching Screens from FFT to R128. Switching to terminal I can see that pam2 process is taking 123% CPU. Killing pam2 process does not relaunch PAM GUI. (Killing lightdm restarts UI with login prompt.)
After reboot I was able to reproduce the issue. Selecting R128 (from any Screen) seems to lock up the display (if AES67 source selected).
The text was updated successfully, but these errors were encountered:
On several occasion the GUI has locked up and become unresponsive. On most recent occasion this was when switching Screens from FFT to R128. Switching to terminal I can see that pam2 process is taking 123% CPU. Killing pam2 process does not relaunch PAM GUI. (Killing lightdm restarts UI with login prompt.)
After reboot I was able to reproduce the issue. Selecting R128 (from any Screen) seems to lock up the display (if AES67 source selected).
The text was updated successfully, but these errors were encountered: