That's fixed in liboobs 2.29.90. Have you asked Chris before assigning him this bug? Generally, there's no need for that, since he will package the new version when he finds time to do it, disregarding the Assignee status.
That's fixed in liboobs 2.29.90. Have you asked Chris before assigning him this bug? Generally, there's no need for that, since he will package the new version when he finds time to do it, disregarding the Assignee status.