I figured that would be the case; it’s a known upstream issue. Thanks for confirming that I didn’t miss something obvious.
Should we mark the control file as breaks kernel < 590? Maybe just for libcuda1 (not quite accurate, but has a result closer to the observed issue)? Or just wait until it shakes out in November? Thanks, joelh
