[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#775765: does weird things on suspend via K menu



Package: kde-plasma-desktop
Version: 5:84
Severity: normal

Hi,

this may be related to systemd. Things have gotten so complex since
then that I am at a loss about how to find out which actual component
is to blame. I hope that someone more knowledgeable will be able to
properly triage and reassign this. It may be possible that this is a
duplicate, which I was not able to determine myself for the same
reasons.

When I tell my system to suspend to RAM via K Menu - Leave - Suspend
to RAM, it properly goes to sleep. However, when I wake it up again, I
find myself at a useable, unlocked desktop with a dialog open saying
that authentication is necessary to suspend the system. When I enter
my password in that dialog, the system goes to sleep again.

The ugly bug is: When I tell the system to suspend, it suspends twice
in a row.

The security relevant bug is: When I tell the system to suspend, and
leave the system alone in this state, assuming that my session was
locked before going to sleep, I actually lose my session to anybody
able to hit the power button since my session is not locked any more
before sending the system to sleep.

Greetings
Marc

-- System Information:
Debian Release: 8.0
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.18.1-zgws1 (SMP w/8 CPU cores)
Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages kde-plasma-desktop depends on:
ii  kde-baseapps    4:4.14.2-1
ii  kde-runtime     4:4.14.2-2
ii  kde-workspace   4:4.11.13-2
ii  plasma-desktop  4:4.11.13-2
ii  udisks2         2.1.3-5
ii  upower          0.99.1-3.1

Versions of packages kde-plasma-desktop recommends:
ii  kdm           4:4.11.13-2
ii  xserver-xorg  1:7.7+7

Versions of packages kde-plasma-desktop suggests:
pn  kde-l10n  <none>

-- no debconf information


Reply to: