Comment 15 for bug 278408

I see this bug too, on freshly installed Fedora 14.

But for me, the first time I click on "new account", it hangs... so I go to a root console, type ps aux|grep ppp, and kill -9 each process I find (I think there is 4).

After that, rerunning kppp works always works for me.

I had seen it on Fedora 14 Beta, so this time I had tried to apply the trick of not using root as it seems they have done on:
https://bugzilla.redhat.com/show_bug.cgi?id=452083

That is, with:
[paul@Arcturus ~]$ groups
paul dialout
[paul@Arcturus ~]$ ls -lh /usr/bin/kppp
lrwxrwxrwx. 1 root root 13 Nov 2 18:27 /usr/bin/kppp -> consolehelper
[paul@Arcturus ~]$ ls -lh /usr/bin/consolehelper
-rwxr-xr-x. 1 bin dialout 6.0K Sep 14 11:34 /usr/bin/consolehelper
[paul@Arcturus ~]$
 My first execution of $kppp &
System asks for root password, so it execute as root anyway...
The following messages showed up:
[paul@Arcturus ~]$ kppp &
[1] 2770
[paul@Arcturus ~]$ Connecting to deprecated signal QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString)
QMetaObject::invokeMethod: No such method KUniqueApplication::loadCommandLineOptionsForNewInstance()
kbuildsycoca4 running...
"KConfigIni: In file /tmp/kde-root/kconf_updateCT2808.tmp, line 1: " Invalid entry (missing '=')
QMetaObject::invokeMethod: No such method KUniqueApplication::loadCommandLineOptionsForNewInstance()
klauncher(2796)/kio (KLauncher): SlavePool: No communication with slave.

And the second times (after the kill -9 of kppp process):
Second run:
[paul@Arcturus ~]$ kppp &
[1] 3122
[paul@Arcturus ~]$ QMetaObject::invokeMethod: No such method KUniqueApplication::loadCommandLineOptionsForNewInstance()

At this point, the dialog window "Create New Account" is there.