Public bug reported:
I encountered a problem contacting mirror admin team through e-mail
mirr...@ubuntu.com.
The issue I want to discuss is that I have set up both archive and
release mirror. Archive mirror has gained offical status immediately,
but there was a problem on release mirror with HEAD
Public bug reported:
The driver keeps reporting all DFS-dependant channels as disabled
despite the correct regdomain is set in CRDA:
root@mamut:/home/patty# iw reg get
global
country CZ: DFS-ETSI
(2400 - 2483 @ 40), (N/A, 20), (N/A)
(5150 - 5250 @ 80), (N/A, 23), (N/A), NO-OUTDOOR
It is Artful... Sorry!
brill@tapir:~$ dpkg -l | grep ecrypt
ii ecryptfs-utils 111-0ubuntu4
amd64ecryptfs cryptographic filesystem (utilities)
ii libecryptfs1 111-0ubuntu4
Public bug reported:
The resulting package that came from cross-compilation of current master
kernel (4.10-rc4+ or more precisely:
0aa0313f9d576affd7747cc3f179feb097d28990) using this command:
make-kpkg --rootcmd fakeroot --arch arm --cross-compile arm-linux-
gnueabihf- --revision=1.0 kernel_imag
Angelo, it seems to me that Mike meant his branch lp:~mcfletch/eric
/update-to-4.5.13 which is perhaps misplaced in the Eric project instead
of Ubuntu package for Eric. I have tested it and it looks OK. Is there
any possibility of pulling his work here, review it and merge if
possible? (May I help
Public bug reported:
I have Eoan hypervisor connected to a Ceph (14.2.2) cluster. There is a
problem with listing and using the rbd volumes. Only one volume is
listed by libvirt functions regardless of how many of them are in the
corresponding pool.
I.e. for my pool called "core":
th@lab02:~$ su
Public bug reported:
When I try to create a new volume in Ceph RBD pool using virt-manager
over eoan server with libvirt I get the following error:
Error creating vol: Couldn't create storage volume 'vol': 'unsupported
configuration: only RAW volumes are supported by this storage pool'
Traceback
Public bug reported:
After upgrading to Jammy I encountered the errors caused by the bundled
plugins TrimeshReader and AMFReader. The first is probably caused by the
missing trimesh PIP package.
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: cura 4.13.0-1
ProcVersionSignature: Ubuntu 5.15.