Package: dmidecode
Version: 3.0-2
Severity: important
Tags: patch
dmidecode seems to be failing on recent uefi firmware, probably related
to SMBIOS 3.0 rollout by vendors. I just upgraded an Asrock Rack
EP2C612D16-2L2T Xeon E5 v3/v4 board to firmware version 2.10 to get
Broadwell-EP CPU
Package: libvirt-bin
Version: 0.9.12-11
Severity: important
Tags: ipv6
libvirt-bin fails to start KVM vm's if IPv4 is not available on the host.
Happens
with libvirt-versions in unstable and the one in experimental (1.0.3-1) - Spice
and VNC video.
The cause seems to be the standard resolver not
On 31. aug. 2012 05:12, Thomas Goirand wrote:
Hi Andre,
Could you explain a bit more what needs to be done in the ip6tables, in
the init script? Should I just create a MiniUPnP chain in the forward
table as well?
I'm ok to write that part, though I need directions.
Only rule that is needed
On 31. aug. 2012 04:32, Thomas Goirand wrote:
On 08/31/2012 05:14 AM, Andre Tomt wrote:
Package: miniupnpd
Version: 1.7-4
Not sure what to make of severity. Its pretty much a requirement for IPv6.
As for most of your bug submission, these are request for new features,
so this falls under
Package: miniupnpd
Version: 1.7-4
In an IPv6 environment the relevant ip6tables rule and chain is not
added, making the IPv6 support broken unless you add the rules yourself.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact
Package: miniupnpd
Version: 1.7-4
It seems newer versions of miniupnpd recommends using the interface name
instead of IP address for listening_ip or -a. Then it will just get
the addresses itself from the interface. This autodetection makes
configuration cleaner and simpler, aids renumbering
I've been thinking a bit about this problem. I think the EXTIP snippet
that causes this problem to begin with is basicly not even needed.
Actually detrimental even.
There are basicly two use cases we need to cover;
1) WAN IP is a single dynamic or static address. This is like 99% of cases.
On 23. aug. 2012 13:49, Thomas Goirand wrote:
On 08/23/2012 06:13 AM, Andre Tomt wrote:
Package: miniupnpd
Version: 1.7-3
Disclaimer: I installed this in ubuntu, but AFAICT there is nothing
Ubuntu specific with this bug.
Initscript magic fails with multiple IP's on WAN interface
On 23. aug. 2012 14:04, Thomas Goirand wrote:
On 08/23/2012 06:08 AM, Andre Tomt wrote:
The build seems to be missing IPv6 support.
Hi,
I don't mind adding support for IPv6, but I don't want to have any
trouble / security problems with it. The init script and everything else
should be able
Package: miniupnpd
Version: 1.7-3
Disclaimer: I installed this in ubuntu, but AFAICT there is nothing
Ubuntu specific with this bug.
Initscript magic fails with multiple IP's on WAN interface.
192.168.99.1 and xx.xx.xx.2 (censored) is set on WAN interface
+ /sbin/iptables -t nat -A
Package: miniupnpd
Version: 1.7-3
Disclaimer: I installed this in ubuntu, but AFAICT there is nothing
Ubuntu specific with this bug.
The build seems to be missing IPv6 support.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble?
Package: miniupnpd
Version: 1.7-3
Disclaimer: I installed this in ubuntu, but AFAICT there is nothing
Ubuntu specific with this bug.
The build seems to be missing IGDv2 support.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble?
Package: miniupnpd
Version: 1.7-3
Disclaimer: I installed this in ubuntu, but AFAICT there is nothing
Ubuntu specific with this bug.
It seems when debconf asks what interface to bind to, it really means
the WAN interface.
--
To UNSUBSCRIBE, email to
Package: miniupnpd
Version: 1.7-3
Severity: wishlist
Disclaimer: I installed this in ubuntu, but AFAICT there is nothing
Ubuntu specific with this bug.
When integrating with other firewall solutions the initscript based
setup of the netfilter chains is often counter-productive. It'd be nice
ulogd 2.0.0 just got released upstream and 1.x is EOL'd. So if any
security issues crops up.. ..and wheezy is freezing ;)
As far as I can tell 2.x is also needed for IPv6 logging/accounting.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe.
Package: php5-fpm
Version: 5.4.4~rc2-1
Severity: important
The php5 FPM SAPI does not reliably start up for me after 5.4.4~rc2-1 migrated
to testing and landed on my system.
It will randomly lock up during startup, just after it has started its worker
processes and should be exiting.
This makes
Package: busybox
Version: 1:1.19.2-1
Severity: critical
Justification: breaks the whole system
It seems $PATH handling has stopped working, breaking initramfs-tools making
the system unbootable.
initramfs-tools dumps to a recovery console during boot as the shell cannot
find its binaries.
Same problem on a Core i7 S1366 platform (Asus P6T Deluxe V2, Intel i7 920,
12GB RAM).
Is there any x86 platform where this multiboot image is actually working
properly?
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact
Is 5.2 still in the pipeline for squeeze? I'd really love to get #552047
squashed on Debian proper, either by moving to 5.2+ or adding the
provided patch.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact
Package: munin
Version: 1.4.1-1
Severity: important
If /etc/munin/munin-conf.d/ directory is empty, munin-cron spews warnings to
cron, which ends
up in my mailbox. This started after upgrading to 1.4.x
Running for example touch /etc/munin/munin-conf.d/local to create a bogus file
stops the
The emtpy munin-conf.d directory was the default configuration after
upgrading here, which is my justification for the bug beeing of severity
important.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact
Package: sdparm
Version: 1.02-1
Severity: wishlist
Version 1.04 available upstream.
-- System Information:
Debian Release: squeeze/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.32-rc6 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8,
Package: openssh-server
Version: 1:5.1p1-5
Severity: important
Tags: patch
When using ForceCommand internal-sftp and you're trying to pass extra
parameters, SFTP will fail
due to a bug in the special casing of internal-sftp in the ForceCommand config
directive processing.
This is
Slight brainfart in the control message upgrading bug to RC; I of course
meant remote DoS ;-)
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
IMQ have been replaced by the mainline supported ifb device + mirred
tc actions. Other than that IMQ have serious stability and design
issues, for example beeing racy with SMP and certain network setups.
mirred and the ifb device does not involve changes to iptables.
--
To UNSUBSCRIBE, email
Seems like there are other features too missing from the current version
in at least etch. Action mirred for example, seems not to work with
2.6.17 kernel.
gw:~# tc filter add dev eth0 parent : protocol ip prio 10 u32 match
u32 0 0 flowid 1:2 action mirred egress mirror dev ifb0
Action 3
Nevermind me. It turned out the documentation from iproute I used was
buggy, fixed documentation was in the git tree and using that worked
just fine.
Sorry about the noise.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
I'd like to see it as a flavour. This is also how pretty much every
other noteworthy distribution is doing it (a -bigsmp or -pae flavour, so
there is some precedence.)
You'd be surprised on how many PAE needing servers there are in
enterprises. Having no officially supported kernel images for
I'm also seeing new odd behaviour after upgrading libnss-ldap.
As long as nscd is not running, slapd start blocks for about 5-10
minutes. If I start nscd before slapd it works, but I might end up with
a invalid cache for some period of time if other lookups have happened
and failed due to
Package: php-interbase
Severity: wishlist
PHP 5.1.4 is now in testing and unstable. Time to update! :-)
And why isn't it just beeing built directly from the php sources itself?
-- System Information:
Debian Release: testing/unstable
APT prefers testing
APT policy: (500, 'testing')
Hi
If you can provide me with /var/local/rrd/mce_sensors.rrd it would be
great. I need to do some testing on this with current versions of
rrdtool, libfreetype etc, so far I've been unable to reproduce.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble?
Package: firebird2-server-common
Version: 1.5.3.4870-7
Followup-For: Bug #240287
As it turns out, the not a system group bug has resurfaced. I'm not sure
which version did it, but it is a problem in 1.5.3.4870-7. A fresh install
resulted in this config:
db-fb1:/# id firebird
uid=100(firebird)
I'm seeing similar segfaults on amd64 in perl, only when libnss-ldap is
loaded. This seems to have gone haywire after amd64 archive got rebuilt
for inclusion as official arch for me. I notice there have been no
uploads of openldap2 since before the big rebuild.
This is breaking things like
Ok, one additional data point, it only happens with ldap specified for
the shadow: entry in nsswitch.conf. passwd: and group: works fine.
Eg:
passwd: compat
group: compat
shadow: compat ldap
- Segfault.
passwd: compat ldap
group: compat ldap
shadow:
Package: libpam-ldap
Version: 180-1
Severity: minor
The bundled pam.d examples are outdated, and does not apply to either sarge,
etch or sid.
Some common-* examples would be very nice.
-- System Information:
Debian Release: testing/unstable
APT prefers testing
APT policy: (500, 'testing')
This bug is still present in sarge, and is very very annoying.
Segfaulting in one of the most used function would be RC in my book, but
then again I have not studied the Debian RC criteria all that well :)
Its one of those things I'd want fixed in 3.1r2.
--
To UNSUBSCRIBE, email to [EMAIL
Package: php5
Severity: wishlist
As separating the php4-interbase source out of the php source manually has
shown to be a very silly and ineffient affair, isn't it time to just build
php5-interbase directly from the php5 source?
The php4-interbase package have always been way behind the version
Package: apache2
Version: 2.0.53-5
Severity: wishlist
conf.d is brilliant for local configuration, so you can have local
changes, without changing the package provided conffiles, eliminating
another maintaince overhead on upgrades.
Problem is, that it is included almost in the beginning, so you
Package: munin
Version: 1.2.0-1
Severity: wishlist
the new [ disk mysql network ..] links in the root page doesn't work too
well in most browsers, as they tend to jump to the anchor *before* the
images have been rendered, leaving you hanging in some arbitrary location
on the graph page.
making
Package: libdevmapper1.01
Version: 2:1.01.00-1
Severity: grave
Justification: renders package unusable
# ls -l /etc/rc2.d/S20libdevmapper1.01
lrwxrwxrwx 1 root root 26 Mar 7 20:59 /etc/rc2.d/S20libdevmapper1.01 -
../init.d/libdevmapper1.01
this used to reside in rcS.d, not rc2.d. I'm pretty
Package: libshout
Severity: wishlist
Your faithfull new-upstream-version nagger here :)
libshout was released as 2.1 a few weeks ago.
-- System Information:
Debian Release: 3.1
APT prefers testing
APT policy: (1000, 'testing'), (500, 'unstable')
Architecture: i386 (i686)
Kernel: Linux
This looks like a temporary file of some sort. Does it even belong in
/etc? Looks a bit iffy to me.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Package: postgresql
Version: 7.4.7-2
Severity: normal
I got this in my mail after a upgrade today; notice the printout of
the root directory contents.. I guess the error is pretty obvious :-)
The postmaster did not start after postgresql was installed:
Stopping PostgreSQL database server:
Package: phpmyadmin
Version: 3:2.6.1-1
Severity: critical
Tags: security
New upstream version addresses several file include and XSS issues; see
http://securityreason.com/adv/phpmyadmin_2.6.1_remote_file_inclusion_and_xss_cxib8o3.4.txt
Also it may be worth considering switching register_globals
make sure you have fileserve1/fileserve in icecast.xml (somewhere in
the icecast section)
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Proposed fix, beware its not been checked for bashisms.
This also adds the check on stop.
--
Mvh,
André Tomt
[EMAIL PROTECTED]
--- /etc/init.d/apache2 2005-02-19 03:07:20.0 +0100
+++ /etc/init.d/apache2.fixed 2005-02-19 03:02:59.0 +0100
@@ -32,7 +32,31 @@
apache_stop() {
Just noticed a minor issue with the proposed fix, when there is no
pidfile, it does not tell like $APACHE2 -k stop would. So to keep things
somewhat consistent with previous behaviour..
add a else statement for the if [ -f /var/run/apache2.pid ] check..
--- /etc/init.d/apache2 2005-02-19
This happens when the turck-mmcache cache files are not cleared after a
PHP-upgrade. Turck would probably need to version check the files, or
something along that route.
So, when upgrading PHP or any of its modules; clear out
/var/cache/turck-mmcache/
--
To UNSUBSCRIBE, email to [EMAIL
The hunk that made cramfs initrds work earlier was the invalidate_bdev
hunk, not the *time hunk. I'm not exactly sure what the *time hunk
fixes, but it has never been needed here for me.
The debian fix for the initrd boot problem was the invalidate_bdev hunk
to fd/block_dev.c ; it was dropped
Package: mdadm
Version: 1.8.1-1
Severity: important
1.8.1 has a severe bug making all newly created RAID arrays get assigned
the same exact UUID, regardless og time or even what machine it runs on.
The UUID in question is 6b8b4567:327b23c6:643c9869:66334873, do a
google search on it, not very
Did you get my sample?
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
51 matches
Mail list logo
