Package: sysvinit-core
Version: 2.88dsf-59.10
Severity: normal
Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate ***
* What led up to the situation? Starting gnome-alsamixer gave a blank screen.
* What exactly did you do (or not do) that was effective (or
ineffective)? Tried starting with systemd.
* What was the outcome of this action? Sound worked.
* What outcome did you expect instead?
*** End of the template - remove these template lines ***
-- System Information:
Debian Release: buster/sid
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 4.15.0-3-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_IN.UTF-8, LC_CTYPE=en_IN.UTF-8 (charmap=UTF-8),
LANGUAGE=en_IN:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)
LSM: AppArmor: enabled
Versions of packages sysvinit-core depends on:
ii debconf [debconf-2.0] 1.5.66
ii debianutils 4.8.4
ii initscripts 2.88dsf-59.10
ii libc6 2.27-3
ii libselinux1 2.7-2+b2
ii libsepol1 2.7-1
ii sysv-rc 2.88dsf-59.10
ii sysvinit-utils 2.88dsf-59.10
sysvinit-core recommends no packages.
Versions of packages sysvinit-core suggests:
pn bootlogd <none>
-- debconf information excluded
