Thanks to everyone who replied - I downloaded the keps file from Amsat and loaded them from local file. I think Gpredict tries to load anything it finds in the local file directory you tell it to use, as long as it's ascii and looks like keplerian elements. Bernard - running GPredict 1.13 on Raspbian Wheezy. Installed via apt-get, so there is also a collection of stock config files in /usr/share/gpredict. For other RPi users, if using the GUI that installs with Raspbian, it has a setting to view the hidden directories, which may make working with your specific configuration a bit easier vs. command line. The Debian dpkg tool can also list files used by gpredict and where they are installed.
Alan - thanks for the reminder - I recall now the discussion following the launch why there were no keps at Celestrack. When I went back to celestrack and searched by NORAD ID, it shows the elements are not available.
I am impressed with the increased computing power in the Pi 2 - running the GUI, Gpredict, and Direwolf (using a USB dongle for sound and another system to display the APRS traffic) runs smoothly.
73 Steve KS1G ks1g@amsat.org