Bug 115256

Summary:	improve nickserv and server password usability
Product:	[Unmaintained] kopete	Reporter:	S. Burmeister <sven.burmeister>
Component:	IRC Plugin	Assignee:	Kopete Developers <kopete-bugs-null>
Status:	RESOLVED UNMAINTAINED
Severity:	normal	CC:	silfreed-kdebugs
Priority:	NOR
Version First Reported In:	0.40.0
Target Milestone:	---
Platform:	openSUSE
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

Description S. Burmeister 2005-10-28 14:41:27 UTC

Version:            (using KDE KDE 3.4.3)
Installed from:    SuSE RPMs
OS:                Linux

When I start kopete I am prompted for the kwallet password. The IRC-accounts however go online already without me having entered the password for kwallet.

I have entered my username and password for freenode in kopete's settings, yet when going online, I am not automatically identified, which I thought would be the purpose of giving kopete my username and password for that server.

Expected behaviour would be to identify the user on the server, if a username and password are available.

Comment 1 George M. Harkin 2005-11-07 19:24:34 UTC

I have verified this bug, exact same issue

Comment 2 Douglas E. Warner 2007-07-11 15:02:22 UTC

I'm currently also experiencing this bug with Kopete 0.12.5 (KDE 3.5.7 on FC-6).

My workaround is currently to go to the account preferences when I first start Kopete and uncheck & recheck the "save password" checkbox.  When I connect to the IRC server I am then automatically identified; but otherwise I am not.

Comment 3 Douglas E. Warner 2007-07-11 15:02:58 UTC

*** This bug has been confirmed by popular vote. ***

Comment 4 Will Stephenson 2007-11-24 16:58:56 UTC

The problem is that there are 2 auth mechanisms in IRC - a server password, and a 'services' (NickServ) password.  Freenode further simplifies/confuses things by passing the server password through to NickServ.  But you need to be able to specify both to be able to connect to any IRC server. We need to make this more intuitive in future.

Comment 5 Justin Zobel 2021-03-09 22:41:28 UTC

Thank you for the bug report.

As this report hasn't seen any changes in 5 years or more, we ask if you can please confirm that the issue still persists.

If this bug is no longer persisting or relevant please change the status to resolved.

Comment 6 Christoph Cullmann 2024-09-18 18:27:54 UTC

Dear user, unfortunately Kopete is no longer maintained.

Please migrate to another solution, e.g. for Jabber a possibility is Kaidan, for Matrix a candidate is NeoChat.