Package: qcontrol
Version: 0.4.2+svn-r40-3
Severity: wishlist
Dear Maintainer,
The current fanspeed control script causes the fan to jump back and forth
between two speed quite easily, at least on my system (419P). I've modified
the base temp() function to implement a hysteresis loop to prevent t
Package: nslcd
Version: 0.8.10-4
Followup-For: Bug #696445
I must add that this does not happen on all machines, on this second machine
the upgrade did not clobber the configuration file. The only difference I can
think of as relevant is that the earlier machine has been running testing
since its
Package: dspam
Version: 3.10.1+dfsg-5
Severity: normal
Dear Maintainer,
After migrating my dspam database to a new PostgreSQL server, I'm seeing the
following errors in PG's log (edited for readability):
ERROR: invalid byte sequence for encoding "UTF8": 0xae:
INSERT INTO dspam_signature_data (
Package: systemd
Version: 44-2
Followup-For: Bug #668798
As another point of information, I do use libpam-systemd (well, I do have it
installed) but that makes no difference:
Setting up openssh-server (1:6.0p1-1) ...
Installing new version of config file /etc/pam.d/sshd ...
[] Restarting ssh
Package: linux-2.6
Version: 3.2.15-1
Severity: normal
Dear Maintainer,
After updating the kernel, I no longer have a picture on my TV. This box acts
as HTPC, the TV is the only display device I have. I do have picture in BIOS
and Grub, but the TV switches to standby mode as soon as the kernel tak
Package: selinux-policy-default
Version: 2:2.20110726-1
Severity: normal
The current ldap module uses /etc/rc.d/.. for the path to the slapd init
script, which causes slapd to linger in initrc_exec_t in permissive mode. I
suspect it will not start at all in enforcing mode.
Solved locally by addin
Package: linux-2.6
Version: 2.6.32-38
Severity: normal
I'm seeing multiple swapper allocation failures (with backtrace) since I
increased the MTU on one of the network interfaces:
[36290.311168] swapper: page allocation failure. order:2, mode:0x4020
[36290.311233] [] (unwind_backtrace+0x0/0xdc) f
Package: gdisk
Version: 0.7.2-1
Severity: normal
It appears that the new gdisk release confuses itself when it needs to write a
protective MBR:
===
# gdisk /dev/sde
GPT fdisk (gdisk) version 0.7.2
Partition table scan:
MBR: not present
BSD: not present
APM: not present
GPT: present
Fo
Package: nfs-kernel-server
Version: 1:1.2.2-2
Severity: normal
Will this be fixed in time for the Squeeze release? For as far as I can see,
the current situation breaks all (bind) mounts within the NFSv4 pseudo-
filesystem. I would think that that is a fairly common scenario.
Or alternatively, if
9 matches
Mail list logo