Bug 157913 - kppp or kde4 unusable - keeps looping thru modem strings
Summary: kppp or kde4 unusable - keeps looping thru modem strings
Status: RESOLVED WORKSFORME
Alias: None
Product: kppp
Classification: Unmaintained
Component: general (other bugs)
Version First Reported In: unspecified
Platform: unspecified Linux
: NOR normal
Target Milestone: ---
Assignee: Harri Porten
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-02-16 09:40 UTC by Slobodan Simic
Modified: 2023-01-12 05:16 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed/Implemented In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Slobodan Simic 2008-02-16 09:40:13 UTC
Version:           2.4.0 (using 4.0.1 (KDE 4.0.1), Kubuntu packages)
Compiler:          gcc
OS:                Linux (x86_64) release 2.6.22-14-generic

I have installed kde4 aside with my perfectly working kde3.
But kde's 4 kppp apps is practicaly unusable because it keeps going thru modem strings and interupts dialing.
It goes ATZ like modem init string, then ATM1L2 to set volume and when it cames to dial with ATDTxxxxxx number
I get OK in log window and then start over with ATZ... ATM1L2... ATDTxxxx and again and again. Luckily I have kppp from kde3 so I can connect to internet but if someone want to use plain kde4 I think connecting to internet with dialup connection will be a nightmare to him.
Comment 1 Slobodan Simic 2008-02-17 16:56:28 UTC
I found that problem is that in kppp for kde4 "modem timeout" and "pppd timeout" cannot be set. Or to be specific, kppp keeps fallback these settings to 1 sec, making connecting impossible. Even tough I make kppprc config file non writable and manually edit modem and pppd timeout settings to normal values.
Comment 2 John Rosich 2008-02-19 18:23:23 UTC
Same issue under Fedora 8 and 9 using KDE 4. KDE 3.5.8 works as it's supposed to under both versions. Identical i386 architecture, fully updated O/S's in all cases. Nothing in error or message logs regarding the problem.
Comment 3 Andrew Crouthamel 2018-11-02 04:21:53 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 4 Andrew Crouthamel 2018-11-16 02:41:39 UTC
Dear Bug Submitter,

This is a reminder that 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?

Thank you for helping us make KDE software even better for everyone!
Comment 5 Slobodan Simic 2018-11-16 11:42:10 UTC
Not used KPPP for a long time.
Tried again some vpn dial-up connections and same behavior occurred.
Noticed that it's pppd problem rather than kppp and solved problem by adding user to "dip" group because pppd is root:dip ownership
Comment 6 Justin Zobel 2022-12-13 02:53:49 UTC
Thank you for reporting this issue in KDE software. As it was reported on an older version, can we please ask you to see if you cazn reproduce the issue with a more recent software version?  
  
If you can confirm this issue still exists in a recent version, please change the version field and the status to "REPORTED" when replying. Thank you!
Comment 7 Bug Janitor Service 2022-12-28 05:23:22 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 8 Bug Janitor Service 2023-01-12 05:16:21 UTC
This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!