This issue isn't specific to my installer. There are reports on other places about it.
By the way, the installer spawns a single process and is pretty barebones all around, I doubt it has anything do do with it.
Frank (or anyone else able to reproduce), could you please try to reproduce this in Debian?
I know the change was upstream, but I've had multiple reports from Ubuntu users and none from Debian, that's why I'm assuming this isn't an issue in Debian although I don't understand why.
Thanks for your reply,
This issue isn't specific to my installer. There are reports on other places about it.
By the way, the installer spawns a single process and is pretty barebones all around, I doubt it has anything do do with it.
Frank (or anyone else able to reproduce), could you please try to reproduce this in Debian?
I know the change was upstream, but I've had multiple reports from Ubuntu users and none from Debian, that's why I'm assuming this isn't an issue in Debian although I don't understand why.
Regards