Bug 305507

Summary:	KDE Wallet is expected after startup, but error message is shown
Product:	[Unmaintained] telepathy	Reporter:	andreaswuest
Component:	contactlist	Assignee:	Telepathy Bugs <kde-telepathy-bugs>
Status:	RESOLVED NOT A BUG
Severity:	normal	CC:	kde
Priority:	NOR
Version:	0.4.0
Target Milestone:	Future
Platform:	Ubuntu
OS:	Linux
Latest Commit:		Version Fixed In:	0.5.0
Sentry Crash Report:
Attachments:	screenshots of the error dialogs

Description andreaswuest 2012-08-20 18:53:27 UTC

Hi,
i am experiencing the following problem, which seems to happen only if you follow the steps below

Reproducible: Always

Steps to Reproduce:
1. start new kde session after booting (coul
2. open KDE IM Contacts application (do not start any other application that uses the 
KDE Wallet) as first and only application.
3. Change state from Offline to Online in the KDE IM Contacts application.



Actual Results:  
4. After that i expect the KDE Wallet Service dialog, because all the IM Account information is stored in the wallet. However i am also getting an Instant Messaging
Dialog saying: 
"There was a problem while trying to connect myuser@googlemail.com - The connection was canceled on your request."
I never canceled anything and i did not expect the Instant messaging dialog to show up (see screenshot). 

Expected Results:  
I only expect the KDE Wallet Service dialog which asks for the wallet password. 


I have no idea why the instant messaging dialog shows up because it does not make sense here.

Comment 1 andreaswuest 2012-08-20 18:54:59 UTC

if i quit the KDE IM Contacts app. and start it again, it behaves differently. it looks like it is keeping a state somewhere even after quitting.

Comment 2 andreaswuest 2012-08-20 19:00:47 UTC

Created attachment 73333 [details]
screenshots of the error dialogs

Comment 3 David Edmundson 2012-08-20 19:48:36 UTC

Thanks for taking the time to make a detailed report, especially the clear steps and screenshot.

This was an issue, and as such all the wallet code was rewritten for 0.5 (release imminent). This bug is now fixed.

Please re-open if this still occurs after 0.5.0 

Thanks again