It should remain as confirmed for now I think. The next step is to apply the patch to the ubuntu package and use that to create a debdiff. The debdiff should the be attached to this bug and then you subscribe ubuntu-main-sponsors or ubuntu-universe-sponsors as appropriate and request sponsorship (these guys will update it to ubuntu repo and then it will arrive as a normal update).
PS. Note that if you can get the patch applied upstream, that's great because it makes it easier to convince ubuntu sponsors that it's the "appropriate way to fix the bug" and it also makes sure that we will never hit this bug again in the future. DS.
It should remain as confirmed for now I think. The next step is to apply the patch to the ubuntu package and use that to create a debdiff. The debdiff should the be attached to this bug and then you subscribe ubuntu- main-sponsors or ubuntu- universe- sponsors as appropriate and request sponsorship (these guys will update it to ubuntu repo and then it will arrive as a normal update).
Details on these two remaining steps is available here: /wiki.ubuntu. com/PackagingGu ide/Recipes/ Debdiff /wiki.ubuntu. com/Sponsorship Process
https:/
https:/
PS. Note that if you can get the patch applied upstream, that's great because it makes it easier to convince ubuntu sponsors that it's the "appropriate way to fix the bug" and it also makes sure that we will never hit this bug again in the future. DS.
Also, for a general overview of bugfixing in ubuntu, check out this page: /wiki.ubuntu. com/MOTU/ TODO/Bugs
https:/
Thanks for working on this patch Antonio, keep up the good work!!