Bug 103919 - kppp: examine modem does not examine the selected modem
Summary: kppp: examine modem does not examine the selected modem
Status: RESOLVED WORKSFORME
Alias: None
Product: kppp
Classification: Unmaintained
Component: general (other bugs)
Version First Reported In: 2.2.0
Platform: Gentoo Packages Linux
: NOR normal
Target Milestone: ---
Assignee: Harri Porten
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-04-14 23:32 UTC by esigra
Modified: 2018-11-02 22:39 UTC (History)
2 users (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 esigra 2005-04-14 23:32:31 UTC
Version:           2.2.0 (using KDE KDE 3.3.2)
Installed from:    Gentoo Packages
OS:                Linux

1. Start kppp as a new user (no previous kppp settings).
2. Press the configure button.
3. Choose the modem tab.
4. Press new...
5. Choose the device tab. Now the modem dropdown box shows the invalid device /dev/modem, which does not even exist! Change this to the correct device (in my case /dev/ttySL0).
6. Switch to the modem tab.
7. Press examine the modem. It fails with the message "can not open the modem". After a little while a message box pops up that says something like "the modem request timed out".
8. Close that box with OK.

My guess is that kppp fails to use the selected device. It tries to use the nonexisting /dev/modem and fails eventhough the user chose something else. To confirm this I did this:
9. Switch to the device tab.
10. Type "A" into the modem name textbox.
11. Press OK.
12. Select "A" in the list and press edit.
13. Choose the modem tab.
14. Press examine the modem. Now the modem is successfully examined.

(This bug was not so easy to discover when I was configuring a newly installed system. For a long time I thought there was something wrong with the kernel configuration and investigated that a lot. Then I installed wvdial and discovered that there was nothing wrong with the system configuration. It was entirely kppp's fault.)
Comment 1 Andrew Crouthamel 2018-11-02 04:16:22 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 2 esigra 2018-11-02 06:25:30 UTC
I can not test it because I no longer use that computer or a modem. My current computer does not have /dev/ttySL0.
Comment 3 Andrew Crouthamel 2018-11-02 22:39:12 UTC
Thanks for the update!