[Bug 2054810] Re: Adding bpf to CONFIG_LSM in linux kernel
Hi Joseph - I just wanted to check in and see how things are going. Is there anything I can do to help? Happy to test out some kernel builds if needed. Thanks! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2054810 Title: Adding bpf to CONFIG_LSM in linux kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2054810/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1818239] Re: scheduler: build failure high negative weighting
I'm at a tad late (5+ years after the last comment), but in case it helps, we just ran into a situation where a user (not cloud admin) exhausted their IP allocations in a user-defined subnet, which caused an error in the nova-compute.log: NoMoreFixedIps: No fixed IP addresses available for network: 62c7b2e2-4406-4dda-9a01-f0ec623335d4 which caused the BuildFailureWeigher to offset the weight by -100. This was in a Stein cluster, so quite old. A newer version may have this disabled by default, but we had to manually disable it. Regardless, it caused all other tenants' VM deployments to fail since every compute node that tried to deploy the above VM resulted in the above error, causing each compute node to be assigned a large negative weight. Just wanted to mention our experience in case it helped someone else who was searching for the problem. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1818239 Title: scheduler: build failure high negative weighting To manage notifications about this bug go to: https://bugs.launchpad.net/charm-nova-cloud-controller/+bug/1818239/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2064128] [NEW] installing Adsys package and running realm command does not install all missing packages
Public bug reported: When I run "Realm discover" command it reports what packages are required. I rechecked this with a new install in a VM. The samba- common-bin package is not installed. I run the "realm join" and the package is still not installed. eric@Ubuntu-AD-22-04B:~$ sudo realm discover MYDC.MYDOMAIN.local [sudo] password for eric: MYDOMAIN.local type: kerberos realm-name: MYDOMAIN.LOCAL domain-name: MYDOMAIN.local configured: no server-software: active-directory client-software: sssd required-package: sssd-tools required-package: sssd required-package: libnss-sss required-package: libpam-sss required-package: adcli required-package: samba-common-bin eric@Ubuntu-AD-22-04B:~$ sudo realm join MYDC.MYDOMAIN.local Password for Administrator: eric@Ubuntu-AD-22-04B:~$ sudo realm discover MYDC.MYDOMAIN.local MYDOMAIN.local type: kerberos realm-name: MYDOMAIN.LOCAL domain-name: MYDOMAIN.local configured: kerberos-member server-software: active-directory client-software: sssd required-package: sssd-tools required-package: sssd required-package: libnss-sss required-package: libpam-sss required-package: adcli required-package: samba-common-bin login-formats: %U@MYDOMAIN.local login-policy: allow-realm-logins eric@Ubuntu-AD-22-04B:~$ sudo apt policy samba-common-bin samba-common-bin: Installed: (none) Candidate: 2:4.15.13+dfsg-0ubuntu1.6 Version table: 2:4.15.13+dfsg-0ubuntu1.6 500 500 http://us.archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 2:4.15.13+dfsg-0ubuntu1.5 500 500 http://security.ubuntu.com/ubuntu jammy-security/main amd64 Packages 2:4.15.5~dfsg-0ubuntu5 500 500 http://us.archive.ubuntu.com/ubuntu jammy/main amd64 Packages eric@Ubuntu-AD-22-04B:~$ The other packages are present prior to the realm join command, I did not show that here for brevity. A developer indicated while discussing another bug that any required packages not installed should get installed during the "realm join" command. I will quote what he said here: "The realm command should be able to automatically figure out and install any required packages, for example if I run realm join to join a domain, the following packages will be automatically installed for me: 'sssd-tools', 'sssd', 'libnss-sss', 'libpam-sss', 'adcli'. So you shouldn't need to install them by hand." So should not samba-common-bin get installed as well? ** Affects: adsys (Ubuntu) Importance: Undecided Status: New ** Tags: adsys join realm -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2064128 Title: installing Adsys package and running realm command does not install all missing packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/adsys/+bug/2064128/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2064009] [NEW] audio device malfunctioning and crash
Public bug reported: Hi my audio device (Philips screen with sound) crashed after using it few hours. Its working badly (kind of distorsion) anytime, was working fine with 22.10 but works badly with debian 12 (same config). Thx I use a Philips screen with HDMI for image and sound Operating System: Kubuntu 24.04 KDE Plasma Version: 5.27.11 KDE Frameworks Version: 5.115.0 Qt Version: 5.15.13 Kernel Version: 6.8.0-31-generic (64-bit) Graphics Platform: X11 Processors: 8 × Intel® Core™ i7-4790S CPU @ 3.20GHz Memory: 15,5 GiB of RAM Graphics Processor: Mesa Intel® HD Graphics 4600 Manufacturer: Dell Inc. Product Name: OptiPlex 9020 System Version: 00 ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1 Uname: Linux 6.8.0-31-generic x86_64 ApportVersion: 2.28.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/seq:kub1580 F pipewire /dev/snd/controlC1: kub1582 F wireplumber /dev/snd/controlC0: kub1582 F wireplumber /dev/snd/controlC2: kub1582 F wireplumber CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Sun Apr 28 14:35:52 2024 InstallationDate: Installed on 2024-04-25 (3 days ago) InstallationMedia: Kubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240425.1) MachineType: Dell Inc. OptiPlex 9020 PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/30/2019 dmi.bios.release: 65.25 dmi.bios.vendor: Dell Inc. dmi.bios.version: A25 dmi.board.name: 0KC9NP dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 16 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA25:bd05/30/2019:br65.25:svnDellInc.:pnOptiPlex9020:pvr00:rvnDellInc.:rn0KC9NP:rvrA00:cvnDellInc.:ct16:cvr:sku05A4: dmi.product.name: OptiPlex 9020 dmi.product.sku: 05A4 dmi.product.version: 00 dmi.sys.vendor: Dell Inc. ** Affects: ubuntu Importance: Undecided Status: New ** Tags: amd64 apport-bug noble -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2064009 Title: audio device malfunctioning and crash To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/2064009/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1285444] Re: Login Successful, Desktop Never Loads
Same issue with Secure boot enable and file system encrypted. The only workaround i find was at the login screen toggle to shell Crtl Alt F3, then login and manually launch the gnome (startx) to see what was wrong.The error was xf86enableio failed to enable io ports -03ff operation. Something wrong in the configuration file perhaps linked with the use of a dual screen configuration. So sudo apt install ubuntu- desktop will allow to run gnome ( without tweaks from canonical). The only problem is that in the x.conf there is a leak of definition for the second screen but i think it's a know bug. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1285444 Title: Login Successful, Desktop Never Loads To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/at-spi2-core/+bug/1285444/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2024377] Re: Adsys can't fetch GPOs
ALL, I am also interested in this. Have the same problems. sssd install worked and Active Directory user login to Ubuntu 22.04.06 LTS fine. But then adsys broke it and had to disable with pam-auth-update. We would like to be able to use the extended GPOs from adsys. Wondering about when it might be released. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2024377 Title: Adsys can't fetch GPOs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/adsys/+bug/2024377/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2054810] Re: Adding bpf to CONFIG_LSM in linux kernel
Joseph - thanks for looking into this. Please let me know if I can be of assistance. I'd be happy to test out the corresponding changes on my end. Just let me know - thank you!! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2054810 Title: Adding bpf to CONFIG_LSM in linux kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2054810/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1447968] Re: ImageMagick is missing JPEG2000 support (needs to be built with openjpeg)
It is April 2024 and I am having trouble getting ImageMagick to convert
JP2 files. Has this problem really been fixed or is just broken again?
I don't see jp2 or J2K listed in the delegates.
PHP Fatal error: Uncaught ImagickException: no decode delegate for this image
format `J2K' @ error/constitute.c/ReadImage/572 in /home/eric/convert-test.php:7
Stack trace:
#0 /home/eric/convert-test.php(7): Imagick->readimage()
#1 {main}
thrown in /home/eric/convert-test.php on line 7
Current versions are:
ImageMagick 7.1.1-31 (Beta) Q16-HDRI x86_64 dd459b01f:20240407
https://imagemagick.org
Features: Cipher DPC HDRI Modules OpenMP(4.5)
Delegates (built-in): jbig jpeg ltdl lzma tiff x xml zlib
Compiler: gcc (9.4)
PHP 7.4.3-4ubuntu2.20 (cli) (built: Feb 21 2024 13:54:34) ( NTS )
Ubuntu 20.04.6 LTS Release:20.04
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1447968
Title:
ImageMagick is missing JPEG2000 support (needs to be built with
openjpeg)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/imagemagick/+bug/1447968/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2054810] Re: Adding bpf to CONFIG_LSM in linux kernel
Can Ubuntu please consider addressing this as a part of the upcoming 24 LTS release? The ability to leverage LSM based BPF programs on Ubuntu out-of-the-box (ie. without having to update grub and rebooting) opens the door to a growing ecosystem of security tooling. There are major computing environments for which the community cannot control things like Grub settings - such as the Ubuntu images used by Microsoft (via GitHub Actions, Azure Pipelines), GitLab (via Jobs), AWS (via vanilla EC2 instances), etc. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2054810 Title: Adding bpf to CONFIG_LSM in linux kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2054810/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2057484] Re: kernel worker event freezes during traffic on iwlwifi
Issue still exists with 6.5.0-26 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2057484 Title: kernel worker event freezes during traffic on iwlwifi To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-6.5/+bug/2057484/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2058109] [NEW] Kernel 5.15.0-100 breaks Intel NIC
Public bug reported: From syslog: Mar 15 12:11:18 kvmMini systemd[1]: Starting Refresh fwupd metadata and update motd... Mar 15 12:11:18 kvmMini fwupdmgr[284042]: Updating lvfs Mar 15 12:11:18 kvmMini fwupdmgr[284042]: Downloading…: 0% Mar 15 12:11:19 kvmMini fwupdmgr[284042]: Idle…: 100% Mar 15 12:11:19 kvmMini fwupdmgr[284042]: Idle…: 100% Mar 15 12:11:19 kvmMini fwupdmgr[284042]: Downloading…: 100% Mar 15 12:11:19 kvmMini fwupdmgr[284042]: Downloading…: 0% Mar 15 12:11:19 kvmMini fwupdmgr[284042]: Downloading…: 1% Mar 15 12:11:19 kvmMini fwupdmgr[284042]: Downloading…: 2% Mar 15 12:11:19 kvmMini fwupdmgr[284042]: Downloading…: 3% ...trimmed content Mar 15 12:11:19 kvmMini fwupdmgr[284042]: Downloading…: 97% Mar 15 12:11:19 kvmMini fwupdmgr[284042]: Downloading…: 98% Mar 15 12:11:19 kvmMini fwupdmgr[284042]: Idle…: 100% Mar 15 12:11:19 kvmMini fwupdmgr[284042]: Idle…: 100% Mar 15 12:11:20 kvmMini fwupdmgr[284042]: Successfully downloaded new metadata: 0 local devices supported Mar 15 12:11:20 kvmMini systemd[1]: fwupd-refresh.service: Deactivated successfully. Mar 15 12:11:20 kvmMini systemd[1]: Finished Refresh fwupd metadata and update motd. Mar 15 12:17:01 kvmMini CRON[284549]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly) Mar 15 12:23:59 kvmMini kernel: [3519186.337746] x86/split lock detection: #AC: CPU 0/KVM/2230725 took a split_lock trap at address: 0xf80746442fb3 Mar 15 12:26:49 kvmMini kernel: [3519356.515727] x86/split lock detection: #AC: CPU 0/KVM/2230725 took a split_lock trap at address: 0xf80746442fb3 Mar 15 13:05:00 kvmMini systemd[1]: run-docker-runtime\x2drunc-moby-5ac73dacfde5bc72437e376d9f1d536f9da1ec70ebdb172d498c0f14b2a79bc4-runc.5pHMXa.mount: Deactivated successfully. Mar 15 13:07:48 kvmMini kernel: [3521815.001961] x86/split lock detection: #AC: CPU 0/KVM/279304 took a split_lock trap at address: 0xf80521c42fb3 Mar 15 13:17:01 kvmMini CRON[289583]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly) Mar 15 13:20:49 kvmMini kernel: [3522596.527060] x86/split lock detection: #AC: CPU 0/KVM/2230725 took a split_lock trap at address: 0xf80746442fb3 Mar 15 13:30:01 kvmMini systemd[1]: run-docker-runtime\x2drunc-moby-5ac73dacfde5bc72437e376d9f1d536f9da1ec70ebdb172d498c0f14b2a79bc4-runc.I79KlX.mount: Deactivated successfully. Mar 15 13:43:22 kvmMini kernel: [3523948.983970] x86/split lock detection: #AC: CPU 0/KVM/279304 took a split_lock trap at address: 0xf80521c42fb3 Mar 15 13:53:22 kvmMini kernel: [3524549.046156] x86/split lock detection: #AC: CPU 0/KVM/1774 took a split_lock trap at address: 0xf8041de42fb3 Mar 15 14:07:33 kvmMini systemd[1]: run-docker-runtime\x2drunc-moby-5ac73dacfde5bc72437e376d9f1d536f9da1ec70ebdb172d498c0f14b2a79bc4-runc.K8Zq9M.mount: Deactivated successfully. Mar 15 14:17:01 kvmMini CRON[294744]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly) Mar 15 14:20:03 kvmMini kernel: [3526150.403065] e1000e :00:1f.6 eno2: Detected Hardware Unit Hang: Mar 15 14:20:03 kvmMini kernel: [3526150.403065] TDH <9f> Mar 15 14:20:03 kvmMini kernel: [3526150.403065] TDT <9> Mar 15 14:20:03 kvmMini kernel: [3526150.403065] next_to_use <9> Mar 15 14:20:03 kvmMini kernel: [3526150.403065] next_to_clean<9e> Mar 15 14:20:03 kvmMini kernel: [3526150.403065] buffer_info[next_to_clean]: Mar 15 14:20:03 kvmMini kernel: [3526150.403065] time_stamp <1348a0aab> Mar 15 14:20:03 kvmMini kernel: [3526150.403065] next_to_watch<9f> Mar 15 14:20:03 kvmMini kernel: [3526150.403065] jiffies <1348a0bb0> Mar 15 14:20:03 kvmMini kernel: [3526150.403065] next_to_watch.status <0> Mar 15 14:20:03 kvmMini kernel: [3526150.403065] MAC Status <40080083> Mar 15 14:20:03 kvmMini kernel: [3526150.403065] PHY Status <796d> Mar 15 14:20:03 kvmMini kernel: [3526150.403065] PHY 1000BASE-T Status <3800> Mar 15 14:20:03 kvmMini kernel: [3526150.403065] PHY Extended Status<3000> Mar 15 14:20:03 kvmMini kernel: [3526150.403065] PCI Status <10> Mar 15 14:20:05 kvmMini kernel: [3526152.391042] e1000e :00:1f.6 eno2: Detected Hardware Unit Hang: Mar 15 14:20:05 kvmMini kernel: [3526152.391042] TDH <9f> Mar 15 14:20:05 kvmMini kernel: [3526152.391042] TDT <9> Mar 15 14:20:05 kvmMini kernel: [3526152.391042] next_to_use <9> Mar 15 14:20:05 kvmMini kernel: [3526152.391042] next_to_clean<9e> Mar 15 14:20:05 kvmMini kernel: [3526152.391042] buffer_info[next_to_clean]: Mar 15 14:20:05 kvmMini kernel: [3526152.391042] time_stamp <1348a0aab> Mar 15 14:20:05 kvmMini kernel: [3526152.391042] next_to_watch<9f> Mar 15 14:20:05 kvmMini kernel: [3526152.391042] jiffies <1348a0da1> Mar 15 14:20:05 kvmMini kernel: [3526152.391042] next_to_watch.status <0> Mar 15 14:20:05 kvmMini kernel: [3526152.391042] MAC Status
[Bug 2057484] Re: kernel worker event freezes during traffic on iwlwifi
Forum post with someone else with same issue: https://askubuntu.com/questions/1507282/ubuntu-22-04-4-wifi-became- unstable-after-some-system-update-and-maybe-install -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2057484 Title: kernel worker event freezes during traffic on iwlwifi To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-6.5/+bug/2057484/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2057484] Re: kernel worker event freezes during traffic on iwlwifi
dmesg output showing crashes of module / call trace [ 1384.485249] Intel(R) Wireless WiFi driver for Linux [ 1384.493042] iwlwifi :3d:00.0: Detected crf-id 0x2001910, cnv-id 0x2001910 wfpm id 0x8000 [ 1384.49] iwlwifi :3d:00.0: PCI dev 272b/00f4, rev=0x472, rfid=0x112200 [ 1384.499749] iwlwifi :3d:00.0: api flags index 2 larger than supported by driver [ 1384.499774] iwlwifi :3d:00.0: TLV_FW_FSEQ_VERSION: FSEQ Version: 0.0.4.125 [ 1384.500287] iwlwifi :3d:00.0: loaded firmware version 83.ec13314b.0 gl-c0-fm-c0-83.ucode op_mode iwlmvm [ 1384.517456] iwlwifi :3d:00.0: Detected Intel(R) TBD Bz device, REV=0x472 [ 1384.517545] thermal thermal_zone9: failed to read out thermal zone (-61) [ 1384.547211] iwlwifi :3d:00.0: WRT: Invalid buffer destination [ 1384.795043] iwlwifi :3d:00.0: loaded PNVM version 8443a58d [ 1384.902439] iwlwifi :3d:00.0: base HW address: a0:b3:39:35:db:df [ 1385.009224] iwlwifi :3d:00.0 wlp61s0f0: renamed from wlan0 [ 1385.099513] iwlwifi :3d:00.0: WRT: Invalid buffer destination [ 1385.462168] iwlwifi :3d:00.0: Registered PHC clock: iwlwifi-PTP, with index: 1 [ 1389.504547] wlp61s0f0: authenticate with 10:27:f5:b4:9a:3a [ 1389.516781] wlp61s0f0: send auth to 10:27:f5:b4:9a:3a (try 1/3) [ 1389.534341] wlp61s0f0: authenticated [ 1389.537849] wlp61s0f0: associate with 10:27:f5:b4:9a:3a (try 1/3) [ 1389.539896] wlp61s0f0: RX AssocResp from 10:27:f5:b4:9a:3a (capab=0x1011 status=0 aid=13) [ 1389.547795] wlp61s0f0: associated [ 1389.590986] wlp61s0f0: Limiting TX power to 30 (30 - 0) dBm as advertised by 10:27:f5:b4:9a:3a [ 1411.216084] [ cut here ] [ 1411.216093] Invalid rxb from HW 0 [ 1411.216133] WARNING: CPU: 3 PID: 3525 at drivers/net/wireless/intel/iwlwifi/pcie/rx.c:1489 iwl_pcie_rx_handle+0x3ce/0x640 [iwlwifi] [ 1411.216236] Modules linked in: iwlmvm iwlwifi ccm xfrm_user xfrm_algo twofish_generic twofish_avx_x86_64 twofish_x86_64_3way twofish_x86_64 twofish_common serpent_avx2 serpent_avx_x86_64 serpent_sse2_x86_64 serpent_generic blowfish_generic blowfish_x86_64 blowfish_common cast5_avx_x86_64 cast5_generic cast_common des_generic libdes camellia_generic camellia_aesni_avx2 camellia_aesni_avx_x86_64 camellia_x86_64 xcbc md4 l2tp_ppp l2tp_netlink l2tp_core ip6_udp_tunnel udp_tunnel pppox rfcomm cmac algif_hash algif_skcipher af_alg xt_CHECKSUM xt_MASQUERADE xt_conntrack ipt_REJECT nf_reject_ipv4 xt_tcpudp nft_compat nft_chain_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 nf_tables nfnetlink bridge stp llc bnep snd_hda_codec_hdmi snd_sof_pci_intel_cnl snd_sof_intel_hda_common soundwire_intel snd_sof_intel_hda_mlink soundwire_cadence snd_sof_intel_hda snd_sof_pci snd_sof_xtensa_dsp snd_ctl_led snd_sof snd_sof_utils snd_soc_hdac_hda snd_hda_ext_core snd_soc_acpi_intel_match snd_soc_acpi snd_hda_codec_realtek [ 1411.216387] soundwire_generic_allocation soundwire_bus snd_hda_codec_generic snd_soc_core snd_compress ac97_bus snd_pcm_dmaengine snd_hda_intel dell_rbtn mei_pxp binfmt_misc mei_hdcp snd_intel_dspcfg mac80211 snd_intel_sdw_acpi joydev intel_rapl_msr snd_hda_codec dell_laptop nls_iso8859_1 snd_hda_core snd_hwdep intel_tcc_cooling x86_pkg_temp_thermal libarc4 intel_powerclamp snd_pcm coretemp snd_seq_midi snd_seq_midi_event dell_wmi uvcvideo dell_smm_hwmon snd_rawmidi btusb videobuf2_vmalloc btrtl kvm_intel uvc btbcm dell_smbios snd_seq videobuf2_memops btintel processor_thermal_device_pci_legacy dcdbas rapl cmdlinepart input_leds videobuf2_v4l2 dell_wmi_sysman snd_seq_device btmtk processor_thermal_device snd_timer qcserial intel_cstate ledtrig_audio intel_wmi_thunderbolt serio_raw dell_wmi_descriptor wmi_bmof firmware_attributes_class mxm_wmi bluetooth videodev qmi_wwan processor_thermal_rfim spi_nor processor_thermal_mbox cdc_wdm cfg80211 snd mei_me videobuf2_common usb_wwan mtd processor_thermal_rapl usbnet [ 1411.216541] ecdh_generic ee1004 mii usbserial mc soundcore hid_multitouch mei ecc intel_rapl_common intel_soc_dts_iosf intel_pch_thermal int3403_thermal mac_hid nvidia_uvm(PO) int340x_thermal_zone intel_hid int3400_thermal acpi_thermal_rel acpi_pad sparse_keymap sch_fq_codel kvmgt mdev vfio_iommu_type1 vfio iommufd kvm irqbypass msr parport_pc ppdev lp parport efi_pstore ip_tables x_tables autofs4 btrfs blake2b_generic raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear nvidia_drm(PO) nvidia_modeset(PO) nvidia(PO) i915 drm_buddy i2c_algo_bit ttm drm_display_helper crct10dif_pclmul crc32_pclmul cec polyval_clmulni hid_generic polyval_generic rc_core ghash_clmulni_intel sha256_ssse3 drm_kms_helper nvme sha1_ssse3 aesni_intel rtsx_pci_sdmmc intel_lpss_pci nvme_core ahci ucsi_acpi crypto_simd i2c_i801 spi_intel_pci intel_lpss thunderbolt psmouse drm e1000e cryptd spi_intel i2c_smbus typec_ucsi xhci_pci rtsx_pci libahci nvme_common i2c_hid_acpi [ 1411.216760]
[Bug 2057484] Re: kernel worker event freezes during traffic on iwlwifi
** Attachment added: "perf record with lockup going o already during whole profile session" https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-6.5/+bug/2057484/+attachment/5755388/+files/perf.data.gz -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2057484 Title: kernel worker event freezes during traffic on iwlwifi To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-6.5/+bug/2057484/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2057484] Re: kernel worker event freezes during traffic on iwlwifi
** Attachment added: "perf record -a -g" https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-6.5/+bug/2057484/+attachment/5755387/+files/perf.data.gz -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2057484 Title: kernel worker event freezes during traffic on iwlwifi To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-6.5/+bug/2057484/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2057484] [NEW] kernel worker event freezes during traffic on iwlwifi
Public bug reported: With traffic on Intel Wifi 7 BE200 card, For a while kernel enter 100% cpu usage on a worker event thread and kworker/0:0-events_freezable is in D state. System highly unresponsive during this time. Happens in 6.5.0-25, does not happen in 6.5.0-17 Description:Ubuntu 22.04.4 LTS Release:22.04 Installed: 6.5.0-25.25~22.04.1 Candidate: 6.5.0-25.25~22.04.1 Version table: *** 6.5.0-25.25~22.04.1 500 500 http://us.archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu jammy-security/main amd64 Packages 100 /var/lib/dpkg/status linux-modules-6.5.0-25-generic: Installed: 6.5.0-25.25~22.04.1 Candidate: 6.5.0-25.25~22.04.1 Version table: *** 6.5.0-25.25~22.04.1 500 500 http://us.archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu jammy-security/main amd64 Packages 100 /var/lib/dpkg/status filename: /lib/modules/6.5.0-25-generic/kernel/drivers/net/wireless/intel/iwlwifi/iwlwifi.ko license:GPL description:Intel(R) Wireless WiFi driver for Linux firmware: iwlwifi-100-5.ucode firmware: iwlwifi-1000-5.ucode firmware: iwlwifi-135-6.ucode firmware: iwlwifi-105-6.ucode firmware: iwlwifi-2030-6.ucode firmware: iwlwifi-2000-6.ucode firmware: iwlwifi-5150-2.ucode firmware: iwlwifi-5000-5.ucode firmware: iwlwifi-6000g2b-6.ucode firmware: iwlwifi-6000g2a-6.ucode firmware: iwlwifi-6050-5.ucode firmware: iwlwifi-6000-6.ucode firmware: iwlwifi-7265D-29.ucode firmware: iwlwifi-7265-17.ucode firmware: iwlwifi-3168-29.ucode firmware: iwlwifi-3160-17.ucode firmware: iwlwifi-7260-17.ucode firmware: iwlwifi-8265-36.ucode firmware: iwlwifi-8000C-36.ucode firmware: iwlwifi-9260-th-b0-jf-b0-46.ucode firmware: iwlwifi-9000-pu-b0-jf-b0-46.ucode firmware: iwlwifi-cc-a0-77.ucode firmware: iwlwifi-QuZ-a0-jf-b0-77.ucode firmware: iwlwifi-QuZ-a0-hr-b0-77.ucode firmware: iwlwifi-Qu-b0-jf-b0-77.ucode firmware: iwlwifi-Qu-c0-hr-b0-77.ucode firmware: iwlwifi-Qu-b0-hr-b0-77.ucode firmware: iwlwifi-ma-b0-mr-a0-83.ucode firmware: iwlwifi-ma-b0-gf4-a0-83.ucode firmware: iwlwifi-ma-b0-gf-a0-83.ucode firmware: iwlwifi-ma-b0-hr-b0-83.ucode firmware: iwlwifi-ma-a0-mr-a0-83.ucode firmware: iwlwifi-ma-a0-gf4-a0-83.ucode firmware: iwlwifi-ma-a0-gf-a0-83.ucode firmware: iwlwifi-ma-a0-hr-b0-83.ucode firmware: iwlwifi-ty-a0-gf-a0-83.ucode firmware: iwlwifi-so-a0-gf-a0-83.ucode firmware: iwlwifi-so-a0-hr-b0-83.ucode firmware: iwlwifi-so-a0-jf-b0-83.ucode firmware: iwlwifi-gl-c0-fm-c0-83.ucode firmware: iwlwifi-gl-b0-fm-b0-83.ucode firmware: iwlwifi-bz-a0-fm4-b0-83.ucode firmware: iwlwifi-bz-a0-fm-c0-83.ucode firmware: iwlwifi-bz-a0-fm-b0-83.ucode firmware: iwlwifi-bz-a0-gf4-a0-83.ucode firmware: iwlwifi-bz-a0-gf-a0-83.ucode firmware: iwlwifi-bz-a0-hr-b0-83.ucode firmware: iwlwifi-sc-a0-wh-a0-83.ucode firmware: iwlwifi-sc-a0-gf4-a0-83.ucode firmware: iwlwifi-sc-a0-gf-a0-83.ucode firmware: iwlwifi-sc-a0-hr-b0-83.ucode firmware: iwlwifi-sc-a0-hr-b0-83.ucode firmware: iwlwifi-sc-a0-fm-c0-83.ucode firmware: iwlwifi-sc-a0-fm-b0-83.ucode srcversion: CE34BB7E0E287E10FEC1E13 alias: pci:v8086dE440sv*sd*bc*sc*i* alias: pci:v8086d7740sv*sd*bc*sc*i* alias: pci:v8086dA840sv*sd*bc*sc*i* alias: pci:v8086d272Bsv*sd*bc*sc*i* alias: pci:v8086d2727sv*sd*bc*sc*i* alias: pci:v8086d7E40sv*sd*bc*sc*i* alias: pci:v8086d2729sv*sd*bc*sc*i* alias: pci:v8086d7F70sv*sd*bc*sc*i* alias: pci:v8086d54F0sv*sd*bc*sc*i* alias: pci:v8086d51F1sv*sd*bc*sc*i* alias: pci:v8086d51F1sv*sd*bc*sc*i* alias: pci:v8086d51F0sv*sd*bc*sc*i* alias: pci:v8086d7AF0sv*sd*bc*sc*i* alias: pci:v8086d7A70sv*sd*bc*sc*i* alias: pci:v8086d2725sv*sd*bc*sc*i* alias: pci:v8086d2723sv*sd*bc*sc*i* alias: pci:v8086dA0F0sv*sd*bc*sc*i* alias: pci:v8086d43F0sv*sd*bc*sc*i* alias: pci:v8086d4DF0sv*sd*bc*sc*i* alias: pci:v8086d3DF0sv*sd*bc*sc*i* alias: pci:v8086d34F0sv*sd*bc*sc*i* alias: pci:v8086d06F0sv*sd*bc*sc*i* alias: pci:v8086d02F0sv*sd*bc*sc*i* alias: pci:v8086dA370sv*sd*bc*sc*i* alias: pci:v8086d9DF0sv*sd*bc*sc*i* alias: pci:v8086d31DCsv*sd*bc*sc*i* alias: pci:v8086d30DCsv*sd*bc*sc*i* alias: pci:v8086d271Csv*sd*bc*sc*i* alias:
[Bug 1885756] Re: crasch in installation
grub-install/dev/sdb a échoué -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1885756 Title: crasch in installation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1885756/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2043299] Re: Linux 6.5 breaks Novation Components web MIDI application
Thank you Jonatan! I can confirm too : using Ubuntu mate 23.10 / 1.26.2. Kernel is Linux 6.5.0-21-generic x86_64 Chrome Version 122.0.6261.94 (Official Build) (64-bit) : no connection, time out Chrome Version 123.0.6312.22 (Official Build) beta (64-bit) : works just fine, circuit tracks is recognized, connected and midi works Hopefully they'll fast track the inclusion of those changes from beta to release, but in the meanwhile beta works fine so not a blocker anymore. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2043299 Title: Linux 6.5 breaks Novation Components web MIDI application To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2043299/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2043299] Re: Linux 6.5 breaks Novation Components web MIDI application
Same behavior here, using Ubuntu mate 23.10 / 1.26.2 and google chrome (from chrome .deb, not chromium or a snap or flatpak). Kernel is Linux 6.5.0-21-generic x86_64 The circuit tracks has firmware 1.15 (latest, from dec 2022), and the following script is run before hand as root to set the midi buffers (this is required with firmwares > 1.02 with the circuit tracks as newer firmwares use bigger chunks to speed up transmissions) #! /bin/bash echo "must be run as root" echo -n "current alsa midi OUT buffer size " cat /sys/module/snd_seq_midi/parameters/output_buffer_size echo 'setting alsa midi OUT buffer to 65535' echo "65536" > /sys/module/snd_seq_midi/parameters/output_buffer_size echo -n "current alsa midi IN buffer size " cat /sys/module/snd_seq_midi/parameters/input_buffer_size echo 'setting alsa midi IN buffer to 65535' echo "65536" > /sys/module/snd_seq_midi/parameters/input_buffer_size echo -n "new alsa midi IN buffer size" cat /sys/module/snd_seq_midi/parameters/input_buffer_size echo -n "new alsa midi OUT buffer size" cat /sys/module/snd_seq_midi/parameters/output_buffer_size Using Chrome, which worked before upgrading to 23.10, the novation components website attempts to connect ( webmidi is enabled/allowed in Chrome for this device), then times out. ( When starting Components in Firefox, the device doesn't show at all, but this is not new and din't work before upgrading to 23.10 either. ) I can connect to the device using components in chrome browser on an android device, so the circuit tracks and usb cable used are working as expected. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2043299 Title: Linux 6.5 breaks Novation Components web MIDI application To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2043299/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2055292] Re: tracker-extract-3 crashed with SIGSYS in epoll_wait()
*** This bug is a duplicate of bug 2055761 *** https://bugs.launchpad.net/bugs/2055761 ** This bug has been marked a duplicate of bug 2055761 tracker-extract-3 crashed with SIGSYS in epoll_wait() -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2055292 Title: tracker-extract-3 crashed with SIGSYS in epoll_wait() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tracker-miners/+bug/2055292/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2037767] Re: file-roller crashed with SIGSEGV in egg_tree_multi_drag_button_release_event()
*** This bug is a duplicate of bug 723841 *** https://bugs.launchpad.net/bugs/723841 ** This bug has been marked a duplicate of bug 723841 file-roller crashed with SIGSEGV in egg_tree_multi_drag_button_release_event() -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2037767 Title: file-roller crashed with SIGSEGV in egg_tree_multi_drag_button_release_event() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/file-roller/+bug/2037767/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2054150] Re: file-roller crashed with SIGSEGV in ???()
*** This bug is a duplicate of bug 723841 *** https://bugs.launchpad.net/bugs/723841 ** This bug is no longer a duplicate of bug 2037767 file-roller crashed with SIGSEGV in egg_tree_multi_drag_button_release_event() ** This bug has been marked a duplicate of bug 723841 file-roller crashed with SIGSEGV in egg_tree_multi_drag_button_release_event() -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2054150 Title: file-roller crashed with SIGSEGV in ???() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/file-roller/+bug/2054150/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2003864] Re: freshclam assert failure: *** stack smashing detected ***: terminated
I installed, in Ubuntu 23.04, the following packages from Debian bookworm: clamav, clamav-base, libclamav11 and clamav-freshclam, version 1.0.0+dfsg-6. There's no crash using libtfm1 version 0.13.1-1 from lunar. -- 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/2003864 Title: freshclam assert failure: *** stack smashing detected ***: terminated To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/clamav/+bug/2003864/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2003864] Re: freshclam assert failure: *** stack smashing detected ***: terminated
** Changed in: clamav (Ubuntu) Status: Confirmed => Invalid -- 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/2003864 Title: freshclam assert failure: *** stack smashing detected ***: terminated To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/clamav/+bug/2003864/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2003864] Re: freshclam assert failure: *** stack smashing detected ***: terminated
I can confirm this is a problem in libtfm. I installed libtfm1 (0.13-4.1) from kinetic repository. Freshclam runs correctly now: $ sudo dpkg -i Downloads/libtfm1_0.13-4.1_amd64.deb dpkg: warning: downgrading libtfm1:amd64 from 0.13.1-1 to 0.13-4.1 (Reading database ... 255083 files and directories currently installed.) Preparing to unpack .../libtfm1_0.13-4.1_amd64.deb ... Unpacking libtfm1:amd64 (0.13-4.1) over (0.13.1-1) ... Setting up libtfm1:amd64 (0.13-4.1) ... Processing triggers for libc-bin (2.36-0ubuntu4) ... $ sudo freshclam Tue Feb 14 13:57:52 2023 -> ClamAV update process started at Tue Feb 14 13:57:52 2023 Tue Feb 14 13:57:52 2023 -> daily database available for update (local version: 26759, remote version: 26812) Current database is 53 versions behind. Downloading database patch # 26760... Time:1.3s, ETA:0.0s [>]1.48KiB/1.48KiB ### LOTS OF DOWNLOADS Downloading database patch # 26812... Time:0.4s, ETA:0.0s [>] 14.29KiB/14.29KiB Tue Feb 14 13:58:21 2023 -> Testing database: '/var/lib/clamav/tmp.24bf72ffd7/clamav-2612b7e0fbdb3a18bf680780eff04d81.tmp-daily.cld' ... Tue Feb 14 13:58:26 2023 -> Database test passed. Tue Feb 14 13:58:26 2023 -> daily.cld updated (version: 26812, sigs: 2020880, f-level: 90, builder: raynman) Tue Feb 14 13:58:26 2023 -> main.cld database is up-to-date (version: 62, sigs: 6647427, f-level: 90, builder: sigmgr) Tue Feb 14 13:58:26 2023 -> bytecode.cld database is up-to-date (version: 333, sigs: 92, f-level: 63, builder: awillia2) Tue Feb 14 13:58:26 2023 -> !NotifyClamd: Can't find or parse configuration file /etc/clamav/clamd.conf ** Also affects: tomsfastmath (Ubuntu) Importance: Undecided Status: New ** Changed in: tomsfastmath (Ubuntu) Status: New => 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/2003864 Title: freshclam assert failure: *** stack smashing detected ***: terminated To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/clamav/+bug/2003864/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2003864] Re: freshclam assert failure: *** stack smashing detected ***: terminated
I submitted a bug report from a recently installed Ubuntu 23.04 (2023-02-10 08:19 daily live image). This time freshclam crashes with a segmentation fault. https://bugs.launchpad.net/ubuntu/+source/clamav/+bug/2006967 -- 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/2003864 Title: freshclam assert failure: *** stack smashing detected ***: terminated To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/clamav/+bug/2003864/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2003864] Re: freshclam assert failure: *** stack smashing detected ***: terminated
** Changed in: clamav (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/2003864 Title: freshclam assert failure: *** stack smashing detected ***: terminated To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/clamav/+bug/2003864/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2003864] Re: freshclam assert failure: *** stack smashing detected ***: terminated
This bug affects me, too. Further information requested by Paride Legovini: 1. What did you do to trigger it? Run "sudo freshclam" to update virus database or "clamscan /path/to/file" to scan a file. 2. Is it reproducible? Yes, it happens every time I run freshclam or clamscan. 3. Was clamav working fine before you upgraded to lunar? Yes. I upgraded to lunar back in October when its repo got available. I think this bug started in late December or early January. Commands output: $ sudo freshclam Fri Feb 10 09:31:41 2023 -> ClamAV update process started at Fri Feb 10 09:31:41 2023 Fri Feb 10 09:31:41 2023 -> daily database available for update (local version: 26759, remote version: 26808) Current database is 49 versions behind. Downloading database patch # 26760... Time:1.4s, ETA:0.0s [>]1.48KiB/1.48KiB *** stack smashing detected ***: terminated Aborted $ clamscan Downloads/AGDLIC-v6.1.0.exe LibClamAV Warning: ** LibClamAV Warning: *** The virus database is older than 7 days! *** LibClamAV Warning: *** Please update it as soon as possible.*** LibClamAV Warning: ** *** stack smashing detected ***: terminated Aborted (core dumped) Should I open a new bug report? -- 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/2003864 Title: freshclam assert failure: *** stack smashing detected ***: terminated To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/clamav/+bug/2003864/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1977464] [NEW] SSH authentication fails when used with gpg-agent
Public bug reported: When using gnupg-pkcs11-scd with gpg-agent for SSH authentication the following error is reported: sign_and_send_pubkey: signing failed for RSA "(none)" from agent: agent refused operation This problem is fixed in upstream gnupg-pkcs11-scd Bug Report: https://github.com/alonbl/gnupg-pkcs11-scd/issues/27 Merge request: https://github.com/alonbl/gnupg-pkcs11-scd/pull/28 I have experienced this problem on 20.04 and 22.04 Upstream has also released a new version that includes this and other bug fixes. Would be great to see all of the fixes brought into Ubuntu. ** Affects: gnupg-pkcs11-scd (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/1977464 Title: SSH authentication fails when used with gpg-agent To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnupg-pkcs11-scd/+bug/1977464/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1976201] Re: first time booting rpi2b crashed after setup wizard (location, timezone, login information)
Yes it's Ubuntu mate On Tue, May 31, 2022, 5:36 AM Dave Jones <1976...@bugs.launchpad.net> wrote: > Can you let me know which image you were trying to boot? The regular > ubuntu desktop image is arm64 only which wouldn't boot on a rev1.1 Pi 2B > board, so I'm guessing this *might* be Ubuntu MATE? > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1976201 > > Title: > first time booting rpi2b crashed after setup wizard (location, > timezone, login information) > > Status in ubiquity package in Ubuntu: > New > > Bug description: > no further information > > ProblemType: Bug > DistroRelease: Ubuntu 21.10 > Package: ubiquity 21.10.10 > ProcVersionSignature: Ubuntu 5.13.0-1009.10-raspi 5.13.14 > Uname: Linux 5.13.0-1009-raspi armv7l > ApportVersion: 2.20.11-0ubuntu71 > Architecture: armhf > CasperMD5CheckResult: unknown > Date: Sun May 29 22:07:03 2022 > ImageMediaBuild: 20211105 > SourcePackage: ubiquity > UbiquityDebug: > > UbiquitySyslog: > > UpgradeStatus: No upgrade log present (probably fresh install) > > To manage notifications about this bug go to: > > https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1976201/+subscriptions > > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1976201 Title: first time booting rpi2b crashed after setup wizard (location, timezone, login information) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1976201/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1976201] [NEW] first time booting rpi2b crashed after setup wizard (location, timezone, login information)
Public bug reported: no further information ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: ubiquity 21.10.10 ProcVersionSignature: Ubuntu 5.13.0-1009.10-raspi 5.13.14 Uname: Linux 5.13.0-1009-raspi armv7l ApportVersion: 2.20.11-0ubuntu71 Architecture: armhf CasperMD5CheckResult: unknown Date: Sun May 29 22:07:03 2022 ImageMediaBuild: 20211105 SourcePackage: ubiquity UbiquityDebug: UbiquitySyslog: UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ubiquity (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug armhf armhf-image impish oem-config raspi-image -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1976201 Title: first time booting rpi2b crashed after setup wizard (location, timezone, login information) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1976201/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1974230] [NEW] Negative cache results from dnsmasq do not include SOA as required in RFC2308
Public bug reported: RFC2308 states: 6 - Negative answers from the cache When a server, in answering a query, encounters a cached negative response it MUST add the cached SOA record to the authority section of the response with the TTL decremented by the amount of time it was stored in the cache. This allows the NXDOMAIN / NODATA response to time out correctly. The effect is that the negative cache results returned by dnsmasq cannot be cached by other resolvers such as systemd-resolved. A good example of why this is a problem: Two clients with systemd-resolved send DNS queries to dnsmasq for the same record The first one makes a query and gets NXDOMAIN with SOA. This results in systemd-resolved caching the negative result. The second client makes a query and gets NODATA without the SOA. This results in systemd-resolved not caching the negative result. Consider a domain name that only has an A record published. When connecting to that domain a lookup happens for the and A record. One can end up in a situation where systemd-resolved has the A record cached locally, but it still goes out to the network to perform the lookup only to get the same negative cache result that is missing the SOA I see this behavior in 18.04 and 22.04 First query to dnsmasq can be cached: dig @10.0.1.21 a.google.com ; <<>> DiG 9.16.1-Ubuntu <<>> @10.0.1.21 a.google.com ; (1 server found) ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 3107 ;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 1 ;; OPT PSEUDOSECTION: ; EDNS: version: 0, flags:; udp: 512 ;; QUESTION SECTION: ;a.google.com. IN A ;; AUTHORITY SECTION: google.com. 60 IN SOA ns1.google.com. dns-admin.google.com. 449437361 900 900 1800 60 ;; Query time: 15 msec ;; SERVER: 10.0.1.21#53(10.0.1.21) ;; WHEN: Thu May 19 15:00:12 EDT 2022 ;; MSG SIZE rcvd: 91 Cached response from dnsmasq cannot be cached: dig @10.0.1.21 a.google.com ; <<>> DiG 9.16.1-Ubuntu <<>> @10.0.1.21 a.google.com ; (1 server found) ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 61408 ;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 1 ;; OPT PSEUDOSECTION: ; EDNS: version: 0, flags:; udp: 4096 ;; QUESTION SECTION: ;a.google.com. IN A ;; Query time: 0 msec ;; SERVER: 10.0.1.21#53(10.0.1.21) ;; WHEN: Thu May 19 15:00:13 EDT 2022 ;; MSG SIZE rcvd: 41 ** Affects: dnsmasq (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/1974230 Title: Negative cache results from dnsmasq do not include SOA as required in RFC2308 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1974230/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1973322] Re: Bacula for 22.04/Jammy
Hello, Bacula 9.6.7 is pretty old, can you upgrade for the tests to 11.0.6 ? Thanks Eric Le mer. 18 mai 2022, 13:55, Alex Murray <1973...@bugs.launchpad.net> a écrit : > As can be seen at > https://launchpad.net/ubuntu/+source/bacula/+publishinghistory bacula > was removed from Ubuntu during the jammy development cycle as it failed > to compile: > > > FTBFS, removed from Debian testing, blocks libssl transition; Debian > bug #997139 > > The process to get this back into jammy would be a StableReleaseUpdate - > https://wiki.ubuntu.com/StableReleaseUpdates - so a version of bacula > which compiles on jammy would have to be prepared and then this > procedure can be followed to get it published back into Ubuntu 22.04 > LTS. > > -- > You received this bug notification because you are subscribed to bacula > in Ubuntu. > https://bugs.launchpad.net/bugs/1973322 > > Title: > Bacula for 22.04/Jammy > > Status in bacula package in Ubuntu: > Confirmed > > Bug description: > Hi, > > it looks like Bacula / bacula-client has been removed from > 22.04/Jammy, while it was and is still available for 21.04. > > Is there a chance to get it back in 22.04? That'd be really handy. > > Were there specific reasons to remove it? I couldn't find anything > useful / official so far. > > To manage notifications about this bug go to: > > https://bugs.launchpad.net/ubuntu/+source/bacula/+bug/1973322/+subscriptions > > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1973322 Title: Bacula for 22.04/Jammy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bacula/+bug/1973322/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1970943] Re: OpenVPN connection fails with smartcard provided private key; please update pkcs11-helper
Suffering from the same problem in 22.04 After applying just this change to the Ubuntu source openvpn works as expected: https://github.com/OpenSC/pkcs11-helper/commit/fba328fd7519833966712589be8fff419219277a -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1970943 Title: OpenVPN connection fails with smartcard provided private key; please update pkcs11-helper To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pkcs11-helper/+bug/1970943/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1874726] Re: GPG PKCS#11 error: "OpenPGP card not available: End of file"
Version 0.10.0 from upstream fixes numerous issues. https://github.com/alonbl/gnupg-pkcs11-scd/blob/master/ChangeLog I had to compile from upstream source to get this working on 20.04 and 22.04. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1874726 Title: GPG PKCS#11 error: "OpenPGP card not available: End of file" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnupg-pkcs11-scd/+bug/1874726/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1972026] [NEW] ua status incorrectly lists reboot required for pre-built FIPS cloud image
Public bug reported: Checking UA status on new Ubuntu 20.04 FIPS cloud image incorrectly lists "Reboot to FIPS kernel required" Deploy a cloud FIPS image such as https://azuremarketplace.microsoft.com/en- us/marketplace/apps/canonical.0001-com-ubuntu-pro-focal-fips After VM creation and booting perform: >lsb_release -rd Description:Ubuntu 20.04.4 LTS Release:20.04 >ua status SERVICE ENTITLED STATUSDESCRIPTION esm-apps yes enabled UA Apps: Extended Security Maintenance (ESM) esm-infra yes enabled UA Infra: Extended Security Maintenance (ESM) fips yes enabled NIST-certified core packages fips-updates yes disabled NIST-certified core packages with priority security updates livepatch yes n/a Canonical Livepatch service usg yes disabled Security compliance and audit tools NOTICES Reboot to FIPS kernel required Enable services with: ua enable Account: 61acb9fc-62f4-4ff7-b760- Subscription: 61acb9fc-62f4-4ff7-b760- Valid until: -12-31 00:00:00+00:00 Technical support level: essential >ua version u27.7~20.04.1 >cat /etc/cloud/build.info build_name: pro-fips-server serial: 20220215.1 After reboot, perform the same "ua status" command and the same notice "Reboot to FIPS kernel required" is displayed. However, FIPS kernel is loaded and UA shows enabled. --- >uname -a Linux temp-test-01 5.4.0-1022-azure-fips #22+fips1-Ubuntu SMP Mon Dec 13 01:12:55 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux --- Running apt shows no applicable updates available. - >apt-get update Hit:1 http://azure.archive.ubuntu.com/ubuntu focal InRelease Hit:2 http://azure.archive.ubuntu.com/ubuntu focal-updates InRelease Hit:3 http://azure.archive.ubuntu.com/ubuntu focal-backports InRelease Hit:4 http://azure.archive.ubuntu.com/ubuntu focal-security InRelease Get:5 https://esm.ubuntu.com/apps/ubuntu focal-apps-security InRelease [7484 B] Get:6 https://esm.ubuntu.com/apps/ubuntu focal-apps-updates InRelease [7432 B] Hit:7 https://esm.ubuntu.com/infra/ubuntu focal-infra-security InRelease Hit:8 https://esm.ubuntu.com/infra/ubuntu focal-infra-updates InRelease Hit:9 https://esm.ubuntu.com/fips/ubuntu focal InRelease Fetched 14.9 kB in 6s (2357 B/s) Reading package lists... Done root@temp-test-01:~# apt list --upgradeable Listing... Done libgcrypt20-hmac/focal 1.8.5-5ubuntu1.fips.1.4 amd64 [upgradable from: 1.8.5-5ubuntu1.fips.1.1] libgcrypt20/focal 1.8.5-5ubuntu1.fips.1.4 amd64 [upgradable from: 1.8.5-5ubuntu1.fips.1.1] snapd/focal-updates 2.54.3+20.04.1ubuntu0.3 amd64 [upgradable from: 2.54.3+20.04.1ubuntu0.2] Expected results: 1) ua status should properly report that a FIPS kernel is active. Is this a check that is failing? 2) lsb_release -rd should show that it is not just 20.04.4 LTS but 20.04.4 LTS FIPS Is this appropriate? FIPS is an enhancement of the mainstream LTS deployment. The more clear that it is a FIPS installation the better, no matter how you go about querying the system information. Is #1 seeing the results of #2 and thus reporting that a reboot to FIPS kernel is required? ** Affects: ubuntu-advantage-tools (Ubuntu) Importance: Undecided Status: New ** Tags: focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1972026 Title: ua status incorrectly lists reboot required for pre-built FIPS cloud image To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-advantage-tools/+bug/1972026/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1970663] Re: Tiny mouse cursor in firefox snap
Hi, this is a major show stopper for me. I cannot use Ubuntu 22.04 at all because of that. Even if I downgrade to 21.10, I will have to stay with that version forever, unless there is a plan to fix that issue in an upcoming version of Ubuntu. The mouse pointer in Firefox is too tiny and I always, constantly, loose track of it. I cannot accept the idea of lowering the whole screen resolution for that single application and it is too time consuming and frustrating to bypass the Ubuntu's packaging system to manually install Firefox from somewhere else. It's been years and years I'm literally fighting to be able to use my LCD screen at a native resolution and I'm so pissed off if I finally have to give up that I am more and more eady to stop using my computer. People can argue this has no importance, but I was told, since two years and more, that NOTHING I do or enjoy has importance. I need a solution, otherwise I cannot use Ubuntu anymore. I will have to switch back to Windows for the time being, but I really dislike that. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1970663 Title: Tiny mouse cursor in firefox snap To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1970663/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1952581] Re: ACPI Error: No handler for Region [VRTC]
I am being affected by this issue as well. My machine fails to boot at all, providing the following error after GRUB [0.39] ACPI Error: No handler for Region [VRTC] (b44dee92) [SystemCMOS] (20210730/euregion-130) [0.394449] ACPI Error: Region SystemCMOS (ID=5) has no handler (20210730/exfldio-261) [0.394457] ACPI Error: Aborting method N_SB.PCOO.LPCB.ECO.RTEC due to previous error (AE_HOT_EXIST) (20210730/psparse-529) [0.394460] ACPI Error: Aborting method N_SII.PCOO.LPCB.ECO._REG due to previous error (AE_MOT_EXIST) (20210730/psparse-529) [0.994991] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0) [0.995017] CPU: 2 PID: 1 Comm: swapper/0 Not tainted 5.15.0-25-generic #25-Ubuntu [0.995039] Hardware name: Razer Blade 17 (2022) - RZ09-0423/DI780, BIOS 1.06 01/27/2022 [0.995060] Call Trace: [0.995071] [0.995084] show_stack.0x52/0x58 [0.995105] dump_stack_lu1.0x4a/Ox5f [0.995126] dump_stack.0x10/0x12 [0.995143] panic.0x149/0x321 [0.995160] mount_block_root.0x144/0x1d9 [0.995182] mount_root.0x10c/Ox118 [0.995200] prepare_namespace.0x13f/Ox18d [0.995220] kernel_init_freeable.0x18c/Ox1b1 [0.995243] ? rest_init.0x100/0x100 [0.995264] kernel_init.0x1b/0x150 [0.995283] ? rest init.0x100/0x100 [0.995302] ret_from_fork.0x1f/0x30 [0.995324] [0.995471] Kernel Offset: 0x180 from Ox8100 (relocation range: Ox8000-Oxbfff) [0.995524] ---[ end Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0, 0) ]--- -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1952581 Title: ACPI Error: No handler for Region [VRTC] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1952581/+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
I just upgraded to 22.04, and was unpleasantly surprised to see ~/snap as a new directory in HOME. If there is no solution for this issue I will be switching back to Fedora. -- 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 1966499] Re: Recent 5.13 kernel has broken KVM support
This issue occurs in my environment with a Windows guest even without PCIe GPU passthrough: anopolsky@IS01209:~$ virsh dumpxml windows-primary |grep hostdev|wc -l 0 anopolsky@IS01209:~$ virsh dumpxml windows-primary |grep -A 4 '' -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1966499 Title: Recent 5.13 kernel has broken KVM support To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1966499/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1966499] Re: Recent 5.13 kernel has broken KVM support
I arrived at work this morning to find a frozen workstation with a full disk. This bug was one of two relevant search results, so I'm documenting the recovery steps I took here in case it will be helpful to others: 1. Held down the power button until the PC turned off. 2. Waited a few seconds and powered the PC back on. 3. On the grub menu, chose Advanced options for Ubuntu -> Ubuntu, with Linux 5.13.0-35-generic (recovery mode) and waited for the system to boot. 4. On the Recovery Menu, chose the root option and hit enter. 5. Ran the following: rm /var/log/kern.log # freed up about 800GB head -n 10 /var/log/syslog > /var/log/syslog.bak # saved a few copies of the error just in case rm /var/log/syslog # freed up another 800GB apt remove linux-image-5.13.0-37-generic linux-image-unsigned-5.13.0-37-generic # it was necessary to remove the second package because that's what apt tried to install when only the first one was specified reboot # temporary fix is complete 6. Allowed the system to boot normally without intervention. 7. Logged in, opened a terminal, and confirmed that the fix worked: uname -a # Expected output: Linux IS01209 5.13.0-35-generic #40~20.04.1-Ubuntu SMP Mon Mar 7 09:18:32 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux virsh list # Expected output: # Id Name State #- # 1my-windows-vm running # # Note: My Windows VM is configured to start on boot. For affected users who have a Windows VM that is not configured to start on boot, it may be necessary to start the VM manually before moving on to the next step. watch du -h /var/log/syslog /var/log/kern.log # Expected output: # Every 2.0s: du -h /var/... (hostname and date/time) # # 320K/var/log/syslog # 100K/var/log/kern.log # # Note: If those two files stay the same size or grow slowly, the fix worked. If those two files grow rapidly, the fix did not work. Note that the above steps will also uninstall the linux-generic-hwe-20.04 package, which will prevent future kernel updates. When this bug is resolved, I plan to run (and recommend that others run) `sudo apt install linux-generic-hwe-20.04` to resume kernel updates. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1966499 Title: Recent 5.13 kernel has broken KVM support To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1966499/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1966811] [NEW] list-oem-metapackages crashed with TypeError in any_oem_metapackages_installed(): 'apt_pkg.Cache' object is not iterable
Public bug reported: Crashed after restarting computer. Maybe during automatic check for updates. ProblemType: Crash DistroRelease: Ubuntu 22.04 Package: update-notifier-common 3.192.52 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon Mar 28 17:00:46 2022 ExecutablePath: /usr/lib/update-notifier/list-oem-metapackages InstallationDate: Installed on 2020-02-26 (760 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200225.4) InterpreterPath: /usr/bin/python3.10 PackageArchitecture: all ProcCmdline: /usr/bin/python3 /usr/lib/update-notifier/list-oem-metapackages Python3Details: /usr/bin/python3.10, Python 3.10.3, python3-minimal, 3.10.1-0ubuntu2 PythonArgs: ['/usr/lib/update-notifier/list-oem-metapackages'] PythonDetails: N/A SourcePackage: update-notifier Title: list-oem-metapackages crashed with TypeError in any_oem_metapackages_installed(): 'apt_pkg.Cache' object is not iterable UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip lpadmin lxd plugdev sambashare sudo vboxusers wireshark modified.conffile..etc.apt.apt.conf.d.10periodic: APT::Periodic::Update-Package-Lists "0"; APT::Periodic::Download-Upgradeable-Packages "0"; APT::Periodic::AutocleanInterval "0"; APT::Periodic::Unattended-Upgrade "0"; mtime.conffile..etc.apt.apt.conf.d.10periodic: 2020-03-01T14:31:08.864240 ** Affects: update-notifier (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-crash jammy need-duplicate-check ** Information type changed from Private to Public -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1966811 Title: list-oem-metapackages crashed with TypeError in any_oem_metapackages_installed(): 'apt_pkg.Cache' object is not iterable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/update-notifier/+bug/1966811/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1966502] [NEW] gjs-console crashed with SIGSEGV
Public bug reported: This crash happens when starting Gnome Extensions. ProblemType: Crash DistroRelease: Ubuntu 22.04 Package: gjs 1.72.0-1 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Mar 25 14:08:33 2022 ExecutablePath: /usr/bin/gjs-console InstallationDate: Installed on 2020-02-26 (757 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200225.4) ProcCmdline: /usr/bin/gjs /usr/share/gnome-shell/org.gnome.Extensions SegvAnalysis: Segfault happened at: 0x7f312f6ecfeb: mov(%rdi),%edi PC (0x7f312f6ecfeb) ok source "(%rdi)" (0x02a0) not located in a known VMA region (needed readable region)! destination "%edi" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: gjs StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so Title: gjs-console crashed with SIGSEGV UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip lpadmin lxd plugdev sambashare sudo vboxusers wireshark separator: ** Affects: gjs (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-crash jammy need-amd64-retrace ** Information type changed from Private to Public -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1966502 Title: gjs-console crashed with SIGSEGV To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gjs/+bug/1966502/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1964923] Re: list-oem-metapackages crashed with AttributeError in packages_for_modalias(): 'Cache' object has no attribute 'packages'
The patch in message #8 fixes this bug for me. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1964923 Title: list-oem-metapackages crashed with AttributeError in packages_for_modalias(): 'Cache' object has no attribute 'packages' To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1964923/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1966130] [NEW] xdg-desktop-portal crashed with SIGSEGV in g_cclosure_marshal_generic()
Public bug reported: This crash happens while starting Epiphany. Despite the crash, the browser seems to work correctly. ProblemType: Crash DistroRelease: Ubuntu 22.04 Package: xdg-desktop-portal 1.14.1-1 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Mar 23 17:58:47 2022 ExecutablePath: /usr/libexec/xdg-desktop-portal InstallationDate: Installed on 2020-02-26 (755 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200225.4) ProcCmdline: /usr/libexec/xdg-desktop-portal SegvAnalysis: Segfault happened at: 0x564faad74421: mov0x8(%rax),%rcx PC (0x564faad74421) ok source "0x8(%rax)" (0x0008) not located in a known VMA region (needed readable region)! destination "%rcx" ok Stack memory exhausted (SP below stack segment) SegvReason: reading NULL VMA Signal: 11 SourcePackage: xdg-desktop-portal StacktraceTop: ?? () ?? () ?? () from /lib/x86_64-linux-gnu/libffi.so.8 ?? () from /lib/x86_64-linux-gnu/libffi.so.8 g_cclosure_marshal_generic () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: xdg-desktop-portal crashed with SIGSEGV in g_cclosure_marshal_generic() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip lpadmin lxd plugdev sambashare sudo vboxusers wireshark separator: ** Affects: xdg-desktop-portal (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-crash jammy ** Information type changed from Private to Public -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1966130 Title: xdg-desktop-portal crashed with SIGSEGV in g_cclosure_marshal_generic() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xdg-desktop-portal/+bug/1966130/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1965459] [NEW] Remmina actively refusing VNC connection Ubuntu 22.04
Public bug reported: Recently installed the developer version of Ubuntu 22.04 on my laptop with the following specifications. Lenovo-ideapad-330-15ARR -- OS: Ubuntu Jammy Jellyfish (development branch) x86_64 Host: 81D2 Lenovo ideapad 330-15ARR Kernel: 5.15.0-22-generic Uptime: 1 hour, 5 mins Packages: 2580 (dpkg), 12 (snap) Shell: bash 5.1.16 Resolution: 1366x768 Terminal: /dev/pts/0 CPU: AMD Ryzen 3 2200U with Radeon Vega Mobile Gfx (4) @ 2.500GHz GPU: AMD ATI Radeon Vega Series / Radeon Vega Mobile Series Memory: 980MiB / 7493MiB org.remmina.Remmina - SNAP Build - 1.4.25 (git v1.4.25) Desktop Environment: GNOME Connecting to: Ubuntu Jammy Jellyfish (development branch) x86_64 Connecting via: VNC Description: After installing Ubuntu Jammy Jellyfish (development branch) x86_64 I tested the VNC connections that I have set up for my machines. My laptop is able to connect to any system with Ubuntu 20.04.4 LTS installed on it. However, when trying to use Remmina to VNC into my laptop with Jammy Jellyfish installed from another machine with Ubuntu 20.04.4 LTS installed the connection is actively refused. I have already checked to make sure that all sharing features are turned on along with the UFW firewall configured to allow connections through port 5900. Also uninstalled Remmina, and reinstalled it on my laptop with Jammy Jellyfish installed. Still get the same issue. The exact error message that comes in in Remmina is "Unable to connect to VNC server" when everything is configured correctly on my laptop with Jammy Jellyfish installed. Just for the sake of experimentation, I set up Jammy Jellyfish on another machine of mine to troubleshoot the issue further. When trying to connect from one machine with Jammy Jellyfish installed on it to another machine with Jammy Jellyfish installed on it;I still get the same error "Unable to connect to VNC server" within the Remmina software. In summary, any machine of mine with Jammy Jellyfish is able to VNC into any machine with Ubuntu 20.04.4 LTS installed on it. No machine with 20.04.4 LTS is able to VNC into another machine with Jammy Jellyfish installed. VNC connections in Remmina between machines with Jammy Jellyfish installed are unable to connect to each other. ** Affects: remmina (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/1965459 Title: Remmina actively refusing VNC connection Ubuntu 22.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/remmina/+bug/1965459/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1946525] Re: Removable media are not mounted automatically
Noob to Ubuntu... I have a similar problem with a U.S. Robotics USR5637 modem. lsusb and usb-devices both show the device, and dmesg shows it being recognized, however it does not show up in /dev as ttyACM*. Running 21.10 on a Raspberry Pi 4. The device works as expected with 20.04.3 LTS also on a Pi 4. I tried Henrik Dahle's work around of reinstalling fuse simply because he had luck with it, but no joy. The device is also not created with it installed during a reboot. lsusb: Bus 001 Device 008: ID 0baf:0303 U.S. Robotics USR5637 56K Faxmodem usb-devices: T: Bus=01 Lev=04 Prnt=06 Port=01 Cnt=01 Dev#= 8 Spd=480 MxCh= 0 D: Ver= 2.00 Cls=02(commc) Sub=00 Prot=00 MxPS=64 #Cfgs= 1 P: Vendor=0baf ProdID=0303 Rev=02.00 S: Manufacturer=U.S.Robotics S: Product=USB Modem S: SerialNumber=002 C: #Ifs= 2 Cfg#= 2 Atr=80 MxPwr=360mA I: If#=0x0 Alt= 0 #EPs= 1 Cls=02(commc) Sub=02 Prot=01 Driver=(none) I: If#=0x1 Alt= 0 #EPs= 2 Cls=0a(data ) Sub=00 Prot=00 Driver=(none) dmesg: [ 127.376952] usb 1-1.2.4.1: new high-speed USB device number 7 using xhci_hcd [ 127.585699] usb 1-1.2.4.1: New USB device found, idVendor=0baf, idProduct=0303, bcdDevice= 2.00 [ 127.585739] usb 1-1.2.4.1: New USB device strings: Mfr=1, Product=2, SerialNumber=10 [ 127.585757] usb 1-1.2.4.1: Product: USB Modem [ 127.585771] usb 1-1.2.4.1: Manufacturer: U.S.Robotics [ 127.585784] usb 1-1.2.4.1: SerialNumber: 002 [ 127.747138] kauditd_printk_skb: 518 callbacks suppressed [ 127.747159] audit: type=1400 audit(1646439492.316:597): apparmor="DENIED" operation="open" profile="snap.chromium.chromium" name="/sys/devices/platform/scb/fd50.pcie/pci:00/:00:00.0/:01:00.0/usb1/1-1/1-1.2/1-1.2.4/1-1.2.4.1/busnum" pid=2810 comm="ThreadPoolForeg" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0 [ 127.747191] audit: type=1400 audit(1646439492.316:598): apparmor="DENIED" operation="open" profile="snap.chromium.chromium" name="/sys/devices/platform/scb/fd50.pcie/pci:00/:00:00.0/:01:00.0/usb1/1-1/1-1.2/1-1.2.4/1-1.2.4.1/devnum" pid=2810 comm="ThreadPoolForeg" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1946525 Title: Removable media are not mounted automatically To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/udisks2/+bug/1946525/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1960996] Re: [sru] sos upstream 4.3
For full changelog reference: This bug was fixed in the package sosreport - 4.3-1ubuntu2 --- sosreport (4.3-1ubuntu2) jammy; urgency=medium * d/p/0003-mention-sos-help-in-sos-manpage.patch: Fix sos-help manpage. -- Eric Desrochers Wed, 16 Feb 2022 13:05:13 -0500 --- sosreport (4.3-1ubuntu1) jammy; urgency=medium * New 4.3 upstream. (LP: #1960996) * For more details, full release note is available here: - https://github.com/sosreport/sos/releases/tag/4.3 * New patches: - d/p/0002-fix-setup-py.patch: Add python sos.help module, it was miss in upstream release. * Former patches, now fixed: - d/p/0002-report-implement_estimate-only.patch - d/p/0003-ceph-add-support-for-containerized-ceph-setup.patch - d/p/0004-ceph-split-plugin-by-components.patch - d/p/0005-openvswitch-get-userspace-datapath-implementations.patch - d/p/0006-report-check-for-symlink-before-rmtree.patch * Remaining patches: - d/p/0001-debian-change-tmp-dir-location.patch: -- Eric Desrochers Tue, 15 Feb 2022 23:10:27 -0500 ** Description changed: [IMPACT] The sos team is pleased to announce the release of sos-4.3. This release includes a number of quality-of-life changes to both end user experience and for contributors dealing with the plugin API. [TEST PLAN] Documentation for Special Cases: https://wiki.ubuntu.com/SosreportUpdates [WHERE PROBLEM COULD OCCUR] Regression could occur at core functionality, which may prevent sos (or its subcommand to work. I consider this regression type as 'low'. That is generally well tested, and we would find a problem at an early stage during the verification phase if it is the case. On the other end, regression could happen and are some kind of expected at plugins levels. As of today, sos has more than 300 plugins. It is nearly impossible to test them all. If a regression is found in a plugin, it is rarely affecting sos core functionalities nor other plugins. So mainly the impact would be limited to that plugin. The impact being that the plugin can't or partially can collect the information that it is instructed to gather. A 3rd party vendor would then ask user/customer to collect the information manually for that particular plugins. Plugins are segmented by services and/or applications (e.g. openstack_keystone, bcache, system, logs, ...) in order to collect things accordingly to the plugin detected or intentionally requested for. Sosreport plugins philosophy is to (as much as possible) maintain backward compatibility when updating a plugin. The risk that an ancient version of a software has been dropped, is unlikely, unless it was intended to be that way for particular reasons. Certain plugin also support the DEB installation way and the snap one (MAAS, LXD, ...) so all Ubuntu standard installation types are covered. * Problem found and fixed during the packaging process: - ** sos-help module wasn't part of the build process - ** sos-help man page wasn't also not part of the build process nor mention in main sos man page + ** sos-help module wasn't part of the build process + ** sos-help man page wasn't also not part of the build process nor mention in main sos man page Bug: https://github.com/sosreport/sos/issues/2860 - PR: + Both commits of PR need to be part of 4.3 Ubuntu package: https://github.com/sosreport/sos/pull/2861 [OTHER INFORMATION] Release note: https://github.com/sosreport/sos/releases/tag/4.3 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1960996 Title: [sru] sos upstream 4.3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sosreport/+bug/1960996/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1960996] Re: [sru] sos upstream 4.3
** Description changed: [IMPACT] The sos team is pleased to announce the release of sos-4.3. This release includes a number of quality-of-life changes to both end user experience and for contributors dealing with the plugin API. [TEST PLAN] Documentation for Special Cases: https://wiki.ubuntu.com/SosreportUpdates [WHERE PROBLEM COULD OCCUR] Regression could occur at core functionality, which may prevent sos (or its subcommand to work. I consider this regression type as 'low'. That is generally well tested, and we would find a problem at an early stage during the verification phase if it is the case. On the other end, regression could happen and are some kind of expected at plugins levels. As of today, sos has more than 300 plugins. It is nearly impossible to test them all. If a regression is found in a plugin, it is rarely affecting sos core functionalities nor other plugins. So mainly the impact would be limited to that plugin. The impact being that the plugin can't or partially can collect the information that it is instructed to gather. A 3rd party vendor would then ask user/customer to collect the information manually for that particular plugins. Plugins are segmented by services and/or applications (e.g. openstack_keystone, bcache, system, logs, ...) in order to collect things accordingly to the plugin detected or intentionally requested for. Sosreport plugins philosophy is to (as much as possible) maintain backward compatibility when updating a plugin. The risk that an ancient version of a software has been dropped, is unlikely, unless it was intended to be that way for particular reasons. Certain plugin also support the DEB installation way and the snap one (MAAS, LXD, ...) so all Ubuntu standard installation types are covered. + * Problem found and fixed during the packaging process: + + ** sos-help module wasn't part of the build process + ** sos-help man page wasn't also not part of the build process nor mention in main sos man page + + Bug: + https://github.com/sosreport/sos/issues/2860 + + PR: + https://github.com/sosreport/sos/pull/2861 + [OTHER INFORMATION] - Release note: + Release note: https://github.com/sosreport/sos/releases/tag/4.3 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1960996 Title: [sru] sos upstream 4.3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sosreport/+bug/1960996/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1960996] Re: [sru] sos upstream 4.3
https://launchpad.net/ubuntu/+source/sosreport/4.3-1ubuntu2 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1960996 Title: [sru] sos upstream 4.3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sosreport/+bug/1960996/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1960996] Re: [sru] sos upstream 4.3
Just notice man page doesn't include sos help. I'll push another update (4.3-1ubuntu2) in Jammy. - Eric -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1960996 Title: [sru] sos upstream 4.3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sosreport/+bug/1960996/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1960996] Re: [sru] sos upstream 4.3
** Changed in: sosreport (Ubuntu Impish) Assignee: (unassigned) => nikhil kshirsagar (nkshirsagar) ** Changed in: sosreport (Ubuntu Focal) Assignee: (unassigned) => nikhil kshirsagar (nkshirsagar) ** Changed in: sosreport (Ubuntu Bionic) Assignee: (unassigned) => nikhil kshirsagar (nkshirsagar) ** Changed in: sosreport (Ubuntu Bionic) Importance: Undecided => Medium ** Changed in: sosreport (Ubuntu Focal) Importance: Undecided => Medium ** Changed in: sosreport (Ubuntu Impish) Importance: Undecided => Medium -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1960996 Title: [sru] sos upstream 4.3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sosreport/+bug/1960996/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1960996] Re: [sru] sos upstream 4.3
Uploaded in Jammy with a quilt patch to fix setup.py (see comment #1) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1960996 Title: [sru] sos upstream 4.3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sosreport/+bug/1960996/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1960996] Re: [sru] sos upstream 4.3
Found one bug that I have reported upstream with regard to sos.help module https://github.com/sosreport/sos/issues/2860 ** Bug watch added: github.com/sosreport/sos/issues #2860 https://github.com/sosreport/sos/issues/2860 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1960996 Title: [sru] sos upstream 4.3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sosreport/+bug/1960996/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1960996] Re: [sru] sos upstream 4.3
** Changed in: sosreport (Ubuntu Jammy) Assignee: (unassigned) => Eric Desrochers (slashd) ** Changed in: sosreport (Ubuntu Jammy) Importance: Undecided => Medium ** Changed in: sosreport (Ubuntu Jammy) Status: New => In Progress ** Tags added: seg sts -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1960996 Title: [sru] sos upstream 4.3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sosreport/+bug/1960996/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1960776] Re: i386 installer crashes
* Sadly the Atom D2500 + the chipset is seen as 32-bit by the 14.04 64-bit installer. * (The 16.04 32/64bit versions both do not have 3D acceleration, only 12.04 and 14.04… and at least 14.04 still gets ESR patches). * 18.04 and newer only boot to a blinking black cursor. * Regarding this “GMA500” graphics chipsets and newer distros: it seems to be “up to the distro to implement for their needs and newer kernels, as Intel does not support this chipset” * The “recipe” or whatever it is called was originally released for the 3.x kernel line. * The EMGD project that is up and running, and needs an OS distro/maintainer to implement is located at the website below * So far community efforts have gotten support for up to 18.04 * https://github.com/EMGD-Community I’m eager to learn how to help, but not sure how I can at the moment other than donating to Ubuntu efforts, etc. Best, Eric From: nore...@launchpad.net on behalf of Dan Bungert <1960...@bugs.launchpad.net> Date: Monday, February 14, 2022 at 4:40 PM To: hilga...@gmail.com Subject: [Bug 1960776] Re: i386 installer crashes @Eric, have you tried the amd64 installer yet? Any better luck with that? -- You received this bug notification because you are subscribed to the bug report. https://bugs.launchpad.net/bugs/1960776 Title: i386 installer crashes Status in ubiquity package in Ubuntu: Invalid Bug description: This was an issue which occurred during setup and brought me to this bug report page. I need an older Ubuntu install for the GMA500 driver which has not been updated for newer distros sadly. (Should I open another bug for no 3D acceleration with GMA500 on 20.04 or 22.04?) ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: ubiquity 2.18.8.13 ProcVersionSignature: Ubuntu 4.4.0-142.168~14.04.1-generic 4.4.167 Uname: Linux 4.4.0-142-generic i686 ApportVersion: 2.14.1-0ubuntu3.29 Architecture: i386 CasperVersion: 1.340.2 Date: Sun Feb 13 22:58:37 2022 InstallCmdLine: file=/cdrom/preseed/ubuntu.seed boot=casper initrd=/casper/initrd quiet splash --- maybe-ubiquity LiveMediaBuild: Ubuntu 14.04.6 LTS "Trusty Tahr" - Release i386 (20190304.5) ProcEnviron: TERM=linux PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1960776/+subscriptions -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1960776 Title: i386 installer crashes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1960776/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1960776] Re: i386 installer crashes
Hello - This is an older release, on older (then-compatible) hardware. I cannot sign in with my account for ESR support because I cannot install it. Replying with the email account I signed up with free the 3-device Ubuntu Advantage limit. What is needed to fix this bug? On Mon, Feb 14, 2022 at 7:40 AM Erich Eickmeyer < 1960...@bugs.launchpad.net> wrote: > Thank you for reporting this bug to Ubuntu. > > Ubuntu 14.04 (trusty) reached end-of-standard-support on April 25, 2019. > > See this document for currently supported Ubuntu releases: > https://wiki.ubuntu.com/Releases > > Please see https://ubuntu.com/support on how to purchase an Ubuntu > Advantage subscription. > > Please also note that we cannot control what releases hardware > manufacturers choose to support. For newer drivers, contact the hardware > manufacturer. > > ** Changed in: ubiquity (Ubuntu) >Status: New => Invalid > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1960776 > > Title: > i386 installer crashes > > Status in ubiquity package in Ubuntu: > Invalid > > Bug description: > This was an issue which occurred during setup and brought me to this > bug report page. I need an older Ubuntu install for the GMA500 driver > which has not been updated for newer distros sadly. > > (Should I open another bug for no 3D acceleration with GMA500 on 20.04 > or 22.04?) > > ProblemType: Bug > DistroRelease: Ubuntu 14.04 > Package: ubiquity 2.18.8.13 > ProcVersionSignature: Ubuntu 4.4.0-142.168~14.04.1-generic 4.4.167 > Uname: Linux 4.4.0-142-generic i686 > ApportVersion: 2.14.1-0ubuntu3.29 > Architecture: i386 > CasperVersion: 1.340.2 > Date: Sun Feb 13 22:58:37 2022 > InstallCmdLine: file=/cdrom/preseed/ubuntu.seed boot=casper > initrd=/casper/initrd quiet splash --- maybe-ubiquity > LiveMediaBuild: Ubuntu 14.04.6 LTS "Trusty Tahr" - Release i386 > (20190304.5) > ProcEnviron: >TERM=linux >PATH=(custom, no user) >XDG_RUNTIME_DIR= >LANG=en_US.UTF-8 > SourcePackage: ubiquity > UpgradeStatus: No upgrade log present (probably fresh install) > > To manage notifications about this bug go to: > > https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1960776/+subscriptions > > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1960776 Title: i386 installer crashes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1960776/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1960776] [NEW] i386 installer crashes
Public bug reported: This was an issue which occurred during setup and brought me to this bug report page. I need an older Ubuntu install for the GMA500 driver which has not been updated for newer distros sadly. (Should I open another bug for no 3D acceleration with GMA500 on 20.04 or 22.04?) ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: ubiquity 2.18.8.13 ProcVersionSignature: Ubuntu 4.4.0-142.168~14.04.1-generic 4.4.167 Uname: Linux 4.4.0-142-generic i686 ApportVersion: 2.14.1-0ubuntu3.29 Architecture: i386 CasperVersion: 1.340.2 Date: Sun Feb 13 22:58:37 2022 InstallCmdLine: file=/cdrom/preseed/ubuntu.seed boot=casper initrd=/casper/initrd quiet splash --- maybe-ubiquity LiveMediaBuild: Ubuntu 14.04.6 LTS "Trusty Tahr" - Release i386 (20190304.5) ProcEnviron: TERM=linux PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ubiquity (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 trusty ubiquity-2.18.8.13 ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1960776 Title: i386 installer crashes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1960776/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1959121] [NEW] nvidia graphics driver stopped working, screen resolution has been degraded
Public bug reported:
Description:Ubuntu 20.04.3 LTS
Release:20.04
N: Unable to locate package pkgname
I expected my computer to recognize my graphics card. It has been working fine
until this morning. When I turned on my computer it took longer than normal to
load and now it does not identify my graphics card and the resolution is
degraded.
apt.log
log time: 2021-06-17 15:56:46.835636
Starting pkgProblemResolver with broken count: 1
Starting 2 pkgProblemResolver with broken count: 1
Investigating (0) linux-modules-nvidia-460-5.8.0-53-generic:amd64 < 5.8.0-53.60>
Broken linux-modules-nvidia-460-5.8.0-53-generic:amd64 Depends on nvidia-kernel>
Considering nvidia-kernel-common-460:amd64 13 as a solution to linux-modules->
Removing linux-modules-nvidia-460-5.8.0-53-generic:amd64 rather than change n>
Done
Log time: 2021-06-17 16:16:26.065339
MarkPurge libsratom-0-0:amd64 < 0.6.4-1 @ii gK > FU=1
Starting pkgProblemResolver with broken count: 1
Starting 2 pkgProblemResolver with broken count: 1
Investigating (0) liblilv-0-0:amd64 < 0.24.6-1ubuntu0.1 @ii gK Ib >
Broken liblilv-0-0:amd64 Depends on libsratom-0-0:amd64 < 0.6.4-1 @ii pgP > (>=>
Considering libsratom-0-0:amd64 1 as a solution to liblilv-0-0:amd64 2
Removing liblilv-0-0:amd64 rather than change libsratom-0-0:amd64
MarkDelete liblilv-0-0:amd64 < 0.24.6-1ubuntu0.1 @ii gK Ib > FU=0
Investigating (0) libavfilter7:amd64 < 7:4.2.4-1ubuntu0.1 @ii gK Ib >
Broken libavfilter7:amd64 Depends on liblilv-0-0:amd64 < 0.24.6-1ubuntu0.1 @ii >
Considering liblilv-0-0:amd64 2 as a solution to libavfilter7:amd64 1
[ File 'apt.log' is unwritable ]
Start-Date: 2021-06-17 16:14:39
Requested-By: office (1000)
Install: linux-signatures-nvidia-5.8.0-55-generic:amd64 (5.8.0-55.62~20.04.1, a>
Upgrade: gnome-control-center-data:amd64 (1:3.36.5-0ubuntu1, 1:3.36.5-0ubuntu2)>
Remove: linux-modules-nvidia-460-5.8.0-53-generic:amd64 (5.8.0-53.60~20.04.1)
End-Date: 2021-06-17 16:16:24
Start-Date: 2021-06-17 16:16:39
Requested-By: office (1000)
Purge: libavfilter7:amd64 (7:4.2.4-1ubuntu0.1), libopencore-amrnb0:amd64 (0.1.5>
End-Date: 2021-06-17 16:16:41
Log started: 2021-06-17 16:14:39
(Reading database ... ^M(Reading database ... 5%^M(Reading database ... 10%^M(R>
Preparing to unpack .../0-nvidia-driver-460_460.80-0ubuntu0.20.04.2_amd64.deb .>
Unpacking nvidia-driver-460 (460.80-0ubuntu0.20.04.2) over (460.73.01-0ubuntu0.>
Preparing to unpack .../1-libnvidia-gl-460_460.80-0ubuntu0.20.04.2_amd64.deb ...
De-configuring libnvidia-gl-460:i386 (460.73.01-0ubuntu0.20.04.1) ...
Unpacking libnvidia-gl-460:amd64 (460.80-0ubuntu0.20.04.2) over (460.73.01-0ubu>
Preparing to unpack .../2-libnvidia-gl-460_460.80-0ubuntu0.20.04.2_i386.deb ...
Unpacking libnvidia-gl-460:i386 (460.80-0ubuntu0.20.04.2) over (460.73.01-0ubun>
Preparing to unpack .../3-nvidia-dkms-460_460.80-0ubuntu0.20.04.2_amd64.deb ...
Removing all DKMS Modules
Done.
Unpacking nvidia-dkms-460 (460.80-0ubuntu0.20.04.2) over (460.73.01-0ubuntu0.20>
Preparing to unpack .../4-nvidia-kernel-source-460_460.80-0ubuntu0.20.04.2_amd6>
Unpacking nvidia-kernel-source-460 (460.80-0ubuntu0.20.04.2) over (460.73.01-0u>
Preparing to unpack .../5-linux-modules-nvidia-460-generic-hwe-20.04_5.8.0-55.6>
Unpacking linux-modules-nvidia-460-generic-hwe-20.04 (5.8.0-55.62~20.04.1) over>
(Reading database ... ^M(Reading database ... 5%^M(Reading database ... 10%^M(R>
Removing linux-modules-nvidia-460-5.8.0-53-generic (5.8.0-53.60~20.04.1) ...
[ File 'apt-term.log' is unwritable ]
7zXZ^@^@^D�ִF^B^@!^A^V^@^@^@t/���]^@)^YJ'�H�^Uh�TZۄUّ���|y�^R^Q��ya��^S��^Y�>
ʆ��G�$^LE�^H��C;}�l^9Ꭱ^V^@���f^S)^Y^H
e17ӕ�ozұ^R�
�^P^N�}^W^^���§��Ԙ#�^W�1�UvĬ^WӺY�e�"^B��fS��"^R^F�^[�(,(^C�H��Վ8J5^Zhi�E+^O>
j!#�b�"?�ˉ��:���F�v�SN^]��V|*S7�^AC^Y^]f��^\})�wɼ���^Fh^h^[Ɓ�>-^ZSj2#^^^Qif>
Yҙ~<�LΎ9oĥ�~K,iyӼ��6mս�ω��$�\k`���^_
½�%�j��ԅ+
�^HA�$G�^B�B��H�zuG�h^D{Ձ!ű�-�^R)5��Qi�O^_Jk�^?˳��T�T�b8^^w��[�^N�X^DX�>
�^K:jw�n^Aئ� ^PWܖ�4��/@^P^C�n� �#�Ҵ��_��^L;i�Ku�~��^F���ʽ��^[�^]��bq�z�>
�^F^P���B�Ԯ^D^Y�^U" �^T�^E;�F���Z�`�^C��^\䒁+�,=�F^^�W���K�mNx-`藬A�,�Y�1��A�?ՠ>
GJ���H�]A<�^R]�c�o�^]Ţ#�^^�^Y���N帹��/^S�^_-��{:^^B�Y7^SCJT���9|c��@==�>
Ӡ1o�j}�r��^X^W!F^@�^E$㲐#ja(^Z��\��^]�5�D^Z��6Xx��}eL��^PۗC�^S�#^Z�q�ٝR�{�^K�>
r��^Zڤ�^Smf��^[w^Wl[^E�>�H���v^F�^(��gSz)�̥���;�^@,TQ�8��ސ��r�^D@/��2��'��[fK�U�>
�^^v�J[���^W�:�9���^KX�9��_^Zq�ZPu}Efi�DoZ���^[�G&^Y'^XU�^_~^B�*}y4V�^S^E >
baY�q^@�@^N�^Y���j��fB���U�^E^H�'qx��S)��+c՟��V��l��*�
WsVA�I7^C�^���AZ�5^S_���^Wj�,B�Į�(�^S^Cd4��InVB>^^ר�'^U^W^^�M�$�a�^L��O>
�E���9^PE��Q�^W���^Yn�e��g^V�oc��?U^D�L��M��7�kx�-^\^X/���^\J�k^O��>
^O�2D�ln���ڇV'��G���_�+��`�u��s�dAn�U�^[���4^]�E~L^D�a��^E�ء^�B^Z^F�JO�U�,�>
��r�/z�Ybn��⺌I^B^N��� w�M^R^B�:��/�D���C�c�^]W�1�7��T^\��^Z���ȥ.��qp�H= ��^B^>
^Z._dH��^xu�/��:-��-*5`0p�ȧ%^P���^Hh��;�.��^V47^K�3wQ�^Vً�9�v��^O^T^U�I�>
[ File
[Bug 1958462] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1958462/+attachment/770/+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/1958462 Title: Keyboard doesn't type in text fields without virtual keyboard enabled in accessibility To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1958462/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1958462] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1958462/+attachment/767/+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/1958462 Title: Keyboard doesn't type in text fields without virtual keyboard enabled in accessibility To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1958462/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1958462] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1958462/+attachment/765/+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/1958462 Title: Keyboard doesn't type in text fields without virtual keyboard enabled in accessibility To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1958462/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1958462] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1958462/+attachment/769/+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/1958462 Title: Keyboard doesn't type in text fields without virtual keyboard enabled in accessibility To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1958462/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1958462] RfKill.txt
apport information ** Attachment added: "RfKill.txt" https://bugs.launchpad.net/bugs/1958462/+attachment/768/+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/1958462 Title: Keyboard doesn't type in text fields without virtual keyboard enabled in accessibility To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1958462/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1958462] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1958462/+attachment/766/+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/1958462 Title: Keyboard doesn't type in text fields without virtual keyboard enabled in accessibility To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1958462/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1958462] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1958462/+attachment/764/+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/1958462 Title: Keyboard doesn't type in text fields without virtual keyboard enabled in accessibility To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1958462/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1958462] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1958462/+attachment/759/+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/1958462 Title: Keyboard doesn't type in text fields without virtual keyboard enabled in accessibility To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1958462/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1958462] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1958462/+attachment/763/+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/1958462 Title: Keyboard doesn't type in text fields without virtual keyboard enabled in accessibility To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1958462/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1958462] PaInfo.txt
apport information ** Attachment added: "PaInfo.txt" https://bugs.launchpad.net/bugs/1958462/+attachment/762/+files/PaInfo.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1958462 Title: Keyboard doesn't type in text fields without virtual keyboard enabled in accessibility To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1958462/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1958462] Lsusb-v.txt
apport information ** Attachment added: "Lsusb-v.txt" https://bugs.launchpad.net/bugs/1958462/+attachment/761/+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/1958462 Title: Keyboard doesn't type in text fields without virtual keyboard enabled in accessibility To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1958462/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1958462] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1958462/+attachment/758/+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/1958462 Title: Keyboard doesn't type in text fields without virtual keyboard enabled in accessibility To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1958462/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1958462] Lsusb-t.txt
apport information ** Attachment added: "Lsusb-t.txt" https://bugs.launchpad.net/bugs/1958462/+attachment/760/+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/1958462 Title: Keyboard doesn't type in text fields without virtual keyboard enabled in accessibility To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1958462/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1958462] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1958462/+attachment/757/+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/1958462 Title: Keyboard doesn't type in text fields without virtual keyboard enabled in accessibility To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1958462/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1958462] Dependencies.txt
apport information ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1958462/+attachment/756/+files/Dependencies.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1958462 Title: Keyboard doesn't type in text fields without virtual keyboard enabled in accessibility To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1958462/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1958462] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1958462/+attachment/755/+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/1958462 Title: Keyboard doesn't type in text fields without virtual keyboard enabled in accessibility To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1958462/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1958462] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1958462/+attachment/754/+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/1958462 Title: Keyboard doesn't type in text fields without virtual keyboard enabled in accessibility To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1958462/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1958462] Re: Keyboard doesn't type in text fields without virtual keyboard enabled in accessibility
apport information ** Tags added: apport-collected staging ** Description changed: On reboot, I can login with my password without the virtual keyboard, and if my screen locks I can type my password. However, when I open up terminal, Firefox, any text box in any application, it fails to input the text I enter from my keyboard as if my keyboard is unplugged. But when I enable on-screen keyboard in the accessibility menu, my keyboard functions as it should. I just now have a virtual keyboard taking up the bottom 1/3 of my screen. I'm running 21.10 on a Raspberry Pi 4 Model B with 4Gb of RAM. My keyboard is a Corsair K100 RGB. I've tried multiple USB ports and multiple reboots and I still am required to enable my virtual keyboard in order for my real keyboard to work. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: linux-image-5.13.0-1015-raspi 5.13.0-1015.17 ProcVersionSignature: Ubuntu 5.13.0-1015.17-raspi 5.13.19 Uname: Linux 5.13.0-1015-raspi aarch64 ApportVersion: 2.20.11-0ubuntu71 Architecture: arm64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Jan 19 16:18:11 2022 ImageMediaBuild: 20211013 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-raspi UpgradeStatus: No upgrade log present (probably fresh install) + --- + ProblemType: Bug + ApportVersion: 2.20.11-0ubuntu71 + Architecture: arm64 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/controlC1: eric 1007 F pulseaudio + /dev/snd/controlC0: eric 1007 F pulseaudio + CasperMD5CheckResult: unknown + CurrentDesktop: ubuntu:GNOME + DistroRelease: Ubuntu 21.10 + ImageMediaBuild: 20211013 + Lspci-vt: -[:00]---00.0-[01]00.0 VIA Technologies, Inc. VL805/806 xHCI USB 3.0 Controller + Package: linux-raspi 5.13.0.1015.20 + PackageArchitecture: arm64 + ProcEnviron: + TERM=xterm-256color + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=en_US.UTF-8 + SHELL=/bin/bash + ProcFB: 0 vc4drmfb + ProcKernelCmdLine: coherent_pool=1M 8250.nr_uarts=0 snd_bcm2835.enable_compat_alsa=0 snd_bcm2835.enable_hdmi=1 video=HDMI-A-1:1920x1080M@60 smsc95xx.macaddr=E4:5F:01:2D:89:75 vc_mem.mem_base=0x3ec0 vc_mem.mem_size=0x4000 dwc_otg.lpm_enable=0 console=tty1 root=LABEL=writable rootfstype=ext4 elevator=deadline rootwait fixrtc quiet splash + ProcVersionSignature: Ubuntu 5.13.0-1015.17-raspi 5.13.19 + RelatedPackageVersions: + linux-restricted-modules-5.13.0-1015-raspi N/A + linux-backports-modules-5.13.0-1015-raspi N/A + linux-firmware 1.201.3 + StagingDrivers: bcm2835_mmal_vchiq bcm2835_codec bcm2835_v4l2 vc_sm_cma bcm2835_isp snd_bcm2835 + Tags: wayland-session arm64-image raspi-image impish staging + Uname: Linux 5.13.0-1015-raspi aarch64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo + _MarkForUpload: True + acpidump: ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1958462/+attachment/753/+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/1958462 Title: Keyboard doesn't type in text fields without virtual keyboard enabled in accessibility To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1958462/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1958462] [NEW] Keyboard doesn't type in text fields without virtual keyboard enabled in accessibility
Public bug reported: On reboot, I can login with my password without the virtual keyboard, and if my screen locks I can type my password. However, when I open up terminal, Firefox, any text box in any application, it fails to input the text I enter from my keyboard as if my keyboard is unplugged. But when I enable on-screen keyboard in the accessibility menu, my keyboard functions as it should. I just now have a virtual keyboard taking up the bottom 1/3 of my screen. I'm running 21.10 on a Raspberry Pi 4 Model B with 4Gb of RAM. My keyboard is a Corsair K100 RGB. I've tried multiple USB ports and multiple reboots and I still am required to enable my virtual keyboard in order for my real keyboard to work. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: linux-image-5.13.0-1015-raspi 5.13.0-1015.17 ProcVersionSignature: Ubuntu 5.13.0-1015.17-raspi 5.13.19 Uname: Linux 5.13.0-1015-raspi aarch64 ApportVersion: 2.20.11-0ubuntu71 Architecture: arm64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Jan 19 16:18:11 2022 ImageMediaBuild: 20211013 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-raspi UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-raspi (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug arm64 arm64-image impish raspi-image wayland-session -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1958462 Title: Keyboard doesn't type in text fields without virtual keyboard enabled in accessibility To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1958462/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1728388] Re: Infinite loop on boot when loading ACPI
** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** No longer affects: linux (Ubuntu) ** Package changed: ubuntu => linux (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1728388 Title: Infinite loop on boot when loading ACPI To manage notifications about this bug go to: https://bugs.launchpad.net/linuxmint/+bug/1728388/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1728388] Re: Infinite loop on boot when loading ACPI
The issue is still present on a 5.15 kernel. On a HP Pavilion 17-0e50sf (Hybrid Graphics: Intel_i915/AMD_radeon ), the system hangs for about 40 seconds after the user login (tested with gdm, lightdm / GNOME, Weston, xfce / Xorg, Wayland). dmesg output: ACPI Error: Aborting method \AMD3._ON due to previous error (AE_AML_LOOP_TIMEOUT) (20210730/psparse-529) acpi device:02: Failed to change power state to D0 [drm] PCIE gen 3 link speeds already enabled [drm] PCIE GART of 2048M enabled (table at 0x0004). radeon :01:00.0: WB enabled radeon :01:00.0: fence driver on ring 0 use gpu addr 0x4c00 radeon :01:00.0: fence driver on ring 1 use gpu addr 0x4c04 radeon :01:00.0: fence driver on ring 2 use gpu addr 0x4c08 radeon :01:00.0: fence driver on ring 3 use gpu addr 0x4c0c radeon :01:00.0: fence driver on ring 4 use gpu addr 0x4c10 debugfs: File 'radeon_ring_gfx' in directory '1' already present! debugfs: File 'radeon_ring_cp1' in directory '1' already present! debugfs: File 'radeon_ring_cp2' in directory '1' already present! debugfs: File 'radeon_ring_dma1' in directory '1' already present! debugfs: File 'radeon_ring_dma2' in directory '1' already present! [drm] ring test on 0 succeeded in 1 usecs [drm] ring test on 1 succeeded in 1 usecs [drm] ring test on 2 succeeded in 1 usecs [drm] ring test on 3 succeeded in 3 usecs [drm] ring test on 4 succeeded in 3 usecs [drm] ib test on ring 0 succeeded in 0 usecs [drm] ib test on ring 1 succeeded in 0 usecs [drm] ib test on ring 2 succeeded in 0 usecs [drm] ib test on ring 3 succeeded in 0 usecs [drm] ib test on ring 4 succeeded in 0 usecs Tried with both radeon and amdgpu kernel modules: same issue. Also tried to call ACPI method \AMD3._ON with acpi_call module: it returns an error after 30 seconds. Blacklisting the radeon and amdgpu modules allows me to work around the problem ** Tags added: regression-release ** Tags added: kernel-bug -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1728388 Title: Infinite loop on boot when loading ACPI To manage notifications about this bug go to: https://bugs.launchpad.net/linuxmint/+bug/1728388/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1728388] Re: Infinite loop on boot when loading ACPI
** Also affects: ubuntu Importance: Undecided Status: New ** Also affects: debian Importance: Undecided Status: New ** Also affects: archlinux 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/1728388 Title: Infinite loop on boot when loading ACPI To manage notifications about this bug go to: https://bugs.launchpad.net/linuxmint/+bug/1728388/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1848831] Re: Intel WiFi AX200 [8086:08b1] subsystem [8086:4070] firmware loading error resulting in no wifi
I have the same problem with a M.2 AX200 card installed in a laptop running Ubuntu 20.04, with kernel 5.11.0-40-generic. I noticed that the WiFi works fine when I force the driver to load the firmware "iwlwifi-cc-a0-48.ucode" by renaming newer versions of this file, and this also worked with previous kernel releases. After every update of linux-firmware, however, the renamed files are replaced and the WiFi starts crash-looping again. Thus, I am confident that the issue is specific to the newer firmware releases for the AX200: - iwlwifi-cc-a0-55.ucode - iwlwifi-cc-a0-59.ucode - iwlwifi-cc-a0-63.ucode Does anyone know what was changed in these firmware revisions? For reference, here is the error message printed when iwlwifi-cc-a0-55.ucode is loaded. It repeats over and over until I delete the aforementioned firmware file: [ 215.397707] iwlwifi :03:00.0: Direct firmware load for iwlwifi-cc-a0-59.ucode failed with error -2 [ 215.397747] iwlwifi :03:00.0: Direct firmware load for iwlwifi-cc-a0-58.ucode failed with error -2 [ 215.397779] iwlwifi :03:00.0: Direct firmware load for iwlwifi-cc-a0-57.ucode failed with error -2 [ 215.397810] iwlwifi :03:00.0: Direct firmware load for iwlwifi-cc-a0-56.ucode failed with error -2 [ 215.398396] iwlwifi :03:00.0: api flags index 2 larger than supported by driver [ 215.398423] iwlwifi :03:00.0: TLV_FW_FSEQ_VERSION: FSEQ Version: 89.3.35.22 [ 215.398430] iwlwifi :03:00.0: Found debug destination: EXTERNAL_DRAM [ 215.398434] iwlwifi :03:00.0: Found debug configuration: 0 [ 215.399009] iwlwifi :03:00.0: loaded firmware version 55.d9698065.0 cc-a0-55.ucode op_mode iwlmvm [ 215.399106] iwlwifi :03:00.0: Detected Intel(R) Wi-Fi 6 AX200 160MHz, REV=0x340 [ 216.087870] iwlwifi :03:00.0: base HW address: b0:7d:64:dc:49:f2 [ 216.101508] thermal thermal_zone2: failed to read out thermal zone (-61) [ 218.817520] iwlwifi :03:00.0: Error sending BT_CONFIG: time out after 2000ms. [ 218.817533] iwlwifi :03:00.0: Current CMD queue read_ptr 5 write_ptr 6 [ 218.817755] iwlwifi :03:00.0: HCMD_ACTIVE already clear for command BT_CONFIG [ 218.817920] iwlwifi :03:00.0: Start IWL Error Log Dump: [ 218.817924] iwlwifi :03:00.0: Status: 0x0040, count: 6 [ 218.817928] iwlwifi :03:00.0: Loaded firmware version: 55.d9698065.0 cc-a0-55.ucode [ 218.817932] iwlwifi :03:00.0: 0x0084 | NMI_INTERRUPT_UNKNOWN [ 218.817936] iwlwifi :03:00.0: 0x00A022F0 | trm_hw_status0 [ 218.817939] iwlwifi :03:00.0: 0x | trm_hw_status1 [ 218.817942] iwlwifi :03:00.0: 0x004FA34A | branchlink2 [ 218.817945] iwlwifi :03:00.0: 0x004E4BBC | interruptlink1 [ 218.817948] iwlwifi :03:00.0: 0x004E4BBC | interruptlink2 [ 218.817950] iwlwifi :03:00.0: 0x00016468 | data1 [ 218.817953] iwlwifi :03:00.0: 0x0100 | data2 [ 218.817956] iwlwifi :03:00.0: 0x | data3 [ 218.817958] iwlwifi :03:00.0: 0x | beacon time [ 218.817961] iwlwifi :03:00.0: 0x00289204 | tsf low [ 218.817963] iwlwifi :03:00.0: 0x | tsf hi [ 218.817966] iwlwifi :03:00.0: 0x | time gp1 [ 218.817968] iwlwifi :03:00.0: 0x0028F457 | time gp2 [ 218.817971] iwlwifi :03:00.0: 0x0001 | uCode revision type [ 218.817974] iwlwifi :03:00.0: 0x0037 | uCode version major [ 218.817976] iwlwifi :03:00.0: 0xD9698065 | uCode version minor [ 218.817979] iwlwifi :03:00.0: 0x0340 | hw version [ 218.817982] iwlwifi :03:00.0: 0x18C89000 | board version [ 218.817984] iwlwifi :03:00.0: 0x803BFD26 | hcmd [ 218.817987] iwlwifi :03:00.0: 0x0002 | isr0 [ 218.817989] iwlwifi :03:00.0: 0x | isr1 [ 218.817992] iwlwifi :03:00.0: 0x08F2 | isr2 [ 218.817994] iwlwifi :03:00.0: 0x00CC | isr3 [ 218.817997] iwlwifi :03:00.0: 0x | isr4 [ 218.818000] iwlwifi :03:00.0: 0x | last cmd Id [ 218.818002] iwlwifi :03:00.0: 0x00016468 | wait_event [ 218.818005] iwlwifi :03:00.0: 0x | l2p_control [ 218.818007] iwlwifi :03:00.0: 0x | l2p_duration [ 218.818010] iwlwifi :03:00.0: 0x | l2p_mhvalid [ 218.818012] iwlwifi :03:00.0: 0x | l2p_addr_match [ 218.818015] iwlwifi :03:00.0: 0x0009 | lmpm_pmg_sel [ 218.818017] iwlwifi :03:00.0: 0x | timestamp [ 218.818019] iwlwifi :03:00.0: 0x0028 | flow_handler [ 218.818171] iwlwifi :03:00.0: Start IWL Error Log Dump: [ 218.818173] iwlwifi :03:00.0: Status: 0x0040, count: 7 [ 218.818177] iwlwifi :03:00.0: 0x2066 | NMI_INTERRUPT_HOST [ 218.818180] iwlwifi :03:00.0: 0x | umac branchlink1 [ 218.818182] iwlwifi :03:00.0: 0x80465826 | umac branchlink2 [ 218.818185] iwlwifi :03:00.0: 0x8048074C | umac interruptlink1 [ 218.818188] iwlwifi :03:00.0: 0x8048074C | umac interruptlink2 [ 218.818190] iwlwifi :03:00.0:
[Bug 1926299] Re: incorrect sensor is read on Lenovo server BMC
[sts-sponsor] After a discussion with ddstreet about nobody being able (as it requires specific HW) nor reply to our request to test the proposed packages for this particular bug. Since the packages of freeipmi are languishing in proposed for about 176 days (as of today) with no responses/outcomes/feebacks/ I have asked the SRU verification team to drop the packages found in -proposed. Note that as ddstreet mentioned, upstream has adopted the fix, so if someone in the Ubuntu community/customer report this bug again in the future and commit on testing the fix in Ubuntu we could consider to backport again. - Eric ** Tags removed: verification-needed-bionic verification-needed-focal verification-needed-hirsute ** Tags added: verification-failed-bionic verification-failed-focal verification-failed-hirsute -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1926299 Title: incorrect sensor is read on Lenovo server BMC To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/freeipmi/+bug/1926299/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1926299] Re: incorrect sensor is read on Lenovo server BMC
[sts-sponsor] After a discussion with ddstreet about nobody being able (as it requires specific HW) nor reply to our request to test the proposed packages for this particular bug. Since the packages of freeipmi are languishing in proposed for about 176 (as of today) with no response/outcome/feebacks/ I have asked the SRU verification team to drop the packages found in -proposed. Note that as ddstreet mentioned, upstream has adopted the fix, so if someone in the Ubuntu community/customer report this bug again in the future and commit on testing the fix in Ubuntu we could consider to re- backport again. - Eric -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1926299 Title: incorrect sensor is read on Lenovo server BMC To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/freeipmi/+bug/1926299/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1900617] Re: gateway error detail is not passed along in raised exception
Is there any reproducer that could exercise the code path you have modified ? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1900617 Title: gateway error detail is not passed along in raised exception To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-etcd3gw/+bug/1900617/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1900617] Re: gateway error detail is not passed along in raised exception
Is there any reproducer that could exercise the code you have modified ? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1900617 Title: gateway error detail is not passed along in raised exception To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-etcd3gw/+bug/1900617/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1900617] Re: gateway error detail is not passed along in raised exception
Not having a good test for the binary package would be a blocker here for the release of the package. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1900617 Title: gateway error detail is not passed along in raised exception To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-etcd3gw/+bug/1900617/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1900617] Re: gateway error detail is not passed along in raised exception
Can you build a reproducer out of the unit tests for this bug while using the binary package ? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1900617 Title: gateway error detail is not passed along in raised exception To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-etcd3gw/+bug/1900617/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1947099] Re: ipconfig does not honour user-requested timeouts in some cases
> I will attempt to upstream this fix to klibc, but I believe the change to Bionic should happen in parallel/independently since the upstream patch will not make its way back to Bionic (which is stuck at 2.0.4, as mentioned above). Yes that is the plan to SRU the fix on top of what is currently found in Bionic's klibc. And I'll gladly sponsor your patch in Bionic. The idea with upstream is to make our contribution available to other who may suffer from the same issue, make sure it won't re-occur in a future release of Ubuntu as we will sync from debian which sync from upstream, ... and also have some kind of upstream adoption/approval/review of your proposal fix. Let's give a few days after the submission for the upstream to have some time to review your patch. If it takes too long for them to get back to us, I'll sponsor the patch as-is, knowing that it was submitted to upstream with a reasonable amount of time given to them to review. - Eric ** Changed in: klibc (Ubuntu Bionic) Assignee: (unassigned) => Khaled El Mously (kmously) ** Changed in: klibc (Ubuntu Bionic) Status: New => In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1947099 Title: ipconfig does not honour user-requested timeouts in some cases To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/klibc/+bug/1947099/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1947099] Re: ipconfig does not honour user-requested timeouts in some cases
And let them judge if it's worth an upstream adoption or not as a first exercise. Then we can take a decision for Ubuntu. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1947099 Title: ipconfig does not honour user-requested timeouts in some cases To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/klibc/+bug/1947099/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1947099] Re: ipconfig does not honour user-requested timeouts in some cases
And let them judge if it's worth the adoption or not as a first exercise. Then we can take a decision for Ubuntu. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1947099 Title: ipconfig does not honour user-requested timeouts in some cases To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/klibc/+bug/1947099/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1947099] Re: ipconfig does not honour user-requested timeouts in some cases
I still believe, it would be a good practice to submit the patch to upstream. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1947099 Title: ipconfig does not honour user-requested timeouts in some cases To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/klibc/+bug/1947099/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1947099] Re: ipconfig does not honour user-requested timeouts in some cases
Khaled El Mously (kmously), Thanks for the update. I'll review this and talk with sil2100, an SRU verification member. Could you please help to fill the SRU template in the description above. Extra documentations can be found here: https://wiki.ubuntu.com/StableReleaseUpdates#SRU_Bug_Template What make Bionic more susceptible to this particular problem ? Bionic kernel version in use ? else ? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1947099 Title: ipconfig does not honour user-requested timeouts in some cases To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/klibc/+bug/1947099/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1820083] Re: TLS params not set for session
Thanks, Heather. Don't forget to do the verification for the other bug as well (LP: #1900617) - Eric -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1820083 Title: TLS params not set for session To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-etcd3gw/+bug/1820083/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1820083] Re: TLS params not set for session
Is there a way you can verify the actual binary package ? Instead of testing it by pulling the source code ? Verification need to be done on the binary package, this is what we will promote in -updates. - Eric -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1820083 Title: TLS params not set for session To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-etcd3gw/+bug/1820083/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 829051] Re: paprefs cannot configure pulseaudio network settings
This bug is still present on 20.10. You'd think after 10 years ... it would get fixed??? Glad I found this thread. Very pleased to have this working with a *very* simple symlink. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/829051 Title: paprefs cannot configure pulseaudio network settings To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/829051/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1941745] Re: [sru] sos upstream 4.2
** Description changed: [IMPACT] The sos team is pleased to announce the release of sos-4.2. This release contains numerous improvements and bug fixes to several components within sos, including an overhaul to the project's test suite and infrastructure. [TEST PLAN] Documentation for Special Cases: https://wiki.ubuntu.com/SosreportUpdates [WHERE PROBLEM COULD OCCUR] Regression could occur at core functionality, which may prevent sos (or its subcommand to work. I consider this regression type as 'low'. That is generally well tested, and we would find a problem at an early stage during the verification phase if it is the case. On the other end, regression could happen and are some kind of expected at plugins levels. As of today, sos has more than 300 plugins. It is nearly impossible to test them all. If a regression is found in a plugin, it is rarely affecting sos core functionalities nor other plugins. So mainly the impact would be limited to that plugin. The impact being that the plugin can't or partially can collect the information that it is instructed to gather. A 3rd party vendor would then ask user/customer to collect the information manually for that particular plugins. Plugins are segmented by services and/or applications (e.g. openstack_keystone, bcache, system, logs, ...) in order to collect things accordingly to the plugin detected or intentionally requested for. + Sosreport plugins philosophy is to (as much as possible) maintain + backward compatibility when updating a plugin. The risk that an ancient + version of a software has been dropped, is unlikely, unless it was + intended to be that way for particular reasons. Certain plugin also + support the DEB installation way and the snap one (MAAS, LXD, ...) so + all Ubuntu standard installation types are covered. + [OTHER INFORMATION] Release note: https://github.com/sosreport/sos/releases/tag/4.2 Debian RFS: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=994564 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1941745 Title: [sru] sos upstream 4.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sosreport/+bug/1941745/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1941745] Re: [sru] sos upstream 4.2
Let's focus our time testing Focal/20.04LTS, which can cover various areas: Openstack, Ceph, k8s, MAAS, juju, Landscape, ... (to only name those) - Eric -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1941745 Title: [sru] sos upstream 4.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sosreport/+bug/1941745/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1941745] Re: [sru] sos upstream 4.2
[VERIFICATION HIRSUTE/IMPISH] Since theses 2 releases are non-LTS. They are less exposed to various context & environment types such as: Openstack, Ceph, k8s, JuJu, MAAS, Landscape, ... It's safe to say that non-LTS should be limited to general sosreport run, most likely in the Desktop area. For that reasons, I don't judge we need to spend time testing non-LTS for such context/environments that typically belongs to LTS version. The autopkgtest (simple.sh) was run successfully, and it already does a lot of general sosreport runs testing. I also tested sosreport myself on H/I and didn't see any problem. With that being said, if someone is keen to do more test, please feel free to do so, but as the maintainer, I consider the verification done for H/I. - Eric ** Tags removed: verification-needed-hirsute verification-needed-impish ** Tags added: verification-done-hirsute verification-done-impish -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1941745 Title: [sru] sos upstream 4.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sosreport/+bug/1941745/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1949495] [NEW] Error shown when using chsh to change shells
Public bug reported: I wanted to change my shell to zsh so I installed the zsh package and then used the chsh command as so: chsh -s $(which zsh) After running the command I am shown the errors: (2021-11-02 12:54:47:928739): [sss_cache] [confdb_get_enabled_domain_list] (0x0040): Failed to get [domains] from [sssd], error [2] (No such file or directory) (2021-11-02 12:54:47:928885): [sss_cache] [init_domains] (0x0020): Could not initialize domains (2021-11-02 12:54:47:949846): [sss_cache] [confdb_get_enabled_domain_list] (0x0040): Failed to get [domains] from [sssd], error [2] (No such file or directory) (2021-11-02 12:54:47:949987): [sss_cache] [init_domains] (0x0020): Could not initialize domains I also receive this error when just running chsh without any parameters. The change is successful, even though the error might lead you to believe otherwise. After logging out and back in, zsh was my default shell. From what I can tell from a quick search, the error has to do with SSSD and Active Directory support so I assume there is something happening around that but honestly don't know enough about it to know if that's correct. Please let me know if there's any additional information needed and thanks for all you do to create and support Ubuntu. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: passwd 1:4.8.1-1ubuntu9 ProcVersionSignature: Ubuntu 5.13.0-20.20-generic 5.13.14 Uname: Linux 5.13.0-20-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Tue Nov 2 13:09:46 2021 InstallationDate: Installed on 2020-12-24 (312 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200907) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: shadow UpgradeStatus: Upgraded to impish on 2021-10-17 (15 days ago) ** Affects: shadow (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug impish -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1949495 Title: Error shown when using chsh to change shells To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shadow/+bug/1949495/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
