Bug 193711 - do not present error when unable to write password
Summary: do not present error when unable to write password
Status: RESOLVED WORKSFORME
Alias: None
Product: kppp
Classification: Unmaintained
Component: general (other bugs)
Version First Reported In: unspecified
Platform: Debian testing Linux
: NOR normal
Target Milestone: ---
Assignee: Harri Porten
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-05-23 02:11 UTC by Thadeu Lima de Souza Cascardo
Modified: 2023-01-08 05:15 UTC (History)
0 users

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


Attachments
fix the bug (934 bytes, patch)
2009-05-23 02:29 UTC, Thadeu Lima de Souza Cascardo
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Thadeu Lima de Souza Cascardo 2009-05-23 02:11:57 UTC
Version:           SVN (using KDE 4.2.2)
OS:                Linux
Installed from:    Debian testing/unstable Packages

When unable to write the password to chap.secrets or pap.secrets, kppp proceeds into calling kppp, instead of presenting an error to the user. This happens, for example, when an installation is not suid by choice of the distributor.
Comment 1 Thadeu Lima de Souza Cascardo 2009-05-23 02:29:44 UTC
Created attachment 33934 [details]
fix the bug

This will fix this bug.
Comment 2 Thadeu Lima de Souza Cascardo 2009-05-23 02:31:05 UTC
One argument against the proposed bug is that, in the case the user has written his/her passwort to the files using any other methods, kppp will present an error instead of trying to connect anyway. Perhaps an option not to set the password should be given to the user.
Comment 3 Andrew Crouthamel 2018-11-02 23:06:17 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 05:25:19 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 Justin Zobel 2022-12-09 22:13:04 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 6 Bug Janitor Service 2022-12-24 05:22:36 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 7 Bug Janitor Service 2023-01-08 05:15:53 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!