[Bug 1944080] Re: [fan-network] Race-condition between "apt update" and dhcp request causes cloud-init error
https://github.com/juju/juju/pull/14028 ** Changed in: juju Status: In Progress => 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/1944080 Title: [fan-network] Race-condition between "apt update" and dhcp request causes cloud-init error To manage notifications about this bug go to: https://bugs.launchpad.net/charm-rabbitmq-server/+bug/1944080/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1972893] [NEW] installer failed
Public bug reported: Jammy installer failed. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: ubiquity 22.04.15 [modified: lib/partman/automatically_partition/question] ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.470 Date: Tue May 10 13:51:25 2022 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu-mate.seed maybe-ubiquity quiet splash --- LiveMediaBuild: Ubuntu-MATE 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: grub-installer UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: grub-installer (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy ubiquity-22.04.15 ubuntu-mate -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1972893 Title: installer failed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1972893/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1967842] Re: Ubuntu 22.04 Beta: linux-firmware iwlwifi-9260-th-b0-jf-b0-46.ucode - Wireless-AC 9260 not working
I also ran into this on upgrade to 22.04 - and the workaround worked for me too. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1967842 Title: Ubuntu 22.04 Beta: linux-firmware iwlwifi-9260-th-b0-jf-b0-46.ucode - Wireless-AC 9260 not working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1967842/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1960658] [NEW] "The screen locker is broken and unlocking is not possible"
Public bug reported: [83212.756483] kscreenlocker_g[81781]: segfault at 44 ip 7f1091c48fe5 sp 7ffcbfebb860 error 6 in libQt5Core.so.5.15.2[7f10919ef000+30e000] [83212.756500] Code: 28 00 00 00 0f 85 bd 05 00 00 0f b6 44 24 43 48 81 c4 88 00 00 00 5b 5d 41 5c 41 5d 41 5e 41 5f c3 0f 1f 40 00 48 89 44 24 60 83 40 04 01 8b 54 24 44 48 83 c0 08 c6 44 24 43 00 48 89 44 24 [87628.204380] kscreenlocker_g[85194]: segfault at 8b18b4df ip 7ff05003ef86 sp 7ffc8b4e2de0 error 4 in libQt5Core.so.5.15.2[7ff04fde5000+30e000] [87628.204391] Code: ba 01 00 00 00 48 83 e1 f8 48 01 c8 48 89 44 24 08 48 89 c6 31 c0 f0 48 0f b1 16 0f 85 f6 05 00 00 48 8b 44 24 30 48 8b 40 08 <48> 8b 40 40 48 89 44 24 38 48 85 c0 75 4c 48 8b 7c 24 08 48 89 c6 Seems a time dependent crash. If unlocking happens shortly after locking it seems to work, however let it sit overnight and two days in a row I see the 'you can't unlock' use loginctl unlock-session 3 screen. See attached photo. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: libkscreenlocker5 5.22.5-0ubuntu1 ProcVersionSignature: Ubuntu 5.13.0-28.31-generic 5.13.19 Uname: Linux 5.13.0-28-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: unknown Date: Fri Feb 11 10:55:38 2022 InstallationDate: Installed on 2020-02-12 (729 days ago) InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) ProcEnviron: LANGUAGE= TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: kscreenlocker UpgradeStatus: Upgraded to impish on 2022-01-04 (38 days ago) ** Affects: kscreenlocker (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug impish ** Attachment added: "photo of lock failure screen" https://bugs.launchpad.net/bugs/1960658/+attachment/5560414/+files/20220211_104418.jpg -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1960658 Title: "The screen locker is broken and unlocking is not possible" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kscreenlocker/+bug/1960658/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1959702] Re: Regression: ip6 ndp broken, host bridge doesn't add vlan guest entry to mdb
It looks to be 'an interesting mystery' we're chasing. This system is in production, so the results below are with the whole 'snooping engine' off as without it the whole thing dies. As such, I don't think the contents of the fdb and mdb tables mean much. The setups below are unchanged, they fail if snooping is on, work when it's off. root@noc1:~# ip -s -d link show vmbridge 6: vmbridge: mtu 1500 qdisc noqueue state UP mode DEFAULT group default qlen 1000 link/ether 52:54:33:bf:a8:78 brd ff:ff:ff:ff:ff:ff promiscuity 0 minmtu 68 maxmtu 65535 bridge forward_delay 1500 hello_time 200 max_age 2000 ageing_time 3 stp_state 0 priority 21 vlan_filtering 1 vlan_protocol 802.1Q bridge_id 0015.52:54:33:bf:a8:78 designated_root 0015.52:54:33:bf:a8:78 root_port 0 root_path_cost 0 topology_change 0 topology_change_detected 0 hello_timer 0.00 tcn_timer0.00 topology_change_timer0.00 gc_timer 137.32 vlan_default_pvid 0 vlan_stats_enabled 0 vlan_stats_per_port 0 group_fwd_mask 0 group_address 01:80:c2:00:00:00 mcast_snooping 0 mcast_router 1 mcast_query_use_ifaddr 0 mcast_querier 0 mcast_hash_elasticity 16 mcast_hash_max 4096 mcast_last_member_count 2 mcast_startup_query_count 2 mcast_last_member_interval 100 mcast_membership_interval 26000 mcast_querier_interval 25500 mcast_query_interval 12500 mcast_query_response_interval 1000 mcast_startup_query_interval 3124 mcast_stats_enabled 0 mcast_igmp_version 2 mcast_mld_version 1 nf_call_iptables 0 nf_call_ip6tables 0 nf_call_arptables 0 addrgenmode none numtxqueues 1 numrxqueues 1 gso_max_size 32000 gso_max_segs 24 RX: bytes packets errors dropped missed mcast 2013504987 17838769 0 0 0 5037107 TX: bytes packets errors dropped carrier collsns 84611 0 0 0 0 The bridge itself has no address of any kind other than a mac. Here's a detail from one of many identical vm setups: ip -s -d link show dbl 16: dbl: mtu 1500 qdisc noqueue master vmbridge state UNKNOWN mode DEFAULT group default qlen 1000 link/ether fe:54:00:60:c5:db brd ff:ff:ff:ff:ff:ff promiscuity 1 minmtu 68 maxmtu 65521 tun type tap pi off vnet_hdr off persist off bridge_slave state forwarding priority 32 cost 100 hairpin off guard off root_block off fastleave off learning on flood on port_id 0x800a port_no 0xa designated_port 32778 designated_cost 0 designated_bridge 0015.52:54:33:bf:a8:78 designated_root 0015.52:54:33:bf:a8:78 hold_timer 0.00 message_age_timer0.00 forward_delay_timer0.00 topology_change_ack 0 config_pending 0 proxy_arp off proxy_arp_wifi off mcast_router 1 mcast_fast_leave off mcast_flood on mcast_to_unicast off neigh_suppress off group_fwd_mask 0 group_fwd_mask_str 0x0 vlan_tunnel off isolated off addrgenmode eui64 numtxqueues 1 numrxqueues 1 gso_max_size 65536 gso_max_segs 65535 RX: bytes packets errors dropped missed mcast 18895018565 174327707 0 25070 0 0 TX: bytes packets errors dropped carrier collsns 30861506740 198028258 0 14270 0 There's some confidential stuff, so I've deleted repetitive vlan entries below. vlan 121 in this sandbox carries 'local lan' traffic. The bridge has an interface on that. vlan 100 is an only-in-rack server-server backbone for ceph. 122 is a public internet ingress on this mixed-use box. #bridge vlan show port vlan-id enp5s2122 PVID Egress Untagged enp4s0f0 103 105 ... 121 PVID Egress Untagged 122 133 enp4s0f1 100 PVID Egress Untagged 101 102 104 lan0noc0port 121 PVID Egress Untagged <-- this has a v4/v6 address for the server's use. ... gate 100 101 ... registry 121 PVID Egress Untagged 127 131 dbl 101 PVID Egress Untagged 121 ... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1959702 Title: Regression: ip6 ndp broken, host bridge doesn't add vlan guest entry to mdb To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1959702/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1959702] Re: Regression: ip6 ndp broken, host bridge doesn't add vlan guest entry to mdb
P.S. The reason this is a security issue is-- there is now an address on the host that the guest also 'knows' and it sits on the bridge giving access to all the other guests on the bridge. Most admins will not 'just know' they need rules to block fe80 traffic generated by host interfaces-- because of course at least one host interface needs an fe80 address for ipv6 neighbor protocols to work. It's a really big 'soft hole'. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1959702 Title: Regression: ip6 ndp broken, host bridge doesn't add vlan guest entry to mdb To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1959702/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1959702] Re: Regression: ip6 ndp broken, host bridge doesn't add vlan guest entry to mdb
I need to repeat: in sysctl.d put this line in a file, then reboot, then your test setup will show the failure: net.ipv6.conf.all.autoconf = 0 Otherwise, in your test setup the tables are populated, then you delete the addresses, but the L3/4 code engaged by even a little time with the fe80:... address at least until there is a timeout in the tables (longer than you wait for your test) kills the platform. Putting the above in then rebooting will avoid that, so you will see the bug when at no time was there an fe80 address on the interface. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1959702 Title: Regression: ip6 ndp broken, host bridge doesn't add vlan guest entry to mdb To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1959702/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1959702] Re: Regression: ip6 ndp broken, host bridge doesn't add vlan guest entry to mdb
** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1959702 Title: Regression: ip6 ndp broken, host bridge doesn't add vlan guest entry to mdb To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1959702/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1960242] [NEW] kernel fault on monitor wakeup, only reboot recovers.
Public bug reported: After a normal day's operations, the monitors switch off after an hour or so. Every morning since Impish, upon waking up and unlocking the system: 2 of the monitors wake, the rest remain in sleep mode. The only recourse is to do a graceful poweroff and cold boot. There is a kernel fault, as follows and in the attached file. It is 100% repeatable. [121665.686476] ceph: mds0 caps renewed [126829.470180] [ cut here ] [126829.470183] WARNING: CPU: 6 PID: 4368 at drivers/gpu/drm/ttm/ttm_bo.c:437 ttm_bo_release+0x2de/0x330 [ttm] [126829.470191] Modules linked in: ceph libceph fscache netfs xt_CHECKSUM ipt_REJECT nf_reject_ipv4 xt_tcpudp xt_conntrack xt_MASQUERADE nf_conntrack_netlink nft_chain_nat nf_nat xfrm_user nf_conntrack xfrm_algo nf_defrag_ipv6 nf_defrag_ipv4 xt_addrtype nft_compat nft_counter br_netfilter nf_tables nfnetlink vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) bridge stp llc overlay lz4 lz4_compress zram snd_hda_codec_realtek snd_hda_codec_generic ledtrig_audio snd_hda_codec_hdmi snd_hda_intel snd_intel_dspcfg intel_rapl_msr snd_intel_sdw_acpi intel_rapl_common snd_hda_codec sch_fq_codel snd_usb_audio snd_hda_core snd_usbmidi_lib snd_hwdep snd_pcm snd_seq_midi edac_mce_amd snd_seq_midi_event snd_rawmidi uvcvideo msr videobuf2_vmalloc parport_pc videobuf2_memops kvm_amd videobuf2_v4l2 videobuf2_common ppdev snd_seq videodev kvm snd_seq_device lp snd_timer rapl parport eeepc_wmi wmi_bmof joydev input_leds mc k10temp ccp snd soundcore mac_hid sunrpc ip_tables x_tables autofs4 btrfs blake2b_generic xor [126829.470220] zstd_compress raid6_pq libcrc32c hid_generic uas usbhid usb_storage hid amdgpu iommu_v2 gpu_sched nouveau radeon mxm_wmi i2c_algo_bit drm_ttm_helper ttm drm_kms_helper syscopyarea sysfillrect crct10dif_pclmul sysimgblt fb_sys_fops crc32_pclmul cec ghash_clmulni_intel rc_core mfd_aaeon aesni_intel asus_wmi crypto_simd sparse_keymap nvme video xhci_pci r8169 gpio_amdpt ahci drm cryptd realtek i2c_piix4 libahci xhci_pci_renesas nvme_core wmi gpio_generic [126829.470239] CPU: 6 PID: 4368 Comm: kwin_x11:cs0 Tainted: G OE 5.13.0-28-generic #31-Ubuntu [126829.470241] Hardware name: System manufacturer System Product Name/PRIME B450-PLUS, BIOS 3211 08/10/2021 [126829.470242] RIP: 0010:ttm_bo_release+0x2de/0x330 [ttm] [126829.470246] Code: e8 17 27 3f f0 e9 ac fd ff ff 49 8b 7e 98 b9 4c 1d 00 00 31 d2 be 01 00 00 00 e8 4d 4a 3f f0 49 8b 46 e8 eb 9d 4c 89 e0 eb 98 <0f> 0b 41 c7 86 84 00 00 00 00 00 00 00 49 8d 76 08 31 d2 4c 89 ef [126829.470247] RSP: 0018:b0df43547d28 EFLAGS: 00010202 [126829.470248] RAX: 0002 RBX: 0002 RCX: [126829.470249] RDX: 0001 RSI: 0246 RDI: 89e51b945ac0 [126829.470250] RBP: b0df43547d50 R08: 89e4529488e8 R09: 0002 [126829.470251] R10: 89e894fe4d38 R11: 89e51c2ffce8 R12: 89e51b9452b0 [126829.470251] R13: 89e8aa050c58 R14: 89e8aa050db8 R15: 89eb3bb8c480 [126829.470252] FS: 7f21ee182640() GS:89ec1e30() knlGS: [126829.470253] CS: 0010 DS: ES: CR0: 80050033 [126829.470254] CR2: 7fbf8805e7e8 CR3: 00045811c000 CR4: 00350ee0 [126829.470255] Call Trace: [126829.470256] [126829.470258] ttm_bo_put+0x30/0x50 [ttm] [126829.470262] amdgpu_bo_unref+0x1e/0x30 [amdgpu] [126829.470365] amdgpu_gem_object_free+0x34/0x50 [amdgpu] [126829.470454] drm_gem_object_free+0x1d/0x30 [drm] [126829.470470] drm_gem_dmabuf_release+0x40/0x60 [drm] [126829.470486] dma_buf_release+0x46/0xa0 [126829.470488] __dentry_kill+0x10e/0x190 [126829.470490] dentry_kill+0x52/0x1c0 [126829.470491] dput+0x12f/0x180 [126829.470492] __fput+0xf0/0x250 [126829.470494] fput+0xe/0x10 [126829.470495] task_work_run+0x6d/0xa0 [126829.470497] exit_to_user_mode_loop+0x150/0x160 [126829.470499] exit_to_user_mode_prepare+0x9f/0xb0 [126829.470500] syscall_exit_to_user_mode+0x27/0x50 [126829.470503] do_syscall_64+0x6e/0xb0 [126829.470504] ? do_syscall_64+0x6e/0xb0 [126829.470506] ? asm_sysvec_apic_timer_interrupt+0xa/0x20 [126829.470507] entry_SYSCALL_64_after_hwframe+0x44/0xae [126829.470509] RIP: 0033:0x7f21fb43e9cb [126829.470510] Code: ff ff ff 85 c0 79 8b 49 c7 c4 ff ff ff ff 5b 5d 4c 89 e0 41 5c c3 66 0f 1f 84 00 00 00 00 00 f3 0f 1e fa b8 10 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d 35 a4 0f 00 f7 d8 64 89 01 48 [126829.470511] RSP: 002b:7f21ee181738 EFLAGS: 0246 ORIG_RAX: 0010 [126829.470513] RAX: RBX: 7f21ee181770 RCX: 7f21fb43e9cb [126829.470513] RDX: 7f21ee181770 RSI: 40086409 RDI: 000d [126829.470514] RBP: 40086409 R08: 55849cb1c370 R09: [126829.470515] R10: R11: 0246 R12: 55849c056508 [126829.470515] R13: 000d R14: 55849c057434 R15: 7f21ee1817a0
Re: [Bug 1959702] Re: Regression: ip6 ndp broken, host bridge doesn't add vlan guest entry to mdb
On 2/5/22 18:59, Jay Vosburgh wrote: > Harry, > > I am attempting to reproduce the behavior you describe, but have been > unable to do so. Could you clarify some of the configuration specifics, > as follows: > > Starting with step 2, > > "2. On the host, create a bridge and vlan with two ports, each with the > chosen vlan as PVID and egress untagged. Assign those ports one each to > the guests as the interface, use e1000. Be sure to NOT autoconfigure the > host side of the bridge ports with any ip4 or ip6 address (including > fe80::), [...]" > > I have configured testbr0 with no addresses, i.e., "ip addr show": > > 15: testbr0: mtu 1500 qdisc noqueue state > UP group default qlen 1000 > link/ether 8c:dc:d4:b3:cb:f1 brd ff:ff:ff:ff:ff:ff > > and added vnet1 and vnet3 (the interfaces that connect to the VMs), to > testbr0, and removing their respective fe80: addresses. I set the bridge > vlan behavior via > > bridge vlan add dev vnet1 vid 1234 pvid untagged > bridge vlan add dev vnet3 vid 1234 pvid untagged > bridge vlan del dev vnet1 vid 1 > bridge vlan del dev vnet3 vid 1 > > then added a separate Ethernet device to the testbr0, removed its fe80: > address, and set its bridge vlan as > > bridge vlan add dev eno50 vid 1234 > bridge vlan del dev eno50 vid 1 > > Adding addresses to the interfaces within the VMs results in ping between > the two functioning (even in the face of "ip neigh flush dev enp7s0"). > > At no time does "bridge mdb" affect the behavior (it lists no entries), > and it in unnecessary to add ff02:ffxx entries as you describe in step 6 > (I presume that your mention of "fe02::ff..." is a typo for "ff02"). > > I am testing with the Ubuntu 5.11.0-46 kernel, which differs slightly from > your 5.11.0-49. From which version did you upgrade (i.e., what was the > last known working version)? I'm preparing to test with 5.11.0-50 (I am > unable to locate -49), but would also like to know if the above > description matches your configuration. > > Thanks. > These are partial, showing the relevant bits. root@noc2:~# uname -a Linux noc2.1.quietfountain.com 5.11.0-49-generic #55-Ubuntu SMP Wed Jan 12 17:36:34 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux root@noc2:~# bridge vlan show port vlan-id enp4s0f1 100 PVID Egress Untagged 101 102 104 gate 100 101 102 103 104 105 ... dbs 102 PVID Egress Untagged 121 dbl 101 PVID Egress Untagged 121 4: enp4s0f1: mtu 1500 qdisc fq_codel master vmbridge state UP group default qlen 1000 link/ether 00:15:17:5a:ea:a9 brd ff:ff:ff:ff:ff:ff ... 13: gate: mtu 1500 qdisc noqueue master vmbridge state UNKNOWN group default qlen 1000 link/ether fe:54:00:9d:61:fa brd ff:ff:ff:ff:ff:ff 15: dbs: mtu 1500 qdisc noqueue master vmbridge state UNKNOWN group default qlen 1000 link/ether fe:54:00:2a:0e:ac brd ff:ff:ff:ff:ff:ff 16: dbl: mtu 1500 qdisc noqueue master vmbridge state UNKNOWN group default qlen 1000 link/ether fe:54:00:f7:d1:8a brd ff:ff:ff:ff:ff:ff 17: fssupport: mtu 1500 qdisc noqueue master vmbridge state UNKNOWN group default qlen 1000 Without turning off snooping, there was no v6 comm between any of them, or on vm's on dbl or dbs on other similarly set up hosts. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1959702 Title: Regression: ip6 ndp broken, host bridge doesn't add vlan guest entry to mdb To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1959702/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1959702] Re: Regression: ip6 ndp broken, host bridge doesn't add vlan guest entry to mdb
On 2/5/22 18:59, Jay Vosburgh wrote: > Harry, > > I am attempting to reproduce the behavior you describe, but have been > unable to do so. Could you clarify some of the configuration specifics, > as follows: > > Starting with step 2, > > "2. On the host, create a bridge and vlan with two ports, each with the > chosen vlan as PVID and egress untagged. Assign those ports one each to > the guests as the interface, use e1000. Be sure to NOT autoconfigure the > host side of the bridge ports with any ip4 or ip6 address (including > fe80::), [...]" > > I have configured testbr0 with no addresses, i.e., "ip addr show": > > 15: testbr0: mtu 1500 qdisc noqueue state > UP group default qlen 1000 > link/ether 8c:dc:d4:b3:cb:f1 brd ff:ff:ff:ff:ff:ff > > and added vnet1 and vnet3 (the interfaces that connect to the VMs), to > testbr0, and removing their respective fe80: addresses. I set the bridge > vlan behavior via > > bridge vlan add dev vnet1 vid 1234 pvid untagged > bridge vlan add dev vnet3 vid 1234 pvid untagged > bridge vlan del dev vnet1 vid 1 > bridge vlan del dev vnet3 vid 1 > > then added a separate Ethernet device to the testbr0, removed its fe80: > address, and set its bridge vlan as > > bridge vlan add dev eno50 vid 1234 > bridge vlan del dev eno50 vid 1 > > Adding addresses to the interfaces within the VMs results in ping between > the two functioning (even in the face of "ip neigh flush dev enp7s0"). > > At no time does "bridge mdb" affect the behavior (it lists no entries), > and it in unnecessary to add ff02:ffxx entries as you describe in step 6 > (I presume that your mention of "fe02::ff..." is a typo for "ff02"). > > I am testing with the Ubuntu 5.11.0-46 kernel, which differs slightly from > your 5.11.0-49. From which version did you upgrade (i.e., what was the > last known working version)? I'm preparing to test with 5.11.0-50 (I am > unable to locate -49), but would also like to know if the above > description matches your configuration. > > Thanks. Also, I'd say if any of the interfaces *ever* had v6 addresses, then there would be entries in the fdb and mdb. But on these systems we have: net.ipv6.conf.all.autoconf = 0 before the interfaces are created. > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1959702 Title: Regression: ip6 ndp broken, host bridge doesn't add vlan guest entry to mdb To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1959702/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1573345] Re: Dual monitor loses settings after screen sleep
Still exists 2/2022. KScreen. After a sleep, it's random which monitors are detected at all. After a sleep some, but not all the monitors come back at all, and the ones that do are horizontally aligned, the stored alignment is lost. The only way to fix it I've found is to reboot. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1573345 Title: Dual monitor loses settings after screen sleep To manage notifications about this bug go to: https://bugs.launchpad.net/kscreen/+bug/1573345/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1959702] Re: Regression: ip6 ndp broken, host bridge doesn't add vlan guest entry to mdb
Yup, those failures were to do with an old radeon chipset on an ancient server. On 2/1/22 17:33, Seth Arnold wrote: > Sounds good, thanks: > > [0.00] Linux version 5.11.0-49-generic (buildd@lcy02-amd64-054) > (gcc (Ubuntu 10.3.0-1ubuntu1) 10.3.0, GNU ld (GNU Binutils for Ubuntu) > 2.36.1) #55-Ubuntu SMP Wed Jan 12 17:36:34 UTC 2022 (Ubuntu > 5.11.0-49.55-generic 5.11.22) > > btw, there were a bunch of memory allocation failures in the dmesg, in > case they weren't obvious. > > ** Attachment removed: "apport.linux-image-5.11.0-49-generic.rw5aqx7x.apport" > > https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1959702/+attachment/5558647/+files/apport.linux-image-5.11.0-49-generic.rw5aqx7x.apport > > ** Information type changed from Private Security to Public Security > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1959702 Title: Regression: ip6 ndp broken, host bridge doesn't add vlan guest entry to mdb To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1959702/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1944720] [NEW] kde-spectacle crashes every time
Public bug reported: I have a multi-display setup, a few traditional HD monitors. Under 21.04, every time I choose 'Take a new screenshot' with the rectangular region area capture mode-- the spectacle just disappears as if it was never launched. The system resumes as if Spectacle was never attempted, there is no option to choose any region, it is as if I had just quit spectacle or had never run it in the first place. Everything operates seemingly normally. Then-- when spectacle is launched a second time -- the system goes immediately into the mode of capturing a rectangular region -- it operates as if the 'take a new screenshot' had just been pressed. After the screenshot is taken, the menu reappears and is normal. ** Affects: kde-spectacle (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/1944720 Title: kde-spectacle crashes every time To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kde-spectacle/+bug/1944720/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1939170] [NEW] package virtualbox-ext-pack (not installed) failed to install/upgrade: new virtualbox-ext-pack package pre-installation script subprocess returned error exit status 1
Public bug reported: Command entered: sudo pkcon install virtualbox-ext-pack ProblemType: Package DistroRelease: Ubuntu 20.04 Package: virtualbox-ext-pack (not installed) ProcVersionSignature: Ubuntu 5.11.0-25.27~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-25-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu27.18 AptOrdering: virtualbox-ext-pack:amd64: Install NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: skip Date: Fri Aug 6 11:35:57 2021 DpkgTerminalLog: Preparing to unpack .../virtualbox-ext-pack_6.1.22-1~ubuntu1.20.04.1_all.deb ... User did not accept the license. dpkg: error processing archive /var/cache/apt/archives/virtualbox-ext-pack_6.1.22-1~ubuntu1.20.04.1_all.deb (--unpack): new virtualbox-ext-pack package pre-installation script subprocess returned error exit status 1 DuplicateSignature: package:virtualbox-ext-pack:(not installed) Preparing to unpack .../virtualbox-ext-pack_6.1.22-1~ubuntu1.20.04.1_all.deb ... User did not accept the license. dpkg: error processing archive /var/cache/apt/archives/virtualbox-ext-pack_6.1.22-1~ubuntu1.20.04.1_all.deb (--unpack): new virtualbox-ext-pack package pre-installation script subprocess returned error exit status 1 ErrorMessage: new virtualbox-ext-pack package pre-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2021-08-04 (1 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.6 SourcePackage: virtualbox-ext-pack Title: package virtualbox-ext-pack (not installed) failed to install/upgrade: new virtualbox-ext-pack package pre-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: virtualbox-ext-pack (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1939170 Title: package virtualbox-ext-pack (not installed) failed to install/upgrade: new virtualbox-ext-pack package pre-installation script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/virtualbox-ext-pack/+bug/1939170/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1930756] [NEW] regression: virtiofsd in qemu-system-common fails selinux related xattr
Public bug reported:
System call lsetfilecon in the guest fails, it worked when the host ran
Groovy.
How to repeat/test virtiofs lsetfilecon regression that breaks dpkg,
prevents upgrades/fixes.
In the guest, for example fedora:
[root@registry1 ~]# getenforce
Permissive
[root@registry1 ~]# cat lsetfilecon.c
#include
#include
#include
void perror(const char *s);
int main(int argc,char *argv[]){
int i;
i= lsetfilecon("/usr/bin/rngtest","system_u:object_r:bin_t:s0");
//i= lsetfilecon("/usr/bin/rngtest;60b9120b","system_u:object_r:bin_t:s0");
printf("ret %lx\n",i);
perror("\n");
return 0;
}
[root@registry1 ~]# gcc lsetfilecon.c -lselinux -o lsetfilecon
[root@registry1 ~]# ./lsetfilecon
ret
: Operation not permitted
[root@registry1 ~]# ls -l /usr/bin/rngtest
-rwxr-xr-x. 1 root root 21176 Apr 27 18:26 /usr/bin/rngtest
[root@registry1 ~]# uname -a
Linux registry1. 5.11.19-300.fc34.x86_64 #1 SMP Fri May 7 14:17:15 UTC 2021
x86_64 x86_64 x86_64 GNU/Linux
On the ubuntu hirsuite host:
root@noc1:/vmsystems/registry1/usr/bin# getfattr -m - -d rngtest
# file: rngtest
security.selinux="system_u:object_r:bin_t:s0"
ls -l rngtest
-rwxr-xr-x. 1 root root 21176 Apr 27 18:26 rngtest
#/usr/lib/qemu/virtiofsd --version
using FUSE kernel interface version 7.32
#uname -a
5.11.0-18-generic #19-Ubuntu SMP Fri May 7 14:22:03 UTC 2021 x86_64 x86_64
x86_64 GNU/Linux
** Affects: qemu (Ubuntu)
Importance: Undecided
Status: New
** Tags: virtiofs
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1930756
Title:
regression: virtiofsd in qemu-system-common fails selinux related
xattr
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1930756/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1914023] Re: Can not create new user
why did I wrote 20.02 when I meant to wrote 20.04, it's a mystery -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1914023 Title: Can not create new user To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/phpmyadmin/+bug/1914023/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1914023] [NEW] Can not create new user
Public bug reported: On Ubuntu 20.04 - due to major internal change on MySQL (the one bundled on 20.02) on a new BUILD (not major version, not even minor version - but build version) ; phpmyadmin on 20.04 can not create new user DETAILS are available here : https://github.com/phpmyadmin/phpmyadmin/issues/16166#issuecomment-640248002 PROPOSED SOLUTION : applying the patch listed here : https://github.com/phpmyadmin/phpmyadmin/issues/16166#issuecomment-640241943 Thank you ! (bad Oracle, bad) ** Affects: phpmyadmin (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/1914023 Title: Can not create new user To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/phpmyadmin/+bug/1914023/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1904566] Re: jackd/alsa: only 2 channels of 4 found on usb-interface Lexicon Omega (ALSA: cannot set channel count to 4 for capture)
Hi, is any further action or info necessary to catch and kill the bug ? Best regards -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1904566 Title: jackd/alsa: only 2 channels of 4 found on usb-interface Lexicon Omega (ALSA: cannot set channel count to 4 for capture) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1904566/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1887190] Re: MSFT Touchpad not working on Lenovo Legion-5 15ARH05
Hi all. Please excuse my novice approach guys but I hope that I am making some kind of contribution! I to have a Lenovo Legion 5 and I am running Opensuse Tumbleweed with Kernel 5.9.11-1 with Gnome 3.38. With some help from the Opensuse forum I have the following error; input: MSFT0001:00 04F3:3186 Touchpad as /devices/platform/AMDI0010:03/i2c-0/i2c- MSFT0001:00/0018:04F3:3186.0001/input/input7 This as you may gather stops my trackpad from working and they have suggested I visit here and ask for any help! All the best - Harry -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1887190 Title: MSFT Touchpad not working on Lenovo Legion-5 15ARH05 To manage notifications about this bug go to: https://bugs.launchpad.net/pop-os/+bug/1887190/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1894902] Re: 2 apparmor items missing for 'groovy'
** Also affects: apparmor (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/1894902 Title: 2 apparmor items missing for 'groovy' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1894902/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1904566] Re: jackd/alsa: only 2 channels of 4 found on usb-interface Lexicon Omega (ALSA: cannot set channel count to 4 for capture)
Hi, i started command apport-collect 1904566 and sent you more information. ** 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/1904566 Title: jackd/alsa: only 2 channels of 4 found on usb-interface Lexicon Omega (ALSA: cannot set channel count to 4 for capture) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1904566/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1904566] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1904566/+attachment/5435720/+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/1904566 Title: jackd/alsa: only 2 channels of 4 found on usb-interface Lexicon Omega (ALSA: cannot set channel count to 4 for capture) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1904566/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1904566] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1904566/+attachment/5435719/+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/1904566 Title: jackd/alsa: only 2 channels of 4 found on usb-interface Lexicon Omega (ALSA: cannot set channel count to 4 for capture) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1904566/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1904566] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1904566/+attachment/5435718/+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/1904566 Title: jackd/alsa: only 2 channels of 4 found on usb-interface Lexicon Omega (ALSA: cannot set channel count to 4 for capture) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1904566/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1904566] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1904566/+attachment/5435715/+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/1904566 Title: jackd/alsa: only 2 channels of 4 found on usb-interface Lexicon Omega (ALSA: cannot set channel count to 4 for capture) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1904566/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1904566] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1904566/+attachment/5435714/+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/1904566 Title: jackd/alsa: only 2 channels of 4 found on usb-interface Lexicon Omega (ALSA: cannot set channel count to 4 for capture) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1904566/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1904566] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1904566/+attachment/5435717/+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/1904566 Title: jackd/alsa: only 2 channels of 4 found on usb-interface Lexicon Omega (ALSA: cannot set channel count to 4 for capture) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1904566/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1904566] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1904566/+attachment/5435716/+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/1904566 Title: jackd/alsa: only 2 channels of 4 found on usb-interface Lexicon Omega (ALSA: cannot set channel count to 4 for capture) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1904566/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1904566] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1904566/+attachment/5435711/+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/1904566 Title: jackd/alsa: only 2 channels of 4 found on usb-interface Lexicon Omega (ALSA: cannot set channel count to 4 for capture) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1904566/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1904566] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1904566/+attachment/5435710/+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/1904566 Title: jackd/alsa: only 2 channels of 4 found on usb-interface Lexicon Omega (ALSA: cannot set channel count to 4 for capture) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1904566/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1904566] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1904566/+attachment/5435713/+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/1904566 Title: jackd/alsa: only 2 channels of 4 found on usb-interface Lexicon Omega (ALSA: cannot set channel count to 4 for capture) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1904566/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1904566] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1904566/+attachment/5435712/+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/1904566 Title: jackd/alsa: only 2 channels of 4 found on usb-interface Lexicon Omega (ALSA: cannot set channel count to 4 for capture) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1904566/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1904566] Re: jackd/alsa: only 2 channels of 4 found on usb-interface Lexicon Omega (ALSA: cannot set channel count to 4 for capture)
4.2-3ubuntu0.18.04.1 amd64 [installiert] libzita-alsa-pcmi0/bionic,now 0.2.0-4ubuntu2 amd64 [installiert] $ apt list --installed|grep -i jackd jackd/bionic,bionic,now 5 all [installiert] jackd2/bionic,now 1.9.12~dfsg-2 amd64 [installiert] jackd2-firewire/bionic,now 1.9.12~dfsg-2 amd64 [installiert] libjack-jackd2-0/bionic,now 1.9.12~dfsg-2 amd64 [installiert] libjack-jackd2-dev/bionic,now 1.9.12~dfsg-2 amd64 [installiert] jackd is configure via qjackctl, no specification of channelcount (only default-value:0 ). Here's the output of jackd starting (finding 4 capture channels + 2 playback channels) --- snip--- Tue Nov 17 12:23:43 2020: Starting jack server... Tue Nov 17 12:23:43 2020: JACK server starting in realtime mode with priority 10 Tue Nov 17 12:23:43 2020: self-connect-mode is "Don't restrict self connect requests" Tue Nov 17 12:23:43 2020: Jack: JackPosixThread::StartImp : create non RT thread Tue Nov 17 12:23:43 2020: Jack: JackPosixThread::ThreadHandler : start Tue Nov 17 12:23:43 2020: Jack: capture device hw:Omega Tue Nov 17 12:23:43 2020: Jack: playback device hw:Omega Tue Nov 17 12:23:43 2020: Jack: apparent rate = 44100 Tue Nov 17 12:23:43 2020: Jack: frames per period = 256 Tue Nov 17 12:23:43 2020: Jack: JackDriver::Open capture_driver_name = hw:Omega Tue Nov 17 12:23:43 2020: Jack: JackDriver::Open playback_driver_name = hw:Omega Tue Nov 17 12:23:43 2020: Jack: Check protocol client = 8 server = 8 Tue Nov 17 12:23:43 2020: Jack: JackEngine::ClientInternalOpen: name = system Tue Nov 17 12:23:43 2020: Jack: JackEngine::AllocateRefNum ref = 0 Tue Nov 17 12:23:43 2020: Jack: JackLinuxFutex::Allocate name = jack_sem.505_default_system val = 0 Tue Nov 17 12:23:43 2020: Jack: JackEngine::NotifyAddClient: name = system Tue Nov 17 12:23:43 2020: Jack: JackGraphManager::SetBufferSize size = 256 Tue Nov 17 12:23:43 2020: Jack: JackConnectionManager::DirectConnect first: ref1 = 0 ref2 = 0 Tue Nov 17 12:23:43 2020: Jack: JackGraphManager::ConnectRefNum cur_index = 0 ref1 = 0 ref2 = 0 Tue Nov 17 12:23:43 2020: Jack: JackDriver::SetupDriverSync driver sem in flush mode Tue Nov 17 12:23:43 2020: Acquired audio card Audio1 Tue Nov 17 12:23:43 2020: creating alsa driver ... hw:Omega|hw:Omega|256|2|44100|0|0|hwmon|swmeter|-|32bit Tue Nov 17 12:23:43 2020: configuring for 44100Hz, period = 256 frames (5.8 ms), buffer = 2 periods Tue Nov 17 12:23:43 2020: ALSA: final selected sample format for capture: 24bit little-endian in 3bytes format Tue Nov 17 12:23:43 2020: ALSA: use 2 periods for capture Tue Nov 17 12:23:43 2020: ALSA: final selected sample format for playback: 24bit little-endian in 3bytes format Tue Nov 17 12:23:43 2020: ALSA: use 2 periods for playback --- snip-- The attachment shows you there are 4 capture-channels. The bug is described here by another person too: https://linuxmusicians.com/viewtopic.php?f=64=21380 My opinion is that somewhere in development of kernel alsa has lost it's capability to configure more than 2 capture-channels. I wonder why nobody else is complaining, maybe because it's an usb-device ? If you need more information, please tell me which, i will provide them. best regards Harry + --- + ProblemType: Bug + ApportVersion: 2.20.9-0ubuntu7.20 + Architecture: amd64 + AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D2', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: + CurrentDesktop: XFCE + DistroRelease: Ubuntu 18.04 + HibernationDevice: + RESUME=none + #RESUME=UUID=dfde7c59-5c49-4cce-9ba4-b8ac106ae5cb + InstallationDate: Installed on 2017-05-20 (1277 days ago) + InstallationMedia: Xubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215) + IwConfig: + lono wireless extensions. + + enp0s31f6 no wireless extensions. + Lsusb: + Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub + Bus 001 Device 003: ID 046d:c501 Logitech, Inc. Cordless Mouse Receiver + Bus 001 Device 002: ID 05e3:0716 Genesys Logic, Inc. USB 2.0 Multislot Card Reader/Writer + Bus 001 Device 004: ID 046a:010e Cherry GmbH + Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub + MachineType: System manufacturer System Product Name + Package: linux-hwe-5.4 + ProcFB: 0 i915drmfb + ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-54-generic root=UUID=af5502e5-b124-4e34-a0d2-ece834ccdc87 ro rootflags=subvol=@ ipv6.disable=1 fastboot plymouth:debug ipv6.disable=1 + ProcVersionSignature: Ubuntu 5.4.0-54.60~18.04.1-generic 5.4.65 + RelatedPackageVersio
[Bug 1904566] Re: jackd/alsa: only 2 channels of 4 found on usb-interface Lexicon Omega (ALSA: cannot set channel count to 4 for capture)
Sorry i choosed my actual kernel, but it seems the bug exists for more than a year in all the kernels since .. ? ** Package changed: ubuntu => linux-hwe-5.4 (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1904566 Title: jackd/alsa: only 2 channels of 4 found on usb-interface Lexicon Omega (ALSA: cannot set channel count to 4 for capture) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.4/+bug/1904566/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1904566] [NEW] jackd/alsa: only 2 channels of 4 found on usb-interface Lexicon Omega (ALSA: cannot set channel count to 4 for capture)
installiert] libjack-jackd2-0/bionic,now 1.9.12~dfsg-2 amd64 [installiert] libjack-jackd2-dev/bionic,now 1.9.12~dfsg-2 amd64 [installiert] jackd is configure via qjackctl, no specification of channelcount (only default-value:0 ). Here's the output of jackd starting (finding 4 capture channels + 2 playback channels) --- snip--- Tue Nov 17 12:23:43 2020: Starting jack server... Tue Nov 17 12:23:43 2020: JACK server starting in realtime mode with priority 10 Tue Nov 17 12:23:43 2020: self-connect-mode is "Don't restrict self connect requests" Tue Nov 17 12:23:43 2020: Jack: JackPosixThread::StartImp : create non RT thread Tue Nov 17 12:23:43 2020: Jack: JackPosixThread::ThreadHandler : start Tue Nov 17 12:23:43 2020: Jack: capture device hw:Omega Tue Nov 17 12:23:43 2020: Jack: playback device hw:Omega Tue Nov 17 12:23:43 2020: Jack: apparent rate = 44100 Tue Nov 17 12:23:43 2020: Jack: frames per period = 256 Tue Nov 17 12:23:43 2020: Jack: JackDriver::Open capture_driver_name = hw:Omega Tue Nov 17 12:23:43 2020: Jack: JackDriver::Open playback_driver_name = hw:Omega Tue Nov 17 12:23:43 2020: Jack: Check protocol client = 8 server = 8 Tue Nov 17 12:23:43 2020: Jack: JackEngine::ClientInternalOpen: name = system Tue Nov 17 12:23:43 2020: Jack: JackEngine::AllocateRefNum ref = 0 Tue Nov 17 12:23:43 2020: Jack: JackLinuxFutex::Allocate name = jack_sem.505_default_system val = 0 Tue Nov 17 12:23:43 2020: Jack: JackEngine::NotifyAddClient: name = system Tue Nov 17 12:23:43 2020: Jack: JackGraphManager::SetBufferSize size = 256 Tue Nov 17 12:23:43 2020: Jack: JackConnectionManager::DirectConnect first: ref1 = 0 ref2 = 0 Tue Nov 17 12:23:43 2020: Jack: JackGraphManager::ConnectRefNum cur_index = 0 ref1 = 0 ref2 = 0 Tue Nov 17 12:23:43 2020: Jack: JackDriver::SetupDriverSync driver sem in flush mode Tue Nov 17 12:23:43 2020: Acquired audio card Audio1 Tue Nov 17 12:23:43 2020: creating alsa driver ... hw:Omega|hw:Omega|256|2|44100|0|0|hwmon|swmeter|-|32bit Tue Nov 17 12:23:43 2020: configuring for 44100Hz, period = 256 frames (5.8 ms), buffer = 2 periods Tue Nov 17 12:23:43 2020: ALSA: final selected sample format for capture: 24bit little-endian in 3bytes format Tue Nov 17 12:23:43 2020: ALSA: use 2 periods for capture Tue Nov 17 12:23:43 2020: ALSA: final selected sample format for playback: 24bit little-endian in 3bytes format Tue Nov 17 12:23:43 2020: ALSA: use 2 periods for playback --- snip-- The attachment shows you there are 4 capture-channels. The bug is described here by another person too: https://linuxmusicians.com/viewtopic.php?f=64=21380 My opinion is that somewhere in development of kernel alsa has lost it's capability to configure more than 2 capture-channels. I wonder why nobody else is complaining, maybe because it's an usb-device ? If you need more information, please tell me which, i will provide them. best regards Harry ** Affects: ubuntu Importance: Undecided Status: New ** Attachment added: "Screenshot showing 4 capture-channels" https://bugs.launchpad.net/bugs/1904566/+attachment/5435139/+files/4-Channels.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1904566 Title: jackd/alsa: only 2 channels of 4 found on usb-interface Lexicon Omega (ALSA: cannot set channel count to 4 for capture) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1904566/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1861532] Re: brightness control not working [Lenovo Legion Y540/Y545]
Sir no resolution legion y545 not working -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1861532 Title: brightness control not working [Lenovo Legion Y540/Y545] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1861532/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1901148] Re: executing grub install /dev/sda failed.
** Description changed:
Ubuntu 20.10
Grub installer failed to install on /dev/sda
tried installing grub manually via "Try Ubuntu" terminal.
unallocated all drives. I have 120gb SSD and 250 HDD.
EFI partitioned
Bios partitioned
No swap partitioned
I think it's an error for both Ubiquity and Grub
+ The device is Lenovo Ideapad 320 14IAP. Previously installed OS are
+ Windows 10, Ubuntu 20.04.
+
I tried boot-repair no luck. details are as follows:
{
boot-repair-4ppa125
[20201023_0638]
== Boot Info Summary
===
- => No boot loader is installed in the MBR of /dev/sda.
- => No boot loader is installed in the MBR of /dev/sdb.
- => Syslinux MBR (5.00 and higher) is installed in the MBR of /dev/sdc.
+ => No boot loader is installed in the MBR of /dev/sda.
+ => No boot loader is installed in the MBR of /dev/sdb.
+ => Syslinux MBR (5.00 and higher) is installed in the MBR of /dev/sdc.
sdc1:
- File system: vfat
- Boot sector type: SYSLINUX 6.03
- Boot sector info: Syslinux looks at sector 32784 of /dev/sdc1 for its
-second stage. The integrity check of Syslinux failed.
-No errors found in the Boot Parameter Block.
- Operating System:
- Boot files:/boot/grub/grub.cfg /syslinux.cfg
-/efi/BOOT/grubx64.efi /ldlinux.sys
+ File system: vfat
+ Boot sector type: SYSLINUX 6.03
+ Boot sector info: Syslinux looks at sector 32784 of /dev/sdc1 for its
+ second stage. The integrity check of Syslinux failed.
+ No errors found in the Boot Parameter Block.
+ Operating System:
+ Boot files:/boot/grub/grub.cfg /syslinux.cfg
+ /efi/BOOT/grubx64.efi /ldlinux.sys
0 OS detected
=
Architecture/Host Info
CPU architecture: 64-bit
Live-session OS is Ubuntu 64-bit (Boot-Repair-Disk 64bit 20200604, bionic,
x86_64)
= UEFI
=
BIOS is EFI-compatible, and is setup in EFI-mode for this live-session.
SecureBoot disabled.
efibootmgr -v
BootCurrent:
Timeout: 0 seconds
BootOrder: ,2001,2003,2002
Boot* Linpus lite
HD(1,MBR,0x428c8a7,0x800,0x1e35800)/File(\EFI\Boot\grubx64.efi)RC
Boot0007* EFI Network 0 for IPv4 (54-E1-AD-6F-12-36)
PciRoot(0x0)/Pci(0x14,0x0)/Pci(0x0,0x0)/MAC(54e1ad6f1236,0)/IPv4(0.0.0.00.0.0.0,0,0)RC
Boot0008* EFI Network 0 for IPv6 (54-E1-AD-6F-12-36)
PciRoot(0x0)/Pci(0x14,0x0)/Pci(0x0,0x0)/MAC(54e1ad6f1236,0)/IPv6([::]:<->[::]:,0,0)RC
Boot2001* EFI USB Device RC
Boot2002* EFI DVD/CDROM RC
Boot2003* EFI Network RC
= Drive/Partition Info
=
Disks info: __
Partitions info (1/3): ___
Partitions info (2/3): ___
Partitions info (3/3): ___
fdisk -l (filtered): _
Disk sda: 111.8 GiB, 120034123776 bytes, 234441648 sectors
Disk identifier: B79E9BD6-815D-4C1C-A6AD-8F3FB1AC130C
Disk sdb: 232.9 GiB, 250059350016 bytes, 488397168 sectors
Disk identifier: 62764C30-4F79-400D-9AB4-09BD0F3BDEA7
Disk sdc: 15.1 GiB, 16219373568 bytes, 31678464 sectors
Disk identifier: 0x0428c8a7
- Boot Start End Sectors Size Id Type
+ Boot Start End Sectors Size Id Type
sdc1 * 2048 31678463 31676416 15.1G c W95 FAT32 (LBA)
Disk zram0: 973.3 MiB, 1020526592 bytes, 249152 sectors
Disk zram1: 973.3 MiB, 1020526592 bytes, 249152 sectors
Disk zram2: 973.3 MiB, 1020526592 bytes, 249152 sectors
Disk zram3: 973.3 MiB, 1020526592 bytes, 249152 sectors
parted -lm (filtered): ___
sda:120GB:scsi:512:512:gpt:ATA ADATA SU650:;
sdb:250GB:scsi:512:512:gpt:ATA Hitachi HTS54322:;
sdc:16.2GB:scsi:512:512:msdos:SRT USB:;
1:1049kB:16.2GB:16.2GB:fat32::boot, lba;
zram3:1021MB:unknown:4096:4096:loop:Unknown:;
1:0.00B:1021MB:1021MB:linux-swap(v1)::;
zram1:1021MB:unknown:4096:4096:loop:Unknown:;
1:0.00B:1021MB:1021MB:linux-swap(v1)::;
zram2:1021MB:unknown:4096:4096:loop:Unknown:;
1:0.00B:1021MB:1021MB:linux-swap(v1)::;
zram0:1021MB:unknown:4096:4096:loop:Unknown:;
1:0.00B:1021MB:1021MB:linux-swap(v1)::;
blkid (filtered):
NAME FSTYPE UUID
[Bug 1901148] Re: executing grub install /dev/sda failed. Fatal Error - Ubiquity
** Summary changed: - executing grub install /dev/sda faile. Fatal Error - Ubiquity + executing grub install /dev/sda failed. Fatal Error - Ubiquity ** Summary changed: - executing grub install /dev/sda failed. Fatal Error - Ubiquity + executing grub install /dev/sda failed. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1901148 Title: executing grub install /dev/sda failed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1901148/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1874610] Re: error: failed to register the EFI boot entry: Operation not permitted.
currently happening to me on Ubuntu 20.10. Never had any issues installing linux systems until I installed Ubuntu 20.10 "executing grub install /dev/sda failed this is a fatal error" also posted a similar report https://bugs.launchpad.net/ubuntu/+source /grub-installer/+bug/1901148 boot-repair did nothing. tried to dual boot with windows 10 in case their installer would fix it. no luck. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1874610 Title: error: failed to register the EFI boot entry: Operation not permitted. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1874610/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1901148] [NEW] executing grub install /dev/sda faile. Fatal Error - Ubiquity
Public bug reported:
Ubuntu 20.10
Grub installer failed to install on /dev/sda
tried installing grub manually via "Try Ubuntu" terminal.
unallocated all drives. I have 120gb SSD and 250 HDD.
EFI partitioned
Bios partitioned
No swap partitioned
I think it's an error for both Ubiquity and Grub
I tried boot-repair no luck. details are as follows:
{
boot-repair-4ppa125 [20201023_0638]
== Boot Info Summary ===
=> No boot loader is installed in the MBR of /dev/sda.
=> No boot loader is installed in the MBR of /dev/sdb.
=> Syslinux MBR (5.00 and higher) is installed in the MBR of /dev/sdc.
sdc1:
File system: vfat
Boot sector type: SYSLINUX 6.03
Boot sector info: Syslinux looks at sector 32784 of /dev/sdc1 for its
second stage. The integrity check of Syslinux failed.
No errors found in the Boot Parameter Block.
Operating System:
Boot files:/boot/grub/grub.cfg /syslinux.cfg
/efi/BOOT/grubx64.efi /ldlinux.sys
0 OS detected =
Architecture/Host Info
CPU architecture: 64-bit
Live-session OS is Ubuntu 64-bit (Boot-Repair-Disk 64bit 20200604, bionic,
x86_64)
= UEFI =
BIOS is EFI-compatible, and is setup in EFI-mode for this live-session.
SecureBoot disabled.
efibootmgr -v
BootCurrent:
Timeout: 0 seconds
BootOrder: ,2001,2003,2002
Boot* Linpus lite
HD(1,MBR,0x428c8a7,0x800,0x1e35800)/File(\EFI\Boot\grubx64.efi)RC
Boot0007* EFI Network 0 for IPv4 (54-E1-AD-6F-12-36)
PciRoot(0x0)/Pci(0x14,0x0)/Pci(0x0,0x0)/MAC(54e1ad6f1236,0)/IPv4(0.0.0.00.0.0.0,0,0)RC
Boot0008* EFI Network 0 for IPv6 (54-E1-AD-6F-12-36)
PciRoot(0x0)/Pci(0x14,0x0)/Pci(0x0,0x0)/MAC(54e1ad6f1236,0)/IPv6([::]:<->[::]:,0,0)RC
Boot2001* EFI USB DeviceRC
Boot2002* EFI DVD/CDROM RC
Boot2003* EFI Network RC
= Drive/Partition Info =
Disks info: __
Partitions info (1/3): ___
Partitions info (2/3): ___
Partitions info (3/3): ___
fdisk -l (filtered): _
Disk sda: 111.8 GiB, 120034123776 bytes, 234441648 sectors
Disk identifier: B79E9BD6-815D-4C1C-A6AD-8F3FB1AC130C
Disk sdb: 232.9 GiB, 250059350016 bytes, 488397168 sectors
Disk identifier: 62764C30-4F79-400D-9AB4-09BD0F3BDEA7
Disk sdc: 15.1 GiB, 16219373568 bytes, 31678464 sectors
Disk identifier: 0x0428c8a7
Boot Start End Sectors Size Id Type
sdc1 * 2048 31678463 31676416 15.1G c W95 FAT32 (LBA)
Disk zram0: 973.3 MiB, 1020526592 bytes, 249152 sectors
Disk zram1: 973.3 MiB, 1020526592 bytes, 249152 sectors
Disk zram2: 973.3 MiB, 1020526592 bytes, 249152 sectors
Disk zram3: 973.3 MiB, 1020526592 bytes, 249152 sectors
parted -lm (filtered): ___
sda:120GB:scsi:512:512:gpt:ATA ADATA SU650:;
sdb:250GB:scsi:512:512:gpt:ATA Hitachi HTS54322:;
sdc:16.2GB:scsi:512:512:msdos:SRT USB:;
1:1049kB:16.2GB:16.2GB:fat32::boot, lba;
zram3:1021MB:unknown:4096:4096:loop:Unknown:;
1:0.00B:1021MB:1021MB:linux-swap(v1)::;
zram1:1021MB:unknown:4096:4096:loop:Unknown:;
1:0.00B:1021MB:1021MB:linux-swap(v1)::;
zram2:1021MB:unknown:4096:4096:loop:Unknown:;
1:0.00B:1021MB:1021MB:linux-swap(v1)::;
zram0:1021MB:unknown:4096:4096:loop:Unknown:;
1:0.00B:1021MB:1021MB:linux-swap(v1)::;
blkid (filtered):
NAME FSTYPE UUID PARTUUID
LABEL PARTLABEL
sda
sdb
sdc
└─sdc1 vfat E25F-A2F70428c8a7-01
BOOT-REPAIR
zram0
zram1
zram2
zram3
df (filtered):
[Bug 1898383] [NEW] tcsh filename pattern matching fails
Public bug reported: TCSH filename pattern matching bug -- To reproduce: 1) Make a subdirectory 2) cd to that subdirectory 3) create or touch the files x1 x2 x3 x4 x5 x6 x7 x8 and x9 4) execute the command: "echo x[7-9]" You will see all the files echo, NOT just x7 x8 and x9... /bin/sh and /bin/bash still do this correctly... but tcsh seems broken! Description:Ubuntu 20.04.1 LTS Release:20.04 tcsh: Installed: 6.21.00-1 Candidate: 6.21.00-1 Version table: *** 6.21.00-1 500 500 http://archive.ubuntu.com/ubuntu focal/universe amd64 Packages 500 http://us.archive.ubuntu.com/ubuntu focal/universe amd64 Packages 100 /var/lib/dpkg/status ** Affects: tcsh (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/1898383 Title: tcsh filename pattern matching fails To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tcsh/+bug/1898383/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1886148] Re: failure to boot groovy daily
S5000PSL - usb creator fails to boot using groovy daily build 9/12, 9/13. Works normally with unetbootin. Daily build did boot perhaps a week or 10 days ago. (Installer failed & crashed when 'something else/ grub bios boot only .. no efi .. but that's another issue. 'Something else' did work when I manually created both a efi and legacy bios partition, even though the efi partition was a waste of space. (gpt partition format). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1886148 Title: failure to boot groovy daily To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-cdimage/+bug/1886148/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1883040] Re: groovy daily won't boot anymore on some older BIOS boxes
This is still an issue 9/13/20, ubuntu mate groovy daily build. pre- uefi server won't boot w/ubuntu usb creator, works with unetbootin. Whatever the change was, it happened within the last 10 days or so. An earlier daily build did boot on that same machine without trouble. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1883040 Title: groovy daily won't boot anymore on some older BIOS boxes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-cdimage/+bug/1883040/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1883040] Re: groovy daily won't boot anymore on some older BIOS boxes
server was bare-metal S5000PSL -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1883040 Title: groovy daily won't boot anymore on some older BIOS boxes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-cdimage/+bug/1883040/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1894902] [NEW] 2 apparmor items missing for 'groovy'
Public bug reported: need to add ~# cat /etc/apparmor.d/local/usr.sbin.ntpd /run/systemd/userdb/io.systemd.Machine wr, /etc/ssl/openssl.cnf r, otherwise you get Sep 8 16:07:44 noc4 kernel: [ 1843.949193] audit: type=1400 audit(1599599264.140:52): apparmor="DENIED" operation="connect" profile="/usr/sbin/ntpd" name="/run/systemd/userdb/io.systemd.Machine" pid=16851 comm="ntpd" requested_mask="wr" denied_mask="wr" fsuid=0 ouid=0 Sep 8 16:11:22 noc4 kernel: [ 2062.263356] audit: type=1400 audit(1599599482.449:138): apparmor="DENIED" operation="open" profile="/usr/sbin/ntpd" name="/etc/ssl/openssl.cnf" pid=17639 comm="ntpd" requested_mask="r" denied_mask="r" fsuid=0 ouid=0 ** Affects: ntpsec (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/1894902 Title: 2 apparmor items missing for 'groovy' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ntpsec/+bug/1894902/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1894868] [NEW] groovy installer crashes on non-efi capable systems
Public bug reported: Attempting to install Groovy using cd image. Normal until bootloader install. The system is not EFI capable (older server, some VMs). Installer advises without EFI the system will crash, etc. Though there is a grub/bios partition, and a btrfs install proceeded normally up till the installer bootloader complaint. After choosing 'continue anyway' and being told I'd have to install a boot loader myself, the installer crashed with what you see in this report. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: ubiquity 20.10.9 ProcVersionSignature: Ubuntu 5.8.0-18.19-generic 5.8.4 Uname: Linux 5.8.0-18-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu45 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.452 Date: Tue Sep 8 10:47:39 2020 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu-mate.seed maybe-ubiquity quiet splash --- LiveMediaBuild: Ubuntu-MATE 20.10 "Groovy Gorilla" - Alpha amd64 (20200907) RebootRequiredPkgs: linux-image-5.8.0-18-generic linux-base SourcePackage: grub-installer UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: grub-installer (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug groovy ubiquity-20.10.9 ubuntu-mate -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1894868 Title: groovy installer crashes on non-efi capable systems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1894868/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1885632] Re: Focal requires tls > mariadb rev
Otto, thanks for the repeated reminder. Kindly note upstream includes a ubuntu repo that fixes this problem. Interested people can get the answer to this problem by following this link: https://downloads.mariadb.org/mariadb/repositories/#distro=Ubuntu_release=focal --ubuntu_focal=digitalocean-sfo=10.5 As of this writing, the steps to fix this bug without waiting or relying on Ubuntu/Canonical is: sudo apt-get install software-properties-common sudo apt-key adv --fetch-keys 'https://mariadb.org/mariadb_release_signing_key.asc' sudo add-apt-repository 'deb [arch=amd64,arm64,ppc64el] http://sfo1.mirrors.digitalocean.com/mariadb/repo/10.5/ubuntu focal main' Otto, with that you can close this report. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1885632 Title: Focal requires tls > mariadb rev To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mariadb-10.3/+bug/1885632/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1893152] Re: random hang/Kernel oops on sleep
.0 - dmi.chassis.asset.tag: No Asset Tag - dmi.chassis.type: 10 - dmi.chassis.vendor: Micro-Star International Co., Ltd. - dmi.chassis.version: N/A - dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrE1541IMS.108:bd05/05/2020:svnMicro-StarInternationalCo.,Ltd.:pnGE66Raider10SFS:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-1541:rvrREV1.0:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrN/A: - dmi.product.family: GE - dmi.product.name: GE66 Raider 10SFS - dmi.product.sku: 1541.1 - dmi.product.version: REV:1.0 - dmi.sys.vendor: Micro-Star International Co., Ltd. + Random freeze on laptop machine, when trying to sleep (normal power- + save/timed sleep mechanism). The machine would not respond to anything + except a hard press of the power button. The attached log output was + recorded at the time of the attempted sleep, indicating a kernel oops. + There are a lot of Nvidia references, so not sure if it's the Nvidia + driver, kernel or both. This is Ubunty 20.04.1 with the latest kernel + 5(Ubuntu 5.4.0-42.46-generic 5.4.44 )and Nvidia river 440.100 ** Changed in: linux (Ubuntu) Assignee: (unassigned) => Harry Bear (harrybear310) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1893152 Title: random hang/Kernel oops on sleep To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1893152/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1893152] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1893152/+attachment/5405012/+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/1893152 Title: random hang/Kernel oops on sleep To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1893152/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1893152] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1893152/+attachment/5405006/+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/1893152 Title: random hang/Kernel oops on sleep To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1893152/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1893152] RfKill.txt
apport information ** Attachment added: "RfKill.txt" https://bugs.launchpad.net/bugs/1893152/+attachment/5405016/+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/1893152 Title: random hang/Kernel oops on sleep To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1893152/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1893152] Lspci-vt.txt
apport information ** Attachment added: "Lspci-vt.txt" https://bugs.launchpad.net/bugs/1893152/+attachment/5405007/+files/Lspci-vt.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1893152 Title: random hang/Kernel oops on sleep To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1893152/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1893152] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1893152/+attachment/5405013/+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/1893152 Title: random hang/Kernel oops on sleep To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1893152/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1893152] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1893152/+attachment/5405008/+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/1893152 Title: random hang/Kernel oops on sleep To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1893152/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1893152] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1893152/+attachment/5405018/+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/1893152 Title: random hang/Kernel oops on sleep To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1893152/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1893152] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1893152/+attachment/5405017/+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/1893152 Title: random hang/Kernel oops on sleep To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1893152/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1893152] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1893152/+attachment/5405011/+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/1893152 Title: random hang/Kernel oops on sleep To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1893152/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1893152] Lsusb-v.txt
apport information ** Attachment added: "Lsusb-v.txt" https://bugs.launchpad.net/bugs/1893152/+attachment/5405010/+files/Lsusb-v.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1893152 Title: random hang/Kernel oops on sleep To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1893152/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1893152] Lsusb-t.txt
apport information ** Attachment added: "Lsusb-t.txt" https://bugs.launchpad.net/bugs/1893152/+attachment/5405009/+files/Lsusb-t.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1893152 Title: random hang/Kernel oops on sleep To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1893152/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1893152] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1893152/+attachment/5405005/+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/1893152 Title: random hang/Kernel oops on sleep To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1893152/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1893152] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1893152/+attachment/5405004/+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/1893152 Title: random hang/Kernel oops on sleep To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1893152/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1893152] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1893152/+attachment/5405014/+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/1893152 Title: random hang/Kernel oops on sleep To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1893152/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1893152] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1893152/+attachment/5405015/+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/1893152 Title: random hang/Kernel oops on sleep To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1893152/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1893152] Re: random hang/Kernel oops on sleep
apport information ** Tags added: apport-collected focal ** Description changed: - Random freeze on laptop machine, when trying to sleep (normal power- - save/timed sleep mechanism). The machine would not respond to anything - except a hard press of the power button. The attached log output was - recorded at the time of the attempted sleep, indicating a kernel oops. - There are a lot of Nvidia references, so not sure if it's the Nvidia - driver, kernel or both. This is Ubunty 20.04.1 with the latest kernel - 5(Ubuntu 5.4.0-42.46-generic 5.4.44 )and Nvidia river 440.100 + Random freeze on laptop machine, when trying to sleep (normal power-save/timed sleep mechanism). The machine would not respond to anything except a hard press of the power button. The attached log output was recorded at the time of the attempted sleep, indicating a kernel oops. There are a lot of Nvidia references, so not sure if it's the Nvidia driver, kernel or both. This is Ubunty 20.04.1 with the latest kernel 5(Ubuntu 5.4.0-42.46-generic 5.4.44 )and Nvidia river 440.100 + --- + ProblemType: Bug + ApportVersion: 2.20.11-0ubuntu27.8 + Architecture: amd64 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/controlC1: emdubp 1966 F pulseaudio + /dev/snd/controlC0: emdubp 1966 F pulseaudio + CasperMD5CheckResult: skip + CurrentDesktop: ubuntu:GNOME + DistroRelease: Ubuntu 20.04 + InstallationDate: Installed on 2020-08-21 (6 days ago) + InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) + MachineType: Micro-Star International Co., Ltd. GE66 Raider 10SFS + NonfreeKernelModules: nvidia_modeset nvidia + Package: linux (not installed) + ProcEnviron: + TERM=xterm-256color + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=en_US.UTF-8 + SHELL=/bin/bash + ProcFB: 0 i915drmfb + ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-42-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 + ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 + RelatedPackageVersions: + linux-restricted-modules-5.4.0-42-generic N/A + linux-backports-modules-5.4.0-42-generic N/A + linux-firmware1.187.2 + Tags: focal + Uname: Linux 5.4.0-42-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dip libvirt lpadmin lxd plugdev sambashare sudo + _MarkForUpload: True + dmi.bios.date: 05/05/2020 + dmi.bios.vendor: American Megatrends Inc. + dmi.bios.version: E1541IMS.108 + dmi.board.asset.tag: Default string + dmi.board.name: MS-1541 + dmi.board.vendor: Micro-Star International Co., Ltd. + dmi.board.version: REV:1.0 + dmi.chassis.asset.tag: No Asset Tag + dmi.chassis.type: 10 + dmi.chassis.vendor: Micro-Star International Co., Ltd. + dmi.chassis.version: N/A + dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrE1541IMS.108:bd05/05/2020:svnMicro-StarInternationalCo.,Ltd.:pnGE66Raider10SFS:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-1541:rvrREV1.0:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrN/A: + dmi.product.family: GE + dmi.product.name: GE66 Raider 10SFS + dmi.product.sku: 1541.1 + dmi.product.version: REV:1.0 + dmi.sys.vendor: Micro-Star International Co., Ltd. ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1893152/+attachment/5405002/+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/1893152 Title: random hang/Kernel oops on sleep To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1893152/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1893152] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1893152/+attachment/5405003/+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/1893152 Title: random hang/Kernel oops on sleep To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1893152/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1893152] Re: random hang/Kernel oops on sleep
** Attachment added: "lspci-vnvn.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1893152/+attachment/5405000/+files/lspci-vnvn.log ** Description changed: Random freeze on laptop machine, when trying to sleep (normal power- save/timed sleep mechanism). The machine would not respond to anything - except a hard press of the power button. The attached kernel oops log - output was recorded in the logs at the time of the attempted sleep, - indicating a kernel oops. There are a lot of Nvidia references, so not - sure if it's the Nvidia driver, kernel or both. This is Ubunty 20.04.1 - with the latest kernel 5(Ubuntu 5.4.0-42.46-generic 5.4.44 )and Nvidia - river 440.100 + except a hard press of the power button. The attached output was + recorded in the logs at the time of the attempted sleep, indicating a + kernel oops. There are a lot of Nvidia references, so not sure if it's + the Nvidia driver, kernel or both. This is Ubunty 20.04.1 with the + latest kernel 5(Ubuntu 5.4.0-42.46-generic 5.4.44 )and Nvidia river + 440.100 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1893152 Title: random hang/Kernel oops on sleep To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1893152/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1893152] Re: random hang/Kernel oops on sleep
** Description changed: Random freeze on laptop machine, when trying to sleep (normal power- save/timed sleep mechanism). The machine would not respond to anything - except a hard press of the power button. The attached output was - recorded in the logs at the time of the attempted sleep, indicating a - kernel oops. There are a lot of Nvidia references, so not sure if it's - the Nvidia driver, kernel or both. This is Ubunty 20.04.1 with the - latest kernel 5(Ubuntu 5.4.0-42.46-generic 5.4.44 )and Nvidia river - 440.100 + except a hard press of the power button. The attached log output was + recorded at the time of the attempted sleep, indicating a kernel oops. + There are a lot of Nvidia references, so not sure if it's the Nvidia + driver, kernel or both. This is Ubunty 20.04.1 with the latest kernel + 5(Ubuntu 5.4.0-42.46-generic 5.4.44 )and Nvidia river 440.100 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1893152 Title: random hang/Kernel oops on sleep To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1893152/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1893152] [NEW] random hang/Kernel oops on sleep
Public bug reported: Random freeze on laptop machine, when trying to sleep (normal power- save/timed sleep mechanism). The machine would not respond to anything except a hard press of the power button. The attached log output was recorded at the time of the attempted sleep, indicating a kernel oops. There are a lot of Nvidia references, so not sure if it's the Nvidia driver, kernel or both. This is Ubunty 20.04.1 with the latest kernel 5(Ubuntu 5.4.0-42.46-generic 5.4.44 )and Nvidia river 440.100 ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1893152 Title: random hang/Kernel oops on sleep To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1893152/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1893152] Re: random hang/Kernel oops on sleep
** Attachment added: "kernel oops log output" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1893152/+attachment/5404999/+files/kerneloops.log ** Description changed: Random freeze on laptop machine, when trying to sleep (normal power- save/timed sleep mechanism). The machine would not respond to anything - except a hard press of the power button. The following was recorded in - the logs at the time of the attempted sleep, indicating a kernel oops. - There are a lot of Nvidia references, so not sure if it's the Nvidia - driver, kernel or both. This is Ubunty 20.04.1 with the latest kernel - 5(Ubuntu 5.4.0-42.46-generic 5.4.44 )and Nvidia river 440.100 + except a hard press of the power button. The attached kernel oops log + output was recorded in the logs at the time of the attempted sleep, + indicating a kernel oops. There are a lot of Nvidia references, so not + sure if it's the Nvidia driver, kernel or both. This is Ubunty 20.04.1 + with the latest kernel 5(Ubuntu 5.4.0-42.46-generic 5.4.44 )and Nvidia + river 440.100 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1893152 Title: random hang/Kernel oops on sleep To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1893152/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1892890] [NEW] The eggs were off and it hurts my belly.
Public bug reported: I bought some "posh" eggs, but when I ate them they were unhygienic. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.16.0-30-generic 3.16.0-30.40~14.04.1 ProcVersionSignature: Ubuntu 3.16.0-30.40~14.04.1-generic 3.16.7-ckt3 Uname: Linux 3.16.0-30-generic i686 ApportVersion: 2.14.1-0ubuntu3.7 Architecture: i386 CurrentDesktop: Unity Date: Tue Aug 25 14:37:28 2020 InstallationDate: Installed on 2020-08-25 (0 days ago) InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release i386 (20150218.1) SourcePackage: linux-lts-utopic UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-lts-utopic (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 trusty -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1892890 Title: The eggs were off and it hurts my belly. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-lts-utopic/+bug/1892890/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1885632] Re: Focal requires tls > mariadb rev
Thanks Otto. It would be an appreciated add-on to the bug reporting system if your firm would add a little alert when it accepts a bug submission to a package that's not in the 'main' repository so we users get a gentle reminder we ought not expect help of the sort the 'main' packages get. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1885632 Title: Focal requires tls > mariadb rev To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mariadb-10.3/+bug/1885632/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1886970] Re: should be warned if major installed package not in upgrade.
That's it? A conclusion with no reasons, no exploration of options? How about a check in the upgrade routine that makes a list of currently installed packages with no reverse dependencies, that do not appear in the new release repos, and warn the user if they consent to the upgrade those packages will either be left behind or go away? That sounds feasible, I suspect many other options would as well. I was hoping for a little more thought here, or at least a reason. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1886970 Title: should be warned if major installed package not in upgrade. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/1886970/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1883880] Re: fix non-8-bit x86 displacements breaking AVX512 builds on Bionic
Thanks Lukasz, Christian, Robie, Matthias, and the various robots and launchpad janitors: appreciate your help! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1883880 Title: fix non-8-bit x86 displacements breaking AVX512 builds on Bionic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/binutils/+bug/1883880/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1883880] Re: fix non-8-bit x86 displacements breaking AVX512 builds on Bionic
Hey Folks, Does the -proposed changes get automatically integrated to -updates after a certain time has passed, or does this require somebody to take action? It would be great to have this update rolled out to 18.04 before OVS 2.14 is released in a week or two. Regards, -Harry -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1883880 Title: fix non-8-bit x86 displacements breaking AVX512 builds on Bionic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/binutils/+bug/1883880/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1883880] Re: fix non-8-bit x86 displacements breaking AVX512 builds on Bionic
Hi All, I have enabled the bionic-proposed repo as described in link. OVS-master is used for testing, containing the build-time binutils bug check as described above. 1) Can confirm that old binutils version (2.30-21ubuntu1~18.04.3) had issue, and OVS was correctly DISabling AVX512. 2) Can confirm that with -proposed binutils (2.30-21ubuntu1~18.04.4), OVS build system is correctly ENabling AVX512 support, as linker checks are passing. After the configure step, I have tested OVS, running traffic and enabling the AVX512 optimizations. It is working as expected, with AVX512 instructions running in the datapath. I believe you have already added the "verification-done" and bionic versions Christian, so I'll not change the status... please let me know if I misunderstood the process. Thanks Robie & Christian for your support on this issue! -Harry -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1883880 Title: fix non-8-bit x86 displacements breaking AVX512 builds on Bionic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/binutils/+bug/1883880/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1886970] [NEW] should be warned if major installed package not in upgrade.
Public bug reported: The clear, simple pop-up graphic advising of a new long term release can lead to major upset with Ubuntu in a way that can be avoided, as follows: Just for the purpose of this wish: Let's call an installed package that provides a capability of interest to the user that's optional, that is to say not a dependency of anything, user-driven. If an installed 'user-driven' package is not available in a new long term release: it's reasonable to suppose an average user would be upset if, trusting the cheery notice of new LTS release won't do 'anything bad', their package-of-interest is mysteriously gone upon reboot. It's just a question of the extent to which Ubuntu wants to be friendly to folks who think it's too much to comprehend the zooming console screenfulls of 'lib*' and so forth being upgraded. We know some major packages (where 'major' means the user went out of their way to install it) arrive only as 'backports' for long term releases, so accepting the LTS until those arrive when the prior version is installed -- will be a loss. There are lots of potential 'right answers', I think the only wrong answer is 'do nothing'. I call this a bug because going along with the clear, obvious intention of the pop-up will in these cases leave the user worse off as their chosen optional package will be gone though you'd think that Ubuntu would have taken that into account before presenting the 'it's all ready!' notice. The case that bit me was freeipa-server, but there are many others. Just dealing with repeated notices on consoles and pop-ups making me go out of my way to turn them off seems, well, less user-friendly than the standard Ubuntu keeps elsewhere. ** Affects: update-manager (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/1886970 Title: should be warned if major installed package not in upgrade. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/1886970/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1878973] Re: clean focal install, crash report qemu-guest-agent
I agree. No issues here these many days. On 7/6/20 9:42 AM, Łukasz Zemczak wrote: > Ok, I think it's as good as it gets, waiting any longer won't make much > difference. Thank you for the verification - releasing! > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1878973 Title: clean focal install, crash report qemu-guest-agent To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1878973/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1883880] Re: fix non-8-bit x86 displacements breaking AVX512 builds on Bionic
Hi Christian, Thanks for the additional info! Confirm that with the PPA the proposed checks now pass: $ echo "vmovaps 0x40(,%rax,1),%zmm0" | as --64 -o avx.o && objdump -d avx.o | grep vmovaps 8: 0: 62 f1 7c 48 28 04 05vmovaps 0x40(,%rax,1),%zmm0 Also the proposed OVS automake build-system changes will enable avx512 correctly: checking binutils avx512 assembler checks passing... yes I'll wait for the SRU team to accept into proposed. Regards, -Harry -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1883880 Title: fix non-8-bit x86 displacements breaking AVX512 builds on Bionic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/binutils/+bug/1883880/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1883880] Re: fix non-8-bit x86 displacements breaking AVX512 builds on Bionic
Hey Folks, Apologies I'm not familiar with the SRU testing process. I'd like to help - have an 18.04 setup for testing here. Is there an easy way to add the test-build PPA and just do an apt update && apt install binutils? https://launchpad.net/~ci-train-ppa- service/+archive/ubuntu/4105/+packages Regards, -Harry -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1883880 Title: fix non-8-bit x86 displacements breaking AVX512 builds on Bionic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/binutils/+bug/1883880/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1885632] [NEW] Focal requires tls > mariadb rev has. ssl dead, websites down on upgrade
Public bug reported: Mariadb 10.3 as provided by Ubuntu and shipped in LTS is compiled against YaSSL version 2.4.4, which supports a maximum tls version of 1.1 as I understand it. See: https://ubuntuforums.org/showthread.php?t=2420831 Focal minimum tls requirement is higher, tls v1.2 as discussed here: https://discourse.ubuntu.com/t/default-to-tls-v1-2-in-all-tls-libraries- in-20-04-lts/12464/3 As a result, all attempts to use ssl that worked pre-focal now hit a hard failure with such as: ERROR 2026 (HY000): SSL connection error: The TLS connection was non- properly terminated. and via libraries: Unable to open database: SSL connection error: error:1408F10B:SSL routines:ssl3_get_record:wrong version number Upstream offers a focal repository, so hopefully this won't be a hard one to merge into standard Ubuntu, since basically without some fix SSL/TLS via mariadb is broken entirely on an LTS version -- and that for 5 years, as they say, needs a close look. I suspect there are other compatibility issues preventing it, but as 'upgrading to focal' killed several web servers -- some sort of pragmatic work-around needs doing. Until then: sudo apt-get install software-properties-common sudo apt-key adv --fetch-keys 'https://mariadb.org/mariadb_release_signing_key.asc' sudo add-apt-repository 'deb [arch=amd64,arm64,ppc64el] http://ftp.utexas.edu/mariadb/repo/10.5/ubuntu focal main' Hope this helps someone... ** Affects: mariadb-10.3 (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/1885632 Title: Focal requires tls > mariadb rev has. ssl dead, websites down on upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mariadb-10.3/+bug/1885632/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1605224] Re: at-spi-registryd.desktop not responding on shutdown
Still happening in clean focal install, mate desktop. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1605224 Title: at-spi-registryd.desktop not responding on shutdown To manage notifications about this bug go to: https://bugs.launchpad.net/at-spi/+bug/1605224/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1884980] Re: patch so apparmor complain->enforcing
Christian, Since to test whether the fix I provided was complete you'd have to install freeipa-server to see all the bloat from apparmor, then try the fix and tweak it that would be enough given the sample error message. But, since you asked, here's a zmore /var/log/syslog.7.gz | grep appa > It's quite small and incomplete, but 796k worth should be enough for you to accept this as a real thing I hope. This log was taken while sssd was in complain mode, not enforcing. Without that ssytemd drop in pushing sssd in complain, most of the 'allowed' would be 'denied', and of course normal operations would be impossible. ** Attachment added: "forChristianEhrhardt.log" https://bugs.launchpad.net/ubuntu/+source/sssd/+bug/1884980/+attachment/5387541/+files/forChristianEhrhardt.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1884980 Title: patch so apparmor complain->enforcing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sssd/+bug/1884980/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1885236] [NEW] focal upgrade python3.8 bugs
Public bug reported: Setting up python3-cephfs (15.2.1-0ubuntu2) ... /usr/lib/python3/dist-packages/ceph_volume_client.py:358: SyntaxWarning: "is not" with a literal. Did you mean "!="? group_id = group_id if group_id is not 'None' else None /usr/lib/python3/dist-packages/ceph_volume_client.py:381: SyntaxWarning: "is" with a literal. Did you mean "=="? readonly = True if access_level is 'r' else False /usr/lib/python3/dist-packages/ceph_volume_client.py:1102: SyntaxWarning: "is" with a literal. Did you mean "=="? unwanted_access_level = 'r' if want_access_level is 'rw' else 'rw' ** Affects: ceph (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/1885236 Title: focal upgrade python3.8 bugs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ceph/+bug/1885236/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1885235] [NEW] python 3.8 bugs in hplip / focal upgrade
Public bug reported: /usr/share/hplip/base/utils.py:2063: SyntaxWarning: "is" with a literal. Did you mean "=="? if weburl is "" or weburl is None: /usr/share/hplip/check-plugin.py:116: SyntaxWarning: "is" with a literal. Did you mean "=="? if log_level is 'debug': /usr/share/hplip/check.py:685: SyntaxWarning: "is not" with a literal. Did you mean "!="? if 'getfacl' not in g and '' is not g and 'file' not in g: /usr/share/hplip/installer/core_install.py:2037: SyntaxWarning: "is" with a literal. Did you mean "=="? if home_dir is "": /usr/share/hplip/ui5/devmgr_ext.py:15: SyntaxWarning: "is not" with a literal. Did you mean "!="? if self.latest_available_version is not "": /usr/share/hplip/ui5/devmgr_ext.py:37: SyntaxWarning: "is not" with a literal. Did you mean "!="? if self.latest_available_version is not "": ** Affects: hplip (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/1885235 Title: python 3.8 bugs in hplip / focal upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/hplip/+bug/1885235/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1884980] Re: patch so apparmor complain->enforcing
Seth, Thanks for the note! I've made the change. Harry Coin -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1884980 Title: patch so apparmor complain->enforcing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sssd/+bug/1884980/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1885061] [NEW] systemd drop in needed to allow krb5.log
Public bug reported: Kindly notice https://bugs.launchpad.net/ubuntu/+source/krb5/+bug/1885024 which won't be fixed in kerberos since freeipa changes the log destination. So freeipa needs to add a systemd drop in to allow the logging. krb5-kdc.service drop in: [Service] ReadWriteDirectories= /var/log ** Affects: freeipa (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/1885061 Title: systemd drop in needed to allow krb5.log To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/freeipa/+bug/1885061/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1885024] [NEW] systemd patch fixes: krb5kdc.log Read-only file system
Public bug reported: Jun 24 11:29:34 registry1 krb5kdc[1244]: Couldn't open log file /var/log/krb5kdc.log: Read-only file system can be fixed by adding ReadWriteDirectories= /var/log to the krb5-kdc.service unit ** Affects: krb5 (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/1885024 Title: systemd patch fixes: krb5kdc.log Read-only file system To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/krb5/+bug/1885024/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1884980] [NEW] patch so apparmor complain->enforcing
Public bug reported: Because /var/log/syslog gets bloated with sssd apparmor related messages, I put the following in /etc/apparmor.d/local/usr.sbin.sssd then I changed sssd from 'complain' to 'enforcing' mode. I put this on a heavy sssd vm running freeipa server that also is running the gui with mate. I can't promise I found all the cases, but I don't see any 'apparmor' messages in the logs on the freeipa servers after a couple days. signal (send) peer="/usr/sbin/sssd//null-/usr/libexec/sssd/sssd_pac", /usr/sbin/sssd ixr, /usr/libexec/sssd/sssd_be ixr, /etc/krb5.conf.d/** r, /etc/krb5.conf.d/ r, /etc/krb5.conf.d r, /etc/sssd r, /etc/sssd/ r, /etc/sssd/** r, /usr/share/sssd r, /usr/share/sssd/ r, /usr/share/sssd/** r, /usr/libexec/sssd/sssd_pac ixr, /etc/gss/mech.d/ r, /etc/gss/mech.d/** r, /usr/libexec/sssd/ldap_child ixr, dbus send bus="system" path="/org/freedesktop/systemd1" interface="org.freedesktop.systemd1.Manager" member="GetDynamicUsers", There are thousands of varied examples you'll see in the logs, generally along the lines of Jun 23 06:41:55 registry2 kernel: [56263.674613] audit: type=1400 audit(1592912515.202:2329356): apparmor="DENIED" operation="signal" profile="/usr/sbin/sssd" pid=1058 comm="sssd" requested_mask="send" denied_mask="send" signal=term peer="/usr/sbin/sssd//null-/usr/libexec/sssd/sssd_pac I'm not a 'deep interest' apparmor dev, no doubt the above list could be improved. HTH Harry ** Affects: sssd (Ubuntu) Importance: Undecided Status: New ** Tags: apparmor -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1884980 Title: patch so apparmor complain->enforcing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sssd/+bug/1884980/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1883880] Re: fix non-8-bit x86 displacements breaking AVX512 builds on Bionic
Proposed patch on OVS Mailing list to check status at configure time for OVS 2.14 using the method Bruce mentioned above: https://patchwork.ozlabs.org/project/openvswitch/patch/20200618165354.87787-7-harry.van.haa...@intel.com/ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1883880 Title: fix non-8-bit x86 displacements breaking AVX512 builds on Bionic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/binutils/+bug/1883880/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1883880] Re: fix non-8-bit x86 displacements breaking AVX512 builds on Bionic
Hi All, I contacted Christian to mention/report, just noting that here. Happy to test if we get an SRU, I'll get email notifications once I post this :) Regards, -Harry -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1883880 Title: fix non-8-bit x86 displacements breaking AVX512 builds on Bionic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/binutils/+bug/1883880/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1575053] Re: Please move the "$HOME/snap" directory to a less obtrusive location
@zyga Thank you! That's awesome! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1575053 Title: Please move the "$HOME/snap" directory to a less obtrusive location To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1575053/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1873325] Re: update-initramfs complains of missing amdgpu firmware files
This is plaguing my system as well. Doing updates gives the errors. Not sure I want to perform a get:clone due to the software I have loaded and that it seems to be an issue with the new kernel. update-initramfs: Generating /boot/initrd.img-5.4.0-37-generic W: Possible missing firmware /lib/firmware/amdgpu/navi12_vcn.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/arcturus_vcn.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/navi12_smc.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/arcturus_smc.bin for module amdgpu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1873325 Title: update-initramfs complains of missing amdgpu firmware files To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1873325/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1855784] Re: Intel Microcode 3.20191115.1ubuntu0.16.04.2 still hangs on warm reboot with Intel(R) Xeon(R) W-2125 CPUi
On 6/10/20 5:48 PM, Henrique de Moraes Holschuh wrote: > This has been reported to be fixed on very similar processors (with the > same microcode signature as yours) in the 20200609 microcode updates, > could you test them? > I see four versions on your webpage: two versions of 3.20200609.0ubuntu0.16.04.1 and two versions of 3.20200609.0ubuntu0.16.04.0. I downloaded all four and both versions of 3.20200609.0ubuntu0.16.04.1 compared without any differences AND both versions of 3.20200609.0ubuntu0.16.04.0 compared without any differences. So in spite of the statement on the web page that each of those versions had a different publishing time, the two versions of .1 seem to be the same and the two versions of .0 seem to be the same. So I tried BOTH versions and warm reboots DID work with either .0 or .1. I left my machine with 3.20200609.0ubuntu0.16.04.1 Let me know if I missed any version you wished me to test... Harry McGavran -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1855784 Title: Intel Microcode 3.20191115.1ubuntu0.16.04.2 still hangs on warm reboot with Intel(R) Xeon(R) W-2125 CPUi To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/intel-microcode/+bug/1855784/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1881611] [NEW] /usr/lib/python3/dist-packages/mysqlx/expr.py:972: SyntaxWarning: "is" with a literal. Did you mean "=="?
Public bug reported:
Setting up python3-mysql.connector (8.0.15-2build1) ...
/usr/lib/python3/dist-packages/mysqlx/expr.py:972: SyntaxWarning: "is" with a
literal. Did you mean "=="?
return "({0})".format(dimension[0]) if len(dimension) is 1 else \
/usr/lib/python3/dist-packages/mysqlx/statement.py:122: SyntaxWarning: "is"
with a literal. Did you mean "=="?
return (default_schema if len(temp) is 1 else temp[0].strip(quote),
Processing triggers for libc-bin (2.31-0ubuntu9) ...
Error: Timeout was reached
** Affects: mysql-connector-python (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/1881611
Title:
/usr/lib/python3/dist-packages/mysqlx/expr.py:972: SyntaxWarning: "is"
with a literal. Did you mean "=="?
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mysql-connector-python/+bug/1881611/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1873607] Re: systemd segv coredump, reboot/poweroff ignored.
No issues so far. Thanks for checking. On May 20, 2020 5:30:40 PM CDT, Dan Streetman <1873...@bugs.launchpad.net> wrote: >@hcoin I assume no more segfaults with the updated pkg? can we mark >this verified for eoan? > >-- >You received this bug notification because you are subscribed to the >bug >report. >https://bugs.launchpad.net/bugs/1873607 > >Title: > systemd segv coredump, reboot/poweroff ignored. > >Status in systemd: > Fix Released >Status in systemd package in Ubuntu: > Fix Released >Status in systemd source package in Bionic: > Fix Committed >Status in systemd source package in Eoan: > Fix Committed >Status in systemd source package in Focal: > Fix Committed >Status in systemd source package in Groovy: > Fix Released > >Bug description: > [impact] > > during systemctl daemon-reload, systemd sometimes segfaults while > serializing a service. > > [test case] > > problem is intermittent, but the upstream bug suggests a reproducer. > Also see original description. > > [regression potential] > > this adjusts serialization, so any regression would likely occur > during serialization/deserialization, e.g. at daemon-reload. > > [scope] > > This is needed for Bionic and later. > > this was introduced by commit e266c068b5597e18b2299f9c9d3ee6cf04198c41 > which is included starting in v234. The commit to fix it is > e9da62b18af647bfa73807e1c7fc3bfa4bb4b2ac which is not yet included in > any release. > > The PR to fix this is https://github.com/systemd/systemd/pull/15546 > > [other info] > >there is an additional PR that further avoids the error, but has not >yet been accepted, and may not be accepted as it may not be necessary. > https://github.com/systemd/systemd/pull/15370 > > [original description] > > Proximate syslog: > >Apr 18 16:26:56 gate2 rssmonitor.py[2001]: settings: Running: ip -all >netns del >Apr 18 16:26:56 gate2 systemd[1]: /lib/systemd/system/dbus.socket:4: >ListenStream= references a path below legacy directory /var/run/, >updating /var/run/dbus/system_bus_socket → /r > un/dbus/system_bus_socket; please update the unit file accordingly. >Apr 18 16:26:56 gate2 systemd[1]: /lib/systemd/system/sssd.service:11: >PIDFile= references a path below legacy directory /var/run/, updating >/var/run/sssd.pid → /run/sssd.pid; plea > se update the unit file accordingly. >Apr 18 16:26:56 gate2 systemd[1]: >/lib/systemd/system/oddjobd.service:6: PIDFile= references a path below >legacy directory /var/run/, updating /var/run/oddjobd.pid → >/run/oddjobd.p > id; please update the unit file accordingly. >Apr 18 16:26:56 gate2 systemd[1]: >/lib/systemd/system/fail2ban.service:12: PIDFile= references a path >below legacy directory /var/run/, updating >/var/run/fail2ban/fail2ban.pid → /r > un/fail2ban/fail2ban.pid; please update the unit file accordingly. >Apr 18 16:26:56 gate2 systemd[1]: >/lib/systemd/system/certmonger.service:6: PIDFile= references a path >below legacy directory /var/run/, updating /var/run/certmonger.pid → >/run/cer > tmonger.pid; please update the unit file accordingly. > Apr 18 16:26:56 gate2 systemd[1]: Reloading. >Apr 18 16:26:56 gate2 kernel: [ 454.966336] systemd[1]: segfault at 50 >ip 55946ed0d6f0 sp 7fff8409d210 error 4 in >systemd[55946ecb4000+ae000] >Apr 18 16:26:56 gate2 kernel: [ 454.966354] Code: a8 48 8b 75 a0 c7 45 >ac 00 00 00 00 48 8b 94 c7 a0 04 00 00 48 89 45 88 48 89 f0 48 39 d6 74 >17 66 2e 0f 1f 84 00 00 00 00 00 <48 > > 8b 40 50 83 45 ac 01 48 39 c2 75 f3 48 8b 45 a0 31 db 4c 8d 7d >Apr 18 16:26:56 gate2 rssmonitor.py[1213]: rssmain: Ran OK: systemctl >daemon-reload >Apr 18 16:26:57 gate2 rssmonitor.py[1213]: rssmain: Running: systemctl >enable rssmonitor.service > Apr 18 16:27:23 gate2 sssd[nss]: Enumeration requested but not enabled >Apr 18 16:27:24 gate2 kernel: [ 482.503042] printk: systemd: 43 output >lines suppressed due to ratelimiting >Apr 18 16:27:24 gate2 systemd[1]: Caught , dumped core as pid >2034. > > ProblemType: Bug > DistroRelease: Ubuntu 19.10 > Package: systemd 242-7ubuntu3.7 > ProcVersionSignature: Ubuntu 5.3.0-46.38-generic 5.3.18 > Uname: Linux 5.3.0-46-generic x86_64 > ApportVersion: 2.20.11-0ubuntu8.8 > Architecture: amd64 > Date: Sat Apr 18 18:09:06 2020 > InstallationDate: Installed on 2019-11-01 (169 days ago) >InstallationMedia: Ubuntu-MATE 19.10 "Eoan Ermine" - Release amd64 >(20191017) > Lsusb: > Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub > Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub > Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub > Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub > MachineType: QEMU Standard PC (i440FX + PIIX, 1996) > ProcEnviron: > SHELL=/bin/bash > LANG=en_US.UTF-8 > TERM=xterm-256color > XDG_RUNTIME_DIR= > PATH=(custom, no user) >ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.3.0-46-generic >root=UUID=82254a10-a9e1-4459-aba0-7876df48d9da ro rootflags=subvol=@ >quiet
[Bug 1879083] Re: default sssd.conf after ipa-client-install crashes sssd
With the line not commented, upon each and every startup in all cases one sees this: May 19 11:37:25 email1 systemd[1]: Starting SSSD NSS Service responder socket. May 19 11:37:25 email1 sssd_check_socket_activated_responders[72216]: (Tue May 19 11:37:12:251510 2020) [sssd] [main] (0x0010): Misconfiguration found for the nss responder. May 19 11:37:25 email1 sssd_check_socket_activated_responders[72216]: The nss responder has been configured to be socket-activated but it's still mentioned in the services' line in /etc/sssd/sssd.conf. May 19 11:37:25 email1 sssd_check_socket_activated_responders[72216]: Please, consider either adjusting your services' line in /etc/sssd/sssd.conf or disabling the nss's socket by calling: May 19 11:37:25 email1 sssd[pac]: Starting up May 19 11:37:25 email1 systemd[1]: Starting SSSD PAM Service responder private socket. May 19 11:37:25 email1 sssd_check_socket_activated_responders[72216]: "systemctl disable sssd-nss.socket" May 19 11:37:25 email1 sssd_check_socket_activated_responders[72218]: (Tue May 19 11:37:12:022884 2020) [sssd] [main] (0x0010): Misconfiguration found for the pam responder. May 19 11:37:25 email1 sssd_check_socket_activated_responders[72218]: The pam responder has been configured to be socket-activated but it's still mentioned in the services' line in /etc/sssd/sssd.conf. May 19 11:37:25 email1 sssd_check_socket_activated_responders[72218]: Please, consider either adjusting your services' line in /etc/sssd/sssd.conf or disabling the pam's socket by calling: May 19 11:37:25 email1 sssd[ssh]: Starting up May 19 11:37:25 email1 systemd[1]: sssd-pam-priv.socket: Control process exited, code=exited, status=17/n/a May 19 11:37:25 email1 sssd_check_socket_activated_responders[72218]: "systemctl disable sssd-pam.socket" May 19 11:37:25 email1 sssd[pam]: Starting up May 19 11:37:25 email1 systemd[1]: sssd-pam-priv.socket: Failed with result 'exit-code'. May 19 11:37:25 email1 sssd[sudo]: Starting up May 19 11:37:25 email1 systemd[1]: Failed to listen on SSSD PAM Service responder private socket. May 19 11:37:25 email1 sssd_check_socket_activated_responders[72224]: (Tue May 19 11:37:13:424695 2020) [sssd] [main] (0x0010): Misconfiguration found for the sudo responder. May 19 11:37:25 email1 sssd_check_socket_activated_responders[72224]: The sudo responder has been configured to be socket-activated but it's still mentioned in the services' line in /etc/sssd/sssd.conf. May 19 11:37:25 email1 sssd_check_socket_activated_responders[72224]: Please, consider either adjusting your services' line in /etc/sssd/sssd.conf or disabling the sudo's socket by calling: May 19 11:37:25 email1 systemd[1]: Dependency failed for SSSD PAM Service responder socket. May 19 11:37:25 email1 sssd_check_socket_activated_responders[72224]: "systemctl disable sssd-sudo.socket" May 19 11:37:25 email1 systemd[1]: sssd-pam.socket: Job sssd-pam.socket/start failed with result 'dependency'. May 19 11:37:25 email1 sssd_check_socket_activated_responders[72221]: (Tue May 19 11:37:13:671260 2020) [sssd] [main] (0x0010): Misconfiguration found for the ssh responder. May 19 11:37:25 email1 sssd_check_socket_activated_responders[72221]: The ssh responder has been configured to be socket-activated but it's still mentioned in the services' line in /etc/sssd/sssd.conf. May 19 11:37:25 email1 sssd_check_socket_activated_responders[72221]: Please, consider either adjusting your services' line in /etc/sssd/sssd.conf or disabling the ssh's socket by calling: May 19 11:37:25 email1 systemd[1]: sssd-nss.socket: Control process exited, code=exited, status=17/n/a May 19 11:37:25 email1 sssd_check_socket_activated_responders[72221]: "systemctl disable sssd-ssh.socket" May 19 11:37:25 email1 systemd[1]: sssd-nss.socket: Failed with result 'exit-code'. May 19 11:37:25 email1 sssd[nss]: Starting up With the line commented, one sees: May 19 11:41:05 email1 systemd[1]: Starting System Security Services Daemon... May 19 11:41:07 email1 sssd: Starting up May 19 11:41:07 email1 kernel: [270731.176590] kauditd_printk_skb: 23 callbacks suppressed May 19 11:41:07 email1 kernel: [270731.176594] audit: type=1400 audit(1589906467.911:65972): apparmor="ALLOWED" operation="exec" profile="/usr/sbin/sssd" name="/usr/libexec/sssd/sssd_be" pid=72354 comm="sssd" requested_mask="x" denied_mask="x" fsuid=0 ouid=0 target="/usr/sbin/sssd//null-/usr/libexec/sssd/sssd_be" May 19 11:41:07 email1 kernel: [270731.178959] audit: type=1400 audit(1589906467.911:65973): apparmor="ALLOWED" operation="file_mmap" profile="/usr/sbin/sssd//null-/usr/libexec/sssd/sssd_be" name="/usr/libexec/sssd/sssd_be" pid=72354 comm="sssd_be" requested_mask="r" denied_mask="r" fsuid=0 ouid=0 May 19 11:41:07 email1 kernel: [270731.179565] audit: type=1400 audit(1589906467.911:65974): apparmor="ALLOWED" operation="file_mmap" profile="/usr/sbin/sssd//null-/usr/libexec/sssd/sssd_be"
[Bug 1879083] [NEW] default sssd.conf after ipa-client-install crashes sssd
Public bug reported: Notice ipa-client-install creates /etc/sssd/sssd.conf but changes in the sssd process's socket approach calls for that file to change /etc/sssd.conf from ... [sssd] services = nss, pam, ssh, sud ... to [sssd] #services = nss, pam, ssh, sud otherwise the sssd service either won't start or complains. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: freeipa-client 4.8.6-1ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: MATE Date: Sat May 16 12:51:21 2020 InstallationDate: Installed on 2020-05-13 (2 days ago) InstallationMedia: Ubuntu-MATE 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: freeipa UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: freeipa (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1879083 Title: default sssd.conf after ipa-client-install crashes sssd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/freeipa/+bug/1879083/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1878994] Re: python3-yubico/focal: "is" with a literal. Did you mean "=="?
python3-yubico specifically, not python-yubico ** Package changed: ubuntu => python-yubico (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1878994 Title: python3-yubico/focal: "is" with a literal. Did you mean "=="? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-yubico/+bug/1878994/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1878994] [NEW] python3-yubico/focal: "is" with a literal. Did you mean "=="?
Public bug reported: Setting up python3-yubico (1.3.3-0.3) ... /usr/lib/python3/dist-packages/yubico/yubikey_config.py:478: SyntaxWarning: "is" with a literal. Did you mean "=="? if slot is 1: /usr/lib/python3/dist-packages/yubico/yubikey_config.py:483: SyntaxWarning: "is" with a literal. Did you mean "=="? elif slot is 2: /usr/lib/python3/dist-packages/yubico/yubikey_usb_hid.py:288: SyntaxWarning: "is" with a literal. Did you mean "=="? if mode is 'nand': /usr/lib/python3/dist-packages/yubico/yubikey_usb_hid.py:294: SyntaxWarning: "is" with a literal. Did you mean "=="? elif mode is 'and': /usr/lib/python3/dist-packages/yubico/yubikey_usb_hid.py:306: SyntaxWarning: "is" with a literal. Did you mean "=="? if mode is 'nand': ** Affects: python-yubico (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/1878994 Title: python3-yubico/focal: "is" with a literal. Did you mean "=="? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-yubico/+bug/1878994/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
