Package: ifupdown
Version: 0.8.19
Severity: normal
Tags: ipv6
Dear Maintainer,
when both IPv4 and IPv6 are statically configured, ifdown first removes
the IPv4 addresses, then puts the interfaces down, and then tries to
remove the IPv6 addresses, which results in the error message
"RTNETLINK
Package: general
Severity: important
Dear Maintainer,
I do not know under which package this bug should be filed or what additional
information is needed to help solve this.
I am running Debian stretch and have configured it to give me text consoles on
boot. I have intel graphics and for Xorg I
Does changing
if [ "$SHLVL" = 1 ]
in ~/.bash_logout to
if [ "$SHLVL" = 2 ]
alter the behaviour?
Yes, in this case I just get the login prompt on the same VT again,
and I can switch back with Ctrl+F1 without any problems.
Source: inspircd
Version: 2.0.23-2
Severity: normal
Dear Maintainer,
the default configuration gives inspircd a --logfile argument
in addition to the section in the config file, which leads
to everything being logged twice.
Package: light-locker
Version: 1.7.0-3
Severity: normal
Dear Maintainer,
I have installed Xfce which includes light-locker. When Xfce blanks the
screen automatically after the configured timespan or if I lock the screen
manually, the screen goes blank and pressing any keys or moving the mouse
I submitted the bug with the wrong subject, sorry for that.
Actually, this had nothing to do with mdadm. The scripts were waiting
for the resume swap partition, which was autodetected by mkinitramfs,
but can not be found anymore because it was encrypted with a random key.
As a workaround, I added the following script to /etc/initramfs-tools/hooks:
#!
Package: initramfs-tools-core
Version: 0.128
Severity: important
Dear Maintainer,
in 0.128 scripts/local was changed to call scripts/local-block/mdadm
repeatedly, resulting in a 20 second delay when booting although my
root filesystem is not on an array and I do not want to uninstall
mdadm.
I use the following temoporary fix for a default instance only setup, which
will persist across reboots:
ln -s /lib/systemd/system/postfix@.service
/etc/systemd/system/postfix.service.wants/postfix@-.service
Actually, this only happens when using
"systemctl restart", not "systemctl start".
Package: openvpn
Version: 2.4.0-6+deb9u1
Severity: normal
Dear Maintainer,
I am running two openvpn instances via config files
/etc/openvpn/server/first.conf
/etc/openvpn/server/second.conf
Starting the second instance via
systemctl start openvpn-server@second
while the first instance is
I have the same problem:
/lib/systemd/system-generators/postfix-instance-generator
does not generate the required links on boot, but it does on reinstall.
Can you show "systemctl status openvpn-server@first.service" and
"systemctl status openvpn-server@second.service", both before and after
the restart?
Actually, the whole directory seems to be removed as it gets a new
inode number. Note that first I have to completely restart "first"
and then
I confirm that I am using "inet_interfaces=..." as well.
Package: firefox-esr
Version: 60.2.2esr-1~deb9u1
Severity: normal
Dear Maintainer,
I have noticed that a binary library libgmpopenh264.so
has been put into
~/.mozilla/firefox/.default/gmp-gmpopenh264/1.6
although media.gmp-gmpopenh264.enabled is false.
I did not install any plugins
15 matches
Mail list logo
