Package: telepathy-mission-control-5 Version: 1:5.16.1-1 Severity: normal Setting the status to Offline and then locking the screen (under KDE with kde-telepathy, but I guess this is a MC bug) or wiating for the auto-away timeout sets the status to away.
This means when I leave my workstation, setting IM to offline in the hope that the resource will, in fact, be offline, is jeopardised by Telepathy going back onlien in order to fulfill its auto-away configuration. Auto-away thus should not be triggered when the manually selected status is anything else than Available! -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.14-1-amd64 (SMP w/2 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages telepathy-mission-control-5 depends on: ii dconf-gsettings-backend [gsettings-backend] 0.20.0-2 ii libc6 2.18-6 ii libdbus-1-3 1.8.2-1 ii libdbus-glib-1-2 0.102-1 ii libglib2.0-0 2.40.0-3 ii libmission-control-plugins0 1:5.16.1-1 ii libnm-glib4 0.9.8.10-2 ii libtelepathy-glib0 0.24.0-1 ii libupower-glib1 0.9.23-2+b2 telepathy-mission-control-5 recommends no packages. Versions of packages telepathy-mission-control-5 suggests: ii telepathy-haze 0.8.0-1 -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
