Bug 262471

Summary:	Kppp don't reset volume accounting
Product:	[Unmaintained] kppp	Reporter:	Sandro kensan <kensan>
Component:	general	Assignee:	Harri Porten <porten>
Status:	RESOLVED WORKSFORME
Severity:	normal
Priority:	NOR
Version First Reported In:	unspecified
Target Milestone:	---
Platform:	PiSi Linux
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

Description Sandro kensan 2011-01-08 00:47:15 UTC

Version:           unspecified (using KDE 4.4.5) 
OS:                Linux

I have set the volume accounting and not set the phone cost accounting. When I reset Volume accounting the total don't change and is not reset. If i then close and open Kppp the Total is not reset.

The workaround is: close Kppp, edit the file ~/.kde4/share/config/kppprc and reset the TotalBytes=0, save and start kppp.


Reproducible: Always

Steps to Reproduce:
Set volume accounting (byte in and out)
don't set phone cost account
browser the web and spend traffic
when Volume accounting is not zero try to reset Volume accounting
press reset Volume e phone cost accounting
press OK

Actual Results:  
The Volume accounting don't change and is not reset.
If i exit from kppp the file ~/.kde4/share/config/kppprc has TotalBytes not zero

Expected Results:  
The Volume accounting reset to zero
when i exit from kppp i expect ~/.kde4/share/config/kppprc has TotalBytes=0

$ kppp -v
Qt: 4.6.3
KDE Development Platform: 4.4.5 (KDE 4.4.5)
KPPP: 2.4.0

Gnu/Linux Pardus 2009.2

Comment 1 Andrew Crouthamel 2018-11-05 03:20:51 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 Andrew Crouthamel 2018-11-17 05:00:54 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? This bug will be moved back to REPORTED Status for manual review later, which may take a while. If you are able to, please lend us a hand.

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

Comment 3 Justin Zobel 2022-12-18 08:18:09 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 4 Bug Janitor Service 2023-01-02 05:26:52 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 5 Bug Janitor Service 2023-01-17 05:18:10 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!