Bug 58491 - weird settlement if connection name includes a colon
Summary: weird settlement if connection name includes a colon
Status: RESOLVED WORKSFORME
Alias: None
Product: kppp
Classification: Applications
Component: general (show other bugs)
Version: 2.1.2
Platform: openSUSE Linux
: NOR normal
Target Milestone: ---
Assignee: Harri Porten
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2003-05-14 20:58 UTC by Andre Klapper
Modified: 2022-12-08 09:04 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Andre Klapper 2003-05-14 20:58:32 UTC
Version:           2.1.2 (using KDE KDE 3.1.1)
Installed from:    SuSE RPMs
OS:          Linux

hi all y'all, in order to reproduce:
in kppp 2.1.2 (on suse 8.1, kde 3.1.1 installed, kppp executed in gnome2.0), i set up a new connection named "colon:colon" (the important is to have a colon [":"] in its name) and its parameters, also with settlement (is this the right translation into english?! - these rule files in order to see how much money you already have to pay for your internet connections - you know what i mean ;-) ).

well, if i try to connect to the internet, i get the error value 16 and i shall debug. if i except this and try to connect for a second time, everything seems to work perfectly.
now when i disconnect and enter the preferences of kppp, on the first page the costs for this connection (after highlighting the connection with a colon in its name) are displayed properly according to the costs taken in the rule file, but if i click on "view logfiles" on the right of this page, i'm getting this data (taken from the csv-export file, don't mind the semicolons):

  colon;14;20:09;01:00;-17s;EUR 1 052 936 512,00;0;1,1 MB;

as you can see, i have been a negative time online, i have to pay a sum which i probably will never earn, and the name of the connection has been cut off directly after the colon in the name (perhaps the colon character is used to seperate tokens in data?!). so i assume that i cannot use a colon in the description/title of my connections. this behaviour was reproduceable.
would be nice if there was implemented something that would parse the entered name of a connection and would hint on this.
sorry i could not patch it myself - i took a look into the source, but i cannot find the right place... :-(

thanks in advance,
cheers,
andre
Comment 1 Andre Klapper 2003-06-18 19:03:51 UTC
hi again, in my opinion, the ":" is used as a seperator character what you can see here:
http://lxr.kde.org/source/kdenetwork/kppp/pppdata.cpp#L824

this seems to be the reason.

andre
Comment 2 George Goldberg 2008-02-18 04:22:38 UTC
Is this bug still present in a recent KDE version, such as 3.5.9 or 4.0.1?
Comment 3 Andre Klapper 2008-02-18 07:59:57 UTC
well, just try and test it yourself, normally bugs don't vanish magically on their own. i don't use KDE anymore nowadays.
Comment 4 Andrew Crouthamel 2018-11-02 04:27:29 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:47:17 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:45 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 Andre Klapper 2022-12-08 09:04:12 UTC
(In reply to Justin Zobel from comment #6)
> 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?

I reported this literally 20 years ago. I wrote here already 15 years ago that I do not know.

This is not a good use of anyone's time, seriously. Neither yours nor mine.