Closed rany2 closed 4 years ago
Not having expose-pids
support doesn't just mean that you'll have performance issues, it means that chromium would break
Oh gosh, that shouldn't be the case at all. I'll have to do some testing locally with the spawn strategy disabled and see what happens.
On Sat, Sep 26, 2020 at 8:13 AM analotia notifications@github.com wrote:
Not having expose-pids support doesn't just mean that you'll have performance issues, it means that chromium would break
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/refi64/zypak/issues/4#issuecomment-699494184, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAM4YSLCT7UOIZXP3LBXVA3SHXSILANCNFSM4R24QUSQ .
@rany2 would appreciate some testing to confirm that the PDF and printing issues are fixed (couldn't really test printing but PDFs should definitely work now)
@refi64 Better late than never but zypak does work now. Printing, PDF, etc... all work. Just saw your comment...
Almost all the other problems I was facing before with zypak were resolved after I enabled support for user namespaces in bubblewrap.
You might want to tell your Chrome flatpak users that printing, pdfs, etc. all would work when you remove bwrap's SUID and enable userns.