Bug 226809

Summary:	Kopete doesn't save current status at exit
Product:	[Unmaintained] kopete	Reporter:	Ivan Andrianov <payableondeath90>
Component:	general	Assignee:	Kopete Developers <kopete-bugs-null>
Status:	RESOLVED UNMAINTAINED
Severity:	wishlist	CC:	pablo
Priority:	NOR
Version First Reported In:	unspecified
Target Milestone:	---
Platform:	openSUSE
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

Description Ivan Andrianov 2010-02-14 14:04:02 UTC

Version:            (using KDE 4.3.5)
OS:                Linux
Installed from:    openSUSE RPMs

I think Kopete must save my status at exit and restore it at startup as a lot of IM clients do.

Comment 1 pablo 2012-02-05 02:10:39 UTC

My Use Case for this feature is the following.

I have a desktop and a laptop.  I use the laptop whenever I do business travel.  I `rsync' my laptop from my desktop.  If I have my laptop out on a trip and my desktop reboots (e.g. power failure), kopete will restart `online'  In order to avoid this problem, I have to set up kopete to always start `offline'

I'd rather `kopete' start with the last status set.  That'll take care of everything.  :)  As a matter of fact, if kopete starts with the last status saved, I don't think there's a reason to have the option to start kopete with a particular status.  

Thank you!

Comment 2 Christoph Cullmann 2024-09-18 18:27:17 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.