Bug 231329

Summary:	Make use of screensaver activation as auto-away trigger optional
Product:	[Applications] konversation	Reporter:	xor <xor>
Component:	general	Assignee:	Konversation Developers <konversation-devel>
Status:	CONFIRMED ---
Severity:	normal	CC:	hein, kde, quazgar, xor
Priority:	NOR
Version:	1.5-rc1
Target Milestone:	---
Platform:	Ubuntu
OS:	Linux
Latest Commit:		Version Fixed In:

Description xor 2010-03-19 17:25:14 UTC

Version:           1.2 (using KDE 4.3.2)
OS:                Linux
Installed from:    Ubuntu Packages

I've configured my identity to be auto-away after 15 minutes (and change nickname to "xor|afk" then), however the following happens:

[16:56] *** You are now known as xor|afk.
[16:56] *** You are now known as xor.
[16:57] *** You are now known as xor|afk.
[16:59] *** You are now known as xor.
[17:01] *** You are now known as xor|afk.
[17:03] *** You are now known as xor.
[17:06] *** You are now known as xor|afk.
[17:06] *** You are now known as xor.
[17:10] *** You are now known as xor|afk.
[17:10] *** You are now known as xor.

Comment 1 Eike Hein 2010-03-19 17:31:38 UTC

Is it possible you're not in agreement with Konversation about what constitutes inactivity? Mouse movement, for example, is activity.

Comment 2 xor 2010-03-19 18:07:50 UTC

The problem is NOT the away => not away changes BUT that it sets away after less than the configured 15 minutes.

Comment 3 Eike Hein 2010-03-19 18:11:30 UTC

Right.

Comment 4 xor 2010-03-19 23:43:33 UTC

I just had luck and saw what triggers the auto-away probably: The activation of the screensaver... This should be separately configurable.

Comment 5 quazgar 2012-08-15 19:44:43 UTC

(In reply to comment #4)
> I just had luck and saw what triggers the auto-away probably: The activation
> of the screensaver... This should be separately configurable.

I can confirm this screensaver-away behaviour here, konversation 1.4 on KDE 4.8.3

Comment 6 Myriam Schweingruber 2013-04-14 09:12:24 UTC

Confirmed by comment #5