Bug 349969

Summary:	'Automatically return on activity' cancels explicit 'away' status.
Product:	[Applications] konversation	Reporter:	Francis Herne <mail>
Component:	general	Assignee:	argonel <argonel>
Status:	ASSIGNED ---
Severity:	normal	CC:	justin.zobel
Priority:	NOR
Version:	1.6
Target Milestone:	---
Platform:	Arch Linux
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description Francis Herne 2015-07-06 17:25:57 UTC

With the settings 'Automatic away' and 'Automatically return on activity' enabled:

After being inactive for [n] minutes (the auto-away time), poking the window will cancel the user's 'away' status.
This is expected if that status was caused by the inactivity timeout, but is undesirable when the user was explicitly marked as 'away' before becoming inactive.

Example of unexpected/unwanted behaviour:
Set 'away' status (e.g. "/away working"). Leave Konversation in background for 15 minutes while working. Briefly focus and click on Konversation window, e.g. when moving it. The 'away' status is now cancelled, despite having set it explicitly and not cancelled it.

Automatic return should only apply when the away status was caused by inactivity, and not silently override the user's actions.

Reproducible: Always

Steps to Reproduce:
1. Enable 'Automatic away' and 'Automatically return on activity'
2. Mark self as away (/away or global-away).
3. Leave window in background for 10mins (or other auto-away timeout).
4. Click on window.

Actual Results:  
Automatic return is triggered, and cancels 'away' status.

Expected Results:  
Should still be marked away, because that status wasn't due to inactivity.

Comment 1 Justin Zobel 2020-12-02 06:25:15 UTC

Thank you for the report, Francis.

As it has been a while since this was reported, can you please test and confirm if this issue is still occurring or if this bug report can be marked as resolved.

I have set the bug status to "needsinfo" pending your response, please change back to "reported" or "resolved" when you respond, thank you.

Comment 2 Bug Janitor Service 2020-12-17 04:34:02 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 3 argonel 2020-12-17 06:48:00 UTC

I'll investigate.