Bug 108561 - kppp sending AT command from "dialing speed" which some modems don't accept. Not possible to turn dialing speed off
Summary: kppp sending AT command from "dialing speed" which some modems don't accept. ...
Status: RESOLVED WORKSFORME
Alias: None
Product: kppp
Classification: Unmaintained
Component: general (other bugs)
Version First Reported In: 2.3.1
Platform: Unlisted Binaries Linux
: NOR normal
Target Milestone: ---
Assignee: Harri Porten
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-07-04 22:44 UTC by Kim Højgaard-Hansen
Modified: 2023-01-07 05:23 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 Kim Højgaard-Hansen 2005-07-04 22:44:21 UTC
Version:           2.3.1 (using KDE KDE 3.4.1)
Installed from:    Unspecified Linux
OS:                Linux

The setting under 

configure -> modems -> modem -> modem commands

called "dialing speed (sec/100)" seems to send at ATS11=(number) command to the modem. Some modems doesn't recognize this command, and errors out the connection. It doesn't seem to be possible to disable this.
Comment 1 Harri Porten 2005-07-04 22:55:49 UTC
One workaround would be to remove the corresponding AT command from the
modem settings. If I recall correctly kppp will the ignore the setting
completely.
Comment 2 Kim Højgaard-Hansen 2005-07-05 20:24:55 UTC
it's not possible to remove... the setting can be put to 0 - 255 (sec/100) with a slidebar, but no matter what sends the command... like ATS11=0 (for dialing speed 0)
Comment 3 Harri Porten 2005-07-05 20:57:48 UTC
Maybe I'm confusing this setting with the one for the sound volume. Will
have to check next time I'm running kppp.
Comment 4 Andrew Crouthamel 2018-11-02 04:22:20 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-16 02:46:32 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 6 Justin Zobel 2022-12-08 00:00:41 UTC
Thank you for reporting this issue in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the issue with a recent software version?

If you can reproduce the issue, please change the status to "REPORTED" when replying. Thank you!
Comment 7 Bug Janitor Service 2022-12-23 05:20:37 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-07 05:23:11 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!