Your message dated Wed, 30 Mar 2016 19:33:19 +0200
with message-id <[email protected]>
and subject line Re: Bug#819500: general: Debian 8.3 CLI reboot using "init 6"
shows username & password in plain text.
has caused the Debian Bug report #819500,
regarding general: Debian 8.3 CLI reboot using "init 6" shows username &
password in plain text.
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
819500: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=819500
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: general
Severity: normal
Dear Maintainer,
* CLI command "shutdown -r now" USUALLY does not work, since systemd replaced
sysvinit in Debian 8 "jessie".
Posted problem on http://www.linuxquestions.org/questions/debian-26/used-to-
shutdown-reboot-from-cli-but-since-systemd-replaced-init-shutdown-cmnd-
broke-4175575779/ got advice to try commmand "init 6". When I try it, I USUALLY
arrive - eventually - at a console login that reports errors - but amongst the
confusing information are the username & password IN PLAIN TEXT! I also had a
single occurrence of my root password split over two lines also in plain text!
Basically the reboot & shutdown commands from the CLI are REALLY buggy!
Another respondent to my query on LQ.org suggested using: "systemctl reboot"
this resulted eventually in poweroff/shutdown.
The MOST annoying part of this bug is its variability: OCCASSIONALLY the
commands work ok! But USUALLY not! Also SOMETIMES on booting-up again after an
unwanted forced-shutdown, the machine powers off without warning USUALLY before
the graphical Login appears & ONCE after an apparently successful login?
-- System Information:
Debian Release: 8.3
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_NZ.UTF-8, LC_CTYPE=en_NZ.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
--- End Message ---
--- Begin Message ---
On Wed, Mar 30, 2016 at 06:57:39AM +1300, beagleburt wrote:
> Package: general
> Severity: normal
>
> Dear Maintainer,
>
> * CLI command "shutdown -r now" USUALLY does not work, since systemd replaced
> sysvinit in Debian 8 "jessie".
> Posted problem on http://www.linuxquestions.org/questions/debian-26/used-to-
> shutdown-reboot-from-cli-but-since-systemd-replaced-init-shutdown-cmnd-
> broke-4175575779/ got advice to try commmand "init 6". When I try it, I
> USUALLY
> arrive - eventually - at a console login that reports errors - but amongst the
> confusing information are the username & password IN PLAIN TEXT! I also had a
> single occurrence of my root password split over two lines also in plain text!
> Basically the reboot & shutdown commands from the CLI are REALLY buggy!
>
> Another respondent to my query on LQ.org suggested using: "systemctl reboot"
> this resulted eventually in poweroff/shutdown.
>
> The MOST annoying part of this bug is its variability: OCCASSIONALLY the
> commands work ok! But USUALLY not! Also SOMETIMES on booting-up again after an
> unwanted forced-shutdown, the machine powers off without warning USUALLY
> before
> the graphical Login appears & ONCE after an apparently successful login?
Hi.
If the machine powers off without warning, it is quite likely that you
have a hardware problem.
Hardware problems are often random and unpredictable, but they are not
software bugs, so they do not usually have a place in the Debian bug system.
I would start by checking memory with the memtest86+ package. After
installing the package, you have to reboot and choose the new GRUB
menu entry that it's added automatically.
Also, I would try to install Debian in a different computer and
configure it identically. If you experience similar problems, then
yes, it could be a bug. But if the problem vanishes, you would have a
good confirmation that your hardware is faulty (random power offs
are already a sign for that).
If you need more help, please ask in debian-user mailing list.
Thanks.
--- End Message ---
_______________________________________________
Pkg-systemd-maintainers mailing list
[email protected]
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
