Bug 317711

Summary:	kopete did not connect to any account
Product:	[Unmaintained] kopete	Reporter:	Evgeny <evdanil>
Component:	general	Assignee:	Kopete Developers <kopete-bugs-null>
Status:	RESOLVED WORKSFORME
Severity:	normal
Priority:	NOR
Version First Reported In:	1.4.0
Target Milestone:	---
Platform:	Ubuntu
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

Description Evgeny 2013-04-02 06:14:40 UTC

when kopete started, it trys to open a kwallet which keeps all my passwords for accounts, if I did not type in password for kwallet in first minute or two, and type it in in 5 minutes - kopete did not connect, maybe the problem not in kopete itself, but only kopete the application where I can reproduce it always with ease.

Reproducible: Always

Steps to Reproduce:
1. create common kwallet for several kopete accounts
2. after kopete startup and kwallet dialog appearance - do not input any password for 2-5 min
3. type in password - kopete will not connect to any of the accounts, kopete restart did not help, looks like kwallet is inaccessible
Actual Results:  
kopete did not connect

Expected Results:  
kopete to use kwallet and to be able to connect after kwallet password will be typed in

Comment 1 Evgeny 2013-04-02 06:21:02 UTC

btw. it is a long stand bug, i could remember that i was facing this issue for at least a couple of years. I thought it maybe my setup (I have a huge contact list with a lot of contacts), but on the last week I so exactly the same behaviour on the account of my spouse, and she has very simple account - icq, jabber with a fee fellows in a contact list.

Comment 2 Andrew Crouthamel 2018-11-10 03:18:58 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:11:28 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-02 02:04:33 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-17 05:15:34 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-02-01 05:05:03 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!