[konversation] [Bug 385945] New: Useless error logging: Nickname "..." has not been added as it is already in the nickname list

[Jonathan Wakely]

https://bugs.kde.org/show_bug.cgi?id=385945

            Bug ID: 385945
           Summary: Useless error logging: Nickname "..." has not been
                    added as it is already in the nickname list
           Product: konversation
           Version: 1.7.2
          Platform: Other
                OS: Linux
            Status: UNCONFIRMED
          Severity: normal
          Priority: NOR
         Component: general
          Assignee: konversation-devel at kde.org
          Reporter: zilla at kayari.org
  Target Milestone: ---

Several times a day my system logs show errors like:

Oct 13 13:50:42 knitphad.home konversation[3283]: Nickname  "someuser"  has not
been added as it is already in the nickname list.

This seems to happen on all networks I'm connected to (freenode, oftc, and an
internal work one).

Sometimes it's even for my own users:

Oct 13 12:53:58 knitphad.home konversation[3283]: Nickname  "jwakely"  has not
been added as it is already in the nickname list.
Oct 13 12:53:59 knitphad.home konversation[3283]: Nickname  "jwakely"  has not
been added as it is already in the nickname list.
Oct 13 12:54:03 knitphad.home konversation[3283]: Nickname  "redi"  has not
been added as it is already in the nickname list.
Oct 13 12:54:03 knitphad.home konversation[3283]: Nickname  "ChanServ"  has not
been added as it is already in the nickname list.
Oct 13 12:54:11 knitphad.home konversation[3283]: Nickname  "jwakely"  has not
been added as it is already in the nickname list.

There is nothing I can do to prevent these, so it's just useless noise in my
logs. Why does it need to be logged, without an option to disable it?

(See also Bug 333969 but that's been in NEEDINFO for years, despite the info
being provided).

-- 
You are receiving this mail because:
You are the assignee for the bug.