To reproduce read the manpage for ubiquity and in the second sentence for description I read It is normally invoked from a desktop icon, and presents a "wizard"-style graphical user interface. ubiquity must be run as root, and will escalate privileges for itself using gksudo, kdesu, kdesudo, or sudo as appropriate. Then since lxqt-sudo is a new way to run GUI programs as root for lxqt in the archives since 16.04 and planned to be shipped with lubuntu 16.10 if ubiquity would need changes to use this. I ended up coming to the conclusion this information is outdated after a long search through the ubiquity code base that this one mention seemed to be left in even though ubiquity uses policykit now so future lubuntu isos need only to have policykit working which could be nicer but if this was in the manpage I could have improved ubuntu in other ways than looking through ubiquity source to try to see if lxqt-sudo could be added. This could be a simple fix but other parts of the manpage might need to be updated as well.
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: ubiquity 2.21.47
ProcVersionSignature: Ubuntu 4.4.0-9.24-generic 4.4.3
Uname: Linux 4.4.0-9-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.20-0ubuntu3
Architecture: amd64
CurrentDesktop: LXDE
Date: Fri Mar 4 14:34:57 2016
InstallationDate: Installed on 2015-06-02 (276 days ago)
InstallationMedia: Lubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150602)
SourcePackage: ubiquity
UpgradeStatus: Upgraded to xenial on 2015-12-27 (68 days ago)
Thank you for taking the time to report this bug and helping to make Ubuntu better. We are sorry that we do not always have the capacity to look at all reported bugs in a timely manner. There have been many changes in Ubuntu since that time you reported the bug and your problem may have been fixed with some of the updates. It would help us a lot if you could test it on a currently supported Ubuntu version. If you test it and it is still an issue, kindly upload the updated logs by running only once:
apport-collect 1553401
and any other logs that are relevant for this particular issue.