[Bug 1964814] Re: linux-firmware fails to upgrade to 20220314.gitcd01f857-0ubuntu1
** Changed in: linux-firmware (Ubuntu Jammy) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1964814 Title: linux-firmware fails to upgrade to 20220314.gitcd01f857-0ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1964814/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1962225] Re: preinst check that kernel revision < 255 now does more harm than good
Same on Ubuntu 20.04.4 LTS on arm64 $ sudo apt-get --fix-broken install Reading package lists... Done Building dependency tree Reading state information... Done Correcting dependencies... Done The following additional packages will be installed: libc6 Suggested packages: glibc-doc The following packages will be upgraded: libc6 1 upgraded, 0 newly installed, 0 to remove and 6 not upgraded. 1 not fully installed or removed. Need to get 0 B/2266 kB of archives. After this operation, 7168 B disk space will be freed. Do you want to continue? [Y/n] y Preconfiguring packages ... (Reading database ... 102158 files and directories currently installed.) Preparing to unpack .../libc6_2.31-0ubuntu9.7_arm64.deb ... ERROR: Your kernel version indicates a revision number of 255 or greater. Glibc has a number of built in assumptions that this revision number is less than 255. If you\'ve built your own kernel, please make sure that any custom version numbers are appended to the upstream kernel number with a dash or some other delimiter. dpkg: error processing archive /var/cache/apt/archives/libc6_2.31-0ubuntu9.7_arm64.deb (--unpack): new libc6:arm64 package pre-installation script subprocess returned error exit status 1 Errors were encountered while processing: /var/cache/apt/archives/libc6_2.31-0ubuntu9.7_arm64.deb E: Sub-process /usr/bin/dpkg returned an error code (1) $ uname -a Linux k2 4.9.277-82 #1 SMP PREEMPT Fri Feb 18 14:35:13 UTC 2022 aarch64 aarch64 aarch64 GNU/Linux $ cat /etc/lsb-release DISTRIB_ID=Ubuntu DISTRIB_RELEASE=20.04 DISTRIB_CODENAME=focal DISTRIB_DESCRIPTION="Ubuntu 20.04.4 LTS" -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1962225 Title: preinst check that kernel revision < 255 now does more harm than good To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1962225/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 225361] Re: .gvfs can't be stat'd by root causing backup tools to fail
.gvfs can't be removed on a 18.04-equivalent OS. $ sudo rm -rf .gvfs [sudo] password for me: rm: cannot remove '.gvfs': Device or resource busy $ uname -a Linux me 4.15.0-54-lowlatency #58-Ubuntu SMP PREEMPT Mon Jun 24 11:45:10 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux $ cat /etc/lsb-release DISTRIB_ID=LinuxMint DISTRIB_RELEASE=19.2 DISTRIB_CODENAME=tina DISTRIB_DESCRIPTION="Linux Mint 19.2 Tina" -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/225361 Title: .gvfs can't be stat'd by root causing backup tools to fail To manage notifications about this bug go to: https://bugs.launchpad.net/gvfs/+bug/225361/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1769335] Re: PC won't boot with latest intel-microcode
I lost sudoer rights after upgrades this week (it's been a while since I rebooted so I can't know what else was upgraded since the previous rebot). $ apt-cache policy intel-microcode intel-microcode: Installed: 3.20180425.1~ubuntu0.16.04.2 Candidate: 3.20180425.1~ubuntu0.16.04.2 Version table: *** 3.20180425.1~ubuntu0.16.04.2 500 500 http://tw.archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages 100 /var/lib/dpkg/status 3.20180425.1~ubuntu0.16.04.1 500 500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 Packages 3.20151106.1 500 500 http://tw.archive.ubuntu.com/ubuntu xenial/restricted amd64 Packages $ uname -a Linux my-os 4.13.0-39-generic #44~16.04.1-Ubuntu SMP Thu Apr 5 16:43:10 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1769335 Title: PC won't boot with latest intel-microcode To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/intel-microcode/+bug/1769335/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1743302] Re: wrong paths in systemd units
Not seeing this problem now, with FSAL VFS it does start (but then it stops due to issues binding to IPV6 interfaces for which there's a fix in upstream). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1743302 Title: wrong paths in systemd units To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nfs-ganesha/+bug/1743302/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1743302] Re: wrong paths in systemd units
Sorry about the spam - I just noticed you saw that on shutdown. Mine can't even start so I don't know whether the problem exists on my system. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1743302 Title: wrong paths in systemd units To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nfs-ganesha/+bug/1743302/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1760391] Re: package acpid 1:2.0.28-1ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
1) Bionic x86_64 (also with Virtualbox) 2) Didn't see any ACPI errors for 2 weeks, until today. 3) Yesterday I enabled Intel Corporation Ethernet Server Adapter I350-T2 which I had in the system, but not configured. Don't know if that could be related or some unrelated package update. I uninstalled acpid to get rid of dependency issues so at least I can start services that depend on acpid. But my system falls asleep very quickly now; I probably need to disable OS power saving. acpid-related system log: May 10 11:51:55 server systemd[1]: acpid.socket: Socket unit configuration has changed while unit has been running, no open socket file descriptor left. The socket unit is not functional until restarted. May 10 11:51:55 server kernel: [ 3129.814826] systemd[1]: avahi-daemon.socket: Socket unit configuration has changed while unit has been running, no open socket file descriptor left. The socket unit is not functional until restarted. May 10 11:51:55 server systemd[1]: acpid.service: Got no socket. May 10 11:51:55 server systemd[1]: acpid.service: Failed to run 'start' task: Invalid argument May 10 11:51:55 server systemd[1]: acpid.service: Failed with result 'resources'. May 10 11:51:55 server systemd[1]: Failed to start ACPI event daemon. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1760391 Title: package acpid 1:2.0.28-1ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/acpid/+bug/1760391/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1686107] Re: Latest kernel update gets stuck
Same here, hosed 17.10 after kernel update to 4.13.0.19. I have LUKS and I can’t boot to see the password prompt. I can only boot back if I choose recovery mode, either with 0.19 or 0.17. Now I removed the both of these and installed an older version (0.16), still the same problem. Related: https://bugs.launchpad.net/ubuntu/xenial/+source/plymouth/+bug/1359689 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1686107 Title: Latest kernel update gets stuck To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1686107/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1359689] Re: cryptsetup password prompt not shown
Same as Moppers, on Artful and can't see LUKS prompt. Only recovery mode lets me access data and my 2nd display cannot work. Earlier today I booted with LUKS just fine, but after suspend I got a black screen on both displays and couldn't recover. After I power cycled it, now I can see LUKS prompt only with recovery mode. I've tried to boot with 4.13.0-16-generic, 4.13.0-17-generic, 4.13.0-19-generic, all have the same problem (blank screen). Now I enabled "proposed" updates to see whether that helps. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1359689 Title: cryptsetup password prompt not shown To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1359689/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1631241] Re: Name resolution stops working after resume from suspend
*** This bug is a duplicate of bug 1639776 *** https://bugs.launchpad.net/bugs/1639776 Also in artful. bug #1639776 is marked as "fixed" which is fake news. The the other guy above, I often see this after disconnecting from VPN (Cisco AnyConnect). My version: dnsmasq/artful,artful 2.78-1 I installed dnscrypt-proxy, checked the IP in /etc/dnscrypt-proxy /dnscrypt-proxy.conf and set the system to use that IP. We'll see if that helps. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1631241 Title: Name resolution stops working after resume from suspend To manage notifications about this bug go to: https://bugs.launchpad.net/dnsmasq/+bug/1631241/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1683747] Re: libvirtError: unsupported configuration: unknown input device type 'virtio1.0-input' (fixed upstream)
** Description changed:
1. Zesty 17.04, x86-64
2. Use virt-manager to attempt to install a VM from Debian ISO (for example
debian-testing-amd64-xfce-CD-1.iso, debian-stretch-DI-rc2-amd64-netinst.iso). I
don't get this problem with Ubuntu ISOs.
-
```
Unable to complete install: 'unsupported configuration: unknown input device
type 'virtio1.0-input''
Traceback (most recent call last):
- File "/usr/share/virt-manager/virtManager/asyncjob.py", line 90, in
cb_wrapper
- callback(asyncjob, *args, **kwargs)
- File "/usr/share/virt-manager/virtManager/create.py", line 2277, in
_do_async_install
- guest.start_install(meter=meter)
- File "/usr/share/virt-manager/virtinst/guest.py", line 501, in start_install
- noboot)
- File "/usr/share/virt-manager/virtinst/guest.py", line 416, in _create_guest
- dom = self.conn.createLinux(start_xml or final_xml, 0)
- File "/usr/lib/python2.7/dist-packages/libvirt.py", line 3491, in
createLinux
- if ret is None:raise libvirtError('virDomainCreateLinux() failed',
conn=self)
+ File "/usr/share/virt-manager/virtManager/asyncjob.py", line 90, in
cb_wrapper
+ callback(asyncjob, *args, **kwargs)
+ File "/usr/share/virt-manager/virtManager/create.py", line 2277, in
_do_async_install
+ guest.start_install(meter=meter)
+ File "/usr/share/virt-manager/virtinst/guest.py", line 501, in start_install
+ noboot)
+ File "/usr/share/virt-manager/virtinst/guest.py", line 416, in _create_guest
+ dom = self.conn.createLinux(start_xml or final_xml, 0)
+ File "/usr/lib/python2.7/dist-packages/libvirt.py", line 3491, in
createLinux
+ if ret is None:raise libvirtError('virDomainCreateLinux() failed',
conn=self)
libvirtError: unsupported configuration: unknown input device type
'virtio1.0-input'
```
- This has been fixed upstream.
+ This has been fixed upstream.
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=846356
+
+ Edit: Did some more digging and just noticed there's an update pending here.
I wonder if it includes fixes for this issue. It'd be good if it did.
+ https://bugs.launchpad.net/ubuntu/+source/virt-manager/+bug/1667114
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1683747
Title:
libvirtError: unsupported configuration: unknown input device type
'virtio1.0-input' (fixed upstream)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/virt-manager/+bug/1683747/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1683747] [NEW] libvirtError: unsupported configuration: unknown input device type 'virtio1.0-input' (fixed upstream)
Public bug reported:
1. Zesty 17.04, x86-64
2. Use virt-manager to attempt to install a VM from Debian ISO (for example
debian-testing-amd64-xfce-CD-1.iso, debian-stretch-DI-rc2-amd64-netinst.iso). I
don't get this problem with Ubuntu ISOs.
```
Unable to complete install: 'unsupported configuration: unknown input device
type 'virtio1.0-input''
Traceback (most recent call last):
File "/usr/share/virt-manager/virtManager/asyncjob.py", line 90, in cb_wrapper
callback(asyncjob, *args, **kwargs)
File "/usr/share/virt-manager/virtManager/create.py", line 2277, in
_do_async_install
guest.start_install(meter=meter)
File "/usr/share/virt-manager/virtinst/guest.py", line 501, in start_install
noboot)
File "/usr/share/virt-manager/virtinst/guest.py", line 416, in _create_guest
dom = self.conn.createLinux(start_xml or final_xml, 0)
File "/usr/lib/python2.7/dist-packages/libvirt.py", line 3491, in createLinux
if ret is None:raise libvirtError('virDomainCreateLinux() failed',
conn=self)
libvirtError: unsupported configuration: unknown input device type
'virtio1.0-input'
```
This has been fixed upstream.
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=846356
** Affects: virt-manager (Ubuntu)
Importance: Undecided
Status: New
** Tags: libvirt virtio1.0-input zesty
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1683747
Title:
libvirtError: unsupported configuration: unknown input device type
'virtio1.0-input' (fixed upstream)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/virt-manager/+bug/1683747/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1576849] Re: dependency mixup of gnuplot and gnuplot5
Not only that, it also runs v5, so it's even worse than just a dependency mix-up. My Xenial version (as of March 2017): Linux ubuntu 4.4.0-66-generic #87-Ubuntu SMP Fri Mar 3 15:29:05 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux Repo info is wrong: gnuplot: Installed: 4.6.6-3 Candidate: 4.6.6-3 And the package is wrong: user@ubuntu:~/data$ which gnuplot5 /usr/bin/gnuplot5 user@ubuntu:~/data$ which gnuplot /usr/bin/gnuplot user@ubuntu:~/data$ gnuplot G N U P L O T Version 5.0 patchlevel 3last modified 2016-02-21 <=== v5.0 started Copyright (C) 1986-1993, 1998, 2004, 2007-2016 Thomas Williams, Colin Kelley and many others gnuplot home: http://www.gnuplot.info faq, bugs, etc: type "help FAQ" immediate help: type "help" (plot window: hit 'h') Terminal type set to 'qt' -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1576849 Title: dependency mixup of gnuplot and gnuplot5 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnuplot/+bug/1576849/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1605053] [NEW] collectl install hangs in colplot setup stage
Public bug reported: * Ubuntu 16.04 x64 (and I've seen this on 14.04 x64 as well) * collectl 4.0.4-1 * colplot 5.0.1-3 $ sudo apt-get install collectl -y - Select lighttpd ... Setting up colplot (5.0.1-3) ... * This is where apt-get install hangs and can't be interrupted with CTRL+C. * Upon system restart, apt-get install doesn't work with other packages either: ... subprocess installed post-installation script was interrupted Errors were encountered while processing: colplot $ ^C $ sudo dpkg --configure -a Setting up colplot (5.0.1-3) ... * It hangs again (but this command can be interrupted); I remove the two packages with dpkg in order to continue * Installing collectl with no colplot (i.e. select "none") Web server integration options) works fine ** Affects: collectl (Ubuntu) Importance: Undecided Status: New ** Tags: colplot ** Description changed: * Ubuntu 16.04 x64 (and I've seen this on 14.04 x64 as well) * collectl 4.0.4-1 * colplot 5.0.1-3 $ sudo apt-get install collectl -y - Select lighttpd ... Setting up colplot (5.0.1-3) ... - * This is where apt-get install hangs. Upon force reboot: - * Upon reboot, apt-get install doesn't work with other packages either: + * This is where apt-get install hangs and can't be interrupted with CTRL+C. + * Upon system restart, apt-get install doesn't work with other packages either: ... - subprocess installed post-installation script was interrupted + subprocess installed post-installation script was interrupted Errors were encountered while processing: - colplot + colplot $ ^C $ sudo dpkg --configure -a Setting up colplot (5.0.1-3) ... - * It hangs again (but this command can be interrupted) - * Installing with no colplot (i.e. select "none" in Web server integration options) works fine + * It hangs again (but this command can be interrupted); I remove the two packages with dpkg in order to continue + * Installing collectl with no colplot (i.e. select "none") Web server integration options) works fine -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1605053 Title: collectl install hangs in colplot setup stage To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/collectl/+bug/1605053/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1306991] Re: pip stops with ImportError for request-Modul
Ugh, no way to edit comments... Above, I moved requests to requests.old. I also have requests-2.4.2.dist-info is not causing this problem, so I moved that back (which is the last line above). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1306991 Title: pip stops with ImportError for request-Modul To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-pip/+bug/1306991/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1306991] Re: pip stops with ImportError for request-Modul
With Python 3.4 and pip3, this is what worked for me: cd /usr/local/lib/python3.4/dist-packages sudo mv requests-2.4.2.dist-info.old requests-2.4.2.dist-info -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1306991 Title: pip stops with ImportError for request-Modul To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-pip/+bug/1306991/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1396536] Re: lxc_start - Exec format error - failed to exec /sbin/init
No my arch is amd64, that's why I specified "-a armhf". I know about qemu (I wasn't sure whether to use static or binfmt), but errors should be meaningful, instead it seems as if lxc is working fine, but in fact it's not. Obviously it's not a matter of permissions, so the error is wrong. The image I used is downloaded from debian.org, so I didn't prepare it myself. Either non-armhf hosts shouldn't list armhf images or should warn (maybe in documentation, if not in code) that those aren't usable without additional packages. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1396536 Title: lxc_start - Exec format error - failed to exec /sbin/init To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1396536/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1396536] Re: lxc_start - Exec format error - failed to exec /sbin/init
$ sudo file /var/lib/lxc/u1/rootfs/sbin/upstart /var/lib/lxc/u1/rootfs/sbin/upstart: ELF 32-bit LSB shared object, ARM, EABI5 version 1 (SYSV), dynamically linked (uses shared libs), for GNU/Linux 2.6.32, BuildID[sha1]=401fd3761e2edac12fc6081bebbfd834a985e11b, stripped -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1396536 Title: lxc_start - Exec format error - failed to exec /sbin/init To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1396536/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1396536] Re: lxc_start - Exec format error - failed to exec /sbin/init
$ sudo ls -lisa /var/lib/lxc/u1/rootfs/sbin/init 541928 0 lrwxrwxrwx 1 root root 7 Nov 19 23:17 /var/lib/lxc/u1/rootfs/sbin/init -> upstart $ sudo ls -lisa /var/lib/lxc/u1/rootfs/sbin/upstart 541969 220 -rwxr-xr-x 1 root root 223596 Nov 19 23:17 /var/lib/lxc/u1/rootfs/sbin/upstart -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1396536 Title: lxc_start - Exec format error - failed to exec /sbin/init To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1396536/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1396536] [NEW] lxc_start - Exec format error - failed to exec /sbin/init
Public bug reported: I have an up to date Ubuntu 14.04. I followed the guide at https://help.ubuntu.com/lts/serverguide/lxc.html sudo apt-get install lxc && sudo lxc-create --template download --name u1 - Choose ubuntu-vivid-armhf, then: sudo lxc-start --name u1 --daemon lxc-start 1416996721.249 INFO lxc_apparmor - changed apparmor profile to lxc-container-default lxc-start 1416996721.249 NOTICE lxc_start - exec'ing '/sbin/init' lxc-start 1416996721.253 ERRORlxc_start - Exec format error - failed to exec /sbin/init lxc- $ sudo lxc-ls --fancy NAME STATEIPV4 IPV6 AUTOSTART u1STOPPED - - NO $ sudo lxc-checkconfig Kernel configuration not found at /proc/config.gz; searching... Kernel configuration found at /boot/config-3.13.0-24-generic --- Namespaces --- Namespaces: enabled Utsname namespace: enabled Ipc namespace: enabled Pid namespace: enabled User namespace: enabled Network namespace: enabled Multiple /dev/pts instances: enabled --- Control groups --- Cgroup: enabled Cgroup clone_children flag: enabled Cgroup device: enabled Cgroup sched: enabled Cgroup cpu account: enabled Cgroup memory controller: enabled Cgroup cpuset: enabled --- Misc --- Veth pair device: enabled Macvlan: enabled Vlan: enabled File capabilities: enabled Note : Before booting a new kernel, you can check its configuration usage : CONFIG=/path/to/config /usr/bin/lxc-checkconfig Except apt-get update and apt-get upgrade I didn't install any other packages (okay, I installed vim and git). ** Affects: lxc (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/1396536 Title: lxc_start - Exec format error - failed to exec /sbin/init To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1396536/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1396536] Re: lxc_start - Exec format error - failed to exec /sbin/init
In case it wasn't clear I followed instructions for "basic privileged usage". not user namespaces. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1396536 Title: lxc_start - Exec format error - failed to exec /sbin/init To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1396536/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
