Am 08.10.2011 18:20, schrieb Christoph Reiter: > Package: network-manager-gnome > Version: 0.9.0-2 > Severity: normal > > I waited for the VPN server to let me in again and did a > > watch -e 'nmcli con up uuid 609bd441-de2d-4654-b798-2154cd3a5882; [ $? -ne 0 > ]' > > which tried to connect about 800 times (every 2 seconds). After some time it > started failing because there was no password/username given. The VPN > preferences dialog showed no password/username anymore. Setting it again had > no > effect, reopening.. empty again. > > Restarting network-manager didn't help. > > ..xsession-errors showed many: > > ** (nm-applet:7212): WARNING **: Failed to create pipe for communicating with > child process (Too many open files) > ** (nm-applet:7212): WARNING **: Failed to create pipe for communicating with > child process (Too many open files) > ** (nm-applet:7212): WARNING **: Failed to create pipe for communicating with > child process (Too many open files) > ** (nm-applet:7212): WARNING **: Failed to create pipe for communicating with > child process (Too many open files) > ** (nm-applet:7212): WARNING **: Failed to create pipe for communicating with > child process (Too many open files) > ** (nm-applet:7212): WARNING **: Failed to create pipe for communicating with > child process (Too many open files) > > Restarting the machine made it work again. >
Are you sure this is a network-manager-gnome problem? It looks like your max number of open files was exhausted which actually led to nm fail to connect. -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth?
signature.asc
Description: OpenPGP digital signature
