[Bug 1879247] Re: [27C6:538D] Goodix fingerprint is not supported.
** Summary changed: - [27C6:538D] goodix fingerprint is not supported. + [27C6:538D] Goodix fingerprint is not supported. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1879247 Title: [27C6:538D] Goodix fingerprint is not supported. To manage notifications about this bug go to: https://bugs.launchpad.net/libfprint/+bug/1879247/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1891974] Re: [06cb:00be] Synaptics fingerprint reader is not supported
** Summary changed: - Can not support Synaptics 06cb:00be fingerprint + [06cb:00be] Synaptics fingerprint reader is not supported -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1891974 Title: [06cb:00be] Synaptics fingerprint reader is not supported To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1891974/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1899882] Re: hdmi monitor on
I'm heading for bed shortly but will watch the email for another 5 minutes. -- John On Mon, Dec 28, 2020 at 11:40 PM John Dunlap wrote: > It's pretty jerky. Then after a number of cycles of blinking screen on > the laptop and the dock seemingly being restarted (the Ethernet kept going > off and on) the external screen came to life and now the system seems to be > operating normally. I did fiddle with the "Display" GUI a bit before it > stopped being jerky. Attached is the dmesg. -- John > > On Mon, Dec 28, 2020 at 11:18 PM John Dunlap > wrote: > >> I suppose these .deb files are the ones you'd like me to try: >> >> -rw-rw-r-- 1 dunlap dunlap 11476820 2020-12-27 18:19 >> linux-headers-5.10.0-051000drmtip20201228_5.10.0-051000drmtip20201228.202012280203_all.deb >> -rw-rw-r-- 1 dunlap dunlap 1248336 2020-12-27 18:22 >> linux-headers-5.10.0-051000drmtip20201228-generic_5.10.0-051000drmtip20201228.202012280203_amd64.deb >> -rw-rw-r-- 1 dunlap dunlap 10981324 2020-12-27 18:21 >> linux-image-unsigned-5.10.0-051000drmtip20201228-generic_5.10.0-051000drmtip20201228.202012280203_amd64.deb >> -rw-rw-r-- 1 dunlap dunlap 56164620 2020-12-27 18:21 >> linux-modules-5.10.0-051000drmtip20201228-generic_5.10.0-051000drmtip20201228.202012280203_amd64.deb >> >> I'll install them and try drm.debug=0x11e log_buf_len=16M in grub >> >> On Mon, Dec 28, 2020 at 10:55 PM koba <1899...@bugs.launchpad.net> wrote: >> >>> @John, if you're free, Would you please help to try drm-tip? >>> You cound just download the files with "generic" and >>> linux_header_***_all.deb >>> https://kernel.ubuntu.com/~kernel-ppa/mainline/drm-tip/2020-12-28/ >>> >>> And enable drm.debug=0x11e log_buf_len=16M in grub. >>> >>> If the issue still exist, please upload the dmesg >>> >>> -- >>> You received this bug notification because you are subscribed to the bug >>> report. >>> https://bugs.launchpad.net/bugs/1899882 >>> >>> Title: >>> hdmi monitor on >>> >>> Status in linux package in Ubuntu: >>> Fix Committed >>> >>> Bug description: >>> XPS 13 9300 -- 50H3P53 -- Dell laptop >>> WD19TB --- 4BWNW43 -- Dell Thunderbolt dock >>> S2319HS -- B4TYZ13 -- Dell 23" external monitor >>> >>> External monitor remains black when waking system after suspending. >>> Works OK when log out then log in or when reboot. >>> Using HDMI cable from dock to monitor. >>> >>> From /var/log/syslog: >>> >>> Oct 14 21:09:41 lt9 kernel: [32059.746520] [ cut here >>> ] >>> Oct 14 21:09:41 lt9 kernel: [32059.746524] WARN_ON(is_mst && (port == >>> PORT_A || port == PORT_E)) >>> Oct 14 21:09:41 lt9 kernel: [32059.746674] WARNING: CPU: 6 PID: 1221 >>> at drivers/gpu/drm/i915/display/intel_ddi.c:3179 >>> intel_ddi_pre_enable_dp.isra.0+0x20f/0x430 [i915] >>> Oct 14 21:09:41 lt9 kernel: [32059.746676] Modules linked in: ccm >>> usblp ftdi_sio usbserial snd_usb_audio snd_usbmidi_lib rfcomm >>> typec_displayport cdc_ether usbnet r8152 mii cmac algif_hash algif_skcipher >>> af_al >>> g bnep btusb btrtl btbcm btintel uvcvideo videobuf2_vmalloc >>> videobuf2_memops bluetooth videobuf2_v4l2 videobuf2_common videodev mc >>> ecdh_generic ecc nls_iso8859_1 snd_sof_pci snd_sof_intel_hda_common >>> snd_soc_hd >>> ac_hda snd_hda_codec_hdmi snd_sof_intel_hda snd_sof_intel_byt >>> snd_sof_intel_ipc snd_sof snd_sof_xtensa_dsp snd_hda_ext_core >>> snd_soc_acpi_intel_match snd_soc_acpi snd_soc_core snd_compress >>> snd_hda_codec_realtek >>>ac97_bus snd_pcm_dmaengine snd_hda_codec_generic snd_hda_intel >>> mei_hdcp snd_intel_dspcfg dell_laptop snd_hda_codec joydev ledtrig_audio >>> intel_rapl_msr snd_hda_core snd_hwdep x86_pkg_temp_thermal intel_powercl >>> amp snd_pcm coretemp kvm_intel kvm snd_seq_midi snd_seq_midi_event >>> snd_rawmidi crct10dif_pclmul ghash_clmulni_intel dell_wmi snd_seq >>> aesni_intel dell_smbios crypto_simd dcdbas cryptd glue_helper rapl >>> Oct 14 21:09:41 lt9 kernel: [32059.746719] intel_cstate iwlmvm >>> input_leds serio_raw mac80211 snd_seq_device intel_wmi_thunderbolt wmi_bmof >>> dell_wmi_descriptor snd_timer libarc4 snd hid_sensor_als hid_sensor_t >>> rigger industrialio_triggered_buffer iwlwifi kfifo_buf >>> hid_sensor_iio_common rtsx_pci_ms 8250_dw memstick soundcore industrialio >>> ucsi_acpi processor_thermal_device intel_rapl_common mei_me typec_ucsi >>> cros_ec_i >>> shtp hid_multitouch mei cfg80211 cros_ec intel_soc_dts_iosf typec >>> int3403_thermal mac_hid int340x_thermal_zone int3400_thermal intel_hid >>> acpi_thermal_rel sparse_keymap acpi_pad acpi_tad sch_fq_codel parport_pc >>>ppdev lp parport ip_tables x_tables autofs4 btrfs zstd_compress >>> usbhid raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor >>> async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear hid_sensor_ >>> hub hid_generic intel_ishtp_loader intel_ishtp_hid rtsx_pci_sdmmc i915 >>> crc32_pclmul rtsx_pci psmouse nvme i2c_algo_bit drm_kms_helper >>> intel_lpss_pci i2c_i801 intel_lpss nvme_core
Re: [Bug 1899882] Re: hdmi monitor on
It's pretty jerky. Then after a number of cycles of blinking screen on the laptop and the dock seemingly being restarted (the Ethernet kept going off and on) the external screen came to life and now the system seems to be operating normally. I did fiddle with the "Display" GUI a bit before it stopped being jerky. Attached is the dmesg. -- John On Mon, Dec 28, 2020 at 11:18 PM John Dunlap wrote: > I suppose these .deb files are the ones you'd like me to try: > > -rw-rw-r-- 1 dunlap dunlap 11476820 2020-12-27 18:19 > linux-headers-5.10.0-051000drmtip20201228_5.10.0-051000drmtip20201228.202012280203_all.deb > -rw-rw-r-- 1 dunlap dunlap 1248336 2020-12-27 18:22 > linux-headers-5.10.0-051000drmtip20201228-generic_5.10.0-051000drmtip20201228.202012280203_amd64.deb > -rw-rw-r-- 1 dunlap dunlap 10981324 2020-12-27 18:21 > linux-image-unsigned-5.10.0-051000drmtip20201228-generic_5.10.0-051000drmtip20201228.202012280203_amd64.deb > -rw-rw-r-- 1 dunlap dunlap 56164620 2020-12-27 18:21 > linux-modules-5.10.0-051000drmtip20201228-generic_5.10.0-051000drmtip20201228.202012280203_amd64.deb > > I'll install them and try drm.debug=0x11e log_buf_len=16M in grub > > On Mon, Dec 28, 2020 at 10:55 PM koba <1899...@bugs.launchpad.net> wrote: > >> @John, if you're free, Would you please help to try drm-tip? >> You cound just download the files with "generic" and >> linux_header_***_all.deb >> https://kernel.ubuntu.com/~kernel-ppa/mainline/drm-tip/2020-12-28/ >> >> And enable drm.debug=0x11e log_buf_len=16M in grub. >> >> If the issue still exist, please upload the dmesg >> >> -- >> You received this bug notification because you are subscribed to the bug >> report. >> https://bugs.launchpad.net/bugs/1899882 >> >> Title: >> hdmi monitor on >> >> Status in linux package in Ubuntu: >> Fix Committed >> >> Bug description: >> XPS 13 9300 -- 50H3P53 -- Dell laptop >> WD19TB --- 4BWNW43 -- Dell Thunderbolt dock >> S2319HS -- B4TYZ13 -- Dell 23" external monitor >> >> External monitor remains black when waking system after suspending. >> Works OK when log out then log in or when reboot. >> Using HDMI cable from dock to monitor. >> >> From /var/log/syslog: >> >> Oct 14 21:09:41 lt9 kernel: [32059.746520] [ cut here >> ] >> Oct 14 21:09:41 lt9 kernel: [32059.746524] WARN_ON(is_mst && (port == >> PORT_A || port == PORT_E)) >> Oct 14 21:09:41 lt9 kernel: [32059.746674] WARNING: CPU: 6 PID: 1221 at >> drivers/gpu/drm/i915/display/intel_ddi.c:3179 >> intel_ddi_pre_enable_dp.isra.0+0x20f/0x430 [i915] >> Oct 14 21:09:41 lt9 kernel: [32059.746676] Modules linked in: ccm usblp >> ftdi_sio usbserial snd_usb_audio snd_usbmidi_lib rfcomm typec_displayport >> cdc_ether usbnet r8152 mii cmac algif_hash algif_skcipher af_al >> g bnep btusb btrtl btbcm btintel uvcvideo videobuf2_vmalloc >> videobuf2_memops bluetooth videobuf2_v4l2 videobuf2_common videodev mc >> ecdh_generic ecc nls_iso8859_1 snd_sof_pci snd_sof_intel_hda_common >> snd_soc_hd >> ac_hda snd_hda_codec_hdmi snd_sof_intel_hda snd_sof_intel_byt >> snd_sof_intel_ipc snd_sof snd_sof_xtensa_dsp snd_hda_ext_core >> snd_soc_acpi_intel_match snd_soc_acpi snd_soc_core snd_compress >> snd_hda_codec_realtek >>ac97_bus snd_pcm_dmaengine snd_hda_codec_generic snd_hda_intel >> mei_hdcp snd_intel_dspcfg dell_laptop snd_hda_codec joydev ledtrig_audio >> intel_rapl_msr snd_hda_core snd_hwdep x86_pkg_temp_thermal intel_powercl >> amp snd_pcm coretemp kvm_intel kvm snd_seq_midi snd_seq_midi_event >> snd_rawmidi crct10dif_pclmul ghash_clmulni_intel dell_wmi snd_seq >> aesni_intel dell_smbios crypto_simd dcdbas cryptd glue_helper rapl >> Oct 14 21:09:41 lt9 kernel: [32059.746719] intel_cstate iwlmvm >> input_leds serio_raw mac80211 snd_seq_device intel_wmi_thunderbolt wmi_bmof >> dell_wmi_descriptor snd_timer libarc4 snd hid_sensor_als hid_sensor_t >> rigger industrialio_triggered_buffer iwlwifi kfifo_buf >> hid_sensor_iio_common rtsx_pci_ms 8250_dw memstick soundcore industrialio >> ucsi_acpi processor_thermal_device intel_rapl_common mei_me typec_ucsi >> cros_ec_i >> shtp hid_multitouch mei cfg80211 cros_ec intel_soc_dts_iosf typec >> int3403_thermal mac_hid int340x_thermal_zone int3400_thermal intel_hid >> acpi_thermal_rel sparse_keymap acpi_pad acpi_tad sch_fq_codel parport_pc >>ppdev lp parport ip_tables x_tables autofs4 btrfs zstd_compress usbhid >> raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx >> xor raid6_pq libcrc32c raid1 raid0 multipath linear hid_sensor_ >> hub hid_generic intel_ishtp_loader intel_ishtp_hid rtsx_pci_sdmmc i915 >> crc32_pclmul rtsx_pci psmouse nvme i2c_algo_bit drm_kms_helper >> intel_lpss_pci i2c_i801 intel_lpss nvme_core syscopyarea idma64 >> Oct 14 21:09:41 lt9 kernel: [32059.746764] sysfillrect virt_dma >> sysimgblt fb_sys_fops intel_ish_ipc thunderbolt drm intel_ishtp wmi i2c_hid >> hid video pinctrl_icelake pinctrl_intel >> Oct 14 21:09:41 lt9 kernel:
[Bug 1626098] Re: Wrong screen capturing and flickering when using gnome-screenshot or kazam on Dell XPS 13 9350
I have the exact same problem with kazam and gnome on arch. I just switched from wayland to xorg but it jumps all over the place in the resulting video like i'm alt-tabbing constantly. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1626098 Title: Wrong screen capturing and flickering when using gnome-screenshot or kazam on Dell XPS 13 9350 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1626098/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1899882] Re: hdmi monitor on
I suppose these .deb files are the ones you'd like me to try: -rw-rw-r-- 1 dunlap dunlap 11476820 2020-12-27 18:19 linux-headers-5.10.0-051000drmtip20201228_5.10.0-051000drmtip20201228.202012280203_all.deb -rw-rw-r-- 1 dunlap dunlap 1248336 2020-12-27 18:22 linux-headers-5.10.0-051000drmtip20201228-generic_5.10.0-051000drmtip20201228.202012280203_amd64.deb -rw-rw-r-- 1 dunlap dunlap 10981324 2020-12-27 18:21 linux-image-unsigned-5.10.0-051000drmtip20201228-generic_5.10.0-051000drmtip20201228.202012280203_amd64.deb -rw-rw-r-- 1 dunlap dunlap 56164620 2020-12-27 18:21 linux-modules-5.10.0-051000drmtip20201228-generic_5.10.0-051000drmtip20201228.202012280203_amd64.deb I'll install them and try drm.debug=0x11e log_buf_len=16M in grub On Mon, Dec 28, 2020 at 10:55 PM koba <1899...@bugs.launchpad.net> wrote: > @John, if you're free, Would you please help to try drm-tip? > You cound just download the files with "generic" and > linux_header_***_all.deb > https://kernel.ubuntu.com/~kernel-ppa/mainline/drm-tip/2020-12-28/ > > And enable drm.debug=0x11e log_buf_len=16M in grub. > > If the issue still exist, please upload the dmesg > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1899882 > > Title: > hdmi monitor on > > Status in linux package in Ubuntu: > Fix Committed > > Bug description: > XPS 13 9300 -- 50H3P53 -- Dell laptop > WD19TB --- 4BWNW43 -- Dell Thunderbolt dock > S2319HS -- B4TYZ13 -- Dell 23" external monitor > > External monitor remains black when waking system after suspending. > Works OK when log out then log in or when reboot. > Using HDMI cable from dock to monitor. > > From /var/log/syslog: > > Oct 14 21:09:41 lt9 kernel: [32059.746520] [ cut here > ] > Oct 14 21:09:41 lt9 kernel: [32059.746524] WARN_ON(is_mst && (port == > PORT_A || port == PORT_E)) > Oct 14 21:09:41 lt9 kernel: [32059.746674] WARNING: CPU: 6 PID: 1221 at > drivers/gpu/drm/i915/display/intel_ddi.c:3179 > intel_ddi_pre_enable_dp.isra.0+0x20f/0x430 [i915] > Oct 14 21:09:41 lt9 kernel: [32059.746676] Modules linked in: ccm usblp > ftdi_sio usbserial snd_usb_audio snd_usbmidi_lib rfcomm typec_displayport > cdc_ether usbnet r8152 mii cmac algif_hash algif_skcipher af_al > g bnep btusb btrtl btbcm btintel uvcvideo videobuf2_vmalloc > videobuf2_memops bluetooth videobuf2_v4l2 videobuf2_common videodev mc > ecdh_generic ecc nls_iso8859_1 snd_sof_pci snd_sof_intel_hda_common > snd_soc_hd > ac_hda snd_hda_codec_hdmi snd_sof_intel_hda snd_sof_intel_byt > snd_sof_intel_ipc snd_sof snd_sof_xtensa_dsp snd_hda_ext_core > snd_soc_acpi_intel_match snd_soc_acpi snd_soc_core snd_compress > snd_hda_codec_realtek >ac97_bus snd_pcm_dmaengine snd_hda_codec_generic snd_hda_intel mei_hdcp > snd_intel_dspcfg dell_laptop snd_hda_codec joydev ledtrig_audio > intel_rapl_msr snd_hda_core snd_hwdep x86_pkg_temp_thermal intel_powercl > amp snd_pcm coretemp kvm_intel kvm snd_seq_midi snd_seq_midi_event > snd_rawmidi crct10dif_pclmul ghash_clmulni_intel dell_wmi snd_seq > aesni_intel dell_smbios crypto_simd dcdbas cryptd glue_helper rapl > Oct 14 21:09:41 lt9 kernel: [32059.746719] intel_cstate iwlmvm > input_leds serio_raw mac80211 snd_seq_device intel_wmi_thunderbolt wmi_bmof > dell_wmi_descriptor snd_timer libarc4 snd hid_sensor_als hid_sensor_t > rigger industrialio_triggered_buffer iwlwifi kfifo_buf > hid_sensor_iio_common rtsx_pci_ms 8250_dw memstick soundcore industrialio > ucsi_acpi processor_thermal_device intel_rapl_common mei_me typec_ucsi > cros_ec_i > shtp hid_multitouch mei cfg80211 cros_ec intel_soc_dts_iosf typec > int3403_thermal mac_hid int340x_thermal_zone int3400_thermal intel_hid > acpi_thermal_rel sparse_keymap acpi_pad acpi_tad sch_fq_codel parport_pc >ppdev lp parport ip_tables x_tables autofs4 btrfs zstd_compress usbhid > raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx > xor raid6_pq libcrc32c raid1 raid0 multipath linear hid_sensor_ > hub hid_generic intel_ishtp_loader intel_ishtp_hid rtsx_pci_sdmmc i915 > crc32_pclmul rtsx_pci psmouse nvme i2c_algo_bit drm_kms_helper > intel_lpss_pci i2c_i801 intel_lpss nvme_core syscopyarea idma64 > Oct 14 21:09:41 lt9 kernel: [32059.746764] sysfillrect virt_dma > sysimgblt fb_sys_fops intel_ish_ipc thunderbolt drm intel_ishtp wmi i2c_hid > hid video pinctrl_icelake pinctrl_intel > Oct 14 21:09:41 lt9 kernel: [32059.746778] CPU: 6 PID: 1221 Comm: Xorg > Tainted: GW 5.4.0-48-generic #52-Ubuntu > Oct 14 21:09:41 lt9 kernel: [32059.746780] Hardware name: Dell Inc. XPS > 13 9300/0RMFN5, BIOS 1.2.0 08/13/2020 > Oct 14 21:09:41 lt9 kernel: [32059.746843] RIP: > 0010:intel_ddi_pre_enable_dp.isra.0+0x20f/0x430 [i915] > Oct 14 21:09:41 lt9 kernel: [32059.746847] Code: ff ff 83 f8 0a bf 00 00 > 00 00 49 0f 44 fc 48 89 7d c0 e9 4b fe ff ff 48 c7 c6 e0 0a 76 c0 48 c7 c7 > 43 79 77 c0 e8 0c c5 bd db
[Bug 1909534] [NEW] package phpmyadmin 4:4.9.5+dfsg1-2 failed to install/upgrade: el subproceso instalado paquete phpmyadmin script pre-removal devolvió el código de salida de error 1
Public bug reported: me da un error relacionado con phpmyadmin. A pesar de habar reinstalado el paquete sigue saliendo el error ProblemType: Package DistroRelease: Ubuntu 20.04 Package: phpmyadmin 4:4.9.5+dfsg1-2 ProcVersionSignature: Ubuntu 5.4.0-58.64-generic 5.4.73 Uname: Linux 5.4.0-58-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.20.11-0ubuntu27.14 AptOrdering: phpmyadmin:amd64: Purge NULL: ConfigurePending NULL: PurgePending NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: skip Date: Mon Dec 28 17:27:51 2020 ErrorMessage: el subproceso instalado paquete phpmyadmin script pre-removal devolvió el código de salida de error 1 InstallationDate: Installed on 2020-12-27 (1 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) PackageArchitecture: all Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2ubuntu0.2 SourcePackage: phpmyadmin Title: package phpmyadmin 4:4.9.5+dfsg1-2 failed to install/upgrade: el subproceso instalado paquete phpmyadmin script pre-removal devolvió el código de salida de error 1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: phpmyadmin (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal third-party-packages -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1909534 Title: package phpmyadmin 4:4.9.5+dfsg1-2 failed to install/upgrade: el subproceso instalado paquete phpmyadmin script pre-removal devolvió el código de salida de error 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/phpmyadmin/+bug/1909534/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1899882] Re: hdmi monitor on
@John, if you're free, Would you please help to try drm-tip? You cound just download the files with "generic" and linux_header_***_all.deb https://kernel.ubuntu.com/~kernel-ppa/mainline/drm-tip/2020-12-28/ And enable drm.debug=0x11e log_buf_len=16M in grub. If the issue still exist, please upload the dmesg -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1899882 Title: hdmi monitor on To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1899882/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1899882] Re: hdmi monitor on
Thanks. I got -4007-oem to run. At boot it presented correctly with a login box on the external screen and the laptop screen available. However when I logged in both screens went blank for a bit after which only the laptop screen was alive but it wasn't the primary so just blank. Right clicking allowed me to get the "Display" GUI and fiddle around. After poking buttons a bit I could get the external screen to come alive but it was pretty mixed up so I have reverted to the -1008-oem. I am using xfce rather than gnome. Regards, John On Mon, Dec 28, 2020 at 9:30 PM koba <1899...@bugs.launchpad.net> wrote: > @John, thats caused by the secure-boot. > You could disable it first. > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1899882 > > Title: > hdmi monitor on > > Status in linux package in Ubuntu: > Fix Committed > > Bug description: > XPS 13 9300 -- 50H3P53 -- Dell laptop > WD19TB --- 4BWNW43 -- Dell Thunderbolt dock > S2319HS -- B4TYZ13 -- Dell 23" external monitor > > External monitor remains black when waking system after suspending. > Works OK when log out then log in or when reboot. > Using HDMI cable from dock to monitor. > > From /var/log/syslog: > > Oct 14 21:09:41 lt9 kernel: [32059.746520] [ cut here > ] > Oct 14 21:09:41 lt9 kernel: [32059.746524] WARN_ON(is_mst && (port == > PORT_A || port == PORT_E)) > Oct 14 21:09:41 lt9 kernel: [32059.746674] WARNING: CPU: 6 PID: 1221 at > drivers/gpu/drm/i915/display/intel_ddi.c:3179 > intel_ddi_pre_enable_dp.isra.0+0x20f/0x430 [i915] > Oct 14 21:09:41 lt9 kernel: [32059.746676] Modules linked in: ccm usblp > ftdi_sio usbserial snd_usb_audio snd_usbmidi_lib rfcomm typec_displayport > cdc_ether usbnet r8152 mii cmac algif_hash algif_skcipher af_al > g bnep btusb btrtl btbcm btintel uvcvideo videobuf2_vmalloc > videobuf2_memops bluetooth videobuf2_v4l2 videobuf2_common videodev mc > ecdh_generic ecc nls_iso8859_1 snd_sof_pci snd_sof_intel_hda_common > snd_soc_hd > ac_hda snd_hda_codec_hdmi snd_sof_intel_hda snd_sof_intel_byt > snd_sof_intel_ipc snd_sof snd_sof_xtensa_dsp snd_hda_ext_core > snd_soc_acpi_intel_match snd_soc_acpi snd_soc_core snd_compress > snd_hda_codec_realtek >ac97_bus snd_pcm_dmaengine snd_hda_codec_generic snd_hda_intel mei_hdcp > snd_intel_dspcfg dell_laptop snd_hda_codec joydev ledtrig_audio > intel_rapl_msr snd_hda_core snd_hwdep x86_pkg_temp_thermal intel_powercl > amp snd_pcm coretemp kvm_intel kvm snd_seq_midi snd_seq_midi_event > snd_rawmidi crct10dif_pclmul ghash_clmulni_intel dell_wmi snd_seq > aesni_intel dell_smbios crypto_simd dcdbas cryptd glue_helper rapl > Oct 14 21:09:41 lt9 kernel: [32059.746719] intel_cstate iwlmvm > input_leds serio_raw mac80211 snd_seq_device intel_wmi_thunderbolt wmi_bmof > dell_wmi_descriptor snd_timer libarc4 snd hid_sensor_als hid_sensor_t > rigger industrialio_triggered_buffer iwlwifi kfifo_buf > hid_sensor_iio_common rtsx_pci_ms 8250_dw memstick soundcore industrialio > ucsi_acpi processor_thermal_device intel_rapl_common mei_me typec_ucsi > cros_ec_i > shtp hid_multitouch mei cfg80211 cros_ec intel_soc_dts_iosf typec > int3403_thermal mac_hid int340x_thermal_zone int3400_thermal intel_hid > acpi_thermal_rel sparse_keymap acpi_pad acpi_tad sch_fq_codel parport_pc >ppdev lp parport ip_tables x_tables autofs4 btrfs zstd_compress usbhid > raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx > xor raid6_pq libcrc32c raid1 raid0 multipath linear hid_sensor_ > hub hid_generic intel_ishtp_loader intel_ishtp_hid rtsx_pci_sdmmc i915 > crc32_pclmul rtsx_pci psmouse nvme i2c_algo_bit drm_kms_helper > intel_lpss_pci i2c_i801 intel_lpss nvme_core syscopyarea idma64 > Oct 14 21:09:41 lt9 kernel: [32059.746764] sysfillrect virt_dma > sysimgblt fb_sys_fops intel_ish_ipc thunderbolt drm intel_ishtp wmi i2c_hid > hid video pinctrl_icelake pinctrl_intel > Oct 14 21:09:41 lt9 kernel: [32059.746778] CPU: 6 PID: 1221 Comm: Xorg > Tainted: GW 5.4.0-48-generic #52-Ubuntu > Oct 14 21:09:41 lt9 kernel: [32059.746780] Hardware name: Dell Inc. XPS > 13 9300/0RMFN5, BIOS 1.2.0 08/13/2020 > Oct 14 21:09:41 lt9 kernel: [32059.746843] RIP: > 0010:intel_ddi_pre_enable_dp.isra.0+0x20f/0x430 [i915] > Oct 14 21:09:41 lt9 kernel: [32059.746847] Code: ff ff 83 f8 0a bf 00 00 > 00 00 49 0f 44 fc 48 89 7d c0 e9 4b fe ff ff 48 c7 c6 e0 0a 76 c0 48 c7 c7 > 43 79 77 c0 e8 0c c5 bd db <0f> 0b e9 ae fe ff ff 41 8b 54 24 70 8b 75 a8 > 4c 89 e7 e8 8a c7 ff > Oct 14 21:09:41 lt9 kernel: [32059.746849] RSP: 0018:b3bf01253850 > EFLAGS: 00010282 > Oct 14 21:09:41 lt9 kernel: [32059.746852] RAX: RBX: > 9f1eebeca000 RCX: > Oct 14 21:09:41 lt9 kernel: [32059.746854] RDX: 0035 RSI: > 9dd955d5 RDI: 0246 > Oct 14 21:09:41 lt9 kernel: [32059.746855] RBP:
[Bug 1890540] Re: [MIR] oem-somerville-squirtle-meta
** Changed in: oem-priority Assignee: Kai-Chuan Hsieh (kchsieh) => Cyrus Lien (cyruslien) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1890540 Title: [MIR] oem-somerville-squirtle-meta To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1890540/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1909521] Re: ftrace test from ubuntu_kernel_selftests timeout on F-5.8 P8
** Also affects: ubuntu-kernel-tests Importance: Undecided Status: New ** Tags added: 5.8 kqa-blocker sru-20201130 ubuntu-kernel-selftests -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1909521 Title: ftrace test from ubuntu_kernel_selftests timeout on F-5.8 P8 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1909521/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1909521] Re: ftrace test from ubuntu_kernel_selftests timeout on F-5.8 P8
This issue can be found on 5.8.0-30.32~20.04.1 with node entei as well, and 5.8.0-25.26~20.04.1 with node modoc. But not 5.8.0-22.23~20.04.1 on modoc (in this kernel this test hang with test [60] event trigger - test inter-event histogram trigger onmatch action ) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1909521 Title: ftrace test from ubuntu_kernel_selftests timeout on F-5.8 P8 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.8/+bug/1909521/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1909521] [NEW] ftrace test from ubuntu_kernel_selftests timeout on F-5.8 P8
Public bug reported: Issue found on Focal 5.8.0-33, with P8 node dryden The ftracetest will timeout with: [17] event tracing - enable/disable with subsystem level files $ sudo ./ftracetest === Ftrace unit tests === [1] Basic trace file check [PASS] [2] Basic test for tracers [PASS] [3] Basic trace clock test [PASS] [4] Basic event tracing check [PASS] [5] Change the ringbuffer size [PASS] [6] Snapshot and tracing setting[PASS] [7] trace_pipe and trace_marker [PASS] [8] Test ftrace direct functions against tracers[UNRESOLVED] [9] Test ftrace direct functions against kprobes[UNRESOLVED] [10] Generic dynamic event - add/remove kprobe events [PASS] [11] Generic dynamic event - add/remove synthetic events[PASS] [12] Generic dynamic event - selective clear (compatibility)[PASS] [13] Generic dynamic event - generic clear event[PASS] [14] event tracing - enable/disable with event level files [PASS] [15] event tracing - restricts events based on pid notrace filtering[PASS] [16] event tracing - restricts events based on pid [PASS] [17] event tracing - enable/disable with subsystem level files (test timeout here) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.8.0-33-generic 5.8.0-33.36~20.04.1 ProcVersionSignature: User Name 5.8.0-33.36~20.04.1-generic 5.8.17 Uname: Linux 5.8.0-33-generic ppc64le .sys.firmware.opal.msglog: Error: [Errno 13] Permission denied: '/sys/firmware/opal/msglog' ApportVersion: 2.20.11-0ubuntu27.12 Architecture: ppc64el CasperMD5CheckResult: skip Date: Tue Dec 29 05:11:04 2020 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcLoadAvg: 1.19 1.24 2.68 3/1472 929062 ProcLocks: 1: POSIX ADVISORY WRITE 2447 00:19:576 0 EOF 2: POSIX ADVISORY WRITE 2720 00:19:597 0 EOF 3: FLOCK ADVISORY WRITE 2685 00:19:647 0 EOF ProcSwaps: Filename TypeSizeUsed Priority /swap.img file 8388544 0 -2 ProcVersion: Linux version 5.8.0-33-generic (buildd@bos02-ppc64el-009) (gcc (User Name 9.3.0-17ubuntu1~20.04) 9.3.0, GNU ld (GNU Binutils for User Name) 2.34) #36~20.04.1-User Name SMP Wed Dec 9 16:57:18 UTC 2020 SourcePackage: linux-signed-hwe-5.8 UpgradeStatus: No upgrade log present (probably fresh install) VarLogDump_list: total 0 cpu_cores: Number of cores present = 20 cpu_coreson: Number of cores online = 20 cpu_smt: SMT=8 ** Affects: linux-signed-hwe-5.8 (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug focal ppc64el uec-images -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1909521 Title: ftrace test from ubuntu_kernel_selftests timeout on F-5.8 P8 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.8/+bug/1909521/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1899882] Re: hdmi monitor on
@John, thats caused by the secure-boot. You could disable it first. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1899882 Title: hdmi monitor on To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1899882/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1899882] Re: hdmi monitor on
Got all five .deb files then used this command: sudo apt install ./*.deb But, when choosing the -4007-oem kernel it says the signature is wrong and quits. The -1008-oem kernel still doesn't start the external display and the dock doesn't run right away. (Ethernet doesn't work). Back to 5.6.0-1036-oem. On Mon, Dec 28, 2020 at 7:58 PM John Dunlap wrote: > Apply all 5 modules? > > On Mon, Dec 28, 2020 at 7:55 PM koba <1899...@bugs.launchpad.net> wrote: > >> it seems the patches haven't been applied. >> could you please try this? Thanks >> >> https://drive.google.com/drive/folders/1975W_7C6IJg9q_IDy08WrJYaIk_zfRp8?usp=sharing >> >> -- >> You received this bug notification because you are subscribed to the bug >> report. >> https://bugs.launchpad.net/bugs/1899882 >> >> Title: >> hdmi monitor on >> >> Status in linux package in Ubuntu: >> Fix Committed >> >> Bug description: >> XPS 13 9300 -- 50H3P53 -- Dell laptop >> WD19TB --- 4BWNW43 -- Dell Thunderbolt dock >> S2319HS -- B4TYZ13 -- Dell 23" external monitor >> >> External monitor remains black when waking system after suspending. >> Works OK when log out then log in or when reboot. >> Using HDMI cable from dock to monitor. >> >> From /var/log/syslog: >> >> Oct 14 21:09:41 lt9 kernel: [32059.746520] [ cut here >> ] >> Oct 14 21:09:41 lt9 kernel: [32059.746524] WARN_ON(is_mst && (port == >> PORT_A || port == PORT_E)) >> Oct 14 21:09:41 lt9 kernel: [32059.746674] WARNING: CPU: 6 PID: 1221 at >> drivers/gpu/drm/i915/display/intel_ddi.c:3179 >> intel_ddi_pre_enable_dp.isra.0+0x20f/0x430 [i915] >> Oct 14 21:09:41 lt9 kernel: [32059.746676] Modules linked in: ccm usblp >> ftdi_sio usbserial snd_usb_audio snd_usbmidi_lib rfcomm typec_displayport >> cdc_ether usbnet r8152 mii cmac algif_hash algif_skcipher af_al >> g bnep btusb btrtl btbcm btintel uvcvideo videobuf2_vmalloc >> videobuf2_memops bluetooth videobuf2_v4l2 videobuf2_common videodev mc >> ecdh_generic ecc nls_iso8859_1 snd_sof_pci snd_sof_intel_hda_common >> snd_soc_hd >> ac_hda snd_hda_codec_hdmi snd_sof_intel_hda snd_sof_intel_byt >> snd_sof_intel_ipc snd_sof snd_sof_xtensa_dsp snd_hda_ext_core >> snd_soc_acpi_intel_match snd_soc_acpi snd_soc_core snd_compress >> snd_hda_codec_realtek >>ac97_bus snd_pcm_dmaengine snd_hda_codec_generic snd_hda_intel >> mei_hdcp snd_intel_dspcfg dell_laptop snd_hda_codec joydev ledtrig_audio >> intel_rapl_msr snd_hda_core snd_hwdep x86_pkg_temp_thermal intel_powercl >> amp snd_pcm coretemp kvm_intel kvm snd_seq_midi snd_seq_midi_event >> snd_rawmidi crct10dif_pclmul ghash_clmulni_intel dell_wmi snd_seq >> aesni_intel dell_smbios crypto_simd dcdbas cryptd glue_helper rapl >> Oct 14 21:09:41 lt9 kernel: [32059.746719] intel_cstate iwlmvm >> input_leds serio_raw mac80211 snd_seq_device intel_wmi_thunderbolt wmi_bmof >> dell_wmi_descriptor snd_timer libarc4 snd hid_sensor_als hid_sensor_t >> rigger industrialio_triggered_buffer iwlwifi kfifo_buf >> hid_sensor_iio_common rtsx_pci_ms 8250_dw memstick soundcore industrialio >> ucsi_acpi processor_thermal_device intel_rapl_common mei_me typec_ucsi >> cros_ec_i >> shtp hid_multitouch mei cfg80211 cros_ec intel_soc_dts_iosf typec >> int3403_thermal mac_hid int340x_thermal_zone int3400_thermal intel_hid >> acpi_thermal_rel sparse_keymap acpi_pad acpi_tad sch_fq_codel parport_pc >>ppdev lp parport ip_tables x_tables autofs4 btrfs zstd_compress usbhid >> raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx >> xor raid6_pq libcrc32c raid1 raid0 multipath linear hid_sensor_ >> hub hid_generic intel_ishtp_loader intel_ishtp_hid rtsx_pci_sdmmc i915 >> crc32_pclmul rtsx_pci psmouse nvme i2c_algo_bit drm_kms_helper >> intel_lpss_pci i2c_i801 intel_lpss nvme_core syscopyarea idma64 >> Oct 14 21:09:41 lt9 kernel: [32059.746764] sysfillrect virt_dma >> sysimgblt fb_sys_fops intel_ish_ipc thunderbolt drm intel_ishtp wmi i2c_hid >> hid video pinctrl_icelake pinctrl_intel >> Oct 14 21:09:41 lt9 kernel: [32059.746778] CPU: 6 PID: 1221 Comm: Xorg >> Tainted: GW 5.4.0-48-generic #52-Ubuntu >> Oct 14 21:09:41 lt9 kernel: [32059.746780] Hardware name: Dell Inc. XPS >> 13 9300/0RMFN5, BIOS 1.2.0 08/13/2020 >> Oct 14 21:09:41 lt9 kernel: [32059.746843] RIP: >> 0010:intel_ddi_pre_enable_dp.isra.0+0x20f/0x430 [i915] >> Oct 14 21:09:41 lt9 kernel: [32059.746847] Code: ff ff 83 f8 0a bf 00 >> 00 00 00 49 0f 44 fc 48 89 7d c0 e9 4b fe ff ff 48 c7 c6 e0 0a 76 c0 48 c7 >> c7 43 79 77 c0 e8 0c c5 bd db <0f> 0b e9 ae fe ff ff 41 8b 54 24 70 8b 75 >> a8 4c 89 e7 e8 8a c7 ff >> Oct 14 21:09:41 lt9 kernel: [32059.746849] RSP: 0018:b3bf01253850 >> EFLAGS: 00010282 >> Oct 14 21:09:41 lt9 kernel: [32059.746852] RAX: RBX: >> 9f1eebeca000 RCX: >> Oct 14 21:09:41 lt9 kernel: [32059.746854] RDX: 0035 RSI: >> 9dd955d5 RDI: 0246 >> Oct 14 21:09:41 lt9 kernel:
[Bug 1909518] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 1909518 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1909518 Title: bcache register_bdev() error cannot allocate memory To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1909518/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1909518] Re: bcache register_bdev() error cannot allocate memory
Also, 18.04 ga-kernel worked fine too. ** Description changed: On 20.04(focal) ga-kernel and 18.04 (hwe-kernel). To make.bcache would fail as below if the back devices are large than 1024G ( 1025 would fail, but not 1024 ). [ 727.756453] bcache: register_bdev() error nvme12n1: cannot allocate memory [ 727.756456] bcache: register_bcache() error : failed to register device [ 727.756471] bcache: bcache_device_free() bcache device (NULL gendisk) stopped There are fix in 5.9 kernel and it can work after install 5.9 kernel on 20.04. The 5.9 kernel are download it from: https://kernel.ubuntu.com /~kernel-ppa/mainline/v5.9.16/ - The similar bug reports are + The similar bug report can be found at https://bugzilla.redhat.com/show_bug.cgi?id=1783075. - It might related to back device type. We tested on "Lenov SR665 Server" - and "Intel P4510 4.0TB U.2 NVMe SSD", the caching disk are "Intel P4800X - 375GB U.2 NVMe SSD". + It might related to back device type. it was tested on "Lenov SR665 + Server" and "Intel P4510 4.0TB U.2 NVMe SSD", the caching disk are + "Intel P4800X 375GB U.2 NVMe SSD". -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1909518 Title: bcache register_bdev() error cannot allocate memory To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1909518/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1909518] [NEW] bcache register_bdev() error cannot allocate memory
Public bug reported: On 20.04(focal) ga-kernel and 18.04 (hwe-kernel). To make.bcache would fail as below if the back devices are large than 1024G ( 1025 would fail, but not 1024 ). [ 727.756453] bcache: register_bdev() error nvme12n1: cannot allocate memory [ 727.756456] bcache: register_bcache() error : failed to register device [ 727.756471] bcache: bcache_device_free() bcache device (NULL gendisk) stopped There are fix in 5.9 kernel and it can work after install 5.9 kernel on 20.04. The 5.9 kernel are download it from: https://kernel.ubuntu.com /~kernel-ppa/mainline/v5.9.16/ The similar bug report can be found at https://bugzilla.redhat.com/show_bug.cgi?id=1783075. It might related to back device type. it was tested on "Lenov SR665 Server" and "Intel P4510 4.0TB U.2 NVMe SSD", the caching disk are "Intel P4800X 375GB U.2 NVMe SSD". ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete ** Tags: bionic focal ga-kernel hwe-kernel ** Tags added: bionic focal ga-kernel hwe-kernel ** Description changed: On 20.04(focal) ga-kernel and 18.04 (hwe-kernel). To make.bcache would - fail as below if the back devices are large than 1024G ( 102% fail, but - 1024 did not). + fail as below if the back devices are large than 1024G ( 1025 would + fail, but not 1024 ). [ 727.756453] bcache: register_bdev() error nvme12n1: cannot allocate memory [ 727.756456] bcache: register_bcache() error : failed to register device [ 727.756471] bcache: bcache_device_free() bcache device (NULL gendisk) stopped - - There are fix in 5.9 kernel and it can work after install 5.9 kernel on 20.04. The 5.9 kernel are download it from: https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.9.16/ + There are fix in 5.9 kernel and it can work after install 5.9 kernel on + 20.04. The 5.9 kernel are download it from: https://kernel.ubuntu.com + /~kernel-ppa/mainline/v5.9.16/ The similar bug reports are https://bugzilla.redhat.com/show_bug.cgi?id=1783075. It might related to back device type. We tested on "Lenov SR665 Server" and "Intel P4510 4.0TB U.2 NVMe SSD", the caching disk are "Intel P4800X 375GB U.2 NVMe SSD". -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1909518 Title: bcache register_bdev() error cannot allocate memory To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1909518/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1900361] Re: attempting to install 20.04 LTS on older PC
[Expired for ubiquity (Ubuntu) because there has been no activity for 60 days.] ** Changed in: ubiquity (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1900361 Title: attempting to install 20.04 LTS on older PC To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1900361/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1900686] Re: Missing files in tex-common caus updmap to fail
[Expired for tex-common (Ubuntu) because there has been no activity for 60 days.] ** Changed in: tex-common (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1900686 Title: Missing files in tex-common caus updmap to fail To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tex-common/+bug/1900686/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1900792] Re: Audio doesn't work on Ubuntu 20.10
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1900792 Title: Audio doesn't work on Ubuntu 20.10 To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1900792/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1901313] Re: Incorrect output when running bashtop
[Expired for bashtop (Ubuntu) because there has been no activity for 60 days.] ** Changed in: bashtop (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1901313 Title: Incorrect output when running bashtop To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bashtop/+bug/1901313/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1901440] Re: Instability in IVSHMEM after updating QEMU 4.2 -> 5.0
[Expired for qemu (Ubuntu) because there has been no activity for 60 days.] ** Changed in: qemu (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1901440 Title: Instability in IVSHMEM after updating QEMU 4.2 -> 5.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1901440/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1901889] Re: package mysql-server-8.0 8.0.22-0ubuntu0.20.04.2 failed to install/upgrade: o subprocesso instalado, do pacote mysql-server-8.0, o script post-installation retornou erro do status de
[Expired for mysql-8.0 (Ubuntu) because there has been no activity for 60 days.] ** Changed in: mysql-8.0 (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1901889 Title: package mysql-server-8.0 8.0.22-0ubuntu0.20.04.2 failed to install/upgrade: o subprocesso instalado, do pacote mysql-server-8.0, o script post-installation retornou erro do status de saída 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mysql-8.0/+bug/1901889/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1901908] Re: [20354, Conexant CX20751/2, Speaker, Internal] volume slider problem
[Expired for alsa-driver (Ubuntu) because there has been no activity for 60 days.] ** Changed in: alsa-driver (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1901908 Title: [20354, Conexant CX20751/2, Speaker, Internal] volume slider problem To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1901908/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1901954] Re: Bluetooth sound card not detected
[Expired for alsa-driver (Ubuntu) because there has been no activity for 60 days.] ** Changed in: alsa-driver (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1901954 Title: Bluetooth sound card not detected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1901954/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1901969] Re: package nginx-extras 1.18.0-6ubuntu2 failed to install/upgrade: installed nginx-extras package post-installation script subprocess returned error exit status 1
[Expired for nginx (Ubuntu) because there has been no activity for 60 days.] ** Changed in: nginx (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1901969 Title: package nginx-extras 1.18.0-6ubuntu2 failed to install/upgrade: installed nginx-extras package post-installation script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nginx/+bug/1901969/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1901956] Re: package mysql-server-8.0 8.0.22-0ubuntu0.20.04.2 failed to install/upgrade: installed mysql-server-8.0 package post-installation script subprocess returned error exit status 1
[Expired for mysql-8.0 (Ubuntu) because there has been no activity for 60 days.] ** Changed in: mysql-8.0 (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1901956 Title: package mysql-server-8.0 8.0.22-0ubuntu0.20.04.2 failed to install/upgrade: installed mysql-server-8.0 package post-installation script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mysql-8.0/+bug/1901956/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1902108] Re: [OMEN by HP Laptop, Realtek ALC295, Speaker, Internal] Pulseaudio fails to detect card
[Expired for pulseaudio (Ubuntu) because there has been no activity for 60 days.] ** Changed in: pulseaudio (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1902108 Title: [OMEN by HP Laptop, Realtek ALC295, Speaker, Internal] Pulseaudio fails to detect card To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1902108/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1902150] Re: Linux Mint Kernel No Headphone sound
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1902150 Title: Linux Mint Kernel No Headphone sound To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1902150/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1899882] Re: hdmi monitor on
Apply all 5 modules? On Mon, Dec 28, 2020 at 7:55 PM koba <1899...@bugs.launchpad.net> wrote: > it seems the patches haven't been applied. > could you please try this? Thanks > > https://drive.google.com/drive/folders/1975W_7C6IJg9q_IDy08WrJYaIk_zfRp8?usp=sharing > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1899882 > > Title: > hdmi monitor on > > Status in linux package in Ubuntu: > Fix Committed > > Bug description: > XPS 13 9300 -- 50H3P53 -- Dell laptop > WD19TB --- 4BWNW43 -- Dell Thunderbolt dock > S2319HS -- B4TYZ13 -- Dell 23" external monitor > > External monitor remains black when waking system after suspending. > Works OK when log out then log in or when reboot. > Using HDMI cable from dock to monitor. > > From /var/log/syslog: > > Oct 14 21:09:41 lt9 kernel: [32059.746520] [ cut here > ] > Oct 14 21:09:41 lt9 kernel: [32059.746524] WARN_ON(is_mst && (port == > PORT_A || port == PORT_E)) > Oct 14 21:09:41 lt9 kernel: [32059.746674] WARNING: CPU: 6 PID: 1221 at > drivers/gpu/drm/i915/display/intel_ddi.c:3179 > intel_ddi_pre_enable_dp.isra.0+0x20f/0x430 [i915] > Oct 14 21:09:41 lt9 kernel: [32059.746676] Modules linked in: ccm usblp > ftdi_sio usbserial snd_usb_audio snd_usbmidi_lib rfcomm typec_displayport > cdc_ether usbnet r8152 mii cmac algif_hash algif_skcipher af_al > g bnep btusb btrtl btbcm btintel uvcvideo videobuf2_vmalloc > videobuf2_memops bluetooth videobuf2_v4l2 videobuf2_common videodev mc > ecdh_generic ecc nls_iso8859_1 snd_sof_pci snd_sof_intel_hda_common > snd_soc_hd > ac_hda snd_hda_codec_hdmi snd_sof_intel_hda snd_sof_intel_byt > snd_sof_intel_ipc snd_sof snd_sof_xtensa_dsp snd_hda_ext_core > snd_soc_acpi_intel_match snd_soc_acpi snd_soc_core snd_compress > snd_hda_codec_realtek >ac97_bus snd_pcm_dmaengine snd_hda_codec_generic snd_hda_intel mei_hdcp > snd_intel_dspcfg dell_laptop snd_hda_codec joydev ledtrig_audio > intel_rapl_msr snd_hda_core snd_hwdep x86_pkg_temp_thermal intel_powercl > amp snd_pcm coretemp kvm_intel kvm snd_seq_midi snd_seq_midi_event > snd_rawmidi crct10dif_pclmul ghash_clmulni_intel dell_wmi snd_seq > aesni_intel dell_smbios crypto_simd dcdbas cryptd glue_helper rapl > Oct 14 21:09:41 lt9 kernel: [32059.746719] intel_cstate iwlmvm > input_leds serio_raw mac80211 snd_seq_device intel_wmi_thunderbolt wmi_bmof > dell_wmi_descriptor snd_timer libarc4 snd hid_sensor_als hid_sensor_t > rigger industrialio_triggered_buffer iwlwifi kfifo_buf > hid_sensor_iio_common rtsx_pci_ms 8250_dw memstick soundcore industrialio > ucsi_acpi processor_thermal_device intel_rapl_common mei_me typec_ucsi > cros_ec_i > shtp hid_multitouch mei cfg80211 cros_ec intel_soc_dts_iosf typec > int3403_thermal mac_hid int340x_thermal_zone int3400_thermal intel_hid > acpi_thermal_rel sparse_keymap acpi_pad acpi_tad sch_fq_codel parport_pc >ppdev lp parport ip_tables x_tables autofs4 btrfs zstd_compress usbhid > raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx > xor raid6_pq libcrc32c raid1 raid0 multipath linear hid_sensor_ > hub hid_generic intel_ishtp_loader intel_ishtp_hid rtsx_pci_sdmmc i915 > crc32_pclmul rtsx_pci psmouse nvme i2c_algo_bit drm_kms_helper > intel_lpss_pci i2c_i801 intel_lpss nvme_core syscopyarea idma64 > Oct 14 21:09:41 lt9 kernel: [32059.746764] sysfillrect virt_dma > sysimgblt fb_sys_fops intel_ish_ipc thunderbolt drm intel_ishtp wmi i2c_hid > hid video pinctrl_icelake pinctrl_intel > Oct 14 21:09:41 lt9 kernel: [32059.746778] CPU: 6 PID: 1221 Comm: Xorg > Tainted: GW 5.4.0-48-generic #52-Ubuntu > Oct 14 21:09:41 lt9 kernel: [32059.746780] Hardware name: Dell Inc. XPS > 13 9300/0RMFN5, BIOS 1.2.0 08/13/2020 > Oct 14 21:09:41 lt9 kernel: [32059.746843] RIP: > 0010:intel_ddi_pre_enable_dp.isra.0+0x20f/0x430 [i915] > Oct 14 21:09:41 lt9 kernel: [32059.746847] Code: ff ff 83 f8 0a bf 00 00 > 00 00 49 0f 44 fc 48 89 7d c0 e9 4b fe ff ff 48 c7 c6 e0 0a 76 c0 48 c7 c7 > 43 79 77 c0 e8 0c c5 bd db <0f> 0b e9 ae fe ff ff 41 8b 54 24 70 8b 75 a8 > 4c 89 e7 e8 8a c7 ff > Oct 14 21:09:41 lt9 kernel: [32059.746849] RSP: 0018:b3bf01253850 > EFLAGS: 00010282 > Oct 14 21:09:41 lt9 kernel: [32059.746852] RAX: RBX: > 9f1eebeca000 RCX: > Oct 14 21:09:41 lt9 kernel: [32059.746854] RDX: 0035 RSI: > 9dd955d5 RDI: 0246 > Oct 14 21:09:41 lt9 kernel: [32059.746855] RBP: b3bf012538a8 R08: > 9dd955a0 R09: 0035 > Oct 14 21:09:41 lt9 kernel: [32059.746857] R10: 9dd95980 R11: > 9dd9559f R12: 9f1eebeca000 > Oct 14 21:09:41 lt9 kernel: [32059.746858] R13: 9f1e1bb67000 R14: > 9f1eebb8 R15: 9f1eebeca120 > Oct 14 21:09:41 lt9 kernel: [32059.746861] FS: 7fd341ab0a80() > GS:9f1eff78() knlGS: > Oct 14
[Bug 1853277] Re: Lenovo ThinkBook 14-IML Touchpad not showing up in /proc/bus/input/devices
As commit 21653a4181ff292480599dad996a2b759ccf050f that fixes this issue has already been applied on F/G/H, I will close this bug with fix- released. Please open a new bug if you're still seeing touchpad issues. Thanks https://lists.ubuntu.com/archives/kernel-team/2020-September/113657.html ** Changed in: linux (Ubuntu Focal) Assignee: Pattapong (apattapong) => (unassigned) ** Changed in: linux (Ubuntu Focal) Assignee: (unassigned) => Kai-Heng Feng (kaihengfeng) ** Changed in: linux (Ubuntu) Status: Triaged => Fix Released ** Changed in: linux (Ubuntu Groovy) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1853277 Title: Lenovo ThinkBook 14-IML Touchpad not showing up in /proc/bus/input/devices To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1853277/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1899882] Re: hdmi monitor on
it seems the patches haven't been applied. could you please try this? Thanks https://drive.google.com/drive/folders/1975W_7C6IJg9q_IDy08WrJYaIk_zfRp8?usp=sharing -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1899882 Title: hdmi monitor on To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1899882/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Fwd: [Bug 1899882] Re: hdmi monitor on
-- Forwarded message - From: John Dunlap Date: Mon, Dec 28, 2020 at 7:34 PM Subject: Re: [Bug 1899882] Re: hdmi monitor on To: Bug 1899882 <1899...@bugs.launchpad.net> Hi Koba, I got these warnings during apt install linux-image-oem-20.04-edge: W: Possible missing firmware /lib/firmware/i915/tgl_huc_7.5.0.bin for module i915 W: Possible missing firmware /lib/firmware/i915/tgl_huc_7.5.0.bin for module i915 W: Possible missing firmware /lib/firmware/i915/tgl_dmc_ver2_08.bin for module i915 dunlap@lt9:~/Desktop$ uname -a Linux lt9 5.10.0-1008-oem #9-Ubuntu SMP Tue Dec 15 14:22:38 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux dunlap@lt9:~/Desktop$ With 5.10.0-1008-oem the external monitor does not turn on when first booted. It does turn on with 5.6.0-1036-oem but not in the configuration I had previously chosen. By fiddling with the "Display" GUI from the "Settings" menu I can finally get it turned on but that state is not maintained on boot. Also, the external display is off for perhaps 30 to 60 s after booting during which time the dock seems to be off because I finally get a notice that the Ethernet connection comes on. The dock seems to be turned off and then on during some of my interactions with the "Display" GUI. All quite slowly. I will go back to 5.6.0-1036-oem for now. Thanks for your help. Regards, John On Mon, Dec 28, 2020 at 6:15 PM koba <1899...@bugs.launchpad.net> wrote: > @John, would you please try this > #sudo apt update > #sudo apt install linux-image-oem-20.04-edge > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1899882 > > Title: > hdmi monitor on > > Status in linux package in Ubuntu: > Fix Committed > > Bug description: > XPS 13 9300 -- 50H3P53 -- Dell laptop > WD19TB --- 4BWNW43 -- Dell Thunderbolt dock > S2319HS -- B4TYZ13 -- Dell 23" external monitor > > External monitor remains black when waking system after suspending. > Works OK when log out then log in or when reboot. > Using HDMI cable from dock to monitor. > > From /var/log/syslog: > > Oct 14 21:09:41 lt9 kernel: [32059.746520] [ cut here > ] > Oct 14 21:09:41 lt9 kernel: [32059.746524] WARN_ON(is_mst && (port == > PORT_A || port == PORT_E)) > Oct 14 21:09:41 lt9 kernel: [32059.746674] WARNING: CPU: 6 PID: 1221 at > drivers/gpu/drm/i915/display/intel_ddi.c:3179 > intel_ddi_pre_enable_dp.isra.0+0x20f/0x430 [i915] > Oct 14 21:09:41 lt9 kernel: [32059.746676] Modules linked in: ccm usblp > ftdi_sio usbserial snd_usb_audio snd_usbmidi_lib rfcomm typec_displayport > cdc_ether usbnet r8152 mii cmac algif_hash algif_skcipher af_al > g bnep btusb btrtl btbcm btintel uvcvideo videobuf2_vmalloc > videobuf2_memops bluetooth videobuf2_v4l2 videobuf2_common videodev mc > ecdh_generic ecc nls_iso8859_1 snd_sof_pci snd_sof_intel_hda_common > snd_soc_hd > ac_hda snd_hda_codec_hdmi snd_sof_intel_hda snd_sof_intel_byt > snd_sof_intel_ipc snd_sof snd_sof_xtensa_dsp snd_hda_ext_core > snd_soc_acpi_intel_match snd_soc_acpi snd_soc_core snd_compress > snd_hda_codec_realtek >ac97_bus snd_pcm_dmaengine snd_hda_codec_generic snd_hda_intel mei_hdcp > snd_intel_dspcfg dell_laptop snd_hda_codec joydev ledtrig_audio > intel_rapl_msr snd_hda_core snd_hwdep x86_pkg_temp_thermal intel_powercl > amp snd_pcm coretemp kvm_intel kvm snd_seq_midi snd_seq_midi_event > snd_rawmidi crct10dif_pclmul ghash_clmulni_intel dell_wmi snd_seq > aesni_intel dell_smbios crypto_simd dcdbas cryptd glue_helper rapl > Oct 14 21:09:41 lt9 kernel: [32059.746719] intel_cstate iwlmvm > input_leds serio_raw mac80211 snd_seq_device intel_wmi_thunderbolt wmi_bmof > dell_wmi_descriptor snd_timer libarc4 snd hid_sensor_als hid_sensor_t > rigger industrialio_triggered_buffer iwlwifi kfifo_buf > hid_sensor_iio_common rtsx_pci_ms 8250_dw memstick soundcore industrialio > ucsi_acpi processor_thermal_device intel_rapl_common mei_me typec_ucsi > cros_ec_i > shtp hid_multitouch mei cfg80211 cros_ec intel_soc_dts_iosf typec > int3403_thermal mac_hid int340x_thermal_zone int3400_thermal intel_hid > acpi_thermal_rel sparse_keymap acpi_pad acpi_tad sch_fq_codel parport_pc >ppdev lp parport ip_tables x_tables autofs4 btrfs zstd_compress usbhid > raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx > xor raid6_pq libcrc32c raid1 raid0 multipath linear hid_sensor_ > hub hid_generic intel_ishtp_loader intel_ishtp_hid rtsx_pci_sdmmc i915 > crc32_pclmul rtsx_pci psmouse nvme i2c_algo_bit drm_kms_helper > intel_lpss_pci i2c_i801 intel_lpss nvme_core syscopyarea idma64 > Oct 14 21:09:41 lt9 kernel: [32059.746764] sysfillrect virt_dma > sysimgblt fb_sys_fops intel_ish_ipc thunderbolt drm intel_ishtp wmi i2c_hid > hid video pinctrl_icelake pinctrl_intel > Oct 14 21:09:41 lt9 kernel: [32059.746778] CPU: 6 PID: 1221 Comm: Xorg > Tainted: GW 5.4.0-48-generic #52-Ubuntu > Oct 14 21:09:41
Re: [Bug 1899882] Re: hdmi monitor on
Hi Koba, I got these warnings during apt install linux-image-oem-20.04-edge: W: Possible missing firmware /lib/firmware/i915/tgl_huc_7.5.0.bin for module i915 W: Possible missing firmware /lib/firmware/i915/tgl_huc_7.5.0.bin for module i915 W: Possible missing firmware /lib/firmware/i915/tgl_dmc_ver2_08.bin for module i915 dunlap@lt9:~/Desktop$ uname -a Linux lt9 5.10.0-1008-oem #9-Ubuntu SMP Tue Dec 15 14:22:38 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux dunlap@lt9:~/Desktop$ With 5.10.0-1008-oem the external monitor does not turn on when first booted. It does turn on with 5.6.0-1036-oem but not in the configuration I had previously chosen. By fiddling with the "Display" GUI from the "Settings" menu I can finally get it turned on but that state is not maintained on boot. Also, the external display is off for perhaps 30 to 60 s after booting during which time the dock seems to be off because I finally get a notice that the Ethernet connection comes on. The dock seems to be turned off and then on during some of my interactions with the "Display" GUI. All quite slowly. I will go back to 5.6.0-1036-oem for now. Thanks for your help. Regards, John On Mon, Dec 28, 2020 at 6:15 PM koba <1899...@bugs.launchpad.net> wrote: > @John, would you please try this > #sudo apt update > #sudo apt install linux-image-oem-20.04-edge > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1899882 > > Title: > hdmi monitor on > > Status in linux package in Ubuntu: > Fix Committed > > Bug description: > XPS 13 9300 -- 50H3P53 -- Dell laptop > WD19TB --- 4BWNW43 -- Dell Thunderbolt dock > S2319HS -- B4TYZ13 -- Dell 23" external monitor > > External monitor remains black when waking system after suspending. > Works OK when log out then log in or when reboot. > Using HDMI cable from dock to monitor. > > From /var/log/syslog: > > Oct 14 21:09:41 lt9 kernel: [32059.746520] [ cut here > ] > Oct 14 21:09:41 lt9 kernel: [32059.746524] WARN_ON(is_mst && (port == > PORT_A || port == PORT_E)) > Oct 14 21:09:41 lt9 kernel: [32059.746674] WARNING: CPU: 6 PID: 1221 at > drivers/gpu/drm/i915/display/intel_ddi.c:3179 > intel_ddi_pre_enable_dp.isra.0+0x20f/0x430 [i915] > Oct 14 21:09:41 lt9 kernel: [32059.746676] Modules linked in: ccm usblp > ftdi_sio usbserial snd_usb_audio snd_usbmidi_lib rfcomm typec_displayport > cdc_ether usbnet r8152 mii cmac algif_hash algif_skcipher af_al > g bnep btusb btrtl btbcm btintel uvcvideo videobuf2_vmalloc > videobuf2_memops bluetooth videobuf2_v4l2 videobuf2_common videodev mc > ecdh_generic ecc nls_iso8859_1 snd_sof_pci snd_sof_intel_hda_common > snd_soc_hd > ac_hda snd_hda_codec_hdmi snd_sof_intel_hda snd_sof_intel_byt > snd_sof_intel_ipc snd_sof snd_sof_xtensa_dsp snd_hda_ext_core > snd_soc_acpi_intel_match snd_soc_acpi snd_soc_core snd_compress > snd_hda_codec_realtek >ac97_bus snd_pcm_dmaengine snd_hda_codec_generic snd_hda_intel mei_hdcp > snd_intel_dspcfg dell_laptop snd_hda_codec joydev ledtrig_audio > intel_rapl_msr snd_hda_core snd_hwdep x86_pkg_temp_thermal intel_powercl > amp snd_pcm coretemp kvm_intel kvm snd_seq_midi snd_seq_midi_event > snd_rawmidi crct10dif_pclmul ghash_clmulni_intel dell_wmi snd_seq > aesni_intel dell_smbios crypto_simd dcdbas cryptd glue_helper rapl > Oct 14 21:09:41 lt9 kernel: [32059.746719] intel_cstate iwlmvm > input_leds serio_raw mac80211 snd_seq_device intel_wmi_thunderbolt wmi_bmof > dell_wmi_descriptor snd_timer libarc4 snd hid_sensor_als hid_sensor_t > rigger industrialio_triggered_buffer iwlwifi kfifo_buf > hid_sensor_iio_common rtsx_pci_ms 8250_dw memstick soundcore industrialio > ucsi_acpi processor_thermal_device intel_rapl_common mei_me typec_ucsi > cros_ec_i > shtp hid_multitouch mei cfg80211 cros_ec intel_soc_dts_iosf typec > int3403_thermal mac_hid int340x_thermal_zone int3400_thermal intel_hid > acpi_thermal_rel sparse_keymap acpi_pad acpi_tad sch_fq_codel parport_pc >ppdev lp parport ip_tables x_tables autofs4 btrfs zstd_compress usbhid > raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx > xor raid6_pq libcrc32c raid1 raid0 multipath linear hid_sensor_ > hub hid_generic intel_ishtp_loader intel_ishtp_hid rtsx_pci_sdmmc i915 > crc32_pclmul rtsx_pci psmouse nvme i2c_algo_bit drm_kms_helper > intel_lpss_pci i2c_i801 intel_lpss nvme_core syscopyarea idma64 > Oct 14 21:09:41 lt9 kernel: [32059.746764] sysfillrect virt_dma > sysimgblt fb_sys_fops intel_ish_ipc thunderbolt drm intel_ishtp wmi i2c_hid > hid video pinctrl_icelake pinctrl_intel > Oct 14 21:09:41 lt9 kernel: [32059.746778] CPU: 6 PID: 1221 Comm: Xorg > Tainted: GW 5.4.0-48-generic #52-Ubuntu > Oct 14 21:09:41 lt9 kernel: [32059.746780] Hardware name: Dell Inc. XPS > 13 9300/0RMFN5, BIOS 1.2.0 08/13/2020 > Oct 14 21:09:41 lt9 kernel: [32059.746843] RIP: >
[Bug 1891721] Re: grub-multi-install attempts to mount a non-existing device after migrating to another system
Interestingly, this issue keeps coming back. Seems that each consecutive update of grub-efi is suffering from it. Each time it happens, the same apt purge helps. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1891721 Title: grub-multi-install attempts to mount a non-existing device after migrating to another system To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1891721/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1899882] Re: hdmi monitor on
@John, would you please try this #sudo apt update #sudo apt install linux-image-oem-20.04-edge -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1899882 Title: hdmi monitor on To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1899882/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1906155] Re: USB Passthrough Fails on Start, Needs domain Reset
FYI, several updates here - for other reasons, but ... BIOS, Linux (Ubuntu), qemu (to master) => now it works on boot. Arrgh! I only say that because I can't duplicate it any more, with all these updates. That's good overall. LOL! Thanks! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1906155 Title: USB Passthrough Fails on Start, Needs domain Reset To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1906155/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1909499] Re: iwlwifi 0000:03:00.0: No beacon heard and the time event is over already...
Would you please try this? #sudo apt update #sudo apt install linux-image-oem-20.04-edge -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1909499 Title: iwlwifi :03:00.0: No beacon heard and the time event is over already... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1909499/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1909506] Re: lubuntu hirsute daily install failed - error message to large for screen
** Description changed: in exploration of EFI issue & theory.. a series of repeated installs was performed. this one failed I believe b/c of random circumstances (mirror sync or packages changing on mirror) thus it's of no value & just bad luck... HOWEVER the calamares error messages didn't fit on display, thus no accept buttons and machine became stopped until ENTER was pressed (using the - button that was off-screen and un-clickable with mouse). photos were - taken, and I'll amend this report shortly with more detail + button that was off-screen and un-clickable with mouse). Photo - https://photos.app.goo.gl/HGWiX8UAPaBjXwZx7 - displays are 1280x1024, right is portrait (tilted-left) + displays are 1280x1024, right is portrait (tilted-left) ; though + portrait display may be detected smaller (1024x768 maybe) the error message may not have been photographed in its position as I dragged it around to try and view accept button at bottom (which may have been before photo was taken).. issue is because of small screen size; occurring only today b/c of bad luck (3 ~identical installs, only 1 had this issue) - ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: calamares 3.2.35-0ubuntu2 ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14 Uname: Linux 5.8.0-25-generic x86_64 .etc.calamares.modules.finished.conf: --- restartNowMode: user-checked restartNowCommand: "systemctl -i reboot" .etc.calamares.modules.partition.conf: efiSystemPartition: "/boot/efi" enableLuksAutomatedPartitioning: true userSwapChoices: none drawNestedPartitions: true defaultFileSystemType: "ext4" .etc.calamares.modules.shellprocess_logs.conf: --- dontChroot: true timeout: 30 script: - calamares-logs-helper @@ROOT@@ .etc.calamares.modules.unpackfs.conf: --- unpack: - source: "/cdrom/casper/filesystem.squashfs" sourcefs: "squashfs" destination: "" ApportVersion: 2.20.11-0ubuntu55 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.456 CurrentDesktop: LXQt Date: Tue Dec 29 12:15:20 2020 LiveMediaBuild: Lubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20201228) RelatedPackageVersions: calamares-settings-ubuntu-common 1:20.10.11 calamares-settings-lubuntu 1:20.10.11 xfsprogs 5.6.0-1ubuntu4 btrfs-progs 5.9-1build1 SourcePackage: calamares UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1909506 Title: lubuntu hirsute daily install failed - error message to large for screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/calamares/+bug/1909506/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1905947] Re: lubuntu hirsute: display configuration doesn't survive logout/reboot
hirsute test install on - dell [optiplex] 755 (c2d-e8300, 8gb, amd/ati radeon rv610/radeon hd2400 pro/xt) prior to logout, and as part of my usual shakedown of system, I adjust monitor.settings to match my setup (landscape + portrait.left) which is applied & saved. on logout & login again, screen setup was back to defaults... not reported in QA-test as it's not part of the install test. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1905947 Title: lubuntu hirsute: display configuration doesn't survive logout/reboot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxqt-config/+bug/1905947/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1909506] Re: lubuntu hirsute daily install failed - error message to large for screen
This bug has been reported on the Ubuntu ISO testing tracker. A list of all reports related to this bug can be found here: http://iso.qa.ubuntu.com/qatracker/reports/bugs/1909506 ** Tags added: iso-testing -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1909506 Title: lubuntu hirsute daily install failed - error message to large for screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/calamares/+bug/1909506/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1904974] Re: calamares selected wrong timezone
Three ~identical QA-test installs on same box today with same type of install (replace partition) exploration of different issue - dell [optiplex] 755 (c2d-e8300, 8gb, amd/ati radeon rv610/radeon hd2400 pro/xt) Locations reported by Calamares during each installs - Sydney AU - Melbourne AU - Sydney AU Both are in same time zone, internet the same on each, and my main box hasn't shown any disconnections to freenode (ie. my dynamic IP address hasn't changed). Max 5 mins between each install (time required to close up QA-test on iso.qa.ubuntu.com & document findings on featherpad on unrelated reason for these installs) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1904974 Title: calamares selected wrong timezone To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/calamares/+bug/1904974/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1909506] Re: lubuntu hirsute daily install failed (two issues)
I believe I've filed this issue before, and expected to find and mark this a duplicate, but currently I've failed to find it (maybe a release that is now EOL?) ** Description changed: in exploration of EFI issue & theory.. a series of repeated installs was performed. this one failed I believe b/c of random circumstances (mirror sync or packages changing on mirror) thus it's of no value & just bad luck... HOWEVER the calamares error messages didn't fit on display, thus no accept buttons and machine became stopped until ENTER was pressed (using the button that was off-screen and un-clickable with mouse). photos were taken, and I'll amend this report shortly with more detail + Photo - https://photos.app.goo.gl/HGWiX8UAPaBjXwZx7 + + displays are 1280x1024, right is portrait (tilted-left) + + the error message may not have been photographed in its position as I + dragged it around to try and view accept button at bottom (which may + have been before photo was taken).. + + issue is because of small screen size; occurring only today b/c of bad + luck (3 ~identical installs, only 1 had this issue) + + ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: calamares 3.2.35-0ubuntu2 ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14 Uname: Linux 5.8.0-25-generic x86_64 .etc.calamares.modules.finished.conf: - --- - restartNowMode: user-checked - restartNowCommand: "systemctl -i reboot" + --- + restartNowMode: user-checked + restartNowCommand: "systemctl -i reboot" .etc.calamares.modules.partition.conf: - efiSystemPartition: "/boot/efi" - enableLuksAutomatedPartitioning: true - userSwapChoices: none - drawNestedPartitions: true - defaultFileSystemType: "ext4" + efiSystemPartition: "/boot/efi" + enableLuksAutomatedPartitioning: true + userSwapChoices: none + drawNestedPartitions: true + defaultFileSystemType: "ext4" .etc.calamares.modules.shellprocess_logs.conf: - --- - dontChroot: true - timeout: 30 - script: - - calamares-logs-helper @@ROOT@@ + --- + dontChroot: true + timeout: 30 + script: + - calamares-logs-helper @@ROOT@@ .etc.calamares.modules.unpackfs.conf: - --- - unpack: - - source: "/cdrom/casper/filesystem.squashfs" - sourcefs: "squashfs" - destination: "" + --- + unpack: + - source: "/cdrom/casper/filesystem.squashfs" + sourcefs: "squashfs" + destination: "" ApportVersion: 2.20.11-0ubuntu55 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.456 CurrentDesktop: LXQt Date: Tue Dec 29 12:15:20 2020 LiveMediaBuild: Lubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20201228) RelatedPackageVersions: - calamares-settings-ubuntu-common 1:20.10.11 - calamares-settings-lubuntu 1:20.10.11 - xfsprogs 5.6.0-1ubuntu4 - btrfs-progs 5.9-1build1 + calamares-settings-ubuntu-common 1:20.10.11 + calamares-settings-lubuntu 1:20.10.11 + xfsprogs 5.6.0-1ubuntu4 + btrfs-progs 5.9-1build1 SourcePackage: calamares UpgradeStatus: No upgrade log present (probably fresh install) ** Summary changed: - lubuntu hirsute daily install failed (two issues) + lubuntu hirsute daily install failed - error message to large for screen ** Changed in: calamares (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/1909506 Title: lubuntu hirsute daily install failed - error message to large for screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/calamares/+bug/1909506/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1909506] [NEW] lubuntu hirsute daily install failed (two issues)
Public bug reported: in exploration of EFI issue & theory.. a series of repeated installs was performed. this one failed I believe b/c of random circumstances (mirror sync or packages changing on mirror) thus it's of no value & just bad luck... HOWEVER the calamares error messages didn't fit on display, thus no accept buttons and machine became stopped until ENTER was pressed (using the button that was off-screen and un-clickable with mouse). photos were taken, and I'll amend this report shortly with more detail ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: calamares 3.2.35-0ubuntu2 ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14 Uname: Linux 5.8.0-25-generic x86_64 .etc.calamares.modules.finished.conf: --- restartNowMode: user-checked restartNowCommand: "systemctl -i reboot" .etc.calamares.modules.partition.conf: efiSystemPartition: "/boot/efi" enableLuksAutomatedPartitioning: true userSwapChoices: none drawNestedPartitions: true defaultFileSystemType: "ext4" .etc.calamares.modules.shellprocess_logs.conf: --- dontChroot: true timeout: 30 script: - calamares-logs-helper @@ROOT@@ .etc.calamares.modules.unpackfs.conf: --- unpack: - source: "/cdrom/casper/filesystem.squashfs" sourcefs: "squashfs" destination: "" ApportVersion: 2.20.11-0ubuntu55 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.456 CurrentDesktop: LXQt Date: Tue Dec 29 12:15:20 2020 LiveMediaBuild: Lubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20201228) RelatedPackageVersions: calamares-settings-ubuntu-common 1:20.10.11 calamares-settings-lubuntu 1:20.10.11 xfsprogs 5.6.0-1ubuntu4 btrfs-progs 5.9-1build1 SourcePackage: calamares UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: calamares (Ubuntu) Importance: Undecided Status: Incomplete ** Tags: amd64 apport-bug hirsute ** Changed in: calamares (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1909506 Title: lubuntu hirsute daily install failed (two issues) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/calamares/+bug/1909506/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1909505] [NEW] MT940 import does not work
Public bug reported: After upgrading to 20.04.1 LTS the MT940 import fails to open the import dialog. It fails silently. - Ubuntu 20.04.1 - GnuCash 1:3.8b-1ubuntu1 File->Import->MT940 - Dialog opens - I can select a downloaded .940 file Expected behaviour: Import Matcher window opens Experienced behaviour: File dialog just closes I tried to run with --extra CLI option for extra info, but it fails silently. Thanks in advance for your efforts. Cheers, Willem Voogd ** Affects: gnucash (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/1909505 Title: MT940 import does not work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnucash/+bug/1909505/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1878279] Re: MSFT0004:00 06CB:CD98 Touchpad/trackpad mouse randomly not recognized from any given boot
Hi, "i8042.nopnp=1 pci=nocrs" also works with Lenovo V17-IIL. Thanks -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1878279 Title: MSFT0004:00 06CB:CD98 Touchpad/trackpad mouse randomly not recognized from any given boot To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1878279/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1907870] Re: Intel UHD Graphics: external monitor detected but black screen (has a preferred mode but no current mode set)
Hi! I have updates on this: ¡IT WAS A CABLE PROBLEM! Same cable and same monitor that works OK with my HP OMEN 15 doesn't work with my HP 440 G7... I tried with a different cable (a shorter one) and everything looks normal. Please, mark this as closed. Thanks everyone for the help, HAPPY 2021. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1907870 Title: Intel UHD Graphics: external monitor detected but black screen (has a preferred mode but no current mode set) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1907870/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1909480] Re: ubuntu installer wont probe block devices if invoked via ssh
** Description changed: - While groping for a workaround to bug #1909478 i tried logging into the - ubiquity installer via ssh. This looks like a very nice feature, but - unfortunately, when logged in thusly via ssh, the installer says "Guided - storage configuration...Block probing did not discover any disks. - Unfortunately this means that installation will not be possible." + While groping for a workaround to bug #1909478 i tried setting the + password on the 'installer' account and logging in via ssh, whereupon + the installer works via ssh. This looks to be a very nice feature, but, + sadly, when logged in thusly via ssh, the installer oddly fails to probe + the discs, saying "Guided storage configuration...Block probing did not + discover any disks. Unfortunately this means that installation will not + be possible." ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubiquity (not installed) 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: pass CasperVersion: 1.445.1 Date: Mon Dec 28 06:35:11 2020 InstallCmdLine: BOOT_IMAGE=(i)/casper/vmlinuz iso-scan/filename=/home/greg/ubuntu-20.04.1-live-server-amd64.iso boot=casper panic=30 toram -- LiveMediaBuild: Ubuntu-Server 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) ProcEnviron: - TERM=screen - PATH=(custom, no user) - LANG=C.UTF-8 - SHELL=/bin/bash + TERM=screen + PATH=(custom, no user) + LANG=C.UTF-8 + SHELL=/bin/bash SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1909480 Title: ubuntu installer wont probe block devices if invoked via ssh To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1909480/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1838151] Re: Poor quality audio with modern Bluetooth headsets in HSP/HFP. Missing wide band speech support (Bluetooth A2DP codecs).
I installed pulseaudio-modules-bt and it does give some new options for sound output and possibly better sound, but microphone sound quality was still iffy. Recorded sound on Audacity seemed better and was slightly louder (according to the DB meter), but a test call on Microsoft Teams was still muffled and unintelligible. I have ordered a Avantree DG80 dongle (which makes the bluetooth connection externally and appears to linux as usb audio) and will hopefully be able to continue working with that, but I would love to see this problem resolved in pulseaudio. For the record, I am using a Sony WH-1000XM4 headset on PopOS 20.10 running on a System76 Darter Pro. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1838151 Title: Poor quality audio with modern Bluetooth headsets in HSP/HFP. Missing wide band speech support (Bluetooth A2DP codecs). To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1838151/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1884295] Re: AttributeError: 'QWebEngineProfile' object has no attribute 'setUrlRequestInterceptor'
** Description changed: Trying to convert a book to pdf with calibre 4.99.4 results in error: ebook-convert TMcGrath-Clean\ Code\ Summary_Agile\ Software\ Craftmanship\ Guidelines-Developer\ Deconstructed\ \(2016\).azw3 TMcGrath-Clean\ Code\ Summary_Agile\ Software\ Craftmanship\ Guidelines-Developer\ Deconstructed\ \(2016\).pdf 1% Converting input to HTML... InputFormatPlugin: MOBI Input running - on /home/gmuller/Downloads/TOPRINT/TMcGrath-Clean Code Summary_Agile Software Craftmanship Guidelines-Developer Deconstructed (2016).azw3 + on /home/user/Downloads/TOPRINT/TMcGrath-Clean Code Summary_Agile Software Craftmanship Guidelines-Developer Deconstructed (2016).azw3 Found KF8 MOBI of type 'standalone' Parsing all content... 34% Running transforms on e-book... Merging user specified metadata... Detecting structure... Flattening CSS and remapping font sizes... Source base font size is 11.95425pt Removing fake margins... Cleaning up manifest... Trimming unused files from manifest... Trimming 'images/3.jpeg' from manifest Creating PDF Output... 67% Running PDF Output plugin The cover image has an id != "cover". Renaming to work around bug in Nook Color 68% Parsed all content for markup transformation Link anchor: text/part.html#1-f22ab0014c924831a14cdb6c59d26a4e not found, linking to top of file instead Link anchor: text/part0001.html#UGI1-f22ab0014c924831a14cdb6c59d26a4e not found, linking to top of file instead Link anchor: text/part0002.html#1T141-f22ab0014c924831a14cdb6c59d26a4e not found, linking to top of file instead Link anchor: text/part0003.html#2RHM1-f22ab0014c924831a14cdb6c59d26a4e not found, linking to top of file instead Link anchor: text/part0004.html#3Q281-f22ab0014c924831a14cdb6c59d26a4e not found, linking to top of file instead Link anchor: text/part0005.html#4OIQ1-f22ab0014c924831a14cdb6c59d26a4e not found, linking to top of file instead Link anchor: text/part0006.html#5N3C1-f22ab0014c924831a14cdb6c59d26a4e not found, linking to top of file instead Link anchor: text/part0007.html#6LJU1-f22ab0014c924831a14cdb6c59d26a4e not found, linking to top of file instead Link anchor: text/part0008.html#7K4G1-f22ab0014c924831a14cdb6c59d26a4e not found, linking to top of file instead Link anchor: text/part0009.html#8IL21-f22ab0014c924831a14cdb6c59d26a4e not found, linking to top of file instead Link anchor: text/part0010.html#9H5K1-f22ab0014c924831a14cdb6c59d26a4e not found, linking to top of file instead Link anchor: text/part0011.html#AFM61-f22ab0014c924831a14cdb6c59d26a4e not found, linking to top of file instead Link anchor: text/part0012.html#BE6O1-f22ab0014c924831a14cdb6c59d26a4e not found, linking to top of file instead Link anchor: text/part0013.html#CCNA1-f22ab0014c924831a14cdb6c59d26a4e not found, linking to top of file instead Link anchor: text/part0014.html#DB7S1-f22ab0014c924831a14cdb6c59d26a4e not found, linking to top of file instead Link anchor: text/part0015.html#E9OE1-f22ab0014c924831a14cdb6c59d26a4e not found, linking to top of file instead Link anchor: text/part0016.html#F8901-f22ab0014c924831a14cdb6c59d26a4e not found, linking to top of file instead Link anchor: text/part0017.html#G6PI1-f22ab0014c924831a14cdb6c59d26a4e not found, linking to top of file instead Link anchor: text/part0018.html#H5A41-f22ab0014c924831a14cdb6c59d26a4e not found, linking to top of file instead Link anchor: text/part0019.html#I3QM2-f22ab0014c924831a14cdb6c59d26a4e not found, linking to top of file instead Link anchor: text/part0020.html#J2B81-f22ab0014c924831a14cdb6c59d26a4e not found, linking to top of file instead 70% Completed markup transformation WebEngineContext used before QtWebEngine::initialize() or OpenGL context creation failed. Traceback (most recent call last): - File "/usr/bin/ebook-convert", line 20, in - sys.exit(main()) - File "/usr/lib/calibre/calibre/ebooks/conversion/cli.py", line 401, in main - plumber.run() - File "/usr/lib/calibre/calibre/ebooks/conversion/plumber.py", line 1274, in run - self.output_plugin.convert(self.oeb, self.output, self.input_plugin, - File "/usr/lib/calibre/calibre/ebooks/conversion/plugins/pdf_output.py", line 188, in convert - self.convert_text(oeb_book) - File "/usr/lib/calibre/calibre/ebooks/conversion/plugins/pdf_output.py", line 253, in convert_text - convert( - File "/usr/lib/calibre/calibre/ebooks/pdf/html_writer.py", line 1195, in convert - manager = RenderManager(opts, log, container.root) - File "/usr/lib/calibre/calibre/ebooks/pdf/html_writer.py", line 279, in __init__ - ans.setUrlRequestInterceptor(self.interceptor) + File "/usr/bin/ebook-convert", line 20, in + sys.exit(main()) + File "/usr/lib/calibre/calibre/ebooks/conversion/cli.py", line 401, in main + plumber.run() + File "/usr/lib/calibre/calibre/ebooks/conversion/plumber.py", line 1274, in run +
[Bug 1909494] Re: wpa_supplicant and iwlwifi failing with "No buffer space available" since "kernel 5.4.0-56"
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: wpasupplicant (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1909494 Title: wpa_supplicant and iwlwifi failing with "No buffer space available" since "kernel 5.4.0-56" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/backport-iwlwifi-dkms/+bug/1909494/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1909494] Re: wpa_supplicant and iwlwifi failing with "No buffer space available" since "kernel 5.4.0-56"
** Package changed: ubuntu => backport-iwlwifi-dkms (Ubuntu) ** Also affects: wpasupplicant (Ubuntu) Importance: Undecided Status: New ** Description changed: There are reproduce-able WiFi aborts with 20.04.1 LTS since update to kernel 5.4.0-56. Behaviour: nm-applet shows a window to enter the WLAN key that is pre- filled. Hitting the "Connect" button reconnects the WiFi network for a small period. The error occurs sometimes very often (e.g. 10 times/minute) or seldom (only one per day). You can see it in /var/log/syslog at the entry >>> wpa_supplicant[xxx]: l2_packet_send - sendto: No buffer space available - As a result 4-Way-Handshake fails and after disconnection the new (old) key is requestet. + As a result 4-Way-Handshake fails and after disconnection the new (old) key is requested. >>> wpa_supplicant[xxx]: wlp3s0: WPA: 4-Way Handshake failed - pre-shared key may be incorrect >>> NetworkManager[xxx]: [xxx] device (wlp3s0): Activation: (wifi) disconnected during association, asking for new key There are a lot of people having this problem (see discussion in german moderated forum: >>> https://forum.ubuntuusers.de/topic/funknetz-schluessel-werden-staendig-abgefragt See also BUG #1908823 and question #694566 >>> https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/1908823 >>> https://answers.launchpad.net/ubuntu/+question/694566 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1909494 Title: wpa_supplicant and iwlwifi failing with "No buffer space available" since "kernel 5.4.0-56" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/backport-iwlwifi-dkms/+bug/1909494/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1899882] Re: hdmi monitor on
Symptoms still basically the same with more recent bios & kernel. -- John XPS 13 9300 -- 50H3P53 -- laptop WD19TB --- 4BWNW43 -- Thunderbolt dock S2319HS -- B4TYZ13 -- 23" monitor using DisplayPort cable uname -a: Linux lt9 5.6.0-1036-oem #39-Ubuntu SMP Wed Dec 2 08:54:16 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux bios: XPS_13_9300_1.4.1.exe -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1899882 Title: hdmi monitor on To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1899882/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 972077] Re: apt repository disk format has race conditions
I'm also affected by this issue -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/972077 Title: apt repository disk format has race conditions To manage notifications about this bug go to: https://bugs.launchpad.net/apt/+bug/972077/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1909502] [NEW] FUSE fails to unmount without privilege in kernel v5.9+
Public bug reported: In kernel v5.9+ there was a refactor to the unmount code path that results in libfuse no longer being able to detect UMOUNT_NOFOLLOW. This resulted in an alternate code path that relied on being able to call unshare and some other work. The patch that caused the bug upstream: https://lore.kernel.org/linux-fsdevel/20200726071356.287160-3-...@lst.de/ The fix upstream (not in tree): https://lore.kernel.org/linux-fsdevel/20201223102604.2078-1-sar...@sargun.me/ The fix in libfuse: https://github.com/libfuse/libfuse/commit/b96e4758041ffac1b8d8c39f4897edd6182a46e9 ** Affects: fuse (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/1909502 Title: FUSE fails to unmount without privilege in kernel v5.9+ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fuse/+bug/1909502/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1909494] Re: wpa_supplicant and iwlwifi failing with "No buffer space available" since "kernel 5.4.0-56"
Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general. It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it. You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage. You might also ask for help in the #ubuntu-bugs irc channel on Freenode. To change the source package that this bug is filed about visit https://bugs.launchpad.net/ubuntu/+bug/1909494/+editstatus and add the package name in the text box next to the word Package. [This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.] ** Tags added: bot-comment -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1909494 Title: wpa_supplicant and iwlwifi failing with "No buffer space available" since "kernel 5.4.0-56" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1909494/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1908335] Re: [SRU][F/G/H/U/OEM-5.6] Fix i2c report error on elan trackpoint
I installed the kernel in -proposed and I still get these errors and non-functional trackpoint. System is a Lenovo L13. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1908335 Title: [SRU][F/G/H/U/OEM-5.6] Fix i2c report error on elan trackpoint To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1908335/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1909496] Re: Blinking login screen
** Package changed: ubuntu => xorg (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1909496 Title: Blinking login screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1909496/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1908335] Re: [SRU][F/G/H/U/OEM-5.6] Fix i2c report error on elan trackpoint
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: linux-oem-5.10 (Ubuntu Groovy) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1908335 Title: [SRU][F/G/H/U/OEM-5.6] Fix i2c report error on elan trackpoint To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1908335/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1908335] Re: [SRU][F/G/H/U/OEM-5.6] Fix i2c report error on elan trackpoint
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: linux-oem-5.10 (Ubuntu Focal) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1908335 Title: [SRU][F/G/H/U/OEM-5.6] Fix i2c report error on elan trackpoint To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1908335/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1908335] Re: [SRU][F/G/H/U/OEM-5.6] Fix i2c report error on elan trackpoint
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: linux-oem-5.10 (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1908335 Title: [SRU][F/G/H/U/OEM-5.6] Fix i2c report error on elan trackpoint To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1908335/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1909500] [NEW] Upgrading 18.04 to 20.04
Public bug reported: Upgrader claims launchpad PPAs are holding up upgrade, but I have purged these. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ubuntu-release-upgrader-core 1:18.04.41 ProcVersionSignature: Ubuntu 4.15.0-128.131-generic 4.15.18 Uname: Linux 4.15.0-128-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.9-0ubuntu7.21 Architecture: amd64 CrashDB: ubuntu Date: Mon Dec 28 19:55:25 2020 InstallationDate: Installed on 2014-07-21 (2351 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) PackageArchitecture: all ProcEnviron: LANGUAGE=en_GB:en TERM=xterm-256color PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-release-upgrader UpgradeStatus: Upgraded to bionic on 2020-12-28 (0 days ago) VarLogDistupgradeTermlog: ** Affects: ubuntu-release-upgrader (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic dist-upgrade third-party-packages -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1909500 Title: Upgrading 18.04 to 20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1909500/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1909494] Re: wpa_supplicant and iwlwifi failing with "No buffer space available" since "kernel 5.4.0-56"
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: ubuntu Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1909494 Title: wpa_supplicant and iwlwifi failing with "No buffer space available" since "kernel 5.4.0-56" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1909494/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1909499] [NEW] iwlwifi 0000:03:00.0: No beacon heard and the time event is over already...
Public bug reported: I see this error frequently inside logs: iwlwifi :03:00.0: No beacon heard and the time event is over already... Also, the internet doesn't seem stable, from time to time it disconnects and reconnects on its own, and other times it disconnects and wants me to enter the key again to connect. However, if i hit the X button to close the password modal and try to connect again from the networks list, it does connect without the need to enter the password. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-firmware 1.187.6 ProcVersionSignature: Ubuntu 5.4.0-58.64-lowlatency 5.4.73 Uname: Linux 5.4.0-58-lowlatency x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lyubo 14448 F pulseaudio /dev/snd/pcmC0D0p: lyubo 14448 F...m pulseaudio CasperMD5CheckResult: skip Date: Mon Dec 28 21:50:51 2020 Dependencies: InstallationDate: Installed on 2020-12-27 (0 days ago) InstallationMedia: Kubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 04f2:b5f7 Chicony Electronics Co., Ltd HD WebCam Bus 001 Device 003: ID 8087:0aa7 Intel Corp. Bus 001 Device 002: ID 275d:0ba6 USB OPTICAL MOUSE Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Acer Aspire A515-51G PackageArchitecture: all ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-58-lowlatency root=/dev/mapper/vgkubuntu-root ro quiet splash lockdown=confidentiality vt.handoff=7 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-58-lowlatency N/A linux-backports-modules-5.4.0-58-lowlatency N/A linux-firmware 1.187.6 SourcePackage: linux-firmware UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/03/2019 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V2.02 dmi.board.asset.tag: Type2 - Board Serial Number dmi.board.name: Charmander_KL dmi.board.vendor: KBL dmi.board.version: V2.02 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V2.02 dmi.modalias: dmi:bvnInsydeCorp.:bvrV2.02:bd01/03/2019:svnAcer:pnAspireA515-51G:pvrV2.02:rvnKBL:rnCharmander_KL:rvrV2.02:cvnAcer:ct10:cvrV2.02: dmi.product.family: Aspire 5 dmi.product.name: Aspire A515-51G dmi.product.sku: dmi.product.version: V2.02 dmi.sys.vendor: Acer ** Affects: linux-firmware (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/1909499 Title: iwlwifi :03:00.0: No beacon heard and the time event is over already... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1909499/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1909497] [NEW] package gdm3 3.36.3-0ubuntu0.20.04.2 failed to install/upgrade: installed gdm3 package post-installation script subprocess returned error exit status 10
Public bug reported: Hi - Such errors started to happen during software updates after I had accidentally deleted my boot partition and restored it using the Ubuntu installation CD. So, the issue is unlikely a bug. Right now, the system is up and running the applications I use correctly. Nevertheless, I believe some of the functionality of OS has been compromised. For example, there are missing icons on "Show Applications". Thanks Vahid ProblemType: Package DistroRelease: Ubuntu 20.04 Package: gdm3 3.36.3-0ubuntu0.20.04.2 ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65 Uname: Linux 5.4.0-54-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.12 Architecture: amd64 CasperMD5CheckResult: skip Date: Mon Dec 28 11:16:04 2020 DpkgHistoryLog: Start-Date: 2020-12-28 11:15:56 Commandline: aptdaemon role='role-commit-packages' sender=':1.108' Upgrade: libldap-2.4-2:amd64 (2.4.49+dfsg-2ubuntu1.4, 2.4.49+dfsg-2ubuntu1.5), libldap-common:amd64 (2.4.49+dfsg-2ubuntu1.4, 2.4.49+dfsg-2ubuntu1.5) Remove: linux-image-5.4.0-51-generic:amd64 (5.4.0-51.56), linux-headers-5.4.0-51-generic:amd64 (5.4.0-51.56), linux-modules-extra-5.4.0-51-generic:amd64 (5.4.0-51.56), linux-modules-5.4.0-51-generic:amd64 (5.4.0-51.56), linux-headers-5.4.0-51:amd64 (5.4.0-51.56) DuplicateSignature: package:gdm3:3.36.3-0ubuntu0.20.04.2 Setting up grub-pc (2.04-1ubuntu26.6) ... dpkg: error processing package grub-pc (--configure): installed grub-pc package post-installation script subprocess returned error exit status 10 ErrorMessage: installed gdm3 package post-installation script subprocess returned error exit status 10 InstallationDate: Installed on 2019-09-22 (463 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) Python3Details: /usr/bin/python3.8, Python 3.8.5, unpackaged PythonDetails: /usr/bin/python2.7, Python 2.7.18, unpackaged RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2ubuntu0.1 SourcePackage: gdm3 Title: package gdm3 3.36.3-0ubuntu0.20.04.2 failed to install/upgrade: installed gdm3 package post-installation script subprocess returned error exit status 10 UpgradeStatus: Upgraded to focal on 2020-09-29 (90 days ago) ** Affects: gdm3 (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/1909497 Title: package gdm3 3.36.3-0ubuntu0.20.04.2 failed to install/upgrade: installed gdm3 package post-installation script subprocess returned error exit status 10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1909497/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1909497] Re: package gdm3 3.36.3-0ubuntu0.20.04.2 failed to install/upgrade: installed gdm3 package post-installation script subprocess returned error exit status 10
** Tags removed: 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/1909497 Title: package gdm3 3.36.3-0ubuntu0.20.04.2 failed to install/upgrade: installed gdm3 package post-installation script subprocess returned error exit status 10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1909497/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1909495] Re: Unable to start BIOS VMs since Linux 5.10
** Changed in: linux (Ubuntu) Status: New => Confirmed ** Description changed: Since 5.10 trying to start any VM with BIOS fails on start. There are stucks on pause immediately after start. Unlike this all VMs on OVMF starts well. + + 5.10 took from here: https://kernel.ubuntu.com/~kernel-ppa/mainline/ $ LC_ALL=C virt-manager --debug [Mon, 28 Dec 2020 20:49:17 virt-manager 14579] DEBUG (cli:204) Launched with command line: /usr/bin/virt-manager --debug [Mon, 28 Dec 2020 20:49:17 virt-manager 14579] DEBUG (virtmanager:163) virt-manager version: 3.2.0 [Mon, 28 Dec 2020 20:49:17 virt-manager 14579] DEBUG (virtmanager:164) virtManager import: /usr/share/virt-manager/virtManager [Mon, 28 Dec 2020 20:49:17 virt-manager 14579] DEBUG (virtmanager:201) PyGObject version: 3.38.0 [Mon, 28 Dec 2020 20:49:17 virt-manager 14579] DEBUG (virtmanager:205) GTK version: 3.24.23 [Mon, 28 Dec 2020 20:49:17 virt-manager 14579] DEBUG (systray:77) Using AppIndicator3 for systray [Mon, 28 Dec 2020 20:49:17 virt-manager 14579] DEBUG (systray:463) Showing systray: False [Mon, 28 Dec 2020 20:49:17 virt-manager 14579] DEBUG (inspection:206) python guestfs is not installed [Mon, 28 Dec 2020 20:49:17 virt-manager 14579] DEBUG (engine:113) Loading stored URIs: qemu+ssh://master@192.168.3.9/system qemu:///system [Mon, 28 Dec 2020 20:49:17 virt-manager 14579] DEBUG (engine:461) processing cli command uri= show_window=manager domain= [Mon, 28 Dec 2020 20:49:17 virt-manager 14579] DEBUG (engine:464) No cli action requested, launching default window [Mon, 28 Dec 2020 20:49:17 virt-manager 14579] DEBUG (manager:185) Showing manager [Mon, 28 Dec 2020 20:49:17 virt-manager 14579] DEBUG (engine:316) window counter incremented to 1 [Mon, 28 Dec 2020 20:49:17 virt-manager 14579] DEBUG (engine:211) Initial gtkapplication activated [Mon, 28 Dec 2020 20:49:17 virt-manager 14579] DEBUG (connection:482) conn=qemu:///system changed to state=Connecting [Mon, 28 Dec 2020 20:49:17 virt-manager 14579] DEBUG (connection:902) Scheduling background open thread for qemu:///system [Mon, 28 Dec 2020 20:49:17 virt-manager 14579] DEBUG (connection:952) libvirt version=6006000 [Mon, 28 Dec 2020 20:49:17 virt-manager 14579] DEBUG (connection:953) daemon version=6006000 [Mon, 28 Dec 2020 20:49:17 virt-manager 14579] DEBUG (connection:954) conn version=500 [Mon, 28 Dec 2020 20:49:17 virt-manager 14579] DEBUG (connection:955) qemu:///system capabilities: a003001e-8c00-00b2-edcd-90e6ba5d1364 x86_64 Penryn Intel tcp rdma 14324000 3581000 0 apparmor 0 dac 0 +64055:+108 +64055:+108 hvm 32 /usr/bin/qemu-system-i386 pc-i440fx-groovy ubuntu pc-i440fx-2.12 pc-i440fx-2.0 pc-i440fx-xenial pc-q35-4.2 pc-i440fx-2.5 pc-i440fx-4.2 pc-i440fx-focal pc-q35-xenial pc-i440fx-1.5 pc-q35-2.7 pc-q35-eoan-hpb pc-i440fx-disco-hpb pc-i440fx-zesty pc-q35-groovy ubuntu-q35 pc-q35-artful pc-i440fx-trusty pc-i440fx-2.2 pc-i440fx-eoan-hpb pc-q35-focal-hpb pc-1.1 pc-q35-bionic-hpb pc-i440fx-artful pc-i440fx-2.7 pc-i440fx-yakkety pc-q35-2.4 pc-q35-cosmic-hpb pc-q35-2.10 pc-i440fx-1.7 pc-q35-2.9 pc-i440fx-2.11 pc-q35-3.1 pc-q35-4.1 pc-i440fx-2.4 pc-1.3 pc-i440fx-4.1 pc-q35-eoan pc-i440fx-2.9 pc-i440fx-bionic-hpb isapc pc-i440fx-1.4 pc-q35-cosmic pc-q35-2.6 pc-i440fx-3.1 pc-q35-bionic pc-q35-disco-hpb pc-i440fx-cosmic pc-q35-2.12 pc-i440fx-bionic pc-q35-groovy-hpb pc-q35-disco pc-i440fx-cosmic-hpb pc-i440fx-2.1 pc-1.0 pc-i440fx-wily pc-i440fx-2.6 pc-q35-4.0.1 pc-i440fx-1.6 pc-q35-5.0 q35 pc-q35-2.8 pc-i440fx-2.10 pc-q35-3.0 pc-q35-zesty pc-q35-4.0 pc-q35-focal microvm pc-i440fx-2.3 pc-i440fx-disco pc-1.2 pc-i440fx-4.0 pc-i440fx-focal-hpb pc-i440fx-groovy-hpb
[Bug 1909495] RelatedPackageVersions.txt
apport information ** Attachment added: "RelatedPackageVersions.txt" https://bugs.launchpad.net/bugs/1909495/+attachment/5447450/+files/RelatedPackageVersions.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1909495 Title: Unable to start BIOS VMs since Linux 5.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1909495/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1909495] Re: Unable to start BIOS VMs since Linux 5.10
apport information ** No longer affects: linux (Ubuntu) ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags added: apport-collected ** Description changed: Since 5.10 trying to start any VM with BIOS fails on start. There are stucks on pause immediately after start. Unlike this all VMs on OVMF starts well. $ LC_ALL=C virt-manager --debug [Mon, 28 Dec 2020 20:49:17 virt-manager 14579] DEBUG (cli:204) Launched with command line: /usr/bin/virt-manager --debug [Mon, 28 Dec 2020 20:49:17 virt-manager 14579] DEBUG (virtmanager:163) virt-manager version: 3.2.0 [Mon, 28 Dec 2020 20:49:17 virt-manager 14579] DEBUG (virtmanager:164) virtManager import: /usr/share/virt-manager/virtManager [Mon, 28 Dec 2020 20:49:17 virt-manager 14579] DEBUG (virtmanager:201) PyGObject version: 3.38.0 [Mon, 28 Dec 2020 20:49:17 virt-manager 14579] DEBUG (virtmanager:205) GTK version: 3.24.23 [Mon, 28 Dec 2020 20:49:17 virt-manager 14579] DEBUG (systray:77) Using AppIndicator3 for systray [Mon, 28 Dec 2020 20:49:17 virt-manager 14579] DEBUG (systray:463) Showing systray: False [Mon, 28 Dec 2020 20:49:17 virt-manager 14579] DEBUG (inspection:206) python guestfs is not installed [Mon, 28 Dec 2020 20:49:17 virt-manager 14579] DEBUG (engine:113) Loading stored URIs: qemu+ssh://master@192.168.3.9/system qemu:///system [Mon, 28 Dec 2020 20:49:17 virt-manager 14579] DEBUG (engine:461) processing cli command uri= show_window=manager domain= [Mon, 28 Dec 2020 20:49:17 virt-manager 14579] DEBUG (engine:464) No cli action requested, launching default window [Mon, 28 Dec 2020 20:49:17 virt-manager 14579] DEBUG (manager:185) Showing manager [Mon, 28 Dec 2020 20:49:17 virt-manager 14579] DEBUG (engine:316) window counter incremented to 1 [Mon, 28 Dec 2020 20:49:17 virt-manager 14579] DEBUG (engine:211) Initial gtkapplication activated [Mon, 28 Dec 2020 20:49:17 virt-manager 14579] DEBUG (connection:482) conn=qemu:///system changed to state=Connecting [Mon, 28 Dec 2020 20:49:17 virt-manager 14579] DEBUG (connection:902) Scheduling background open thread for qemu:///system [Mon, 28 Dec 2020 20:49:17 virt-manager 14579] DEBUG (connection:952) libvirt version=6006000 [Mon, 28 Dec 2020 20:49:17 virt-manager 14579] DEBUG (connection:953) daemon version=6006000 [Mon, 28 Dec 2020 20:49:17 virt-manager 14579] DEBUG (connection:954) conn version=500 [Mon, 28 Dec 2020 20:49:17 virt-manager 14579] DEBUG (connection:955) qemu:///system capabilities: a003001e-8c00-00b2-edcd-90e6ba5d1364 x86_64 Penryn Intel tcp rdma 14324000 3581000 0 apparmor 0 dac 0 +64055:+108 +64055:+108 hvm 32 /usr/bin/qemu-system-i386 pc-i440fx-groovy ubuntu pc-i440fx-2.12 pc-i440fx-2.0 pc-i440fx-xenial pc-q35-4.2 pc-i440fx-2.5 pc-i440fx-4.2 pc-i440fx-focal pc-q35-xenial pc-i440fx-1.5 pc-q35-2.7 pc-q35-eoan-hpb pc-i440fx-disco-hpb pc-i440fx-zesty pc-q35-groovy ubuntu-q35 pc-q35-artful pc-i440fx-trusty pc-i440fx-2.2 pc-i440fx-eoan-hpb pc-q35-focal-hpb pc-1.1 pc-q35-bionic-hpb pc-i440fx-artful pc-i440fx-2.7 pc-i440fx-yakkety pc-q35-2.4 pc-q35-cosmic-hpb pc-q35-2.10 pc-i440fx-1.7 pc-q35-2.9 pc-i440fx-2.11 pc-q35-3.1 pc-q35-4.1 pc-i440fx-2.4 pc-1.3 pc-i440fx-4.1 pc-q35-eoan pc-i440fx-2.9 pc-i440fx-bionic-hpb isapc pc-i440fx-1.4 pc-q35-cosmic pc-q35-2.6 pc-i440fx-3.1 pc-q35-bionic pc-q35-disco-hpb pc-i440fx-cosmic pc-q35-2.12 pc-i440fx-bionic pc-q35-groovy-hpb pc-q35-disco pc-i440fx-cosmic-hpb pc-i440fx-2.1 pc-1.0 pc-i440fx-wily pc-i440fx-2.6 pc-q35-4.0.1 pc-i440fx-1.6 pc-q35-5.0 q35 pc-q35-2.8 pc-i440fx-2.10 pc-q35-3.0 pc-q35-zesty pc-q35-4.0 pc-q35-focal microvm pc-i440fx-2.3 pc-i440fx-disco pc-1.2 pc-i440fx-4.0 pc-i440fx-focal-hpb
[Bug 1909495] Re: Unable to start BIOS VMs since Linux 5.10
** Summary changed: - Unable to start BIOS VMs since Linux 5.10.1 + Unable to start BIOS VMs since Linux 5.10 ** Description changed: - Since 5.10.1 trying to start any VM with BIOS fails on start. They stuck - on pause immediately after start. Unlike this al VMs on OVMF starts - well. + Since 5.10 trying to start any VM with BIOS fails on start. There are + stucks on pause immediately after start. Unlike this al VMs on OVMF + starts well. $ LC_ALL=C virt-manager --debug [Mon, 28 Dec 2020 20:49:17 virt-manager 14579] DEBUG (cli:204) Launched with command line: /usr/bin/virt-manager --debug [Mon, 28 Dec 2020 20:49:17 virt-manager 14579] DEBUG (virtmanager:163) virt-manager version: 3.2.0 [Mon, 28 Dec 2020 20:49:17 virt-manager 14579] DEBUG (virtmanager:164) virtManager import: /usr/share/virt-manager/virtManager [Mon, 28 Dec 2020 20:49:17 virt-manager 14579] DEBUG (virtmanager:201) PyGObject version: 3.38.0 [Mon, 28 Dec 2020 20:49:17 virt-manager 14579] DEBUG (virtmanager:205) GTK version: 3.24.23 [Mon, 28 Dec 2020 20:49:17 virt-manager 14579] DEBUG (systray:77) Using AppIndicator3 for systray [Mon, 28 Dec 2020 20:49:17 virt-manager 14579] DEBUG (systray:463) Showing systray: False [Mon, 28 Dec 2020 20:49:17 virt-manager 14579] DEBUG (inspection:206) python guestfs is not installed [Mon, 28 Dec 2020 20:49:17 virt-manager 14579] DEBUG (engine:113) Loading stored URIs: qemu+ssh://master@192.168.3.9/system qemu:///system [Mon, 28 Dec 2020 20:49:17 virt-manager 14579] DEBUG (engine:461) processing cli command uri= show_window=manager domain= [Mon, 28 Dec 2020 20:49:17 virt-manager 14579] DEBUG (engine:464) No cli action requested, launching default window [Mon, 28 Dec 2020 20:49:17 virt-manager 14579] DEBUG (manager:185) Showing manager [Mon, 28 Dec 2020 20:49:17 virt-manager 14579] DEBUG (engine:316) window counter incremented to 1 [Mon, 28 Dec 2020 20:49:17 virt-manager 14579] DEBUG (engine:211) Initial gtkapplication activated [Mon, 28 Dec 2020 20:49:17 virt-manager 14579] DEBUG (connection:482) conn=qemu:///system changed to state=Connecting [Mon, 28 Dec 2020 20:49:17 virt-manager 14579] DEBUG (connection:902) Scheduling background open thread for qemu:///system [Mon, 28 Dec 2020 20:49:17 virt-manager 14579] DEBUG (connection:952) libvirt version=6006000 [Mon, 28 Dec 2020 20:49:17 virt-manager 14579] DEBUG (connection:953) daemon version=6006000 [Mon, 28 Dec 2020 20:49:17 virt-manager 14579] DEBUG (connection:954) conn version=500 [Mon, 28 Dec 2020 20:49:17 virt-manager 14579] DEBUG (connection:955) qemu:///system capabilities: a003001e-8c00-00b2-edcd-90e6ba5d1364 x86_64 Penryn Intel tcp rdma 14324000 3581000 0 apparmor 0 dac 0 +64055:+108 +64055:+108 hvm 32 /usr/bin/qemu-system-i386 pc-i440fx-groovy ubuntu pc-i440fx-2.12 pc-i440fx-2.0 pc-i440fx-xenial pc-q35-4.2 pc-i440fx-2.5 pc-i440fx-4.2 pc-i440fx-focal pc-q35-xenial pc-i440fx-1.5 pc-q35-2.7 pc-q35-eoan-hpb pc-i440fx-disco-hpb pc-i440fx-zesty pc-q35-groovy ubuntu-q35 pc-q35-artful pc-i440fx-trusty pc-i440fx-2.2 pc-i440fx-eoan-hpb pc-q35-focal-hpb pc-1.1 pc-q35-bionic-hpb pc-i440fx-artful pc-i440fx-2.7 pc-i440fx-yakkety pc-q35-2.4 pc-q35-cosmic-hpb pc-q35-2.10 pc-i440fx-1.7 pc-q35-2.9 pc-i440fx-2.11 pc-q35-3.1 pc-q35-4.1 pc-i440fx-2.4 pc-1.3 pc-i440fx-4.1 pc-q35-eoan pc-i440fx-2.9 pc-i440fx-bionic-hpb isapc pc-i440fx-1.4 pc-q35-cosmic pc-q35-2.6 pc-i440fx-3.1 pc-q35-bionic pc-q35-disco-hpb pc-i440fx-cosmic pc-q35-2.12 pc-i440fx-bionic pc-q35-groovy-hpb pc-q35-disco pc-i440fx-cosmic-hpb pc-i440fx-2.1 pc-1.0 pc-i440fx-wily pc-i440fx-2.6 pc-q35-4.0.1 pc-i440fx-1.6 pc-q35-5.0 q35 pc-q35-2.8 pc-i440fx-2.10 pc-q35-3.0 pc-q35-zesty pc-q35-4.0 pc-q35-focal microvm
[Bug 1909496] [NEW] Blinking login screen
Public bug reported: Hello, I am facing this issue since the upgrade of Ubuntu to Ubuntu 20.04.1 LTS. The issue still persists even after re-installing Ubuntu 20.04.1 LTS. Due to inactivity the system goes to the Suspend mode. On restoring from the suspend mode the login screen appears but it starts to blink continuously making it impossible to use the system. The only option is to force restart the system. Please let me know if this is an already known issue/bug and if there is a solution available for the same. Thank You ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-58.64-generic 5.4.73 Uname: Linux 5.4.0-58-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Dec 28 19:21:12 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Skylake GT2 [HD Graphics 520] [8086:1916] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Dell Skylake GT2 [HD Graphics 520] [1028:0793] InstallationDate: Installed on 2020-12-27 (0 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Dell Inc. Vostro 15-3568 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-58-generic root=UUID=44a1973f-ce3f-46bb-ab72-156c1d047556 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/23/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 01.08.00 dmi.board.name: 05HRPP dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr01.08.00:bd03/23/2017:svnDellInc.:pnVostro15-3568:pvr:rvnDellInc.:rn05HRPP:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.family: Vostro dmi.product.name: Vostro 15-3568 dmi.product.sku: 0793 dmi.sys.vendor: Dell 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.6 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: 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/1909496 Title: Blinking login screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1909496/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1909495] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 1909495 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1909495 Title: Unable to start BIOS VMs since Linux 5.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1909495/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1909495] [NEW] Unable to start BIOS VMs since Linux 5.10
Public bug reported: Since 5.10 trying to start any VM with BIOS fails on start. There are stucks on pause immediately after start. Unlike this al VMs on OVMF starts well. $ LC_ALL=C virt-manager --debug [Mon, 28 Dec 2020 20:49:17 virt-manager 14579] DEBUG (cli:204) Launched with command line: /usr/bin/virt-manager --debug [Mon, 28 Dec 2020 20:49:17 virt-manager 14579] DEBUG (virtmanager:163) virt-manager version: 3.2.0 [Mon, 28 Dec 2020 20:49:17 virt-manager 14579] DEBUG (virtmanager:164) virtManager import: /usr/share/virt-manager/virtManager [Mon, 28 Dec 2020 20:49:17 virt-manager 14579] DEBUG (virtmanager:201) PyGObject version: 3.38.0 [Mon, 28 Dec 2020 20:49:17 virt-manager 14579] DEBUG (virtmanager:205) GTK version: 3.24.23 [Mon, 28 Dec 2020 20:49:17 virt-manager 14579] DEBUG (systray:77) Using AppIndicator3 for systray [Mon, 28 Dec 2020 20:49:17 virt-manager 14579] DEBUG (systray:463) Showing systray: False [Mon, 28 Dec 2020 20:49:17 virt-manager 14579] DEBUG (inspection:206) python guestfs is not installed [Mon, 28 Dec 2020 20:49:17 virt-manager 14579] DEBUG (engine:113) Loading stored URIs: qemu+ssh://master@192.168.3.9/system qemu:///system [Mon, 28 Dec 2020 20:49:17 virt-manager 14579] DEBUG (engine:461) processing cli command uri= show_window=manager domain= [Mon, 28 Dec 2020 20:49:17 virt-manager 14579] DEBUG (engine:464) No cli action requested, launching default window [Mon, 28 Dec 2020 20:49:17 virt-manager 14579] DEBUG (manager:185) Showing manager [Mon, 28 Dec 2020 20:49:17 virt-manager 14579] DEBUG (engine:316) window counter incremented to 1 [Mon, 28 Dec 2020 20:49:17 virt-manager 14579] DEBUG (engine:211) Initial gtkapplication activated [Mon, 28 Dec 2020 20:49:17 virt-manager 14579] DEBUG (connection:482) conn=qemu:///system changed to state=Connecting [Mon, 28 Dec 2020 20:49:17 virt-manager 14579] DEBUG (connection:902) Scheduling background open thread for qemu:///system [Mon, 28 Dec 2020 20:49:17 virt-manager 14579] DEBUG (connection:952) libvirt version=6006000 [Mon, 28 Dec 2020 20:49:17 virt-manager 14579] DEBUG (connection:953) daemon version=6006000 [Mon, 28 Dec 2020 20:49:17 virt-manager 14579] DEBUG (connection:954) conn version=500 [Mon, 28 Dec 2020 20:49:17 virt-manager 14579] DEBUG (connection:955) qemu:///system capabilities: a003001e-8c00-00b2-edcd-90e6ba5d1364 x86_64 Penryn Intel tcp rdma 14324000 3581000 0 apparmor 0 dac 0 +64055:+108 +64055:+108 hvm 32 /usr/bin/qemu-system-i386 pc-i440fx-groovy ubuntu pc-i440fx-2.12 pc-i440fx-2.0 pc-i440fx-xenial pc-q35-4.2 pc-i440fx-2.5 pc-i440fx-4.2 pc-i440fx-focal pc-q35-xenial pc-i440fx-1.5 pc-q35-2.7 pc-q35-eoan-hpb pc-i440fx-disco-hpb pc-i440fx-zesty pc-q35-groovy ubuntu-q35 pc-q35-artful pc-i440fx-trusty pc-i440fx-2.2 pc-i440fx-eoan-hpb pc-q35-focal-hpb pc-1.1 pc-q35-bionic-hpb pc-i440fx-artful pc-i440fx-2.7 pc-i440fx-yakkety pc-q35-2.4 pc-q35-cosmic-hpb pc-q35-2.10 pc-i440fx-1.7 pc-q35-2.9 pc-i440fx-2.11 pc-q35-3.1 pc-q35-4.1 pc-i440fx-2.4 pc-1.3 pc-i440fx-4.1 pc-q35-eoan pc-i440fx-2.9 pc-i440fx-bionic-hpb isapc pc-i440fx-1.4 pc-q35-cosmic pc-q35-2.6 pc-i440fx-3.1 pc-q35-bionic pc-q35-disco-hpb pc-i440fx-cosmic pc-q35-2.12 pc-i440fx-bionic pc-q35-groovy-hpb pc-q35-disco pc-i440fx-cosmic-hpb pc-i440fx-2.1 pc-1.0 pc-i440fx-wily pc-i440fx-2.6 pc-q35-4.0.1 pc-i440fx-1.6 pc-q35-5.0 q35 pc-q35-2.8 pc-i440fx-2.10 pc-q35-3.0 pc-q35-zesty pc-q35-4.0 pc-q35-focal microvm pc-i440fx-2.3 pc-i440fx-disco pc-1.2 pc-i440fx-4.0 pc-i440fx-focal-hpb pc-i440fx-groovy-hpb pc-i440fx-5.0 pc pc-i440fx-2.8 pc-i440fx-eoan pc-q35-2.5 pc-i440fx-3.0 pc-q35-yakkety pc-q35-2.11 hvm 64 /usr/bin/qemu-system-x86_64 pc-i440fx-groovy ubuntu pc-i440fx-2.12 pc-i440fx-2.0 pc-i440fx-xenial pc-q35-4.2 pc-i440fx-2.5 pc-i440fx-4.2 pc-i440fx-focal pc-q35-xenial
[Bug 1848180] Re: LVM initrd fails to activate btrfs multidevice root
** Attachment added: "/etc/initramfs-tools/scripts/local-top/btrfs-lvm" https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1848180/+attachment/5447426/+files/local-top.script -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1848180 Title: LVM initrd fails to activate btrfs multidevice root To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1848180/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1848180] Re: LVM initrd fails to activate btrfs multidevice root
OK, attached are some initramfs scripts: local-top.hook -> /etc/initramfs-tools/hooks/btrfs-lvm local-top.script -> /etc/initramfs-tools/scripts/local-top/btrfs-lvm I've tried to make them reasonably generic, the root fs is examined on initramfs creation, component btrfs devices extracted and tested to see if they are LVM LVs, and if so added to a config file inside them initramfs. Then on boot all those LVs are activated before attempting to mount root. ** Attachment added: "/etc/initramfs-tools/hooks/btrfs-lvm" https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1848180/+attachment/5447425/+files/local-top.hook -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1848180 Title: LVM initrd fails to activate btrfs multidevice root To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1848180/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1909494] [NEW] wpa_supplicant and iwlwifi failing with "No buffer space available" since "kernel 5.4.0-56"
Public bug reported: There are reproduce-able WiFi aborts with 20.04.1 LTS since update to kernel 5.4.0-56. Behaviour: nm-applet shows a window to enter the WLAN key that is pre- filled. Hitting the "Connect" button reconnects the WiFi network for a small period. The error occurs sometimes very often (e.g. 10 times/minute) or seldom (only one per day). You can see it in /var/log/syslog at the entry >>> wpa_supplicant[xxx]: l2_packet_send - sendto: No buffer space available As a result 4-Way-Handshake fails and after disconnection the new (old) key is requestet. >>> wpa_supplicant[xxx]: wlp3s0: WPA: 4-Way Handshake failed - pre-shared key >>> may be incorrect >>> NetworkManager[xxx]: [xxx] device (wlp3s0): Activation: (wifi) >>> disconnected during association, asking for new key There are a lot of people having this problem (see discussion in german moderated forum: >>> https://forum.ubuntuusers.de/topic/funknetz-schluessel-werden-staendig-abgefragt See also BUG #1908823 and question #694566 >>> https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/1908823 >>> https://answers.launchpad.net/ubuntu/+question/694566 ** Affects: ubuntu Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1909494 Title: wpa_supplicant and iwlwifi failing with "No buffer space available" since "kernel 5.4.0-56" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1909494/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1907050] Re: cannot install hplip
I am very very glad that you replied me and helped me I just cant thank you in words... god bless you all -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1907050 Title: cannot install hplip To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1907050/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 287215] Re: xmodmap settings not getting honored when keyboard devices are hotplugged
mgsloan: That's pretty awful indeed, because applying these keyboard settings locks up all keyboard input for multiple seconds. (depending on how many settings you need to apply) Do I read https://bugs.freedesktop.org/show_bug.cgi?id=25262 right when I say that this is saying that Xorg does not support ANY settings OF ANY KIND done by the user, and that it's somehow working as intended that the user's preferences are wiped whenever Xorg feels like it? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/287215 Title: xmodmap settings not getting honored when keyboard devices are hotplugged To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/287215/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 722370] Re: segfault when using the "up" key
*** This bug is a duplicate of bug 1639586 *** https://bugs.launchpad.net/bugs/1639586 ** This bug has been marked a duplicate of bug 1639586 jumpnbump crashes when jumping -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/722370 Title: segfault when using the "up" key To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/jumpnbump/+bug/722370/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1848180] Re: LVM initrd fails to activate btrfs multidevice root
I'm seeing this on focal as well. Running vgchange when the initramfs crashes to shell no longer seems to work - it just hangs. I have to add break=mount to kernel command line and do it there. Now working on hacking something into /etc/initramfs-tools/scripts/local-top/ - @Gabriele, that should allow you to make your changes permanent. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1848180 Title: LVM initrd fails to activate btrfs multidevice root To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1848180/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1909492] [NEW] quadrapassel locked up. Frozen screen.
Public bug reported: === Info === PID: 11176 (quadrapassel) UID: 1000 (jim) GID: 1000 (jim) Signal: 5 (TRAP) Timestamp: Sun 2020-12-27 17:47:33 EST (18h ago) Command Line: quadrapassel Executable: /usr/games/quadrapassel Control Group: /user.slice/user-1000.slice/session-c2.scope Unit: session-c2.scope Slice: user-1000.slice Session: c2 Owner UID: 1000 (jim) Boot ID: 00779cd3939045efbbc09e0d1ebfbbba Machine ID: 2e6db7b3feeb408ba59f7482257bc249 Hostname: jim-broom Storage: /var/lib/systemd/coredump/core.quadrapassel.1000.00779cd3939045efbbc09e0d1ebfbbba.11176.1609109253.lz4 Message: Process 11176 (quadrapassel) of user 1000 dumped core. Stack trace of thread 11176: #0 0x7f58d7e940d5 n/a (libglib-2.0.so.0 + 0x580d5) #1 0x7f58d7e96abc g_log_writer_default (libglib-2.0.so.0 + 0x5aabc) #2 0x7f58d7e94d17 g_log_structured_array (libglib-2.0.so.0 + 0x58d17) #3 0x7f58d7e95744 g_log_structured_standard (libglib-2.0.so.0 + 0x59744) #4 0x7f58d713fcea n/a (libgdk-3.so.0 + 0x68cea) #5 0x7f58d714cd13 n/a (libgdk-3.so.0 + 0x75d13) #6 0x7f58d6f9d0db _XError (libX11.so.6 + 0x410db) #7 0x7f58d5940baf n/a (libGLX_mesa.so.0 + 0x38baf) #8 0x7f58d59438c0 n/a (libGLX_mesa.so.0 + 0x3b8c0) #9 0x7f58d72842ac n/a (libcogl.so.20 + 0x7b2ac) #10 0x7f58d8373c08 n/a (libclutter-1.0.so.0 + 0x47c08) #11 0x7f58d83e4e80 n/a (libclutter-1.0.so.0 + 0xb8e80) #12 0x7f58d83cde49 n/a (libclutter-1.0.so.0 + 0xa1e49) #13 0x7f58d7e8dfbd g_main_context_dispatch (libglib-2.0.so.0 + 0x51fbd) #14 0x7f58d7e8e240 n/a (libglib-2.0.so.0 + 0x52240) #15 0x7f58d7e8e2e3 g_main_context_iteration (libglib-2.0.so.0 + 0x522e3) #16 0x7f58d822dfd5 g_application_run (libgio-2.0.so.0 + 0xe2fd5) #17 0x55e7c75ea2a9 n/a (quadrapassel + 0x152a9) #18 0x7f58d733b0b3 __libc_start_main (libc.so.6 + 0x270b3) #19 0x55e7c75dd59e n/a (quadrapassel + 0x859e) Stack trace of thread 11179: #0 0x7f58d6e06376 futex_wait_cancelable (libpthread.so.0 + 0x10376) #1 0x7f58d448662b n/a (r600_dri.so + 0x47c62b) #2 0x7f58d448623b n/a (r600_dri.so + 0x47c23b) #3 0x7f58d6dff609 start_thread (libpthread.so.0 + 0x9609) #4 0x7f58d7436293 __clone (libc.so.6 + 0x122293) Stack trace of thread 11184: #0 0x7f58d7429aff __GI___poll (libc.so.6 + 0x115aff) #1 0x7f58d7e8e1ae n/a (libglib-2.0.so.0 + 0x521ae) #2 0x7f58d7e8e2e3 g_main_context_iteration (libglib-2.0.so.0 + 0x522e3) #3 0x7f58d7e8e331 n/a (libglib-2.0.so.0 + 0x52331) #4 0x7f58d7eb7931 n/a (libglib-2.0.so.0 + 0x7b931) #5 0x7f58d6dff609 start_thread (libpthread.so.0 + 0x9609) #6 0x7f58d7436293 __clone (libc.so.6 + 0x122293) Stack trace of thread 11180: #0 0x7f58d6e06376 futex_wait_cancelable (libpthread.so.0 + 0x10376) #1 0x7f58d448662b n/a (r600_dri.so + 0x47c62b) #2 0x7f58d448623b n/a (r600_dri.so + 0x47c23b) #3 0x7f58d6dff609 start_thread (libpthread.so.0 + 0x9609) #4 0x7f58d7436293 __clone (libc.so.6 + 0x122293) Stack trace of thread 11183: #0 0x7f58d6e06376 futex_wait_cancelable (libpthread.so.0 + 0x10376) #1 0x7f58d448662b n/a (r600_dri.so + 0x47c62b) #2 0x7f58d448623b n/a (r600_dri.so + 0x47c23b) #3 0x7f58d6dff609 start_thread (libpthread.so.0 + 0x9609) #4 0x7f58d7436293 __clone (libc.so.6 + 0x122293) Stack trace of thread 11182: #0 0x7f58d6e06376 futex_wait_cancelable (libpthread.so.0 + 0x10376) #1 0x7f58d448662b n/a (r600_dri.so + 0x47c62b) #2 0x7f58d448623b n/a (r600_dri.so + 0x47c23b) #3 0x7f58d6dff609 start_thread (libpthread.so.0 + 0x9609) #4 0x7f58d7436293 __clone (libc.so.6 + 0x122293) Stack trace of thread 11186:
[Bug 1816296] Re: Unable to connect to dbus: Could not connect: Permission denied
Using focal Kubuntu. Firefox filling .xsession-errors Has pyqt5 (5.14.1+dfsg-3build1) focal; & current versions of other dbus related files that are standard. fred@z97-focal-kubuntu:~$ uname -a Linux z97-focal-kubuntu 5.4.0-58-generic #64-Ubuntu SMP Wed Dec 9 08:16:25 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux fred@z97-focal-kubuntu:~$ echo $DESKTOP_SESSION plasma fred@z97-focal-kubuntu:~$ cat /etc/X11/default-display-manager /usr/bin/sddm fred@z97-focal-kubuntu:~$ cat /etc/lsb-release DISTRIB_ID=Ubuntu DISTRIB_RELEASE=20.04 DISTRIB_CODENAME=focal DISTRIB_DESCRIPTION="Ubuntu 20.04.1 LTS" fred@z97-focal-kubuntu:~$ apt show firefox Package: firefox Version: 84.0+build3-0ubuntu0.20.04.1 ** (/usr/lib/firefox/firefox:112432): WARNING **: 09:37:31.184: Unable to connect to dbus: Could not connect: Permission denied ** (/usr/lib/firefox/firefox:112483): WARNING **: 09:37:31.636: Unable to connect to dbus: Could not connect: Permission denied ** (/usr/lib/firefox/firefox:112515): WARNING **: 09:37:31.830: Unable to connect to dbus: Could not connect: Permission denied ** (/usr/lib/firefox/firefox:112540): WARNING **: 09:37:31.970: Unable to connect to dbus: Could not connect: Permission denied ** (/usr/lib/firefox/firefox:112609): WARNING **: 09:37:33.138: Unable to connect to dbus: Could not connect: Permission denied ** (/usr/lib/firefox/firefox:112734): WARNING **: 09:38:27.515: Unable to connect to dbus: Could not connect: Permission denied ** (/usr/lib/firefox/firefox:112782): WARNING **: 09:38:27.981: Unable to connect to dbus: Could not connect: Permission denied ** (/usr/lib/firefox/firefox:112833): WARNING **: 09:38:28.518: Unable to connect to dbus: Could not connect: Permission denied -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1816296 Title: Unable to connect to dbus: Could not connect: Permission denied To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/appmenu-gtk-module/+bug/1816296/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1909491] [NEW] INSTALL CRASH
Public bug reported: INSTALL CRASHED ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubiquity 20.04.15.2 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.445.1 CurrentDesktop: ubuntu:GNOME Date: Mon Dec 28 09:43:22 2020 LiveMediaBuild: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) ProcEnviron: LANGUAGE=en_US.UTF-8 PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 LC_NUMERIC=C.UTF-8 SourcePackage: grub-installer UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: grub-installer (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/1909491 Title: INSTALL CRASH To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1909491/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1879989] Re: "Failed to play sound: No such driver" ubuntu 20.04
Thanks Eric, this also fixed it for me. :) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1879989 Title: "Failed to play sound: No such driver" ubuntu 20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1879989/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1876442] Re: [snap] chromium causing many audit messages in syslog
Same problem here. It seems this post is about the same problem: https://ubuntuforums.org/showthread.php?t=2444175 Workaround from that post: run the chromium directly without using Snap: /snap/chromium/current/usr/lib/chromium-browser/chrome & It seems to work. However, all personal configuration is linked to the Snap version so you'll have to configure it again (for example, you lose all cookies, bookmarks, etc). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1876442 Title: [snap] chromium causing many audit messages in syslog To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1876442/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1909488] [NEW] Grub-efi-amd64-signed cannot be apploaded into the /target/
Public bug reported: Grub-efi-amd64-signed cannot be apploaded into the /target/ ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubiquity 20.04.15.2 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.445.1 Date: Mon Dec 28 16:45:48 2020 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed maybe-ubiquity quiet splash --- LiveMediaBuild: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) SourcePackage: grub-installer UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: grub-installer (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ubiquity-20.04.15.2 ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1909488 Title: Grub-efi-amd64-signed cannot be apploaded into the /target/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1909488/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1909487] [NEW] Set up stops and a message is "grub-install/dev/nvme0n1"
Public bug reported: Set up stops and a message is "grub-install/dev/nvme0n1" ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubiquity 20.04.15.2 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.445.1 CurrentDesktop: ubuntu:GNOME Date: Mon Dec 28 16:08:52 2020 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed maybe-ubiquity quiet splash --- LiveMediaBuild: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) ProcEnviron: LANGUAGE=uk_UA.UTF-8 PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=uk_UA.UTF-8 LC_NUMERIC=C.UTF-8 SourcePackage: grub-installer UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: grub-installer (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ubiquity-20.04.15.2 ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1909487 Title: Set up stops and a message is "grub-install/dev/nvme0n1" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1909487/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1575053] Re: Please move the "$HOME/snap" directory to a less obtrusive location
@jean-miguel and anyone else affected: Please report your feedback to Ubuntu customer support too, so that they can draw their own conclusion on how their product decisions affect their user base. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1575053 Title: Please move the "$HOME/snap" directory to a less obtrusive location To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1575053/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1908025] Re: export var=~root does not expand ~root to /root
I agree that this is a useful feature (including that export a=$b does not split words and export a=* does not generate pathnames); FreeBSD sh has had it for a few years: https://cgit.freebsd.org/src/commit/?id=84fbdd8ca068ec63c6c9a931303d3811738128cb . It is specified by https://www.austingroupbugs.net/view.php?id=351 planned for the next major revision of POSIX.1. ** Bug watch added: www.austingroupbugs.net/ #351 https://www.austingroupbugs.net/view.php?id=351 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1908025 Title: export var=~root does not expand ~root to /root To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dash/+bug/1908025/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1579735] Re: kscreen spams my systemlog
Same or similar bug, on a fresh Kubuntu 20.10 installation ? 28/12/2020 13:45org.kde.KScreen kscreen.xcb.helper: RRNotify_OutputProperty (ignored) 28/12/2020 13:45org.kde.KScreen kscreen.xcb.helper: Output: 570 28/12/2020 13:45org.kde.KScreen kscreen.xcb.helper: Property: Backlight 28/12/2020 13:45org.kde.KScreen kscreen.xcb.helper: State (newValue, Deleted): 0 'sys.log' is constantly filled with this. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1579735 Title: kscreen spams my systemlog To manage notifications about this bug go to: https://bugs.launchpad.net/kubuntu-ppa/+bug/1579735/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1905593] Re: Support synaptics devices 0xF9, 0xFC, 0xC2, 0xC9, 0xE7
tested the new version(1:1.90.2+tod1-0ubuntu1~20.04.4) in focal- proposed, it works ** Tags removed: verification-needed verification-needed-focal verification-needed-groovy ** Tags added: verification-done verification-done-focal verification-done-groovy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1905593 Title: Support synaptics devices 0xF9, 0xFC, 0xC2, 0xC9, 0xE7 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1905593/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1909393] Re: Xubuntu 20.04 LTS / Thunar File Manager error GDBUS related
** Summary changed: - Thunar File Manager error GDBUS related + Xubuntu 20.04 LTS / Thunar File Manager error GDBUS related -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1909393 Title: Xubuntu 20.04 LTS / Thunar File Manager error GDBUS related To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xubuntu-meta/+bug/1909393/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1909478] [NEW] ubuntu installer Create LVM volume group Devices are invisible
Public bug reported: Booted ubuntu installer live iso, got as far as "Create LVM volume group", which presents a list of Devices which are invisible. The tab key clearly steps through the invisible devices, but as they are invisible i cant see which to choose. As a sometimes workaround, by hitting the spacebar on each invisible choice, the size is shown, and i can sometimes deduce from that which device it is, tho if several devices are the same size even that doesn't help. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubiquity (not installed) 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: pass CasperVersion: 1.445.1 Date: Mon Dec 28 06:44:19 2020 InstallCmdLine: BOOT_IMAGE=(i)/casper/vmlinuz iso-scan/filename=/home/greg/ubuntu-20.04.1-live-server-amd64.iso boot=casper panic=30 toram -- LiveMediaBuild: Ubuntu-Server 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) ProcEnviron: TERM=screen PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ubiquity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal uec-images -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1909478 Title: ubuntu installer Create LVM volume group Devices are invisible To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1909478/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1909479] [NEW] Composed characteres are still not managed by gdm greeter
Public bug reported: Similary behaviour of this bug was report in #1716159 and #1765261, but still occured. Step to reproduce : - Login your Ubuntu 20.04 desktop session, - Modifi the user password with User Pannel Settings, - Select a User, - Change his password with a new one containing some composed char like "ë" or "ê" (composed by two keys for example "^" key + "e" key), - Validate. Now, the User is not abble to connect himself with gdm, because it never allow the user fills the composed characters (nothing appends) in the password field. The user can login by using command line with the new password. "password" cmd line produce same thing when use composed character, gdm is still not able to manage composed character. ** Affects: gdm3 (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/1909479 Title: Composed characteres are still not managed by gdm greeter To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1909479/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1909480] [NEW] ubuntu installer wont probe block devices if invoked via ssh
Public bug reported: While groping for a workaround to bug #1909478 i tried logging into the ubiquity installer via ssh. This looks like a very nice feature, but unfortunately, when logged in thusly via ssh, the installer says "Guided storage configuration...Block probing did not discover any disks. Unfortunately this means that installation will not be possible." ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubiquity (not installed) 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: pass CasperVersion: 1.445.1 Date: Mon Dec 28 06:35:11 2020 InstallCmdLine: BOOT_IMAGE=(i)/casper/vmlinuz iso-scan/filename=/home/greg/ubuntu-20.04.1-live-server-amd64.iso boot=casper panic=30 toram -- LiveMediaBuild: Ubuntu-Server 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) ProcEnviron: TERM=screen PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ubiquity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal uec-images -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1909480 Title: ubuntu installer wont probe block devices if invoked via ssh To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1909480/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1904093] Re: libpcl 1.10.0 bugs
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: pcl (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1904093 Title: libpcl 1.10.0 bugs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pcl/+bug/1904093/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1909474] Re: System hangs after attaching Mediatek mt76x2u based USB Wifi network adapter
Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general. It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it. You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage. You might also ask for help in the #ubuntu-bugs irc channel on Freenode. To change the source package that this bug is filed about visit https://bugs.launchpad.net/ubuntu/+bug/1909474/+editstatus and add the package name in the text box next to the word Package. [This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.] ** Tags added: bot-comment -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1909474 Title: System hangs after attaching Mediatek mt76x2u based USB Wifi network adapter To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1909474/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1909355] Re: 20.04 install software raid fails. SSD's have identical WWN's.
** Attachment added: "syslog" https://bugs.launchpad.net/ubuntu/+source/subiquity/+bug/1909355/+attachment/5447388/+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/1909355 Title: 20.04 install software raid fails. SSD's have identical WWN's. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/subiquity/+bug/1909355/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1909355] Re: 20.04 install software raid fails. SSD's have identical WWN's.
Apologies for this: I assumed mdadm has this problem too, but that's a mistake. mdadm can handle hdd's when they have identical WWN's. The message "device or resource busy" is caused by something else. So it's clearly a subiquity bug. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1909355 Title: 20.04 install software raid fails. SSD's have identical WWN's. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/subiquity/+bug/1909355/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
