Package: systemd-cron
Version: 1.15.18-1
Severity: normal
Tags: security
X-Debbugs-Cc: robert.siemer-report...@backsla.sh, Debian Security Team
Crontabs, especially in /var/spool/cron are not readable to all users.
Translated command lines in unit files in
/run/systemd/generator on the other h
Package: libnss-systemd
Version: 250.3-1
Severity: normal
X-Debbugs-Cc: robert.siemer-report...@backsla.sh
/var/lib/dpkg/info/libnss-systemd\:i386.postinst does not add
`systemd` on the shadow and gshadow lines of /etc/nsswitch.conf,
only passwd and group.
All four dbs should have `systemd` added
g Tracking System
> Contact ow...@bugs.debian.org with problems
>
>
>
> -- Forwarded message --
> From: James McCoy
> To: Robert Siemer ,
> 1004118-d...@bugs.debian.org
> Cc:
> Bcc:
> Date: Fri, 21 Jan 2022 08:37:52 -0500
> Subject: Re: Bug#1004118: E1187: Fai
Package: vim-tiny
Version: 2:8.2.3995-1
Severity: normal
X-Debbugs-Cc: robert.siemer-report...@backsla.sh
vim-tiny should come with defaults.vim, I believe. Which way I’m not sure,
but it seems vim-common does not deliver it and vim-tiny does not depend
on vim-runtime, which has it.
-- Package
Without libunbound it works. – Problem solved? :-o
On Wed, Jan 19, 2022 at 12:41 PM David Bürgin wrote:
> Robert Siemer:
> > Opendkim does not run.
> >
> > # opendkim -f
> > [1642532480] libunbound[837:0] error: nettle random(yarrow) cannot
> initialize, g
Package: opendkim
Version: 2.11.0~beta2-6
Severity: important
X-Debbugs-Cc: robert.siemer-report...@backsla.sh
Opendkim does not run.
# opendkim -f
[1642532480] libunbound[837:0] error: nettle random(yarrow) cannot initialize,
getentropy failed: Function not implemented
opendkim: can't configure
I got the same problem, that is, I had to manually run on the
initramfs-shell:
lvm lvchange -aly /dev/vg0/lvol0
but the patch didn’t fix the problem. – Coincidently I used this
constant rebooting to switch from lilo to grub; and that did the trick!
I reversed the patch (and reran update-init
wrote:
> On Wed, 2007-06-20 at 20:08 +0200, Robert Siemer wrote:
> > I'm pleased to announce a reliable and fast test scenario:
> >
> > $ xset dpms 10 20 30
> > [wait 10 seconds]
> > [screen goes blank (DPMS gets active)]
> > $ xset -dpms
> > [no DP
I'm pleased to announce a reliable and fast test scenario:
$ xset dpms 10 20 30
[wait 10 seconds]
[screen goes blank (DPMS gets active)]
$ xset -dpms
[no DPMS kicks in, not even after 10 seconds]
$ xset +dpms
[wait 10 seconds]
What I now expect is that DPMS suspends (or actually "standbys") the
On Sun, Jun 03, 2007 at 10:44:15PM +0200, Brice Goglin wrote:
> Hi,
>
> About 6 months ago, you reported a bug to the Debian BTS regarding DPMS
> not kicking automatically as expected. Did you reproduce this problem
> recently? With latest xserver-xorg-core in unstable? Xserver 1.3 has
> been ther
Package: xserver-xorg-video-ati
Version: 1:6.6.3-2
Severity: normal
$ xset q says:
...
DPMS (Energy Star):
Standby: 480Suspend: 600Off: 3000
DPMS is Enabled
Monitor is On
but DPMS does not switch the monitor to anything else but "On."
$ xset dpms force standby
$ xset dpms force su
Package: apr
Version: 1.2.7
Severity: important
in debian/rules I had to comment out that line:
ifeq ($(DEB_BUILD_ARCH),i386)
# CONFFLAGS=apr_lock_method=USE_PROC_PTHREAD_SERIALIZE
CONFFLAGS=
else
...after some hours of investigation! I have no idea what this should be
usefull fo
Package: stun
Version: 0.96.dfsg-1
Severity: important
The /etc/init.d/stun script tries to change user with --user. It should
be --chuid on start. --user is for stopping or something... it has not
effect on startup here!
-- System Information:
Debian Release: 3.1
Architecture: i386 (i686)
Kernel
13 matches
Mail list logo
