hannah-foo2zjs is marked for autoremoval from testing

hannah-foo2zjs 1:2 is marked for autoremoval from testing on 2018-01-25 It is affected by these RC bugs: 885545: hannah-foo2zjs: Don't depend on gksu

utf8-migration-tool is marked for autoremoval from testing

utf8-migration-tool 0.5.9 is marked for autoremoval from testing on 2018-01-25 It is affected by these RC bugs: 885492: utf8-migration-tool: Depends on unmaintained pygtk

reinteract is marked for autoremoval from testing

reinteract 0.5.0-6 is marked for autoremoval from testing on 2018-01-25 It is affected by these RC bugs: 885477: reinteract: Depends on unmaintained pygtk

ntfs-config is marked for autoremoval from testing

ntfs-config 1.0.1-11 is marked for autoremoval from testing on 2018-01-25 It is affected by these RC bugs: 885510: ntfs-config: Depends on unmaintained pygtk

xmms2tray is marked for autoremoval from testing

xmms2tray 0.5.1-3 is marked for autoremoval from testing on 2018-01-25 It is affected by these RC bugs: 885495: xmms2tray: Depends on unmaintained pygtk

Bug#610380: pm-utils: pm-suspend-hybrid fails to resume after power loss

The behavior you describe as "the uswsusp backend" is the only behavior described in the man page for pm-suspend-hybrid. It doesn't mention an alternate behavior at all, let alone that the alternate behavior is the *default*. As of version 1.4.1-17 it's still true that pm-utils doesn't suggest or

Bug#886302: pm-utils: Black screen when resuming from pm-suspend-hybrid

Package: pm-utils Version: 1.4.1-17 Severity: normal When I run `pm-suspend-hybrid` the screen goes black and the system suspends. When I wake it up, the screen does not go "un-black". The system is definitely awake, because I can ssh into it, but I can't go back to what I was doing because o