Symptom
You're running a Fedora 19 OS. Initially AT&T Global Network Client (agnclient) was working fine. Once the kernel got updated, the agnclient UI couldn't be started. Specifically, bumblebee-nvidia driver is installed on the system. And if you run /opt/agns/bin/agnclient from a terminal, libEGL.so.1 is complained missing.
Solution
Configure ldconfig with bumblebee version of libEGL.so.1.
[tony@yftpi ~]$ echo "/usr/lib/nvidia-bumblebee" | sudo tee /etc/ld.so.conf.d/bumblebee-nvidia-x86_64.conf
[sudo] password for tony:
/usr/lib/nvidia-bumblebee
[tony@yftpi ~]$
[tony@yftpi ~]$ sudo ldconfig
Story
Ever since I upgraded to Fedora 19, it's been observed that AT&T Global Network Client (agnclient) failed to start every time the kernel package got updated. This is something I access corporate network with from outside of the office, so it's kind of critical for me.
Last time I ran into this awkward situation I didn't suffer for long, it got fixed somehow by the update of a bunch of mesa-* packages, and I therefore wasn't paying much attention. Last night, however, I wasn't this lucky. It went down, and there weren't any updates available for any of the mesa packages whatsoever.
I happened to have a virtual machine (VM) that's running Fedora 19 as well, which proved to be a good test bed. I installed agnclient on it and it worked like a charm, even with the latest kernel, surprisingly. I managed to get the binary file name (/opt/agns/bin/agnclient) of the agnclient UI from the VM, and tried to run it from terminal on my laptop. This is a better approach than from UI in terms of debugging, since whatever the program outputs will be printed on the terminal. You can then get some clue from these error messages. In this case, it complained about not being able to locate libEGL.so.1.
I compared the outputs of locate libEGL.so.1 from the VM and my laptop, it seems the bumblebee-nvidia driver had deleted libEGL.so.1 from /usr/lib and provided its own version in /usr/lib/nvidia-bumblebee. This explains why everything is OK in the VM, where the bumblebee driver isn't installed. Every time mesa-libEGL.i686 is updated, the library is put in /usr/lib. And every time there is a kernel update, bumblebee re-configures itself and deletes the library in /usr/lib. The rest of the story seemed rather straightforward. I added /etc/ld.so.conf.d/bumblebee-nvidia-x86_64.conf so that ldconfig could recognize things in /usr/lib/nvidia-bumblebee. After that agnclient is back on.
