Package: molly-guard
Version: 0.5.1-1
Severity: important

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Today when I hit CTRL+ALT+BACKSPACE on my laptop (due to an Xorg crash)
the system started shutting down services but then at some (quite late,
I believe) point spewed out this:

/etc/molly-guard/run.d/30-query-hostname: 48: 
/etc/molly-guard/run.d/30-query-hostname: tty: not found
W: aborting reboot due to 30-query-hostname exiting with code 127.

...and asked for password to a rescue shell.

I found no other (polite) way out than typing in root password: Had it
been a non-admin user there would have been no way out but to pull the
plug, I believe, risking data loss.  Hence the severity (and arguably it
should be even more severe).

My system has separate root and /usr partitions, and I suspect the issue
might be molly-guard being invoked after /usr partition was unmounted.


 - Jonas


- -- System Information:
Debian Release: 8.0
  APT prefers unstable
  APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 3.17.0-trunk-amd64 (SMP w/2 CPU cores)
Locale: LANG=da_DK.UTF-8, LC_CTYPE=da_DK.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages molly-guard depends on:
ii  procps  2:3.3.9-8

molly-guard recommends no packages.

molly-guard suggests no packages.

- -- no debconf information

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iQF8BAEBCgBmBQJUe3kXXxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w
ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQ3NjQ4ODQwMTIyRTJDNTBFQzUxRDQwRTI0
RUMxQjcyMjM3NEY5QkQ2AAoJEE7BtyI3T5vWmBsIAIw3ooAhC+ruJgh4HS+x73I/
ayHm4U+k7kqRZus6BfmzdBtj9+Bl9b0rNkavmgNzOGL7bys1lxy6mAnHhd+C/Oe1
2+pwk5P3Aaill3VbOOCVCe1ONZ+7GsZFGN+N7KPIOI90kw7NuaJtkkxdMMKerbDQ
QMsJ3eff+Bi14mHWA3C1vf9pWHelFeZKQPIYbVj5brLA1Yjsxdcyo3uyxGon0f6M
dZ+3OgR8NhujBylXmddOaILDyEmQrqdS0FqFsq6aCCZk1xOsKuyoK39S435vth/q
fIQLhY6i5qQyxw8E2bxZIDsSflPZToTHd8kPvIkn120FK4XGbF9XtogtoW3OIBU=
=s+nG
-----END PGP SIGNATURE-----


-- 
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]

Reply via email to