qtparted is left running after cancelling Ubiquity in Kubuntu

Bug #44346 reported by Krzysztof Lichota
6
Affects Status Importance Assigned to Milestone
qtparted (Ubuntu)
Won't Fix
High
Kubuntu Bugs

Bug Description

Kubuntu version: after flight 7 (installed on disk)
ubiquity-frontend-kde version: 0.99.77

When Ubiquity is cancelled during "custom partitioning" step, qtparted is left running, eating most of CPU.

Revision history for this message
Colin Watson (cjwatson) wrote :

Jonathan, this is a bug in qtparted; in installer mode, it needs to be careful to exit when its stdin goes away. gparted gets this right, so you can compare with that.

Revision history for this message
Krzysztof Lichota (krzysiek-launchpad-ubuntu-com) wrote :

Hm, I don't think it is a major bug. In normal case user will install Kubuntu or in case he decides to cancel, he will reboot the computer if it consumes CPU.

Revision history for this message
Colin Watson (cjwatson) wrote :

I think it's major. All installer subprocesses must make sure that they go away as soon as possible if their stdin disappears, otherwise there is a risk of bugs similar to bug 40464.

Revision history for this message
Krzysztof Lichota (krzysiek-launchpad-ubuntu-com) wrote :

Fair enough, nobody wants data corruption :)

Frode M. Døving (frode)
Changed in qtparted:
assignee: nobody → kubuntu-team
Revision history for this message
Paul Dufresne (paulduf) wrote :

All people here seems to indirectly agree the bug exist.

Changed in qtparted:
status: Unconfirmed → Confirmed
Revision history for this message
Colin Watson (cjwatson) wrote :

This is no longer an issue, as the installer no longer uses gparted or qtparted, but implements its own partitioner which doesn't suffer from this problem.

Changed in qtparted:
status: Confirmed → Won't Fix
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.