[Bug 1960650] [NEW] Bundled plugins TrimeshReader and AMDReader fail
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.0-18.18-generic 5.15.12 Uname: Linux 5.15.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu76 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Feb 11 17:06:58 2022 InstallationDate: Installed on 2020-10-23 (476 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Beta amd64 (20200930) PackageArchitecture: all RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: cura UpgradeStatus: Upgraded to jammy on 2022-01-30 (12 days ago) ** Affects: cura (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy uec-images wayland-session ** Attachment added: "console output" https://bugs.launchpad.net/bugs/1960650/+attachment/5560408/+files/cura.out.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1960650 Title: Bundled plugins TrimeshReader and AMDReader fail To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cura/+bug/1960650/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1869729] [NEW] DFS is not enabled, majority of 5GHz channels are not accessible
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, AUTO-BW (5250 - 5350 @ 80), (N/A, 20), (0 ms), NO-OUTDOOR, DFS, AUTO-BW (5470 - 5725 @ 160), (N/A, 26), (0 ms), DFS (57000 - 66000 @ 2160), (N/A, 40), (N/A) root@mamut:/home/patty# iw list Wiphy phy0 max # scan SSIDs: 9 max scan IEs length: 2304 bytes max # sched scan SSIDs: 0 max # match sets: 0 max # scan plans: 1 max scan plan interval: -1 max scan plan iterations: 0 Retry short limit: 7 Retry long limit: 4 Coverage class: 0 (up to 0m) Supported Ciphers: * WEP40 (00-0f-ac:1) * WEP104 (00-0f-ac:5) * TKIP (00-0f-ac:2) * CCMP-128 (00-0f-ac:4) Available Antennas: TX 0 RX 0 Supported interface modes: * IBSS * managed * AP Band 1: Capabilities: 0x1962 HT20/HT40 Static SM Power Save RX HT20 SGI RX HT40 SGI RX STBC 1-stream Max AMSDU length: 7935 bytes DSSS/CCK HT40 Maximum RX AMPDU length 65535 bytes (exponent: 0x003) Minimum RX AMPDU time spacing: 16 usec (0x07) HT Max RX data rate: 150 Mbps HT TX/RX MCS rate indexes supported: 0-7 Bitrates (non-HT): * 1.0 Mbps * 2.0 Mbps * 5.5 Mbps * 11.0 Mbps * 6.0 Mbps * 9.0 Mbps * 12.0 Mbps * 18.0 Mbps * 24.0 Mbps * 36.0 Mbps * 48.0 Mbps * 54.0 Mbps Frequencies: * 2412 MHz [1] (20.0 dBm) * 2417 MHz [2] (20.0 dBm) * 2422 MHz [3] (20.0 dBm) * 2427 MHz [4] (20.0 dBm) * 2432 MHz [5] (20.0 dBm) * 2437 MHz [6] (20.0 dBm) * 2442 MHz [7] (20.0 dBm) * 2447 MHz [8] (20.0 dBm) * 2452 MHz [9] (20.0 dBm) * 2457 MHz [10] (20.0 dBm) * 2462 MHz [11] (20.0 dBm) * 2467 MHz [12] (20.0 dBm) * 2472 MHz [13] (20.0 dBm) * 2484 MHz [14] (disabled) Band 2: Capabilities: 0x1862 HT20/HT40 Static SM Power Save RX HT20 SGI RX HT40 SGI No RX STBC Max AMSDU length: 7935 bytes DSSS/CCK HT40 Maximum RX AMPDU length 65535 bytes (exponent: 0x003) Minimum RX AMPDU time spacing: 16 usec (0x07) HT Max RX data rate: 150 Mbps HT TX/RX MCS rate indexes supported: 0-7 VHT Capabilities (0x03c00120): Max MPDU length: 3895 Supported Channel Width: neither 160 nor 80+80 short GI (80 MHz) +HTC-VHT VHT RX MCS set: 1 streams: MCS 0-9 2 streams: not supported 3 streams: not supported 4 streams: not supported 5 streams: not supported 6 streams: not supported 7 streams: not supported 8 streams: not supported VHT RX highest supported: 434 Mbps VHT TX MCS set: 1 streams: MCS 0-9 2 streams: not supported 3 streams: not supported 4 streams: not supported 5 streams: not supported 6 streams: not supported 7 streams: not supported 8 streams: not supported VHT TX highest supported: 434 Mbps Bitrates (non-HT): * 6.0 Mbps * 9.0 Mbps * 12.0 Mbps * 18.0 Mbps * 24.0 Mbps * 36.0 Mbps * 48.0 Mbps * 54.0
[Bug 1859253] [NEW] rbd driver fails to create a new volume
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 (most recent call last):
File "/usr/share/virt-manager/virtinst/storage.py", line 682, in install
vol = self.pool.createXML(xml, createflags)
File "/usr/lib/python3/dist-packages/libvirt.py", line 3220, in createXML
if ret is None:raise libvirtError('virStorageVolCreateXML() failed',
pool=self)
libvirt.libvirtError: unsupported configuration: only RAW volumes are supported
by this storage pool
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/usr/share/virt-manager/virtManager/asyncjob.py", line 75, in cb_wrapper
callback(asyncjob, *args, **kwargs)
File "/usr/share/virt-manager/virtManager/createvol.py", line 339, in
_async_vol_create
vol.install(meter=meter)
File "/usr/share/virt-manager/virtinst/storage.py", line 692, in install
"'%s': '%s'" % (self.name, str(e)))
RuntimeError: Couldn't create storage volume 'vol': 'unsupported configuration:
only RAW volumes are supported by this storage pool'
It is likely known bug that is already fixed in upstream:
https://bugzilla.redhat.com/show_bug.cgi?id=1724065
** Affects: libvirt (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/1859253
Title:
rbd driver fails to create a new volume
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1859253/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1858341] [NEW] rbd driver does not list all volumes in pool
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:~$ sudo virsh vol-list core NamePath - kocka core/kocka th@lab02:~$ sudo rbd ls core kocka taz The bug is apparently known and already fixed in upstream: https://github.com/libvirt/libvirt/commit/9b7c4048fa0559fd81d57b7f7d13b1dccd6a99b2 ** Affects: libvirt (Ubuntu) Importance: Undecided Status: New ** Description changed: 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 caled "core": + I.e. for my pool called "core": th@lab02:~$ sudo virsh vol-list core - NamePath + NamePath - - kocka core/kocka - + kocka core/kocka th@lab02:~$ sudo rbd ls core kocka taz The problem is apparently known and fixed in upstream: https://github.com/libvirt/libvirt/commit/9b7c4048fa0559fd81d57b7f7d13b1dccd6a99b2 ** Description changed: 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:~$ sudo virsh vol-list core NamePath - kocka core/kocka th@lab02:~$ sudo rbd ls core kocka taz - The problem is apparently known and fixed in upstream: + The bug is apparently known and already fixed in upstream: https://github.com/libvirt/libvirt/commit/9b7c4048fa0559fd81d57b7f7d13b1dccd6a99b2 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1858341 Title: rbd driver does not list all volumes in pool To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1858341/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1718658] Re: ecryptfs-mount-private fails to initialize ecryptfs keys
It is Artful... Sorry! brill@tapir:~$ dpkg -l | grep ecrypt ii ecryptfs-utils 111-0ubuntu4 amd64ecryptfs cryptographic filesystem (utilities) ii libecryptfs1 111-0ubuntu4 amd64ecryptfs cryptographic filesystem (library) brill@tapir:~$ uname -a Linux tapir 4.13.0-11-generic #12-Ubuntu SMP Tue Sep 12 16:03:57 UTC 2017 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/1718658 Title: ecryptfs-mount-private fails to initialize ecryptfs keys To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ecryptfs-utils/+bug/1718658/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1658756] [NEW] Cross-compiled kernel package contains host binaries
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_image kernel_headers contained files in /usr/src/linux-headers-/scripts/mod/ that have been compiled for the host architecture, not for the target one. It complicates building new modules with the libraries. There were many x86_64 binaries, so here is only and example from my test: root@turris:~# file /usr/src/linux-headers-4.10.0-rc4+/scripts/mod/modpost /usr/src/linux-headers-4.10.0-rc4+/scripts/mod/modpost: ELF 64-bit LSB shared object, x86-64, version 1 (SYSV), dynamically linked, interpreter /lib64/ld-linux-x86-64.so.2, for GNU/Linux 2.6.32, BuildID[sha1]=bd976cc4c263e4ebd659ce143d8f9eebcb39b518, stripped ** Affects: kernel-package (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/1658756 Title: Cross-compiled kernel package contains host binaries To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kernel-package/+bug/1658756/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1161315] Re: Eric segmentation fault
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 in any way?) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1161315 Title: Eric segmentation fault To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/eric/+bug/1161315/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 319823] [NEW] problem contacting mirror admin team and gaining official status for Ignum releases mirror
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 HEADER and FOOTER including. I rectified the problem but I was not successful contacting mirror admins to notify them about the change and to re-apply for official status. The mirror is https://launchpad.net/ubuntu/+mirror/ucho.ignum.cz-release ** Affects: ubuntu Importance: Undecided Status: New -- problem contacting mirror admin team and gaining official status for Ignum releases mirror https://bugs.launchpad.net/bugs/319823 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
