Bug 333969

Summary:	addNickname: Nickname "<foo>" has not been added as it is already in the nickname list.
Product:	[Applications] konversation	Reporter:	Toralf Förster <toralf.foerster>
Component:	logging	Assignee:	Konversation Developers <konversation-devel>
Status:	RESOLVED FIXED
Severity:	normal	CC:	hein, zilla
Priority:	NOR
Version:	1.5
Target Milestone:	---
Platform:	Gentoo Packages
OS:	Linux
Latest Commit:	https://commits.kde.org/konversation/2a281c144ced97e5859a70cbf1503c33f4b6183b	Version Fixed In:
Sentry Crash Report:

Description Toralf Förster 2014-04-27 20:32:23 UTC

B/c I deactivated all debug message via kdebugdialog I do assume, these are (unwanted) error messages - found in .xsession-erros :

konversation(7850) Channel::addNickname: Nickname  "Hello71_"  has not been added as it is already in the nickname list. 

SSL Observatory: Retrying a submission...
X Error: BadWindow (invalid Window parameter) 3
  Major opcode: 20 (X_GetProperty)
  Resource id:  0x3800150
konversation(7850) Channel::addNickname: Nickname  "dabbott"  has not been added as it is already in the nickname list. 

konversation(7850) Channel::addNickname: Nickname  "dabbott"  has not been added as it is already in the nickname list. 

konversation(7850) Channel::addNickname: Nickname  "dabbott"  has not been added as it is already in the nickname list. 

SSL Observatory: Cert submission failure 0: 
SSL Observatory: Planning to retry submission...
konversation(7850) Channel::addNickname: Nickname  "NeddySeagoon"  has not been added as it is already in the nickname list. 

konversation(7850) Channel::addNickname: Nickname  "NeddySeagoon"  has not been added as it is already in the nickname list.

konversation(7850) Channel::addNickname: Nickname  "NeddySeagoon"  has not been added as it is already in the nickname list.


Reproducible: Always

Comment 1 Eike Hein 2014-04-28 05:45:14 UTC

Thanks - these indeed intentionally bypass the debug messaging system since this is something that ought not to occur (though it's fairly harmless when it does). Could you tell us what network this happen on?

Comment 2 Toralf Förster 2014-04-28 16:59:15 UTC

It was the IRC server of freenode and some of the #gentoo channels.
Locally I do use a wifi connection FWIW.

Comment 3 Jonathan Wakely 2017-10-19 11:00:17 UTC

If you need to know the network for the message to be useful, maybe the network should be included in the message! Otherwise it's just noise in the logs, and there's nothing the user can do to avoid the errors (I don't control the Freenode IRC servers!)

Comment 4 argonel 2017-11-10 09:09:24 UTC

Git commit 2a281c144ced97e5859a70cbf1503c33f4b6183b by Eli MacKenzie.
Committed on 09/11/2017 at 23:49.
Pushed by argonel into branch '1.7'.

Silence unwanted debug output
Related: bug 385945

M  +2    -2    src/irc/channel.cpp

https://commits.kde.org/konversation/2a281c144ced97e5859a70cbf1503c33f4b6183b