[Bug 1952411] Re: Lenovo 14W Gen2 - Touchpad don't work
I have this device, the ACPI tables must be patched for the kernel to recognize the touchpad. See Attachment. ** Patch added: "DSDT patch for working touchpad" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1952411/+attachment/5795163/+files/dsdt.patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1952411 Title: Lenovo 14W Gen2 - Touchpad don't work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1952411/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2064177] Re: Window borders and shadows missing from GTK3 dialogs (if autologin is enabled and Xorg is used)
It seems like Regional Formats or language problem to me. I installed new Ubuntu 24.04 in English (US) and the windows worked fine. When I changed Regional Formats to Korean and reboot the system, the window problem started and remains. I think the password/login process in Ubuntu has a problem with cjk language. In Ubuntu 22.04, I installed 4 languages (English, Russian, Japanese, Korean), and whenever the login prompt appears, there were only English and Russian available. In addition, I had to change the input language because the default language was set to Russian in the prompt no matter what the language order. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2064177 Title: Window borders and shadows missing from GTK3 dialogs (if autologin is enabled and Xorg is used) To manage notifications about this bug go to: https://bugs.launchpad.net/gtk/+bug/2064177/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2070020] Re: Lenovo dock no longer working after upgrade from 6.5.0-35 to 6.5.0-41
Hi Chris. I still don't have access to my laptop but Jorg (who can't get launchpad to let him login) has confirmed it works fine with 6.8. He plugging the dock in and it just worked perfectly. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2070020 Title: Lenovo dock no longer working after upgrade from 6.5.0-35 to 6.5.0-41 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2070020/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2070020] Re: Lenovo dock no longer working after upgrade from 6.5.0-35 to 6.5.0-41
I'm going to play middleman. Jorg_Mertin via framework forum: Went on the launchpad and tried to follow the bug here Bug #2070020 “Lenovo dock no longer working after upgrade from 6...” : Bugs : linux package : Ubuntu So - mruffel has compiled a kernel and I tested it. Can’t log into bugs.launchpad.net - always getting a 500 internal server error on login. So posting here: It does not work. Kernel: [mar. juin 25 10:49:31 2024] Linux version 6.5.0-41-generic (buildd@lcy02-amd64-028) (x86_64-linux-gnu-gcc-12 (Ubuntu 12.3.0-1ubuntu1~22.04) 12.3.0, GNU ld (GNU Binutils for Ubuntu) 2.38) #41~22.04.2+TEST2070020v20240625b1-Ubun tu SMP PREEMPT_DYNAMIC Mo (Ubuntu 6.5.0-41.41~22.04.2+TEST2070020v20240625b1-generic 6.5.13) Getting various of these: ``` [mar. juin 25 10:50:30 2024] [ cut here ] [mar. juin 25 10:50:30 2024] WARNING: CPU: 15 PID: 1400 at drivers/gpu/drm/amd/amdgpu/../display/amdgpu_dm/amdgpu_dm_helpers.c:190 fill_dc_mst_payload_table_from_drm+0xb7/0x250 [amdgpu] [mar. juin 25 10:50:30 2024] Modules linked in: r8153_ecm cdc_ether usbnet r8152 mii snd_usb_audio snd_usbmidi_lib snd_ump mc ccm rfcomm cmac algif_hash algif_skcipher af_alg bnep sunrpc binfmt_misc dm_crypt intel_rapl_msr intel_rapl_common snd_hda_codec_realtek snd_hda_codec_generic ledtrig_audio snd_sof_amd_rembrandt snd_sof_amd_renoir snd_sof_amd_acp snd_sof_pci snd_sof_xtensa_dsp snd_hda_codec_hdmi snd_sof snd_hda_intel snd_sof_utils snd_intel_dspcfg snd_intel_sdw_acpi mt7921e snd_hda_codec edac_mce_amd mt7921_common snd_soc_core snd_hda_core btusb mt76_connac_lib snd_hwdep snd_compress btrtl ac97_bus kvm_amd btbcm snd_pcm_dmaengine mt76 btintel snd_seq_midi btmtk snd_pci_ps snd_seq_midi_event mac80211 snd_rpl_pci_acp6x snd_rawmidi snd_acp_pci kvm snd_pci_acp6x bluetooth snd_seq hid_sensor_als snd_pcm hid_sensor_trigger industrialio_triggered_buffer kfifo_buf irqbypass hid_sensor_iio_common ecdh_generic snd_seq_device nls_iso8859_1 ecc joydev rapl input_leds snd_pci_acp5x industrialio typec_displayport hid_multitouch wmi_bmof [mar. juin 25 10:50:30 2024] snd_timer k10temp cfg80211 snd_rn_pci_acp3x snd_acp_config snd snd_soc_acpi snd_pci_acp3x ccp libarc4 soundcore mac_hid amd_pmf amd_pmc platform_profile sch_fq_codel 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 usbhid amdgpu amdxcp iommu_v2 drm_buddy gpu_sched i2c_algo_bit drm_suballoc_helper drm_ttm_helper ttm crct10dif_pclmul crc32_pclmul polyval_clmulni polyval_generic drm_display_helper ghash_clmulni_intel cec sha256_ssse3 nvme sha1_ssse3 rc_core aesni_intel nvme_core drm_kms_helper hid_sensor_hub ucsi_acpi crypto_simd cros_ec_lpcs hid_generic cros_ec cryptd typec_ucsi thunderbolt i2c_piix4 xhci_pci drm xhci_pci_renesas nvme_common typec video i2c_hid_acpi wmi i2c_hid hid [mar. juin 25 10:50:30 2024] CPU: 15 PID: 1400 Comm: kwin_wayland Tainted: G W 6.5.0-41-generic #41~22.04.2+TEST2070020v20240625b1-Ubuntu [mar. juin 25 10:50:30 2024] Hardware name: Framework Laptop 16 (AMD Ryzen 7040 Series)/FRANMZCP07, BIOS 03.03 03/27/2024 [mar. juin 25 10:50:30 2024] RIP: 0010:fill_dc_mst_payload_table_from_drm+0xb7/0x250 [amdgpu] [mar. juin 25 10:50:30 2024] Code: fe 06 0f 87 1f 01 00 00 0f b6 7a 09 41 38 7d 00 75 dd 0f b7 0d 0e a5 af 00 4b 8d 14 76 66 89 8c d5 50 ff ff ff 41 39 df 75 31 <0f> 0b eb 2d 49 83 ff 06 0f 87 53 01 00 00 0f b7 0d e8 a4 af 00 8a [mar. juin 25 10:50:30 2024] RSP: 0018:af2949fc3230 EFLAGS: 00010246 [mar. juin 25 10:50:30 2024] RAX: af2949fc33c8 RBX: RCX: [mar. juin 25 10:50:30 2024] RDX: af2949fc3330 RSI: 9a1b347b9bb0 RDI: af2949fc32e8 [mar. juin 25 10:50:30 2024] RBP: af2949fc3318 R08: 9a1b347b9800 R09: [mar. juin 25 10:50:30 2024] R10: R11: R12: af2949fc3268 [mar. juin 25 10:50:30 2024] R13: af2949fc3268 R14: af2949fc3330 R15: [mar. juin 25 10:50:30 2024] FS: 775f49951140() GS:9a29621c() knlGS: [mar. juin 25 10:50:30 2024] CS: 0010 DS: ES: CR0: 80050033 [mar. juin 25 10:50:30 2024] CR2: 61b19c5aaf98 CR3: 000111dca000 CR4: 00750ee0 [mar. juin 25 10:50:30 2024] PKRU: 5554 [mar. juin 25 10:50:30 2024] Call Trace: [mar. juin 25 10:50:30 2024] [mar. juin 25 10:50:30 2024] ? show_regs+0x6d/0x80 [mar. juin 25 10:50:30 2024] ? __warn+0x89/0x160 [mar. juin 25 10:50:30 2024] ? fill_dc_mst_payload_table_from_drm+0xb7/0x250 [amdgpu] [mar. juin 25 10:50:30 2024] ? report_bug+0x17e/0x1b0 [mar. juin 25 10:50:30 2024] ? handle_bug+0x46/0x90 [mar. juin 25 10:50:30 2024] ? exc_invalid_op+0x18/0x80 [mar. juin 25 10:50:30 2024] ? asm_exc_invalid_op+0x1b/0x20 [mar. juin 25 10:50:30 2024] ?
[Bug 2070020] Re: Lenovo dock no longer working after upgrade from 6.5.0-35 to 6.5.0-41
I wish I could but I am away until Saturday and don't have my laptop with me. If nobody has done it by Saturday I can do it then. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2070020 Title: Lenovo dock no longer working after upgrade from 6.5.0-35 to 6.5.0-41 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2070020/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2070079] Re: Latest kernel makes usb 4 run as 3.0
I forgot to add I am using a framework 16 with a Ryzen 7 7840HS. I created a request for help on the framework forum and another person had the same issue. https://community.frame.work/t/linux-suddenly-lost-my-monitors-on-my- dock/53291/10 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2070079 Title: Latest kernel makes usb 4 run as 3.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-6.5/+bug/2070079/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2070079] acpidump.txt
apport information ** Attachment added: "acpidump.txt" https://bugs.launchpad.net/bugs/2070079/+attachment/5791264/+files/acpidump.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2070079 Title: Latest kernel makes usb 4 run as 3.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-6.5/+bug/2070079/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2070079] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/2070079/+attachment/5791262/+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/2070079 Title: Latest kernel makes usb 4 run as 3.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-6.5/+bug/2070079/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2070079] RfKill.txt
apport information ** Attachment added: "RfKill.txt" https://bugs.launchpad.net/bugs/2070079/+attachment/5791261/+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/2070079 Title: Latest kernel makes usb 4 run as 3.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-6.5/+bug/2070079/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2070079] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/2070079/+attachment/5791255/+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/2070079 Title: Latest kernel makes usb 4 run as 3.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-6.5/+bug/2070079/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2070079] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/2070079/+attachment/5791258/+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/2070079 Title: Latest kernel makes usb 4 run as 3.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-6.5/+bug/2070079/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2070079] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/2070079/+attachment/5791260/+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/2070079 Title: Latest kernel makes usb 4 run as 3.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-6.5/+bug/2070079/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2070079] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/2070079/+attachment/5791257/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2070079 Title: Latest kernel makes usb 4 run as 3.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-6.5/+bug/2070079/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2070079] Lsusb-v.txt
apport information ** Attachment added: "Lsusb-v.txt" https://bugs.launchpad.net/bugs/2070079/+attachment/5791253/+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/2070079 Title: Latest kernel makes usb 4 run as 3.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-6.5/+bug/2070079/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2070079] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/2070079/+attachment/5791251/+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/2070079 Title: Latest kernel makes usb 4 run as 3.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-6.5/+bug/2070079/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2070079] Lspci-vt.txt
apport information ** Attachment added: "Lspci-vt.txt" https://bugs.launchpad.net/bugs/2070079/+attachment/5791250/+files/Lspci-vt.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2070079 Title: Latest kernel makes usb 4 run as 3.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-6.5/+bug/2070079/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2070079] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/2070079/+attachment/5791259/+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/2070079 Title: Latest kernel makes usb 4 run as 3.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-6.5/+bug/2070079/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2070079] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/2070079/+attachment/5791263/+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/2070079 Title: Latest kernel makes usb 4 run as 3.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-6.5/+bug/2070079/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2070079] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/2070079/+attachment/5791256/+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/2070079 Title: Latest kernel makes usb 4 run as 3.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-6.5/+bug/2070079/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2070079] Lsusb-t.txt
apport information ** Attachment added: "Lsusb-t.txt" https://bugs.launchpad.net/bugs/2070079/+attachment/5791252/+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/2070079 Title: Latest kernel makes usb 4 run as 3.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-6.5/+bug/2070079/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2070079] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/2070079/+attachment/5791246/+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/2070079 Title: Latest kernel makes usb 4 run as 3.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-6.5/+bug/2070079/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2070079] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/2070079/+attachment/5791248/+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/2070079 Title: Latest kernel makes usb 4 run as 3.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-6.5/+bug/2070079/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2070079] AudioDevicesInUse.txt
apport information ** Attachment added: "AudioDevicesInUse.txt" https://bugs.launchpad.net/bugs/2070079/+attachment/5791245/+files/AudioDevicesInUse.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2070079 Title: Latest kernel makes usb 4 run as 3.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-6.5/+bug/2070079/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2070079] PaInfo.txt
apport information ** Attachment added: "PaInfo.txt" https://bugs.launchpad.net/bugs/2070079/+attachment/5791254/+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/2070079 Title: Latest kernel makes usb 4 run as 3.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-6.5/+bug/2070079/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2070079] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/2070079/+attachment/5791249/+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/2070079 Title: Latest kernel makes usb 4 run as 3.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-6.5/+bug/2070079/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2070079] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/2070079/+attachment/5791247/+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/2070079 Title: Latest kernel makes usb 4 run as 3.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-6.5/+bug/2070079/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2070079] [NEW] Latest kernel makes usb 4 run as 3.0
Public bug reported: When my kernel was updated from 6.5.0-35-generic to 6.5.0-41-generic my monitors connected via a thunderbolt 3 dock stopped working. It seemed I did not have the bandwidth anymore. The logs showed I only had v3.0 bandwidth despite it being a v4.0 port. When I went back to 6.5.0-35-generic it worked again. It also worked when I switched to 6.5.0-060500-generic --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: zorin:GNOME DistroRelease: Zorin OS 17 InstallationDate: Installed on 2024-04-21 (61 days ago) InstallationMedia: Zorin-OS 17.1 Core 64bit MachineType: Framework Laptop 16 (AMD Ryzen 7040 Series) Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-41-generic root=/dev/mapper/vgzorin-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 6.5.0-41.41~22.04.2-generic 6.5.13 RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: linux-restricted-modules-6.5.0-41-generic N/A linux-backports-modules-6.5.0-41-generic N/A linux-firmware20220329.git681281e4-0ubuntu3.31 Tags: jammy wayland-session Uname: Linux 6.5.0-41-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/27/2024 dmi.bios.release: 3.3 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 03.03 dmi.board.asset.tag: * dmi.board.name: FRANMZCP07 dmi.board.vendor: Framework dmi.board.version: A7 dmi.chassis.asset.tag: FRAGAACPA740940011 dmi.chassis.type: 10 dmi.chassis.vendor: Framework dmi.chassis.version: A7 dmi.modalias: dmi:bvnINSYDECorp.:bvr03.03:bd03/27/2024:br3.3:svnFramework:pnLaptop16(AMDRyzen7040Series):pvrA7:rvnFramework:rnFRANMZCP07:rvrA7:cvnFramework:ct10:cvrA7:skuFRAGAACP07: dmi.product.family: 16in Laptop dmi.product.name: Laptop 16 (AMD Ryzen 7040 Series) dmi.product.sku: FRAGAACP07 dmi.product.version: A7 dmi.sys.vendor: Framework ** Affects: linux-signed-hwe-6.5 (Ubuntu) Importance: Undecided Status: New ** Tags: apport-collected jammy wayland-session ** Tags added: apport-collected jammy wayland-session ** Description changed: - When my kernel was updated from 6.5.0-35-generic to 6.5.0-41-generic my - monitors connected via a thunderbolt 3 dock stopped working. It seemed I - did not have the bandwidth anymore. The logs showed I only had v3.0 - bandwidth despite it being a v4.0 port. When I went back to - 6.5.0-35-generic it worked again. It also worked when I switched to - 6.5.0-060500-generic + When my kernel was updated from 6.5.0-35-generic to 6.5.0-41-generic my monitors connected via a thunderbolt 3 dock stopped working. It seemed I did not have the bandwidth anymore. The logs showed I only had v3.0 bandwidth despite it being a v4.0 port. When I went back to 6.5.0-35-generic it worked again. It also worked when I switched to 6.5.0-060500-generic + --- + ProblemType: Bug + ApportVersion: 2.20.11-0ubuntu82.5 + Architecture: amd64 + CasperMD5CheckResult: pass + CurrentDesktop: zorin:GNOME + DistroRelease: Zorin OS 17 + InstallationDate: Installed on 2024-04-21 (61 days ago) + InstallationMedia: Zorin-OS 17.1 Core 64bit + MachineType: Framework Laptop 16 (AMD Ryzen 7040 Series) + Package: linux (not installed) + ProcFB: 0 amdgpudrmfb + ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-41-generic root=/dev/mapper/vgzorin-root ro quiet splash vt.handoff=7 + ProcVersionSignature: Ubuntu 6.5.0-41.41~22.04.2-generic 6.5.13 + RebootRequiredPkgs: Error: path contained symlinks. + RelatedPackageVersions: + linux-restricted-modules-6.5.0-41-generic N/A + linux-backports-modules-6.5.0-41-generic N/A + linux-firmware20220329.git681281e4-0ubuntu3.31 + Tags: jammy wayland-session + Uname: Linux 6.5.0-41-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo + _MarkForUpload: True + dmi.bios.date: 03/27/2024 + dmi.bios.release: 3.3 + dmi.bios.vendor: INSYDE Corp. + dmi.bios.version: 03.03 + dmi.board.asset.tag: * + dmi.board.name: FRANMZCP07 + dmi.board.vendor: Framework + dmi.board.version: A7 + dmi.chassis.asset.tag: FRAGAACPA740940011 + dmi.chassis.type: 10 + dmi.chassis.vendor: Framework + dmi.chassis.version: A7 + dmi.modalias: dmi:bvnINSYDECorp.:bvr03.03:bd03/27/2024:br3.3:svnFramework:pnLaptop16(AMDRyzen7040Series):pvrA7:rvnFramework:rnFRANMZCP07:rvrA7:cvnFramework:ct10:cvrA7:skuFRAGAACP07: + dmi.product.family: 16in Laptop + dmi.product.name: Laptop 16 (AMD Ryzen 7040 Series) + dmi.product.sku: FRAGAACP07 + dmi.product.version: A7 + dmi.sys.vendor: Framework -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2070079 Title: Latest kernel makes usb 4 run as 3.0 To manage
[Bug 2070079] AlsaInfo.txt
apport information ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/2070079/+attachment/5791244/+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/2070079 Title: Latest kernel makes usb 4 run as 3.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-6.5/+bug/2070079/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: Application for ubuntu-desktop membership
I can vouch for Daniel's long history working on desktop components and am sure he'll continue to do great work on Ubuntu desktop. +1 from me makes 3/3 - adding him to the team now. On Tue, Jun 18, 2024 at 6:47 PM Sebastien Bacher wrote: > Hey desktopers, > > I've worked with Daniel for a long time and I'm confident that he can be > trusted with access to the desktop set. He demonstrated high quality > work on our different desktop environments over the year, is one of our > top upstream contributors to GNOME and understands the Ubuntu > cycles/community/processes (SRU, freezes, ...). He's already actively > working on our desktop packages on launchpad and salsa and having direct > access should make things easier for everyone. > > +1 from me! > > Cheers, > Sébastien Bacher > > On 18/06/2024 07:16, Daniel van Vugt wrote: > > Hi desktoppers, > > > > I would like to be considered for membership in the ubuntu-desktop team. > > > > Starting as a Linux user in the 1990s, I moved to Ubuntu around about > 2007. In > > 2011 I started contributing to the Unity desktop and was asked to join > > Canonical. In 2012 I joined the Canonical Desktop team as the full time > > maintainer of Compiz underlying the Unity desktop. In 2013 I moved onto > the Mir > > team and stayed there until 2017 when I returned to the Canonical > Desktop team > > where I remain today. > > > > Throughout this time I've had countless uploads sponsored, and have > remained > > the top (human) contributor to bug management karma in Ubuntu for most > of a decade. > > > > Being able to upload packages myself would remove the biggest delay I > > experience in my daily work and make the whole team slightly more > efficient. > > Thanks for your consideration... > > > > - Daniel > > > > > > -- > ubuntu-desktop mailing list > ubuntu-desktop@lists.ubuntu.com > https://lists.ubuntu.com/mailman/listinfo/ubuntu-desktop > -- ubuntu-desktop mailing list ubuntu-desktop@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-desktop
[Bug 1989976]
(In reply to Robert Townley from comment #10) > The short answer is the analogy falls down a little here because these are > master keys. Imagine you have one automobile - a . > You do not have a single Chevy key, but you do have keys for a 78 Mazda GLC, > a BMW, and your house. None of those would work! But you try them and it > is like magic, all three of these master keys unlock the 1957 Chevy Bel Air. [Cross-Device Authentication (CDA)](https://passkeys.dev/docs/reference/terms/#cross-device- authentication-cda) allows your iPhone to vouch for your logon attempt on your Desktop because it is cabled to it or within BlueTooth range. About the time the pandemic arrived in the US, almost all Credit Cards had these chips on them. The contactless nature of these credit cards meant germs were not spread as much. The chip stores a private key. Effectively, TPM hardware in your desktop or laptop or iPhone has one of these credit card chips. The public key can travel all over the internet, but the private key should never ever leave the device it was created on. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1989976 Title: [upstream] wishlist: Passkeys should be supported To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1989976/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1989976]
The short answer is the analogy falls down a little here because these are master keys. Imagine you have one automobile - a . You do not have a single Chevy key, but you do have keys for a 78 Mazda GLC, a BMW, and your house. None of those would work! But you try them and it is like magic, all three of these master keys unlock the 1957 Chevy Bel Air. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1989976 Title: [upstream] wishlist: Passkeys should be supported To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1989976/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1989976]
(In reply to Mildred Ki'Lya from comment #7) > It seems Firefox implemented passkeys for Windows and MacOS but lack support > for Linux as shown in https://www.passkeys.io/compatible-devices > > I don't quite understand what is so platform specific. Of course, integration > in the native platform password manager is nice but not mandatory. Firefox > already stores its passwords and can sync them with Firefox Sync. What's so > different with passkeys and what's the status of this feature? > > As a web developer if I can provide passkeys as the primary login method, > this would be a great step forward, but it'd be better to have full browser > compatibility. PassKeys.io is really saying there is a workaround when they write ["Phone passkeys (QR code flow) and physical security keys only"](https://www.passkeys.io/compatible-devices). The private part of the passkey should never leave the device it was created on, so by design, it should not sync anywhere else. However, if you have a passkey on your cellphone or YubiKey but want to authenticate on your Linux desktop, then Bluetooth ( or a USB cable) connected to your desktop should offer a workaround. It worked for me before but not sure which Linux PC and which web browser on which Linux machine. If your Linux desktop has supported TPM hardware, then i do not see why it would not work. US DOD does it. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1989976 Title: [upstream] wishlist: Passkeys should be supported To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1989976/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 237941]
(In reply to avada from comment #51) > (In reply to Dave Martin from comment #50) > > I've highlighted this bug many times and (have just checked) my first > > report was 18 years ago in bug 118394 which is still open. Eighteen > > years, please, let's have a fix !!This bug and the lack of a vertical > > tabs option in base Firefox (I use a 3rd party addon, tree style tab, > > wonderful) are major detractions to this browser. > > Just let it go, not going to happen. Use the above mentioned for this > functionality, and other useful ones such as jumping to the searched > bookmark/folder's location on the tree: > https://addons.mozilla.org/firefox/addon/bookmark-search-plus-2/ > It opens in the sidebar the same way as the built in sidebar. But a month ago, Mozilla had not announced they were inserting artificial intelligence into our browser. Those neural nets need to vacuum up my 101,109 bookmarks and let me search folders. Better yet, the a.i. will tell us what folder we want before we type it in. [https://www.reddit.com/r/firefox/comments/1de7bu1/were_the_firefox_leadership_team_at_mozilla_ama/?utm_campaign=Reddit+AMA+with+Firefox+leadership_medium=bitly_source=SUMO+Banner]( Mozilla leadership will be promising that today. They will lean on a.i. to squash all these outstanding bugs. ) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/237941 Title: Bookmarking Folder Location To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/237941/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 2055114] Re: fail2ban is broken in 24.04 Noble
The new package has been working good for me EXCEPT wordpress thinks it isn't running even though it is AND it acts on the WordPress filters and jails I have installed. -_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_- Eskimo North Linux Friendly Internet Access, Shell Accounts, and Hosting. Knowledgeable human assistance, not telephone trees or script readers. See our web site: http://www.eskimo.com/ (206) 812-0051 or (800) 246-6874. On Tue, 11 Jun 2024, Brian Murray wrote: > Date: Tue, 11 Jun 2024 20:05:13 - > From: Brian Murray <2055...@bugs.launchpad.net> > To: nan...@eskimo.com > Subject: [Bug 2055114] Re: fail2ban is broken in 24.04 Noble > > Hello Robert, or anyone else affected, > > Accepted fail2ban into noble-proposed. The package will build now and be > available at > https://launchpad.net/ubuntu/+source/fail2ban/1.0.2-3ubuntu0.1 in a few > hours, and then in the -proposed repository. > > Please help us by testing this new package. See > https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how > to enable and use -proposed. Your feedback will aid us getting this > update out to other Ubuntu users. > > If this package fixes the bug for you, please add a comment to this bug, > mentioning the version of the package you tested, what testing has been > performed on the package and change the tag from verification-needed- > noble to verification-done-noble. If it does not fix the bug for you, > please add a comment stating that, and change the tag to verification- > failed-noble. In either case, without details of your testing we will > not be able to proceed. > > Further information regarding the verification process can be found at > https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in > advance for helping! > > N.B. The updated package will be released to -updates after the bug(s) > fixed by this package have been verified and the package has been in > -proposed for a minimum of 7 days. > > ** Changed in: fail2ban (Ubuntu Noble) > Status: Confirmed => Fix Committed > > ** Tags added: verification-needed verification-needed-noble > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/2055114 > > Title: > fail2ban is broken in 24.04 Noble > > Status in fail2ban package in Ubuntu: > Fix Released > Status in fail2ban source package in Noble: > Fix Committed > Status in fail2ban source package in Oracular: > Fix Released > > Bug description: > [ Impact ] > * fail2ban fails to start on Ubuntu 24.04, due to new Python and deprecated > classes (now vendored upstream) > > [ Test Plan ] > * Install and check systemctl status fail2ban. > > [ Where problems could occur ] > * Nowhere, fixing a program failing to start > > [ Other info ] > Was working in 22.04, but after upgrading to 24.04 I get this: > > × fail2ban.service - Fail2Ban Service > Loaded: loaded (/etc/systemd/system/fail2ban.service; enabled; preset: > enabled) > Active: failed (Result: exit-code) since Sun 2024-02-25 02:27:29 PST; 1 > day 18h ago > Duration: 2.330s > Docs: man:fail2ban(1) > Process: 1130 ExecStartPre=/bin/mkdir -p /run/fail2ban (code=exited, > status=0/SUCCESS) > Process: 1133 ExecStart=/usr/local/bin/fail2ban-server -xf start > (code=exited, status=255/EXCEPTION) > Main PID: 1133 (code=exited, status=255/EXCEPTION) > CPU: 660ms > > Feb 25 02:27:26 mx1 systemd[1]: Starting fail2ban.service - Fail2Ban > Service... > Feb 25 02:27:26 mx1 systemd[1]: Started fail2ban.service - Fail2Ban Service. > Feb 25 02:27:28 mx1 fail2ban-server[1133]: 2024-02-25 02:27:28,952 fail2ban > [1133]: ERROR No module named 'asynchat' > Feb 25 02:27:29 mx1 systemd[1]: fail2ban.service: Main process exited, > code=exited, status=255/EXCEPTION > Feb 25 02:27:29 mx1 systemd[1]: fail2ban.service: Failed with result > 'exit-code'. > > grep fail2ban syslog > 2024-02-25T02:25:17.813593-08:00 mx1 systemd[1]: Stopping fail2ban.service - > Fail2Ban Service... > 2024-02-25T02:27:26.625640-08:00 mx1 systemd[1]: Starting fail2ban.service - > Fail2Ban Service... > 2024-02-25T02:27:26.678572-08:00 mx1 systemd[1]: Started fail2ban.service - > Fail2Ban Service. > 2024-02-25T02:27:28.954548-08:00 mx1 fail2ban-server[1133]: 2024-02-25 > 02:27:28,952 fail2ban[1133]: ERROR No module named > 'asynchat' > 2024-02-25T02:27:29.004733-08:00 mx1 systemd[1]: fail2ban.service: Main > process exited, code=exited, status=255/EXCEPTION > 2024-02-25T02:27:29.004834-08:00 mx1 systemd[1]: fail
[Bug 320140] Re: can't copy between two sftp connections
I can't reproduce the issue, it is solved. ** Changed in: krusader (Ubuntu) Status: Incomplete => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/320140 Title: can't copy between two sftp connections To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/krusader/+bug/320140/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2068747] [NEW] Impossible d'évaluer la mise à niveau
Public bug reported: could not upgrade to 23.10 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: ubuntu-release-upgrader-core 1:22.04.19 ProcVersionSignature: Ubuntu 5.15.0-112.122-generic 5.15.152 Uname: Linux 5.15.0-112-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Fri Jun 7 17:53:00 2024 InstallationDate: Installed on 2024-06-07 (0 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-release-upgrader UpgradeStatus: Upgraded to jammy on 2024-06-07 (0 days ago) VarLogDistupgradeTermlog: mtime.conffile..etc.update-manager.release-upgrades: 2024-06-07T17:43:12.981472 ** Affects: ubuntu-release-upgrader (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug dist-upgrade jammy third-party-packages 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/2068747 Title: Impossible d'évaluer la mise à niveau To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/2068747/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2065925] Re: connexion to server lost
ran version 0.5 without issues on ubuntu 22.04, after upgrade to 24.04 still on 0.5, but I now get "the connection to the server has been lost" whenever the game starts (continue, quick start, single player+start, pick saved game ...) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2065925 Title: connexion to server lost To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/freeorion/+bug/2065925/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2067940] [NEW] package linux-headers-6.8.0-35-generic 6.8.0-35.35 failed to install/upgrade: installed linux-headers-6.8.0-35-generic package post-installation script subprocess returned error ex
Public bug reported: I clicked on the update that was offered to me through the standard software updater. ProblemType: Package DistroRelease: Ubuntu 24.04 Package: linux-headers-6.8.0-35-generic 6.8.0-35.35 ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1 Uname: Linux 6.8.0-31-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.28.1-0ubuntu3 Architecture: amd64 CRDA: N/A CasperMD5CheckResult: pass Date: Mon Jun 3 14:48:41 2024 ErrorMessage: installed linux-headers-6.8.0-35-generic package post-installation script subprocess returned error exit status 11 InstallationDate: Installed on 2024-05-14 (21 days ago) InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424) MachineType: LENOVO 20EGS0RA02 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-31-generic root=UUID=138ba324-feb2-4704-bb05-dc37105666e0 ro quiet splash vt.handoff=7 Python3Details: /usr/bin/python3.12, Python 3.12.3, python3-minimal, 3.12.3-0ubuntu1 PythonDetails: N/A RelatedPackageVersions: grub-pc N/A SourcePackage: linux Title: package linux-headers-6.8.0-35-generic 6.8.0-35.35 failed to install/upgrade: installed linux-headers-6.8.0-35-generic package post-installation script subprocess returned error exit status 11 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/02/2021 dmi.bios.release: 2.42 dmi.bios.vendor: LENOVO dmi.bios.version: GNET94WW (2.42 ) dmi.board.asset.tag: Not Available dmi.board.name: 20EGS0RA02 dmi.board.vendor: LENOVO dmi.board.version: SDK0E50510 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.ec.firmware.release: 1.14 dmi.modalias: dmi:bvnLENOVO:bvrGNET94WW(2.42):bd06/02/2021:br2.42:efr1.14:svnLENOVO:pn20EGS0RA02:pvrThinkPadW541:rvnLENOVO:rn20EGS0RA02:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNotAvailable:skuLENOVO_MT_20EG: dmi.product.family: ThinkPad W541 dmi.product.name: 20EGS0RA02 dmi.product.sku: LENOVO_MT_20EG dmi.product.version: ThinkPad W541 dmi.sys.vendor: LENOVO ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package noble -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2067940 Title: package linux-headers-6.8.0-35-generic 6.8.0-35.35 failed to install/upgrade: installed linux-headers-6.8.0-35-generic package post-installation script subprocess returned error exit status 11 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2067940/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2041727] Re: "netplan apply" produces ovsdb-server.service WARNING even when openvswitch-switch not installed
Xubuntu 22.04.03 This bug suddenly appeared about 2024 05 20. Seems to be preventing DN resolution on internal network. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2041727 Title: "netplan apply" produces ovsdb-server.service WARNING even when openvswitch-switch not installed To manage notifications about this bug go to: https://bugs.launchpad.net/netplan/+bug/2041727/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2066315] Re: Users who upgraded to rejected SRU 1.72.4-0ubuntu0.22.04.1 aren't restored
Verified on Jammy in AWS workspaces. Test plan: 1. Upgrade from 1.72.4-0ubuntu0.22.04.1 to 1.72.4-0ubuntu0.22.04.3~really.is.1.72.2.0ubuntu2 2. Monitor system for couple of days Done in 3 VMs, no issues detected. I'll keep VMs running for couple of days doing random GUI operations and update this case if anything will be detected. ** Tags removed: verification-needed-jammy ** Tags added: verification-done-jammy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2066315 Title: Users who upgraded to rejected SRU 1.72.4-0ubuntu0.22.04.1 aren't restored To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gjs/+bug/2066315/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 117514] Re: seahorse does not synchronize keys with keyserver
In 24.04 desktop if you choose two keys to sync, the program will crash. Also, does not look like the sync even works. I had to use the below command to get my key to sync. gpg --send-keys --keyserver keyserver.ubuntu.com -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/117514 Title: seahorse does not synchronize keys with keyserver To manage notifications about this bug go to: https://bugs.launchpad.net/seahorse/+bug/117514/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2064548] Re: kwallet will not accept passw; nor let me change it
If you need to reset the password and it’s not accepting the current one, you might need to delete the wallet file to reset it. The wallet file is usually located at /home//.local/share/kwalletd/kdewallet.kwl. Deleting this file will prompt the creation of a new wallet and allow you to set a new password. https://www-netbenefits.com -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2064548 Title: kwallet will not accept passw; nor let me change it To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kwalletmanager/+bug/2064548/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2061986] Re: Mount CIFS fails with Permission denied
Verified issue on both linux/5.4.0-186.206 and linux/5.15.0-111.121. Following steps from description I was not able to reproduce issue nor I did not hit any new problems. Marking as verified. ** Tags removed: verification-needed-focal-linux verification-needed-jammy-linux ** Tags added: verification-done-focal-linux verification-done-jammy-linux -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2061986 Title: Mount CIFS fails with Permission denied To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2061986/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2064647] Re: Documentation for how to enable gnome-remote-desktop on a completly headless system
From Upstream I tried to enable using some commands through grdctl with no such luck grdctl enable [20:15:58:493] [60992:ee40] [ERROR][com.freerdp.crypto] - [x509_utils_from_pem]: BIO_new failed for certificate RDP server certificate is invalid. Usage: grdctl [OPTIONS...] COMMAND [SUBCOMMAND]... grdctl --headless enable [20:[61000:ee48] [ERROR][com.freerdp.crypto] - [x509_utils_from_pem]: BIO_new failed for certificate 16:02:476] RDP server certificate is invalid. Init TPM credentials failed because No TPM device found, using GKeyFile as fallback. Usage: grdctl [OPTIONS...] COMMAND [SUBCOMMAND]... grdctl --system enable Error changing to home directory /var/lib/gnome-remote-desktop: No such file or directory From @pnowack That's a packaging issue. Please report that to your distro. g-r-d installs both a sysusers and a tmpfiles file for the user for the system daemon and its config dirs. The sysusers and tmpfiles hooks usually run on a reboot, but they also MUST run when installing the respective pkg, in particular: after the decompression of the files (post-installation hooks). This works fine on other distros, like Arch (pacman automatically detects such sysusers- or tmpfiles-file installation and runs the respective hooks for that). apt or dpkg must also be able to correctly handle this (regardless of the pkg). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2064647 Title: Documentation for how to enable gnome-remote-desktop on a completly headless system To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-remote-desktop/+bug/2064647/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2064685] Re: write says write: effective gid does not match group of /dev/pts/5
This does not really fix security because one aspect of security is availability to legitimate users and this breaks the latter. Seems there are better ways to fix such as restricting what this can write to with apparmor? Or just fixing the coding so it does parse the input more carefully. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2064685 Title: write says write: effective gid does not match group of /dev/pts/5 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/2064685/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2064647] [NEW] Documentation for how to enable gnome-remote-desktop on a completly headless system
Public bug reported: Asked to create a new bug from https://bugs.launchpad.net/ubuntu/+source/gnome-remote- desktop/+bug/206 I am on a completely headless system starting from a minimal ubuntu-server 24.04 installation. I have installed the desktop using apt install ubuntu-desktop I want to use the new gnome-remote-desktop so that I can create a developer machine in a VM environment that can be accessed through a thin client as an example using Microsoft RDP I suspect there is some missing documentation. Starting the service using systemctl start gnome-remote-desktop.service results in: journalctl -xeu gnome-remote-desktop.service Apr 30 10:16:39 localhost systemd[1]: Starting gnome-remote-desktop.service - GNOME Remote Desktop... ░░ Subject: A start job for unit gnome-remote-desktop.service has begun execution ░░ Defined-By: systemd ░░ Support: http://www.ubuntu.com/support ░░ ░░ A start job for unit gnome-remote-desktop.service has begun execution. ░░ ░░ The job identifier is 2929. Apr 30 10:16:39 localhost (p-daemon)[1613]: gnome-remote-desktop.service: Failed to determine user credentials: No such process Apr 30 10:16:39 localhost systemd[1]: gnome-remote-desktop.service: Main process exited, code=exited, status=217/USER ░░ Subject: Unit process exited ░░ Defined-By: systemd ░░ Support: http://www.ubuntu.com/support ░░ ░░ An ExecStart= process belonging to unit gnome-remote-desktop.service has exited. ░░ ░░ The process' exit code is 'exited' and its exit status is 217. Running sudo systemd-sysusers does create some new users, restarting the remote desktop now gives: May 02 14:27:47 localhost gnome-remote-de[36906]: Init TPM credentials failed because No TPM device found, using GKeyFile as fallback May 02 14:27:47 localhost gnome-remote-de[36906]: Init file credentials failed: Error creating directory /var/lib/gnome-remote-desktop: Permission denied May 02 14:27:47 localhost gnome-remote-desktop-daemon[36906]: ** May 02 14:27:47 localhost gnome-remote-desktop-daemon[36906]: ERROR:../src/grd-settings.c:345:grd_settings_constructed: assertion failed: (priv->credentials) May 02 14:27:47 localhost gnome-remote-desktop-daemon[36906]: Bail out! ERROR:../src/grd-settings.c:345:grd_settings_constructed: assertion failed: (priv->credentials) May 02 14:27:47 localhost systemd[1]: gnome-remote-desktop.service: Main process exited, code=dumped, status=6/ABRT As a headless system I can not use any UI controls so I suspect there is some command / config that needs to to be set before launching rdp ** Affects: gnome-remote-desktop (Ubuntu) Importance: Low Status: Triaged ** Description changed: Asked to create a new bug from https://bugs.launchpad.net/ubuntu/+source/gnome-remote- desktop/+bug/206 - I am on a completely headless system starting from a minimal ubuntu-server 24.04 installation. - I have installed the desktop using apt install ubuntu-desktop + I am on a completely headless system starting from a minimal ubuntu-server 24.04 installation. + I have installed the desktop using apt install ubuntu-desktop I want to use the new gnome-remote-desktop so that I can create a developer machine in a VM environment that can be accessed through a - thin client using Microsoft RDP + thin client as an example using Microsoft RDP I suspect there is some missing documentation. Starting the service using systemctl start gnome-remote-desktop.service results in: journalctl -xeu gnome-remote-desktop.service Apr 30 10:16:39 localhost systemd[1]: Starting gnome-remote-desktop.service - GNOME Remote Desktop... ░░ Subject: A start job for unit gnome-remote-desktop.service has begun execution ░░ Defined-By: systemd ░░ Support: http://www.ubuntu.com/support ░░ ░░ A start job for unit gnome-remote-desktop.service has begun execution. ░░ ░░ The job identifier is 2929. Apr 30 10:16:39 localhost (p-daemon)[1613]: gnome-remote-desktop.service: Failed to determine user credentials: No such process Apr 30 10:16:39 localhost systemd[1]: gnome-remote-desktop.service: Main process exited, code=exited, status=217/USER ░░ Subject: Unit process exited ░░ Defined-By: systemd ░░ Support: http://www.ubuntu.com/support ░░ ░░ An ExecStart= process belonging to unit gnome-remote-desktop.service has exited. ░░ ░░ The process' exit code is 'exited' and its exit status is 217. - Running sudo systemd-sysusers does create some new users, restarting the remote desktop now gives: May 02 14:27:47 localhost gnome-remote-de[36906]: Init TPM credentials failed because No TPM device found, using GKeyFile as fallback May 02 14:27:47 localhost gnome-remote-de[36906]: Init file credentials failed: Error creating directory /var/lib/gnome-remote-desktop: Permission denied May 02 14:27:47 localhost gnome-remote-desktop-daemon[36906]: ** May 02 14:27:47 localhost gnome-remote-desktop-daemon[36906]:
[Bug 2063333] Re: gnome-remote-desktop.service: Failed to determine user credentials: No such process
I using it in a cloud provider using ssh, I want to be able to configure it completely headless. I can not log into the UI. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/206 Title: gnome-remote-desktop.service: Failed to determine user credentials: No such process To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-remote-desktop/+bug/206/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2063333] Re: gnome-remote-desktop.service: Failed to determine user credentials: No such process
Nothing really reported from running the above command /usr/libexec/gnome-remote-desktop-daemon --system ** (gnome-remote-desktop-daemon:36048): WARNING **: 11:01:25.879: Init TPM credentials failed because No TPM device found, using GKeyFile as fallback But no ports are open netstat -tnlp Active Internet connections (only servers) Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name tcp0 0 127.0.0.1:631 0.0.0.0:* LISTEN 29997/cupsd tcp0 0 127.0.0.54:53 0.0.0.0:* LISTEN 16105/systemd-resol tcp0 0 127.0.0.53:53 0.0.0.0:* LISTEN 16105/systemd-resol tcp6 0 0 ::1:631 :::*LISTEN 29997/cupsd tcp6 0 0 :::22 :::*LISTEN 1/systemd I restarted GDM3 ps -aux | grep gnome gdm35757 0.0 0.6 233060 6144 tty1 Ssl+ 11:01 0:00 /usr/libexec/gdm-wayland-session dbus-run-session -- gnome-session --autostart /usr/share/gdm/greeter/autostart gdm35761 0.0 0.2 6500 2432 tty1 S+ 11:01 0:00 dbus-run-session -- gnome-session --autostart /usr/share/gdm/greeter/autostart gdm35763 0.0 1.8 518252 18304 tty1 Sl+ 11:01 0:00 /usr/libexec/gnome-session-binary --autostart /usr/share/gdm/greeter/autostart gdm35772 1.0 22.0 3251940 217456 tty1 Sl+ 11:01 0:01 /usr/bin/gnome-shell gdm35799 0.0 0.7 236060 7552 tty1 Sl+ 11:01 0:00 /usr/libexec/at-spi2-registryd --use-gnome-session gdm35822 0.0 2.7 2590472 26852 tty1Sl+ 11:01 0:00 /usr/bin/gjs -m /usr/share/gnome-shell/org.gnome.Shell.Notifications gdm36027 0.0 2.7 2590464 26860 tty1Sl+ 11:01 0:00 /usr/bin/gjs -m /usr/share/gnome-shell/org.gnome.ScreenSaver root 36090 0.0 1.7 439656 16896 ttyS0Sl+ 11:02 0:00 /usr/libexec/gnome-remote-desktop-daemon --system -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/206 Title: gnome-remote-desktop.service: Failed to determine user credentials: No such process To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-remote-desktop/+bug/206/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2063333] Re: gnome-remote-desktop.service: Failed to determine user credentials: No such process
Also seeing the same issue on a headless server (Linode) 24.04 Ubuntu server Installed ubuntu-desktop cat /etc/os-release PRETTY_NAME="Ubuntu 24.04 LTS" NAME="Ubuntu" VERSION_ID="24.04" VERSION="24.04 LTS (Noble Numbat)" VERSION_CODENAME=noble ID=ubuntu ID_LIKE=debian HOME_URL="https://www.ubuntu.com/; SUPPORT_URL="https://help.ubuntu.com/; BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/; PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy; UBUNTU_CODENAME=noble LOGO=ubuntu-logo journalctl -xeu gnome-remote-desktop.service Apr 30 10:16:39 localhost systemd[1]: Starting gnome-remote-desktop.service - GNOME Remote Desktop... ░░ Subject: A start job for unit gnome-remote-desktop.service has begun execution ░░ Defined-By: systemd ░░ Support: http://www.ubuntu.com/support ░░ ░░ A start job for unit gnome-remote-desktop.service has begun execution. ░░ ░░ The job identifier is 2929. Apr 30 10:16:39 localhost (p-daemon)[1613]: gnome-remote-desktop.service: Failed to determine user credentials: No such process Apr 30 10:16:39 localhost systemd[1]: gnome-remote-desktop.service: Main process exited, code=exited, status=217/USER ░░ Subject: Unit process exited ░░ Defined-By: systemd ░░ Support: http://www.ubuntu.com/support ░░ ░░ An ExecStart= process belonging to unit gnome-remote-desktop.service has exited. ░░ ░░ The process' exit code is 'exited' and its exit status is 217. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/206 Title: gnome-remote-desktop.service: Failed to determine user credentials: No such process To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-remote-desktop/+bug/206/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2061228] Re: Upgrading Ubuntu Jammy to Ubuntu Noble fails with error message
*** This bug is a duplicate of bug 2054761 *** https://bugs.launchpad.net/bugs/2054761 Got the same or similar error. While doing a do-release-update from 22.04 to 24.04 it crashed halfway the installation of packages. After rebooting could only get a terminal window using ctrl-alt-F2. I tried to do a dpkg --configure -a but that feild due to too many errors. It turned out that networking did not work because the resolv wa not there. I do not know how to reinstall that. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2061228 Title: Upgrading Ubuntu Jammy to Ubuntu Noble fails with error message To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/2061228/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2061986] Re: Mount CIFS fails with Permission denied
Attaching tcpdump output without patch ** Attachment added: "base_5_15_104_filtered.pcap" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2061986/+attachment/5766752/+files/base_5_15_104_filtered.pcap -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2061986 Title: Mount CIFS fails with Permission denied To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2061986/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2061986] Re: Mount CIFS fails with Permission denied
Attaching tcpdump output with patch ** Attachment added: "base_5_15_104_with_patch_filtered.pcap" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2061986/+attachment/5766753/+files/base_5_15_104_with_patch_filtered.pcap -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2061986 Title: Mount CIFS fails with Permission denied To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2061986/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2061986] [NEW] Mount CIFS fails with Permission denied
Public bug reported: [ Impact ] * Mounting SMB share from server without Key Exchange capability is failing with Access Denied error * Even though SMB server during Session Setup Response in NTLMSSP_CHALLANGE message does not advertise Key Exchange capabilities SMB client < 5.16 will forcefully use it leading to error response during TCON requests. * Issue can be reproduced on 5.15 or older Kernels, there is no reproduction on 6.5 Kernel * This scenario was fixed in upstream commit 9de0737d5ba0425c3154d5d83da12a8fa8595c0f * An example of server without Key Exchange capability is Oracle Solaris 11.4 SMB zfs, meaning mounting share from that server will result in ACCESS_DENIED error. [ Test Plan ] * So far issue was reported only with Oracle Solaris 11.04 smb server and Ubuntu with Kernel <= 5.15 * To reproduce, setup Oracle Solaris SMB server and try to mount share on 22.04/20.04 (5.15/5.04) Steps to configure SMB server: 1. Download the ISO for Oracle Solaris Common Build Edition [1] 2. Create a VM with at least 16 GB of memory - I have experienced installation issues with less memory 3. Install Oracle Solaris using the downloaded ISO a. Make sure to create a test user 4. Log into the VM as the root user 5. Create a test directory for the share: a. mkdir /smbshare && chmod 777 /smbshare 6. Disable the normal Samba daemon: [2] a. svcadm disable svc:/network/samba b. svcadm disable svc:/network/wins 7 Configure the server to serve Samba shares using ZFS in Workgroup mode [3] a. svcadm enable -r smb/server b. smbadm join -w workgroup 8 Update the /etc/pam.d/other file to require authentication by adding the following line: a. password requiredpam_smb_passwd.so.1nowarn 9. Reset the password for the test user so that it is updated in the SMB password database 10. Create the pool and share it using Samba: [4] a. zfs create -o mountpoint=/smbshare/ rpool/smbshare b. zfs share -o share.smb=on rpool/smbshare%share [1] <https://www.oracle.com/solaris/solaris11/downloads/solaris-downloads.html> [2] <https://docs.oracle.com/cd/E26502_01/html/E29004/migratingfromsamba.html#scrolltoc> [3] <https://docs.oracle.com/cd/E26502_01/html/E29004/configuringoperationmodetm.html#configureworkgroupmodetask> [4] <https://docs.oracle.com/cd/E26502_01/html/E29004/managingsmbshares.html#createstaticsmbsharezfstask> * With server configured, mount share using ubuntu SMB client Expected result: mount operation should succeed Actual result: mount returns following error: root@ubuntu20:/mnt# mount -t cifs -o username=rmalz //192.168.50.217/smbshare test Password for rmalz@//192.168.50.217/smbshare: mount error(13): Permission denied Refer to the mount.cifs(8) manual page (e.g. man mount.cifs) and kernel log messages (dmesg) [ Where problems could occur ] * Upstream patch is changing smb client behavior based on server NTLMSSP_CHALLENGE Negotiate Flags, if server does not advertise Key Exchange Capability but requires it from client communication might be broken. It is unknown if such servers are used, such instance should be treated as a server bug. * Patch is available in upstream kernel since 5.16, any issues associated with it should be already detected. * Patch adds additional requirement checks on server NTLM flags, although it is possible to hit these checks, I was not able to find any instances of that occurring. * To lower regression potential, upstream patch backported to Ubuntu 5.15 and 5.04 Kernels have been tested in following environments: smb server: Oracle Solaris 11.04, Ubuntu 22.04 HWE smb client: Ubuntu 22.04, Ubuntu 20.04 During testing no issues have been detected. [ Other Info ] * Error message coming from SMB client is the same as providing incorrect credentials, which might confuse users. * Attaching tcpdump pcaps with SMB operations from 5.15 Kernel with and without patch. ** Affects: linux (Ubuntu) Importance: Medium Assignee: Robert Malz (rmalz) Status: New ** Affects: linux (Ubuntu Focal) Importance: Medium Assignee: Robert Malz (rmalz) Status: New ** Affects: linux (Ubuntu Jammy) Importance: Medium Assignee: Robert Malz (rmalz) Status: New ** Changed in: linux (Ubuntu) Assignee: (unassigned) => Robert Malz (rmalz) ** Changed in: linux (Ubuntu) Importance: Undecided => Medium ** Also affects: linux (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Jammy) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Focal) Assignee: (unassigned) => Robert Malz (rmalz) ** Changed in: linux (Ubuntu Jammy) Assignee: (unassigned) => Robert Malz (rmalz) ** Changed in: linux (Ubuntu Focal) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Jammy)
[Bug 1898783] Re: kcmshell5 user_manager autologin (with sddm) fail on user deletion
Expected behavior: Display error message and/or show logon screen User is able to make GUI unusable when deleting account configured with autologin -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1898783 Title: kcmshell5 user_manager autologin (with sddm) fail on user deletion To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sddm-kcm/+bug/1898783/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1898783] Re: kcmshell5 user_manager autologin (with sddm) fail on user deletion
Not solved in kubuntu 23.10 Easier way to reproduce: Create file /etc/sddm.conf.d/kde_settings.conf with content [Autologin] Relogin=false Session=plasma User=nonexistentuser ** Changed in: sddm-kcm (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1898783 Title: kcmshell5 user_manager autologin (with sddm) fail on user deletion To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sddm-kcm/+bug/1898783/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2051720]
(In reply to Luiz Von Dentz from comment #16) > Can you guys try with the following change: > > https://patchwork.kernel.org/project/bluetooth/patch/20240401193515.2525201- > 1-luiz.de...@gmail.com/ I have the same issue and applied this patch to my kernel, but it seems to have broken the btintel module. I get a null pointer deref on boot and bluetooth is broken: [2.317366] BUG: kernel NULL pointer dereference, address: 0070 [2.317699] #PF: supervisor read access in kernel mode [2.317993] #PF: error_code(0x) - not-present page [2.318280] PGD 0 P4D 0 [2.318283] Oops: [#1] PREEMPT SMP NOPTI [2.318842] CPU: 3 PID: 185 Comm: kworker/u33:0 Not tainted 6.8.3-gentoo-dist #1 [2.318844] Hardware name: AZW SER/SER, BIOS SER7PRO_P5C8V30 09/15/2023 [2.318845] Workqueue: hci0 hci_alloc_dev_priv [bluetooth] [2.319426] RIP: 0010:btintel_configure_setup+0x245/0x970 [btintel] [2.320365] Code: 85 ff 75 a1 f0 41 80 8e 51 06 00 00 02 f0 41 80 8e 51 06 00 00 04 f0 41 80 8e 51 06 00 00 08 49 c7 86 38 17 00 00 b0 63 66 c1 <83> 7b 70 0a 75 7b 48 8b 83 d0 00 00 00 80 78 01 37 75 6e 0f 1f 44 [2.320691] RSP: 0018:a215005cfd48 EFLAGS: 00010202 [2.321452] RAX: RBX: RCX: 8026 [2.321760] RDX: 8027 RSI: d3238404d700 RDI: [2.322437] RBP: 91a940ccc6c8 R08: 8027 R09: 8026 [2.322438] R10: 0001 R11: R12: 91a940ccc6d0 [2.322439] R13: 91a947f50c00 R14: 91a940ccc000 R15: 91a940ccca88 [2.322441] FS: () GS:91af820c() knlGS: [2.323737] CS: 0010 DS: ES: CR0: 80050033 [2.323739] CR2: 0070 CR3: 00010dfa2000 CR4: 00f50ef0 [2.323740] PKRU: 5554 [2.323740] Call Trace: [2.323743] [2.326248] ? __die_body+0x68/0xb0 [2.326253] ? page_fault_oops+0x3a3/0x400 [2.326256] ? exc_page_fault+0x60/0xf0 [2.326265] ? asm_exc_page_fault+0x26/0x30 [2.326269] ? btintel_configure_setup+0x245/0x970 [btintel] [2.328091] ? btintel_configure_setup+0x16c/0x970 [btintel] [2.328093] ? __ia32_compat_sys_sysinfo+0x230/0x270 [2.329006] hci_dev_open_sync+0x166/0x1610 [bluetooth] [2.329013] ? srso_alias_return_thunk+0x5/0xfbef5 [2.329015] ? srso_alias_return_thunk+0x5/0xfbef5 [2.329016] ? srso_alias_return_thunk+0x5/0xfbef5 [2.329018] hci_alloc_dev_priv+0x164e/0x1bc0 [bluetooth] [2.329023] process_scheduled_works+0x24b/0x450 [2.329026] worker_thread+0x2c3/0x420 [2.329028] ? __pfx_worker_thread+0x10/0x10 [2.329030] kthread+0xe8/0x110 [2.329032] ? __pfx_kthread+0x10/0x10 [2.329033] ret_from_fork+0x37/0x50 [2.329036] ? __pfx_kthread+0x10/0x10 [2.329038] ret_from_fork_asm+0x1b/0x30 [2.329043] [2.329043] Modules linked in: amdxcp(+) ac97_bus(+) iwlwifi(+) snd_hda_codec(+) btusb snd_pcm_dmaengine gpu_sched vfat btbcm snd_pci_ps drm_suballoc_helper btintel i2c_algo_bit fat snd_rpl_pci_acp6x kvm(+) drm_ttm_helper snd_hda_core snd_acp_pci btrtl ttm snd_acp_legacy_common btmtk snd_pci_acp6x irqbypass drm_exec snd_hwdep snd_pci_acp5x snd_pcm drm_display_helper bluetooth snd_rn_pci_acp3x wmi_bmof cfg80211 snd_timer snd_acp_config rapl cec snd_soc_acpi snd pcspkr drm_buddy soundcore i2c_piix4 k10temp snd_pci_acp3x rfkill amd_pmc fuse loop nfnetlink crct10dif_pclmul crc32_pclmul crc32c_intel nvme polyval_clmulni polyval_generic ghash_clmulni_intel thunderbolt sha512_ssse3 sha256_ssse3 sha1_ssse3 nvme_core amd_sfh ccp sp5100_tco r8169 nvme_auth realtek video wmi i2c_hid_acpi i2c_hid serio_raw [2.329083] CR2: 0070 [2.329085] ---[ end trace ]--- [2.329087] RIP: 0010:btintel_configure_setup+0x245/0x970 [btintel] [2.329089] Code: 85 ff 75 a1 f0 41 80 8e 51 06 00 00 02 f0 41 80 8e 51 06 00 00 04 f0 41 80 8e 51 06 00 00 08 49 c7 86 38 17 00 00 b0 63 66 c1 <83> 7b 70 0a 75 7b 48 8b 83 d0 00 00 00 80 78 01 37 75 6e 0f 1f 44 [2.329090] RSP: 0018:a215005cfd48 EFLAGS: 00010202 [2.329091] RAX: RBX: RCX: 8026 [2.329092] RDX: 8027 RSI: d3238404d700 RDI: [2.329093] RBP: 91a940ccc6c8 R08: 8027 R09: 8026 [2.329093] R10: 0001 R11: R12: 91a940ccc6d0 [2.329094] R13: 91a947f50c00 R14: 91a940ccc000 R15: 91a940ccca88 [2.329095] FS: () GS:91af820c() knlGS: [2.329096] CS: 0010 DS: ES: CR0: 80050033 [2.329096] CR2: 0070 CR3: 00010dfa2000 CR4: 00f50ef0 [2.329097] PKRU: 5554 [2.329098] note: kworker/u33:0[185] exited with irqs disabled -- You received this bug notification because you are a member of
[Bug 2055761] Re: tracker-extract-3 crashed with SIGSYS in epoll_wait()
This is a new computer with the following specs: MB: MSI X670E tomahawk proc: AMD 7950X VIdeo: Nvidia 4070 ti Super Mem: 128 GB Kingston fury 6000 Installed Ubuntu 24.04 daily because 22.04 did not work with this hardware and the latest nvidia driver -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2055761 Title: tracker-extract-3 crashed with SIGSYS in epoll_wait() To manage notifications about this bug go to: https://bugs.launchpad.net/tracker/+bug/2055761/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2058491] [NEW] (mate-appearance-properties : GTK+ 2.x symbols detected. Using GTK+ 2.x and GTK+ 3 in the same process
Public bug reported: Appears to be cross-compiled with both GTK+2 and GTK+3 flags. Fails to start due to error: (mate-appearance-properties:15895): Gtk-ERROR **: 17:02:39.177: GTK+ 2.x symbols detected. Using GTK+ 2.x and GTK+ 3 in the same process is not supported I know this is coming from a rather old version of Ubuntu 18.04, but there is a reason why I'm running an old installation, and the lack of resources is why I am running Mate. Thought I should at least let you know this is happening. ** Affects: ubuntu-mate-settings (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/2058491 Title: (mate-appearance-properties : GTK+ 2.x symbols detected. Using GTK+ 2.x and GTK+ 3 in the same process To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-mate-settings/+bug/2058491/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2054872] Re: Cannot change IRQ 70 affinity: Input/output error
irqbalance 1.9.3-2ubuntu4 verified on 6.8.0-11-generic Issue no longer reproduces. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2054872 Title: Cannot change IRQ 70 affinity: Input/output error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/irqbalance/+bug/2054872/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2058143] Re: Decoding glitchy on GM45 - MR has been pending since 2020
So the MR fixing the particular glitch I'm seeing on my Thinkpad T400 / GM45 is https://github.com/intel/intel-vaapi-driver/pull/514 . Including that would be enough to close this bug - it's pretty small and straight forward. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2058143 Title: Decoding glitchy on GM45 - MR has been pending since 2020 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/intel-vaapi-driver/+bug/2058143/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2058143] [NEW] Decoding glitchy on GM45 - MR has been pending since 2020
Public bug reported: Ubuntu 24.04 will ship with Gstreamer 1.24, which finally promoted many "va*" plugins to primary, i.e. enabled them by default and will thus be used by more apps than in the past. I tested this on an old Thinkpad T400 / Intel GM45 and ran into a glitch. Fortunately there's pending MR (see below) fixing that - but Intel does not seem to maintain https://github.com/intel/intel-vaapi- driver any more, so it will likely never get merged or released. I'd thus like to request to add the MR in question to the Debian/Ubuntu package. However, while on it, it might sense to add a few more fixes that have accumulated: - All new commits on the master branch (~7?) - https://github.com/intel/intel-vaapi-driver/pull/566, which will be needed for upcoming Wayland compositor changes. - https://github.com/intel/intel-vaapi-driver/pull/514 which fixes glitches for e.g. Gstreamer based players on very old generations (GM45). I tested/verified this one myself. - Potentially: https://github.com/intel/intel-vaapi-driver/pull/530 - unfortunately I don't have the hardware to verify this one. If you prefer, I can also try to open a MR at https://salsa.debian.org/multimedia-team/intel-vaapi- driver/-/merge_requests - but I'm not very used to the debian packaging workflow. Thanks for considering :) ** Affects: intel-vaapi-driver (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/2058143 Title: Decoding glitchy on GM45 - MR has been pending since 2020 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/intel-vaapi-driver/+bug/2058143/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2024937]
For those looking for a work around: I use gnupg instead and it works for me even better than ssh agent. Gnupg can be autostarted via systemd. The configuration was not obvious though. A few pointers: - https://wiki.archlinux.org/title/GnuPG#SSH_agent - https://unix.stackexchange.com/a/423516 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2024937 Title: ssh-agent is not started via startplasma-wayland To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/plasma-workspace/+bug/2024937/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2054872] Re: Cannot change IRQ 70 affinity: Input/output error
174955 233311 126152
160532 145524 171051 153168 119414 134045 Function call interrupts
+ TLB: 94988 98433 115358 96450 118525 98758 124773 94916 123529 90824 119527
95110 120917 98504 107344 96577 TLB shootdowns
+ TRM: 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 Thermal event interrupts
+ THR: 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 Threshold APIC interrupts
+ DFR: 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 Deferred Error APIC interrupts
+ MCE: 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 Machine check exceptions
+ MCP: 15 15 15 15 15 15 15 15 15 15 15 15 15 15 15 15 Machine check polls
+ ERR: 1
+ MIS: 0
+ PIN: 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 Posted-interrupt notification event
+ NPI: 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 Nested posted-interrupt event
+ PIW: 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 Posted-interrupt wakeup event
** Patch added: "noble.debdiff"
https://bugs.launchpad.net/ubuntu/+source/irqbalance/+bug/2054872/+attachment/5756029/+files/noble.debdiff
** Changed in: irqbalance (Ubuntu)
Importance: Undecided => Medium
** Changed in: irqbalance (Ubuntu)
Status: Incomplete => In Progress
** Changed in: irqbalance (Ubuntu)
Assignee: (unassigned) => Robert Malz (rmalz)
** Also affects: irqbalance (Ubuntu Noble)
Importance: Medium
Assignee: Robert Malz (rmalz)
Status: 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/2054872
Title:
Cannot change IRQ 70 affinity: Input/output error
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/irqbalance/+bug/2054872/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 2055114] Re: fail2ban is broken in 24.04 Noble
This does make it run. Thank you.
-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-
Eskimo North Linux Friendly Internet Access, Shell Accounts, and Hosting.
Knowledgeable human assistance, not telephone trees or script readers.
See our web site: http://www.eskimo.com/ (206) 812-0051 or (800) 246-6874.
On Sun, 10 Mar 2024, Åka Sikrom wrote:
> Date: Sun, 10 Mar 2024 12:30:18 -
> From: Åka Sikrom <2055...@bugs.launchpad.net>
> To: nan...@eskimo.com
> Subject: [Bug 2055114] Re: fail2ban is broken in 24.04 Noble
>
> As of this commit from 12 Dec 2023:
> https://github.com/fail2ban/fail2ban/commit/1024452fe1befeb5a0a014386a81ec183cd45bb5
> upstream ships its source with the missing async* libraries embedded,
> which solves the issue for now.
>
>
> Here is a suggested workaround for Noble until the fix hopefully finds its
> way into the repos.
>
> DISCLAMER: Try at your own risk. I am not an Ubuntu/Debian developer.
> Next time you receive a proper package update of fail2ban via apt, any
> of the manually-downloaded files below may cause conflicts and break
> your system.
>
> mkdir -m 0755 /usr/lib/python3/dist-packages/fail2ban/compat
> wget -O /usr/lib/python3/dist-packages/fail2ban/compat/asynchat.py
> https://github.com/fail2ban/fail2ban/raw/1024452fe1befeb5a0a014386a81ec183cd45bb5/fail2ban/compat/asynchat.py
> wget -O /usr/lib/python3/dist-packages/fail2ban/compat/asyncore.py
> https://github.com/fail2ban/fail2ban/raw/1024452fe1befeb5a0a014386a81ec183cd45bb5/fail2ban/compat/asyncore.py
> cp -p
> /usr/lib/python3/dist-packages/fail2ban/server/asyncserver.py{,.original}
> wget -O /usr/lib/python3/dist-packages/fail2ban/server/asyncserver.py
> https://github.com/fail2ban/fail2ban/raw/1024452fe1befeb5a0a014386a81ec183cd45bb5/fail2ban/server/asyncserver.py
>
> My custom-boostrapped Noble test system is also missing the required
> 'distutils' Python module by default. The fail2ban package does not have
> 'python3-setuptools' listed under "Depends" in its control file, which
> it possibly should at this point. Official Ubuntu images may already
> have it installed via other packages, but if not, you will need to
> install it as well:
>
> apt install python3-setuptools
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/2055114
>
> Title:
> fail2ban is broken in 24.04 Noble
>
> Status in fail2ban package in Ubuntu:
> Confirmed
>
> Bug description:
> Was working in 22.04, but after upgrading to 24.04 I get this:
>
> × fail2ban.service - Fail2Ban Service
> Loaded: loaded (/etc/systemd/system/fail2ban.service; enabled; preset:
> enabled)
> Active: failed (Result: exit-code) since Sun 2024-02-25 02:27:29 PST; 1
> day 18h ago
> Duration: 2.330s
> Docs: man:fail2ban(1)
> Process: 1130 ExecStartPre=/bin/mkdir -p /run/fail2ban (code=exited,
> status=0/SUCCESS)
> Process: 1133 ExecStart=/usr/local/bin/fail2ban-server -xf start
> (code=exited, status=255/EXCEPTION)
> Main PID: 1133 (code=exited, status=255/EXCEPTION)
> CPU: 660ms
>
> Feb 25 02:27:26 mx1 systemd[1]: Starting fail2ban.service - Fail2Ban
> Service...
> Feb 25 02:27:26 mx1 systemd[1]: Started fail2ban.service - Fail2Ban Service.
> Feb 25 02:27:28 mx1 fail2ban-server[1133]: 2024-02-25 02:27:28,952 fail2ban
> [1133]: ERROR No module named 'asynchat'
> Feb 25 02:27:29 mx1 systemd[1]: fail2ban.service: Main process exited,
> code=exited, status=255/EXCEPTION
> Feb 25 02:27:29 mx1 systemd[1]: fail2ban.service: Failed with result
> 'exit-code'.
>
> grep fail2ban syslog
> 2024-02-25T02:25:17.813593-08:00 mx1 systemd[1]: Stopping fail2ban.service -
> Fail2Ban Service...
> 2024-02-25T02:27:26.625640-08:00 mx1 systemd[1]: Starting fail2ban.service -
> Fail2Ban Service...
> 2024-02-25T02:27:26.678572-08:00 mx1 systemd[1]: Started fail2ban.service -
> Fail2Ban Service.
> 2024-02-25T02:27:28.954548-08:00 mx1 fail2ban-server[1133]: 2024-02-25
> 02:27:28,952 fail2ban[1133]: ERROR No module named
> 'asynchat'
> 2024-02-25T02:27:29.004733-08:00 mx1 systemd[1]: fail2ban.service: Main
> process exited, code=exited, status=255/EXCEPTION
> 2024-02-25T02:27:29.004834-08:00 mx1 systemd[1]: fail2ban.service: Failed
> with result 'exit-code'.
>
> Seems 24.04 is missing a python 3.12 module 'asynchat'.
>
> This leaves my systems vulnerable to brute-force password guessing
> attacks.
>
> ProblemType: Bug
> DistroRelease: Ubuntu 24.04
> Package: fail2ban 1.0.2-3
> Uname: Linux 6.7.6 x86_64
> ApportVersion: 2.28.0-0ubuntu1
> Architecture: amd64
> CasperMD5CheckResult: unknown
> CurrentDesktop: MATE
> Date: Mon Feb 26 20:33:12 2024
> InstallationDate: Installed on 2017-08-14 (2388 days ago)
> InstallationMedia: Ubuntu-MATE 17.04 "Zesty Zapus" - Release amd64 (20170412)
> PackageArchitecture: all
> SourcePackage: fail2ban
>
[Bug 2055114] Re: fail2ban is broken in 24.04 Noble
I wish people wouldn't use languages like python which changes it's packages and syntax weekly, but since they do the obvious question, is anyone going to work on this? It is a rather important security tool. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2055114 Title: fail2ban is broken in 24.04 Noble To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fail2ban/+bug/2055114/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2055782] [NEW] Installation of linux crashes installing grub to dedicated disk
Public bug reported: 4Tb SSD Disk was wiped for this install ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: ubiquity 22.04.20 ProcVersionSignature: Ubuntu 6.2.0-26.26~22.04.1-generic 6.2.13 Uname: Linux 6.2.0-26-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.470.2 CurrentDesktop: ubuntu:GNOME Date: Sat Mar 2 08:52:40 2024 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz nomodeset file=/cdrom/preseed/ubuntu.seed maybe-ubiquity quiet splash --- LiveMediaBuild: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230807.2) RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: grub-installer UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: grub-installer (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy ubiquity-22.04.20 ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2055782 Title: Installation of linux crashes installing grub to dedicated disk To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/2055782/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2036239] Re: Intel E810-XXV - NETDEV WATCHDOG: (ice): transmit queue timed out
** Tags removed: verification-needed-mantic-linux ** Tags added: verification-done-mantic-linux -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2036239 Title: Intel E810-XXV - NETDEV WATCHDOG: (ice): transmit queue timed out To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2036239/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2036239] Re: Intel E810-XXV - NETDEV WATCHDOG: (ice): transmit queue timed out
LP update: Mantic update: Due to lack of reproduction environment I have been performing following regression test: 1. Setup: nic: 2port E810-C both interfaces set up in bonding kernel: 6.5.0-25-generic 2. Test cases: 0) verified that code from the change is used during driver init a) stress traffic for 12h (multiple streams of iperf (tcp)) b) if up/down during stress traffic c) reload driver during stress traffic Look for any issues related to traffic processing, look for tx_hangs 3. Result: No issues have been detected during test execution -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2036239 Title: Intel E810-XXV - NETDEV WATCHDOG: (ice): transmit queue timed out To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2036239/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2036239] Re: Intel E810-XXV - NETDEV WATCHDOG: (ice): transmit queue timed out
Hi Roxana, Mantic verification is still not finished. I did some touch tests without stress traffic. I'm trying to get my hands on E810 device to finish testing, I'll update ticket once it's done. Wishful ETA EOW 09. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2036239 Title: Intel E810-XXV - NETDEV WATCHDOG: (ice): transmit queue timed out To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2036239/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 2023322]
Bug driver 470, Nvidia GTX 650 W dniu 26.02.2024 o 04:06, Craig pisze: > (In reply to Michael Catanzaro from comment #62) >> Hi Craig and Thomas (and Emil if you're still around): if you're still >> encountering problems with NVIDIA graphics, please report new a bug and >> leave a comment here linking to the new bug. > My problem was on legacy nvidia driver, and newer versions wouldn't even > start. But I now know a workaround (GSK_RENDERER=cairo) and don't expect > there will be a fix for my old driver anyway. > https://gitlab.gnome.org/GNOME/gtk/-/issues/5858 > ** Attachment added: "Zrzut ekranu z 2024-02-26 14-51-55.png" https://bugs.launchpad.net/bugs/2023322/+attachment/5749476/+files/Zrzut%20ekranu%20z%202024-02-26%0A%2014-51-55.png ** Attachment added: "Zrzut ekranu z 2024-02-26 14-52-37.png" https://bugs.launchpad.net/bugs/2023322/+attachment/5749477/+files/Zrzut%20ekranu%20z%202024-02-26%0A%2014-52-37.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2023322 Title: GTK internal browser does not render with Nvidia drivers To manage notifications about this bug go to: https://bugs.launchpad.net/webkit/+bug/2023322/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: unixodbc-dev 2.3.11 seems broken
Now I'm not sure unixodbc-dev from Ubuntu is compatible with msodbc17/18 drivers. Anyway, here is the link of the opened issue on the github: https://github.com/microsoft/linux-package-repositories/issues/36 On Tue, Feb 14, 2023 at 5:45 AM Nicholas Guriev wrote: > On 12.02.2023 02:46:37 MSK Robert Ayrapetyan wrote: > > You're right, it came from: > > > > https://packages.microsoft.com/ubuntu/20.04/prod focal/main amd64 > > unixodbc-dev amd64 2.3.11 [42.1 kB] > > > > What's the best way to install the right package (2.3.11-2) without > > removing MS repo? > > You can lower priority of Microsoft's repository putting the following in > the > /etc/apt/preferences file. > > Package: * > Pin: origin "packages.microsoft.com" > Pin-Priority: 100 > > See apt_preferences(5) for details. > -- > Ubuntu-devel-discuss mailing list > Ubuntu-devel-discuss@lists.ubuntu.com > Modify settings or unsubscribe at: > https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss > -- Ubuntu-devel-discuss mailing list Ubuntu-devel-discuss@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss
Re: unixodbc-dev 2.3.11 seems broken
Do you know what's the best way to report this issue to the maintainers of MS repo? On Sat, Feb 11, 2023 at 4:41 PM Thomas Ward wrote: > Unfortunately here your choices are limited. The ODBC from Microsoft is > different than the one in the repos and the two packages conflict. > > From my experience you will have to pick one or the other - use > Microsoft's packaged ODBC and no headers, or use the one in the repos with > the headers and not use Microsoft. > > > > Sent from my Galaxy > > > > ---- Original message > From: Robert Ayrapetyan > Date: 2/11/23 18:56 (GMT-05:00) > To: ubuntu-devel-discuss@lists.ubuntu.com > Subject: Re: unixodbc-dev 2.3.11 seems broken > > Seems it comes as part of msodbcsql18 from official MS repository... > > On Sat, Feb 11, 2023 at 3:46 PM Robert Ayrapetyan < > robert.ayrapet...@gmail.com> wrote: > >> You're right, it came from: >> >> https://packages.microsoft.com/ubuntu/20.04/prod focal/main amd64 >> unixodbc-dev amd64 2.3.11 [42.1 kB] >> >> What's the best way to install the right package (2.3.11-2) without >> removing MS repo? >> >> On Sat, Feb 11, 2023 at 3:09 PM Colin Watson wrote: >> >>> On Sat, Feb 11, 2023 at 10:13:13AM -0800, Robert Ayrapetyan wrote: >>> > # lsb_release -a >>> > No LSB modules are available. >>> > Distributor ID: Ubuntu >>> > Description:Ubuntu 20.04.5 LTS >>> > Release:20.04 >>> > Codename: focal >>> > >>> > >>> > # apt show unixodbc-dev >>> > Package: unixodbc-dev >>> > Version: 2.3.11 >>> >>> This is not a package that comes from Ubuntu 20.04, and in fact it >>> doesn't appear to have come from any version of Ubuntu at all (versions >>> of unixodbc-dev provided by Ubuntu have some kind of suffix after the >>> upstream version number - for example, the version in Ubuntu 22.10 is >>> 2.3.11-2). Where did you get it from? The package is clearly broken, >>> but that isn't an Ubuntu problem - perhaps you should reinstall the >>> working version from Ubuntu. >>> >>> -- >>> Colin Watson (he/him) [cjwat...@ubuntu.com] >>> >>> -- >>> Ubuntu-devel-discuss mailing list >>> Ubuntu-devel-discuss@lists.ubuntu.com >>> Modify settings or unsubscribe at: >>> https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss >>> >> -- Ubuntu-devel-discuss mailing list Ubuntu-devel-discuss@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss
Re: unixodbc-dev 2.3.11 seems broken
Seems it comes as part of msodbcsql18 from official MS repository... On Sat, Feb 11, 2023 at 3:46 PM Robert Ayrapetyan < robert.ayrapet...@gmail.com> wrote: > You're right, it came from: > > https://packages.microsoft.com/ubuntu/20.04/prod focal/main amd64 > unixodbc-dev amd64 2.3.11 [42.1 kB] > > What's the best way to install the right package (2.3.11-2) without > removing MS repo? > > On Sat, Feb 11, 2023 at 3:09 PM Colin Watson wrote: > >> On Sat, Feb 11, 2023 at 10:13:13AM -0800, Robert Ayrapetyan wrote: >> > # lsb_release -a >> > No LSB modules are available. >> > Distributor ID: Ubuntu >> > Description:Ubuntu 20.04.5 LTS >> > Release:20.04 >> > Codename: focal >> > >> > >> > # apt show unixodbc-dev >> > Package: unixodbc-dev >> > Version: 2.3.11 >> >> This is not a package that comes from Ubuntu 20.04, and in fact it >> doesn't appear to have come from any version of Ubuntu at all (versions >> of unixodbc-dev provided by Ubuntu have some kind of suffix after the >> upstream version number - for example, the version in Ubuntu 22.10 is >> 2.3.11-2). Where did you get it from? The package is clearly broken, >> but that isn't an Ubuntu problem - perhaps you should reinstall the >> working version from Ubuntu. >> >> -- >> Colin Watson (he/him) [cjwat...@ubuntu.com] >> >> -- >> Ubuntu-devel-discuss mailing list >> Ubuntu-devel-discuss@lists.ubuntu.com >> Modify settings or unsubscribe at: >> https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss >> > -- Ubuntu-devel-discuss mailing list Ubuntu-devel-discuss@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss
Re: unixodbc-dev 2.3.11 seems broken
You're right, it came from: https://packages.microsoft.com/ubuntu/20.04/prod focal/main amd64 unixodbc-dev amd64 2.3.11 [42.1 kB] What's the best way to install the right package (2.3.11-2) without removing MS repo? On Sat, Feb 11, 2023 at 3:09 PM Colin Watson wrote: > On Sat, Feb 11, 2023 at 10:13:13AM -0800, Robert Ayrapetyan wrote: > > # lsb_release -a > > No LSB modules are available. > > Distributor ID: Ubuntu > > Description:Ubuntu 20.04.5 LTS > > Release:20.04 > > Codename: focal > > > > > > # apt show unixodbc-dev > > Package: unixodbc-dev > > Version: 2.3.11 > > This is not a package that comes from Ubuntu 20.04, and in fact it > doesn't appear to have come from any version of Ubuntu at all (versions > of unixodbc-dev provided by Ubuntu have some kind of suffix after the > upstream version number - for example, the version in Ubuntu 22.10 is > 2.3.11-2). Where did you get it from? The package is clearly broken, > but that isn't an Ubuntu problem - perhaps you should reinstall the > working version from Ubuntu. > > -- > Colin Watson (he/him) [cjwat...@ubuntu.com] > > -- > Ubuntu-devel-discuss mailing list > Ubuntu-devel-discuss@lists.ubuntu.com > Modify settings or unsubscribe at: > https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss > -- Ubuntu-devel-discuss mailing list Ubuntu-devel-discuss@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss
Re: unixodbc-dev 2.3.11 seems broken
More details: # lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 20.04.5 LTS Release:20.04 Codename: focal # apt show unixodbc-dev Package: unixodbc-dev Version: 2.3.11 Status: install ok installed Priority: extra Section: devel Source: unixodbc Maintainer: Ubuntu Developers Original-Maintainer: Steve Langasek Installed-Size: 1,739 kB Depends: unixodbc (= 2.3.11), odbcinst1debian2 (= 2.3.11), libltdl3-dev Conflicts: libiodbc2-dev, remembrance-agent (<< 2.11-4) Homepage: http://www.unixodbc.org/ Download-Size: unknown APT-Manual-Installed: yes APT-Sources: /var/lib/dpkg/status Description: ODBC libraries for UNIX (development files) # cat /usr/include/sqltypes.h | grep unixodbc.h * In these cases, the compiler uses #defines stored in unixodbc.h to determine the #include "unixodbc.h" # find / -name 'unixodbc*' /var/lib/dpkg/info/unixodbc.list /var/lib/dpkg/info/unixodbc-dev.list /var/lib/dpkg/info/unixodbc-dev.md5sums /var/lib/dpkg/info/unixodbc.md5sums /usr/share/doc/unixodbc /usr/share/doc/unixodbc-dev /usr/include/x86_64-linux-gnu/unixodbc_conf.h On Fri, Feb 10, 2023 at 8:40 PM Robert Ayrapetyan < robert.ayrapet...@gmail.com> wrote: > Hello, I've started to get: > > /usr/include/sqltypes.h:56:10: fatal error: unixodbc.h: No such file or > directory >56 | #include "unixodbc.h" > > when building certain packages. > As per list of files: > https://packages.ubuntu.com/focal/amd64/unixodbc-dev/filelist, unixodbc.h > is not part of it, but it's part of > ftp://ftp.unixodbc.org/pub/unixODBC/unixODBC-2.3.11.tar.gz. > > Am I missing something? Thanks. > > -- Ubuntu-devel-discuss mailing list Ubuntu-devel-discuss@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss
unixodbc-dev 2.3.11 seems broken
Hello, I've started to get: /usr/include/sqltypes.h:56:10: fatal error: unixodbc.h: No such file or directory 56 | #include "unixodbc.h" when building certain packages. As per list of files: https://packages.ubuntu.com/focal/amd64/unixodbc-dev/filelist, unixodbc.h is not part of it, but it's part of ftp://ftp.unixodbc.org/pub/unixODBC/unixODBC-2.3.11.tar.gz. Am I missing something? Thanks. -- Ubuntu-devel-discuss mailing list Ubuntu-devel-discuss@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss
Plans to update rsync?
Hello, I could not, for the life of me, figure out how to report a bug or request a package to be updated (other than emailing this list or getting on IRC). But thought I'd give this a try. In rsync 3.2.3, there is a bug when the remote shell is zsh, it sends some unescaped characters when using `--chown` flag. This is fixed in 3.2.5. Currently, Jammy is shipping 3.2.3, are there any plans to upgrade rsync? The only known workaround is to install an 'out-of-tree' version of rsync or switch the remote shell to bash. Robert Landers Software Engineer Utrecht NL -- Ubuntu-devel-discuss mailing list Ubuntu-devel-discuss@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss
Re: [ubuntu-us-mi] Glitches with 22.04
I’m using 22.04 as a base image within Docker. Have not had any obvious issues. Regards, - Robert On Tue, Nov 8, 2022 at 5:49 PM Justin Macauley wrote: > Hi there, > > Anyone else experiencing major problems with the 22.04 lts version of > Ubuntu? Running slow on fast hardware for instance or your snap store > acting up? Any improvements in the short term release do you know? I've had > to do now two reinstalls of Ubuntu in the last several days and about ready > to disregard 22.04 till the next LTS update. Frustrated by it. Hoping > someone else has some thoughts. This issue seems to be made worse by the > installation of programs (glitches and bugs) into the os. > -- > ubuntu-us-mi mailing list > ubuntu-us-mi@lists.ubuntu.com > Modify settings or unsubscribe at: > https://lists.ubuntu.com/mailman/listinfo/ubuntu-us-mi > -- ubuntu-us-mi mailing list ubuntu-us-mi@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-us-mi
Re: Packaging New Software
Thank you both so much. I have been stuck trying to find a coherent tutorial on how to begin. The official packaging guide has clearly been abandoned years ago and nobody really cares. On Fri, Sep 9, 2022 at 2:00 PM Mechtilde wrote: > Hello Shafiei, > > I did a similar thing since some years > > https://salsa.debian.org/ddp-team/dpb > > The description itself is in German, but the script which description > begins in Part3 is in English > > You can find the book as PDF and the main script build-gbp.sh in the > CI/CD with download artifacts > > Kind regards > > Mechtilde > > Am 09.09.22 um 19:27 schrieb A. Shafiei: > > Hello, > > > > I have written a small tutorial for packaging new software with git. > > In case anyone is interested, it is found here: > > https://git.launchpad.net/~farsi-fonts/+git/tutorial/plain/build.sh > > > > old tutorial using bzr is found here: > > > https://packaging.ubuntu.com/html/packaging-new-software.html#starting-a-package > > > > Regards. > > > > > > -- > Mechtilde Stehmann > > ## Debian Developer > ## PGP encryption welcome > ## F0E3 7F3D C87A 4998 2899 39E7 F287 7BBA 141A AD7F > > -- > Ubuntu-motu mailing list > Ubuntu-motu@lists.ubuntu.com > Modify settings or unsubscribe at: > https://lists.ubuntu.com/mailman/listinfo/ubuntu-motu > -- Ubuntu-motu mailing list Ubuntu-motu@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-motu
Packaging New Software
My goal is to learn the correct and current process for packaging new software on Ubuntu 22.04 LTS. I am following the Packaging Guide and I have arrived at the section "Starting a Package" (4.2). https://packaging.ubuntu.com/html/packaging-new-software.html#starting-a-package I can see that the instructions require an old version of Ubuntu 22.04 in a container or virtual machine due to commands used in the example not being available in the current release. This indicates to me that this is not the current process that developers use to package new software anymore. Is there newer documentation of the current process that I can read and follow? -- Ubuntu-motu mailing list Ubuntu-motu@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-motu
[Bug 1978821] Re: libbrotli1 upgrade to 1.0.9 due to security
It's CVE-2020-8927 Apparently the earlier versions of Brotli have been patched, see https://usn.ubuntu.com/4568-1/ Still, it's confusing to see an earlier version and be unsure whether it was patched or not. I would think that a change from 1.0.3 or 1.0.7 to 1.0.9 would be safe. ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2020-8927 -- 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/1978821 Title: libbrotli1 upgrade to 1.0.9 due to security To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/brotli/+bug/1978821/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1977621] [NEW] Transparency come and go
Public bug reported: Prior to upgrading to 22.04 everything worked as expected, after upgrading my panels are no longer transparent. The mate-tweak settings are not properly applied during login or reboot. If I after reboot set my panels transparent again, sometimes it will let me, sometimes it won't. If it lets me, the next time I logout and login again they are no longer transparent. I am not using Wayland, I use the Xorg Intel kernel server, this because I have Intel graphics and use virtualized GPU on a virtual machine, this does not work with Wayland and for that matter neither does Synaptic. Really I wish Wayland and Systemd and a bunch of the other modern atrocities that have transformed Ubuntu from a good reliable OS into an unstable difficult OS would just die. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: mate-desktop 1.26.0-1 Uname: Linux 5.17.12 x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: MATE Date: Fri Jun 3 14:51:00 2022 SourcePackage: mate-desktop UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: mate-desktop (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy third-party-packages -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1977621 Title: Transparency come and go To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mate-desktop/+bug/1977621/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1975557] Re: blank screen does not turn off display backlight
** Reply to message from Daniel van Vugt <1975...@bugs.launchpad.net> on Wed, 25 May 2022 06:15:35 - I get an error running apport-collect. I am beginning to think that the last update to this system went wrong. There are other problems comming up which I did not have before. I have now tried the display with another 22.04 install and that works OK. So I think this problem report should be closed. bob1@Juptier:~$ apport-collect 1975557 ERROR: connecting to Launchpad failed: Unable to find the server at launchpad.net You can reset the credentials by removing the file "/home/bob1/.cache/apport/launchpad.credentials" bob1@Juptier:~$ > The difference between 21.10 and 22.04 might just be that we now default > to Wayland instead of Xorg. So the display subsystems are different. > > Please run this command to gather more information: > > apport-collect 1975557 > > And to save time in future please use the 'ubuntu-bug' command to report > new bugs. > > ** Tags added: jammy > > ** Package changed: xorg (Ubuntu) => gnome-shell (Ubuntu) > > ** Changed in: gnome-shell (Ubuntu) >Status: New => Incomplete > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1975557 > > Title: > blank screen does not turn off display backlight > > Status in gnome-shell package in Ubuntu: > Incomplete > > Bug description: > I updated a system from 21.10 to 22.04 and noticed that when the > screen is blanked by no keyboard or mouse activity that the backlight > in the VGA monitor is still on. The "settings->Displays" has "Unknown > Display" which I assume means the system does not know what commands > to send to the monitor to shut it off. I booted a live DVD of 21.10 > and the settings has the VGA display as 'AOC 22" ' which is correct > and the screen blanking works correctly. So it seems that the > definition for the AOC displays have been removed from 22.04. > > This behavior is different on Ubuntu 21.10, the VGA display is blank and the > backlight is off. A minor nit is on 21.10 the "settings->Displays" shows the > VGA display manufacture name, on 22.04 the > VGA display manufacture name is "Unknown Display". > > I have discovered that the settings have the following options > > "settings->Power->Screen Blank" with a time value to be selected and the > following text on the next line "Turns the screen off after a period of > inactivity" > > "settings->Privacy->Screen->Blank Screen Display" with a time value to be > selected and the following text on the next line "Period of inactivity after > which the screen will go blank" > > The two options have different actions but seem to be connected because > changing the time on one changes the time on the other. > > My guess is that the update changed the action for Ubuntu 22.04. I > would like the 21.10 behavior, that is to turn off the VGA display not > just blank the display when selecting the "settings->Power->Screen > Blank" for 22.04. > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1975557/+subscriptions -- Robert Blair Tell me and I forget. Teach me and I remember. Involve me and I learn. -- Xun Kuang (Confucian philosopher) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1975557 Title: blank screen does not turn off display backlight To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1975557/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1967013] Re: Bionic update: upstream stable patchset 2022-03-29
As stated in the bug ticket linked above, this commit: https://kernel.ubuntu.com/git/ubuntu/ubuntu-bionic.git/commit/kernel/module.c?h=Ubuntu-4.15.0-177.186=3879f4364139acb2bd3932e6a15994f109c49d6b causes issues on hardware where the intel_lpss driver tries to load the intel idma driver, because this commit: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/drivers/mfd/intel-lpss.c?id=569fac74627cc332a2097a7a4bfdc654b8e7f273 has not been backported to the 4.15 kernel. I propose backporting this commit to the 4.15 kernel ASAP to fix the issue. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1967013 Title: Bionic update: upstream stable patchset 2022-03-29 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1967013/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1973167] Re: linux-image-4.15.0-177-generic freezes on the welcome screen
FIXED IT! It is indeed the intel_lpss driver, at least in my case. This commit: https://kernel.ubuntu.com/git/ubuntu/ubuntu-bionic.git/commit/kernel/module.c?h=Ubuntu-4.15.0-177.186=3879f4364139acb2bd3932e6a15994f109c49d6b will not work right when a module that is asynchronously loaded tries to synchronously load a module, which is not (or no longer?) allowed. It appears the intel_lpss driver did just that until this commit: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/drivers/mfd/intel- lpss.c?id=569fac74627cc332a2097a7a4bfdc654b8e7f273 But this commit has not been backported to the 4.15 kernel, so the intel_lpss driver delivered with the 4.15.0-177 kernel package does not have it. Applying this commit to the 4.15.0-177 source tree, rebuilding and replacing (only!) the intel_lpss.ko module makes the kernel load without delays for me. I confirmed the same with kernel 4.15.0-180. So now we only need to convince the Ubuntu maintainers to backport https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/drivers/mfd/intel- lpss.c?id=569fac74627cc332a2097a7a4bfdc654b8e7f273 to the 4.15 kernel... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1973167 Title: linux-image-4.15.0-177-generic freezes on the welcome screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1973167/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1967013] Re: Bionic update: upstream stable patchset 2022-03-29
This commit is suspected to cause issues for many users: https://kernel.ubuntu.com/git/ubuntu/ubuntu-bionic.git/commit/kernel/module.c?h=Ubuntu-4.15.0-177.186=3879f4364139acb2bd3932e6a15994f109c49d6b Please see this bug ticket: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1973167 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1967013 Title: Bionic update: upstream stable patchset 2022-03-29 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1967013/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1973167] Re: linux-image-4.15.0-177-generic freezes on the welcome screen
My "prime suspect" is this commit: https://kernel.ubuntu.com/git/ubuntu/ubuntu-bionic.git/commit/kernel/module.c?h=Ubuntu-4.15.0-177.186=3879f4364139acb2bd3932e6a15994f109c49d6b Also see Linus' comments when this patch was submitted to the mainline kernel: https://www.spinics.net/lists/kernel/msg4223720.html "that might be a big deal slowing things down at boot time. [...] Comments? Maybe this is a "just apply it, see if somebody screams" situation?" From what I understand, other measures taken in the kernel and modules make this issue no longer occur, so my hypothesis is that this may not have caused issues in the current kernel. So the mistake was that Canonical backported this commit to a very old kernel version that kernel.org no longer maintains... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1973167 Title: linux-image-4.15.0-177-generic freezes on the welcome screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1973167/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1973167] Re: linux-image-4.15.0-177-generic freezes on the welcome screen
I have found a change between 176 and 177 that looks suspicious:
diff -upr --color 176/linux-source-4.15.0/kernel/module.c
177/linux-source-4.15.0/kernel/module.c
--- 176/linux-source-4.15.0/kernel/module.c 2022-03-29 19:39:48.0
+0200
+++ 177/linux-source-4.15.0/kernel/module.c 2022-04-14 22:22:50.0
+0200
@@ -3520,22 +3514,13 @@ static noinline int do_init_module(struc
- /*
-* We need to finish all async code before the module init sequence
-* is done. This has potential to deadlock. For example, a newly
-* detected block device can trigger request_module() of the
-* default iosched from async probing task. Once userland helper
-* reaches here, async_synchronize_full() will wait on the async
-* task waiting on request_module() and deadlock.
-*
-* This deadlock is avoided by perfomring async_synchronize_full()
-* iff module init queued any async jobs. This isn't a full
-* solution as it will deadlock the same if module loading from
-* async jobs nests more than once; however, due to the various
-* constraints, this hack seems to be the best option for now.
-* Please refer to the following thread for details.
-*
-* http://thread.gmane.org/gmane.linux.kernel/1420814
-*/
- if (!mod->async_probe_requested && (current->flags & PF_USED_ASYNC))
+ /*
+* We need to finish all async code before the module init sequence
+* is done. This has potential to deadlock if synchronous module
+* loading is requested from async (which is not allowed!).
+*
+* See commit 0fdff3ec6d87 ("async, kmod: warn on synchronous
+* request_module() from async workers") for more details.
+*/
+ if (!mod->async_probe_requested)
async_synchronize_full();
Maybe this is the deadlock we're all running into...?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1973167
Title:
linux-image-4.15.0-177-generic freezes on the welcome screen
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1973167/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1974203] Re: NO IRQ HANDLER FOR VECTOR
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1974203 Title: NO IRQ HANDLER FOR VECTOR To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1974203/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1975557] [NEW] blank screen does not turn off display backlight
Public bug reported: I updated a system from 21.10 to 22.04 and noticed that when the screen is blanked by no keyboard or mouse activity that the backlight in the VGA monitor is still on. The "settings->Displays" has "Unknown Display" which I assume means the system does not know what commands to send to the monitor to shut it off. I booted a live DVD of 21.10 and the settings has the VGA display as 'AOC 22" ' which is correct and the screen blanking works correctly. So it seems that the definition for the AOC displays have been removed from 22.04. This behavior is different on Ubuntu 21.10, the VGA display is blank and the backlight is off. A minor nit is on 21.10 the "settings->Displays" shows the VGA display manufacture name, on 22.04 the VGA display manufacture name is "Unknown Display". I have discovered that the settings have the following options "settings->Power->Screen Blank" with a time value to be selected and the following text on the next line "Turns the screen off after a period of inactivity" "settings->Privacy->Screen->Blank Screen Display" with a time value to be selected and the following text on the next line "Period of inactivity after which the screen will go blank" The two options have different actions but seem to be connected because changing the time on one changes the time on the other. My guess is that the update changed the action for Ubuntu 22.04. I would like the 21.10 behavior, that is to turn off the VGA display not just blank the display when selecting the "settings->Power->Screen Blank" for 22.04. ** Affects: 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/1975557 Title: blank screen does not turn off display backlight To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1975557/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1973167] Re: linux-image-4.15.0-177-generic freezes on the welcome screen
Trying to isolate the issue, I: 1. Booted my portable Ubuntu 18.04.6 installation on a different machine (different CPU, chipset, but still Intel). On the other machine, kernel 4.15.0-177 booted without issues, so apparently it does not depend on the installation, but rather on the hardware or BIOS whether the freeze occurs or not. 2. Replaced the entire /lib/modules/4.15.0-177-generic/ with the contents from /lib/modules/4.15.0-176-generic/ and rebuilt initramfs. This did NOT cure the freezes (only caused a lot of module signature errors, confirming that the modules really were replaced). So whatever is causing the freezes is not in one of loadable modules, but rather within the kernel itself or the builtin modules. Still, the 176-to-177 diff over the builtin modules is HUGE... :-/ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1973167 Title: linux-image-4.15.0-177-generic freezes on the welcome screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1973167/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1974203] Re: NO IRQ HANDLER FOR VECTOR
Thanks for reply Daniel. When booting I can see this notification : "no irq handler ..." + "live patch cve-2013-1798 ... " in other words no update possible as no archive folder ... Doest it make any sense to you ? Le 20/05/2022 à 04:46, Daniel van Vugt a écrit : > Please explain in more detail what the problem is you are experiencing. > > ** Package changed: xorg (Ubuntu) => ubuntu > > ** Changed in: ubuntu > Status: New => Incomplete > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1974203 Title: NO IRQ HANDLER FOR VECTOR To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1974203/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1974102] Re: Sun4u emulation network does not work
Ok, I'll try to specify a lance interface, I think I specified hme, as the documentation said it had changed to that. -_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_- Eskimo North Linux Friendly Internet Access, Shell Accounts, and Hosting. Knowledgeable human assistance, not telephone trees or script readers. See our web site: http://www.eskimo.com/ (206) 812-0051 or (800) 246-6874. On Fri, 20 May 2022, Paride Legovini wrote: > Date: Fri, 20 May 2022 13:54:13 - > From: Paride Legovini <1974...@bugs.launchpad.net> > To: nan...@eskimo.com > Subject: [Bug 1974102] Re: Sun4u emulation network does not work > > Hello Robert and thanks for this bug report. I checked what NICs are > supported on sparc, and: > > $ qemu-system-sparc -net nic,model='?' > Supported NIC models: > lance > > so apparently it's only lance. Now, is there any trace of this NIC on > the guest system? Does it show up in `ip addr` or `ip link`? Does it > show up in lspci / dmesg? Is there any trace of a lance kernel module > (this may be CONFIG_LANCE in the kernel config)? > > My guess here is that the guest system is lacking drivers for the lance > NIC, so it will show up in lspci but not no `ip link`, however I'm a bit > in the dark. Let us know your findings and we'll see if there's anything > we can do from the Ubuntu side. Thanks! > > ** Changed in: qemu (Ubuntu) > Status: New => Incomplete > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1974102 > > Title: > Sun4u emulation network does not work > > Status in qemu package in Ubuntu: > Incomplete > > Bug description: > I've created a virtual machine using the following arguments: > > qemu-system-sparc -bios /opt/roms/ss5.bin -vga cg3 -hda > /var/lib/libvirt/images/ultra3.img -cdrom /opt/iso/redhat62.iso > > Where /opt/roms/ss5.bin are ROMS I obtained from a website for SS-5, > /var/lib/libvirt/images/ultra3.img is a qcow2 image file 4GB, and > /opt/iso/redhat62.iso is a redhat 6.2 image I copied using cp /dev/sr0 > /opt/iso/redhat62.iso. > > I was able to successfully install and boot the virtual machine with > Redhat 6.2, however the network interface does not talk. Can't even > ping the interface of the physical machine it is hosted on. > > virt-manager sparc is completely useless, no way to load from a CD > image and if I try to import the existing disk image I created this > way, the monitor blows up. > > ProblemType: Bug > DistroRelease: Ubuntu 22.04 > Package: qemu-system-sparc 1:6.2+dfsg-2ubuntu6 > Uname: Linux 5.17.7 x86_64 > ApportVersion: 2.20.11-0ubuntu82.1 > Architecture: amd64 > CasperMD5CheckResult: unknown > CurrentDesktop: MATE > Date: Wed May 18 16:38:57 2022 > InstallationDate: Installed on 2017-05-27 (1817 days ago) > InstallationMedia: Ubuntu-MATE 17.04 "Zesty Zapus" - Release amd64 (20170412) > Lsusb: > Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub > Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub > Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub > Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub > Lsusb-t: > /: Bus 04.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/2p, 1M > /: Bus 03.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/2p, 480M > /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/10p, 5000M > /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/16p, 480M > MachineType: System manufacturer System Product Name > ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.17.7 > root=UUID=a5625ed7-127f-48e2-8430-167d139254ec ro quiet splash vt.handoff=7 > RebootRequiredPkgs: Error: path contained symlinks. > SourcePackage: qemu > UpgradeStatus: Upgraded to jammy on 2022-05-16 (2 days ago) > dmi.bios.date: 04/26/2017 > dmi.bios.release: 5.12 > dmi.bios.vendor: American Megatrends Inc. > dmi.bios.version: 3402 > dmi.board.asset.tag: Default string > dmi.board.name: Z170 PRO GAMING > dmi.board.vendor: ASUSTeK COMPUTER INC. > dmi.board.version: Rev X.0x > dmi.chassis.asset.tag: Default string > dmi.chassis.type: 3 > dmi.chassis.vendor: Default string > dmi.chassis.version: Default string > dmi.modalias: > dmi:bvnAmericanMegatrendsInc.:bvr3402:bd04/26/2017:br5.12:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ170PROGAMING:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU: > dmi.product.family: To be filled by O.E.M. > dmi.product.name: System Product Name > dmi.product.sku: SKU > dmi.product.version: System Version > dmi.sys.vendor: System manuf
[Bug 1974203] [NEW] NO IRQ HANDLER FOR VECTOR
Public bug reported: CANNOT UPDATE ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-84.94-generic 5.4.133 Uname: Linux 5.4.0-84-generic x86_64 NonfreeKernelModules: lkp_Ubuntu_5_4_0_84_94_generic_85 .tmp.unity_support_test.0: ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 CasperMD5CheckResult: skip CompositorRunning: None Date: Thu May 19 16:30:38 2022 DistUpgraded: 2020-10-06 18:55:54,955 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: L’exécution du processus fils « ./xorg_fix_proprietary.py » a échoué (Aucun fichier ou dossier de ce type) (8)) DistroCodename: focal DistroVariant: ubuntu DpkgLog: GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Kabini [Radeon HD 8210] [1002:9834] (prog-if 00 [VGA controller]) Subsystem: Lenovo Kabini [Radeon HD 8210] [17aa:3802] InstallationDate: Installed on 2018-11-18 (1277 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: LENOVO 20240 ProcEnviron: PATH=(custom, no user) LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-84-generic root=UUID=1d6c2f9c-9ac1-47d3-8a0a-480bb5876f61 ro quiet splash SourcePackage: xorg UpgradeStatus: Upgraded to focal on 2020-10-06 (589 days ago) dmi.bios.date: 12/04/2013 dmi.bios.vendor: LENOVO dmi.bios.version: 82CN27WW(V3.00) dmi.board.asset.tag: No Asset Tag dmi.board.name: Lenovo G505 dmi.board.vendor: LENOVO dmi.board.version: 31900058Std dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo G505 dmi.modalias: dmi:bvnLENOVO:bvr82CN27WW(V3.00):bd12/04/2013:svnLENOVO:pn20240:pvrLenovoG505:rvnLENOVO:rnLenovoG505:rvr31900058Std:cvnLENOVO:ct10:cvrLenovoG505: dmi.product.family: IDEAPAD dmi.product.name: 20240 dmi.product.sku: LENOVO_MT_20240 dmi.product.version: Lenovo G505 dmi.sys.vendor: LENOVO modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2021-10-31T16:07:37.548006 version.compiz: compiz 1:0.9.14.1+20.04.20200211-0ubuntu1 version.libdrm2: libdrm2 2.4.105-3~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.3-0ubuntu0.2~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 21.0.3-0ubuntu0.2~20.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 xserver.bootTime: Sun Nov 18 18:23:05 2018 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.18.3-1ubuntu2.2 xserver.video_driver: radeon ** Affects: ubuntu Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1974203 Title: NO IRQ HANDLER FOR VECTOR To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1974203/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1974102] [NEW] Sun4u emulation network does not work
Public bug reported: I've created a virtual machine using the following arguments: qemu-system-sparc -bios /opt/roms/ss5.bin -vga cg3 -hda /var/lib/libvirt/images/ultra3.img -cdrom /opt/iso/redhat62.iso Where /opt/roms/ss5.bin are ROMS I obtained from a website for SS-5, /var/lib/libvirt/images/ultra3.img is a qcow2 image file 4GB, and /opt/iso/redhat62.iso is a redhat 6.2 image I copied using cp /dev/sr0 /opt/iso/redhat62.iso. I was able to successfully install and boot the virtual machine with Redhat 6.2, however the network interface does not talk. Can't even ping the interface of the physical machine it is hosted on. virt-manager sparc is completely useless, no way to load from a CD image and if I try to import the existing disk image I created this way, the monitor blows up. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: qemu-system-sparc 1:6.2+dfsg-2ubuntu6 Uname: Linux 5.17.7 x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: MATE Date: Wed May 18 16:38:57 2022 InstallationDate: Installed on 2017-05-27 (1817 days ago) InstallationMedia: Ubuntu-MATE 17.04 "Zesty Zapus" - Release amd64 (20170412) Lsusb: Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 04.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/2p, 1M /: Bus 03.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/2p, 480M /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/10p, 5000M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/16p, 480M MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.17.7 root=UUID=a5625ed7-127f-48e2-8430-167d139254ec ro quiet splash vt.handoff=7 RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: qemu UpgradeStatus: Upgraded to jammy on 2022-05-16 (2 days ago) dmi.bios.date: 04/26/2017 dmi.bios.release: 5.12 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3402 dmi.board.asset.tag: Default string dmi.board.name: Z170 PRO GAMING dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3402:bd04/26/2017:br5.12:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ170PROGAMING:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer ** Affects: qemu (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1974102 Title: Sun4u emulation network does not work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1974102/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1973101] Re: After upgrade to 22.04 NFS exports for vers 2 and 3 no longer work
It was only partly successful, it failed to merge udp = y into the new conf. Also Ubuntu's decision to compile their kernels without UDP support is dumb. It does not make a huge difference in size or speed of the kernel and it does eliminate legacy support as the original NFS version 2 and version 3 specifications had no support for TCP. As it is I self compile a non-trivial portion of my server infrastructure because Ubuntu just does not provide the facilities that I need. I switched to Ubuntu from Redhat in 2012, when Redhat got to be this way. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1973101 Title: After upgrade to 22.04 NFS exports for vers 2 and 3 no longer work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nfs-utils/+bug/1973101/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1973101] Re: After upgrade to 22.04 NFS exports for vers 2 and 3 no longer work
This is just plain WRONG. The issue is NOT the kernel, upstream or otherwise. I am using 5.17.7 compiled directly from kernel source off of kernel.org, and was using the SAME kernel under 20.04. The issue was your new configuration file, /etc/nfs.conf, that did not exist prior to 22.04, and thus I had no reason to look for it, having UDP disabled by default even for versions 2 and 3 of NFS which makes ZERO sense as version 2 and 3 of NFS did not support TCP. Once I was made aware of this conf file by you simply turning version 2 and UDP on resolved my issues. You can close this bug if you like but having udp = n by default in this conf file is dumb, the current upstream kernel supports it just fine. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1973101 Title: After upgrade to 22.04 NFS exports for vers 2 and 3 no longer work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nfs-utils/+bug/1973101/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1973645] [NEW] git-lfs migrte import painfully slow (3.0.2)
Public bug reported: Hello, git-lfs shipped with Ubuntu 22.04 (version 3.0.2) is very slow when doing "lfs migrate import". This is upstream bug/regression: https://github.com/git-lfs/git-lfs/issues/4750 Is there is any chance to backport/upgrade git-lfs package for Ubuntu 22.04? ** Affects: git-lfs (Ubuntu) Importance: Undecided Status: New ** Summary changed: - git-lfs migrte import painfuly slow (3.0.2) + git-lfs migrte import painfully slow (3.0.2) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1973645 Title: git-lfs migrte import painfully slow (3.0.2) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/git-lfs/+bug/1973645/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1962541] Re: PEAP wifi can't connect (ubuntu live/installer is also not working
Promotion from -proposed sure would be nice. I see verification has been done but a update excuses shows an netplan.io regression[1]. I'm not sure if the test is flaky but I see that seb retried it a few times[2] last week and it failed consistently, so maybe not. I'm just curious if there's any status on the test failure. (Also, I started writing this thinking it had been a month but it's been less than a week and I can't tell time. I know it wouldn't be promoted with less than a week in -proposed anyway.) [1] https://people.canonical.com/~ubuntu-archive/proposed-migration/jammy/update_excuses.html#wpa [2] https://autopkgtest.ubuntu.com/packages/netplan.io/jammy/arm64 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1962541 Title: PEAP wifi can't connect (ubuntu live/installer is also not working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1962541/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1962541] Re: PEAP wifi can't connect (ubuntu live/installer is also not working
Thank you Seb, I had the issue reported in this bug in a WeWork today (first time connecting since updating to Jammy) and the package in -proposed resolved the issue for me as well. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1962541 Title: PEAP wifi can't connect (ubuntu live/installer is also not working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1962541/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
