[Bug 2060326] Re: unnattended upgrades stuck burning 100% cpu
Same here, `unattended-upgrade` hogging CPU for 10hours straight already. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2060326 Title: unnattended upgrades stuck burning 100% cpu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/2060326/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1977545] [NEW] xrandr: Failed to get size of gamma for output default
Public bug reported: spectrum@04397701017:/opt/swSpectrum/bin$ xrandr xrandr: Failed to get size of gamma for output default Screen 0: minimum 1920 x 1080, current 1920 x 1080, maximum 1920 x 1080 default connected 1920x1080+0+0 0mm x 0mm 1920x1080 77.0* Display setup GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.gnome.SettingsDaemon was not provided by any .service files ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8.1 ProcVersionSignature: Ubuntu 4.4.0-148.174~14.04.1-generic 4.4.177 Uname: Linux 4.4.0-148-generic x86_64 .tmp.unity.support.test.1: ApportVersion: 2.14.1-0ubuntu3.29 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Fri Jun 3 17:50:08 2022 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Device [8086:9bc8] (rev 03) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:09b4] InstallationDate: Installed on 2022-05-27 (7 days ago) InstallationMedia: VMI 14.04 - Release amd64 MachineType: Dell Inc. Vostro 3681 PlymouthDebug: Error: [Errno 13] Permission denied: '/var/log/plymouth-debug.log' ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-148-generic.efi.signed root=UUID=27e11871-0570-4fe3-91a8-53cd0df8d538 ro splash quiet i915.alpha_support=1 Renderer: Software SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/13/2022 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.8.2 dmi.board.name: 0X9X1W dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.8.2:bd01/13/2022:svnDellInc.:pnVostro3681:pvr:rvnDellInc.:rn0X9X1W:rvrA00:cvnDellInc.:ct3:cvr: dmi.product.name: Vostro 3681 dmi.sys.vendor: Dell Inc. drirc: version.compiz: compiz 1:0.9.11.3+14.04.20160425-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.67-1ubuntu0.14.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.6 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.6 version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.11 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1.7 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Fri Jun 3 17:29:43 2022 xserver.configfile: default xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.15.1-0ubuntu2.11 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug third-party-packages trusty ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1977545 Title: xrandr: Failed to get size of gamma for output default To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1977545/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1973297] Re: HP Probook 450 G8 model T87 support in kernel
lspci -nnk 00:00.0 Host bridge [0600]: Intel Corporation 11th Gen Core Processor Host Bridge/DRAM Registers [8086:9a14] (rev 01) Subsystem: Hewlett-Packard Company Device [103c:8a75] Kernel modules: igen6_edac 00:02.0 VGA compatible controller [0300]: Intel Corporation TigerLake-LP GT2 [Iris Xe Graphics] [8086:9a49] (rev 01) DeviceName: Onboard IGD Subsystem: Hewlett-Packard Company Device [103c:8a75] Kernel driver in use: i915 Kernel modules: i915 00:04.0 Signal processing controller [1180]: Intel Corporation TigerLake-LP Dynamic Tuning Processor Participant [8086:9a03] (rev 01) Subsystem: Hewlett-Packard Company Device [103c:8a75] Kernel driver in use: proc_thermal Kernel modules: processor_thermal_device_pci_legacy 00:0a.0 Signal processing controller [1180]: Intel Corporation Tigerlake Telemetry Aggregator Driver [8086:9a0d] (rev 01) Subsystem: Hewlett-Packard Company Device [103c:8a75] Kernel driver in use: intel_vsec 00:0d.0 USB controller [0c03]: Intel Corporation Tiger Lake-LP Thunderbolt 4 USB Controller [8086:9a13] (rev 01) Subsystem: Hewlett-Packard Company Device [103c:8a75] Kernel driver in use: xhci_hcd Kernel modules: xhci_pci 00:0e.0 RAID bus controller [0104]: Intel Corporation Volume Management Device NVMe RAID Controller [8086:9a0b] Subsystem: Hewlett-Packard Company Device [103c:8a75] Kernel driver in use: vmd Kernel modules: vmd 00:14.0 USB controller [0c03]: Intel Corporation Tiger Lake-LP USB 3.2 Gen 2x1 xHCI Host Controller [8086:a0ed] (rev 20) Subsystem: Hewlett-Packard Company Device [103c:8a75] Kernel driver in use: xhci_hcd Kernel modules: xhci_pci 00:14.2 RAM memory [0500]: Intel Corporation Tiger Lake-LP Shared SRAM [8086:a0ef] (rev 20) Subsystem: Hewlett-Packard Company Device [103c:8a75] 00:14.3 Network controller [0280]: Intel Corporation Wi-Fi 6 AX201 [8086:a0f0] (rev 20) Subsystem: Intel Corporation Device [8086:0074] Kernel driver in use: iwlwifi Kernel modules: iwlwifi 00:15.0 Serial bus controller [0c80]: Intel Corporation Tiger Lake-LP Serial IO I2C Controller #0 [8086:a0e8] (rev 20) Subsystem: Hewlett-Packard Company Device [103c:8a75] Kernel driver in use: intel-lpss Kernel modules: intel_lpss_pci 00:16.0 Communication controller [0780]: Intel Corporation Tiger Lake-LP Management Engine Interface [8086:a0e0] (rev 20) Subsystem: Hewlett-Packard Company Device [103c:8a75] Kernel driver in use: mei_me Kernel modules: mei_me 00:1c.0 PCI bridge [0604]: Intel Corporation Tigerlake PCH-LP PCI Express Root Port #6 [8086:a0bd] (rev 20) Subsystem: Hewlett-Packard Company Device [103c:8a75] Kernel driver in use: pcieport 00:1c.7 PCI bridge [0604]: Intel Corporation Tiger Lake-LP PCI Express Root Port #8 [8086:a0bf] (rev 20) Subsystem: Hewlett-Packard Company Device [103c:8a75] Kernel driver in use: pcieport 00:1d.0 PCI bridge [0604]: Intel Corporation Tiger Lake-LP PCI Express Root Port #9 [8086:a0b0] (rev 20) Subsystem: Hewlett-Packard Company Device [103c:8a75] Kernel driver in use: pcieport 00:1f.0 ISA bridge [0601]: Intel Corporation Tiger Lake-LP LPC Controller [8086:a082] (rev 20) Subsystem: Hewlett-Packard Company Device [103c:8a75] 00:1f.3 Multimedia audio controller [0401]: Intel Corporation Tiger Lake-LP Smart Sound Technology Audio Controller [8086:a0c8] (rev 20) Subsystem: Hewlett-Packard Company Device [103c:8a75] Kernel driver in use: sof-audio-pci-intel-tgl Kernel modules: snd_hda_intel, snd_sof_pci_intel_tgl 00:1f.4 SMBus [0c05]: Intel Corporation Tiger Lake-LP SMBus Controller [8086:a0a3] (rev 20) Subsystem: Hewlett-Packard Company Device [103c:8a75] Kernel driver in use: i801_smbus Kernel modules: i2c_i801 00:1f.5 Serial bus controller [0c80]: Intel Corporation Tiger Lake-LP SPI Controller [8086:a0a4] (rev 20) Subsystem: Hewlett-Packard Company Device [103c:8a75] Kernel driver in use: intel-spi Kernel modules: intel_spi_pci 01:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTS522A PCI Express Card Reader [10ec:522a] (rev 01) Subsystem: Hewlett-Packard Company Device [103c:8a75] Kernel driver in use: rtsx_pci Kernel modules: rtsx_pci 02:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller [10ec:8168] (rev 15) Subsystem: Hewlett-Packard Company Device [103c:8a75] Kernel driver in use: r8168 Kernel modules: r8169, r8168 03:00.0 Non-Volatile memory controller [0108]: Intel Corporation Device [8086:f1aa] (rev 03) Subsystem: Intel Corporation Device [8086:390f] Kernel driver in use: nvme -- You received this bug notification
[Bug 1973297] Re: HP Probook 450 G8 model T87 support in kernel
HP released this year new submodels for some G8 models of laptops and changed subsystem PCI ID for these new submodels. For example, my own laptop has bios ID T87 and lspci shows 00:1f.3 Multimedia audio controller [0401]: Intel Corporation Tiger Lake-LP Smart Sound Technology Audio Controller [8086:a0c8] (rev 20) Subsystem: Hewlett-Packard Company Device [103c:8a75] !!![103c:8a75] but not [103c:87e7]!!! I prepared little fix related to this information regarding new model of Probook 450 G8 and successfully tested it on 5.17.5 kernel. -cut-here--- diff --color -uNr linux-5.17.1/sound/pci/hda/patch_realtek.c linux-5.17.1.patched/sound/pci/hda/patch_realtek.c --- linux-5.17.1/sound/pci/hda/patch_realtek.c 2022-04-30 17:05:50.580721519 +0300 +++ linux-5.17.1.patched/sound/pci/hda/patch_realtek.c 2022-05-05 00:32:58.495948987 +0300 @@ -8953,6 +8953,7 @@ SND_PCI_QUIRK(0x103c, 0x87c8, "HP", ALC287_FIXUP_HP_GPIO_LED), SND_PCI_QUIRK(0x103c, 0x87e5, "HP ProBook 440 G8 Notebook PC", ALC236_FIXUP_HP_GPIO_LED), SND_PCI_QUIRK(0x103c, 0x87e7, "HP ProBook 450 G8 Notebook PC", ALC236_FIXUP_HP_GPIO_LED), + SND_PCI_QUIRK(0x103c, 0x8a75, "HP ProBook 450 G8 Notebook PC T87", ALC236_FIXUP_HP_GPIO_LED), SND_PCI_QUIRK(0x103c, 0x87f1, "HP ProBook 630 G8 Notebook PC", ALC236_FIXUP_HP_GPIO_LED), SND_PCI_QUIRK(0x103c, 0x87f2, "HP ProBook 640 G8 Notebook PC", ALC236_FIXUP_HP_GPIO_LED), SND_PCI_QUIRK(0x103c, 0x87f4, "HP", ALC287_FIXUP_HP_GPIO_LED), -cut-here--- P.S. looks like it is good to add next strings to patch_realtek.c also, but I can't test it: SND_PCI_QUIRK(0x103c, 0x8a73, "HP ProBook 430 G8 Notebook PC T87", ALC236_FIXUP_HP_GPIO_LED), SND_PCI_QUIRK(0x103c, 0x8a74, "HP ProBook 440 G8 Notebook PC T87", ALC236_FIXUP_HP_GPIO_LED), SND_PCI_QUIRK(0x103c, 0x8a76, "HP ProBook 440 G8 Notebook PC T88", ALC236_FIXUP_HP_GPIO_LED), SND_PCI_QUIRK(0x103c, 0x8a77, "HP ProBook 450 G8 Notebook PC T88", ALC236_FIXUP_HP_GPIO_LED), SND_PCI_QUIRK(0x103c, 0x8aB3, "HP EliteBook 840 G8 Notebook PC T39", ALC285_FIXUP_HP_GPIO_LED),HP released this year new submodels for some G8 models of laptops and changed subsystem PCI ID for these new submodels. For example, my own laptop has bios ID T87 and lspci shows 00:1f.3 Multimedia audio controller [0401]: Intel Corporation Tiger Lake-LP Smart Sound Technology Audio Controller [8086:a0c8] (rev 20) Subsystem: Hewlett-Packard Company Device [103c:8a75] !!![103c:8a75] but not [103c:87e7]!!! I prepared little fix related to this information regarding new model of Probook 450 G8 and successfully tested it on 5.17.5 kernel. -cut-here--- diff --color -uNr linux-5.17.1/sound/pci/hda/patch_realtek.c linux-5.17.1.patched/sound/pci/hda/patch_realtek.c --- linux-5.17.1/sound/pci/hda/patch_realtek.c 2022-04-30 17:05:50.580721519 +0300 +++ linux-5.17.1.patched/sound/pci/hda/patch_realtek.c 2022-05-05 00:32:58.495948987 +0300 @@ -8953,6 +8953,7 @@ SND_PCI_QUIRK(0x103c, 0x87c8, "HP", ALC287_FIXUP_HP_GPIO_LED), SND_PCI_QUIRK(0x103c, 0x87e5, "HP ProBook 440 G8 Notebook PC", ALC236_FIXUP_HP_GPIO_LED), SND_PCI_QUIRK(0x103c, 0x87e7, "HP ProBook 450 G8 Notebook PC", ALC236_FIXUP_HP_GPIO_LED), + SND_PCI_QUIRK(0x103c, 0x8a75, "HP ProBook 450 G8 Notebook PC T87", ALC236_FIXUP_HP_GPIO_LED), SND_PCI_QUIRK(0x103c, 0x87f1, "HP ProBook 630 G8 Notebook PC", ALC236_FIXUP_HP_GPIO_LED), SND_PCI_QUIRK(0x103c, 0x87f2, "HP ProBook 640 G8 Notebook PC", ALC236_FIXUP_HP_GPIO_LED), SND_PCI_QUIRK(0x103c, 0x87f4, "HP", ALC287_FIXUP_HP_GPIO_LED), -cut-here--- P.S. looks like it is good to add next strings to patch_realtek.c also, but I can't test it: SND_PCI_QUIRK(0x103c, 0x8a73, "HP ProBook 430 G8 Notebook PC T87", ALC236_FIXUP_HP_GPIO_LED), SND_PCI_QUIRK(0x103c, 0x8a74, "HP ProBook 440 G8 Notebook PC T87", ALC236_FIXUP_HP_GPIO_LED), SND_PCI_QUIRK(0x103c, 0x8a76, "HP ProBook 440 G8 Notebook PC T88", ALC236_FIXUP_HP_GPIO_LED), SND_PCI_QUIRK(0x103c, 0x8a77, "HP ProBook 450 G8 Notebook PC T88", ALC236_FIXUP_HP_GPIO_LED), SND_PCI_QUIRK(0x103c, 0x8aB3, "HP EliteBook 840 G8 Notebook PC T39", ALC285_FIXUP_HP_GPIO_LED), -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1973297 Title: HP Probook 450 G8 model T87 support in kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1973297/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1973297] [NEW] HP Probook 450 G8 model T87 support in kernel
Public bug reported: [Impact] The mic mute/audio mute LEDS are not work on HP Probook 450 G8 model T87 [Fix] It needs the specific quirk for the hardware layout. Thus, add the quirks to make it works. [Test] After applying the quirk, the audio/mic mute LEDs are working good. [Where problems could occur] Hewlett-Packard released this year new submodels for some G8 models of laptops and changed subsystem PCI ID for these new submodels. HP published special information about this in the next document: https://support.hp.com/us-en/document/ish_5789324-5789376-16 For example, even HP Probook 450 G8 model listed in sound/pci/hda/patch_realtek.c, in the laptop with recent T87 submodel audio/mic mute LEDs not working because of changed subsystem PCI ID. ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete ** Tags: laptop leds mute sound -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1973297 Title: HP Probook 450 G8 model T87 support in kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1973297/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1971987] Re: On release upgrade, Snaps don't change channel
Here is my /var/log/dist-upgrade/main.log. After upgrade from 21.10 to 22.04, gtk-common-themes snap was on latest/stable/ubuntu-19.04 channel. ** Attachment added: "main.log" https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1971987/+attachment/5589325/+files/main.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1971987 Title: On release upgrade, Snaps don't change channel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1971987/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1965493] Re: Bluez is crashing
Hello, It seems, I catch the same issue. Pastebin: https://termbin.com/wn0u $ lsb_release -rd Description:Linux Mint 20.3 Release:20.3 ** Attachment added: "crash.tar.gz" https://bugs.launchpad.net/ubuntu/+source/bluez-tools/+bug/1965493/+attachment/5577951/+files/crash.tar.gz -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1965493 Title: Bluez is crashing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez-tools/+bug/1965493/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1964660] [NEW] Suspend is not working properly after kernel trace in acpi
Public bug reported: This is probably duplicate of https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1896482 which is marked is fixed, but apparently is not. Sometimes when suspending laptop I am getting kernel trace (below). After that lid close button is not working anymore and S0ix is not working properly, laptop suspends, but it gets hot in a bag and battery usage is too high during sleep. [249667.446194] PM: suspend entry (s2idle) [249667.456868] Filesystems sync: 0.010 seconds [249667.579423] Freezing user space processes ... (elapsed 0.004 seconds) done. [249667.583763] OOM killer disabled. [249667.583765] Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done. [249667.585261] printk: Suspending console(s) (use no_console_suspend to debug) [249668.521948] ACPI: EC: interrupt blocked [255061.034393] [ cut here ] [255061.034396] WARNING: CPU: 0 PID: 106955 at kernel/workqueue.c:1440 __queue_work+0x31b/0x480 [255061.034409] Modules linked in: cdc_ether usbnet r8152 mii unix_diag snd_usb_audio snd_usbmidi_lib snd_rawmidi snd_seq_device binfmt_misc veth zfs(PO) zunicode(PO) zzstd(O) zlua(O) zavl(PO) icp(PO) zcommon(PO) znvpair(PO) spl(O) vhost_vsock vmw_vsock_virtio_transport_common vhost vhost_iotlb vsock ccm rfcomm cmac algif_hash algif_skcipher af_alg overlay bnep snd_ctl_led snd_soc_skl_hda_dsp snd_soc_intel_hda_dsp_common snd_soc_hdac_hdmi nls_iso8859_1 snd_hda_codec_hdmi snd_hda_codec_realtek intel_tcc_cooling snd_hda_codec_generic x86_pkg_temp_thermal snd_soc_dmic intel_powerclamp snd_sof_pci_intel_tgl snd_sof_intel_hda_common soundwire_intel soundwire_generic_allocation soundwire_cadence snd_sof_intel_hda mei_hdcp snd_sof_pci intel_rapl_msr snd_sof_xtensa_dsp kvm_intel snd_sof snd_soc_hdac_hda kvm snd_hda_ext_core snd_soc_acpi_intel_match snd_soc_acpi soundwire_bus joydev ledtrig_audio snd_soc_core snd_compress intel_cstate serio_raw efi_pstore ac97_bus snd_pcm_dmaengine btusb btrtl [255061.034482] iwlmvm uvcvideo snd_hda_intel btbcm videobuf2_vmalloc hid_sensor_gyro_3d hid_sensor_magn_3d hid_sensor_custom_intel_hinge hid_sensor_incl_3d btintel hid_sensor_als hid_sensor_rotation hid_sensor_accel_3d videobuf2_memops snd_intel_dspcfg videobuf2_v4l2 snd_intel_sdw_acpi hid_sensor_trigger mac80211 bluetooth industrialio_triggered_buffer videobuf2_common snd_hda_codec snd_hda_core videodev snd_hwdep wmi_bmof ecdh_generic processor_thermal_device_pci_legacy mc ecc kfifo_buf input_leds libarc4 hid_sensor_iio_common industrialio snd_pcm processor_thermal_device snd_timer processor_thermal_rfim iwlwifi snd processor_thermal_mbox soundcore processor_thermal_rapl mei_me cros_ec_ishtp ucsi_acpi mei pmt_telemetry hid_multitouch intel_rapl_common typec_ucsi cros_ec pmt_class igen6_edac intel_soc_dts_iosf cfg80211 typec int3403_thermal soc_button_array int340x_thermal_zone int3400_thermal intel_hid acpi_thermal_rel wireless_hotkey mac_hid sparse_keymap acpi_pad ip6t_REJECT [255061.034541] nf_reject_ipv6 ip6_tables nft_chain_nat xt_MASQUERADE xt_CHECKSUM xt_TCPMSS nft_counter ipt_REJECT nf_reject_ipv4 xt_state xt_conntrack xt_multiport xt_tcpudp nft_compat nf_tables nfnetlink sch_fq_codel coretemp nf_nat_ftp nf_conntrack_ftp nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 libcrc32c bridge stp llc parport_pc ppdev lp parport ip_tables x_tables autofs4 dm_crypt hid_sensor_custom hid_sensor_hub intel_ishtp_loader intel_ishtp_hid usbhid hid_generic i915 i2c_algo_bit ttm drm_kms_helper syscopyarea sysfillrect sysimgblt crct10dif_pclmul fb_sys_fops crc32_pclmul ghash_clmulni_intel nvme cec rc_core i2c_hid_acpi aesni_intel intel_ish_ipc intel_lpss_pci crypto_simd i2c_i801 i2c_hid intel_lpss i2c_smbus cryptd nvme_core idma64 drm intel_ishtp thunderbolt vmd xhci_pci xhci_pci_renesas intel_pmt wmi hid video pinctrl_tigerlake [255061.034606] CPU: 0 PID: 106955 Comm: kworker/0:0 Tainted: P U O 5.15.0-18-generic #18-Ubuntu [255061.034610] Hardware name: HP HP Elite Dragonfly G2 Notebook PC/8716, BIOS T90 Ver. 01.08.00 01/14/2022 [255061.034613] Workqueue: kec_query acpi_ec_event_processor [255061.034620] RIP: 0010:__queue_work+0x31b/0x480 [255061.034626] Code: ff 49 89 c7 e9 93 fe ff ff 65 8b 05 2f 77 94 6a a9 00 01 ff 00 75 13 65 48 8b 3c 25 c0 fb 01 00 f6 47 2c 20 0f 85 95 00 00 00 <0f> 0b 48 83 c4 18 5b 41 5c 41 5d 41 5e 41 5f 5d c3 48 8b 05 a5 07 [255061.034629] RSP: 0018:9605c7a078b8 EFLAGS: 00010087 [255061.034632] RAX: 89b3cfa39d00 RBX: 0002 RCX: 0004 [255061.034634] RDX: 89ac40204990 RSI: 89ac402c4800 RDI: 89adeccc8000 [255061.034635] RBP: 9605c7a078f8 R08: R09: 0001 [255061.034637] R10: 0020 R11: R12: 2000
[Bug 1896482] Re: acpi event detection crashes
Getting same trace on 5.15.0-18-generic. And besides non-working lid switch, s2idle is eating way more battery after this trace. [83424.717757] Call Trace: [83424.717759] [83424.717761] ? acpi_os_release_lock+0xe/0x10 [83424.717768] queue_work_on+0x39/0x60 [83424.717772] advance_transaction+0x1f6/0x590 [83424.717776] acpi_ec_transaction_unlocked+0xfd/0x320 [83424.717780] acpi_ec_transaction+0xb8/0x180 [83424.717784] acpi_ec_space_handler+0x1d8/0x290 [83424.717788] acpi_ev_address_space_dispatch+0x314/0x3d3 [83424.717791] ? acpi_ec_add+0x1c0/0x1c0 [83424.717795] acpi_ex_access_region+0x1c6/0x25f [83424.717798] ? acpi_ut_trace_u32+0x2b/0x73 [83424.717802] acpi_ex_field_datum_io+0x18a/0x42d [83424.717805] acpi_ex_extract_from_field+0x17b/0x36b [83424.717809] acpi_ex_read_data_from_field+0x326/0x378 [83424.717812] acpi_ex_resolve_node_to_value+0x3a7/0x4dd [83424.717816] acpi_ex_resolve_to_value+0x111/0x1aa [83424.717819] acpi_ds_evaluate_name_path+0xb1/0x169 [83424.717823] ? acpi_db_single_step+0x1e/0x258 [83424.717826] acpi_ds_exec_end_op+0x11f/0x79f [83424.717830] acpi_ps_parse_loop+0x587/0x660 [83424.717833] acpi_ps_parse_aml+0x1af/0x552 [83424.717837] acpi_ps_execute_method+0x208/0x2ca [83424.717840] acpi_ns_evaluate+0x34e/0x4f0 [83424.717842] acpi_evaluate_object+0x18e/0x3b4 [83424.717845] ? finish_task_switch.isra.0+0xa6/0x270 [83424.717850] acpi_ec_event_processor+0x6b/0xa0 [83424.717853] process_one_work+0x228/0x3d0 [83424.717858] worker_thread+0x53/0x410 [83424.717862] kthread+0x11b/0x140 [83424.717866] ? process_one_work+0x3d0/0x3d0 [83424.717870] ? set_kthread_struct+0x50/0x50 [83424.717874] ret_from_fork+0x1f/0x30 [83424.717880] [83424.717882] ---[ end trace b980c7f0525783f6 ]--- -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1896482 Title: acpi event detection crashes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1896482/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1961422] [NEW] nvidia-kernel-source-460 460.73.01-0ubuntu0.20.04.1: nvidia kernel module failed to build
Public bug reported: I don't know what's happened, but ubuntu said that smth went wrong, and I should report it ProblemType: Package DistroRelease: Ubuntu 20.04 Package: nvidia-kernel-source-460 460.73.01-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.13.0-28.31~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-28-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip DKMSKernelVersion: 5.13.0-30-generic Date: Fri Feb 18 16:24:44 2022 Dependencies: DuplicateSignature: dkms:nvidia-kernel-source-460:460.73.01-0ubuntu0.20.04.1:/var/lib/dkms/nvidia/460.73.01/build/nvidia-drm/nvidia-drm-crtc.c:311:23: error: initialization of ‘int (*)(struct drm_plane *, struct drm_atomic_state *)’ from incompatible pointer type ‘int (*)(struct drm_plane *, struct drm_plane_state *)’ [-Werror=incompatible-pointer-types] InstallationDate: Installed on 2021-03-07 (348 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) PackageVersion: 460.73.01-0ubuntu0.20.04.1 Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.5 SourcePackage: nvidia-graphics-drivers-460 Title: nvidia-kernel-source-460 460.73.01-0ubuntu0.20.04.1: nvidia kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: nvidia-graphics-drivers-460 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1961422 Title: nvidia-kernel-source-460 460.73.01-0ubuntu0.20.04.1: nvidia kernel module failed to build To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-460/+bug/1961422/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1816634] Re: GNOME Shell consistently ignores mouse clicks in a particular app window
The bug is reproduced on Eclipse IDE (screenshot https://disk.yandex.ru/i/z7kqQV47z8xeFQ). Left click always closes the popup window instead of set focus on it. Pressing the "F2" buttons leads to the same result. Ubuntu 20.04.3 LTS GNOME Shell 3.36.9 Eclipse 2021-12 (4.22.0) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1816634 Title: GNOME Shell consistently ignores mouse clicks in a particular app window To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1816634/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1960096] [NEW] package ca-certificates-java 20190909 failed to install/upgrade: installed ca-certificates-java package post-installation script subprocess returned error exit status 127
Public bug reported: The bug appeared during the *clean* installation of openjdk-18-jdk. The package was installed using `apt install openjdk-18-jdk --no-install- recommends`. It's important to mention that no previous java has been installed, so no `java` executable existed on post-install. The cause of the problem is: Processing triggers of ca-certificates (20210119ubuntu1) … Updating certificates in /etc/ssl/certs... 0 added, 0 removed; done. Running hooks in /etc/ca-certificates/update.d... /etc/ca-certificates/update.d/jks-keystore: 82: java: not found E: /etc/ca-certificates/update.d/jks-keystore exited with code 1. done. ProblemType: Package DistroRelease: Ubuntu 21.10 Package: ca-certificates-java 20190909 ProcVersionSignature: Ubuntu 5.13.0-28.31-generic 5.13.19 Uname: Linux 5.13.0-28-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: pass Date: Sat Feb 5 08:45:11 2022 ErrorMessage: installed ca-certificates-java package post-installation script subprocess returned error exit status 127 InstallationDate: Installed on 2022-02-01 (3 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) PackageArchitecture: all Python3Details: /usr/bin/python3.9, Python 3.9.7, python3-minimal, 3.9.4-1build1 PythonDetails: N/A RelatedPackageVersions: dpkg 1.20.9ubuntu2 apt 2.3.9 SourcePackage: ca-certificates-java Title: package ca-certificates-java 20190909 failed to install/upgrade: installed ca-certificates-java package post-installation script subprocess returned error exit status 127 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ca-certificates-java (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package impish -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1960096 Title: package ca-certificates-java 20190909 failed to install/upgrade: installed ca-certificates-java package post-installation script subprocess returned error exit status 127 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ca-certificates-java/+bug/1960096/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1956401] Re: amdgpu hangs for 90 seconds at a time in 5.13.0-23, but 5.13.0-22 works
5.13.0-25 fixed for me amdgpu graphics init issue on AMD Ryzen 5 3400G. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1956401 Title: amdgpu hangs for 90 seconds at a time in 5.13.0-23, but 5.13.0-22 works To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1956401/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1956401] Re: amdgpu hangs for 90 seconds at a time in 5.13.0-23, but 5.13.0-22 works
Enabled proposed, kernel updated to 5.13.0-24-generic. Works fine! Thanks a lot for the quick fix. System:Host: alrock Kernel: 5.13.0-24-generic x86_64 bits: 64 Desktop: GNOME 40.5 Distro: Ubuntu 21.10 (Impish Indri) CPU: Info: Quad Core model: AMD Ryzen 5 3400G with Radeon Vega Graphics bits: 64 type: MT MCP cache: L2: 2 MiB Speed: 1400 MHz min/max: 1400/3700 MHz Core speeds (MHz): 1: 1400 2: 1350 3: 1404 4: 1388 5: 1384 6: 1399 7: 1397 8: 1352 Graphics: Device-1: Advanced Micro Devices [AMD/ATI] Picasso driver: amdgpu v: kernel Display: wayland server: X.Org 1.21.1.2 driver: loaded: ati,radeon,vesa unloaded: fbdev,modesetting resolution: 1920x1200~60Hz OpenGL: renderer: AMD Radeon Vega 11 Graphics (RAVEN DRM 3.41.0 5.13.0-24-generic LLVM 12.0.1) v: 4.6 Mesa 21.2.2 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1956401 Title: amdgpu hangs for 90 seconds at a time in 5.13.0-23, but 5.13.0-22 works To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1956401/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1956532] Re: Linux Kernel 5.13.0-23 Slows everything
Another "slow" kernel on AMD CPU, see also bug 1956408 and bug 1956396 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1956532 Title: Linux Kernel 5.13.0-23 Slows everything To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1956532/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1956383] Re: Ubuntu "impish" 21.10 Linux kernel "5.13.0-23.23" no video after reboot
Observe the same, confirmed that it is an issue with amdgpu failing to init graphics, see bug 1956399 Not sure how dupes are supposed to be handled. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1956383 Title: Ubuntu "impish" 21.10 Linux kernel "5.13.0-23.23" no video after reboot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1956383/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1956408] Re: Ubuntu 21.10 very slow after kernel update to 5.13.0-23-generic
This one and bug 1956396 look like duplicates. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1956408 Title: Ubuntu 21.10 very slow after kernel update to 5.13.0-23-generic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1956408/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1956396] Re: kernel 5.13.0-23 extremely slow boot on AMD proc/graphics
There is a bunch of AMD graphics related bugs associated with the latest kernel update on 21.10. I wonder whether they could have common root cause. Personally, I observe the same behavior as described in comment #4 above, I've submitted bug 1956399. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1956396 Title: kernel 5.13.0-23 extremely slow boot on AMD proc/graphics To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1956396/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1956399] Re: Regression: kernel does not init graphics (?) on AMD Ryzen 5 3400G
Confirmed that graphics init fails: when system is restarted with broken kernel, it is accessible via ssh. Grepping for amdgpu in kern.log results in: Jan 5 18:50:53 alrock kernel: [3.910928] [drm] amdgpu kernel modesetting enabled. Jan 5 18:50:53 alrock kernel: [3.911042] amdgpu: Topology: Add APU node [0x0:0x0] Jan 5 18:50:53 alrock kernel: [3.91] fb0: switching to amdgpudrmfb from EFI VGA Jan 5 18:50:53 alrock kernel: [3.911516] amdgpu :09:00.0: vgaarb: deactivate vga console Jan 5 18:50:53 alrock kernel: [3.911701] amdgpu :09:00.0: amdgpu: Trusted Memory Zone (TMZ) feature enabled Jan 5 18:50:53 alrock kernel: [3.943546] amdgpu :09:00.0: amdgpu: Fetched VBIOS from ROM BAR Jan 5 18:50:53 alrock kernel: [3.943551] amdgpu: ATOM BIOS: 113-PICASSO-118 Jan 5 18:50:53 alrock kernel: [3.943983] amdgpu :09:00.0: amdgpu: VRAM: 2048M 0x00F4 - 0x00F47FFF (2048M used) Jan 5 18:50:53 alrock kernel: [3.943986] amdgpu :09:00.0: amdgpu: GART: 1024M 0x - 0x3FFF Jan 5 18:50:53 alrock kernel: [3.943989] amdgpu :09:00.0: amdgpu: AGP: 267419648M 0x00F8 - 0x Jan 5 18:50:53 alrock kernel: [3.944034] [drm] amdgpu: 2048M of VRAM memory ready Jan 5 18:50:53 alrock kernel: [3.944040] [drm] amdgpu: 3072M of GTT memory ready. Jan 5 18:50:53 alrock kernel: [3.951844] amdgpu: hwmgr_sw_init smu backed is smu10_smu Jan 5 18:50:53 alrock kernel: [3.953750] amdgpu :09:00.0: amdgpu: Will use PSP to load VCN firmware Jan 5 18:50:53 alrock kernel: [4.039547] amdgpu :09:00.0: amdgpu: RAS: optional ras ta ucode is not available Jan 5 18:50:53 alrock kernel: [4.044506] amdgpu :09:00.0: amdgpu: RAP: optional rap ta ucode is not available Jan 5 18:50:53 alrock kernel: [4.083438] snd_hda_intel :09:00.1: bound :09:00.0 (ops amdgpu_dm_audio_component_bind_ops [amdgpu]) Jan 5 18:50:53 alrock kernel: [4.196382] kfd kfd: amdgpu: Allocated 3969056 bytes on gart Jan 5 18:50:53 alrock kernel: [4.196450] kfd kfd: amdgpu: error getting iommu info. is the iommu enabled? Jan 5 18:50:53 alrock kernel: [4.196455] kfd kfd: amdgpu: Error initializing iommuv2 Jan 5 18:50:53 alrock kernel: [4.196616] kfd kfd: amdgpu: device 1002:15d8 NOT added due to errors Jan 5 18:50:53 alrock kernel: [4.196619] kfd kfd: amdgpu: Failed to resume IOMMU for device 1002:15d8 Jan 5 18:50:53 alrock kernel: [4.196622] amdgpu :09:00.0: amdgpu: amdgpu_device_ip_init failed Jan 5 18:50:53 alrock kernel: [4.196626] amdgpu :09:00.0: amdgpu: Fatal error during GPU init Jan 5 18:50:53 alrock kernel: [4.196629] amdgpu :09:00.0: amdgpu: amdgpu: finishing device. Jan 5 18:50:53 alrock kernel: [4.242549] [drm] amdgpu: ttm finalized -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1956399 Title: Regression: kernel does not init graphics (?) on AMD Ryzen 5 3400G To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1956399/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1956399] [NEW] Regression: kernel does not init graphics (?) on AMD Ryzen 5 3400G
Public bug reported: After latest upgrade of linux-image to 5.13.0.23.34 system seem to boot, but it looks like graphics does not initialize correctly. After showing initial init logging, at the moment when X should init and graphics login should appear, monitor just goes to sleep and provides diagnostic message that there is no signal on selected input. apt upgrade log: Start-Date: 2022-01-04 23:21:11 Commandline: apt upgrade Requested-By: xx (1000) Install: linux-modules-extra-5.13.0-23-generic:amd64 (5.13.0-23.23, automatic), linux-image-5.13.0-23-generic:amd64 (5.13.0-23.23, automatic), linux-headers-5.13.0-23-generic:amd64 (5.13.0-23.23, automatic), linux-modules-5.13.0-23-generic:amd64 (5.13.0-23.23, automatic), linux-headers-5.13.0-23:amd64 (5.13.0-23.23, automatic) Upgrade: linux-headers-generic:amd64 (5.13.0.22.33, 5.13.0.23.34), google-chrome-stable:amd64 (96.0.4664.110-1, 97.0.4692.71-1), linux-generic:amd64 (5.13.0.22.33, 5.13.0.23.34), linux-image-generic:amd64 (5.13.0.22.33, 5.13.0.23.34), linux-libc-dev:amd64 (5.13.0-22.22, 5.13.0-23.23) End-Date: 2022-01-04 23:22:39 Currently working around this issues by booting previous version of the kernel. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: linux-generic 5.13.0.23.34 ProcVersionSignature: Ubuntu 5.13.0-22.22-generic 5.13.19 Uname: Linux 5.13.0-22-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: alexei 2532 F pulseaudio /dev/snd/pcmC1D0p: alexei 2532 F...m pulseaudio /dev/snd/controlC0: alexei 2532 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Jan 5 01:02:53 2022 HibernationDevice: RESUME=UUID=45af239b-c597-45a1-bb72-3ba25b5ee546 InstallationDate: Installed on 2016-01-06 (2190 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) IwConfig: lono wireless extensions. enp8s0no wireless extensions. lxcbr0no wireless extensions. MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-22-generic root=UUID=d4f27b9e-0cff-49e1-8392-a41aa520bd85 ro RelatedPackageVersions: linux-restricted-modules-5.13.0-22-generic N/A linux-backports-modules-5.13.0-22-generic N/A linux-firmware 1.201.3 RfKill: SourcePackage: linux UpgradeStatus: Upgraded to impish on 2021-10-05 (91 days ago) dmi.bios.date: 05/10/2021 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P5.00 dmi.board.name: B450 Pro4 dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP5.00:bd05/10/2021:br5.17:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB450Pro4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:skuToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-bug impish 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/1956399 Title: Regression: kernel does not init graphics (?) on AMD Ryzen 5 3400G To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1956399/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1888598] Re: Pulseaudio breaks HDMI audio on sleep/wake
the same problem on 21.10 pulseaudio package 1:15.0+dfsg1-1ubuntu2 default output is reset in random order after resume from sleep. Sometimes it stays as it was before suspend, but more often it just changes to HDMI or dock output. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1888598 Title: Pulseaudio breaks HDMI audio on sleep/wake To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1888598/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1870597]
Was this patch sent to the maintainers? If so, was it applied? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1870597 Title: libinput says "your system is too slow" To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1870597/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1911435] Re: xrdp session is not using the same PATH as a console session
As soon as the Kubunta repository is updated, I will immediately check the new version. I am glad! Well done! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1911435 Title: xrdp session is not using the same PATH as a console session To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xrdp/+bug/1911435/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1906476] Re: PANIC at zfs_znode.c:335:zfs_znode_sa_init() // VERIFY(0 == sa_handle_get_from_db(zfsvfs->z_os, db, zp, SA_HDL_SHARED, >z_sa_hdl)) failed
I have the same problem on my two machines that have identical setup. ZFS on root and data (two pools), compression enabled, some subvolumes are encrypted. ubuntu 21.10 Kernel 5.13.0-20-generic $ zfs --version zfs-2.0.6-1ubuntu2 zfs-kmod-2.0.6-1ubuntu2 First panic happens after I log in with my OS user, this triggers decryption of zfs subvolumes via PAM and voila: VERIFY(0 == sa_handle_get_from_db(zfsvfs->z_os, db, zp, SA_HDL_SHARED, >z_sa_hdl)) failed PANIC at zfs_znode.c:339:zfs_znode_sa_init() Showing stack for process 8821 CPU: 6 PID: 8821 Comm: Cache2 I/O Tainted: P O 5.13.0-20-generic #20-Ubuntu Hardware name: ASUS System Product Name/PRO H410T, BIOS 1401 07/27/2020 Call Trace: show_stack+0x52/0x58 dump_stack+0x7d/0x9c spl_dumpstack+0x29/0x2b [spl] spl_panic+0xd4/0xfc [spl] ? queued_spin_unlock+0x9/0x10 [zfs] ? do_raw_spin_unlock+0x9/0x10 [zfs] ? __raw_spin_unlock+0x9/0x10 [zfs] ? dmu_buf_replace_user+0x65/0x80 [zfs] ? dmu_buf_set_user+0x13/0x20 [zfs] ? dmu_buf_set_user_ie+0x15/0x20 [zfs] zfs_znode_sa_init+0xd9/0xe0 [zfs] … The system itself is still usable but becomes unresponsive here and there, on irregular basis. And then it goes on and on with messages like this in dmesg: INFO: task Cache2 I/O:8821 blocked for more than 1208 seconds. Tainted: P O 5.13.0-20-generic #20-Ubuntu "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. task:Cache2 I/O state:D stack:0 pid: 8821 ppid: 4247 flags:0x Call Trace: __schedule+0x268/0x680 schedule+0x4f/0xc0 spl_panic+0xfa/0xfc [spl] ? queued_spin_unlock+0x9/0x10 [zfs] ? do_raw_spin_unlock+0x9/0x10 [zfs] ? __raw_spin_unlock+0x9/0x10 [zfs] ? dmu_buf_replace_user+0x65/0x80 [zfs] ? dmu_buf_set_user+0x13/0x20 [zfs] ? dmu_buf_set_user_ie+0x15/0x20 [zfs] zfs_znode_sa_init+0xd9/0xe0 [zfs] … Processes that are suffering from being locked forever in 'D' state (ps output second column) are usually firefox, gsd-housekeeping , sometimes gnome-shell and, as in case above, find. I believe gnome-shell causes nautilus to misbehave. What also sucks is that this seems to cause my laptop to abort entering sleep mode with resource busy error, recursively. So it would try to enter sleep, abort (there's a message in syslog) and try again, until the battery depletes completely. Adding `zfs.zfs_recover=1` to kernel boot parameter list maybe helps (thank you https://launchpad.net/~jawn-smith). At least it prevented the first zfs_node panic message from appearing in dmesg after login, but this needs longer and more detailed observation under different loads. Also, an open question remains whether having such kernel parameter for regular use is appropriate. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1906476 Title: PANIC at zfs_znode.c:335:zfs_znode_sa_init() // VERIFY(0 == sa_handle_get_from_db(zfsvfs->z_os, db, zp, SA_HDL_SHARED, >z_sa_hdl)) failed To manage notifications about this bug go to: https://bugs.launchpad.net/zfs/+bug/1906476/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1862899] Re: Cannon Point-LP CNVi: Error sending STATISTICS_CMD: time out after 2000ms.
Again the same problem, with fresher software: Xubuntu 20.04, Kernel version 5.4.0-74-generic. Laptop is different, but the same model: > product: 20QD00L1PB (LENOVO_MT_20QD_BU_Think_FM_ThinkPad X1 Carbon 7th) No updates were installed recently (checked in /var/log/apt/history.log). Logs are attached. ** Attachment added: "/var/log/syslog with two pieces of logs with crash" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1862899/+attachment/5505094/+files/syslog_2021-06-16 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1862899 Title: Cannon Point-LP CNVi: Error sending STATISTICS_CMD: time out after 2000ms. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1862899/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1863434] Re: 20.04 grub menu not visible
I seem to have the same bug under Linux Mint 19.1 on a late 2008 MacBook. After some upgrade a few months ago, I've got a [problem with shim- signed][1], where I was getting "Failed to set MokListRT" error and no GRUB menu. After purging shim-signed, the error messages were gone, but the GRUB menu did not come back. I tried the solution linked to from comment #23, and it worked, but (1) the menu does not look the same as before, (2) there seem to be somewhat unusual timeouts before the menu is shown and after a boot option is selected, but I may be wrong. The workaround suggested in comment #23 is to set GRUB_TERMINAL=console in /etc/default/grub. [1]: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1867092 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1863434 Title: 20.04 grub menu not visible To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1863434/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1922353] Re: Overview sometimes fails to appear or disappear in gnome-shell 3.38
I can also confirm that update with hirsute-proposed enabled solves the problem for me. Before this, the problem used to be readily reproduced by the procedure described in comment #51. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1922353 Title: Overview sometimes fails to appear or disappear in gnome-shell 3.38 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1922353/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1868553] Re: libefi* integration breaks grub-install on MD devices
Here's a Debian bug report from 2019 for the same issue: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=925591 ** Bug watch added: Debian Bug tracker #925591 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=925591 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1868553 Title: libefi* integration breaks grub-install on MD devices To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/curtin/+bug/1868553/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1720438] Re: brightness control broken nvidia
I've found this forum thread: https://forums.developer.nvidia.com/t/solus-nvidia-gtx-1070-brightness- control-not-working/54472 If I understand correctly, the OP resolved his issue by setting the kernel boot parameter nvidia.NVreg_EnableBacklightHandler=1 This did not solve the issue for me, however. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1720438 Title: brightness control broken nvidia To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-power/+bug/1720438/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1922499] [NEW] Ubuntu 21.04 installer crashed on encrypted partition install
Public bug reported: I tried to install on encrypted partition (/boot unencrypted, / encrypted). Same steps installing works on 20.04.x images install, but crashes on 21.04 beta Installing without encryption works ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: ubiquity 21.04.13 ProcVersionSignature: Ubuntu 5.11.0-13.14-generic 5.11.7 Uname: Linux 5.11.0-13-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu61 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.461 Date: Sun Apr 4 21:34:44 2021 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed maybe-ubiquity quiet splash --- LiveMediaBuild: Ubuntu 21.04 "Hirsute Hippo" - Beta amd64 (20210404) RebootRequiredPkgs: linux-image-5.11.0-13-generic linux-base SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ubiquity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug hirsute ubiquity-21.04.13 ubuntu ** Attachment added: "syslog" https://bugs.launchpad.net/bugs/1922499/+attachment/5484001/+files/syslog -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1922499 Title: Ubuntu 21.04 installer crashed on encrypted partition install To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1922499/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1751759] Re: Add option to turn off Ubuntu dock
The built-in extensions (Desktop Icons, Ubuntu AppIndicators, Ubuntu Dock) can be deactivated using the Extensions app. Is it enough to close 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/1751759 Title: Add option to turn off Ubuntu dock To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1751759/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1841039] Re: Multiple keys have same keycode on HP ProBook 450 G6
Seems like this issue caused by HP's fn key driver for windows I own 440 G6 and had this issue for a long time but mystically it dissapeared once after my laptop was discharged for a long time but after win10 installation (2nd ssd with it died, so i installed new one and reinstalled w10) it stopped work again ive tried to update bios, but reverted it back as newer bioses locks possibility of enabling intel speedstep and only power reset solves issue until you will boot windows again -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1841039 Title: Multiple keys have same keycode on HP ProBook 450 G6 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1841039/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1911435] Re: xrdp session is not using the same PATH as a console session
year 2012 9 years have passed, and we still can't get the XRDP out of the box https://askubuntu.com/questions/92333/ubuntu-has-a-different-path-when- accessed-over-xrdp-session?answertab=oldest#tab-top -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1911435 Title: xrdp session is not using the same PATH as a console session To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xrdp/+bug/1911435/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1911435] Re: xrdp session is not using the same PATH as a console session
Kubuntu 20.04 20.10 21.04 echo "$PATH" XRDP USER /sbin:/bin:/usr/bin:/usr/local/bin:/snap/bin echo "$PATH" locale USER /usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/snap/bin -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1911435 Title: xrdp session is not using the same PATH as a console session To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xrdp/+bug/1911435/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1911435] Re: xrdp session is not using the same PATH as a console session
why is the old version XRDP repo Why hasn't error /bin and /usr/binbeen fixed for a year now? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1911435 Title: xrdp session is not using the same PATH as a console session To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xrdp/+bug/1911435/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1911435] Re: xrdp session is not using the same PATH as a console session
hirsute hippo Kubuntu 21.04 Alfa and XRDP 0.9.12-1.1 PATH was not fixed not work -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1911435 Title: xrdp session is not using the same PATH as a console session To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xrdp/+bug/1911435/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1915857] [NEW] native extension doesn't work
Public bug reported: Package ruby-murmurhash3 could work in two ways: native and pure ruby. In Focal works in pure ruby only, which is slower than native extension. How to reproduce: $ docker run -it ubuntu:focal # apt-get update && apt-get install ruby-murmurhash3 # ruby -e 'require "murmurhash3"' Attention: used pure ruby version of MurmurHash3 I've made some further investigations. I've installed this library as a gem (apt-get install build-essential ruby-dev && gem install murmurhash3) and I've saw that message about pure ruby version didn't appear. I've searched, where is located file native.so. I've found it in 3 places: /var/lib/gems/2.7.0/gems/murmurhash3-0.1.6/lib/native.so /var/lib/gems/2.7.0/gems/murmurhash3-0.1.6/ext/murmurhash3/native.so /var/lib/gems/2.7.0/extensions/x86_64-linux/2.7.0/murmurhash3-0.1.6/native.so After restarting docker container, and installing ruby-murmurhash3 again, I copied file /usr/lib/x86_64-linux-gnu/rubygems-integration/2.7.0/extensions/x86_64-linux/2.7.0/murmurhash3-0.1.6/native.so to /usr/lib/x86_64-linux-gnu/rubygems-integration/2.7.0/gems/murmurhash3-0.1.6/ext/murmurhash3/ and the problem was solved. Please, fix the package this way. Current package version: ruby-murmurhash3 0.1.6-2build1 amd64 ** Affects: ruby-murmurhash3 (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/1915857 Title: native extension doesn't work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ruby-murmurhash3/+bug/1915857/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1890791]
I regularly see this on Fedora 33 with Dolphin 20.08.3 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1890791 Title: Dolphin isn't Noticing Newly Created Files To manage notifications about this bug go to: https://bugs.launchpad.net/dolphin/+bug/1890791/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1890791]
(In reply to equeim from comment #4) > I regularly see this on Fedora 33 with Dolphin 20.08.3 (not every time, but at least once a day) -- You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to dolphin in Ubuntu. https://bugs.launchpad.net/bugs/1890791 Title: Dolphin isn't Noticing Newly Created Files To manage notifications about this bug go to: https://bugs.launchpad.net/dolphin/+bug/1890791/+subscriptions -- kubuntu-bugs mailing list kubuntu-b...@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 1849346] Re: [snap] kerberos GSSAPI no longer works after deb->snap transition
Sorry, I changed the issue's type accidently. ** Information type changed from Public Security to Public -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1849346 Title: [snap] kerberos GSSAPI no longer works after deb->snap transition To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1849346/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1849346] Re: [snap] kerberos GSSAPI no longer works after deb->snap transition
This problem still persist and SPNEGO won't work even with new policies: https://cloud.google.com/docs/chrome-enterprise/policies/?policy=AuthServerAllowlist https://cloud.google.com/docs/chrome-enterprise/policies/?policy=AuthNegotiateDelegateAllowlist The policies are loaded successfully but kerboros negotiation won't work ** Information type changed from Public to Public Security -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1849346 Title: [snap] kerberos GSSAPI no longer works after deb->snap transition To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1849346/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1866732] Re: [snap] Unable to add policies
The bug is solved We need to create folder mkdir -p /etc/chromium-browser/policies/managed manually and then browsre check the policies successfully -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1866732 Title: [snap] Unable to add policies To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1866732/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1414753] Re: Chromium browser 39.0.2171.65 does not load policies
Hello! This bug still persist in Chromium 87.0.4280.66 (Official Build) snap (64-bit) Ubuntu 20.10 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1414753 Title: Chromium browser 39.0.2171.65 does not load policies To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1414753/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1465183] Re: ubuntu 15.04 dhcp: option routers and option rfc3442-classless-static-routes
In fact, RedHat, Windows, MacOS don't ignore an default routes with classless-static_route option. What about to add an some tunable to have same behavior in Ubuntu? It should be not a hard -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1465183 Title: ubuntu 15.04 dhcp: option routers and option rfc3442-classless-static- routes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1465183/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1453514] Re: Highlighted text in pdf files is not shown on prints
To add to my point 2: the same effect happens when using `pdftocairo` in command line, so maybe the current issue is not about Evince. It remains the problem with annotations created in Evince that just disappear on printing. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1453514 Title: Highlighted text in pdf files is not shown on prints To manage notifications about this bug go to: https://bugs.launchpad.net/evince/+bug/1453514/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1453514] Re: Highlighted text in pdf files is not shown on prints
In fact, there seem to be multiple issues with printing annotations (at least text highlighting). This is about Evince 3.36.7 and Okular 20.08.2. 1. If a highlighting annotation is created in Evince, it is visible when the file is opened with Evince, Okular, or Xournal++, but it disappears on printing to PDF file from any of these programs, and it disappears on exporting to PDF from Xournal++. (I believe it also disappears on actual printing.) 2. If a highlighting annotation is created in Okular, it is visible in Evince, Okular, and Xournal++, but when printing to PDF from Evince or Xournal++, the first highlighting is ok, but all the others hide the text that is supposed to be highlighted. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1453514 Title: Highlighted text in pdf files is not shown on prints To manage notifications about this bug go to: https://bugs.launchpad.net/evince/+bug/1453514/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1902483] [NEW] Sparse file not allowed (on btrfs), 20.04
Public bug reported:
Hello there.
I have just installed Ubuntu 20.04 on my PC with a single partition on
btrfs file system. There was no show any errors during installation.
When I rebooted, I got the legacy grub menu and when I select any option
of boot (either windows or ubuntu), I'm getting message:
error: sparse files not allowed. Press any key to continue.
I found some manaul and removed the following lines doing via that
manual:
recordfail=1
if [ -n ${have_grubenv} ]; then save_env recordfail; fi
So, when I removed these entries, the system booted just fine.
I have no idea why these two lines would cause a problem, but they appear to.
There already were same bugs, I've seen(one of them more than 9 years ago
started (#464743 e.g.)).
Is it so hard to fix this?
** Affects: grub2 (Ubuntu)
Importance: Undecided
Status: New
** Tags: btrfs grub sparse
** Tags removed: file
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1902483
Title:
Sparse file not allowed (on btrfs), 20.04
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1902483/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 464743] Re: error: sparse file not allowed with reiserfs
Still relevant on Ubuntu 20.04. Bug started 9 years ago =) No one cares. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/464743 Title: error: sparse file not allowed with reiserfs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/464743/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1892013] Re: libzip needs update and build agains proper libssl-dev not libcrypt
Hello, anybody home? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1892013 Title: libzip needs update and build agains proper libssl-dev not libcrypt To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libzip/+bug/1892013/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1892584] Re: wine game 'rune classic' hungs the OS on exit
I've tested ubuntu kernel 5.4.0-26-generic + debian packages (full os install). It works fine. I can conclude this not kernel issue but X-server or amd drivers. Debian packages which works: ii x11-xserver-utils7.7+8 amd64X server utilities ii xserver-common 2:1.20.4-1+deb10u1 all common files used by various X servers ii xserver-xephyr 2:1.20.4-1+deb10u1 amd64nested X server ii xserver-xorg 1:7.7+19 amd64X.Org X server ii xserver-xorg-core2:1.20.4-1+deb10u1 amd64Xorg X server - core server ii xserver-xorg-input-all 1:7.7+19 amd64X.Org X server -- input driver metapackage ii xserver-xorg-input-libinput 0.28.2-2 amd64X.Org X server -- libinput input driver ii xserver-xorg-input-wacom 0.34.99.1-1 amd64X.Org X server -- Wacom input driver ii xserver-xorg-legacy 2:1.20.4-1+deb10u1 amd64setuid root Xorg server wrapper ii xserver-xorg-video-all 1:7.7+19 amd64X.Org X server -- output driver metapackage ii xserver-xorg-video-amdgpu18.1.99+git20190207-1 amd64X.Org X server -- AMDGPU display driver ii xserver-xorg-video-ati 1:19.0.1-1 amd64X.Org X server -- AMD/ATI display driver wrapper ii xserver-xorg-video-fbdev 1:0.5.0-1 amd64X.Org X server -- fbdev display driver ii xserver-xorg-video-intel 2:2.99.917+git20180925-2 amd64X.Org X server -- Intel i8xx, i9xx display driver ii xserver-xorg-video-nouveau 1:1.0.16-1 amd64X.Org X server -- Nouveau display driver ii xserver-xorg-video-qxl 0.1.5-2+b1 amd64X.Org X server -- QXL display driver ii xserver-xorg-video-radeon1:19.0.1-1 amd64X.Org X server -- AMD/ATI Radeon display driver ii xserver-xorg-video-vesa 1:2.4.0-1 amd64X.Org X server -- VESA display driver ii xserver-xorg-video-vmware1:13.3.0-2 amd64X.Org X server -- VMware display driver -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1892584 Title: wine game 'rune classic' hungs the OS on exit To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-amdgpu/+bug/1892584/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1727321] Re: drag and drop through the side panel to activate the window is not working.
** Tags added: focal groovy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1727321 Title: drag and drop through the side panel to activate the window is not working. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1727321/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1893816] [NEW] package linux-headers-5.6.0-1023-oem 5.6.0-1023.23 failed to install/upgrade: installed linux-headers-5.6.0-1023-oem package post-installation script subprocess returned error exit
Public bug reported: automatically appeared when I tried sudo apt-get upgrade ProblemType: Package DistroRelease: Ubuntu 20.04 Package: linux-headers-5.6.0-1023-oem 5.6.0-1023.23 Uname: Linux 5.8.1-050801-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 CasperMD5CheckResult: skip Date: Tue Sep 1 10:44:24 2020 ErrorMessage: installed linux-headers-5.6.0-1023-oem package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2020-08-04 (27 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2ubuntu0.1 SourcePackage: linux-oem-5.6 Title: package linux-headers-5.6.0-1023-oem 5.6.0-1023.23 failed to install/upgrade: installed linux-headers-5.6.0-1023-oem package post-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-oem-5.6 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1893816 Title: package linux-headers-5.6.0-1023-oem 5.6.0-1023.23 failed to install/upgrade: installed linux-headers-5.6.0-1023-oem package post- installation script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-oem-5.6/+bug/1893816/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1892584] [NEW] wine game 'rune classic' hungs the OS on exit
Public bug reported: Hello! Rune Classic hungs OS on exit (music plays, but X or keyboard caps lock not responding), Debian 10 works fine. https://www.gog.com/game/rune_classic ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xserver-xorg-video-amdgpu 19.1.0-1 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Aug 22 19:03:42 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: virtualbox, 6.1.10: added wireguard, 1.0.20200611: added GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Picasso [1002:15d8] (rev c2) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Picasso [1043:1b11] MachineType: ASUSTeK COMPUTER INC. ZenBook UX431DA_UM431DA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-26-generic root=/dev/mapper/vg0-root ro SourcePackage: xserver-xorg-video-amdgpu UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/11/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX431DA.301 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX431DA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX431DA.301:bd09/11/2019:svnASUSTeKCOMPUTERINC.:pnZenBookUX431DA_UM431DA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX431DA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ZenBook dmi.product.name: ZenBook UX431DA_UM431DA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A 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 ** Affects: xserver-xorg-video-amdgpu (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/1892584 Title: wine game 'rune classic' hungs the OS on exit To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-amdgpu/+bug/1892584/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1846374] Re: Having a video playing/paused when switched to another user generates gigabytes of error logs
Just deleted 240G syslog file after system stalled. Syslog.1 is 20G full of folowing: Aug 19 08:24:41 alexey-ASUS io.elementary.wingpanel.desktop[1935]: [7f6cd43aa790] vdpau_chroma filter error: video mixer rendering failure: An invalid handle value was provided. Aug 19 08:24:41 alexey-ASUS io.elementary.wingpanel.desktop[1935]: [7f6cd43aa790] vdpau_chroma filter error: video mixer features failure: An invalid handle value was provided. Aug 19 08:24:41 alexey-ASUS io.elementary.wingpanel.desktop[1935]: [7f6cd43aa790] vdpau_chroma filter error: video mixer attributes failure: An invalid handle value was provided. Aug 19 08:24:41 alexey-ASUS io.elementary.wingpanel.desktop[1935]: [7f6cd43aa790] vdpau_chroma filter error: video mixer rendering failure: An invalid handle value was provided. Aug 19 08:24:41 alexey-ASUS io.elementary.wingpanel.desktop[1935]: [7f6cd43aa790] vdpau_chroma filter error: video mixer features failure: An invalid handle value was provided. Aug 19 08:24:41 alexey-ASUS io.elementary.wingpanel.desktop[1935]: [7f6cd43aa790] vdpau_chroma filter error: video mixer attributes failure: An invalid handle value was provided. Aug 19 08:24:41 alexey-ASUS io.elementary.wingpanel.desktop[1935]: [7f6cd43aa790] vdpau_chroma filter error: video mixer rendering failure: An invalid handle value was provided. Aug 19 08:24:41 alexey-ASUS io.elementary.wingpanel.desktop[1935]: [7f6cd43aa790] vdpau_chroma filter error: video mixer features failure: An invalid handle value was provided. Aug 19 08:24:41 alexey-ASUS io.elementary.wingpanel.desktop[1935]: [7f6cd43aa790] vdpau_chroma filter error: video mixer attributes failure: An invalid handle value was provided. Aug 19 08:24:41 alexey-ASUS io.elementary.wingpanel.desktop[1935]: [7f6cd43aa790] vdpau_chroma filter error: video mixer rendering failure: An invalid handle value was provided. Aug 19 08:24:41 alexey-ASUS io.elementary.wingpanel.desktop[1935]: [7f6cd43aa790] vdpau_chroma filter error: video mixer features failure: An invalid handle value was provided. Aug 19 08:24:41 alexey-ASUS io.elementary.wingpanel.desktop[1935]: [7f6cd43aa790] vdpau_chroma filter error: video mixer attributes failure: An invalid handle value was provided. Aug 19 08:24:41 alexey-ASUS io.elementary.wingpanel.desktop[1935]: [7f6cd43aa790] vdpau_chroma filter error: video mixer rendering failure: An invalid handle value was provided. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1846374 Title: Having a video playing/paused when switched to another user generates gigabytes of error logs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1846374/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1892013] [NEW] libzip needs update and build agains proper libssl-dev not libcrypt
Public bug reported: Currently libzip in ubuntu very old (1.2.1). Also libzip have to be builded with cmake with proper encryption library like openssl, because Ark creates broken AES256 encrypted zip files, cuz again libzip builded against libcrpyt(libxcrypt) seems doesnt support AES256 at all. ** Affects: libzip (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/1892013 Title: libzip needs update and build agains proper libssl-dev not libcrypt To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libzip/+bug/1892013/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1884759] Re: U2f yubikey stopped working in chromium snap
For now I can send udev event instead of replugging:
ls -l /sys/class/hidraw/ | grep :1050: | awk -F/ '{print $NF}' | xargs
-r -L1 -I T udevadm trigger -c add --name-match=T
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1884759
Title:
U2f yubikey stopped working in chromium snap
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1884759/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1884759] Re: U2f yubikey stopped working in chromium snap
Hm, now I updated chrome to 84.0.4147.105 (1260) and can reproduce it reliably by inserting yubikey and then starting chromium with new profile (chromium --user-data-dir=./111). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1884759 Title: U2f yubikey stopped working in chromium snap To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1884759/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1884759] Re: U2f yubikey stopped working in chromium snap
Sorry for long delay. No I can't reproduce it anymore in a way I described before, but it still happens to me. For now certain is that repluging yubikey fixes the problem, reboot doesn't. Upgrading the snap most probably triggering it, need to test it more times. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1884759 Title: U2f yubikey stopped working in chromium snap To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1884759/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1884759] Re: U2f yubikey stopped working in chromium snap
Funny thing. I have Yubikey 5C Nano and it is hard to get out of port. So I plugged spare Yubikey 4 to get dmesg lines and it worked with chromium. Then I replugged my yubikey 5c nano and it worked too. Then I rebooted without unplugging yubikey and it not working in chromium again but works in firefox. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1884759 Title: U2f yubikey stopped working in chromium snap To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1884759/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1884759] Re: U2f yubikey stopped working in chromium snap
name: chromium summary: Chromium web browser, open-source version of Chrome publisher: Canonical* contact: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bugs?field.tag=snap license: unset description: | An open-source browser project that aims to build a safer, faster, and more stable way for all Internet users to experience the web. commands: - chromium.chromedriver - chromium snap-id: XKEcBqPM06H1Z7zGOdG5fbICuf8NWK5R tracking: latest/stable refresh-date: 12 days ago, at 19:18 MSK installed:84.0.4147.89 (1229) 166MB - -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1884759 Title: U2f yubikey stopped working in chromium snap To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1884759/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1884759] Re: U2f yubikey stopped working in chromium snap
Still not working. And right link to test is https://demo.yubico.com /webauthn-technical/registration -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1884759 Title: U2f yubikey stopped working in chromium snap To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1884759/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1889162] [NEW] golang-1.13-race-detector-runtime conflicts with golang-1.13-src
Public bug reported: Two packages conflicts with file: /usr/lib/go-1.13/src/runtime/race/race_linux_amd64.syso and /usr/share/go-1.13/src/runtime/race/race_linux_amd64.syso Booth packages pointing to one file with different file path. As result 'debsums -c' always show changed system files. axet@axet-laptop:~$ ls -i /usr/lib/go-1.13/src/runtime/race/race_linux_amd64.syso 3070001 /usr/lib/go-1.13/src/runtime/race/race_linux_amd64.syso axet@axet-laptop:~$ ls -i /usr/share/go-1.13/src/runtime/race/race_linux_amd64.syso 3070001 /usr/share/go-1.13/src/runtime/race/race_linux_amd64.syso ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: golang-1.13-race-detector-runtime 0.0+svn332029-0ubuntu2 [modified: usr/lib/go-1.13/src/runtime/race/race_linux_amd64.syso] ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Jul 28 10:23:58 2020 Dependencies: SourcePackage: golang-1.13-race-detector-runtime UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: golang-1.13-race-detector-runtime (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1889162 Title: golang-1.13-race-detector-runtime conflicts with golang-1.13-src To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/golang-1.13-race-detector-runtime/+bug/1889162/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1886075] Re: Switch app windows using mouse wheel over dock icon
This option does exist in Ubuntu Dock. It's just disabled by default. It can be activated using Dconf Editor. Set the parameter 'org.gnome.shell.extensions.dash-to-dock' to be equal to 'cycle-windows'. It can also be easily done by running this command: gsettings set org.gnome.shell.extensions.dash-to-dock scroll-action 'cycle-windows' -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1886075 Title: Switch app windows using mouse wheel over dock icon To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1886075/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1884759] Re: U2f yubikey stopped working in chromium snap
** Changed in: chromium-browser (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/1884759 Title: U2f yubikey stopped working in chromium snap To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1884759/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1884759] Re: U2f yubikey stopped working in chromium snap
Log attached. Relevant line probably [92777:92906:0709/115647.054273:ERROR:udev_watcher.cc(96)] Failed to begin udev enumeration. ** Attachment added: "chrom3.log" https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1884759/+attachment/5390970/+files/chrom3.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1884759 Title: U2f yubikey stopped working in chromium snap To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1884759/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1885159] Re: Firefox after update doesn't start - Ubuntu 16.04.6 LTS
Same here: Ubuntu 16.04.6 LTS. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1885159 Title: Firefox after update doesn't start - Ubuntu 16.04.6 LTS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1885159/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1884759] Re: U2f yubikey stopped working in chromium snap
Tested firefox snap - u2f works. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1884759 Title: U2f yubikey stopped working in chromium snap To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1884759/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1884759] Re: U2f yubikey stopped working in chromium snap
I use it only for github, no special setup was needed (udev rules are already there for PIV). I logged last time some months ago so I don't know when it stopped working exactly. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1884759 Title: U2f yubikey stopped working in chromium snap To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1884759/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1872026] Re: App icon aspect ratio in the panel is broken
It fixes the issue for me after update of gnome-shell package with focal-proposed enabled. gnome-shell version is 3.36.3-1ubuntu1~20.04.2 Tested using winecfg. ** Tags removed: verification-needed-focal ** Tags added: verification-done-focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1872026 Title: App icon aspect ratio in the panel is broken To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1872026/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1884759] [NEW] U2f yubikey stopped working in chromium snap
Public bug reported: I was previously using u2f from yubikey in chromium snap, but now it doesn't work. No apparmor deny in dmesg (except accessing bluez), u2f slot is conneced. U2f still works in firefox installed as deb. # snap connections chromium | grep u2f u2f-devices chromium:u2f-devices :u2f-devices manual ** Affects: chromium-browser (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/1884759 Title: U2f yubikey stopped working in chromium snap To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1884759/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1850439] Re: No sound on ASUS UX534FT
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1850439/comments/170 first two commands are working for me, I've got my sound! thanks! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1850439 Title: No sound on ASUS UX534FT To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1850439/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1880226] Re: from_yaml filter failure on focal
Clean focal install doesn't have the problem. Installing saltstack from their official repo breaks ansible. Closing the ticket. ** Changed in: ansible (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1880226 Title: from_yaml filter failure on focal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ansible/+bug/1880226/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1880226] Re: from_yaml filter failure on focal
I have tried package versions from eoan (ansible, python3-yaml, python3-jinja2) and id didn't helped. So it looks like priblem is with python3.8 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1880226 Title: from_yaml filter failure on focal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ansible/+bug/1880226/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1880226] [NEW] from_yaml filter failure on focal
Public bug reported:
1. Create file "test.yaml" with content "test: true"
2. Create local playbook "playbook.yaml"
- hosts: localhost
connection: local
gather_facts: no
tasks:
- debug:
msg: "{{ lookup('file', 'test.yaml')|from_yaml }}"
3. Run playbook
ansible-playbook playbook.yaml
Error is:
fatal: [localhost]: FAILED! => {"msg": "Unexpected templating type error
occurred on ({{ lookup('file', 'test.yaml')|from_yaml }}): a string or
stream input is required"}
On eoan this works fine.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: ansible 2.9.6+dfsg-1
ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34
Uname: Linux 5.4.0-31-generic x86_64
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: X-Cinnamon
Date: Fri May 22 21:41:05 2020
PackageArchitecture: all
SourcePackage: ansible
UpgradeStatus: No upgrade log present (probably fresh install)
** Affects: ansible (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug focal
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1880226
Title:
from_yaml filter failure on focal
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ansible/+bug/1880226/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1873321] Re: The Show Applications button should be clickable in the corner or bottom of the screen
I have updated yaru-theme from focal-proposed. I confirm that together with gnome-shell-extension-ubuntu-dock previously updated from proposed this fixes the issue for me in focal. gnome-shell-extension-ubuntu-dock (68ubuntu1~20.04.1) yaru-theme (20.04.7) Many thanks to everyone involved! ** Tags removed: verification-needed-focal ** Tags added: verification-done-focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1873321 Title: The Show Applications button should be clickable in the corner or bottom of the screen To manage notifications about this bug go to: https://bugs.launchpad.net/dash-to-dock/+bug/1873321/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1873321] Re: The Show Applications button should be clickable in the corner or bottom of the screen
I have updated gnome-shell-extension-ubuntu-dock from focal-proposed and it doesn't fix the issue for me at the moment. I can guess that this is because yaru-theme is not yet updated in focal-proposed. gnome-shell-extension-ubuntu-dock (68ubuntu1~20.04.1) yaru-theme-gnome-shell (20.04.6) ** Tags removed: verification-needed-focal ** Tags added: verification-failed-focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1873321 Title: The Show Applications button should be clickable in the corner or bottom of the screen To manage notifications about this bug go to: https://bugs.launchpad.net/dash-to-dock/+bug/1873321/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1873321] Re: The Show Applications button should be clickable in the corner or bottom of the screen
I confirm that the issue is fixed for me in groovy. gnome-shell-extension-ubuntu-dock (68ubuntu1) yaru-theme-gnome-shell (20.10.1) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1873321 Title: The Show Applications button should be clickable in the corner or bottom of the screen To manage notifications about this bug go to: https://bugs.launchpad.net/dash-to-dock/+bug/1873321/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1876459] Re: windows 1909 drivers update breaks ALC294 sound
fix is here https://bugzilla.kernel.org/show_bug.cgi?id=207553 ** Bug watch added: Linux Kernel Bug Tracker #207553 https://bugzilla.kernel.org/show_bug.cgi?id=207553 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1876459 Title: windows 1909 drivers update breaks ALC294 sound To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1876459/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1876459] Re: windows 1909 drivers update breaks ALC294 sound
** Description changed: Hello! + + SHORT VERSION: + + Recent windows drivers initialize ALC294 with 24bit 48000HZ, after + rebooting to linux it produce garbaged sound (it decay every second, + very strange effect). If you reboot from windows 10 1909 directly to + linux it broken. You have to turn power off complete to reset the + device. + + + LONG VERSION: I recently install recent version of windows on separate partition and got garbaged sound on booth OS! My old version of windows was 1803 and everying was ok, I updated to 1909 and it got broken sound. Probably due to some firmware / configs / updates on sound chip. I let Windows to update drivers and notice my sound card driver got replaced by realtek drivers and sound got fixed on windows! But linux still not working propertly! also-info.sh shows two devices: http://alsa-project.org/db/?f=6d80e374011ccba05d32c8a6e6bde57316cbf06d This how it was on booth Linux and Windows 1810 before update. Windows also used to show two devices "AMD High Definition Audio Device", "High Definition Audio Device". Something tells me alsa detect cards correctly. But now, something changed and alsa need to update configs... Now Windows shows two devices: "AMD High Definition Audio Device" and second "Realtek(R) Audio". AMD High Definition Audio Device/10.0.1.10/HDAUDIO\FUNC_01_1002_AA01_00AA0100& REV_1007\5&14BACE15&0&0001 Realtek Semiconductor Corp./6.0.8757.1/HDAUDIO\FUNC_01_10EC_0294_10431B11& REV_1000\5&7195807&0&0001 AMD Audio CoProcessor/1.16.0.86/PCI\VEN_1022_15E2_15E21022_00\4&280 56CF2&0&0541 High Definition Audio Controller/10.0.18362.1 /PCI\VEN_1022_15E3_1B111043_00\4&28056CF2&0&0641 High Definition Audio Controller/10.0.18362.1/PCI\VEN_1002_15DE_15DE1002_00\4&28056CF2&0&0141 As you can see from new windows drivers it detects two devices 1002:AA01 and 10ec:0294, but alsa keep detecting 1002:15de and 1022:15e3 On Ubuntu machine sound still completely garbaged and sounds like broken speakers. My headphones makes even stranger sounds. Not sure what to do. I found several links about this issue here: https://github.com/torvalds/linux/commit/60083f9e94b2f28047d71ed778adf89357c1a8fb https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1850439 https://askubuntu.com/questions/1175095/asus-zenbook-ux534f-no-sound- from-speakers-headphones/1186977 Windows 1909 without updates shows those id's: AMD High Definition Audio Device/10.0.1.10/HDAUDIO\FUNC_01_1002_AA01_00AA0100& REV_1007\5&14BACE15&0&0001 High Definition Audio Device/10.0.18362.356/HDAUDIO\FUNC_01_10EC_0294_10431B11& REV_1000\5&7195807&0&0001 Windows 1803 without updates (old external installation, I still can boot here, and confirming those drivers produce exactly same sound issues like on linux): AMD High Definition Audio Device/10.0.1.6/HDAUDIO\FUNC_01_1002_AA01_00AA0100& REV_1007\5&14BACE15&0&0001 High Definition Audio Device/10.0.17134.1006/HDAUDIO\FUNC_01_10EC_0294_10431B11& REV_1000\5&7195807&0&0001 AMD Audio CoProcessor/1.17.0.94/PCI\VEN_1022_15E2_15E21022_00\4&280 56CF2&0&0541 Also, this sound card requires few addtitional actions to perform from here: https://wiki.archlinux.org/index.php/ASUS_Zenbook_UX390 - !!! If I turn off my notebook completely and boot directly into linux - sound works fine! Until I reboot to windows and get back into linux - without poweroff. I guess windows drivers set hardware to 24bit 48000HZ - channel, and alsa drivers does not reset it. - ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-26-generic 5.4.0-26.30 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: axet 1433 F pulseaudio /dev/snd/controlC0: axet 1433 F pulseaudio CasperMD5CheckResult: skip Date: Sat May 2 16:25:01 2020 MachineType: ASUSTeK COMPUTER INC. ZenBook UX431DA_UM431DA ProcEnviron: LANGUAGE=en_US TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-26-generic root=/dev/mapper/vg0-root ro acpi_enforce_resources=lax PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.4.0-26-generic N/A linux-backports-modules-5.4.0-26-generic N/A linux-firmware1.187 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/11/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX431DA.301 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX431DA
[Bug 1876459] Re: windows 1909 drivers update breaks ALC294 sound
** Description changed: Hello! I recently install recent version of windows on separate partition and got garbaged sound on booth OS! My old version of windows was 1803 and everying was ok, I updated to 1909 and it got broken sound. Probably due to some firmware / configs / updates on sound chip. I let Windows to update drivers and notice my sound card driver got replaced by realtek drivers and sound got fixed on windows! But linux still not working propertly! also-info.sh shows two devices: http://alsa-project.org/db/?f=6d80e374011ccba05d32c8a6e6bde57316cbf06d This how it was on booth Linux and Windows 1810 before update. Windows also used to show two devices "AMD High Definition Audio Device", "High Definition Audio Device". Something tells me alsa detect cards correctly. But now, something changed and alsa need to update configs... Now Windows shows two devices: "AMD High Definition Audio Device" and second "Realtek(R) Audio". AMD High Definition Audio Device/10.0.1.10/HDAUDIO\FUNC_01_1002_AA01_00AA0100& REV_1007\5&14BACE15&0&0001 Realtek Semiconductor Corp./6.0.8757.1/HDAUDIO\FUNC_01_10EC_0294_10431B11& REV_1000\5&7195807&0&0001 AMD Audio CoProcessor/1.16.0.86/PCI\VEN_1022_15E2_15E21022_00\4&280 56CF2&0&0541 High Definition Audio Controller/10.0.18362.1 /PCI\VEN_1022_15E3_1B111043_00\4&28056CF2&0&0641 High Definition Audio Controller/10.0.18362.1/PCI\VEN_1002_15DE_15DE1002_00\4&28056CF2&0&0141 As you can see from new windows drivers it detects two devices 1002:AA01 and 10ec:0294, but alsa keep detecting 1002:15de and 1022:15e3 On Ubuntu machine sound still completely garbaged and sounds like broken speakers. My headphones makes even stranger sounds. Not sure what to do. I found several links about this issue here: https://github.com/torvalds/linux/commit/60083f9e94b2f28047d71ed778adf89357c1a8fb https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1850439 https://askubuntu.com/questions/1175095/asus-zenbook-ux534f-no-sound- from-speakers-headphones/1186977 Windows 1909 without updates shows those id's: AMD High Definition Audio Device/10.0.1.10/HDAUDIO\FUNC_01_1002_AA01_00AA0100& REV_1007\5&14BACE15&0&0001 High Definition Audio Device/10.0.18362.356/HDAUDIO\FUNC_01_10EC_0294_10431B11& REV_1000\5&7195807&0&0001 Windows 1803 without updates (old external installation, I still can boot here, and confirming those drivers produce exactly same sound issues like on linux): AMD High Definition Audio Device/10.0.1.6/HDAUDIO\FUNC_01_1002_AA01_00AA0100& REV_1007\5&14BACE15&0&0001 High Definition Audio Device/10.0.17134.1006/HDAUDIO\FUNC_01_10EC_0294_10431B11& REV_1000\5&7195807&0&0001 AMD Audio CoProcessor/1.17.0.94/PCI\VEN_1022_15E2_15E21022_00\4&280 56CF2&0&0541 Also, this sound card requires few addtitional actions to perform from here: https://wiki.archlinux.org/index.php/ASUS_Zenbook_UX390 - !!! If I turn off my notebook completely and boot directly into linux sound works fine! Until I reboot to windows and get back into linux - without poweroff. I guess this is hardware state which affected. - + without poweroff. I guess windows drivers set hardware to 24bit 48000HZ + channel, and alsa drivers does not reset it. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-26-generic 5.4.0-26.30 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: axet 1433 F pulseaudio /dev/snd/controlC0: axet 1433 F pulseaudio CasperMD5CheckResult: skip Date: Sat May 2 16:25:01 2020 MachineType: ASUSTeK COMPUTER INC. ZenBook UX431DA_UM431DA ProcEnviron: LANGUAGE=en_US TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-26-generic root=/dev/mapper/vg0-root ro acpi_enforce_resources=lax PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.4.0-26-generic N/A linux-backports-modules-5.4.0-26-generic N/A linux-firmware1.187 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/11/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX431DA.301 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX431DA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias:
[Bug 1876459] Re: windows 1909 drivers update breaks ALC294 sound
** Description changed: Hello! I recently install recent version of windows on separate partition and got garbaged sound on booth OS! My old version of windows was 1803 and everying was ok, I updated to 1909 and it got broken sound. Probably due to some firmware / configs / updates on sound chip. I let Windows to update drivers and notice my sound card driver got replaced by realtek drivers and sound got fixed on windows! But linux still not working propertly! also-info.sh shows two devices: http://alsa-project.org/db/?f=6d80e374011ccba05d32c8a6e6bde57316cbf06d This how it was on booth Linux and Windows 1810 before update. Windows also used to show two devices "AMD High Definition Audio Device", "High Definition Audio Device". Something tells me alsa detect cards correctly. But now, something changed and alsa need to update configs... Now Windows shows two devices: "AMD High Definition Audio Device" and second "Realtek(R) Audio". AMD High Definition Audio Device/10.0.1.10/HDAUDIO\FUNC_01_1002_AA01_00AA0100& REV_1007\5&14BACE15&0&0001 Realtek Semiconductor Corp./6.0.8757.1/HDAUDIO\FUNC_01_10EC_0294_10431B11& REV_1000\5&7195807&0&0001 AMD Audio CoProcessor/1.16.0.86/PCI\VEN_1022_15E2_15E21022_00\4&280 56CF2&0&0541 High Definition Audio Controller/10.0.18362.1 /PCI\VEN_1022_15E3_1B111043_00\4&28056CF2&0&0641 High Definition Audio Controller/10.0.18362.1/PCI\VEN_1002_15DE_15DE1002_00\4&28056CF2&0&0141 - As you can see from new windows drivers it detects two devices 1002:AA01 and 10ec:0294, but alsa keep detecting 1002:15de and 1022:15e3 On Ubuntu machine sound still completely garbaged and sounds like broken speakers. My headphones makes even stranger sounds. Not sure what to do. I found several links about this issue here: https://github.com/torvalds/linux/commit/60083f9e94b2f28047d71ed778adf89357c1a8fb https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1850439 https://askubuntu.com/questions/1175095/asus-zenbook-ux534f-no-sound- from-speakers-headphones/1186977 Windows 1909 without updates shows those id's: AMD High Definition Audio Device/10.0.1.10/HDAUDIO\FUNC_01_1002_AA01_00AA0100& REV_1007\5&14BACE15&0&0001 High Definition Audio Device/10.0.18362.356/HDAUDIO\FUNC_01_10EC_0294_10431B11& REV_1000\5&7195807&0&0001 Windows 1803 without updates (old external installation, I still can boot here, and confirming those drivers produce exactly same sound issues like on linux): AMD High Definition Audio Device/10.0.1.6/HDAUDIO\FUNC_01_1002_AA01_00AA0100& REV_1007\5&14BACE15&0&0001 High Definition Audio Device/10.0.17134.1006/HDAUDIO\FUNC_01_10EC_0294_10431B11& REV_1000\5&7195807&0&0001 AMD Audio CoProcessor/1.17.0.94/PCI\VEN_1022_15E2_15E21022_00\4&280 56CF2&0&0541 Also, this sound card requires few addtitional actions to perform from here: https://wiki.archlinux.org/index.php/ASUS_Zenbook_UX390 + + + !!! If I turn off my notebook completely and boot directly into linux + sound works fine! Until I reboot to windows and get back into linux + without poweroff. I guess this is hardware state which affected. + ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-26-generic 5.4.0-26.30 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: axet 1433 F pulseaudio /dev/snd/controlC0: axet 1433 F pulseaudio CasperMD5CheckResult: skip Date: Sat May 2 16:25:01 2020 MachineType: ASUSTeK COMPUTER INC. ZenBook UX431DA_UM431DA ProcEnviron: LANGUAGE=en_US TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-26-generic root=/dev/mapper/vg0-root ro acpi_enforce_resources=lax PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.4.0-26-generic N/A linux-backports-modules-5.4.0-26-generic N/A linux-firmware1.187 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/11/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX431DA.301 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX431DA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias:
[Bug 1876459] Re: windows 1909 drivers update breaks ALC294 sound
** Description changed: Hello! I recently install recent version of windows on separate partition and got garbaged sound on booth OS! My old version of windows was 1803 and everying was ok, I updated to 1909 and it got broken sound. Probably due to some firmware / configs / updates on sound chip. I let Windows to update drivers and notice my sound card driver got replaced by realtek drivers and sound got fixed on windows! But linux still not working propertly! also-info.sh shows two devices: http://alsa-project.org/db/?f=6d80e374011ccba05d32c8a6e6bde57316cbf06d This how it was on booth Linux and Windows 1810 before update. Windows also used to show two devices "AMD High Definition Audio Device", "High Definition Audio Device". Something tells me alsa detect cards correctly. But now, something changed and alsa need to update configs... Now Windows shows two devices: "AMD High Definition Audio Device" and second "Realtek(R) Audio". AMD High Definition Audio Device/10.0.1.10/HDAUDIO\FUNC_01_1002_AA01_00AA0100& REV_1007\5&14BACE15&0&0001 Realtek Semiconductor Corp./6.0.8757.1/HDAUDIO\FUNC_01_10EC_0294_10431B11& REV_1000\5&7195807&0&0001 AMD Audio CoProcessor/1.16.0.86/PCI\VEN_1022_15E2_15E21022_00\4&280 56CF2&0&0541 + High Definition Audio Controller/10.0.18362.1 + /PCI\VEN_1022_15E3_1B111043_00\4&28056CF2&0&0641 + High Definition Audio Controller/10.0.18362.1/PCI\VEN_1002_15DE_15DE1002_00\4&28056CF2&0&0141 + As you can see from new windows drivers it detects two devices 1002:AA01 and 10ec:0294, but alsa keep detecting 1002:15de and 1022:15e3 On Ubuntu machine sound still completely garbaged and sounds like broken speakers. My headphones makes even stranger sounds. Not sure what to do. I found several links about this issue here: https://github.com/torvalds/linux/commit/60083f9e94b2f28047d71ed778adf89357c1a8fb https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1850439 https://askubuntu.com/questions/1175095/asus-zenbook-ux534f-no-sound- from-speakers-headphones/1186977 Windows 1909 without updates shows those id's: AMD High Definition Audio Device/10.0.1.10/HDAUDIO\FUNC_01_1002_AA01_00AA0100& REV_1007\5&14BACE15&0&0001 High Definition Audio Device/10.0.18362.356/HDAUDIO\FUNC_01_10EC_0294_10431B11& REV_1000\5&7195807&0&0001 Windows 1803 without updates (old external installation, I still can boot here, and confirming those drivers produce exactly same sound issues like on linux): AMD High Definition Audio Device/10.0.1.6/HDAUDIO\FUNC_01_1002_AA01_00AA0100& REV_1007\5&14BACE15&0&0001 High Definition Audio Device/10.0.17134.1006/HDAUDIO\FUNC_01_10EC_0294_10431B11& REV_1000\5&7195807&0&0001 AMD Audio CoProcessor/1.17.0.94/PCI\VEN_1022_15E2_15E21022_00\4&280 56CF2&0&0541 Also, this sound card requires few addtitional actions to perform from here: https://wiki.archlinux.org/index.php/ASUS_Zenbook_UX390 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-26-generic 5.4.0-26.30 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: axet 1433 F pulseaudio /dev/snd/controlC0: axet 1433 F pulseaudio CasperMD5CheckResult: skip Date: Sat May 2 16:25:01 2020 MachineType: ASUSTeK COMPUTER INC. ZenBook UX431DA_UM431DA ProcEnviron: LANGUAGE=en_US TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-26-generic root=/dev/mapper/vg0-root ro acpi_enforce_resources=lax PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.4.0-26-generic N/A linux-backports-modules-5.4.0-26-generic N/A linux-firmware1.187 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/11/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX431DA.301 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX431DA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX431DA.301:bd09/11/2019:svnASUSTeKCOMPUTERINC.:pnZenBookUX431DA_UM431DA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX431DA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ZenBook dmi.product.name: ZenBook UX431DA_UM431DA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. -- You received this bug notification because you are a member of
[Bug 1876459] [NEW] windows 1909 drivers update breaks ALC294 sound
Public bug reported: Hello! I recently install recent version of windows on separate partition and got garbaged sound on booth OS! My old version of windows was 1803 and everying was ok, I updated to 1909 and it got broken sound. Probably due to some firmware / configs / updates on sound chip. I let Windows to update drivers and notice my sound card driver got replaced by realtek drivers and sound got fixed on windows! But linux still not working propertly! also-info.sh shows two devices: http://alsa-project.org/db/?f=6d80e374011ccba05d32c8a6e6bde57316cbf06d This how it was on booth Linux and Windows 1810 before update. Windows also used to show two devices "AMD High Definition Audio Device", "High Definition Audio Device". Something tells me alsa detect cards correctly. But now, something changed and alsa need to update configs... Now Windows shows two devices: "AMD High Definition Audio Device" and second "Realtek(R) Audio". AMD High Definition Audio Device/10.0.1.10/HDAUDIO\FUNC_01_1002_AA01_00AA0100& REV_1007\5&14BACE15&0&0001 Realtek Semiconductor Corp./6.0.8757.1/HDAUDIO\FUNC_01_10EC_0294_10431B11& REV_1000\5&7195807&0&0001 AMD Audio CoProcessor/1.16.0.86/PCI\VEN_1022_15E2_15E21022_00\4&280 56CF2&0&0541 As you can see from new windows drivers it detects two devices 1002:AA01 and 10ec:0294, but alsa keep detecting 1002:15de and 1022:15e3 On Ubuntu machine sound still completely garbaged and sounds like broken speakers. My headphones makes even stranger sounds. Not sure what to do. I found several links about this issue here: https://github.com/torvalds/linux/commit/60083f9e94b2f28047d71ed778adf89357c1a8fb https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1850439 https://askubuntu.com/questions/1175095/asus-zenbook-ux534f-no-sound- from-speakers-headphones/1186977 Windows 1909 without updates shows those id's: AMD High Definition Audio Device/10.0.1.10/HDAUDIO\FUNC_01_1002_AA01_00AA0100& REV_1007\5&14BACE15&0&0001 High Definition Audio Device/10.0.18362.356/HDAUDIO\FUNC_01_10EC_0294_10431B11& REV_1000\5&7195807&0&0001 Windows 1803 without updates (old external installation, I still can boot here, and confirming those drivers produce exactly same sound issues like on linux): AMD High Definition Audio Device/10.0.1.6/HDAUDIO\FUNC_01_1002_AA01_00AA0100& REV_1007\5&14BACE15&0&0001 High Definition Audio Device/10.0.17134.1006/HDAUDIO\FUNC_01_10EC_0294_10431B11& REV_1000\5&7195807&0&0001 AMD Audio CoProcessor/1.17.0.94/PCI\VEN_1022_15E2_15E21022_00\4&280 56CF2&0&0541 Also, this sound card requires few addtitional actions to perform from here: https://wiki.archlinux.org/index.php/ASUS_Zenbook_UX390 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-26-generic 5.4.0-26.30 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: axet 1433 F pulseaudio /dev/snd/controlC0: axet 1433 F pulseaudio CasperMD5CheckResult: skip Date: Sat May 2 16:25:01 2020 MachineType: ASUSTeK COMPUTER INC. ZenBook UX431DA_UM431DA ProcEnviron: LANGUAGE=en_US TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-26-generic root=/dev/mapper/vg0-root ro acpi_enforce_resources=lax PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.4.0-26-generic N/A linux-backports-modules-5.4.0-26-generic N/A linux-firmware1.187 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/11/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX431DA.301 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX431DA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX431DA.301:bd09/11/2019:svnASUSTeKCOMPUTERINC.:pnZenBookUX431DA_UM431DA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX431DA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ZenBook dmi.product.name: ZenBook UX431DA_UM431DA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1876459 Title: windows 1909 drivers update breaks ALC294 sound To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1876459/+subscriptions -- ubuntu-bugs mailing
[Bug 1876459] Re: windows 1909 drivers update breaks ALC294 sound
Re-posting broken links: http://alsa-project.org/db/?f=6d80e374011ccba05d32c8a6e6bde57316cbf06d https://github.com/torvalds/linux/commit/60083f9e94b2f28047d71ed778adf89357c1a8fb https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1850439 https://askubuntu.com/questions/1175095/asus-zenbook-ux534f-no-sound- from-speakers-headphones/1186977 ** Description changed: Hello! I recently install recent version of windows on separate partition and got garbaged sound on booth OS! My old version of windows was 1803 and everying was ok, I updated to 1909 and it got broken sound. Probably due to some firmware / configs / updates on sound chip. I let Windows to update drivers and notice my sound card driver got replaced by realtek drivers and sound got fixed on windows! But linux still not working propertly! also-info.sh shows two devices: - http://alsa-project.org/db/?f=6d80e3...bde57316cbf06d + http://alsa-project.org/db/?f=6d80e374011ccba05d32c8a6e6bde57316cbf06d This how it was on booth Linux and Windows 1810 before update. Windows also used to show two devices "AMD High Definition Audio Device", "High Definition Audio Device". Something tells me alsa detect cards correctly. But now, something changed and alsa need to update configs... Now Windows shows two devices: "AMD High Definition Audio Device" and second "Realtek(R) Audio". AMD High Definition Audio Device/10.0.1.10/HDAUDIO\FUNC_01_1002_AA01_00AA0100& REV_1007\5&14BACE15&0&0001 Realtek Semiconductor Corp./6.0.8757.1/HDAUDIO\FUNC_01_10EC_0294_10431B11& REV_1000\5&7195807&0&0001 AMD Audio CoProcessor/1.16.0.86/PCI\VEN_1022_15E2_15E21022_00\4&280 56CF2&0&0541 As you can see from new windows drivers it detects two devices 1002:AA01 and 10ec:0294, but alsa keep detecting 1002:15de and 1022:15e3 On Ubuntu machine sound still completely garbaged and sounds like broken speakers. My headphones makes even stranger sounds. Not sure what to do. I found several links about this issue here: https://github.com/torvalds/linux/co...adf89357c1a8fb https://bugs.launchpad.net/ubuntu/+s...x/+bug/1850439 https://askubuntu.com/questions/1175...phones/1186977 Windows 1909 without updates shows those id's: AMD High Definition Audio Device/10.0.1.10/HDAUDIO\FUNC_01_1002_AA01_00AA0100& REV_1007\5&14BACE15&0&0001 High Definition Audio Device/10.0.18362.356/HDAUDIO\FUNC_01_10EC_0294_10431B11& REV_1000\5&7195807&0&0001 - Windows 1803 without updates (old external installation): + Windows 1803 without updates (old external installation, I still can + boot here, and confirming those drivers produce exactly same sound + issues like on linux): AMD High Definition Audio Device/10.0.1.6/HDAUDIO\FUNC_01_1002_AA01_00AA0100& REV_1007\5&14BACE15&0&0001 High Definition Audio Device/10.0.17134.1006/HDAUDIO\FUNC_01_10EC_0294_10431B11& REV_1000\5&7195807&0&0001 AMD Audio CoProcessor/1.17.0.94/PCI\VEN_1022_15E2_15E21022_00\4&280 56CF2&0&0541 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-26-generic 5.4.0-26.30 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: - USERPID ACCESS COMMAND - /dev/snd/controlC1: axet 1433 F pulseaudio - /dev/snd/controlC0: axet 1433 F pulseaudio + USERPID ACCESS COMMAND + /dev/snd/controlC1: axet 1433 F pulseaudio + /dev/snd/controlC0: axet 1433 F pulseaudio CasperMD5CheckResult: skip Date: Sat May 2 16:25:01 2020 MachineType: ASUSTeK COMPUTER INC. ZenBook UX431DA_UM431DA ProcEnviron: - LANGUAGE=en_US - TERM=xterm-256color - PATH=(custom, no user) - LANG=en_US.UTF-8 - SHELL=/bin/bash + LANGUAGE=en_US + TERM=xterm-256color + PATH=(custom, no user) + LANG=en_US.UTF-8 + SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-26-generic root=/dev/mapper/vg0-root ro acpi_enforce_resources=lax PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: - linux-restricted-modules-5.4.0-26-generic N/A - linux-backports-modules-5.4.0-26-generic N/A - linux-firmware1.187 + linux-restricted-modules-5.4.0-26-generic N/A + linux-backports-modules-5.4.0-26-generic N/A + linux-firmware1.187 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/11/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX431DA.301 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX431DA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC.
[Bug 1864901] Re: [snap] suggestion: alert users when the snap has been refreshed while running
tarantula!root# ps axu | grep chr root 561745 0.0 0.0 6436 728 pts/2S+ 15:20 0:00 grep chr tarantula!root# snap refresh chromium error: cannot refresh "chromium": snap "chromium" has running apps (chromium) Had to restart snapd to update chromium snap. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1864901 Title: [snap] suggestion: alert users when the snap has been refreshed while running To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1864901/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1864901] Re: [snap] suggestion: alert users when the snap has been refreshed while running
tarantula!root# snap refresh core18 20200427 from Canonical✓ refreshed tarantula!root# snap refresh All snaps up to date. tarantula!root# snap list | grep chromium chromium 81.0.4044.1221119 latest/stable canonical*- tarantula!root# snap info --abs-time chromium name: chromium summary: Chromium web browser, open-source version of Chrome publisher: Canonical✓ store-url: https://snapcraft.io/chromium contact: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bugs?field.tag=snap license: unset description: | An open-source browser project that aims to build a safer, faster, and more stable way for all Internet users to experience the web. commands: - chromium.chromedriver - chromium snap-id: XKEcBqPM06H1Z7zGOdG5fbICuf8NWK5R tracking: latest/stable refresh-date: 2020-04-25T11:23:52+03:00 channels: latest/stable:81.0.4044.129 2020-04-29T17:25:51Z (1135) 161MB - latest/candidate: 81.0.4044.129 2020-04-28T18:04:52Z (1135) 161MB - latest/beta: 83.0.4103.23 2020-04-25T02:07:58Z (1125) 163MB - latest/edge: 84.0.4128.3 2020-04-29T05:50:21Z (1136) 164MB - installed: 81.0.4044.122 (1119) 161MB - -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1864901 Title: [snap] suggestion: alert users when the snap has been refreshed while running To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1864901/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1864901] Re: [snap] suggestion: alert users when the snap has been refreshed while running
tarantula!root# snap refresh All snaps up to date. How do I get the "latest" ? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1864901 Title: [snap] suggestion: alert users when the snap has been refreshed while running To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1864901/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1864901] Re: [snap] suggestion: alert users when the snap has been refreshed while running
I'm still seeing the problem. tarantula!root# snap refresh All snaps up to date. tarantula!root# snap list | grep chromium chromium 81.0.4044.1221119 latest/stable canonical*- -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1864901 Title: [snap] suggestion: alert users when the snap has been refreshed while running To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1864901/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1872268] Re: Gnome Shell completely freezes Ubuntu 20.04
*** This bug is a duplicate of bug 1843182 *** https://bugs.launchpad.net/bugs/1843182 Sorry, not the + key, but the key Esc -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1872268 Title: Gnome Shell completely freezes Ubuntu 20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1872268/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1872268] Re: Gnome Shell completely freezes Ubuntu 20.04
*** This bug is a duplicate of bug 1843182 *** https://bugs.launchpad.net/bugs/1843182 I have the same problem, I have grouped all applications into categories. To reproduce the error, I open the category after clicking + and so on several times until it freezes. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1872268 Title: Gnome Shell completely freezes Ubuntu 20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1872268/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1870827]
(In reply to Dennis Mayr from comment #53) Ubuntu LTS has special policy for some programs (e.g. Firefox) to upgrade them. I'm using Ubuntu 16.04 and have latest stable Firefox. So this is not a problem. > What other workarounds are available in a shorter timeframe? https://bugzilla.mozilla.org/show_bug.cgi?id=1495900#c44 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1870827 Title: Firefox hangs after simultaneously opening Chrome/Electron-based applications To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1870827/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1874913] [NEW] vrms does not report linux-firmware package
Public bug reported: linux-firmware contains amdgpu and intel wifi proprietary binary, this package well reported by vrms on debian (vs firmware-amd-graphics and firmware-iwlwifi) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: vrms 1.25ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Apr 25 00:01:31 2020 Dependencies: PackageArchitecture: all SourcePackage: vrms UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: vrms (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1874913 Title: vrms does not report linux-firmware package To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vrms/+bug/1874913/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1873476] [NEW] incorrect status intel 8265 / 8275
Public bug reported: software-properties reporting I have not working Intel 8265 / 8275 device it offer options: This device not working. grayed 1) using iwlwifi 2) continue using manually installed drivers. grayed 3) Do not use device But device working fine without any manually installed drivers. I'm using original Ubuntu 19.10 installation. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: software-properties-gtk 0.98.5 ProcVersionSignature: Ubuntu 5.3.0-46.38-generic 5.3.18 Uname: Linux 5.3.0-46-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu8.8 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Apr 17 17:52:46 2020 PackageArchitecture: all SourcePackage: software-properties UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: software-properties (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1873476 Title: incorrect status intel 8265 / 8275 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1873476/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1776873] Re: Whitelisted allowedURLschemes breaks some desktop apps
I just found the issue second ago. It is related to SNAP_REEXEC behavior. The idea is to run snap from snap_core installed from snap. If you have system snap installed it will be reexec'd from snap core. To disable it you need to change the source. Just run this before compilation and you will be ok: sed -i 's/!osutil.GetenvBool(reExecKey, true)/true/' snapd-*/cmd/cmd_linux.go -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1776873 Title: Whitelisted allowedURLschemes breaks some desktop apps To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1776873/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1776873] Re: Whitelisted allowedURLschemes breaks some desktop apps
Seems like a new linux virus preventing me from running compiled snap. Not the right place to report but who knows? When I recompile the snap package and changed "help" output to "refresh !!! and remove snaps" and unpack the content of resulting file into 123/. I reinstall the system package and result md5 sum look like this: axet@axet-laptop:~/local$ md5sum 123/usr/bin/snap /usr/bin/snap f6639f5060dcd23506082f6ff0699f72 123/usr/bin/snap f6639f5060dcd23506082f6ff0699f72 /usr/bin/snap axet@axet-laptop:~/local$ When I run the package from ./123/usr/bin/snap I got my "!!! and remove snaps" but when I ran the same file (same md5) from /usr/bin/snap I got the old output. axet@axet-laptop:~/local$ ./123/usr/bin/snap The snap command lets you install, configure, refresh !!! and remove snaps. Snaps are packages that work across many different Linux distributions, enabling secure delivery and operation of the latest apps and utilities. ... axet@axet-laptop:~/local$ /usr/bin/snap The snap command lets you install, configure, refresh and remove snaps. Snaps are packages that work across many different Linux distributions, enabling secure delivery and operation of the latest apps and utilities. ... Even when I copy my /usr/bin/snap into 11 file and run it from another location I still getting my new "!!! and remove" string. Seems like somthing (bug or virus) load old snap package when I run it from /usr/bin/snap location and when I read the same file I get my actual file system data. Not sure what kind of virus, trojan or system nvme, encryption or kernel bug I have... Maybe anyone knows? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1776873 Title: Whitelisted allowedURLschemes breaks some desktop apps To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1776873/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1776873] Re: Whitelisted allowedURLschemes breaks some desktop apps
For some reason I unable to rebuild snapd following #29 instruction. All goes fine, but in the end xdg-open wont work. I've checked /var/log/syslog and it full of: chromium_chromium.desktop[1674]: user-open error: Supplied URL scheme "magnet" is not allowed What is interesting, when I'm changing the source code of launcher.go I also changed the line with error text to "Supplied !!! URL scheme"... but in syslog error line still appears the same with out "!!!" this conclude changes never goes into the /usr/bin/snap binary file. I tried to remove ~/.cache/go-build /tmp/go-build turn off wifi, but still resulting package still produce old version of error text. I have no idea how to rebuild package correctly, following #28 not working. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1776873 Title: Whitelisted allowedURLschemes breaks some desktop apps To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1776873/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1851385] Re: ubuntu 19.10 / print bug : requires authentication
*** This bug is a duplicate of bug 1849859 *** https://bugs.launchpad.net/bugs/1849859 I have the same issue on two PCs with HP LaserJet 1020 printer connected to the Wi-Fi router on Ubuntu 19.10. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1851385 Title: ubuntu 19.10 / print bug : requires authentication To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1851385/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1862899] [NEW] Cannon Point-LP CNVi: Error sending STATISTICS_CMD: time out after 2000ms.
Public bug reported: I have Lenovo ThinkPad X1 Carbon 7th (20QD003CRT), wifi adapter "Intel Corporation Cannon Point-LP CNVi [Wireless-AC] (rev 11)". Xubuntu 19.10 amd64 installed, without dualboot (no any other system installed). I use UEFI to boot. Problem: yesterday my internal wifi adapter stopped to work for some seconds, GUI (XFCE desktop) freezed too, and then returned back to work. All from /var/log/syslog for this time: Feb 11 12:25:52 C9086 kernel: [10371.979560] iwlwifi :00:14.3: Error sending STATISTICS_CMD: time out after 2000ms. Feb 11 12:25:52 C9086 kernel: [10371.979569] iwlwifi :00:14.3: Current CMD queue read_ptr 119 write_ptr 120 Feb 11 12:25:53 C9086 kernel: [10372.228460] iwlwifi :00:14.3: HW error, resetting before reading Feb 11 12:25:54 C9086 kernel: [10372.235464] iwlwifi :00:14.3: Start IWL Error Log Dump: Feb 11 12:25:54 C9086 kernel: [10372.235467] iwlwifi :00:14.3: Status: 0x0080, count: 453879397 Feb 11 12:25:54 C9086 kernel: [10372.235468] iwlwifi :00:14.3: Loaded firmware version: 46.6bf1df06.0 Feb 11 12:25:54 C9086 kernel: [10372.235469] iwlwifi :00:14.3: 0xB15FDEBE | ADVANCED_SYSASSERT Feb 11 12:25:54 C9086 kernel: [10372.235470] iwlwifi :00:14.3: 0x0AAAE311 | trm_hw_status0 Feb 11 12:25:54 C9086 kernel: [10372.235471] iwlwifi :00:14.3: 0x4ABEAA8E | trm_hw_status1 Feb 11 12:25:54 C9086 kernel: [10372.235472] iwlwifi :00:14.3: 0x2C23FA10 | branchlink2 Feb 11 12:25:54 C9086 kernel: [10372.235472] iwlwifi :00:14.3: 0x379A2F8D | interruptlink1 Feb 11 12:25:54 C9086 kernel: [10372.235473] iwlwifi :00:14.3: 0x21730095 | interruptlink2 Feb 11 12:25:54 C9086 kernel: [10372.235473] iwlwifi :00:14.3: 0x43BDCC1D | data1 Feb 11 12:25:54 C9086 kernel: [10372.235474] iwlwifi :00:14.3: 0x7C910E05 | data2 Feb 11 12:25:54 C9086 kernel: [10372.235475] iwlwifi :00:14.3: 0x2DB0BBD2 | data3 Feb 11 12:25:54 C9086 kernel: [10372.235475] iwlwifi :00:14.3: 0x5288F8D1 | beacon time Feb 11 12:25:54 C9086 kernel: [10372.235476] iwlwifi :00:14.3: 0xC6FAB7FC | tsf low Feb 11 12:25:54 C9086 kernel: [10372.235477] iwlwifi :00:14.3: 0x050D2726 | tsf hi Feb 11 12:25:54 C9086 kernel: [10372.235477] iwlwifi :00:14.3: 0xD3DD7697 | time gp1 Feb 11 12:25:54 C9086 kernel: [10372.235478] iwlwifi :00:14.3: 0x923A05D9 | time gp2 Feb 11 12:25:54 C9086 kernel: [10372.235479] iwlwifi :00:14.3: 0xE3F5F9F3 | uCode revision type Feb 11 12:25:54 C9086 kernel: [10372.235479] iwlwifi :00:14.3: 0xB6996AB0 | uCode version major Feb 11 12:25:54 C9086 kernel: [10372.235480] iwlwifi :00:14.3: 0x1F870BDB | uCode version minor Feb 11 12:25:54 C9086 kernel: [10372.235481] iwlwifi :00:14.3: 0x094F68F9 | hw version Feb 11 12:25:54 C9086 kernel: [10372.235481] iwlwifi :00:14.3: 0xBDFD2CE7 | board version Feb 11 12:25:54 C9086 kernel: [10372.235482] iwlwifi :00:14.3: 0x726FB65D | hcmd Feb 11 12:25:54 C9086 kernel: [10372.235483] iwlwifi :00:14.3: 0x5C2E5991 | isr0 Feb 11 12:25:54 C9086 kernel: [10372.235483] iwlwifi :00:14.3: 0x3D72BE19 | isr1 Feb 11 12:25:54 C9086 kernel: [10372.235484] iwlwifi :00:14.3: 0x89DCC17D | isr2 Feb 11 12:25:54 C9086 kernel: [10372.235485] iwlwifi :00:14.3: 0x77D5EED7 | isr3 Feb 11 12:25:54 C9086 kernel: [10372.235485] iwlwifi :00:14.3: 0x408F00D3 | isr4 Feb 11 12:25:54 C9086 kernel: [10372.235486] iwlwifi :00:14.3: 0x79D5F948 | last cmd Id Feb 11 12:25:54 C9086 kernel: [10372.235487] iwlwifi :00:14.3: 0x4390E360 | wait_event Feb 11 12:25:54 C9086 kernel: [10372.235487] iwlwifi :00:14.3: 0xADCFE78F | l2p_control Feb 11 12:25:54 C9086 kernel: [10372.235488] iwlwifi :00:14.3: 0x113C819A | l2p_duration Feb 11 12:25:54 C9086 kernel: [10372.235489] iwlwifi :00:14.3: 0xD133CCA0 | l2p_mhvalid Feb 11 12:25:54 C9086 kernel: [10372.235489] iwlwifi :00:14.3: 0x8CF68910 | l2p_addr_match Feb 11 12:25:54 C9086 kernel: [10372.235490] iwlwifi :00:14.3: 0x1656B4BC | lmpm_pmg_sel Feb 11 12:25:54 C9086 kernel: [10372.235491] iwlwifi :00:14.3: 0xB103BF28 | timestamp Feb 11 12:25:54 C9086 kernel: [10372.235491] iwlwifi :00:14.3: 0x4FD31C1C | flow_handler Feb 11 12:25:54 C9086 kernel: [10372.235524] iwlwifi :00:14.3: Start IWL Error Log Dump: Feb 11 12:25:54 C9086 kernel: [10372.235524] iwlwifi :00:14.3: Status: 0x0080, count: -1758659929 Feb 11 12:25:54 C9086 kernel: [10372.235525] iwlwifi :00:14.3: 0xAFAFB72B | ADVANCED_SYSASSERT Feb 11 12:25:54 C9086 kernel: [10372.235526] iwlwifi :00:14.3: 0x992FBC29 | umac branchlink1 Feb 11 12:25:54 C9086 kernel: [10372.235526] iwlwifi :00:14.3: 0xE5AB6416 | umac branchlink2 Feb 11 12:25:54 C9086 kernel: [10372.235527] iwlwifi :00:14.3: 0x9A220B9D | umac interruptlink1 Feb 11 12:25:54 C9086 kernel: [10372.235528] iwlwifi :00:14.3: 0xF5EB4D4F | umac interruptlink2 Feb 11 12:25:54 C9086 kernel: [10372.235528] iwlwifi :00:14.3:
[Bug 1370953] Re: layout switch is delayed
I confirm this bug is still present in ubuntu 19.10. My comment in gnome bug tracker: https://gitlab.gnome.org/GNOME/gnome- shell/issues/1154#note_696130 ** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/issues #1154 https://gitlab.gnome.org/GNOME/gnome-shell/issues/1154 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1370953 Title: layout switch is delayed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1370953/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1860781] Re: netplan networkd - bridge configuration not work
In systemd-networkd documentation found that networkd assign different MAC address to the bridge than physical interface has and this my lead to some connection issues. To avoid this problems you must specify MAC address to bridge interface same as on your physical device. After I add proper MAC address to bridge interface configuration start working. New working config: network: version: 2 renderer: networkd ethernets: enp0s3: dhcp4: no dhcp6: no bridges: br-ex: macaddress: 08:00:27:0b:07:94 interfaces: [enp0s3] addresses: [10.64.10.100/24] gateway4: 10.64.10.1 mtu: 1500 nameservers: addresses: [8.8.8.8] dhcp4: no dhcp6: no parameters: stp: no I suggest this MAC address issue should be mentioned in Netplan documentation. Particular in examples page (https://netplan.io/examples) because it appear as first result when googling how to configure network with netplan. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1860781 Title: netplan networkd - bridge configuration not work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/netplan.io/+bug/1860781/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
