Bug 164725

Summary: KPPP freezes on set-up
Product: [Applications] kppp Reporter: Marc <m.chattle>
Component: generalAssignee: Harri Porten <porten>
Status: RESOLVED WORKSFORME    
Severity: normal CC: andrew.crouthamel, dufresnep, jetrull
Priority: NOR    
Version: unspecified   
Target Milestone: ---   
Platform: Fedora RPMs   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description Marc 2008-06-23 10:11:40 UTC
Version:           kdenetwork-4.0.5-3.fc9.i386.rpm (using KDE 4.0.5)
Installed from:    Fedora RPMs
Compiler:          RedHat rpm Fedora 9 KPPP used via Gnome desktop
OS:                Linux

Please note this was reported on Bugzilla RedHat (452083), and they asked for it to be reported also here.  Thank you.

Description of problem:

Open KPPP to set-up a modem connection via Gnome desktop.  KPPP window opens,
but freezes on manual set-up when the new account is selected.  However, if you
select the modem tab first, you can enter modem settings and then the new
account settings can be entered, but this isn't the way it normally works.  Even
when settings are eventually entered into KPPP as described above, the modem
won't connect with KPPP (I think the error code 16 comes up, but will need to
check).

Entering settings and connecting to the ISP do work with System-Config-Network
via Gnome, though.

Version-Release number of selected component (if applicable):

Didn't work with the original component when F9 came out, and doesn't work with
the current update (10 June 2008): kdenetwork-4.0.5-3.fc9.i386.rpm  

How reproducible:

Every time, even when a reboot is tried.

Steps to Reproduce:
1. Open KPPP and try to enter modem account and set-up settings.
2. KPPP freezes when the new account manual set-up is selected.
3. Managed to enter settings if the modem settings are entered first, then the
new account settings, but modem won't connect.
  
Actual results:

Not able to connect with KPPP even when settings are eventually able to be entered.

Expected results:

Expect to be able to enter settings, and connect to ISP.

Additional info:

System-Config-Network works and the modem connects.


Comment #1 From Steven M. Parrish 	on 2008-06-20 17:11 EST 	[reply] 	 

Checked upstream and could not find matching bug report.  Please report upstream
at http://bugs.kde.org and add upstream info to this report.  We will monitor
upstream for resolution.  Thanks
Comment 1 Jonathan Thomas 2009-07-27 16:55:51 UTC
We received a similar report downstream at Kubuntu at https://launchpad.net/bugs/278408
Comment 2 Jeff Trull 2010-03-25 21:51:26 UTC
I also observe this problem, now in KDE 4.4 (via Kubuntu Lucid).  Basically creating new accounts fails (hangs), although it's possible to configure the modem.  After a few tries I managed to get it to work manually, but 3 times out of four it simply hung on the "create new account" step.

Incorporating kppp's functionality into the network manager would be a perfectly good solution IMO.
Comment 3 Paul Dufresne 2010-11-03 02:21:30 UTC
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.
Comment 4 Andrew Crouthamel 2018-11-05 03:19:27 UTC
Dear Bug Submitter,

This bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? I am setting the status to NEEDSINFO pending your response, please change the Status back to REPORTED when you respond.

Thank you for helping us make KDE software even better for everyone!
Comment 5 Andrew Crouthamel 2018-11-13 19:07:32 UTC
Email from Marc:

Hello Andrew, Thank you for this bolt from the blue. As I recall, the bug I referred to was fixed at the time, and I recall noting this, so am not sure why this has resurfaced. I stopped using Fedora some time ago as it was too buggy and had too many large quantity updates that drained my metered download capacity. I don't have my bugzilla login details any more, so am unable to disable this report. Best wishes, Marc.