[Touch-packages] [Bug 1837202] [NEW] leading tabs in here-documents are always stripped even when they should not

2019-07-19 Thread Detlev Zundel
Public bug reported: Here documents from the command line with tabs are not handled correctly. Here is a transcript showing the problem - there is a tab in front of "This is indented" in the file: dzu@zarniwoop:~$ cat tab-test #!/bin/bash cat < This is unindented > This is indented > STOP This

[Touch-packages] [Bug 1662137] Re: 16.04 recovery shell works only for two minutes

2017-02-06 Thread Detlev Zundel
** Attachment added: "Output of "systemd-analyze blame" for the session after the rescue session" https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1662137/+attachment/4813979/+files/systemd-analyze-blame -- You received this bug notification because you are a member of Ubuntu Touch

[Touch-packages] [Bug 1662137] Re: 16.04 recovery shell works only for two minutes

2017-02-06 Thread Detlev Zundel
** Attachment added: "Journal for rescue session" https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1662137/+attachment/4813978/+files/journalctl-b-1 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu.

[Touch-packages] [Bug 1662137] [NEW] 16.04 recovery shell works only for two minutes

2017-02-06 Thread Detlev Zundel
Public bug reported: Selecting "Rescue" shell from the "Advanced options" menu in grub enters the "friendly-recovery" service and allows to drop into a root shell. After ~120 seconds, systemd sees a timeout and starts another "friendly- recovery" whiptail process. This and the running shell now

[Touch-packages] [Bug 1661851] Re: cannot enter rescue or emergency state from running system

2017-02-04 Thread Detlev Zundel
One more info - after making the journal persistent, this is the end of the journal for the session ending with the hang: Feb 04 16:22:00 harry systemd[1]: Stopped ACPI Events Check. Feb 04 16:22:00 harry systemd[1]: Stopped target Sockets. Feb 04 16:22:00 harry systemd[1]: Closed UUID

[Touch-packages] [Bug 1661851] [NEW] cannot enter rescue or emergency state from running system

2017-02-04 Thread Detlev Zundel
Public bug reported: Typing "systemctl rescue" in a running system brings down the system and prompts Welcome to rescue mode! After logging in, type "journalctl -xb" to view system logs, "systemctl reboot" to reboot, "systemctl default" or ^D to boot into default mode. Press Enter for