Bug 306548

Summary:	Bookmark manager issue with double hashes "##chan"
Product:	[Applications] konversation	Reporter:	Xavier Hourcade <public.oss>
Component:	general	Assignee:	Konversation Developers <konversation-devel>
Status:	RESOLVED WORKSFORME
Severity:	normal	CC:	hein, public.oss
Priority:	NOR
Version:	1.5-rc1
Target Milestone:	---
Platform:	unspecified
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description Xavier Hourcade 2012-09-10 14:04:26 UTC

Bookmark manager issue with double hashes "##chan"
Guess it relates to the part from kdelibs, but specific to IRC usage ?

If one makes a bookmark from a joined channel "##chan",, or directly makes a new entry for "##chan" in the bookmark manager, then
- it is stored as eg. irc://server/##chan
- but it is *displayed* as eg. irc://server/#%23chan

Then, if one goes back to edit the URI, eg. just to change irc to ircs :
- it is *stored* as eg. ircs://server/#%23chan

Which is wrong, and make the bookmark unusable : clicking it, Konversation would try to open a chan with such literal name i.e. \#\%23chan (the whole "#" character topic is one of the RFC pitfalls, IMMO the RFC is too liberal, but oh well).

Workaround : within the bookmark manager, one needs to edit the entry again by overwriting "blindly" both hashes and typing them again :
- it is *stored* as eg. irc://server/##chan again

Confusing!

Comment 1 Xavier Hourcade 2012-09-10 14:08:15 UTC

See also section "2.5.1. Channel Names" at https://tools.ietf.org/html/draft-butcher-irc-url-04

Comment 2 Andrew Crouthamel 2018-11-10 03:12:55 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 3 Andrew Crouthamel 2018-11-20 04:04:09 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 4 Justin Zobel 2023-01-01 04:20:06 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 5 Bug Janitor Service 2023-01-16 05:13:20 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 6 Bug Janitor Service 2023-01-31 05:05:34 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!