** 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.git
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 f
.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-r
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 tab
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/
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
Tit
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 uninstal
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
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
*** 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
** 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: 'unsup
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 configur
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
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 sy
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 U
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/bu
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 im
$ 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
$ 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 receiv
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 14169
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
21 matches
Mail list logo
