[Bug 2076170] [NEW] riscv64 linux image/header/module package versions don't exist for their meta package versions
Public bug reported: Hi, Running mantic on a riscv64 system, trying (a little late) to upgrade from mantic to noble, I ran into "Please install all available updates for your release before upgrading" even after a dist-upgrade. On closer inspection, I see: The following packages have been kept back: linux-generic linux-headers-generic linux-image-generic linux-tools-generic That seems to be because the 6.5.0-42 release made it into the meta packages, but not the actual binary packages: ubuntu@vf2:~$ sudo apt-get install linux-generic=6.5.0.42.42.1 linux-image-generic=6.5.0.42.42.1 linux-headers-generic=6.5.0.42.42.1 linux-tools-generic=6.5.0.42.42.1 Reading package lists... Done Building dependency tree... Done Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: linux-headers-generic : Depends: linux-headers-6.5.0-42-generic but it is not installable linux-image-generic : Depends: linux-image-6.5.0-42-generic but it is not installable Depends: linux-modules-extra-6.5.0-42-generic but it is not installable linux-tools-generic : Depends: linux-tools-6.5.0-42-generic but it is not installable E: Unable to correct problems, you have held broken packages. ubuntu@vf2:~$ These packages don't exist on the archive servers in mantic{,-updates,-security}, and don't seem to exist in -proposed either, however a complete set of 6.5.0-44 packages does exist in -proposed, which unblocks d-r-u for now at least. Do let me know if this should be targeted elsewhere, obviously it's a packaging/release bug rather than an actual released kernel bug. ** Affects: linux (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/2076170 Title: riscv64 linux image/header/module package versions don't exist for their meta package versions To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2076170/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2056111] Re: Bluetooth disabled with MODULES=dep on 24.04
Just to confirm this is still an issue on the final Noble release. Not a huge problem, MODULES=most is the default and works fine. It was nice to be able to have smaller files and thus more space in /boot when it worked with MODULES=dep previously though. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2056111 Title: Bluetooth disabled with MODULES=dep on 24.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2056111/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2056111] Re: Bluetooth disabled with MODULES=dep on 24.04
** Summary changed: - Bluetooth driver disappears from initramfs with MODULES=dep on 24.04 + Bluetooth disabled with MODULES=dep on 24.04 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2056111 Title: Bluetooth disabled with MODULES=dep on 24.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2056111/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2056111] Re: Bluetooth driver disappears from initramfs with MODULES=dep on 24.04
Interestingly, if I rebuild the initramfs with "MODULES=dep", I get the following firmware files in the initramfs under usr/lib/firmware/intel: usr/lib/firmware/intel/ibt-11-5.ddc.zst usr/lib/firmware/intel/ibt-11-5.sfi.zst usr/lib/firmware/intel/ibt-12-16.ddc.zst usr/lib/firmware/intel/ibt-12-16.sfi.zst And the following (currently loaded) btintel kernel module: usr/lib/modules/6.8.0-11-generic/kernel/drivers/bluetooth/btintel.ko.zst Note that my failure is for intel/ibt-19-0-4.sfi specifically though, not listed above. Building with "most", I get none of the above, these are the only files in the "intel" directory: usr/lib/firmware/intel/ice usr/lib/firmware/intel/ice/ddp usr/lib/firmware/intel/ice/ddp/ice-1.3.35.0.pkg.zst usr/lib/firmware/intel/ice/ddp/ice.pkg.zst There's also no match (via lsinitramfs) for "btintel" when I build using "most". However, bluetooth works fine using "most', and not with "dep", so I'm likely barking up the wrong tree here. Full diff between the two initramfs files here: https://paste.ubuntu.com/p/vMR5BGf9Hy/ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2056111 Title: Bluetooth driver disappears from initramfs with MODULES=dep on 24.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2056111/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2056111] [NEW] Bluetooth driver disappears from initramfs with MODULES=dep on 24.04
Public bug reported: Hi, I'm running the noble prerelease on x86, and have had MODULES=dep set in /etc/initramfs-tools/initramfs.conf for some time with no issues. Over the weekend, I noticed updates to linux-image-6.8.0-11-generic, linux-modules-6.8.0-11-generic etc, with an associated initramfs rebuild. After the next reboot, bluetooth was unavailable - via dmesg: 2024-03-04T13:32:47.584364+07:00 x1c9 kernel: Bluetooth: hci0: Failed to load Intel firmware file intel/ibt-19-0-4.sfi (-2) 2024-03-04T13:32:47.584367+07:00 x1c9 kernel: Bluetooth: hci0: Reading supported features failed (-56) 2024-03-04T13:32:47.584367+07:00 x1c9 kernel: Bluetooth: hci0: Error reading debug features 2024-03-04T13:32:47.584368+07:00 x1c9 kernel: Bluetooth: hci0: HCI LE Coded PHY feature bit is set, but its usage is not supported. 2024-03-04T13:32:47.584368+07:00 x1c9 kernel: Bluetooth: hci0: Failed to read MSFT supported features (-56) I'd set MODULES=dep via /etc/initramfs-tools/initramfs.conf many releases ago (this system was installed with 21.04 and has been upgraded to each of the six subsequent series in turn since), which had always worked until now. Reverting that to MODULES=most (which I believe is the default), rebuilding the initramfs and rebooting has restored Bluetooth functionality. I'm not entirely sure which package this should be filed against - I know the referenced intel/ibt-19-0-4.sfi file is actually part of linux- firmware, and initramfs-tools is presumably also involved, but I see no recent updates to either of those packages (last updated on my system in early February, and I've definitely rebooted since then with no issues), so I'm assuming this must be kernel-related, but I may be misunderstanding how this all fits together. ** Affects: linux (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/2056111 Title: Bluetooth driver disappears from initramfs with MODULES=dep on 24.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2056111/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1821251] Re: please add cnf support to debmirror
** Changed in: debmirror (Ubuntu) Status: Fix Released => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1821251 Title: please add cnf support to debmirror To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt-mirror/+bug/1821251/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1873138] Re: monitoring-plugins-standard installs rpcbind via recommends
It should probably be noted that this was rejected in Debian a while back: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=751120 I've filed a separate bug against rpcbind (LP:1873166) to see whether check_rpc could be split into its own package. If that were to happen, then monitoring-plugins could Recommend the new package to satisfy its own requirements without the overhead of also installing and running the rpcbind daemon. ** Bug watch added: Debian Bug tracker #751120 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=751120 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1873138 Title: monitoring-plugins-standard installs rpcbind via recommends To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/monitoring-plugins/+bug/1873138/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1873166] [NEW] Consider splitting check_rpc into a separate package
Public bug reported: There are situations in which the check_rpc utility is required, but in which the user does not wish to also gain an rpc daemon running as root, particularly given LP:1687930 (and perhaps LP:1430181). Separating out the check_rpc utility into its own package seems the simplest way to address this. ** Affects: rpcbind (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/1873166 Title: Consider splitting check_rpc into a separate package To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rpcbind/+bug/1873166/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1873138] [NEW] monitoring-plugins-standard installs rpcbind via recommends
Public bug reported: The monitoring-plugins-standard package has a long list of recommends: Recommends: bind9-host | host, dnsutils, libnet-snmp-perl, rpcbind, smbclient, snmp, libdbi1 (>= 0.8.4), libldap-2.4-2 (>= 2.4.7), libmysqlclient20 (>= 5.7.11), libpq5 Given that apt-get will install Recommends by default, this means that any machine with Nagios plugins installed will also end up with a rpc daemon running as root. Could rpcbind perhaps be moved to Suggests? ** Affects: monitoring-plugins (Ubuntu) Importance: Undecided Status: Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1873138 Title: monitoring-plugins-standard installs rpcbind via recommends To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/monitoring-plugins/+bug/1873138/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1871302] [NEW] Console bell sound is broken
Public bug reported: This is in 20.04 focal on amd64, package version 0.15.0-1build1 Kitty is unable to make a bell sound, erroring with: > Failed to load libcanberra.so, cannot play beep sound, with error: (null) This was fixed upstream here: https://github.com/kovidgoyal/kitty/pull/2178 Fix was released in 0.15.1, but focal is on 0.15.0. ** Affects: kitty (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/1871302 Title: Console bell sound is broken To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kitty/+bug/1871302/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1828496] Re: service haproxy reload sometimes fails to pick up new TLS certificates
Hi Paride, sorry for the late reply - summer holidays. 1). Unfortunately it's a rare one, and I'm not sure exactly what state the service needs to be in, in order to trigger the bug. 2). I believe the pastebin in comment #7 is representative, and that the PIDs don't change, but rather new haproxy processes appear alongside the older ones. I'll certainly confirm and update this bug next time this pops up. It just might be a while before that happens again. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1828496 Title: service haproxy reload sometimes fails to pick up new TLS certificates To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/haproxy/+bug/1828496/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1828496] Re: service haproxy reload sometimes fails to pick up new TLS certificates
It was marked Incomplete in #4, so there's new detail in #5, #7 and #8 - I just missed re-opening it until now. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1828496 Title: service haproxy reload sometimes fails to pick up new TLS certificates To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/haproxy/+bug/1828496/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1828496] Re: service haproxy reload sometimes fails to pick up new TLS certificates
** Changed in: haproxy (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1828496 Title: service haproxy reload sometimes fails to pick up new TLS certificates To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/haproxy/+bug/1828496/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1828496] Re: service haproxy reload sometimes fails to pick up new TLS certificates
Never mind, here it is on Xenial: https://pastebin.ubuntu.com/p/3zbQdnTBtF/ There's nothing relevant to haproxy in syslog, but here's the relevant lines from /var/log/haproxy.log: https://pastebin.ubuntu.com/p/HJT3WRc8Dw/ While the proxy processes apparently did stop, the pid 2215 process did not. Running 'systemctl restart haproxy.service' afterwards killed both processes, and started a single fresh one with a new pid, which I think is correct behaviour. So this does indeed seem likely to be down to using 'service' here. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1828496 Title: service haproxy reload sometimes fails to pick up new TLS certificates To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/haproxy/+bug/1828496/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1828496] Re: service haproxy reload sometimes fails to pick up new TLS certificates
Something similar came up today on a Trusty instance, the WARNING lines are possibly relevant here. To be clear, no certificates were involved in this case, but I did catch the old processes still running after a reload: ubuntu@foo:~$ ps auxf | grep haproxy ubuntu 10790 0.0 0.0 10480 932 pts/2S+ 07:20 0:00 \_ grep --color=auto haproxy haproxy 15581 0.0 0.0 21424 2048 ?Ss May23 1:36 /usr/sbin/haproxy -f /etc/haproxy/haproxy.cfg -p /var/run/haproxy.pid -D -sf 15502 ubuntu@foo:~$ sudo service haproxy reload * Reloading haproxy haproxy [WARNING] 143/072015 (10813) : config : 'option httplog' not usable with frontend 'foo-lb-2-80' (needs 'mode http'). Falling back to 'option tcplog'. [WARNING] 143/072015 (10815) : config : 'option httplog' not usable with frontend 'foo-lb-2-80' (needs 'mode http'). Falling back to 'option tcplog'. [ OK ] ubuntu@foo:~$ ps auxf | grep haproxy ubuntu 10845 0.0 0.0 10480 932 pts/2S+ 07:20 0:00 \_ grep --color=auto haproxy haproxy 15581 0.0 0.0 21424 2048 ?Ss May23 1:36 /usr/sbin/haproxy -f /etc/haproxy/haproxy.cfg -p /var/run/haproxy.pid -D -sf 15502 haproxy 10816 0.0 0.0 21016 1536 ?Ss 07:20 0:00 /usr/sbin/haproxy -f /etc/haproxy/haproxy.cfg -p /var/run/haproxy.pid -D -sf 15581 ubuntu@juju-prodstack-ols-assertions-sign-machine-14:~$ In this case though, neither a 'service haproxy restart' nor a stop+start would kill the old process, I had to send it a TERM signal in the end. I understand that Trusty is no longer supported outside of ESM - if this isn't helpful, I'll delete and update if/when I can reproduce on Xenial or later. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1828496 Title: service haproxy reload sometimes fails to pick up new TLS certificates To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/haproxy/+bug/1828496/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1828496] Re: service haproxy reload sometimes fails to pick up new TLS certificates
This is haproxy 1.6.3-1ubuntu0.2 on Xenial/16.04 running on amd64 hardware. Reproduction steps: 1. Install haproxy and configure it to use a TLS certificate 2. Renew and replace that certificate 3. Run 'service haproxy reload' 4. Sometimes this starts serving the new certificate, sometimes it doesn't ** Changed in: haproxy (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1828496 Title: service haproxy reload sometimes fails to pick up new TLS certificates To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/haproxy/+bug/1828496/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1828496] [NEW] service haproxy reload sometimes fails to pick up new TLS certificates
Public bug reported: I suspect this is the same thing reported on StackOverflow: "I had this same issue where even after reloading the config, haproxy would randomly serve old certs. After looking around for many days the issue was that "reload" operation created a new process without killing the old one. Confirm this by "ps aux | grep haproxy"." https://stackoverflow.com/questions/46040504/haproxy-wont-recognize-new- certificate In our setup, we automate Let's Encrypt certificate renewals, and a fresh certificate will trigger a reload of the service. But occasionally this reload doesn't seem to do anything. Will update with details next time it happens, and hopefully confirm the multiple process theory. ** Affects: haproxy (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/1828496 Title: service haproxy reload sometimes fails to pick up new TLS certificates To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/haproxy/+bug/1828496/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1459692] Re: [MIR] anope
** No longer affects: inspircd (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1459692 Title: [MIR] anope To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/anope/+bug/1459692/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1459692] Re: [MIR] anope
** Also affects: inspircd (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/1459692 Title: [MIR] anope To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/anope/+bug/1459692/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1766770] Re: 4.15.0-15-generic can't find root device
I've confirmed this issue on a second G7 with the same model of RAID controller but a simpler disk setup (no bcache or mdraid): https://pastebin.ubuntu.com/p/bK5xQrXZmD/ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1766770 Title: 4.15.0-15-generic can't find root device To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1766770/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1766770] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1766770/+attachment/5126873/+files/UdevDb.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1766770 Title: 4.15.0-15-generic can't find root device To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1766770/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1766770] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1766770/+attachment/5126871/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1766770 Title: 4.15.0-15-generic can't find root device To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1766770/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1766770] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1766770/+attachment/5126869/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1766770 Title: 4.15.0-15-generic can't find root device To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1766770/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1766770] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1766770/+attachment/5126872/+files/ProcModules.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1766770 Title: 4.15.0-15-generic can't find root device To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1766770/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1766770] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1766770/+attachment/5126866/+files/Lspci.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1766770 Title: 4.15.0-15-generic can't find root device To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1766770/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1766770] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1766770/+attachment/5126870/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1766770 Title: 4.15.0-15-generic can't find root device To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1766770/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1766770] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1766770/+attachment/5126865/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1766770 Title: 4.15.0-15-generic can't find root device To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1766770/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1766770] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1766770/+attachment/5126874/+files/WifiSyslog.txt ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1766770 Title: 4.15.0-15-generic can't find root device To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1766770/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1766770] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1766770/+attachment/5126868/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1766770 Title: 4.15.0-15-generic can't find root device To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1766770/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1766770] Re: 4.15.0-15-generic can't find root device
apport information ** Tags added: apport-collected xenial ** Description changed: This is on a Hewlett-Packard ProLiant DL380 G7, with a Smart Array P410i RAID controller containing a RAID 1+0 array of four SATA hard drives. It's running Ubuntu 16.04 with the linux-image-generic-hwe-16.04-edge packages installed. The root partition consists of a simple ext4 filesystem on /dev/sda1, which is on the RAID array There is a more complex secondary mount involving mdraid and bcache intended to be mounted at /srv - but we're seeing problems before that comes into play. Booting into the last 4.13 kernel (4.13.0-39-generic) works fine. - Booting into the latest 4.15 kernel (4.15.0-15-generic) results in the - root device not being found, and a stacktrace before an initramfs - prompt: https://pastebin.ubuntu.com/p/JnTXQ5YP9W/ + Booting into the latest 4.15 kernel (4.15.0-15-generic) results in the root device not being found, and a stacktrace before an initramfs prompt: https://pastebin.ubuntu.com/p/JnTXQ5YP9W/ + --- + AlsaDevices: + total 0 + crw-rw 1 root audio 116, 1 Apr 25 03:37 seq + crw-rw 1 root audio 116, 33 Apr 25 03:37 timer + AplayDevices: Error: [Errno 2] No such file or directory + ApportVersion: 2.20.1-0ubuntu2.16 + Architecture: amd64 + ArecordDevices: Error: [Errno 2] No such file or directory + AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: + DistroRelease: Ubuntu 16.04 + IwConfig: Error: [Errno 2] No such file or directory + MachineType: HP ProLiant DL380 G7 + Package: linux (not installed) + PciMultimedia: + + ProcFB: 0 radeondrmfb + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-39-generic root=UUID=dd30f756-2a4d-43e5-b49c-dfbafbceea9d ro console=ttyS1,38400 nosplash + ProcVersionSignature: Ubuntu 4.13.0-39.44~16.04.1-generic 4.13.16 + RelatedPackageVersions: + linux-restricted-modules-4.13.0-39-generic N/A + linux-backports-modules-4.13.0-39-generic N/A + linux-firmware 1.157.17 + RfKill: Error: [Errno 2] No such file or directory + Tags: xenial + Uname: Linux 4.13.0-39-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm + _MarkForUpload: True + dmi.bios.date: 08/16/2015 + dmi.bios.vendor: HP + dmi.bios.version: P67 + dmi.chassis.type: 23 + dmi.chassis.vendor: HP + dmi.modalias: dmi:bvnHP:bvrP67:bd08/16/2015:svnHP:pnProLiantDL380G7:pvr:cvnHP:ct23:cvr: + dmi.product.family: ProLiant + dmi.product.name: ProLiant DL380 G7 + dmi.sys.vendor: HP ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1766770/+attachment/5126864/+files/CRDA.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1766770 Title: 4.15.0-15-generic can't find root device To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1766770/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1766770] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1766770/+attachment/5126867/+files/Lsusb.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1766770 Title: 4.15.0-15-generic can't find root device To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1766770/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1766770] Re: 4.15.0-15-generic can't find root device
** Attachment added: "version.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1766770/+attachment/5126847/+files/version.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1766770 Title: 4.15.0-15-generic can't find root device To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1766770/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1766770] [NEW] 4.15.0-15-generic can't find root device
Public bug reported: This is on a Hewlett-Packard ProLiant DL380 G7, with a Smart Array P410i RAID controller containing a RAID 1+0 array of four SATA hard drives. It's running Ubuntu 16.04 with the linux-image-generic-hwe-16.04-edge packages installed. The root partition consists of a simple ext4 filesystem on /dev/sda1, which is on the RAID array There is a more complex secondary mount involving mdraid and bcache intended to be mounted at /srv - but we're seeing problems before that comes into play. Booting into the last 4.13 kernel (4.13.0-39-generic) works fine. Booting into the latest 4.15 kernel (4.15.0-15-generic) results in the root device not being found, and a stacktrace before an initramfs prompt: https://pastebin.ubuntu.com/p/JnTXQ5YP9W/ ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Attachment added: "lspci-vnvn.log" https://bugs.launchpad.net/bugs/1766770/+attachment/5126846/+files/lspci-vnvn.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1766770 Title: 4.15.0-15-generic can't find root device To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1766770/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1719210] Re: Bluetooth audio to A2DP headset no longer works following upgrade from 4.12 to 4.13 in artful
Seeing similar issues with a Logitech M337 bluetooth mouse under the new 4.13.0-11 kernel. Reverting to 4.12.0-13 solves 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/1719210 Title: Bluetooth audio to A2DP headset no longer works following upgrade from 4.12 to 4.13 in artful To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1719210/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1678064] Re: Attempting to install to a single btrfs root partition crashes the installer
Hmm, that warning may be a red herring actually. If I instead run kvm as follows, I encounter the same error, even without the "block 0" warning: $ qemu-img create -f raw target.img 10G Formatting 'target.img', fmt=raw size=10737418240 $ kvm -m 1024 -cdrom custom.iso -drive file=target.img,format=raw warning: host doesn't support requested feature: CPUID.8001H:ECX.svm [bit 2] $ http://pastebin.ubuntu.com/25367641/ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1678064 Title: Attempting to install to a single btrfs root partition crashes the installer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/subiquity/+bug/1678064/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1678064] Re: Attempting to install to a single btrfs root partition crashes the installer
Hi, Sorry for the very late reply here, here's the log as requested: http://pastebin.ubuntu.com/25331706/ On closer inspection, it's likely worth mentioning two warnings emitted by kvm cli I listed in the original report: $ qemu-img create -f raw target.img 10G Formatting 'target.img', fmt=raw size=10737418240 $ kvm -m 1024 -cdrom custom.iso -hda target.img WARNING: Image format was not specified for 'target.img' and probing guessed raw. Automatically detecting the format is dangerous for raw images, write operations on block 0 will be restricted. Specify the 'raw' format explicitly to remove the restrictions. warning: host doesn't support requested feature: CPUID.8001H:ECX.svm [bit 2] ** Changed in: subiquity (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1678064 Title: Attempting to install to a single btrfs root partition crashes the installer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/subiquity/+bug/1678064/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1678064] [NEW] Attempting to install to a single btrfs root partition crashes the installer
Public bug reported: If I create a single partition, type btrfs mounted as /, the installer takes me briefly to the next screen to input user details, but crashes as I enter my name. The error detail box is empty. Partition details: http://people.canonical.com/~barryprice/subi1.png Error screen: http://people.canonical.com/~barryprice/subi2.png This is running under kvm on an amd64 system, via: $ qemu-img create -f raw target.img 10G $ kvm -m 1024 -cdrom custom.iso -hda target.img Performing exactly the same actions but choosing ext4 rather than btrfs works fine. ** Affects: subiquity (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/1678064 Title: Attempting to install to a single btrfs root partition crashes the installer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/subiquity/+bug/1678064/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1667590] Re: Attempting to sync the ubuntu:12.04 image consistently hangs
Thanks, the systemctl restart suggestion did the trick. It's definitely possible that the first attempt ran into network issues. Should there perhaps be a timeout for download operations to avoid this? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1667590 Title: Attempting to sync the ubuntu:12.04 image consistently hangs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxd/+bug/1667590/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1667590] [NEW] Attempting to sync the ubuntu:12.04 image consistently hangs
Public bug reported: Hi, I have successfully synced the ubuntu:14.04, ubuntu:16.04 and ubuntu:16.10 images from cloud-images.ubuntu.com but for some reason the ubuntu:12.04 image can't be retrieved - the process consistently hangs before even making the request from the remote server. http://pastebin.ubuntu.com/24057592/plain/ ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: lxd 2.9.2-0ubuntu1 ProcVersionSignature: Ubuntu 4.10.0-8.10-generic 4.10.0-rc8 Uname: Linux 4.10.0-8-generic x86_64 NonfreeKernelModules: zfs zunicode zavl zcommon znvpair ApportVersion: 2.20.4-0ubuntu2 Architecture: amd64 CurrentDesktop: i3 Date: Fri Feb 24 14:35:10 2017 InstallationDate: Installed on 2016-11-08 (107 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) SourcePackage: lxd UpgradeStatus: Upgraded to zesty on 2017-01-24 (31 days ago) ** Affects: lxd (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug zesty -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1667590 Title: Attempting to sync the ubuntu:12.04 image consistently hangs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxd/+bug/1667590/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1660004] Re: Elements of charm-tools broken under zesty
To be clear, running Ubuntu 17.04 Zesty Zapus on amd64, package version is from the archive, 2.1.2-0ubuntu4. I also tried the PPA release, 2.2.0-0ubuntu1~ubuntu17.04.1~ppa2, and found the same issue there. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1660004 Title: Elements of charm-tools broken under zesty To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/charm-tools/+bug/1660004/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1660004] [NEW] Elements of charm-tools broken under zesty
Public bug reported: I was specifically interested in 'charm build', but kept getting this traceback regardless of arguments given: http://pastebin.ubuntu.com/23878542/ On running 'charm help' it looks like many other components are similarly affected, since they can't even run with the --description argument: http://pastebin.ubuntu.com/23878538/ ** Affects: charm-tools (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/1660004 Title: Elements of charm-tools broken under zesty To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/charm-tools/+bug/1660004/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1413401] Re: python-django-celery package is broken in Trusty
** Tags added: canonical-is -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1413401 Title: python-django-celery package is broken in Trusty To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/django-celery/+bug/1413401/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1650261] [NEW] snaps with hyphens in their names get badly-named systemd mount definitions
Public bug reported: e.g. installing the canonical-livepatch snap gives me: /etc/systemd/system/snap-canonical\x2dlivepatch-17.mount /etc/systemd/system/snap.canonical-livepatch.canonical-livepatchd.service /etc/systemd/system/multi-user.target.wants/snap-canonical\x2dlivepatch-17.mount /etc/systemd/system/multi-user.target.wants/snap.canonical-livepatch.canonical-livepatchd.service The .service files are named sensibly, but the .mount files get a '\x2d' instead of a '-'. This is particularly troublesome on hosts where /etc/ is kept in revision control, as e.g. bzr will crash on encountering these particular type of filenames. ** Affects: snapd (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/1650261 Title: snaps with hyphens in their names get badly-named systemd mount definitions To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1650261/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1641028] Re: Volume controls non-functional for Audio device: Intel Corporation Device 9d71 (rev 21)
Sorry, missed the questions in #19. This is a fresh install on a brand-new laptop, the bug has been present since the initial install and has persisted with each kernel upgrade since then. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1641028 Title: Volume controls non-functional for Audio device: Intel Corporation Device 9d71 (rev 21) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1641028/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1641028] Re: Volume controls non-functional for Audio device: Intel Corporation Device 9d71 (rev 21)
Confirmed with upstream kernel 4.9.0-040900rc5-generic #201611131431. ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed ** Tags added: kernel-bug-exists-upstream -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1641028 Title: Volume controls non-functional for Audio device: Intel Corporation Device 9d71 (rev 21) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1641028/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1641290] [NEW] [04f3:0903] Elan Microelectronics Corp fingerprint reader not recognised
Public bug reported: Running "fprint-demo" with this hardware installed reports "No devices found". This is the integrated reader in new ASUS ZenBook UX390UA laptops. lsusb -v output here: http://paste.ubuntu.com/23464942/ ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: libfprint0 1:0.6.0-2 ProcVersionSignature: Ubuntu 4.8.0-27.29-generic 4.8.1 Uname: Linux 4.8.0-27-generic x86_64 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 CurrentDesktop: Unity Date: Sat Nov 12 15:59:17 2016 InstallationDate: Installed on 2016-11-08 (3 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) SourcePackage: libfprint UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: libfprint (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug yakkety -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1641290 Title: [04f3:0903] Elan Microelectronics Corp fingerprint reader not recognised To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libfprint/+bug/1641290/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1640799] Re: lxdbr0 configuration is not obvious
Thanks, that reference was exactly what I needed - 'lxd network edit lxdbr0' was the command I was looking for. I do think it might be an idea to document that more explicitly in the package itself though, whether in the man page or elsewhere. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1640799 Title: lxdbr0 configuration is not obvious To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxd/+bug/1640799/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1641028] Re: Volume controls non-functional for Audio device: Intel Corporation Device 9d71 (rev 21)
** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1641028 Title: Volume controls non-functional for Audio device: Intel Corporation Device 9d71 (rev 21) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1641028/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1641028] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1641028/+attachment/4775783/+files/Lspci.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1641028 Title: Volume controls non-functional for Audio device: Intel Corporation Device 9d71 (rev 21) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1641028/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1641028] JournalErrors.txt
apport information ** Attachment added: "JournalErrors.txt" https://bugs.launchpad.net/bugs/1641028/+attachment/4775782/+files/JournalErrors.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1641028 Title: Volume controls non-functional for Audio device: Intel Corporation Device 9d71 (rev 21) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1641028/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1641028] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1641028/+attachment/4775784/+files/Lsusb.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1641028 Title: Volume controls non-functional for Audio device: Intel Corporation Device 9d71 (rev 21) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1641028/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1641028] RfKill.txt
apport information ** Attachment added: "RfKill.txt" https://bugs.launchpad.net/bugs/1641028/+attachment/4775790/+files/RfKill.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1641028 Title: Volume controls non-functional for Audio device: Intel Corporation Device 9d71 (rev 21) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1641028/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1641028] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1641028/+attachment/4775789/+files/PulseList.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1641028 Title: Volume controls non-functional for Audio device: Intel Corporation Device 9d71 (rev 21) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1641028/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1641028] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1641028/+attachment/4775792/+files/WifiSyslog.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1641028 Title: Volume controls non-functional for Audio device: Intel Corporation Device 9d71 (rev 21) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1641028/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1641028] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1641028/+attachment/4775786/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1641028 Title: Volume controls non-functional for Audio device: Intel Corporation Device 9d71 (rev 21) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1641028/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1641028] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1641028/+attachment/4775788/+files/ProcModules.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1641028 Title: Volume controls non-functional for Audio device: Intel Corporation Device 9d71 (rev 21) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1641028/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1641028] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1641028/+attachment/4775791/+files/UdevDb.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1641028 Title: Volume controls non-functional for Audio device: Intel Corporation Device 9d71 (rev 21) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1641028/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1641028] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1641028/+attachment/4775787/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1641028 Title: Volume controls non-functional for Audio device: Intel Corporation Device 9d71 (rev 21) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1641028/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1641028] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1641028/+attachment/4775785/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1641028 Title: Volume controls non-functional for Audio device: Intel Corporation Device 9d71 (rev 21) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1641028/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1641028] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1641028/+attachment/4775779/+files/CRDA.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1641028 Title: Volume controls non-functional for Audio device: Intel Corporation Device 9d71 (rev 21) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1641028/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1641028] Re: Volume controls non-functional for Audio device: Intel Corporation Device 9d71 (rev 21)
apport information ** Tags added: apport-collected yakkety ** Description changed: Using the latest Ubuntu 16.10 amd64 on a new ASUS ZenBook UX390UAK. $ dmesg | egrep -i 'audio|sound' [ 22.315357] snd_hda_intel :00:1f.3: bound :00:02.0 (ops i915_audio_component_bind_ops [i915]) [ 22.346209] snd_hda_codec_realtek hdaudioC0D0: autoconfig for ALC295: line_outs=2 (0x14/0x17/0x0/0x0/0x0) type:speaker [ 22.346211] snd_hda_codec_realtek hdaudioC0D0:speaker_outs=0 (0x0/0x0/0x0/0x0/0x0) [ 22.346212] snd_hda_codec_realtek hdaudioC0D0:hp_outs=1 (0x21/0x0/0x0/0x0/0x0) [ 22.346212] snd_hda_codec_realtek hdaudioC0D0:mono: mono_out=0x0 [ 22.346213] snd_hda_codec_realtek hdaudioC0D0:inputs: [ 22.346214] snd_hda_codec_realtek hdaudioC0D0: Mic=0x12 [ 22.360623] input: HDA Intel PCH Headphone as /devices/pci:00/:00:1f.3/sound/card0/input8 [ 22.360677] input: HDA Intel PCH HDMI/DP,pcm=3 as /devices/pci:00/:00:1f.3/sound/card0/input10 [ 22.360724] input: HDA Intel PCH HDMI/DP,pcm=7 as /devices/pci:00/:00:1f.3/sound/card0/input11 [ 22.360769] input: HDA Intel PCH HDMI/DP,pcm=8 as /devices/pci:00/:00:1f.3/sound/card0/input12 $ lspci | egrep -i 'audio|sound' 00:1f.3 Audio device: Intel Corporation Device 9d71 (rev 21) The onboard sound device generally works perfectly, but the volume level can only be set to 100% or mute. Using the keyboard volume control hotkeys in Unity shows the overlay and a decrease/increase in the volume indicator, but the volume remains at its maximum. The mute hotkey works fine. Same in e.g. alsamixer, I can move the Master channel volume to anything between 0 and 100 but the volume remains constantly at maximum unless I mute the channel. Individual applications with their own volume controls work fine. - Plugging in a USB headset and adjusting the volume levels for that - device works fine. + Plugging in a USB headset and adjusting the volume levels for that device works fine. + --- + ApportVersion: 2.20.3-0ubuntu8 + Architecture: amd64 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/controlC0: barryprice 4775 F pulseaudio + CurrentDesktop: Unity + DistroRelease: Ubuntu 16.10 + HibernationDevice: RESUME=UUID=a86ccfbe-7a2c-4a9d-8897-8c78f45e851d + InstallationDate: Installed on 2016-11-08 (2 days ago) + InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) + MachineType: ASUSTeK COMPUTER INC. UX390UAK + NonfreeKernelModules: zfs zunicode zcommon znvpair zavl + Package: linux (not installed) + ProcFB: 0 inteldrmfb + ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.8.0-27-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 + ProcVersionSignature: Ubuntu 4.8.0-27.29-generic 4.8.1 + RelatedPackageVersions: + linux-restricted-modules-4.8.0-27-generic N/A + linux-backports-modules-4.8.0-27-generic N/A + linux-firmware1.161 + Tags: yakkety + Uname: Linux 4.8.0-27-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo + _MarkForUpload: True + dmi.bios.date: 08/31/2016 + dmi.bios.vendor: American Megatrends Inc. + dmi.bios.version: UX390UAK.303 + dmi.board.asset.tag: ATN12345678901234567 + dmi.board.name: UX390UAK + dmi.board.vendor: ASUSTeK COMPUTER INC. + dmi.board.version: 1.0 + dmi.chassis.asset.tag: No Asset Tag + dmi.chassis.type: 10 + dmi.chassis.vendor: ASUSTeK COMPUTER INC. + dmi.chassis.version: 1.0 + dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX390UAK.303:bd08/31/2016:svnASUSTeKCOMPUTERINC.:pnUX390UAK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX390UAK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: + dmi.product.name: UX390UAK + dmi.product.version: 1.0 + dmi.sys.vendor: ASUSTeK COMPUTER INC. ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1641028/+attachment/4775778/+files/AlsaInfo.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1641028 Title: Volume controls non-functional for Audio device: Intel Corporation Device 9d71 (rev 21) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1641028/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1641028] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1641028/+attachment/4775780/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1641028 Title: Volume controls non-functional for Audio device: Intel Corporation Device 9d71 (rev 21) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1641028/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1641028] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1641028/+attachment/4775781/+files/IwConfig.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1641028 Title: Volume controls non-functional for Audio device: Intel Corporation Device 9d71 (rev 21) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1641028/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1641028] [NEW] Volume controls non-functional for Audio device: Intel Corporation Device 9d71 (rev 21)
Public bug reported: Using the latest Ubuntu 16.10 amd64 on a new ASUS ZenBook UX390UAK. $ dmesg | egrep -i 'audio|sound' [ 22.315357] snd_hda_intel :00:1f.3: bound :00:02.0 (ops i915_audio_component_bind_ops [i915]) [ 22.346209] snd_hda_codec_realtek hdaudioC0D0: autoconfig for ALC295: line_outs=2 (0x14/0x17/0x0/0x0/0x0) type:speaker [ 22.346211] snd_hda_codec_realtek hdaudioC0D0:speaker_outs=0 (0x0/0x0/0x0/0x0/0x0) [ 22.346212] snd_hda_codec_realtek hdaudioC0D0:hp_outs=1 (0x21/0x0/0x0/0x0/0x0) [ 22.346212] snd_hda_codec_realtek hdaudioC0D0:mono: mono_out=0x0 [ 22.346213] snd_hda_codec_realtek hdaudioC0D0:inputs: [ 22.346214] snd_hda_codec_realtek hdaudioC0D0: Mic=0x12 [ 22.360623] input: HDA Intel PCH Headphone as /devices/pci:00/:00:1f.3/sound/card0/input8 [ 22.360677] input: HDA Intel PCH HDMI/DP,pcm=3 as /devices/pci:00/:00:1f.3/sound/card0/input10 [ 22.360724] input: HDA Intel PCH HDMI/DP,pcm=7 as /devices/pci:00/:00:1f.3/sound/card0/input11 [ 22.360769] input: HDA Intel PCH HDMI/DP,pcm=8 as /devices/pci:00/:00:1f.3/sound/card0/input12 $ lspci | egrep -i 'audio|sound' 00:1f.3 Audio device: Intel Corporation Device 9d71 (rev 21) The onboard sound device generally works perfectly, but the volume level can only be set to 100% or mute. Using the keyboard volume control hotkeys in Unity shows the overlay and a decrease/increase in the volume indicator, but the volume remains at its maximum. The mute hotkey works fine. Same in e.g. alsamixer, I can move the Master channel volume to anything between 0 and 100 but the volume remains constantly at maximum unless I mute the channel. Individual applications with their own volume controls work fine. Plugging in a USB headset and adjusting the volume levels for that device works fine. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Attachment added: "version.log" https://bugs.launchpad.net/bugs/1641028/+attachment/4775753/+files/version.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1641028 Title: Volume controls non-functional for Audio device: Intel Corporation Device 9d71 (rev 21) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1641028/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1641028] Re: Volume controls non-functional for Audio device: Intel Corporation Device 9d71 (rev 21)
** Attachment added: "lspci-vnvn.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1641028/+attachment/4775754/+files/lspci-vnvn.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1641028 Title: Volume controls non-functional for Audio device: Intel Corporation Device 9d71 (rev 21) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1641028/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1640799] [NEW] lxdbr0 configuration is not obvious
Public bug reported: It looks like the ability to configure lxdbr0 via /etc/default/lxd- bridge went away with release 2.3. LXD's automatic setup assigned a CIDR range that already exists on my network, so I'd like to reconfigure it to use a different range. All online documentation seems to refer to the non-existent /etc/default /lxd-bridge - it's unclear to me how I'm supposed to configure things here. I've seen a number of suggestions to run "sudo dpkg-reconfigure -p medium lxd", but this now does nothing, as does "sudo dpkg-reconfigure -p low lxd". Running "sudo lxd init" gives me the option to configure a new bridge, but not to reconfigure the existing one. I'm running the latest Yakkety on amd64, fully updated. $ dpkg -l | grep lxd ii lxd 2.4.1-0ubuntu1 amd64Container hypervisor based on LXC - daemon ii lxd-client 2.4.1-0ubuntu1 amd64Container hypervisor based on LXC - client ** Affects: lxd (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/1640799 Title: lxdbr0 configuration is not obvious To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxd/+bug/1640799/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1392317] Re: Incorrect order of messages with RepeatedMsgReduction on
** Tags added: canonical-is -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1392317 Title: Incorrect order of messages with RepeatedMsgReduction on To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/1392317/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1629766] [NEW] Syntax error in /usr/lib/lxd/upgrade-bridge
Public bug reported: Version 2.3-0ubuntu5 of the lxd package in yakkety contains a typo in a script, which breaks package installation: Setting up lxd (2.3-0ubuntu5) ... Installing new version of config file /etc/init.d/lxd ... Installing new version of config file /etc/init/lxd.conf ... Old bridge configuration detected in /etc/default/lxd-bridge, upgrading Unsetting deprecated profile options Attempting to kill current lxd-bridge /usr/lib/lxd/upgrade-bridge: 58: kill: No such process Bringing down and renaming existing bridge lxdbr0 to lxd-upgrade Creating a new LXD bridge /usr/lib/lxd/upgrade-bridge: 147: /usr/lib/lxd/upgrade-bridge: Syntax error: end of file unexpected (expecting "fi") dpkg: error processing package lxd (--configure): subprocess installed post-installation script returned error exit status 2 On closer inspection, there's an extra "t" on line 93, "fit" instead of "fi". Manually correcting this line and running "sudo apt-get install -f" solves the problem: http://pastebin.ubuntu.com/23268764/ ** Affects: lxd (Ubuntu) Importance: Undecided Status: New ** Description changed: - Version 2.3-0ubuntu5 of the lxd package in yakkety contains a typo, - which breaks package installation: + Version 2.3-0ubuntu5 of the lxd package in yakkety contains a typo in a + script, which breaks package installation: Setting up lxd (2.3-0ubuntu5) ... Installing new version of config file /etc/init.d/lxd ... Installing new version of config file /etc/init/lxd.conf ... Old bridge configuration detected in /etc/default/lxd-bridge, upgrading Unsetting deprecated profile options Attempting to kill current lxd-bridge /usr/lib/lxd/upgrade-bridge: 58: kill: No such process Bringing down and renaming existing bridge lxdbr0 to lxd-upgrade Creating a new LXD bridge /usr/lib/lxd/upgrade-bridge: 147: /usr/lib/lxd/upgrade-bridge: Syntax error: end of file unexpected (expecting "fi") dpkg: error processing package lxd (--configure): - subprocess installed post-installation script returned error exit status 2 + subprocess installed post-installation script returned error exit status 2 On closer inspection, there's an extra "t" on line 93, "fit" instead of "fi". Manually correcting this line and running "sudo apt-get install -f" solves the problem: http://pastebin.ubuntu.com/23268764/ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1629766 Title: Syntax error in /usr/lib/lxd/upgrade-bridge To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxd/+bug/1629766/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1512185] Re: qemu-nbd on ARM64 deadlock? Stuck in rt_sigtimedwait([BUS ALRM IO], ..) and futex(0x7f749ec230, FUTEX_WAIT, ...)
Hi Joseph, Happy to test upstream kernels, but this setup requires a 64-bit native arm64/aarch64 kernel, which I can't see at the link provided - only 32-bit armhf kernels. Currently we're running the kernel from the linux-generic-lts-wily package: Linux swirlix18 4.2.0-16-generic #19~14.04.1-Ubuntu SMP Thu Oct 8 15:36:19 UTC 2015 aarch64 aarch64 aarch64 GNU/Linux If you know where we can find an appropriate mainline kernel, we can get it tested. Thanks. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1512185 Title: qemu-nbd on ARM64 deadlock? Stuck in rt_sigtimedwait([BUS ALRM IO], ..) and futex(0x7f749ec230, FUTEX_WAIT, ...) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1512185/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1059030] [NEW] HTML entity encoding bugs
Public bug reported: The web interface in transmission-daemon now shows the bare character strings "↑" and "↓" instead of the appropriate HTML entities, since the latest update in Ubuntu 12.04 LTS. ** Affects: transmission (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/1059030 Title: HTML entity encoding bugs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/transmission/+bug/1059030/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs