Bug#1041715: chkrootkit runs at very inopportune times (when the server is loaded)
Package: chkrootkit Version: 0.57-2+b2 Severity: normal X-Debbugs-Cc: james.bottom...@hansenpartnership.com The systemd chkrootkit.timer has this line: OnBootSec=30min Which means it runs 30 minutes after a reboot. I tend to upgrade my servers in the early morning, which means it's still running when people start using the services (and it is very disk heavy so they notice the slowdown). Ideally this should run from cron.daily so it can be sequenced with all the other daily services. However, if you insist on running it from systemd, can it at least have an OnCalendar timer set from a config file, so I can sequence it to begin at night? -- System Information: Debian Release: trixie/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 6.3.0-1-amd64 (SMP w/8 CPU threads; PREEMPT) Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages chkrootkit depends on: ii libc6 2.37-5 Versions of packages chkrootkit recommends: ii binutils2.40.90.20230714-2 ii cron [cron-daemon] 3.0pl1-162 ii iproute26.4.0-1 ii mailutils [mailx] 1:3.16-1 ii net-tools 2.10-0.1 ii postfix [mail-transport-agent] 3.8.1-2 ii procps 2:4.0.3-1 ii systemd-sysv253.5-1 chkrootkit suggests no packages. -- no debconf information
Bug#1024822: asterisk: fail2ban no longer monitors asterisk
Package: asterisk Version: 1:20.0.0~dfsg+~cs6.12.40431414-2 Severity: important X-Debbugs-Cc: james.bottom...@hansenpartnership.com Upgrading to the current version of asterisk changes the log location in /etc/asterisk/logger.conf from messages->messages.log This causes fail2ban to stop logging asterisk because its configuration in /etc/fail2ban/jail.conf is logfile = /var/log/asterisk/messages Either change the logging path back to what it was or update fail2ban to look in the new location. -- System Information: Debian Release: bookworm/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 6.0.0-4-amd64 (SMP w/8 CPU threads; PREEMPT) Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages asterisk depends on: ii adduser3.129 ii asterisk-config1:20.0.0~dfsg+~cs6.12.40431414-2 ii asterisk-core-sounds-en1.6.1-1 ii asterisk-modules 1:20.0.0~dfsg+~cs6.12.40431414-2 ii init-system-helpers1.65.2 ii libc6 2.36-5 ii libcap21:2.44-1 ii libcrypt1 1:4.4.30-1 ii libedit2 3.1-20221030-1 ii libjansson42.14-2 ii libpopt0 1.19+dfsg-1 ii libsqlite3-0 3.39.4-1 ii libssl33.0.7-1 ii libsystemd0252.1-1 ii liburiparser1 0.9.7+dfsg-1 ii libuuid1 2.38.1-1.1+b1 ii libxml22.9.14+dfsg-1.1+b2 ii libxslt1.1 1.1.35-1 ii lsb-base 11.5 ii sysvinit-utils [lsb-base] 3.05-6 Versions of packages asterisk recommends: ii asterisk-moh-opsound-gsm 2.03-1.1 ii sox 14.4.2+git20190427-3+b1 Versions of packages asterisk suggests: pn asterisk-dahdi ii asterisk-dev 1:20.0.0~dfsg+~cs6.12.40431414-2 ii asterisk-doc 1:20.0.0~dfsg+~cs6.12.40431414-2 pn asterisk-ooh323 pn asterisk-opus -- no debconf information
Bug#1024443: asterisk-modules no longer includes chan_sip which breaks existing configs
Package: asterisk-modules Version: 1:20.0.0~dfsg+~cs6.12.40431414-2 Severity: grave Justification: renders package unusable X-Debbugs-Cc: james.bottom...@hansenpartnership.com The package asterisk-module no longer contains chan_sip.so which means that all existing SIP configuration with chan_sip stop functioning. I realise a migration to chan_pjsip is eventually required, but that requires at least notice of when chan_sip will be deprecated This actually seems to be a simple configuration error. chan_sip can be built by adding it to ADDONS_ENABLE in debian/rules -- System Information: Debian Release: bookworm/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 6.0.0-4-amd64 (SMP w/8 CPU threads; PREEMPT) Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages asterisk-modules depends on: ii libc-client2007e 8:2007f~dfsg-7+b2 ii libc6 2.36-5 ii libcodec2-1.0 1.0.5-1 ii libcurl4 7.86.0-1 ii libglib2.0-0 2.74.1-2 ii libgmime-3.0-03.2.13+dfsg-2 ii libgsm1 1.0.22-1 ii libical3 3.0.16-1+b1 ii libiksemel3 1.4-4 ii libjack0 [libjack-0.125] 1:0.126.0-1 ii libldap-2.5-0 2.5.13+dfsg-2+b1 ii liblua5.2-0 5.2.4-2 ii libneon27 0.32.4-1 ii libodbc2 2.3.11-2 ii libogg0 1.3.5-1 ii libopencore-amrnb00.1.6-1 ii libopencore-amrwb00.1.6-1 ii libopusfile0 0.12-2 ii libportaudio2 19.6.0-1.2 ii libpq515.1-1 ii libradcli41.2.11-1+b2 ii libresample1 0.1.3-5 ii libsnmp40 5.9.3+dfsg-1+b2 ii libspandsp2 0.0.6+dfsg-2 ii libspeex1 1.2.1-1 ii libspeexdsp1 1.2.1-1 ii libsqlite3-0 3.39.4-1 ii libsrtp2-12.4.2-3 ii libssl3 3.0.7-1 ii libsybdb5 1.3.6-1.1 ii libunbound8 1.17.0-1 ii libvo-amrwbenc0 0.1.3-2 ii libvorbis0a 1.3.7-1 ii libvorbisenc2 1.3.7-1 ii libvorbisfile31.3.7-1 ii libxml2 2.9.14+dfsg-1.1+b2 ii zlib1g1:1.2.11.dfsg-4.1 asterisk-modules recommends no packages. asterisk-modules suggests no packages. -- no debconf information
Bug#1005381: asterisk: app_macro.so module is missing from asterisk-modules
Package: asterisk Version: 1:16.23.0~dfsg+~cs6.10.40431411-1 Severity: important X-Debbugs-Cc: james.bottom...@hansenpartnership.com I can't figure out why because the debian/rules file still has menuselect/menuselect --enable app_macro in execute_before_dh_auto_build: When I run this menuselect command manually it builds app_macro, but apparently it doesn't get built by dpkg-buildpackage which is why it's missing from asterisk-modules -- System Information: Debian Release: bookworm/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 5.15.0-3-amd64 (SMP w/8 CPU threads) Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1), LANGUAGE not set Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages asterisk depends on: ii adduser 3.118 ii asterisk-config 1:16.23.0~dfsg+~cs6.10.40431411-1 ii asterisk-core-sounds-en 1.6.1-1 ii asterisk-modules 1:16.23.0~dfsg+~cs6.10.40431411-1 ii init-system-helpers 1.61 ii libc62.33-5 ii libcap2 1:2.44-1 ii libcrypt11:4.4.27-1.1 ii libedit2 3.1-20210910-1 ii libjansson4 2.13.1-1.1 ii libpopt0 1.18-3 ii libsqlite3-0 3.37.2-2 ii libssl1.11.1.1m-1 ii libsystemd0 250.3-2 ii liburiparser10.9.6+dfsg-1 ii libuuid1 2.37.3-1+b1 ii libxml2 2.9.12+dfsg-5+b1 ii libxslt1.1 1.1.34-4 ii lsb-base 11.1.0 Versions of packages asterisk recommends: ii asterisk-moh-opsound-gsm 2.03-1.1 ii asterisk-voicemail [asterisk-voicemail-s 1:16.23.0~dfsg+~cs6.10.40431411-1 ii sox 14.4.2+git20190427-2 Versions of packages asterisk suggests: pn asterisk-dahdi ii asterisk-dev 1:16.23.0~dfsg+~cs6.10.40431411-1 ii asterisk-doc 1:16.23.0~dfsg+~cs6.10.40431411-1 pn asterisk-ooh323 pn asterisk-opus pn asterisk-vpb -- no debconf information
Bug#971047: wordpress: permalinks fails if wordpress sites have different url prefix paths
Package: wordpress
Version: 5.5.1+dfsg1-1
Severity: normal
Debian wordpress allows for multiple instances of wordpress to be served
from the same box by using config fragments in /etc/wordpress/config-.php
However, /usr/share/wordpress/.htaccess is not fragmented. This is
a problem because permalinks, when enabled places the prefix base into
the htaccess file. So the htaccess file for http://blog.example.com/
is
RewriteEngine On
RewriteBase /
RewriteRule ^index\.php$ - [L]
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule . /index.php [L]
But the htaccess for http://www.example.com/my/site is
RewriteEngine On
RewriteBase /my/site
RewriteRule ^index\.php$ - [L]
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule . /my/site/index.php [L]
Which are completely incompatible, only one or other can work.
There is actually a compatible .htaccess way of doing this, which is
to eliminate the absolute path and use the ability of apache 2.4.16+
to use Alias relative htaccss rewrites, so the .htaccess file
supporting both URLs becomes
RewriteEngine On
RewriteRule ^index\.php$ - [L]
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule . index.php [L]
This still has the bug that all sites or none must use permalinks, but
at least it allows multiple sites with different prefix directories.
-- System Information:
Debian Release: bullseye/sid
APT prefers testing
APT policy: (500, 'testing'), (500, 'stable')
Architecture: i386 (i686)
Kernel: Linux 5.8.0-2-686 (SMP w/1 CPU thread)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages wordpress depends on:
ii apache2 [httpd] 2.4.46-1
ii ca-certificates 20200601
ii libapache2-mod-php 2:7.4+76
ii libapache2-mod-php5 5.6.30+dfsg-0+deb8u1
ii libapache2-mod-php7.4 [libapache2-mod-php] 7.4.9-2
ii libjs-cropper 1.2.2-1
ii libjs-underscore1.9.1~dfsg-1
ii mysql-client-5.6 [virtual-mysql-client] 5.6.30-1
ii php 2:7.4+76
ii php-gd 2:7.4+76
ii php-getid3 1.9.20+dfsg-1
ii php55.6.30+dfsg-0+deb8u1
ii php5-gd 5.6.30+dfsg-0+deb8u1
ii php5-mysql 5.6.30+dfsg-0+deb8u1
ii php7.4 [php]7.4.9-2
ii php7.4-gd [php-gd] 7.4.9-2
ii php7.4-mysql [php-mysqlnd] 7.4.9-2
Versions of packages wordpress recommends:
ii wordpress-l10n5.5.1+dfsg1-1
ii wordpress-theme-twentytwenty 5.5.1+dfsg1-1
Versions of packages wordpress suggests:
ii mysql-server-5.6 [virtual-mysql-server] 5.6.30-1
pn php-ssh2
-- Configuration Files:
/etc/wordpress/htaccess changed [not included]
-- no debconf information
Bug#958830: php-apcu: upgrade to php-apcu 5.1.17->18 breaks nextcloud
Package: php-apcu Version: 5.1.18+4.0.11-1+b1 Severity: grave Justification: renders package unusable After the upgrade nextcloud just gives an internal server error The problem seems to be that nextcloud is configured to use apcu as a memory cache and this version of apcu only has php7.4 files. Nextcloud is currently stuck on php7.3 so the memory cache it's told to use doesn't exist. I can fix this in my nextcloud config.php by commenting out the line 'memcache.local' => '\\OC\\Memcache\\APCu', But the problem certainly makes apcu unusable by nextcloud -- System Information: Debian Release: bullseye/sid APT prefers testing APT policy: (500, 'testing'), (500, 'stable') Architecture: i386 (i686) Kernel: Linux 5.5.0-2-686 (SMP w/1 CPU core) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages php-apcu depends on: ii libc62.30-4 ii php-common 2:69 ii php7.4-cli [phpapi-20190902] 7.4.5-1 ii php7.4-phpdbg [phpapi-20190902] 7.4.5-1 Versions of packages php-apcu recommends: ii php-apcu-bc 1.0.5-2+b1 Versions of packages php-apcu suggests: ii php-gd 2:7.3+69 ii php7.2-gd [php-gd] 7.2.9-1 ii php7.3-gd [php-gd] 7.3.15-3 -- no debconf information
Bug#955247: amavisd-new: upgrade of amavis fails to start daemon
Package: amavisd-new Version: 1:2.11.1-1 Severity: grave Justification: renders package unusable After upgrading to the latest amavisd-new in testing, it fails to start. This is the error from the logs Mar 28 10:22:18 bedivere amavis[3095]: (!)Net::Server: 2020/03/28-10:22:18 Couldn't open pid file "/var/run/amavis/amavisd.pid" [No such file or directory].\n\n at line 177 in file /usr/share/perl5/Net/Server.pm Mar 28 10:22:20 bedivere systemd[1]: amavis.service: Main process exited, code=exited, status=1/FAILURE Mar 28 10:22:20 bedivere systemd[1]: amavis.service: Failed with result 'exit-code'. It looks like the package transitioned to depending on files in /run, but no-one told systemd, so the fix is to add RuntimeDirectory=amavis To amavis.service -- System Information: Debian Release: bullseye/sid APT prefers testing APT policy: (500, 'testing'), (500, 'stable') Architecture: i386 (i686) Kernel: Linux 5.4.0-4-686 (SMP w/1 CPU core) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages amavisd-new depends on: ii adduser3.118 ii debconf [debconf-2.0] 1.5.73 ii file 1:5.38-4 ii init-system-helpers1.57 pn libarchive-tar-perl ii libarchive-zip-perl1.68-1 ii libberkeleydb-perl 0.62-1+b1 ii libcompress-raw-zlib-perl 2.093-1 ii libconvert-tnef-perl 0.18-1 ii libconvert-uulib-perl 1:1.5~dfsg-1+b2 pn libdigest-md5-perl ii libio-stringy-perl 2.111-3 ii libmail-dkim-perl 0.58-1 ii libmailtools-perl 2.21-1 pn libmime-base64-perl ii libmime-tools-perl 5.509-1 ii libnet-libidn-perl 0.12.ds-3+b2 ii libnet-server-perl 2.009-1 ii libunix-syslog-perl1.1-3+b2 ii lsb-base 11.1.0 ii pax1:20190825-1 ii perl [libtime-hires-perl] 5.30.0-9 Versions of packages amavisd-new recommends: ii altermime 0.3.10-10 pn libnet-patricia-perl ii ripole0.2.0+20081101.0215-4 Versions of packages amavisd-new suggests: ii apt-listchanges 3.22 ii arj 3.10.22-23 ii cabextract 1.9-3 ii clamav 0.102.2+dfsg-2 ii clamav-daemon0.102.2+dfsg-2 ii cpio 2.13+dfsg-2 ii dspam3.10.2+dfsg-13 pn lhasa ii libauthen-sasl-perl 2.1600-1 ii libdbi-perl 1.643-1 ii libmail-dkim-perl0.58-1 ii libnet-ldap-perl 1:0.6600+dfsg-1 ii libsnmp-perl 5.8+dfsg-2 pn libzeromq-perl ii lzop 1.04-1 ii nomarch 1.4-3+b2 ii p7zip16.02+dfsg-7 ii rpm 4.14.2.1+dfsg1-1.1 ii spamassassin 3.4.4-1 ii unrar1:5.6.6-2 -- Configuration Files: /etc/amavis/en_US/template-virus-sender.txt changed [not included] /etc/cron.daily/amavisd-new changed [not included] -- debconf information excluded -- debsums errors found: debsums: changed file /lib/systemd/system/amavis.service (from amavisd-new package)
Bug#923208: libengine-pkcs11-openssl: libengines-pkcs11-openssl is installing to the wrong engine directory on x86
Package: libengine-pkcs11-openssl Version: 0.4.9-3 Severity: grave Justification: renders package unusable The problem is this: bedivere:~# dpkg -L libengine-pkcs11-openssl |grep engines /usr/lib/i686-linux-gnu/engines-1.1 /usr/lib/i686-linux-gnu/engines-1.1/pkcs11.la /usr/lib/i686-linux-gnu/engines-1.1/pkcs11.so /usr/lib/i686-linux-gnu/engines-1.1/libpkcs11.so But if you look at where the openssl engines dir actually is bedivere:~# dpkg -L libssl1.1 |grep engines /usr/lib/i386-linux-gnu/engines-1.1 /usr/lib/i386-linux-gnu/engines-1.1/afalg.so /usr/lib/i386-linux-gnu/engines-1.1/capi.so /usr/lib/i386-linux-gnu/engines-1.1/padlock.so The result being the pkcs11 engine is unusable leading to errors like this: [ 221s] invalid engine "pkcs11" [ 221s] 4145891072:error:25066067:DSO support routines:dlfcn_load:could not load the shared library:../crypto/dso/dso_dlfcn.c:117:filename(/usr/lib/i386-linux-gnu/engines-1.1/pkcs11.so): /usr/lib/i386-linux-gnu/engines-1.1/pkcs11.so: cannot open shared object file: No such file or directory This looks to be caused by an incorrect override to the --enginesdir configure flag in the debian/rules file of libp11: --- ENGINES_DIR := /usr/lib/$(DEB_HOST_GNU_TYPE)/engines-$(OPENSSL_VERSION) %: dh $@ override_dh_auto_configure: dh_auto_configure -- \ --with-enginesdir=$(ENGINES_DIR) --- I think the libcrypto pkgconf file just works, so there's no need for the override. -- System Information: Debian Release: buster/sid APT prefers testing APT policy: (500, 'testing'), (500, 'stable') Architecture: i386 (i686) Kernel: Linux 4.19.0-2-686 (SMP w/1 CPU core) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages libengine-pkcs11-openssl depends on: ii libc6 2.28-6 ii libssl1.1 1.1.1a-1 ii p11-kit0.23.14-2 libengine-pkcs11-openssl recommends no packages. libengine-pkcs11-openssl suggests no packages. -- no debconf information
Bug#920533: asterisk: on upgrade from 13.23.1 to 16.1.1 RTP streams get misdirected to NAT devices
Package: asterisk Version: 1:16.1.1~dfsg-1 Severity: important The symptom is that NAT connected devices can't send or receive audio tcpdump shows the asterisk server is sending audio to the RTP header address, which is behind the NAT instead of the NAT gateway address. Further debugging shows that __ast_read() is never actually getting to the ast_rtp_read() function because __ast_read() always has an AST_TIMER_EVENT_EXPIRED so the RTP nat detection and setup is never called because we technically have never received an RTP packet from the remote. I've fixed this in my local installation by setting the RTP remote address to the sip remote address if chan_sip detects a nat, but this seems to be a timer problem so this fix is likely only papering it over. -- System Information: Debian Release: buster/sid APT prefers testing APT policy: (500, 'testing'), (500, 'stable') Architecture: i386 (i686) Kernel: Linux 4.19.0-1-686 (SMP w/1 CPU core) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages asterisk depends on: ii adduser 3.118 ii asterisk-config 1:16.1.1~dfsg-1 ii asterisk-core-sounds-en 1.6.1-1 ii asterisk-modules 1:16.1.1~dfsg-1 ii libc62.28-5 ii libcap2 1:2.25-1.2 ii libedit2 3.1-20181209-1 ii libgcc1 1:8.2.0-14 ii libjansson4 2.12-1 ii libpopt0 1.16-11 ii libsqlite3-0 3.26.0+fossilbc891ac6b-1 ii libssl1.11.1.1a-1 ii libsystemd0 240-4 ii liburiparser10.9.1-1 ii libuuid1 2.33.1-0.1 ii libxml2 2.9.4+dfsg1-7+b3 ii libxslt1.1 1.1.32-2 ii lsb-base 10.2018112800 Versions of packages asterisk recommends: ii asterisk-moh-opsound-gsm 2.03-1 ii asterisk-voicemail [asterisk-voicemail-storage] 1:16.1.1~dfsg-1 ii sox 14.4.2-3 Versions of packages asterisk suggests: pn asterisk-dahdi ii asterisk-dev 1:16.1.1~dfsg-1 ii asterisk-doc 1:16.1.1~dfsg-1 pn asterisk-ooh323 pn asterisk-opus pn asterisk-vpb -- no debconf information -- debsums errors found: debsums: changed file /usr/sbin/asterisk (from asterisk package)
Bug#916543: php7.2: obsoleting php7.2 in favour of php7.3 breaks nextcloud
Package: php7.2-common Version: 7.2.9-1 Severity: important It looks like several php 7 requiring web applications have not successfully migrated from 7.2 to 7.3, among them being nextcloud. It definitely still fails with 7.3 (nextcloud latest production 14.0.4). Unreleased nextcloud 15 is targetted for php 7.3 In the meantime upgrading php-defaults removes php7.2-gd which is what caused nextcloud to fail (the rest of libapache2-mod-php7.2 remains installed but would likely begin losing pieces as well) -- System Information: Debian Release: buster/sid APT prefers testing APT policy: (500, 'testing'), (500, 'stable') Architecture: i386 (i686) Kernel: Linux 4.18.0-3-686 (SMP w/1 CPU core) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages php7.2 depends on: ii libapache2-mod-php7.2 7.2.9-1 ii php7.2-common 7.2.9-1 php7.2 recommends no packages. php7.2 suggests no packages. Versions of packages php7.2-common depends on: ii libc6 2.27-8 ii libssl1.1 1.1.1a-1 ii php-common 2:68 ii ucf 3.0038 -- no debconf information
Bug#541702: linux-image-2.6.30-1-686: Kernel fails to start networking because no e100 firmware
Package: linux-image-2.6.30-1-686 Version: 2.6.30-5 Severity: serious Justification: Policy 2.2.1 On upgrade from 2.6.30-2-686 networking (on a remote machine) failed to start, meaning that a support ticket had to be opened for KVM access. Diagnosis revealed that the e100 driver in 2.6.26-2-686 required no firmware, so the firmware-linux package wasn't installed. Apparently 2.6.30-1-686 was built with external firmware for the e100 so it now depends on the firmware-linux package. This is a serious policy violation because required hardware stops working after the upgrade. Fix suggested is to make 2.6.30-1-686 depend on linux-firmware so that on upgrade the necessary firmware is present. -- Package-specific info: -- System Information: Debian Release: squeeze/sid APT prefers testing APT policy: (500, 'testing'), (500, 'stable') Architecture: i386 (i686) Kernel: Linux 2.6.26-2-686 (SMP w/1 CPU core) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages linux-image-2.6.30-1-686 depends on: ii debconf [debconf-2.0] 1.5.27 Debian configuration management sy ii initramfs-tools [linux-initra 0.93.4 tools for generating an initramfs ii module-init-tools 3.9-2 tools for managing Linux kernel mo Versions of packages linux-image-2.6.30-1-686 recommends: ii libc6-i6862.9-23 GNU C Library: Shared libraries [i Versions of packages linux-image-2.6.30-1-686 suggests: ii grub 0.97-55GRand Unified Bootloader (dummy pa ii grub-legacy [grub]0.97-55GRand Unified Bootloader (Legacy v pn linux-doc-2.6.30 none (no description available) -- debconf information: linux-image-2.6.30-1-686/preinst/lilo-has-ramdisk: shared/kernel-image/really-run-bootloader: true linux-image-2.6.30-1-686/postinst/old-initrd-link-2.6.30-1-686: true linux-image-2.6.30-1-686/postinst/create-kimage-link-2.6.30-1-686: true linux-image-2.6.30-1-686/postinst/depmod-error-2.6.30-1-686: false linux-image-2.6.30-1-686/postinst/old-system-map-link-2.6.30-1-686: true linux-image-2.6.30-1-686/prerm/would-invalidate-boot-loader-2.6.30-1-686: true linux-image-2.6.30-1-686/preinst/overwriting-modules-2.6.30-1-686: true linux-image-2.6.30-1-686/preinst/lilo-initrd-2.6.30-1-686: true linux-image-2.6.30-1-686/postinst/old-dir-initrd-link-2.6.30-1-686: true linux-image-2.6.30-1-686/preinst/failed-to-move-modules-2.6.30-1-686: linux-image-2.6.30-1-686/postinst/bootloader-test-error-2.6.30-1-686: linux-image-2.6.30-1-686/preinst/abort-install-2.6.30-1-686: linux-image-2.6.30-1-686/postinst/bootloader-error-2.6.30-1-686: linux-image-2.6.30-1-686/preinst/initrd-2.6.30-1-686: linux-image-2.6.30-1-686/prerm/removing-running-kernel-2.6.30-1-686: true linux-image-2.6.30-1-686/postinst/kimage-is-a-directory: linux-image-2.6.30-1-686/preinst/abort-overwrite-2.6.30-1-686: linux-image-2.6.30-1-686/preinst/elilo-initrd-2.6.30-1-686: true linux-image-2.6.30-1-686/preinst/bootloader-initrd-2.6.30-1-686: true linux-image-2.6.30-1-686/postinst/depmod-error-initrd-2.6.30-1-686: false -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
