This occurs since gtk3.
While not a real big deal can cause user confusion & possibly an error.
Test case:
boot to a live cd > install on any machine with several existing partitions
choose install, from partitioner choices > something else
If the partitioning window is scrollable go down to the bottom & do something (eg. choose a partition to remove or free space to partition
As soon as the action is complete the window resets to top, chosen action likely will not be seen in the window
What should happen:
Window should remain at scrolled location
ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: ubiquity (not installed)
ProcVersionSignature: Ubuntu 3.12.0-7.15-generic 3.12.4
Uname: Linux 3.12.0-7-generic x86_64
ApportVersion: 2.12.7-0ubuntu2
Architecture: amd64
CurrentDesktop: Unity
Date: Wed Dec 18 10:33:23 2013
InstallCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.12.0-7-generic root=UUID=491c9582-7465-4087-a527-707a1f4d9e2e ro intel_pstate=enable
SourcePackage: ubiquity
UpgradeStatus: No upgrade log present (probably fresh install)
---
ApportVersion: 2.20.9-0ubuntu2
Architecture: amd64
CasperVersion: 1.392
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 18.04
InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi file=/cdrom/preseed/ubuntu.seed boot=casper quiet splash ---
LiveMediaBuild: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180403)
Package: ubiquity 18.04.4
PackageArchitecture: amd64
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=<set>
LANG=C.UTF-8
SHELL=/bin/bash
ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
Tags: bionic ubiquity-18.04.4 ubuntu
Uname: Linux 4.15.0-13-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
_MarkForUpload: True
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 https:/
and any other logs that are relevant for this particular issue.