[Bug 2072648] Re: Regression in Apache 2.4.52-1ubuntu4.10 causes intermittent errors in mod_proxy_http2 backend
I can confirm that the package that you provided fixes the issue for me. Thank you very much for the quick help! Your intuition seems to better than mine, because I have to admit that it took me a while how the commit that you linked fixes the issue and how it was previously introduced by the security fix. For those readers who are interested and do not want to read all the relevant sections of the source code themselves, here is the explanation: The patch for CVE-2024-38477 introduced a check that verifies that the URI contains a hostname. As long as this check was missing, a dormant bug in proxy_http2_handler that in case of a retry caused ap_proxy_determine_connection to be called for a URL that had already been processed by this function, did not cause any immediate problems (I guess the URL got somewhat mangled, but this did not matter because the affected parts of were not used after that). With the introduction of the check of the hostname, this bug suddenly became visible. As this bug was in mod_proxy_http2, proxy connections to HTTP/1 servers were not affected, which lead to this funny effect that HTTP/2 connections occassionally failed while HTTP/1 connections were unaffected, even though the security patch itself did not make any changes to the HTTP/2 logic. ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2024-38477 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2072648 Title: Regression in Apache 2.4.52-1ubuntu4.10 causes intermittent errors in mod_proxy_http2 backend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apache2/+bug/2072648/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2072648] Re: Regression in Apache 2.4.52-1ubuntu4.10 causes intermittent errors in mod_proxy_http2 backend
Thanks for picking this up. I redacted the URI because some of the examples contained sensitive data and the the value depends on the actual request, but it always seems to be the actual request URI including the query string. Here are a few examples that do not contain sensitive data: URI has no hostname: /?module=Login URI has no hostname: /index.php?date=yesterday=API=API.getWidgetMetadata_limit=-1=JSON=1=1=day URI has no hostname: /index.php?date=yesterday=API=json=API.getReportPagesMetadata_limit=-1==1=day If you send me a link to packages with a potential fix, I am happy to test them. The problem appears so frequently that I can easily reproduce it within a few minutes. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2072648 Title: Regression in Apache 2.4.52-1ubuntu4.10 causes intermittent errors in mod_proxy_http2 backend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apache2/+bug/2072648/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2072648] [NEW] Regression in Apache 2.4.52-1ubuntu4.10 causes intermittent errors in mod_proxy_http2 backend
Public bug reported: Version 2.4.52-1ubuntu4.10 of the apache2 package that was released in order to fix the issues described in USN-6885-1 introduced a regression that leads to intermittent 502 errors when proxying requests to a HTTP/2 server. This issue is not present in version 2.4.52-1ubuntu4.9 of the package, so it must have been introduced as a side effect of the security fixes. The affected server uses the following configuration to proxy requests to an Apache HTTPd version 2.4.61 that is running inside a Docker container: ProxyPass "/" "h2c://localhost:8080/" ProxyPassReverse "/" "http://localhost:8080/; ProxyPreserveHost On RequestHeader set "X-Forwarded-Proto" "expr=%{REQUEST_SCHEME}" RequestHeader unset "X-Forwarded-For" RequestHeader unset "X-Forwarded-Host" RequestHeader unset "X-Forwarded-Server" This configuration works without any problems when using Apache 2.4.52-1ubuntu4.9. After upgrading to Apache 2.4.52-1ubuntu4.10, the following error message is intermittently displayed when trying to access a proxied resource: Bad Gateway The proxy server received an invalid response from an upstream server. The proxy server could not handle the request Reason: URI has no hostname: /… Apache/2.4.52 (Ubuntu) Server at … Port 443 The request does not show up in the log of the server running inside the Docker container, so it seems like it is not forwarded correctly. This problem does not appear when changing ProxyPass "/" "h2c://localhost:8080/" to ProxyPass "/" "http://localhost:8080/; so it only seems to appear when using the HTTP/2 backend. My best guess is that one of the changes that were introduced to address the security vulnerabilities also introduced a race condition that is only triggered when using HTTP/2 that is more parallel in nature. This seems to be corroborated by my observation that this problem seems to appear more frequently when many requests are forwarded in parallel or at least quick succession. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: apache2 2.4.52-1ubuntu4.10 ProcVersionSignature: Ubuntu 5.15.0-113.123-generic 5.15.152 Uname: Linux 5.15.0-113-generic x86_64 Apache2ConfdDirListing: False Apache2Modules: httpd (pid 580607) already running ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown Date: Wed Jul 10 14:25:29 2024 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: apache2 UpgradeStatus: Upgraded to jammy on 2024-01-05 (187 days ago) ** Affects: apache2 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy uec-images -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2072648 Title: Regression in Apache 2.4.52-1ubuntu4.10 causes intermittent errors in mod_proxy_http2 backend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apache2/+bug/2072648/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1938097] Re: ubuntu-advantage-tools upgrade fails configure
An alternative workaround is uninstalling the cloud-init package. If this package is not installed, cloud-init cannot be found, so the error does not happen. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1938097 Title: ubuntu-advantage-tools upgrade fails configure To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-advantage-tools/+bug/1938097/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1938097] Re: ubuntu-advantage-tools upgrade fails configure
I think the problem is in the postinst script, line 295: cloud_id="" if command -v "cloud-id" > /dev/null ; then cloud_id=$(cloud-id) fi The third line should rather be: cloud_id=$(cloud-id || true) This way, an error reported by the cloud-id command is treated just like if cloud-id is not available (which seems reasonable to me). As a workaround, you can edit the file /var/lib/dpkg/info/ubuntu- advantage-tools.postinst making this change and then run dpkg --configure -a. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1938097 Title: ubuntu-advantage-tools upgrade fails configure To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-advantage-tools/+bug/1938097/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1734700] Re: mounting CIFS share failure (cifs_mount failed w/return code = -2)
I can also confirm that installing the keyutils package fixes the problem (on Ubuntu 20.04). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1734700 Title: mounting CIFS share failure (cifs_mount failed w/return code = -2) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cifs-utils/+bug/1734700/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1887177] Re: ovsdb-server.service needs a depedency on local-fs.target
We are affected by this bug, too. A more stable workaround than modifying /lib/systemd/system/ovsdb- server.service might be adding an overrides file (so that the fix will survive package upgrades). On our affected systems, we added a file /etc/systemd/system/ovsdb- server.service.d/after-local-fs.conf with the following content: [Unit] After=local-fs.target -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1887177 Title: ovsdb-server.service needs a depedency on local-fs.target To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openvswitch/+bug/1887177/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1867916] Re: Regression in kernel 4.15.0-91 causes kernel panic with Bcache
We don’t have any systems with Xenial any longer, so I can’t test there. In fact, just this week we decommissioned the Bionic-based system where I originally discovered this bug, so even there, I can’t test it any longer. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1867916 Title: Regression in kernel 4.15.0-91 causes kernel panic with Bcache To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1867916/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1867916] Re: Regression in kernel 4.15.0-91 causes kernel panic with Bcache
Thank you, Mauricio! I can confirm that your test kernel for Bionic (4.15.0-110.111+lp1867916.1) fixes the problem for me. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1867916 Title: Regression in kernel 4.15.0-91 causes kernel panic with Bcache To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1867916/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1867916] Re: Regression in kernel 4.15.0-91 causes kernel panic with Bcache
Hi Mauricio, according to my Bash history, I used the following two commands to create the Bcache device: make-bcache -B -b 524288 -w 524288 -o 8192 /dev/vg0/vg2-backend make-bcache -C -b 4194304 -w 4096 -o 8192 /dev/vg1/vg2-cache I think the reason why I used this block size was that the MD RAID device backing vg0 uses a stripe size of 512K and I wanted to ensure that everything is neatly aligned. Best regards, Sebastian -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1867916 Title: Regression in kernel 4.15.0-91 causes kernel panic with Bcache To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1867916/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1867916] Re: Regression in kernel 4.15.0-91 causes kernel panic with Bcache
Hi Mauricio, I have attached the requested information. Best regards, Sebastian ** Attachment added: "lp1867916-queue_block_size.seb" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1867916/+attachment/5379837/+files/lp1867916-queue_block_size.seb -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1867916 Title: Regression in kernel 4.15.0-91 causes kernel panic with Bcache To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1867916/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1867916] Re: Regression in kernel 4.15.0-91 causes kernel panic with Bcache
Hi Mauricio, I can confirm that your patched kernel fixes the problem for me on Bionic (kernel 4.15). Thanks for your help! -Sebastian -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1867916 Title: Regression in kernel 4.15.0-91 causes kernel panic with Bcache To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1867916/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1867916] Re: Regression in kernel 4.15.0-91 causes kernel panic with Bcache
Hi Mauricio, thanks for your support. I have attached the requested information to the bug. I had to pseudomize some of the logical volume names because they are considered sensitive, but I did so in a consistent way so the structure should still be clear. So that you don’t have to look through all details, here is a rough overview: There are six physical disks: 4 HDDs (sda, sdb, sdc, sdd) and 2 SSDs (sde, sdf). There are three DM RAID devices: - md0 is a RAID 1 that uses /dev/sda1, /dev/sdb1, /dev/sdc1, and /dev/sdd1. This device stores the boot partition. - md1 is a RAID 6 that uses /dev/sda2, /dev/sdb2, /dev/sdc2, and /dev/sdd2. This device is the only physical volume backing volume group vg0. - md2 is a RAID 1 that uses /dev/sde1 and /dev/sdf1. This device is used as the cache device (read/write) for Bcache. There are three LVM volume groups: - vg0 is backed by /dev/md0 and stores the root FS, the swap partition, a few LVs that are used for VMs, and an LV called vg2-backend, that is used by Bcache. - vg1 is backed by /dev/md2 and only has an LV called vg2-cache that is used by Bcache. - vg2 is backed by /dev/bcache0. It only contains LVs that are used for VMs. There is one Bcache device: - bcache0 is backed by /dev/vg0/vg2-backend (backend device) and /dev/vg1/vg2-cache (cache device). This device is used as the PV for vg2. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1867916 Title: Regression in kernel 4.15.0-91 causes kernel panic with Bcache To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1867916/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1867916] Re: Regression in kernel 4.15.0-91 causes kernel panic with Bcache
** Attachment added: "block device hierarchy" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1867916/+attachment/5347771/+files/lp1867916.1.out -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1867916 Title: Regression in kernel 4.15.0-91 causes kernel panic with Bcache To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1867916/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1867916] Re: Regression in kernel 4.15.0-91 causes kernel panic with Bcache
Hi Mauricio, there is the problem that this tarball contains an awful lot of sensitive data, some of that personal data that is protected under the GDPR. Maybe you could tell me which specific parts / sections you are interested in, so that I can anonymize and upload them. Thanks, Sebastian -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1867916 Title: Regression in kernel 4.15.0-91 causes kernel panic with Bcache To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1867916/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1867916] [NEW] Regression in kernel 4.15.0-91 causes kernel panic with Bcache
Public bug reported: After upgrading from kernel 4.15.0-88 to 4.15.0-91 one of our systems does not boot any longer. It always crashes during boot with a kernel panic. I suspect that this crash might be related to Bcache because this is the only one of our systems where we use Bcache and the kernel panic appears right after Bcache initialization. I already checked that this bug still exists in the 4.15.0-92.93 kernel from proposed. Unfortunately, I cannot do a bisect because this is a critical production system and we do not have any other system with a similar configuration. I attached a screenshot with the trace of the kernel panic. The last message that appears before the kernel panic (or rather the last one that I can see - there is a rather long pause between that message and the panic and I cannot scroll up far enough to ensure that there are no other messages in between) is: bcache: register_bcache() error /dev/dm-0: device already registered When booting with kernel 4.15.0-88 that does not have this problem, the next message is bcache: register_bcache() error /dev/dm-12: device already registered (emitting change event) After that the next message is: Begin: Loading essential drivers ... done This message also appears after the kernel panic, but the boot process stalls and the system can only be recovered by doing a hardware reset. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-88-generic 4.15.0-88.88 ProcVersionSignature: Ubuntu 4.15.0-88.88-generic 4.15.18 Uname: Linux 4.15.0-88-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Mar 17 21:08 seq crw-rw 1 root audio 116, 33 Mar 17 21:08 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.11 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Wed Mar 18 12:55:18 2020 HibernationDevice: RESUME=UUID=40512ea2-9fce-40f5-8362-5daf955cc26a InstallationDate: Installed on 2013-07-02 (2450 days ago) InstallationMedia: Ubuntu-Server 12.04.2 LTS "Precise Pangolin" - Release amd64 (20130214) MachineType: HP ProLiant DL160 G6 PciMultimedia: ProcFB: 0 mgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-88-generic root=/dev/mapper/vg0-root ro nosmt nomdmonddf nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw RelatedPackageVersions: linux-restricted-modules-4.15.0-88-generic N/A linux-backports-modules-4.15.0-88-generic N/A linux-firmware 1.173.16 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: Upgraded to bionic on 2018-09-23 (541 days ago) dmi.bios.date: 11/06/2009 dmi.bios.vendor: HP dmi.bios.version: O33 dmi.chassis.asset.tag: 0191525 dmi.chassis.type: 23 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrO33:bd11/06/2009:svnHP:pnProLiantDL160G6:pvr:cvnHP:ct23:cvr: dmi.product.name: ProLiant DL160 G6 dmi.sys.vendor: HP ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic ** Attachment added: "Screenshot of the kernel panic" https://bugs.launchpad.net/bugs/1867916/+attachment/5338345/+files/IMG_3762.JPG -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1867916 Title: Regression in kernel 4.15.0-91 causes kernel panic with Bcache To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1867916/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1337898] Re: Invalid symlinks for libungif.so and libungif.a
I guess there is only one case where the current "fix" would help. If someone had some library providing libungif in a different place, the broken symlinks in /usr/lib might take precedence, thus hiding the correct files. In my opinion, removing the dangling symlinks is a slight improvement on the current situation and the risk of breaking something is very low. On the hand, I do not know whethere there are other considerations regarding a SRU in addition to the potential for regressions (which is low in this case). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1337898 Title: Invalid symlinks for libungif.so and libungif.a To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/giflib/+bug/1337898/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1337898] Re: Invalid symlinks for libungif.so and libungif.a
I tested the package from trusty-proposed, but I am not sure whether the issue can be considered fixed. In fact, the dangling symlinks have been removed, but they have not been added in the right place. This means that software depending on libungif will still not compile. The question is, whether this is by intention: Should libgif provide an alias for libungif (because it effectively provides the functionality of libungif) or is it an intentional choice not to provide libungif and should all software depending on it be changed to depend on libgif instead? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1337898 Title: Invalid symlinks for libungif.so and libungif.a To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/giflib/+bug/1337898/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1337898] Re: Invalid symlinks for libungif.so and libungif.a
I updated the Impact and Test Case sections of this bug's description. I hope this better fits the purpose of describing the actual impact on users. ** Description changed: Impact == - libgif-dev in Ubuntu 14.04 LTS depends on libgif4 and has these symlinks: - /usr/lib/libungif.a -> libgif.a - /usr/lib/libungif.so -> libgif.so.4.1.6 - /usr/lib/x86_64-linux-gnu/libgif.so -> libgif.so.4.1.6 - /usr/lib/libungif.la -> libgif.la - - libgif4 has these files: - /usr/lib/x86_64-linux-gnu/libgif.so.4.1.6 - /usr/lib/x86_64-linux-gnu/libgif.so.4 -> libgif.so.4.1.6 - - Only the 3rd symlink (the multiarch one) in libgif-dev is correct. The - others are dangling. - - This was caused by an obsolete debian/libgif-dev.links + Linking programs that need libungif ("-lungif") will fail. Test Case = - Verify that libgif-dev only includes the one working symlink: - /usr/lib/x86_64-linux-gnu/libgif.so -> libgif.so.4.1.6 + apt-get install build-essential libgif-dev + cat >>test.c EOF + int main(int argc, char **argv) { + return 0; + } + EOF + gcc -lungif test.c + + GCC will fail with "/usr/bin/ld: cannot find -lungif" on affected + systems. Regression Potential None, just removing some dangling symlinks that couldn't work any way. Original Bug Report === In Ubuntu 14.04 LTS on x86_64 I am experiencing the following bug in libgif-dev 4.1.6-11: Symbol links for libungif.a, libungif.la, and libungif.so are created in /usr/lib that point to libgif.a, libgif.la and libgif.so.4.1.6 respectively. However, these files are not in /usr/lib but in /usr/lib/x86_64-linux-gnu. Therefore, the symbol links are invalid. I suggest fixing this by placing the symbol links in the same directory as the target files. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1337898 Title: Invalid symlinks for libungif.so and libungif.a To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/giflib/+bug/1337898/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1608646] Re: ip4 static routes added in NetworkManager UI fail and prevent connection
The workaround suggested by Ikuya Awashiro (setting the gateway for the route to 0.0.0.0) does not work for me. The problem persits even after applying this workaround. The VPN connection is only established when all static routes are deleted from the configuration. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1608646 Title: ip4 static routes added in NetworkManager UI fail and prevent connection To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1608646/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1611348] Re: support for pki missing
** Patch added: "bareos-openssl.patch" https://bugs.launchpad.net/ubuntu/+source/bareos/+bug/1611348/+attachment/4738164/+files/bareos-openssl.patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1611348 Title: support for pki missing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bareos/+bug/1611348/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1611348] Re: support for pki missing
This problem exists because the build-process of the package compiles against GnuTLS insteaed of OpenSSL. The encryption features are only supported when compiling with OpenSSL. In order to change from GnuTLS to OpenSSL, the following changes have to be applied to the source tree: diff -Naur bareos-14.2.6-gnutls/debian/control bareos-14.2.6-openssl/debian/control --- bareos-14.2.6-gnutls/debian/control 2016-04-02 00:12:43.0 +0200 +++ bareos-14.2.6-openssl/debian/control2016-09-10 11:51:27.0 +0200 @@ -15,7 +15,7 @@ liblzo2-dev, libqt4-dev, libreadline-dev, - libgnutls28-dev, + libssl-dev, libwrap0-dev, libx11-dev, libsqlite3-dev, libmysqlclient-dev, libpq-dev, diff -Naur bareos-14.2.6-gnutls/debian/rules bareos-14.2.6-openssl/debian/rules --- bareos-14.2.6-gnutls/debian/rules 2016-04-02 00:12:43.0 +0200 +++ bareos-14.2.6-openssl/debian/rules 2016-09-10 11:48:47.0 +0200 @@ -54,8 +54,8 @@ --with-mysql \ --with-sqlite3 \ --with-tcp-wrappers \ - --without-openssl \ - --with-gnutls \ + --with-openssl \ + --without-gnutls \ --with-dir-user=$(DIRECTOR_DAEMON_USER) \ --with-dir-group=$(DAEMON_GROUP) \ --with-sd-user=$(STORAGE_DAEMON_USER) \ However, the package maintainer might have had good reasons to change from OpenSSL to GnuTLS. Funnily, even though the package is currently built with GnuTLS, the binary package still depends on OpenSSL, due to a dependency defined in the control file. I guess this was just forgotten when changing from OpenSSL to GnuTLS, but it means that when changing back to OpenSSL, this actually does not have an effect on the binary dependencies. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1611348 Title: support for pki missing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bareos/+bug/1611348/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1527902] Re: 3.13.0-71: IPv6 UDP DNS packets are not received
I think that unlike the bug title and description suggest, this bug is not limited to IPv6. I am having the same problem with FreeRADIUS when RADIUS packets are received over IPv4. This problem is fixed by the Kernel from trusty-proposed, too. Actually, this problem looks a lot like a regression that already appeared in 3.13.0-66 and was fixed in 3.13.0-67 (see bug #1510213 which turned out to be the same problem as tracked in #1508510). So maybe, some measures should be taken to ensure that this regression does not make it into a released kernel again but it is detected during QA. A side note regading the problem with FreeRADIUS: I only had this problem on a multi-core multi-socket machine. On a multi-core single- socket machine, it did not appear, but this might just have been a coincidence. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1527902 Title: 3.13.0-71: IPv6 UDP DNS packets are not received To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1527902/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1337898] Re: Invalid symlinks for libungif.so and libungif.a
@sds: Yes, they exist, but in /usr/lib, while they should be in /usr/lib/x86_64-linux-gnu (depending on the platform). As libgif.* is not in /usr/lib, the symbol links point to files that do not exist. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1337898 Title: Invalid symlinks for libungif.so and libungif.a To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/giflib/+bug/1337898/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1337898] Re: Invalid symlinks for libungif.so and libungif.a
Are there any plans to backport this change to giflib-4.1.6-11 on trusty? Considering that trusty is still going to be supported for more than three years, it might make sense to backport this bugfix. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1337898 Title: Invalid symlinks for libungif.so and libungif.a To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/giflib/+bug/1337898/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1510213] Re: Regression: Stable kernel update to 3.13.0-66 breaks UDP sockets
*** This bug is a duplicate of bug 1508510 *** https://bugs.launchpad.net/bugs/1508510 I can confirm that this bug is a duplicate of bug #1508510 and that the kernel from -proposed fixes the problem. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1510213 Title: Regression: Stable kernel update to 3.13.0-66 breaks UDP sockets To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1510213/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1510213] [NEW] Regression: Stable kernel update to 3.13.0-66 breaks UDP sockets
Public bug reported: I am running the 3.13 series kernel on Ubuntu 14.04 LTS (Trusty Tahr). A change introduced in version 3.13.0-66.108 of this kernel breaks UDP sockets under certain circumstances. The effect is that the recvfrom operation returns with an error, setting errno to EFAULT, even though the pointers passed to recvfrom are okay. Using bisection, I could track down this problem to a single change: 2dde51aa53393a531b493e3a8194e4d467e194a3 is the first bad commit commit 2dde51aa53393a531b493e3a8194e4d467e194a3 Author: Herbert XuDate: Mon Jul 13 20:01:42 2015 +0800 net: Fix skb csum races when peeking BugLink: http://bugs.launchpad.net/bugs/1500810 [ Upstream commit 89c22d8c3b278212eef6a8cc66b570bc840a6f5a ] When we calculate the checksum on the recv path, we store the result in the skb as an optimisation in case we need the checksum again down the line. This is in fact bogus for the MSG_PEEK case as this is done without any locking. So multiple threads can peek and then store the result to the same skb, potentially resulting in bogus skb states. This patch fixes this by only storing the result if the skb is not shared. This preserves the optimisations for the few cases where it can be done safely due to locking or other reasons, e.g., SIOCINQ. Signed-off-by: Herbert Xu Acked-by: Eric Dumazet Signed-off-by: David S. Miller Signed-off-by: Kamal Mostafa Signed-off-by: Luis Henriques :04 04 423debc59ddbc7424283e647e609289fd40dc494 2511e80df4c30a7309737f6b3cee0260269a0ef7 M net Steps to reproduce the problem: Install freeradius, and have a radius client connect to the RADIUS server. After a short amount of time, freeradius spins at 100% CPU, alternating between a select and recvfrom call. The recvfrom call fails every time with error EFAULT. As an alternative to freeradius, you can use the following minimal program that I wrote that also exhibits this problem: #include #include #include #include #include #include #include #include #include int prepare_socket(int port) { int sock = socket(AF_INET, SOCK_DGRAM, 0); if (sock < 0) { printf("Could not create socket.\n"); return -1; } int opt = 1; if (setsockopt(sock, SOL_IP, IP_PKTINFO, , sizeof(opt)) < 0) { printf("setsockopt failed.\n"); return -1; } struct sockaddr_in bind_addr; bind_addr.sin_family = AF_INET; bind_addr.sin_port = htons(port); bind_addr.sin_addr.s_addr = INADDR_ANY; int rc = bind(sock, (struct sockaddr *) _addr, sizeof(bind_addr)); if (rc < 0) { printf("Could not bind socket.\n"); return -1; } return sock; } int main(int argc, char **argv) { int sock = prepare_socket(1812); if (sock < 0) { return 1; } for (;;) { unsigned char buffer[4]; struct sockaddr src; socklen_t src_len = sizeof(src); ssize_t received_len = recvfrom(sock, buffer, sizeof(buffer), MSG_PEEK, , _len); if (received_len < 0) { if (errno == EAGAIN) { printf("EAGAIN\n"); continue; } printf("recvfrom failed.\n"); perror(NULL); return 1; } if (received_len == 4) { src_len = sizeof(src); received_len = recvfrom(sock, buffer, sizeof(buffer), 0, , _len); if (received_len != 4) { printf("Strange received length.\n"); return 1; } } } /* Never reached */ return 0; } However, I did not find out how to craft the traffic that triggers the bug. However, the traffic from a RADIUS client (a WiFi AP in my case) reliably triggers the bug after a few seconds. As this is perfectly legal code and the problem only appears with the change introduced earlier, I think that this is a regression and the change in question should be removed from the stable kernel tree. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-66-generic 3.13.0-66.108 ProcVersionSignature: Ubuntu 3.13.0-66.108-generic 3.13.11-ckt27 Uname: Linux 3.13.0-66-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Oct 25 19:23 seq crw-rw 1 root audio 116, 33 Oct 25 19:23 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.14.1-0ubuntu3.16 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: Error: [Errno 2] No such file or directory: 'iw' Date: Mon Oct 26 18:58:42 2015 HibernationDevice: RESUME=/dev/mapper/vg0-swap InstallationDate: Installed on 2015-01-02 (296 days ago) InstallationMedia: Ubuntu-Server 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.3) IwConfig: eth0 no wireless extensions. lono
[Bug 1406105] Re: Broken logrotate script in freeradius-2.1.12+dfsg-1.2ubuntu8 on Ubuntu 14.04 LTS
I verified that the bug is fixed in version 2.1.12+dfsg-1.2ubuntu8.1 and that the upgrade process (restart) works as intended. Thank you very much for your efforts in fixing this bug. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1406105 Title: Broken logrotate script in freeradius-2.1.12+dfsg-1.2ubuntu8 on Ubuntu 14.04 LTS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/freeradius/+bug/1406105/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1406105] Re: Broken logrotate script in freeradius-2.1.12+dfsg-1.2ubuntu8 on Ubuntu 14.04 LTS
I verified that the bug is fixed in version 2.1.12+dfsg-1.2ubuntu8.1 and that the upgrade process (restart) works as intended. Thank you very much for your efforts in fixing this bug. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1406105 Title: Broken logrotate script in freeradius-2.1.12+dfsg-1.2ubuntu8 on Ubuntu 14.04 LTS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/freeradius/+bug/1406105/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1406105] Re: Broken logrotate script in freeradius-2.1.12+dfsg-1.2ubuntu8 on Ubuntu 14.04 LTS
** Tags removed: verification-needed ** Tags added: verification-done -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1406105 Title: Broken logrotate script in freeradius-2.1.12+dfsg-1.2ubuntu8 on Ubuntu 14.04 LTS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/freeradius/+bug/1406105/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1406105] Re: Broken logrotate script in freeradius-2.1.12+dfsg-1.2ubuntu8 on Ubuntu 14.04 LTS
** Tags removed: verification-needed ** Tags added: verification-done -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1406105 Title: Broken logrotate script in freeradius-2.1.12+dfsg-1.2ubuntu8 on Ubuntu 14.04 LTS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/freeradius/+bug/1406105/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1406105] [NEW] Broken logrotate script in freeradius-2.1.12+dfsg-1.2ubuntu8 on Ubuntu 14.04 LTS
Public bug reported: The freeradius-2.1.12+dfsg-1.2ubuntu8 on Ubuntu 14.04 LTS (Trusty Tahr) has a bug in the logrotate script (/etc/logrotate.d/freeradius): The command /etc/init.d/freeradius reload is used for reloading freeradius after its logfile(s) have been rotated. However, in Ubuntu 14.04 LTS freeradius is managed by Upstart, so that the script cannot work (the PID file does not exist). Therefore, the logrotate script should use initctl reload freeradius instead. Please note that this might not work either at the moment, due to bug #1282683. However, when this bug is finally fixed, the command mentioned earlier should work. ** Affects: freeradius (Ubuntu) Importance: Undecided Status: New ** Patch added: Suggested patch for logrotate script https://bugs.launchpad.net/bugs/1406105/+attachment/4288786/+files/freeradius_logrotate.patch -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to freeradius in Ubuntu. https://bugs.launchpad.net/bugs/1406105 Title: Broken logrotate script in freeradius-2.1.12+dfsg-1.2ubuntu8 on Ubuntu 14.04 LTS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/freeradius/+bug/1406105/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1406105] Re: Broken logrotate script in freeradius-2.1.12+dfsg-1.2ubuntu8 on Ubuntu 14.04 LTS
I just realized that there is a better solution for the logrotate script: By using service freeradius reload, the script will work when Upstart is used but also when the traditional init script is used. ** Patch added: Revised patch for the logrotate script https://bugs.launchpad.net/ubuntu/+source/freeradius/+bug/1406105/+attachment/4288787/+files/freeradius_logrotate.patch -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to freeradius in Ubuntu. https://bugs.launchpad.net/bugs/1406105 Title: Broken logrotate script in freeradius-2.1.12+dfsg-1.2ubuntu8 on Ubuntu 14.04 LTS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/freeradius/+bug/1406105/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1406105] [NEW] Broken logrotate script in freeradius-2.1.12+dfsg-1.2ubuntu8 on Ubuntu 14.04 LTS
Public bug reported: The freeradius-2.1.12+dfsg-1.2ubuntu8 on Ubuntu 14.04 LTS (Trusty Tahr) has a bug in the logrotate script (/etc/logrotate.d/freeradius): The command /etc/init.d/freeradius reload is used for reloading freeradius after its logfile(s) have been rotated. However, in Ubuntu 14.04 LTS freeradius is managed by Upstart, so that the script cannot work (the PID file does not exist). Therefore, the logrotate script should use initctl reload freeradius instead. Please note that this might not work either at the moment, due to bug #1282683. However, when this bug is finally fixed, the command mentioned earlier should work. ** Affects: freeradius (Ubuntu) Importance: Undecided Status: New ** Patch added: Suggested patch for logrotate script https://bugs.launchpad.net/bugs/1406105/+attachment/4288786/+files/freeradius_logrotate.patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1406105 Title: Broken logrotate script in freeradius-2.1.12+dfsg-1.2ubuntu8 on Ubuntu 14.04 LTS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/freeradius/+bug/1406105/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1406105] Re: Broken logrotate script in freeradius-2.1.12+dfsg-1.2ubuntu8 on Ubuntu 14.04 LTS
I just realized that there is a better solution for the logrotate script: By using service freeradius reload, the script will work when Upstart is used but also when the traditional init script is used. ** Patch added: Revised patch for the logrotate script https://bugs.launchpad.net/ubuntu/+source/freeradius/+bug/1406105/+attachment/4288787/+files/freeradius_logrotate.patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1406105 Title: Broken logrotate script in freeradius-2.1.12+dfsg-1.2ubuntu8 on Ubuntu 14.04 LTS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/freeradius/+bug/1406105/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 940825] Re: apt-get update reporting not acceptable
I think that the originally described problem is in fact caused by the bug described in #20. Unless we expect every archive mirror to support ranged requests (which IMHO is a bit much to ask), the 406 error needs to be handled properly. Even if a mirror supports ranges, the implementation in the client is still buggy because of the incorrect handling of ranges for compressed files. Therefore, I will change the description of this bug if I do not hear any other opinion within the next two days. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/940825 Title: apt-get update reporting not acceptable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/940825/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1333553] Re: linux-image-3.13.0-29-generic - soft lockup in kvm guests
*** This bug is a duplicate of bug 1307473 *** https://bugs.launchpad.net/bugs/1307473 I am not sure whether this bug is really a duplicate of #1307473. I experienced the problems described in this bug report without CPU pinning being used. I might add that I had the impression that Windows guests (Windows Server 2012 R2) were more severly affected than Linux guests. However, Linux guests seemed to be more affected if also running the 3.13 kernel. In my case, I experienced the problem after upgrading a VM host from Precise (using kernel 3.5.0-52) to Trusty (using kernel 3.13.0-30). For now, I downgraded back to Precise which made the problems go away. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1333553 Title: linux-image-3.13.0-29-generic - soft lockup in kvm guests To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-lts-trusty/+bug/1333553/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1337898] [NEW] Invalid symlinks for libungif.so and libungif.a
Public bug reported: In Ubuntu 14.04 LTS on x86_64 I am experiencing the following bug in libgif-dev 4.1.6-11: Symbol links for libungif.a, libungif.la, and libungif.so are created in /usr/lib that point to libgif.a, libgif.la and libgif.so.4.1.6 respectively. However, these files are not in /usr/lib but in /usr/lib/x86_64-linux-gnu. Therefore, the symbol links are invalid. I suggest fixing this by placing the symbol links in the same directory as the target files. ** Affects: giflib (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1337898 Title: Invalid symlinks for libungif.so and libungif.a To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/giflib/+bug/1337898/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 940825] Re: apt-get update reporting not acceptable
This problem seems to appear when a file has been partially downloaded to /var/lib/apt/lists/partial and the server does not support request ranges. Here is the error I got when running aptitude update and the corresponding HTTP requests / responses: [...] Err http://de.archive.ubuntu.com precise-updates/universe i386 Packages 406 Not Acceptable [IP: 141.30.13.20 80] [...] W: Failed to fetch http://de.archive.ubuntu.com/ubuntu/dists/precise-updates/universe/binary-i386/Packages 406 Not Acceptable [IP: 141.30.13.20 80] E: Some index files failed to download. They have been ignored, or old ones used instead. The HTTP requests and responses for this file are: GET /ubuntu/dists/precise-updates/universe/binary-i386/Packages.bz2 HTTP/1.1 Host: de.archive.ubuntu.com Connection: keep-alive Cache-Control: max-age=0 Range: bytes=15556- If-Range: Fri, 06 Sep 2013 23:35:00 GMT User-Agent: Debian APT-HTTP/1.3 (0.8.16~exp12ubuntu10.12) HTTP/1.1 416 Requested Range Not Satisfiable Date: Sat, 07 Sep 2013 17:51:48 GMT Connection: keep-alive Server: ATS/3.0.5 Content-Length: 0 GET /ubuntu/dists/precise-updates/universe/binary-i386/Packages.gz HTTP/1.1 Host: de.archive.ubuntu.com Connection: keep-alive Cache-Control: max-age=0 Range: bytes=15556- If-Range: Fri, 06 Sep 2013 23:35:00 GMT User-Agent: Debian APT-HTTP/1.3 (0.8.16~exp12ubuntu10.12) HTTP/1.1 416 Requested Range Not Satisfiable Date: Sat, 07 Sep 2013 17:51:48 GMT Connection: keep-alive Server: ATS/3.0.5 Content-Length: 0 GET /ubuntu/dists/precise-updates/universe/binary-i386/Packages HTTP/1.1 Host: de.archive.ubuntu.com Connection: keep-alive Cache-Control: max-age=0 Accept: text/* Range: bytes=15556- If-Range: Fri, 06 Sep 2013 23:35:00 GMT User-Agent: Debian APT-HTTP/1.3 (0.8.16~exp12ubuntu10.12) HTTP/1.1 406 Not Acceptable Date: Sat, 07 Sep 2013 17:51:48 GMT Server: ATS/3.0.5 Alternates: {Packages.bz2 1 {type application/x-bzip2} {length 219035}}, {Packages.gz 1 {type application/x-gzip} {length 279396}} Vary: negotiate,accept,Accept-Encoding TCN: list Content-Length: 576 Content-Type: text/html; charset=iso-8859-1 Age: 0 Connection: keep-alive [... response body omitted ...] In this case the file /var/lib/apt/lists/partial/de.archive.ubuntu .com_ubuntu_dists_precise-updates_universe_binary-i386_Packages had a size of 15557 bytes. So I think the following thing happens: Apt finds a partially downloaded file, so it tries to continue downloading this file by sending a request with the Range header set. The server cannot serve this request (either because it does not support ranges or because the specified range is invalid). Thus it sends a 416 response. Now Apt makes a mistake: Instead of sending the request again without the Range header, it proceeds to the next file (Packages.gz after Packages.bz2 failed and finally Packages). Funnily it uses the same range there. I think there are two bugs regarding the download of partially download files: 1) The start for the Range header is calculated from the file size on disk. However correct start depends on the type of the compression used. In my example, the file on disk was gzip compressed but the bzip2 version is requested first. Obviously Apt should only try to continue downloading a file with the same compression. 2) When a 416 error occurs, Apt proceeds to the next type of compression instead of trying to download the complete file again. This leads to problems when the server does not support ranges or the range specified is invalid for some reason. Apt should detect a 416 error and proceed with trying to download the complete file. Maybe someone knowing the Apt code better can dig into it and find the place where these changes need to be made. As a workaround, when you are experiencing a 406 error, you can delete the corresponding file(s) in /var/lib/apt/lists/partial. This fixed the problem in my case. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/940825 Title: apt-get update reporting not acceptable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/940825/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1125611] Re: DKMS brcompat module circular dependency causes broken module
I tested the following packages from precise-proposed on Ubuntu 12.04 LTS (amd64) and they work fine for me: openvswitch-brcompat_1.4.0-1ubuntu1.5 openvswitch-common_1.4.0-1ubuntu1.5 openvswitch-controller_1.4.0-1ubuntu1.5 openvswitch-datapath-dkms_1.4.0-1ubuntu1.5 openvswitch-pki_1.4.0-1ubuntu1.5 openvswitch-switch_1.4.0-1ubuntu1.5 -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to openvswitch in Ubuntu. https://bugs.launchpad.net/bugs/1125611 Title: DKMS brcompat module circular dependency causes broken module To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openvswitch/+bug/1125611/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1125611] Re: DKMS brcompat module circular dependency causes broken module
I tested the following packages from precise-proposed on Ubuntu 12.04 LTS (amd64) and they work fine for me: openvswitch-brcompat_1.4.0-1ubuntu1.5 openvswitch-common_1.4.0-1ubuntu1.5 openvswitch-controller_1.4.0-1ubuntu1.5 openvswitch-datapath-dkms_1.4.0-1ubuntu1.5 openvswitch-pki_1.4.0-1ubuntu1.5 openvswitch-switch_1.4.0-1ubuntu1.5 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1125611 Title: DKMS brcompat module circular dependency causes broken module To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openvswitch/+bug/1125611/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1125611] Re: Upgrade to 1.4.0-1ubuntu1.4 breaks brcompat support
I do not think that it is the same bug as originally described in bug #1088160. This bug was an issue with the build system. However, it might be the same problem that that one comment (https://bugs.launchpad.net/ubuntu/+source/openvswitch/+bug/1088160/comments/2) to that bug described. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to openvswitch in Ubuntu. https://bugs.launchpad.net/bugs/1125611 Title: Upgrade to 1.4.0-1ubuntu1.4 breaks brcompat support To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openvswitch/+bug/1125611/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1125611] Re: DKMS brcompat module circular dependency causes broken module
I can confirm the the new version (from the PPA) fixes the problem for me. Thank you very much for the quick solution! -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to openvswitch in Ubuntu. https://bugs.launchpad.net/bugs/1125611 Title: DKMS brcompat module circular dependency causes broken module To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openvswitch/+bug/1125611/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1125611] Re: Upgrade to 1.4.0-1ubuntu1.4 breaks brcompat support
I do not think that it is the same bug as originally described in bug #1088160. This bug was an issue with the build system. However, it might be the same problem that that one comment (https://bugs.launchpad.net/ubuntu/+source/openvswitch/+bug/1088160/comments/2) to that bug described. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1125611 Title: Upgrade to 1.4.0-1ubuntu1.4 breaks brcompat support To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openvswitch/+bug/1125611/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1125611] Re: DKMS brcompat module circular dependency causes broken module
I can confirm the the new version (from the PPA) fixes the problem for me. Thank you very much for the quick solution! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1125611 Title: DKMS brcompat module circular dependency causes broken module To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openvswitch/+bug/1125611/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1125611] [NEW] Upgrade to 1.4.0-1ubuntu1.4 breaks brcompat support
Public bug reported: On Ubuntu 12.04.2 LTS, after an automatic upgrade from openvswitch 1.4.0-1ubuntu1.3 to openvswith 1.4.0-1ubuntu1.4 the brcompat support does not work any longer. The brcompat kernel module can be build, installed, and loaded, but openvswitch-brcompatd will not start with the error message: ovs- brcompatd: could not open brcompat socket. Check brcompat kernel module. After a downgrade back to version 1.4.0-1ubuntu1.3 brcompat works again. I think this is essentially the same problem as described here: https://answers.launchpad.net/ubuntu/+source/openvswitch/+question/221334 It might be unrelated, but after the upgrade lsmod does not list the openvswitch module as a dependency of the brcompat module. After downgrading, the dependency is shown again. ** Affects: openvswitch (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to openvswitch in Ubuntu. https://bugs.launchpad.net/bugs/1125611 Title: Upgrade to 1.4.0-1ubuntu1.4 breaks brcompat support To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openvswitch/+bug/1125611/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1125611] [NEW] Upgrade to 1.4.0-1ubuntu1.4 breaks brcompat support
Public bug reported: On Ubuntu 12.04.2 LTS, after an automatic upgrade from openvswitch 1.4.0-1ubuntu1.3 to openvswith 1.4.0-1ubuntu1.4 the brcompat support does not work any longer. The brcompat kernel module can be build, installed, and loaded, but openvswitch-brcompatd will not start with the error message: ovs- brcompatd: could not open brcompat socket. Check brcompat kernel module. After a downgrade back to version 1.4.0-1ubuntu1.3 brcompat works again. I think this is essentially the same problem as described here: https://answers.launchpad.net/ubuntu/+source/openvswitch/+question/221334 It might be unrelated, but after the upgrade lsmod does not list the openvswitch module as a dependency of the brcompat module. After downgrading, the dependency is shown again. ** Affects: openvswitch (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1125611 Title: Upgrade to 1.4.0-1ubuntu1.4 breaks brcompat support To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openvswitch/+bug/1125611/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 986371] Re: Regression in nvidia-graphics-drivers causes freezes in combination with gnome-screensaver
Peter, yes I was trying to install the nvidia-current from the quantal repository, which has the dependency on the newer X version. A few weeks ago I updated the affected system to precise. The version of the nvidia-current package in precise had the same problems as the one in lucid. In fact it was even worse, because the system was freezing all the time. I guess this is due to Unity using a lot of GFX features. I then installed the nvidia-current from quantal (this is version 295.53-0ubuntu1). In precise this worked because the X server is newer. This fixed the problem for me. There are no freezes with this version of the Nvidia driver. So it really seems like Nvidia introduced a bug with the security fix, but they only fixed it in the 295-series of the driver. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/986371 Title: Regression in nvidia-graphics-drivers causes freezes in combination with gnome-screensaver To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers/+bug/986371/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 986371] Re: Regression in nvidia-graphics-drivers causes freezes in combination with gnome-screensaver
It might be fixed in 295.49, however there is no way to test this, because 295.49 is only available in quantal while I am running lucid. In fact I cannot install it manually either, because it depends on xserver- xorg-core (= 2:1.10.99.901) and the newest version available in lucid is 2:1.7.6-2ubuntu7.11. However, my point is, that this bug is a regression, because it did not appear in the original 195.36 nvidia driver at was introduced with the security patch. I read bug #959842 and the only two regressions listed there are a) problems with CUDA debugging and b) problems with some OpenGL applications running slow. CUDA debugging clearly has nothing to do with gnome-screensaver. and I am quite sure it is not the known OpenGL problem either, because I changed the screen saver to blank screen and the problem persists. Thus, I think OpenGL is not involved either. In conclusion, at the moment with have a version of the nvidia driver in lucid, which breaks (basic) things that worked before. I think there are two appropriate ways to address this: Either the patch can be changed in a way that fixes this bug. This is the preferred solution. If this cannot be done (like with the CUDA debugging problem), we should try to make the 295.49 version of the driver work with the X11 version from lucid. By the way, if this bug is really not fixed before 295.49, that it is even present in precise, which would mean that both LTS versions supported at the moment have a broken version of the nvidia driver. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/986371 Title: Regression in nvidia-graphics-drivers causes freezes in combination with gnome-screensaver To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-common/+bug/986371/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 986371] Re: Regression in nvidia-graphics-drivers causes freezes in combination with gnome-screensaver
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/986371 Title: Regression in nvidia-graphics-drivers causes freezes in combination with gnome-screensaver To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-common/+bug/986371/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 986371] [NEW] Regression in nvidia-graphics-drivers causes freezes in combination with gnome-screensaver
Public bug reported: The security update of the nvidia graphics driver causes a problem on my system (GeForce 8800 GTS): When the screen is locked (using gnome-screensaver) the screen freezes for about 30 seconds. The same thing happens, when the screen is unlocked. This problem appeared after installing the security updates advised by USN-1420-1 ( nvidia-173-modaliases_173.14.22-0ubuntu11.1, nvidia- current_195.36.24-0ubuntu1~10.04.2 and nvidia-current- modaliases_195.36.24-0ubuntu1~10.04.2). When downgrading to the original package versions (nvidia-173-modaliases_173.14.20-0ubuntu5, nvidia- current_195.36.15-0ubuntu2 and nvidia-current- modaliases_195.36.15-0ubuntu2), the problem vanishes. After installing the updated versions again, it reappears. This bug is reproducible: It occurs every time the screen is locked or unlocked as long as the newer versions of the before-mentioned packages are installed. While this bug is not critical (the system only freezes for 30 to 60 seconds), it is very annoying, in particular because it is a regression introduced with a security update. ProblemType: Bug DistroRelease: Ubuntu 10.04 Package: nvidia-common 0.2.23 ProcVersionSignature: Ubuntu 2.6.32-40.87-generic 2.6.32.57+drm33.23 Uname: Linux 2.6.32-40-generic x86_64 NonfreeKernelModules: nvidia Architecture: amd64 Date: Fri Apr 20 21:50:42 2012 ProcEnviron: LANGUAGE=de_DE:de:en_GB:en PATH=(custom, user) LANG=de_DE.utf8 SHELL=/bin/bash SourcePackage: nvidia-common ** Affects: nvidia-common (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug lucid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/986371 Title: Regression in nvidia-graphics-drivers causes freezes in combination with gnome-screensaver To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-common/+bug/986371/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 350936] Re: Should shut down domains on system shutdown
The problem of shutting down the virtual machines consists of two parts: If a init-script is used, libvirtd might be killed, before the shutdown command has been sent to the virtual machines. If the pre-stop script in the libvirt-bin upstart job is used or a new upstart job starting on stopping libvirt-bin is used, the computer is rebooted, the VMs are killed by the sendsigs script. Even if the sendsigs script is modified to not kill the VMs, the reboot or halt script might run before the libvirt-bin upstart job has been stopped. I use the following approach, which works quite well for me: I added a libvirt-shutdown-domains upstart job, which is a task starting on stopping libvirt-bin, thus running before libvirt-bin is stopped. This makes sure that libvirt-bin is not stopped, before the VMs are shutdown. In fact, I also included a runlevel check in the libvirt-shutdown-domains script, so that the VMs are only shutdown, when libvirtd is stopped because of a runlevel change. This allows for libvirtd to be restarted (e.g. when libvirt-bin is upgraded) without having to shutdown all VMs. I also added a init-script running before the sendsigs script, which waits for libvirt-bin to be stopped (or a timeout, whichever occurs first). Thus, sendsigs will not kill VMs and the machine will not be rebooted or powered off, before the VMs have been stopped. The scripts I wrote for this can be found at http://sebastian.marsching.com/wiki/Linux/KVM#Shutdown_virtual_machines_on_host_system_shutdown and some more explanations can be found at http://sebastian.marsching.com/blog/archives/112-KVM-and-Graceful- Shutdown-on-Ubuntu.html. The solution I created is not perfect though because of two issues: 1. The python-libvirt package is needed, because I use a Python script to shutdown the virtual machines. You might want to use a shell script using virsh for that, thus eliminating this dependency. 2. The timeout, after which the shutdown will proceed anyway, is configured at two different places: The init-script and the Python script called by the upstart job. You might want to put both in the same place (e.g. /etc/default/libvirt-bin). -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to kvm in Ubuntu. https://bugs.launchpad.net/bugs/350936 Title: Should shut down domains on system shutdown To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kvm/+bug/350936/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 350936] Re: Should shut down domains on system shutdown
The problem of shutting down the virtual machines consists of two parts: If a init-script is used, libvirtd might be killed, before the shutdown command has been sent to the virtual machines. If the pre-stop script in the libvirt-bin upstart job is used or a new upstart job starting on stopping libvirt-bin is used, the computer is rebooted, the VMs are killed by the sendsigs script. Even if the sendsigs script is modified to not kill the VMs, the reboot or halt script might run before the libvirt-bin upstart job has been stopped. I use the following approach, which works quite well for me: I added a libvirt-shutdown-domains upstart job, which is a task starting on stopping libvirt-bin, thus running before libvirt-bin is stopped. This makes sure that libvirt-bin is not stopped, before the VMs are shutdown. In fact, I also included a runlevel check in the libvirt-shutdown-domains script, so that the VMs are only shutdown, when libvirtd is stopped because of a runlevel change. This allows for libvirtd to be restarted (e.g. when libvirt-bin is upgraded) without having to shutdown all VMs. I also added a init-script running before the sendsigs script, which waits for libvirt-bin to be stopped (or a timeout, whichever occurs first). Thus, sendsigs will not kill VMs and the machine will not be rebooted or powered off, before the VMs have been stopped. The scripts I wrote for this can be found at http://sebastian.marsching.com/wiki/Linux/KVM#Shutdown_virtual_machines_on_host_system_shutdown and some more explanations can be found at http://sebastian.marsching.com/blog/archives/112-KVM-and-Graceful- Shutdown-on-Ubuntu.html. The solution I created is not perfect though because of two issues: 1. The python-libvirt package is needed, because I use a Python script to shutdown the virtual machines. You might want to use a shell script using virsh for that, thus eliminating this dependency. 2. The timeout, after which the shutdown will proceed anyway, is configured at two different places: The init-script and the Python script called by the upstart job. You might want to put both in the same place (e.g. /etc/default/libvirt-bin). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/350936 Title: Should shut down domains on system shutdown To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kvm/+bug/350936/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 280421] [NEW] ethtool not available in post-ifup script
Public bug reported: Binary package hint: ethtool PROBLEM: I am running Ubuntu 8.04 in a Xen DomU. To fix network performance issues, the line post-up /usr/sbin/ethtool -K eth0 tx off is needed for the virtual ethernet device within the /etc/network/intefaces file. Usually this works fine, however if /usr is stored on its own partition this command fails, as /usr is not yet mounted when udev executes ifup for the ethernet device. Unfortunately this causes some very strange errors like /etc/init.d/networking stop to fail bacause the eth0 interface is brought up but not correctly registered in the state file. The only workaround at the moment is to disable the ifup / ifdown hooks in /etc/udev/rules.d/85-ifupdown.rules. PROPOSED SOLUTION: The best solution would be moving /usr/sbin/ethtool to /sbin/ethtool so that it is available on startup before /usr has been mounted. ** Affects: ethtool (Ubuntu) Importance: Undecided Status: New -- ethtool not available in post-ifup script https://bugs.launchpad.net/bugs/280421 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs