Public bug reported:
While tracking down a problem related to upstart, I decided to check the
syntax of all my upstart init files. I wrote this simple script:
for a in /etc/init/*; do init-checkconf $a; done 21 | grep invalid
This script said that a number of files had syntax errors. When the
For example, here are two consecutive runs of the script showing
different results:
root@ladastra:/etc/init# for a in /etc/init/*; do init-checkconf $a; done 21
| grep invalid
ERROR: File /etc/init/alsa-state.conf: syntax invalid:
ERROR: File /etc/init/alsa-store.conf: syntax invalid:
ERROR:
Actually, it seems there isn't anything in particular about being in a
script that causes init-checkconf to return random results. If I repeat
the same command a number of times the results vary:
root@ladastra:/oldroot/home/drewes# init-checkconf /etc/init/tty5.conf
File
Public bug reported:
Booting very new laptop hardware (ASUS Zenbook UX431FA) from 18.04 usb
install (also 18.10, also 19.04 daily) leads to black screen. Adding
"nomodeset" to kernel boot parameter gives 800x600 video only and
permits installing OS to disk. Applying updates and hardware
** Description changed:
Booting very new laptop hardware (ASUS Zenbook UX431FA) from 18.04 usb
install (also 18.10, also 19.04 daily) leads to black screen. Adding
"nomodeset" to kernel boot parameter gives 800x600 video only and
permits installing OS to disk. Applying updates and
5 matches
Mail list logo
