[General Paranoid Android Discussion] TKruzze:
Unfortunately, as functionality and the new 'Material Design' features of Google's apps grow, the size continues to grow as well. Currently, there is no method to 'shoehorn' a GApps package into a smaller than required system partition.

The GApps packages I'm working on will do exactly what you're looking for. For instance, you'll be able to take the Full Modular package and remove apps you don't want or need and make it install on a device with a very small system partition. However, for now, the only choice is to switch to a smaller GApps package.

Once the new GApps packages are released and everything has slowed down a bit for me, I MAY take a look at this, again, and see if it makes sense to revive it. For now, though, "It's dead, Jim". :)

This is not PA GApps related. You might try asking Google or doing a 'Clean' install to see if the problem is on your end.

As a possible further explanation, we have found that a LOT of older devices with limited RAM (<=1GB), just don't have sufficient RAM available for the addon.d backup script to back up all GApps into RAM and do a proper restore. [MENTION=4544860]osm0sis[/MENTION] has taken the lead on remedying this issue in PA GApps by testing if your device has sufficient space available in /tmp and, if not, to backup to your internal SDCard storage. We thought we had all the bugs worked out, but there appears to be some more testing required. Once this is complete, we'll add it back and it may prevent this type of problem from happening in the future.

What may have happened in your case (just speculating) is that your device did not have sufficient space to back up GApps (using 70-gapps.sh script). Then, when it tried to execute the Chrome backup and restore (78-chrome.sh script), there still wasn't sufficient space available and the backup/restore failed, leaving you with no Chrome. It's also likely that other GApps packages were not properly restored, though there is no way to tell for certain.

My suggestion is if you have a legacy device with <1GB of RAM that you hold off on using the backup/restore functions if (and ONLY IF) you are running the Full or Stock packages. I almost NEVER use this feature myself as I prefer to do what I call a 'Clean/Dirty' flash using the method outlined in FAQ #6. This would only be until we can update the CM addon.d scripts to work as I outlined above.

Once the new packages are released and working smoothly, I'll take a look at adding features. For now, though, no further changes are planned.

Just checked links for Stock GApps on the OP and they worked fine for me.

As suggested, read the OP. Everything should be working as clearly outlined in post #1.

Definitely not a PA GApps issue. Try clearing data/cache for the offending app. If that don't work, a clean install may be in order.

It's an issue on your end. There is no code or scripting that I use, ANYWHERE, that deletes or removes the Google Keyboard. See my not above regarding the backup/restore scripts to see if that might also apply to you.

A Clean install using these GApps should work perfectly. The only issue that can even be remotely traced back to the current GApps packages is installing the Google Keyboard as part of a dirty install (i.e. no data wipe). For some reason, the Google Keyboard does not like to be installed on anything other than a clean install (Factory Reset, System wipe). However, even that issue is on Google's side of things.