[Bug 1882354] Re: [Intel T4200] all application open in black
Can you please attach a screenshot or photo of the problem? ** Summary changed: - graphics card + [Intel T4200] all application open in black ** Package changed: xorg (Ubuntu) => mutter (Ubuntu) ** Changed in: mutter (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/1882354 Title: [Intel T4200] all application open in black To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1882354/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1882231] Re: Tooltip for Rubbish Bin desktop icon displays "Empty Wastebasket" or "Empty Trash"
** Summary changed: - Tooltip for Rubbish Bin displays "Wastebasket ..." instead of "Rubbish Bin ..." + Tooltip for Rubbish Bin desktop icon displays "Empty Wastebasket" or "Empty Trash" ** Summary changed: - Tooltip for Rubbish Bin desktop icon displays "Empty Wastebasket" or "Empty Trash" + Context menu for Rubbish Bin desktop icon displays "Empty Wastebasket" or "Empty Trash" ** Changed in: gnome-shell-extension-desktop-icons (Ubuntu) Importance: Undecided => Low ** Bug watch added: gitlab.gnome.org/World/ShellExtensions/desktop-icons/-/issues #208 https://gitlab.gnome.org/World/ShellExtensions/desktop-icons/-/issues/208 ** Also affects: gnome-shell-extension-desktop-icons via https://gitlab.gnome.org/World/ShellExtensions/desktop-icons/-/issues/208 Importance: Unknown Status: Unknown ** Changed in: gnome-shell-extension-desktop-icons (Ubuntu) Status: Confirmed => Triaged -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1882231 Title: Context menu for Rubbish Bin desktop icon displays "Empty Wastebasket" or "Empty Trash" To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell-extension-desktop-icons/+bug/1882231/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1880125] Re: v3d driver clock problem forces OpenGL to use software rendering
** Also affects: linux-raspi (Ubuntu Focal) 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/1880125 Title: v3d driver clock problem forces OpenGL to use software rendering To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1880125/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1871385] Re: gnome-control-center crashed with SIGSEGV in _cogl_gpu_info_parse_version_string()
Actually it looks like a common issue: https://errors.ubuntu.com/problem/52cceae54b9e2fbd142648250df0027efdebcb2e ** Description changed: + https://errors.ubuntu.com/problem/52cceae54b9e2fbd142648250df0027efdebcb2e + + --- + i need help ProblemType: Crash DistroRelease: Ubuntu 20.04 Package: gnome-control-center 1:3.36.1-1ubuntu4 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu24 Architecture: amd64 CurrentDesktop: Budgie:GNOME Date: Tue Apr 7 14:53:42 2020 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2020-04-07 (0 days ago) InstallationMedia: Ubuntu-Budgie 20.04 LTS "Focal Fossa" - Beta amd64 (20200405) ProcCmdline: gnome-control-center sound ProcEnviron: - LANGUAGE=fr_FR - PATH=(custom, no user) - XDG_RUNTIME_DIR= - LANG=fr_FR.UTF-8 - SHELL=/bin/bash + LANGUAGE=fr_FR + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=fr_FR.UTF-8 + SHELL=/bin/bash SegvAnalysis: - Segfault happened at: 0x7f57bb0eb1ea <__GI_strtoul_l_internal+58>: movsbq 0x0(%r13),%rax - PC (0x7f57bb0eb1ea) ok - source "0x0(%r13)" (0x) not located in a known VMA region (needed readable region)! - destination "%rax" ok + Segfault happened at: 0x7f57bb0eb1ea <__GI_strtoul_l_internal+58>: movsbq 0x0(%r13),%rax + PC (0x7f57bb0eb1ea) ok + source "0x0(%r13)" (0x) not located in a known VMA region (needed readable region)! + destination "%rax" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: gnome-control-center StacktraceTop: - __GI_strtoul_l_internal (nptr=0x0, endptr=0x7fff3a4881c8, base=10, group=, loc=0x7f57bb289960 <_nl_C_locobj>) at ../stdlib/strtol_l.c:292 - ?? () from /lib/x86_64-linux-gnu/libcogl.so.20 - ?? () from /lib/x86_64-linux-gnu/libcogl.so.20 - ?? () from /lib/x86_64-linux-gnu/libcogl.so.20 - ?? () from /lib/x86_64-linux-gnu/libcogl.so.20 + __GI_strtoul_l_internal (nptr=0x0, endptr=0x7fff3a4881c8, base=10, group=, loc=0x7f57bb289960 <_nl_C_locobj>) at ../stdlib/strtol_l.c:292 + ?? () from /lib/x86_64-linux-gnu/libcogl.so.20 + ?? () from /lib/x86_64-linux-gnu/libcogl.so.20 + ?? () from /lib/x86_64-linux-gnu/libcogl.so.20 + ?? () from /lib/x86_64-linux-gnu/libcogl.so.20 Title: gnome-control-center crashed with SIGSEGV in __GI_strtoul_l_internal() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo separator: ** Changed in: gnome-control-center (Ubuntu) Status: Expired => Confirmed ** Summary changed: - gnome-control-center crashed with SIGSEGV in _cogl_gpu_info_parse_version_string() + gnome-control-center crashed with SIGSEGV in strtoul() from _cogl_gpu_info_parse_version_string() ** Summary changed: - gnome-control-center crashed with SIGSEGV in strtoul() from _cogl_gpu_info_parse_version_string() + gnome-control-center crashed with SIGSEGV in __GI_strtoul_l_internal() from _cogl_gpu_info_parse_version_string() ** Bug watch added: gitlab.gnome.org/GNOME/gnome-control-center/-/issues #1019 https://gitlab.gnome.org/GNOME/gnome-control-center/-/issues/1019 ** Also affects: gnome-control-center via https://gitlab.gnome.org/GNOME/gnome-control-center/-/issues/1019 Importance: Unknown Status: Unknown ** Changed in: gnome-control-center (Ubuntu) Importance: Low => Medium ** Tags added: bionic groovy xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1871385 Title: gnome-control-center crashed with SIGSEGV in __GI_strtoul_l_internal() from _cogl_gpu_info_parse_version_string() To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1871385/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1880041] XorgLog.txt
apport information ** Attachment added: "XorgLog.txt" https://bugs.launchpad.net/bugs/1880041/+attachment/5381511/+files/XorgLog.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1880041 Title: Failing to shutdown/power off or reboot on AMD Ryzen CPUs on kernel versions 5.3.0-52 and later To manage notifications about this bug go to: https://bugs.launchpad.net/dri/+bug/1880041/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1878194] Re: [Sennheiser HD 4.50 BTNC] Bluetooth headset not working when selecting HSP/HFP audio profile in Focal Fossa
I also experience this issue with 2 different Brand of Bluetooth Headset: ATH-CRK75BTH Edifier W200BT Problem also appears every time I switch bluetooh devices as INPUT device and OUTPUT using HEADSET Unit (HSP/HFP). Input indicator bar doesn't move and test OUTPUT doesn't produce any sound. When I tried video conferencing with my friend, he couldn't hear my voice and of course I can't hear him either. This is fresh installation using Ubuntu 20.04 (no prior Ubuntu or other Linux distro in this laptop). A2DP mode works normal. Currently I'm using internal laptop microphone and A2DP combination for video conferencing. Just now, I ran "sudo apt dist-upgrade, some packages were updated. But still not work for HSP/HFP mode output and Bluetooth mic input. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1878194 Title: [Sennheiser HD 4.50 BTNC] Bluetooth headset not working when selecting HSP/HFP audio profile in Focal Fossa To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1878194/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1880041] XorgLogOld.txt
apport information ** Attachment added: "XorgLogOld.txt" https://bugs.launchpad.net/bugs/1880041/+attachment/5381512/+files/XorgLogOld.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1880041 Title: Failing to shutdown/power off or reboot on AMD Ryzen CPUs on kernel versions 5.3.0-52 and later To manage notifications about this bug go to: https://bugs.launchpad.net/dri/+bug/1880041/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1880041] xdpyinfo.txt
apport information ** Attachment added: "xdpyinfo.txt" https://bugs.launchpad.net/bugs/1880041/+attachment/5381514/+files/xdpyinfo.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1880041 Title: Failing to shutdown/power off or reboot on AMD Ryzen CPUs on kernel versions 5.3.0-52 and later To manage notifications about this bug go to: https://bugs.launchpad.net/dri/+bug/1880041/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1880041] Xrandr.txt
apport information ** Attachment added: "Xrandr.txt" https://bugs.launchpad.net/bugs/1880041/+attachment/5381513/+files/Xrandr.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1880041 Title: Failing to shutdown/power off or reboot on AMD Ryzen CPUs on kernel versions 5.3.0-52 and later To manage notifications about this bug go to: https://bugs.launchpad.net/dri/+bug/1880041/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1880041] DpkgLog.txt
apport information ** Attachment added: "DpkgLog.txt" https://bugs.launchpad.net/bugs/1880041/+attachment/5381503/+files/DpkgLog.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1880041 Title: Failing to shutdown/power off or reboot on AMD Ryzen CPUs on kernel versions 5.3.0-52 and later To manage notifications about this bug go to: https://bugs.launchpad.net/dri/+bug/1880041/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1880041] Re: Failing to shutdown/power off or reboot on AMD Ryzen CPUs on kernel versions 5.3.0-52 and later
ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.15 Architecture: amd64 BootLog: Error: [Errno 13] Keine Berechtigung: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME DistUpgraded: Fresh install DistroCodename: bionic DistroRelease: Ubuntu 18.04 DistroVariant: ubuntu GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Vega 10 XT [Radeon RX Vega 64] [1002:687f] (rev c3) (prog-if 00 [VGA controller]) Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Vega 10 XT [Radeon RX Vega 64] [1002:0b36] InstallationDate: Installed on 2019-04-12 (422 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) MachineType: Micro-Star International Co., Ltd MS-7B86 Package: linux-meta-hwe ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.3.0-51-generic root=UUID=afdf9011-a57a-434a-bcb5-0587e1b57161 ro rootflags=subvol=@ quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.3.0-51.44~18.04.2-generic 5.3.18 Tags: bionic ubuntu Uname: Linux 5.3.0-51-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 09/21/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.20 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B450 GAMING PLUS (MS-7B86) dmi.board.vendor: Micro-Star International Co., Ltd dmi.board.version: 1.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.20:bd09/21/2018:svnMicro-StarInternationalCo.,Ltd:pnMS-7B86:pvr1.0:rvnMicro-StarInternationalCo.,Ltd:rnB450GAMINGPLUS(MS-7B86):rvr1.0:cvnMicro-StarInternationalCo.,Ltd:ct3:cvr1.0: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7B86 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 1.0 dmi.sys.vendor: Micro-Star International Co., Ltd version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1~18.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~18.04.3 version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~18.04.3 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A ** Tags added: apport-collected bionic ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1880041 Title: Failing to shutdown/power off or reboot on AMD Ryzen CPUs on kernel versions 5.3.0-52 and later To manage notifications about this bug go to: https://bugs.launchpad.net/dri/+bug/1880041/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1881097] Re: [Thinkpad X1C7][Thinkpad X1C8]F1 and F4 Hotkey LED Light Stays ON/OFF when USB Headset is attached.
** Changed in: linux (Ubuntu) Importance: Undecided => Wishlist -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1881097 Title: [Thinkpad X1C7][Thinkpad X1C8]F1 and F4 Hotkey LED Light Stays ON/OFF when USB Headset is attached. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1881097/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1881687] Re: Desktop is blank after logging in without a monitor attached
** Also affects: gnome-shell via https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/2883 Importance: Unknown Status: Unknown ** Changed in: gnome-shell (Ubuntu) Status: Incomplete => New ** Changed in: mutter (Ubuntu) Status: Incomplete => Triaged ** Changed in: gnome-shell (Ubuntu) Status: New => Triaged -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1881687 Title: Desktop is blank after logging in without a monitor attached To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1881687/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1880041] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1880041/+attachment/5381510/+files/UdevDb.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1880041 Title: Failing to shutdown/power off or reboot on AMD Ryzen CPUs on kernel versions 5.3.0-52 and later To manage notifications about this bug go to: https://bugs.launchpad.net/dri/+bug/1880041/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1880041] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1880041/+attachment/5381502/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1880041 Title: Failing to shutdown/power off or reboot on AMD Ryzen CPUs on kernel versions 5.3.0-52 and later To manage notifications about this bug go to: https://bugs.launchpad.net/dri/+bug/1880041/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1880041] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1880041/+attachment/5381505/+files/Lsusb.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1880041 Title: Failing to shutdown/power off or reboot on AMD Ryzen CPUs on kernel versions 5.3.0-52 and later To manage notifications about this bug go to: https://bugs.launchpad.net/dri/+bug/1880041/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1880041] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1880041/+attachment/5381509/+files/ProcModules.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1880041 Title: Failing to shutdown/power off or reboot on AMD Ryzen CPUs on kernel versions 5.3.0-52 and later To manage notifications about this bug go to: https://bugs.launchpad.net/dri/+bug/1880041/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1880041] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1880041/+attachment/5381504/+files/Lspci.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1880041 Title: Failing to shutdown/power off or reboot on AMD Ryzen CPUs on kernel versions 5.3.0-52 and later To manage notifications about this bug go to: https://bugs.launchpad.net/dri/+bug/1880041/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1880041] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1880041/+attachment/5381507/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1880041 Title: Failing to shutdown/power off or reboot on AMD Ryzen CPUs on kernel versions 5.3.0-52 and later To manage notifications about this bug go to: https://bugs.launchpad.net/dri/+bug/1880041/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1880041] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1880041/+attachment/5381508/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1880041 Title: Failing to shutdown/power off or reboot on AMD Ryzen CPUs on kernel versions 5.3.0-52 and later To manage notifications about this bug go to: https://bugs.launchpad.net/dri/+bug/1880041/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1880041] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1880041/+attachment/5381506/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1880041 Title: Failing to shutdown/power off or reboot on AMD Ryzen CPUs on kernel versions 5.3.0-52 and later To manage notifications about this bug go to: https://bugs.launchpad.net/dri/+bug/1880041/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1878194] Re: [Sennheiser HD 4.50 BTNC] Bluetooth headset not working when selecting HSP/HFP audio profile in Focal Fossa
I also experience this issue with 2 different Brand of Bluetooth Headset: ATH-CRK75BTH Edifier W200BT Problem also appears every time I switch bluetooh devices as INPUT device and OUTPUT using HEADSET Unit (HSP/HFP). Input indicator bar doesn't move and test OUTPUT doesn't produce any sound. When I tried video conferencing with my friend, he couldn't hear my voice and of course I can't hear him either. This is fresh installation using Ubuntu 20.04 (no prior Ubuntu or other Linux distro in this laptop). A2DP mode works normal. Currently I'm using internal laptop microphone and A2DP combination for video conferencing. Just now, I ran "sudo apt dist-upgrade, some packages were updated. But still not work for HSP/HFP mode output and Bluetooth mic input. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1878194 Title: [Sennheiser HD 4.50 BTNC] Bluetooth headset not working when selecting HSP/HFP audio profile in Focal Fossa To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1878194/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1821434] Re: Panic on suspend/resume Kernel panic - not syncing: stack-protector: Kernel stack is corrupted in: sata_pmp_eh_recover+0xa2b/0xa40
Thanks for the verification @vali !! ** Tags removed: verification-needed-eoan verification-needed-focal verification-needed-xenial ** Tags added: verification-done-eoan verification-done-focal verification-done-xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1821434 Title: Panic on suspend/resume Kernel panic - not syncing: stack-protector: Kernel stack is corrupted in: sata_pmp_eh_recover+0xa2b/0xa40 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1821434/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1882491] Re: /usr/bin/gnome-control-center:11:__GI_____strtoul_l_internal:_cogl_gpu_info_parse_version_string:check_mesa_driver_package:_cogl_gpu_info_init:_cogl_driver_update_features
*** This bug is a duplicate of bug 1871385 *** https://bugs.launchpad.net/bugs/1871385 ** This bug has been marked a duplicate of bug 1871385 gnome-control-center crashed with SIGSEGV in _cogl_gpu_info_parse_version_string() -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1882491 Title: /usr/bin/gnome-control- center:11:__GI_strtoul_l_internal:_cogl_gpu_info_parse_version_string:check_mesa_driver_package:_cogl_gpu_info_init:_cogl_driver_update_features To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1882491/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1882491] [NEW] /usr/bin/gnome-control-center:11:__GI_____strtoul_l_internal:_cogl_gpu_info_parse_version_string:check_mesa_driver_package:_cogl_gpu_info_init:_cogl_driver_update_features
*** This bug is a duplicate of bug 1871385 *** https://bugs.launchpad.net/bugs/1871385 Public bug reported: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-control-center. This problem was most recently seen with package version 1:3.36.2-1ubuntu1, the problem page at https://errors.ubuntu.com/problem/52cceae54b9e2fbd142648250df0027efdebcb2e contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New ** Tags: artful bionic cosmic disco eoan focal groovy xenial zesty -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1882491 Title: /usr/bin/gnome-control- center:11:__GI_strtoul_l_internal:_cogl_gpu_info_parse_version_string:check_mesa_driver_package:_cogl_gpu_info_init:_cogl_driver_update_features To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1882491/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1879325] Re: Unable to remove disk metadata on vm
** Tags removed: verification-needed verification-needed-focal ** Tags added: verification-done verification-done-focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1879325 Title: Unable to remove disk metadata on vm To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1879325/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1882490] [NEW] gsd-media-keys unable to get default source or sink
Public bug reported: jlquinn@cerberus:~$ lsb_release -rd Description:Ubuntu 18.04.4 LTS Release:18.04 jlquinn@cerberus:~$ apt-cache policy gnome-settings-daemon gnome-settings-daemon: Installed: 3.28.1-0ubuntu1.3 Candidate: 3.28.1-0ubuntu1.3 Version table: *** 3.28.1-0ubuntu1.3 500 500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 100 /var/lib/dpkg/status 3.28.1-0ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages In my log, I see the following messages: Jun 08 00:27:19 cerberus gsd-media-keys[3584]: Unable to get default sink Jun 08 00:27:19 cerberus gsd-media-keys[3584]: Unable to get default source This seems like something is amiss. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-settings-daemon 3.28.1-0ubuntu1.3 ProcVersionSignature: Ubuntu 5.3.0-53.47~18.04.1-generic 5.3.18 Uname: Linux 5.3.0-53-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.15 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Jun 8 01:03:33 2020 InstallationDate: Installed on 2020-05-29 (9 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-settings-daemon UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-settings-daemon (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1882490 Title: gsd-media-keys unable to get default source or sink To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1882490/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1882482] Re: Ubuntu 16.04LTS setup can success in my Laptop(HP-Compaq_nc6400) by required a previous windows OS Setup which have a partition active. When I am trying the setup without other OS Ex
After an hour I have retrieved setup by the option-"Update" selected (internet connected). Yet it seems same error !! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1882482 Title: Ubuntu 16.04LTS setup can success in my Laptop(HP-Compaq_nc6400) by required a previous windows OS Setup which have a partition active. When I am trying the setup without other OS Exist or any mass storage (as a blank Hard Disk)- it shows error to setup Ubuntu. So using reporting option just telling you the problem to improve the development forums. Thank you To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1882482/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1881852] Re: neutron-netns-cleanup does not work in Ubuntu
** Merge proposal linked: https://code.launchpad.net/~ubuntu-server-dev/ubuntu/+source/neutron/+git/neutron/+merge/385247 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1881852 Title: neutron-netns-cleanup does not work in Ubuntu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/neutron/+bug/1881852/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1882488] [NEW] Install of Ubuntu 20.04 LTS fails partway though
Public bug reported: There were other bugs on the list that were similar to mine, but they were all trying to install other OS versions. I'm trying to install Ubuntu 20.04 LTS on my machine from a USB, and I'm trying to dual boot it with Windows 10. I have already have Win 10 on the same hard drive that I'm trying to put Ubuntu on, it's on an NVME SSD (500 gig model). There are a few interesting things that happen during the installation process that likely help lead to the Ubuntu install crashing before completion. One of them is that when it gets to the install options, there is actually no listing for "Install Ubuntu Alongside Windows". The only options are for "Erase Disk and Install Ubuntu" and "Something Else". So, I click "Something Else". The other interesting thing I've noted is that there is no EFI file detected on my hard drive once you click "Something Else" to manually partition your drive, so I have to make one by selecting EFI partition and giving it 250MB or so. If you try to click the install before you do this, a warning message will pop up that you may ruin the installation, so I always obey the warning. I believe this is part of the problem because it doesn't show to create an EFI file in any of the Ubuntu install guides I've seen, so I strongly believe it leads to the crash. Once I finish manually partitioning, giving ~20gigs for the "/" directory and the rest of my 200GB partition to my "/home" directory, it goes through the install, and then it eventually crashes at the same part every time. "Executing 'grub-install/dev/nvme' failed. "This is a fatal error." The above is what the error message reads. I've even tried to install Ubuntu again, directly after it failed, with half the Ubuntu install still on the hard drive. Hilariously enough, there came an option for "Install Ubuntu 20.04 alongside Ubuntu 20.04" because it detected the other install. I selected that option, but it still failed at the exact same spot, with the exact same error. Once it fails, it will not boot to any Ubuntu partition. In fact, I have to go into "Disks" from my temporary Ubuntu USB, select the Windows 10 partition, and make it bootable in order for Windows 10 to boot. Hope this helps. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubiquity 20.04.15 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckMismatches: ./pool/restricted/l/linux-restricted-modules/linux-modules-nvidia-440-5.4.0-26-generic_5.4.0-26.30+2_amd64.deb CasperMD5CheckResult: skip CasperVersion: 1.445 Date: Sun Jun 7 21:10:01 2020 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed maybe-ubiquity quiet splash --- LiveMediaBuild: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) 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 ubuntu ** Description changed: There were other bugs on the list that were similar to mine, but they were all trying to install other OS versions. I'm trying to install - Ubuntu 20.04 LTS on my machine, and I'm trying to dual boot it with - Windows 10. I have already have Win 10 on the same hard drive that I'm - trying to put Ubuntu on, it's on an NVME SSD (500 gig model). There are - a few interesting things that happen during the installation process - that likely help lead to the Ubuntu install crashing before completion. - One of them is that when it gets to the install options, there is - actually no listing for "Install Ubuntu Alongside Windows". The only - options are for "Erase Disk and Install Ubuntu" and "Something Else". - So, I click "Something Else". The other interesting thing I've noted is - that there is no EFI file detected on my hard drive once you click - "Something Else" to manually partition your drive, so I have to make one - by selecting EFI partition and giving it 250MB or so. If you try to - click the install before you do this, a warning message will pop up that - you may ruin the installation, so I always obey the warning. I believe - this is part of the problem because it doesn't show to create an EFI - file in any of the Ubuntu install guides I've seen, so I strongly + Ubuntu 20.04 LTS on my machine from a USB, and I'm trying to dual boot + it with Windows 10. I have already have Win 10 on the same hard drive + that I'm trying to put Ubuntu on, it's on an NVME SSD (500 gig model). + There are a few interesting things that happen during the installation + process that likely help lead to the Ubuntu install crashing before + completion. One of them is that when it gets to the install options, + there is actually no listing for "Install Ubuntu Alongside Windows". + The only
[Bug 1881771] Re: neutron-ipset-cleanup fails with Traceback: Unhandled error: oslo_config.cfg.NoSuchOptError: no such option AGENT in group [DEFAULT]
** Merge proposal linked: https://code.launchpad.net/~ubuntu-server-dev/ubuntu/+source/neutron/+git/neutron/+merge/385247 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1881771 Title: neutron-ipset-cleanup fails with Traceback: Unhandled error: oslo_config.cfg.NoSuchOptError: no such option AGENT in group [DEFAULT] To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1881771/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1876320] Re: Port parameter sshd_config is 22 AND whatever you specify
FYI - 1:8.2p1-4ubuntu1 migrated into groovy - 1:8.3p1-1 got into Debian containing the fix, so this can be a sync again - added SRU template here - uploaded to Focal-unapproved ** Description changed: + [Impact] + + * The "Port" option in sshd_config is accumulative, but due to a bug re- +adds the default when an include is encountered. Therefore we have these +cases +a) Port 722 + Listens on 722 (correct) +b) Port 722 + Port + Listens on 722 & (correct) +c) Port 722 + include /path/to/otherconfig + Listens on 722 & 22 (applied defaults as if Port was unset) + + * Of the above (c) is a bug, not documented that way and can lead to open +ports not expected and not wanted. + + [Test Case] + + * Test if defaults are applied even if option is specified + + Rename sshd_config to something_else and replace sshd_config with two + lines to include the original config (now called something_else) and set + the Port to 7722: + + systemctl stop ssh + mv /etc/ssh/sshd_config /etc/ssh/something_else + cat > /etc/ssh/sshd_config
[Bug 1882483] Re: ThinkPad P1 Gen 2 does not boot
nvidia drivers are not loaded, please install nvidia-driver-440 and try again. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1882483 Title: ThinkPad P1 Gen 2 does not boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1882483/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1881687] Re: Desktop is blank after logging in without a monitor attached
Thanks. Here is the issue in the gnome-shell tracker: https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/2883 ** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/-/issues #2883 https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/2883 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1881687 Title: Desktop is blank after logging in without a monitor attached To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1881687/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1882487] Re: USB headset stops working
This is the log from when I plug the device from the working port into the misbehaving port: Jun 08 00:27:24 cerberus kernel: debugfs: Directory '26' with parent 'devices' already present! Jun 08 00:27:24 cerberus kernel: usb 3-11.3: new full-speed USB device number 65 using xhci_hcd Jun 08 00:27:24 cerberus sshd[47656]: Failed password for root from 139.199.115.133 port 38408 ssh2 Jun 08 00:27:25 cerberus sshd[47656]: Received disconnect from 139.199.115.133 port 38408:11: Bye Bye [preauth] Jun 08 00:27:25 cerberus sshd[47656]: Disconnected from authenticating user root 139.199.115.133 port 38408 [preauth] Jun 08 00:27:25 cerberus kernel: usb 3-11.3: Device not responding to setup address. Jun 08 00:27:25 cerberus kernel: debugfs: Directory '05' with parent 'devices' already present! Jun 08 00:27:25 cerberus kernel: usb 3-11.3: device descriptor read/all, error -32 Jun 08 00:27:25 cerberus kernel: debugfs: Directory '16' with parent 'devices' already present! Jun 08 00:27:25 cerberus kernel: usb 3-11.3: new full-speed USB device number 66 using xhci_hcd Jun 08 00:27:25 cerberus kernel: usb 3-11.3: Device not responding to setup address. Jun 08 00:27:25 cerberus kernel: debugfs: Directory '29' with parent 'devices' already present! Jun 08 00:27:25 cerberus sshd[47658]: Failed password for root from 213.183.101.89 port 40696 ssh2 Jun 08 00:27:26 cerberus sshd[47658]: Received disconnect from 213.183.101.89 port 40696:11: Bye Bye [preauth] Jun 08 00:27:26 cerberus sshd[47658]: Disconnected from authenticating user root 213.183.101.89 port 40696 [preauth] Jun 08 00:27:26 cerberus kernel: usb 3-11.3: device descriptor read/all, error -32 Jun 08 00:27:26 cerberus kernel: usb 3-11-port3: attempt power cycle Jun 08 00:27:26 cerberus kernel: debugfs: Directory '22' with parent 'devices' already present! Jun 08 00:27:26 cerberus kernel: usb 3-11.3: new full-speed USB device number 67 using xhci_hcd Jun 08 00:27:26 cerberus kernel: usb 3-11.3: Device not responding to setup address. Jun 08 00:27:26 cerberus kernel: debugfs: Directory '02' with parent 'devices' already present! Jun 08 00:27:26 cerberus kernel: usb 3-11.3: device descriptor read/8, error -32 Jun 08 00:27:27 cerberus kernel: usb 3-11.3: device descriptor read/8, error -32 Jun 08 00:27:27 cerberus kernel: debugfs: Directory '08' with parent 'devices' already present! Jun 08 00:27:27 cerberus kernel: usb 3-11.3: new full-speed USB device number 68 using xhci_hcd Jun 08 00:27:27 cerberus kernel: usb 3-11.3: Device not responding to setup address. Jun 08 00:27:27 cerberus kernel: debugfs: Directory '15' with parent 'devices' already present! Jun 08 00:27:27 cerberus kernel: usb 3-11.3: device descriptor read/8, error -32 Jun 08 00:27:27 cerberus kernel: usb 3-11.3: device descriptor read/8, error -32 Jun 08 00:27:27 cerberus kernel: usb 3-11-port3: unable to enumerate USB device -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1882487 Title: USB headset stops working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta-hwe/+bug/1882487/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1882487] [NEW] USB headset stops working
Public bug reported: root@cerberus:/var/log# lsb_release -rd Description:Ubuntu 18.04.4 LTS Release:18.04 jlquinn@cerberus:~$ apt-cache policy linux-generic-hwe-18.04 linux-generic-hwe-18.04: Installed: 5.3.0.53.110 Candidate: 5.3.0.53.110 I have a Logitech usb headset that stopped working for unknown reasons. It had been working fine, then seems deactivated. There is a light on the volume control that is no longer lit up. Surprisingly, if I did lsusb, the light briefly lights up, and shuts off. It is plugged into a usb hub on my monitor which had been working fine for a couple months. I plugged it into a different usb on the computer itself, and the headset starts working as expected. Plugging it back into the monitor hub, I see the light on the device flash a couple times, then shut off. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-generic-hwe-18.04 5.3.0.53.110 ProcVersionSignature: Ubuntu 5.3.0-53.47~18.04.1-generic 5.3.18 Uname: Linux 5.3.0-53-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.15 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Jun 8 00:16:57 2020 InstallationDate: Installed on 2020-05-29 (9 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-meta-hwe UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-meta-hwe (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1882487 Title: USB headset stops working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta-hwe/+bug/1882487/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1882487] Re: USB headset stops working
Here's what seems like the relevant portion of the kernel log where the device log appears ok, and where it starts to go bad. Jun 6 17:44:12 cerberus kernel: [620023.619292] hid-generic 0003:046D:0A8F.0045: input,hidraw7: USB HID v1.11 Device [Logitech USB Headset Logitech USB Headset] on usb-:00:14. 0-11.3/input3 Jun 6 19:24:43 cerberus kernel: [626054.614288] usb 3-11: USB disconnect, device number 126 Jun 6 19:24:43 cerberus kernel: [626054.614292] usb 3-11.3: USB disconnect, device number 127 Jun 6 19:24:45 cerberus kernel: [626056.528798] usb 4-4: Disable of device-initiated U1 failed. Jun 6 19:24:45 cerberus kernel: [626056.532295] usb 4-4: Disable of device-initiated U2 failed. Jun 6 19:24:45 cerberus kernel: [626056.657614] usb 4-4: reset SuperSpeed Gen 1 USB device number 15 using xhci_hcd Jun 6 19:24:45 cerberus kernel: [626057.041278] usb 3-11: new high-speed USB device number 5 using xhci_hcd Jun 6 19:24:45 cerberus kernel: [626057.063343] usb 3-11: New USB device found, idVendor=2109, idProduct=2811, bcdDevice=90.90 Jun 6 19:24:45 cerberus kernel: [626057.063348] usb 3-11: New USB device strings: Mfr=1, Product=2, SerialNumber=0 Jun 6 19:24:45 cerberus kernel: [626057.063350] usb 3-11: Product: USB2.0 Hub Jun 6 19:24:45 cerberus kernel: [626057.063352] usb 3-11: Manufacturer: VIA Labs, Inc. Jun 6 19:24:45 cerberus kernel: [626057.064033] hub 3-11:1.0: USB hub found Jun 6 19:24:45 cerberus kernel: [626057.064165] hub 3-11:1.0: 4 ports detected Jun 6 19:24:46 cerberus kernel: [626057.369269] usb 3-11.3: new full-speed USB device number 7 using xhci_hcd Jun 6 19:24:47 cerberus kernel: [626058.789112] usb 3-11.3: New USB device found, idVendor=046d, idProduct=0a8f, bcdDevice= 0.12 Jun 6 19:24:47 cerberus kernel: [626058.789116] usb 3-11.3: New USB device strings: Mfr=3, Product=1, SerialNumber=0 Jun 6 19:24:47 cerberus kernel: [626058.789119] usb 3-11.3: Product: Logitech USB Headset Jun 6 19:24:47 cerberus kernel: [626058.789121] usb 3-11.3: Manufacturer: Logitech USB Headset Jun 6 19:24:48 cerberus kernel: [626059.379000] input: Logitech USB Headset Logitech USB Headset as /devices/pci:00/:00:14.0/usb3/3-11/3-11.3/3-11.3:1.3/0003:046D:0A8F.004 6/input/input94 Jun 6 19:24:48 cerberus kernel: [626059.437566] hid-generic 0003:046D:0A8F.0046: input,hidraw7: USB HID v1.11 Device [Logitech USB Headset Logitech USB Headset] on usb-:00:14. 0-11.3/input3 Jun 6 19:38:00 cerberus kernel: [626852.308189] usb 3-11: USB disconnect, device number 5 Jun 6 19:38:00 cerberus kernel: [626852.308193] usb 3-11.3: USB disconnect, device number 7 Jun 6 19:38:04 cerberus kernel: [626855.724635] usb 4-4: Disable of device-initiated U1 failed. Jun 6 19:38:04 cerberus kernel: [626855.728132] usb 4-4: Disable of device-initiated U2 failed. Jun 6 19:38:04 cerberus kernel: [626855.853383] usb 4-4: reset SuperSpeed Gen 1 USB device number 15 using xhci_hcd Jun 6 19:38:04 cerberus kernel: [626856.241122] usb 3-11: new high-speed USB device number 8 using xhci_hcd Jun 6 19:38:04 cerberus kernel: [626856.263123] usb 3-11: New USB device found, idVendor=2109, idProduct=2811, bcdDevice=90.90 Jun 6 19:38:04 cerberus kernel: [626856.263126] usb 3-11: New USB device strings: Mfr=1, Product=2, SerialNumber=0 Jun 6 19:38:04 cerberus kernel: [626856.263129] usb 3-11: Product: USB2.0 Hub Jun 6 19:38:04 cerberus kernel: [626856.263131] usb 3-11: Manufacturer: VIA Labs, Inc. Jun 6 19:38:04 cerberus kernel: [626856.263786] hub 3-11:1.0: USB hub found Jun 6 19:38:04 cerberus kernel: [626856.263916] hub 3-11:1.0: 4 ports detected Jun 6 19:38:05 cerberus kernel: [626856.569115] usb 3-11.3: new full-speed USB device number 10 using xhci_hcd Jun 6 19:38:06 cerberus kernel: [626857.981374] usb 3-11.3: New USB device found, idVendor=046d, idProduct=0a8f, bcdDevice= 0.12 Jun 6 19:38:06 cerberus kernel: [626857.981378] usb 3-11.3: New USB device strings: Mfr=3, Product=1, SerialNumber=0 Jun 6 19:38:06 cerberus kernel: [626857.981381] usb 3-11.3: Product: Logitech USB Headset Jun 6 19:38:06 cerberus kernel: [626857.981383] usb 3-11.3: Manufacturer: Logitech USB Headset Jun 6 19:38:07 cerberus kernel: [626858.567678] input: Logitech USB Headset Logitech USB Headset as /devices/pci:00/:00:14.0/usb3/3-11/3-11.3/3-11.3:1.3/0003:046D:0A8F.0047/input/input95 Jun 6 19:38:06 cerberus kernel: [626857.981383] usb 3-11.3: Manufacturer: Logitech USB Headset Jun 6 19:38:07 cerberus kernel: [626858.567678] input: Logitech USB Headset Logitech USB Headset as /devices/pci:00/:00:14.0/usb3/3-11/3-11.3/3-11.3:1.3/0003:046D:0A8F.004 7/input/input95 Jun 6 19:38:07 cerberus kernel: [626858.625328] hid-generic 0003:046D:0A8F.0047: input,hidraw7: USB HID v1.11 Device [Logitech USB Headset Logitech USB Headset] on usb-:00:14. 0-11.3/input3 Jun 6 19:38:08 cerberus kernel: [626859.692643] usb 3-11: USB
[Bug 1856434] Re: blk_update_request: I/O error, dev sdb, sector 976772992 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 0
Thanks Joel, the firmware you posted worked for us. I will note we have the HBA330 mini, which has it's own distinct upgrade file as opposed to the regular HBA330. HBA330 mini: https://www.dell.com/support/home/en-au/drivers/driversdetails?driverid=124x2 i'm still a bit puzzled why a firmware update fixed this, since our rhel7 servers did not experience the issue, only Ubuntu (hence i was expecting a kernel driver issue/regression). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1856434 Title: blk_update_request: I/O error, dev sdb, sector 976772992 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1856434/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1882482] Re: Ubuntu 16.04LTS setup can success in my Laptop(HP-Compaq_nc6400) by required a previous windows OS Setup which have a partition active. When I am trying the setup without other OS Ex
Thank you for taking the time to report this bug and helping to make Ubuntu better. We noticed that you were installing the LTS version of Ubuntu using an older version of the installation media. The latest point release of 16.04 is 16.04.3. Please try installing from that version of the installation media and see if that resolves your issue. Thanks in advance! [This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.] ** Changed in: ubiquity (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/1882482 Title: Ubuntu 16.04LTS setup can success in my Laptop(HP-Compaq_nc6400) by required a previous windows OS Setup which have a partition active. When I am trying the setup without other OS Exist or any mass storage (as a blank Hard Disk)- it shows error to setup Ubuntu. So using reporting option just telling you the problem to improve the development forums. Thank you To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1882482/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1871385] Re: gnome-control-center crashed with SIGSEGV in _cogl_gpu_info_parse_version_string()
[Expired for gnome-control-center (Ubuntu) because there has been no activity for 60 days.] ** Changed in: gnome-control-center (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/1871385 Title: gnome-control-center crashed with SIGSEGV in _cogl_gpu_info_parse_version_string() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1871385/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1868988] Re: apt assert failure: malloc(): mismatching next->prev_size (unsorted)
[Expired for apt (Ubuntu) because there has been no activity for 60 days.] ** Changed in: apt (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/1868988 Title: apt assert failure: malloc(): mismatching next->prev_size (unsorted) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1868988/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1871536] Re: "Ubuntu Software" icon absent from dash after installing 20.04 beta
[Expired for gnome-software (Ubuntu) because there has been no activity for 60 days.] ** Changed in: gnome-software (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/1871536 Title: "Ubuntu Software" icon absent from dash after installing 20.04 beta To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1871536/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1871727] Re: 20.04 grub flashes on login Dell laptop 10gen. Chip
[Expired for syslinux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: syslinux (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/1871727 Title: 20.04 grub flashes on login Dell laptop 10gen. Chip To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/syslinux/+bug/1871727/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1871562] Re: [ThinkPad P1 and ThinkPad X1 Extreme] System got hang during the first boot.
[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/1871562 Title: [ThinkPad P1 and ThinkPad X1 Extreme] System got hang during the first boot. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1871562/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1882480] Re: nvme driver issue causing massive system lag on resume from suspend
** Description changed: When I resume from suspend, my system initially appears to be frozen. The screen is black and/or the input devices are not working. After several minutes, I can switch to a console (and then to the desktop) but the system is under full load, to the point that even trivial commands will take up to three minutes to execute. The only way out of this situation is to do a reboot. I see that dmesg is showing an NVME related stack trace and then the repeating message "timeout, completion polled". I ran into the same issue a few months ago when I started using my current motherboard (ASUS Prime x470-PRO). It got solved by flashing my BIOS to the latest version. ASUS have not put out any newer since then so I guess this will require a kernel fix. + UPDATE: this would appear to be happening only when I run my CPU in + powersave mode (reduced speed and 4-6 vCPUs disabled). + release: ubuntu 20.04 kernel: Linux Dapple 5.4.0-33-generic #37-Ubuntu SMP Thu May 21 12:53:59 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux also tried kernel: Linux Dapple 5.4.0-34-generic #38-Ubuntu SMP Mon May 25 15:46:55 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux (developer repository) - ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-33-generic 5.4.0-33.37 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Uname: Linux 5.4.0-33-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jurgen 1998 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Jun 8 04:43:36 2020 InstallationDate: Installed on 2020-04-05 (63 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) IwConfig: lono wireless extensions. enp10s0 no wireless extensions. MachineType: System manufacturer System Product Name ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-33-generic root=UUID=2b0aa93b-fb72-4ce6-a28a-0569be4848ea ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-33-generic N/A linux-backports-modules-5.4.0-33-generic N/A linux-firmware1.187 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/13/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 5406 dmi.board.asset.tag: Default string dmi.board.name: PRIME X470-PRO dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr5406:bd11/13/2019:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEX470-PRO:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1882480 Title: nvme driver issue causing massive system lag on resume from suspend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1882480/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1882481] Re: A dialog box stays on desktop and does not go away
This sounds like bug 1824874. To help us check that please: 1. Provide a screenshot or photo of the problem; and 2. After the dialog has appeared run: journalctl -b0 > journal.txt or if you had to reboot then run: journalctl -b-1 > prevboot.txt and attach the resulting text file here. ** Package changed: xorg (Ubuntu) => gnome-shell (Ubuntu) ** Changed in: gnome-shell (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/1882481 Title: A dialog box stays on desktop and does not go away To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1882481/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1882481] Re: A dialog box stays on desktop and does not go away
** 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/1882481 Title: A dialog box stays on desktop and does not go away To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1882481/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1881669] Re: Object .Gjs_AppIndicatorIconActor__1 (0x5582a2e9b240), has been already finalized. Impossible to set any property to it
** Changed in: gnome-shell-extension-appindicator (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/1881669 Title: Object .Gjs_AppIndicatorIconActor__1 (0x5582a2e9b240), has been already finalized. Impossible to set any property to it To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-appindicator/+bug/1881669/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1882212] Re: Cursor blinks/flickers on screen refresh (only on built in monitor)
I suggest using 'Ubuntu on Wayland' as a workaround. You can fix the "too small" problem by running: gsettings set org.gnome.mutter experimental-features "['scale-monitor- framebuffer','x11-randr-fractional-scaling']" and then log into 'Ubuntu on Wayland' again. You should now have fractional scaling options and without this bug. ** Tags added: multimonitor ** Changed in: mutter (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/1882212 Title: Cursor blinks/flickers on screen refresh (only on built in monitor) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1882212/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1882478] Re: smpboot: don't call topology_sane() when Sub-NUMA-Clustering is enabled
** Description changed: BugLink: https://bugs.launchpad.net/bugs/1882478 [Impact] Intel Skylake server processors and onward have a different Last Level Cache (LLC) topology than earlier processors, and such processors have a new feature called Sub-NUMA-Clustering (SNC) which is similar to the existing Cluster-On-Die (CoD) feature earlier server processors has. Sub-NUMA-Clustering divides the system into two "slices", each of which are allocated half the CPU cores, half the Last Level Cache and one memory controller. Each slice is enumerated as a NUMA node. The difference between Sub-NUMA-Clustering and Cluster-On-Die is how the Last Level Cache is exposed to each NUMA node. CoD had the same cache line present in each half of the LLC. In SNC, each cache line is only present in its respective slice. Because of this, the semantics around accessing LLC changes, with a process accessing NUMA-local memory only seeing half the LLC capacity. On systems with Sub-NUMA-Clustering enabled, on the Xenial 4.4 and Bionic 4.15 kernels we see the following oops during NUMA node enumeration: node #0, CPUs: #1 #2 #3 #4 #5 #6 node #1, CPUs: #7 sched: CPU #7's llc-sibling CPU #0 is not on the same node! [node: 1 != 0]. Ignoring dependency. WARNING: CPU: 7 PID: 0 at /build/linux-hwe-F5opqf/linux-hwe-4.15.0/arch/x86/kernel/smpboot.c:375 topology_sane.isra.4+0x6c/0x70 Modules linked in: CPU: 7 PID: 0 Comm: swapper/7 Not tainted 4.15.0-47-generic #50~16.04.1-Ubuntu Hardware name: HPE ProLiant DL360 Gen10/ProLiant DL360 Gen10, BIOS U32 10/02/2018 RIP: 0010:topology_sane.isra.4+0x6c/0x70 Call Trace: set_cpu_sibling_map+0x153/0x540 start_secondary+0xb2/0x200 secondary_startup_64+0xa5/0xb0 #8 #9 #10 #11 #12 #13 node #0, CPUs: #14 #15 #16 #17 #18 #19 #20 node #1, CPUs: #21 #22 #23 #24 #25 #26 #27 smp: Brought up 2 nodes, 28 CPUs This was with a Intel Xeon Gold 5120 CPU on a HP DL360 Gen10. The oops happens because topology_sane() checks to see if the Last Level Cache line matches across different CPUs, which it no longer does. [Fix] The fix comes in the form of the following upstream commit, which landed in Linux 4.17: commit 1340ccfa9a9afefdbab90d7935d4ed19817e37c2 Author: Alison Schofield Date: Fri Apr 6 17:21:30 2018 -0700 Subject: x86,sched: Allow topologies where NUMA nodes share an LLC Link: https://github.com/torvalds/linux/commit/1340ccfa9a9afefdbab90d7935d4ed19817e37c2 The commit adds a check for this particular family of Intel processors, and if the CPU family matches, it simply skips the check to topology_sane(). The commit needs minor backports to Xenial 4.4 and Bionic 4.15, with the only remarks being re-arranging #includes and small context fixups. [Testcase] Unfortunately, this is hardware specific. To test this, you need a Intel Skylake server processor which supports Sub-NUMA-Clustering. We have a customer with a Intel Xeon Gold 5120 CPU on a HP DL360 Gen10 that has successfully tested the below test kernels, with good results. Xenial 4.4 ppa: https://launchpad.net/~mruffell/+archive/ubuntu/sf280048-test-ga Xenial 4.15 HWE ppa: https://launchpad.net/~mruffell/+archive/ubuntu/sf280048-test-hwe Running the test kernel, the oops does not reproduce: smp: Bringing up secondary CPUs ... x86: Booting SMP configuration: node #0, CPUs: #1 NMI watchdog: Enabled. Permanently consumes one hw-PMU counter. #2 #3 #4 #5 #6 node #1, CPUs: #7 #8 #9 #10 #11 #12 #13 node #0, CPUs: #14 #15 #16 #17 #18 #19 #20 node #1, CPUs: #21 #22 #23 #24 #25 #26 #27 smp: Brought up 2 nodes, 28 CPUs smpboot: Max logical packages: 1 smpboot: Total of 28 processors activated [Regression Potential] The commit modifies a small section of smpboot code, which every machine will execute on boot. The majority of the commit breaks up a large if statement into smaller blocks than it was previously, and adds an extra if statement to check for a specific processor family. If a regression were to occur, some machines would or would not make their calls to topology_sane(), which in the worst case, would result in a oops message and slightly degraded performance. The system would still function normally. The commit has been present since 4.17-rc2 and is present in Eoan and Focal. There are no fixup commits, and no additional processor families have been added since. Because of the small re-arrangement in logic, and the addition of a - processor family check, these changes a fairly minor, and I don't think - it will cause any regressions. + processor family check, these changes are fairly minor, and I don't + think it will cause any regressions. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.
[Bug 1882484] [NEW] Firewall rule in before.rules for dhcp is wrong
Public bug reported: The file delivered - /usr/share/ufw/iptables/before.rules which is then copied to - /etc/ufw/before.rules Delivered by Package: # allow dhcp client to work -A ufw-before-input -p udp --sport 67 --dport 68 -j ACCEPT The ports for --sport and --dport are swapped Should be: -A ufw-before-input -p udp --sport 68 --dport 67 -j ACCEPT Package version found in: 0.36-0ubuntu0.1 Note: ISC DHCP uses RAW sockets, which bypasses iptables anyway and doesn't drop the packets with the incorrect configuration. This has had me stumped for the last hour. ** Affects: ufw (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/1882484 Title: Firewall rule in before.rules for dhcp is wrong To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ufw/+bug/1882484/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1882483] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (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/1882483 Title: ThinkPad P1 Gen 2 does not boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1882483/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1880954] Re: Ubuntu 20.04 freezes when logging in with external monitors connected
An upstream bug: https://gitlab.gnome.org/GNOME/mutter/-/issues/938 suggests that: Error setting property 'PowerSaveMode' on interface org.gnome.Mutter.DisplayConfig: Timeout was reached (g-io-error-quark, 24) is a symptom and not the problem. So... Thank you for taking the time to report this bug and helping to make Ubuntu better. It sounds like some part of the system has crashed. To help us find the cause of the crash please follow these steps: 1. Look in /var/crash for crash files and if found run: ubuntu-bug YOURFILE.crash Then tell us the ID of the newly-created bug. 2. If step 1 failed then look at https://errors.ubuntu.com/user/ID where ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine. Do you find any links to recent problems on that page? If so then please send the links to us. 3. If step 2 also failed then apply the workaround from bug 994921, reboot, reproduce the crash, and retry step 1. Please take care to avoid attaching .crash files to bugs as we are unable to process them as file attachments. It would also be a security risk for yourself. ** Summary changed: - Ubuntu 20.04 freezes when logging in + Ubuntu 20.04 freezes when logging in with external monitors connected ** Tags added: multimonitor ** Also affects: mutter (Ubuntu) Importance: Undecided Status: New ** Bug watch added: gitlab.gnome.org/GNOME/mutter/-/issues #938 https://gitlab.gnome.org/GNOME/mutter/-/issues/938 ** Also affects: mutter via https://gitlab.gnome.org/GNOME/mutter/-/issues/938 Importance: Unknown Status: Unknown ** Summary changed: - Ubuntu 20.04 freezes when logging in with external monitors connected + Ubuntu 20.04 freezes when logging in with external monitors connected [Error setting property 'PowerSaveMode' on interface org.gnome.Mutter.DisplayConfig: Timeout was reached (g-io-error-quark, 24)] ** Also affects: gnome-settings-daemon (Ubuntu) Importance: Undecided Status: New ** No longer affects: mutter ** No longer affects: gnome-settings-daemon (Ubuntu) ** Changed in: mutter (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/1880954 Title: Ubuntu 20.04 freezes when logging in with external monitors connected [Error setting property 'PowerSaveMode' on interface org.gnome.Mutter.DisplayConfig: Timeout was reached (g-io-error-quark, 24)] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1880954/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1870971] Re: [amdgpu] Xubuntu 20.04 boots to black screen on Lenovo Ideapad L340-17API
Seen on ThinkPad E495. Updated BIOS to 1.16 -- good but did NOT solve this particular issue. Still getting the boot-to-black issue on battery power, on a random basis. Attempting the workaround from Alexander in #3 and #5. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1870971 Title: [amdgpu] Xubuntu 20.04 boots to black screen on Lenovo Ideapad L340-17API To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1870971/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1882483] [NEW] ThinkPad P1 Gen 2 does not boot
Public bug reported: Hi, Kernels > 5.4.0-28 can not boot Ubuntu 20.04 when *NO* HDMI monitor plugged. Kernels > 5.4.0-28 can boot Ubuntu 20.04 when HDMI monitor plugged. There is also a separate problem: No wake up after hibernation, only repeated sound without screen image - physical shutdown is only workaround I have. Thank you, Igor ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-modules-5.4.0-33-generic 5.4.0-33.37 ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30 Uname: Linux 5.4.0-28-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: igor 2358 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Jun 8 05:37:59 2020 Dependencies: InstallationDate: Installed on 2020-04-01 (67 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200331) MachineType: LENOVO 20QTCTO1WW ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-28-generic root=UUID=f0159a4a-cd4b-48f7-8119-f697cb539ce5 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-28-generic N/A linux-backports-modules-5.4.0-28-generic N/A linux-firmware1.187 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/20/2020 dmi.bios.vendor: LENOVO dmi.bios.version: N2OET42W (1.29 ) dmi.board.asset.tag: Not Available dmi.board.name: 20QTCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0R32862 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN2OET42W(1.29):bd01/20/2020:svnLENOVO:pn20QTCTO1WW:pvrThinkPadP1Gen2:rvnLENOVO:rn20QTCTO1WW:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad P1 Gen 2 dmi.product.name: 20QTCTO1WW dmi.product.sku: LENOVO_MT_20QT_BU_Think_FM_ThinkPad P1 Gen 2 dmi.product.version: ThinkPad P1 Gen 2 dmi.sys.vendor: LENOVO ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1882483 Title: ThinkPad P1 Gen 2 does not boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1882483/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1880640] Re: unable to create '/bin/systemd-hwdb.dpkg-new' (while processing './bin/systemd- hwdb'): Operation not permitted
*** This bug is a duplicate of bug 1874887 *** https://bugs.launchpad.net/bugs/1874887 ** This bug has been marked a duplicate of bug 1874887 package udev 245.4-4ubuntu3 failed to install/upgrade: installed udev package post-installation script subprocess returned error exit status 1 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1880640 Title: unable to create '/bin/systemd-hwdb.dpkg-new' (while processing './bin/systemd- hwdb'): Operation not permitted To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1880640/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1882482] [NEW] Ubuntu 16.04LTS setup can success in my Laptop(HP-Compaq_nc6400) by required a previous windows OS Setup which have a partition active. When I am trying the setup without other OS
Public bug reported: For users need to get help setup in NTFS-communities - I want to request authors for make the option in system to backup the partition into an image-file which can load with windowsOS boot option. Best technique is the setup progress could select the NTFS-partition by .img-file such as Android setup in NTFS. If any related apps can define, please tell me link. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: ubiquity 2.21.63 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic i686 ApportVersion: 2.20.1-0ubuntu2 Architecture: i386 CasperVersion: 1.376 Date: Mon Jun 8 05:08:41 2020 InstallCmdLine: file=/cdrom/preseed/ubuntu.seed boot=casper only-ubiquity cdrom-detect/try-usb=true noprompt floppy.allowed_drive_mask=0 ignore_uuid initrd=/casper/initrd.lz quiet splash --- BOOT_IMAGE=/casper/vmlinuz LiveMediaBuild: Ubuntu 16.04 LTS "Xenial Xerus" - Release i386 (20160420.1) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ubiquity (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 ubiquity-2.21.63 ubuntu xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1882482 Title: Ubuntu 16.04LTS setup can success in my Laptop(HP-Compaq_nc6400) by required a previous windows OS Setup which have a partition active. When I am trying the setup without other OS Exist or any mass storage (as a blank Hard Disk)- it shows error to setup Ubuntu. So using reporting option just telling you the problem to improve the development forums. Thank you To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1882482/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1808418] Re: Thinkpad T430u won't boot without noapic workaround
$ rmadison linux When groovy jumps to 5.7, it's time to change. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1808418 Title: Thinkpad T430u won't boot without noapic workaround To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1808418/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1882480] Re: nvme driver issue causing massive system lag on resume from suspend
** Description changed: When I resume from suspend, my system initially appears to be frozen. The screen is black and/or the input devices are not working. After several minutes, I can switch to a console (and then to the desktop) but the system is under full load, to the point that even trivial commands will take up to three minutes to execute. The only way out of this situation is to do a reboot. I see that dmesg is showing an NVME related stack trace and then the repeating message "timeout, completion polled". I ran into the same issue a few months ago when I started using my current motherboard (ASUS Prime x470-PRO). It got solved by flashing my BIOS to the latest version. ASUS have not put out any newer since then so I guess this will require a kernel fix. release: ubuntu 20.04 kernel: Linux Dapple 5.4.0-33-generic #37-Ubuntu SMP Thu May 21 12:53:59 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux + also tried kernel: Linux Dapple 5.4.0-34-generic #38-Ubuntu SMP Mon May 25 15:46:55 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux (developer repository) + ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-33-generic 5.4.0-33.37 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Uname: Linux 5.4.0-33-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 AudioDevicesInUse: - USERPID ACCESS COMMAND - /dev/snd/controlC0: jurgen 1998 F pulseaudio + USERPID ACCESS COMMAND + /dev/snd/controlC0: jurgen 1998 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Jun 8 04:43:36 2020 InstallationDate: Installed on 2020-04-05 (63 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) IwConfig: - lono wireless extensions. - - enp10s0 no wireless extensions. + lono wireless extensions. + + enp10s0 no wireless extensions. MachineType: System manufacturer System Product Name ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-33-generic root=UUID=2b0aa93b-fb72-4ce6-a28a-0569be4848ea ro quiet splash vt.handoff=7 RelatedPackageVersions: - linux-restricted-modules-5.4.0-33-generic N/A - linux-backports-modules-5.4.0-33-generic N/A - linux-firmware1.187 + linux-restricted-modules-5.4.0-33-generic N/A + linux-backports-modules-5.4.0-33-generic N/A + linux-firmware1.187 RfKill: - + SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/13/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 5406 dmi.board.asset.tag: Default string dmi.board.name: PRIME X470-PRO dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr5406:bd11/13/2019:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEX470-PRO:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1882480 Title: nvme driver issue causing massive system lag on resume from suspend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1882480/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1882481] [NEW] A dialog box stays on desktop and does not go away
Public bug reported: Upon rebooting, I get dialog box Authentication Required Authentication is required to start 'cups.service'. I can type in the password and click Authenticate, but then nothing happens. I can't see under the box. I can't move the box, can't cancel the dialog. But, I can click on where I know the underneath icon to be and that click is accepted and the program in question runs. It appears the display manager does not remove the image after it is done with the dialog. I have recently done a clean install of 20.04. There is a screenshot in this Stack Exchange post: https://askubuntu.com/questions/1242999/dialog-box-does-not-accept-input-stays-on-top-and-hides-everything-under-it-ub ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Uname: Linux 5.4.0-33-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Jun 7 23:10:43 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: amdgpu, 3.3-19, 5.4.0-31-generic, x86_64: installed amdgpu, 3.3-19, 5.4.0-33-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon RX 470/480/570/570X/580/580X/590] [1002:67df] (rev e7) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] Radeon RX 580 [1462:8a92] InstallationDate: Installed on 2020-05-12 (26 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: System manufacturer System Product Name ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-33-generic root=UUID=ebb08f84-7501-4461-a5c4-c69c3c25d9b0 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/30/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0804 dmi.board.asset.tag: Default string dmi.board.name: ROG ZENITH EXTREME dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0804:bd11/30/2017:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGZENITHEXTREME:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz 1:0.9.14.1+20.04.20200211-0ubuntu1 version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2 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/1882481 Title: A dialog box stays on desktop and does not go away To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1882481/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1882480] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (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/1882480 Title: nvme driver issue causing massive system lag on resume from suspend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1882480/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1882480] Re: nvme driver issue causing massive system lag on resume from suspend
I am including the output of the dmesg command as ran immediately after resume from suspend - it shows the stack trace I am referring to in my bug report. ** Attachment added: "dmesg_2020-06-08_04:12.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1882480/+attachment/5381446/+files/dmesg_2020-06-08_04%3A12.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1882480 Title: nvme driver issue causing massive system lag on resume from suspend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1882480/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1882480] [NEW] nvme driver issue causing massive system lag on resume from suspend
Public bug reported: When I resume from suspend, my system initially appears to be frozen. The screen is black and/or the input devices are not working. After several minutes, I can switch to a console (and then to the desktop) but the system is under full load, to the point that even trivial commands will take up to three minutes to execute. The only way out of this situation is to do a reboot. I see that dmesg is showing an NVME related stack trace and then the repeating message "timeout, completion polled". I ran into the same issue a few months ago when I started using my current motherboard (ASUS Prime x470-PRO). It got solved by flashing my BIOS to the latest version. ASUS have not put out any newer since then so I guess this will require a kernel fix. release: ubuntu 20.04 kernel: Linux Dapple 5.4.0-33-generic #37-Ubuntu SMP Thu May 21 12:53:59 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-33-generic 5.4.0-33.37 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Uname: Linux 5.4.0-33-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jurgen 1998 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Jun 8 04:43:36 2020 InstallationDate: Installed on 2020-04-05 (63 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) IwConfig: lono wireless extensions. enp10s0 no wireless extensions. MachineType: System manufacturer System Product Name ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-33-generic root=UUID=2b0aa93b-fb72-4ce6-a28a-0569be4848ea ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-33-generic N/A linux-backports-modules-5.4.0-33-generic N/A linux-firmware1.187 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/13/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 5406 dmi.board.asset.tag: Default string dmi.board.name: PRIME X470-PRO dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr5406:bd11/13/2019:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEX470-PRO:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** 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/1882480 Title: nvme driver issue causing massive system lag on resume from suspend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1882480/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1882410] Re: GNOME Shell crashed with signal 5
alas there are 2 files in /var/crash neither of them line up with when the crash happened nothing in https://errors.ubuntu.com/user/ID since 2017 I've made the change to /etc/apport/crashdb.conf (that was the workaround right?) we'll see when it happens again after I reboot next -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1882410 Title: GNOME Shell crashed with signal 5 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1882410/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1882410] Re: GNOME Shell crashed with signal 5
Thank you for taking the time to report this bug and helping to make Ubuntu better. It sounds like some part of the system has crashed. To help us find the cause of the crash please follow these steps: 1. Look in /var/crash for crash files and if found run: ubuntu-bug YOURFILE.crash Then tell us the ID of the newly-created bug. 2. If step 1 failed then look at https://errors.ubuntu.com/user/ID where ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine. Do you find any links to recent problems on that page? If so then please send the links to us. 3. If step 2 also failed then apply the workaround from bug 994921, reboot, reproduce the crash, and retry step 1. Please take care to avoid attaching .crash files to bugs as we are unable to process them as file attachments. It would also be a security risk for yourself. ** Changed in: gnome-shell (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/1882410 Title: GNOME Shell crashed with signal 5 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1882410/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1882479] [NEW] claws-mail cannot connect to yahoo mail, gnutls problem?
Public bug reported: Distribution: Linux Mint 18.3 Mate Sometime in the last few weeks lost the ability to connect to yahoo IMAP mail using Claws Mail. The problem appears to be coming from gnutls: ~ $ gnutls-cli -V -p 993 imap.mail.yahoo.com Processed 127 CA certificate(s). Resolving 'imap.mail.yahoo.com'... Connecting to '216.155.194.49:993'... - Certificate type: X.509 - Got a certificate list of 2 certificates. - Certificate[0] info: - X.509 Certificate Information: ...snip... -END CERTIFICATE- - Status: The certificate is trusted. - Server's trusted authorities: [0]: C=US,O=Entrust\, Inc.,OU=See www.entrust.net/legal-terms,OU=(c) 2012 Entrust\, Inc. - for authorized use only,CN=Entrust Root Certification Authority - EC1 ...snip... [97]: C=US,O=DigiCert Inc,OU=www.digicert.com,CN=DigiCert Global Root G2 - Successfully sent 0 certificate(s) to server. *** Fatal error: Internal error in memory allocation. *** Handshake has failed GnuTLS error: Internal error in memory allocation. Trying to connect with openssl seems to work. version information: $ gnutls-cli -v gnutls-cli 3.4.10 claws-mail 3.13.2 ** Affects: claws-mail (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/1882479 Title: claws-mail cannot connect to yahoo mail, gnutls problem? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/claws-mail/+bug/1882479/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1878275] Re: wayland session hard freezes on login from GDM (X11 session works fine)
And if all else fails, please attach 'gdb' to the process: sudo gdb /usr/bin/gnome-shell PID and retrieve a backtrace of all threads using: thread apply all bt ** Summary changed: - wayland session hard freezes on login from GDM (X11 session works fine) + [qxl] wayland session hard freezes on login from GDM (X11 session works fine) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1878275 Title: [qxl] wayland session hard freezes on login from GDM (X11 session works fine) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1878275/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1882478] [NEW] smpboot: don't call topology_sane() when Sub-NUMA-Clustering is enabled
Public bug reported: BugLink: https://bugs.launchpad.net/bugs/1882478 [Impact] Intel Skylake server processors and onward have a different Last Level Cache (LLC) topology than earlier processors, and such processors have a new feature called Sub-NUMA-Clustering (SNC) which is similar to the existing Cluster-On-Die (CoD) feature earlier server processors has. Sub-NUMA-Clustering divides the system into two "slices", each of which are allocated half the CPU cores, half the Last Level Cache and one memory controller. Each slice is enumerated as a NUMA node. The difference between Sub-NUMA-Clustering and Cluster-On-Die is how the Last Level Cache is exposed to each NUMA node. CoD had the same cache line present in each half of the LLC. In SNC, each cache line is only present in its respective slice. Because of this, the semantics around accessing LLC changes, with a process accessing NUMA-local memory only seeing half the LLC capacity. On systems with Sub-NUMA-Clustering enabled, on the Xenial 4.4 and Bionic 4.15 kernels we see the following oops during NUMA node enumeration: node #0, CPUs: #1 #2 #3 #4 #5 #6 node #1, CPUs: #7 sched: CPU #7's llc-sibling CPU #0 is not on the same node! [node: 1 != 0]. Ignoring dependency. WARNING: CPU: 7 PID: 0 at /build/linux-hwe-F5opqf/linux-hwe-4.15.0/arch/x86/kernel/smpboot.c:375 topology_sane.isra.4+0x6c/0x70 Modules linked in: CPU: 7 PID: 0 Comm: swapper/7 Not tainted 4.15.0-47-generic #50~16.04.1-Ubuntu Hardware name: HPE ProLiant DL360 Gen10/ProLiant DL360 Gen10, BIOS U32 10/02/2018 RIP: 0010:topology_sane.isra.4+0x6c/0x70 Call Trace: set_cpu_sibling_map+0x153/0x540 start_secondary+0xb2/0x200 secondary_startup_64+0xa5/0xb0 #8 #9 #10 #11 #12 #13 node #0, CPUs: #14 #15 #16 #17 #18 #19 #20 node #1, CPUs: #21 #22 #23 #24 #25 #26 #27 smp: Brought up 2 nodes, 28 CPUs This was with a Intel Xeon Gold 5120 CPU on a HP DL360 Gen10. The oops happens because topology_sane() checks to see if the Last Level Cache line matches across different CPUs, which it no longer does. [Fix] The fix comes in the form of the following upstream commit, which landed in Linux 4.17: commit 1340ccfa9a9afefdbab90d7935d4ed19817e37c2 Author: Alison Schofield Date: Fri Apr 6 17:21:30 2018 -0700 Subject: x86,sched: Allow topologies where NUMA nodes share an LLC Link: https://github.com/torvalds/linux/commit/1340ccfa9a9afefdbab90d7935d4ed19817e37c2 The commit adds a check for this particular family of Intel processors, and if the CPU family matches, it simply skips the check to topology_sane(). The commit needs minor backports to Xenial 4.4 and Bionic 4.15, with the only remarks being re-arranging #includes and small context fixups. [Testcase] Unfortunately, this is hardware specific. To test this, you need a Intel Skylake server processor which supports Sub-NUMA-Clustering. We have a customer with a Intel Xeon Gold 5120 CPU on a HP DL360 Gen10 that has successfully tested the below test kernels, with good results. Xenial 4.4 ppa: https://launchpad.net/~mruffell/+archive/ubuntu/sf280048-test-ga Xenial 4.15 HWE ppa: https://launchpad.net/~mruffell/+archive/ubuntu/sf280048-test-hwe Running the test kernel, the oops does not reproduce: smp: Bringing up secondary CPUs ... x86: Booting SMP configuration: node #0, CPUs: #1 NMI watchdog: Enabled. Permanently consumes one hw-PMU counter. #2 #3 #4 #5 #6 node #1, CPUs: #7 #8 #9 #10 #11 #12 #13 node #0, CPUs: #14 #15 #16 #17 #18 #19 #20 node #1, CPUs: #21 #22 #23 #24 #25 #26 #27 smp: Brought up 2 nodes, 28 CPUs smpboot: Max logical packages: 1 smpboot: Total of 28 processors activated [Regression Potential] The commit modifies a small section of smpboot code, which every machine will execute on boot. The majority of the commit breaks up a large if statement into smaller blocks than it was previously, and adds an extra if statement to check for a specific processor family. If a regression were to occur, some machines would or would not make their calls to topology_sane(), which in the worst case, would result in a oops message and slightly degraded performance. The system would still function normally. The commit has been present since 4.17-rc2 and is present in Eoan and Focal. There are no fixup commits, and no additional processor families have been added since. Because of the small re-arrangement in logic, and the addition of a processor family check, these changes a fairly minor, and I don't think it will cause any regressions. ** Affects: linux (Ubuntu) Importance: Undecided Status: Fix Released ** Affects: linux (Ubuntu Xenial) Importance: Medium Assignee: Matthew Ruffell (mruffell) Status: In Progress ** Affects: linux (Ubuntu Bionic) Importance: Medium Assignee: Matthew Ruffell (mruffell) Status: In Progress ** Tags: sts ** Also affects: linux (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: linux (Ubuntu
[Bug 1878275] Re: wayland session hard freezes on login from GDM (X11 session works fine)
Thanks but that also is failing to retrace. Try a different signal like: kill -SEGV ... ** Changed in: mutter (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1878275 Title: [qxl] wayland session hard freezes on login from GDM (X11 session works fine) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1878275/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1876209] Re: Clementine fails to open application window in 20.04 after 1st run
The underlying issue here is that the systray icon no longer can open the app window. The oods of this being fixed in 20.04 are slim to none so users should change that setting on 1st run of clementine. ** Summary changed: - Clementine fails to open application window in 20.04 after 1st run + Clementine fails to open application window in 20.04 after 1st rundue to default setting & systray icon fails to open app window ** Summary changed: - Clementine fails to open application window in 20.04 after 1st rundue to default setting & systray icon fails to open app window + Clementine fails to open application window in 20.04 after 1st run due to default setting & systray icon fails to open app window -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1876209 Title: Clementine fails to open application window in 20.04 after 1st run due to default setting & systray icon fails to open app window To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/clementine/+bug/1876209/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1878544] Re: kernel NULL pointer dereference when plugging/unpluggin USB-c (power or hub)
@Victor, Sorry, it's my fault. please wait the next released(>= 5.4.0-34) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1878544 Title: kernel NULL pointer dereference when plugging/unpluggin USB-c (power or hub) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1878544/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1882434] Re: gnome-shell crashes on lock screen
Thank you for taking the time to report this bug and helping to make Ubuntu better. Please execute the following command only once, as it will automatically gather debugging information, in a terminal: apport-collect 1882434 When reporting bugs in the future please use apport by using 'ubuntu- bug' and the name of the package affected. You can learn more about this functionality at https://wiki.ubuntu.com/ReportingBugs. ** Changed in: gnome-shell (Ubuntu) Status: New => Incomplete ** Tags added: focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1882434 Title: gnome-shell crashes on lock screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1882434/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1882434] Re: gnome-shell crashes on lock screen
This is probably bug 184. But in case it's not... Thank you for taking the time to report this bug and helping to make Ubuntu better. It sounds like some part of the system has crashed. To help us find the cause of the crash please follow these steps: 1. Look in /var/crash for crash files and if found run: ubuntu-bug YOURFILE.crash Then tell us the ID of the newly-created bug. 2. If step 1 failed then look at https://errors.ubuntu.com/user/ID where ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine. Do you find any links to recent problems on that page? If so then please send the links to us. 3. If step 2 also failed then apply the workaround from bug 994921, reboot, reproduce the crash, and retry step 1. Please take care to avoid attaching .crash files to bugs as we are unable to process them as file attachments. It would also be a security risk for yourself. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1882434 Title: gnome-shell crashes on lock screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1882434/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1882462] Re: Displays wake up pre-maturely (likely driven by notification)
The most common issue we're seeing in this area right now is that gnome- shell crashes on lock, and so locking fails. That's bug 184 with a fix coming soon. Please also check /var/crash in case there is any evidence there (it might be a different crash). Secondly, we find extensions cause a lot of bugs in gnome-shell. So please try without these: 'system-moni...@paradoxxx.zero.gmail.com', 'topic...@phocean.net', 'pixel-sa...@deadalnix.me' ** Changed in: gnome-shell (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/1882462 Title: Displays wake up pre-maturely (likely driven by notification) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1882462/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1843982] Re: Various programs crashed with SIGSEGV in g_str_hash() from g_hash_table_lookup() from update_user()
The upstream bug mentions: > When gdm is configured with AutomaticLogin, restarting accounts- daemon.service causes consumers to crash so it might be possible to verify that way. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1843982 Title: Various programs crashed with SIGSEGV in g_str_hash() from g_hash_table_lookup() from update_user() To manage notifications about this bug go to: https://bugs.launchpad.net/accountsservice/+bug/1843982/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1864287] Re: pulseaudio still trying to reproduce audio to HDMI without the HDMI cable connected
The bug automatically closed because we received no response to comment #1. Please follow the instructions in comment #1 and in comment #5. ** Changed in: pulseaudio (Ubuntu) Status: Expired => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1864287 Title: pulseaudio still trying to reproduce audio to HDMI without the HDMI cable connected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1864287/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1560094] Re: Starting bluez service is denied
In progress? ** Changed in: bluez (Ubuntu) Status: In Progress => Incomplete ** Changed in: bluez (Ubuntu) Assignee: Scott Sweeny (ssweeny) => (unassigned) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1560094 Title: Starting bluez service is denied To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1560094/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1865300] Re: gnome-shell-hotplug-sniffer crashed with SIGSEGV in g_str_hash() from g_hash_table_lookup() from deep_count_more_files_callback()
** Changed in: gnome-shell (Ubuntu) Status: In Progress => Fix Committed ** Changed in: gnome-shell (Ubuntu Focal) Status: In Progress => Fix Committed ** Tags added: fixed-in-3.36.4 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1865300 Title: gnome-shell-hotplug-sniffer crashed with SIGSEGV in g_str_hash() from g_hash_table_lookup() from deep_count_more_files_callback() To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1865300/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1882473] Re: test bug
** Changed in: systemd Status: Unknown => New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1882473 Title: test bug To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1882473/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1882473] Re: test bug
yeah, there is now ability to add url to upstream github issue. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1882473 Title: test bug To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1882473/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1882473] [NEW] test bug
Public bug reported: test upstream bug ** Affects: systemd Importance: Unknown Status: New ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Bug watch added: github.com/systemd/systemd/issues #16090 https://github.com/systemd/systemd/issues/16090 ** Also affects: systemd via https://github.com/systemd/systemd/issues/16090 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1882473 Title: test bug To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1882473/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1327801] Re: Bightness and contrast settings have no effect
It is only an issue with the out of the box drivers, installing the proper Epson drivers and importantly, configuring the Network Plugin, solves the matter for me. http://download.ebz.epson.net/man/linux/imagescanv3_e.html#sec6-1 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1327801 Title: Bightness and contrast settings have no effect To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/simple-scan/+bug/1327801/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1810176] Re: libmtp error could not get object handles
Experiencing the same problem on Ubuntu 20.04 when trying to copy files to DCIM/Camera folder on Android Samsung a20 device. MTP is basically unusable. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1810176 Title: libmtp error could not get object handles To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libmtp/+bug/1810176/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1555904] Re: opal-prd not installed by default on ppc64el systems
** Also affects: subiquity 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/1555904 Title: opal-prd not installed by default on ppc64el systems To manage notifications about this bug go to: https://bugs.launchpad.net/subiquity/+bug/1555904/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1740419] Re: Please remove system-config-samba from Ubuntu
HellooOoo… removing a package without replacing its features by something else is NOT a fix. It's just a feature removal. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1740419 Title: Please remove system-config-samba from Ubuntu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/system-config-samba/+bug/1740419/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1882471] Re: thumbnails for mp3 / flac from in-file embedded picture
** Description changed: Hi, here is an Ubuntu Budgie 20.04. It uses Nemo 4.4.2 as file explorer. I've noticed here my music files, mainly mp3, only show their generic icons and not their embedded picture for cover art. I've got this → https://aws1.discourse- cdn.com/standard17/uploads/ubuntubudgie/original/2X/8/8b66f4a45787193d226ae6b3bdcf83e364b84f3f.png I expected something like this → https://aws1.discourse- cdn.com/standard17/uploads/ubuntubudgie/original/2X/f/fb30fd0c844dbe15b966921edfe9ab9e0754ebf8.png Here are my installed packages regarding thumbnails, I think : - + _ django@ASGARD:~$ dpkg -l | grep -Ei 'thumbnailer|ffmpeg|nemo' ii chromium-codecs-ffmpeg-extra 81.0.4044.129-0ubuntu0.20.04.1 amd64Transitional package - chromium-codecs-ffmpeg-extra -> chromium-ffmpeg snap ii ffmpeg7:4.2.2-1ubuntu1 amd64Tools for transcoding, streaming and playing of multimedia files ii ffmpegthumbnailer 2.1.1-0.2build2 amd64fast and lightweight video thumbnailer ii folder-color-nemo 0.0.88 all Folder Color for Nemo ii gir1.2-nemo-3.0 4.4.2-2 amd64libraries for nemo components - gir bindings ii gstreamer1.0-libav:amd64 1.16.2-2 amd64ffmpeg plugin for GStreamer ii libavcodec-extra:amd647:4.2.2-1ubuntu1 amd64FFmpeg library with extra codecs (metapackage) ii libavcodec-extra58:amd64 7:4.2.2-1ubuntu1 amd64FFmpeg library with additional de/encoders for audio/video codecs ii libavdevice58:amd64 7:4.2.2-1ubuntu1 amd64FFmpeg library for handling input and output devices - runtime files ii libavfilter7:amd647:4.2.2-1ubuntu1 amd64FFmpeg library containing media filters - runtime files ii libavformat58:amd64 7:4.2.2-1ubuntu1 amd64FFmpeg library with (de)muxers for multimedia containers - runtime files ii libavresample4:amd64 7:4.2.2-1ubuntu1 amd64FFmpeg compatibility library for resampling - runtime files ii libavutil56:amd64 7:4.2.2-1ubuntu1 amd64FFmpeg library with functions for simplifying programming - runtime files ii libffmpegthumbnailer4v5 2.1.1-0.2build2 amd64shared library for ffmpegthumbnailer ii libgdk-pixbuf2.0-bin 2.40.0+dfsg-3 amd64GDK Pixbuf library (thumbnailer) ii libnemo-extension1:amd64 4.4.2-2 amd64Nemo component system facilities ii libpostproc55:amd64 7:4.2.2-1ubuntu1 amd64FFmpeg library for post processing - runtime files ii libswresample3:amd64 7:4.2.2-1ubuntu1 amd64FFmpeg library for audio resampling, rematrixing etc. - runtime files ii libswscale5:amd64 7:4.2.2-1ubuntu1 amd64FFmpeg library for image scaling and various conversions - runtime files ii nemo 4.4.2-2 amd64File manager and graphical shell for Cinnamon ii nemo-data 4.4.2-2 all File manager and graphical shell for Cinnamon (data files) ii nemo-fileroller 4.4.0-2 amd64File Roller integration for Nemo ii nemo-python 4.4.0-3 amd64Python bindings for nemo components - django@ASGARD:~$ - + django@ASGARD:~$ + _ Thumbnails are OK for video files though. I followed suggestions from here https://github.com/linuxmint/nemo/issues/2280#issuecomment-571996421 I had edited /usr/share/thumbnailers/ffmpegthumbnailer.thumbnailer but that does not change anything in Nemo. - + _ - django@ASGARD:~$ cat /usr/share/thumbnailers/ffmpegthumbnailer.thumbnailer + django@ASGARD:~$ cat
[Bug 1882471] [NEW] thumbnails for mp3 / flac from in-file embedded picture
Public bug reported: Hi, here is an Ubuntu Budgie 20.04. It uses Nemo 4.4.2 as file explorer. I've noticed here my music files, mainly mp3, only show their generic icons and not their embedded picture for cover art. I've got this → https://aws1.discourse- cdn.com/standard17/uploads/ubuntubudgie/original/2X/8/8b66f4a45787193d226ae6b3bdcf83e364b84f3f.png I expected something like this → https://aws1.discourse- cdn.com/standard17/uploads/ubuntubudgie/original/2X/f/fb30fd0c844dbe15b966921edfe9ab9e0754ebf8.png Here are my installed packages regarding thumbnails, I think : django@ASGARD:~$ dpkg -l | grep -Ei 'thumbnailer|ffmpeg|nemo' ii chromium-codecs-ffmpeg-extra 81.0.4044.129-0ubuntu0.20.04.1 amd64Transitional package - chromium-codecs-ffmpeg-extra -> chromium-ffmpeg snap ii ffmpeg7:4.2.2-1ubuntu1 amd64Tools for transcoding, streaming and playing of multimedia files ii ffmpegthumbnailer 2.1.1-0.2build2 amd64fast and lightweight video thumbnailer ii folder-color-nemo 0.0.88 all Folder Color for Nemo ii gir1.2-nemo-3.0 4.4.2-2 amd64libraries for nemo components - gir bindings ii gstreamer1.0-libav:amd64 1.16.2-2 amd64ffmpeg plugin for GStreamer ii libavcodec-extra:amd647:4.2.2-1ubuntu1 amd64FFmpeg library with extra codecs (metapackage) ii libavcodec-extra58:amd64 7:4.2.2-1ubuntu1 amd64FFmpeg library with additional de/encoders for audio/video codecs ii libavdevice58:amd64 7:4.2.2-1ubuntu1 amd64FFmpeg library for handling input and output devices - runtime files ii libavfilter7:amd647:4.2.2-1ubuntu1 amd64FFmpeg library containing media filters - runtime files ii libavformat58:amd64 7:4.2.2-1ubuntu1 amd64FFmpeg library with (de)muxers for multimedia containers - runtime files ii libavresample4:amd64 7:4.2.2-1ubuntu1 amd64FFmpeg compatibility library for resampling - runtime files ii libavutil56:amd64 7:4.2.2-1ubuntu1 amd64FFmpeg library with functions for simplifying programming - runtime files ii libffmpegthumbnailer4v5 2.1.1-0.2build2 amd64shared library for ffmpegthumbnailer ii libgdk-pixbuf2.0-bin 2.40.0+dfsg-3 amd64GDK Pixbuf library (thumbnailer) ii libnemo-extension1:amd64 4.4.2-2 amd64Nemo component system facilities ii libpostproc55:amd64 7:4.2.2-1ubuntu1 amd64FFmpeg library for post processing - runtime files ii libswresample3:amd64 7:4.2.2-1ubuntu1 amd64FFmpeg library for audio resampling, rematrixing etc. - runtime files ii libswscale5:amd64 7:4.2.2-1ubuntu1 amd64FFmpeg library for image scaling and various conversions - runtime files ii nemo 4.4.2-2 amd64File manager and graphical shell for Cinnamon ii nemo-data 4.4.2-2 all File manager and graphical shell for Cinnamon (data files) ii nemo-fileroller 4.4.0-2 amd64File Roller integration for Nemo ii nemo-python 4.4.0-3 amd64Python bindings for nemo components django@ASGARD:~$ Thumbnails are OK for video files though. I followed suggestions from here https://github.com/linuxmint/nemo/issues/2280#issuecomment-571996421 I had edited /usr/share/thumbnailers/ffmpegthumbnailer.thumbnailer but that does not change anything in Nemo. django@ASGARD:~$ cat /usr/share/thumbnailers/ffmpegthumbnailer.thumbnailer [Thumbnailer Entry] TryExec=ffmpegthumbnailer Exec=ffmpegthumbnailer -i %i -o %o -s %s -f MimeType=video/jpeg;video/mp4;video/mpeg;video/quicktime;video/x-ms-asf;video/x-ms-wm;video/x-ms-wmv;video/x-msvideo;video/x-flv;video/x-matroska;video/webm;video/mp2t;audio/flac;audio/mpeg django@ASGARD:~$
[Bug 1882418] Re: spamprobe crashes on email containing images
The attachment "Workaround for images crashing spamprobe" seems to be a patch. If it isn't, please remove the "patch" flag from the attachment, remove the "patch" tag, and if you are a member of the ~ubuntu- reviewers, unsubscribe the team. [This is an automated message performed by a Launchpad user owned by ~brian-murray, for any issues please contact him.] ** Tags added: patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1882418 Title: spamprobe crashes on email containing images To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/spamprobe/+bug/1882418/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1882465] Re: trying to install win10 ubuntu 20 dual boot on a partition on an HP Pavilion DV4
Thank you for taking the time to report this bug and helping to make Ubuntu better. Reviewing your log files attached to this bug report it seems that there is a problem with your installation media (CD/DVD). You can verify the integrity of the Ubuntu ISO files you downloaded by following the instructions at https://help.ubuntu.com/community/HowToMD5SUM. You might also retry your installation with new media. In the event that is is not in fact an error with your installation media please set the bug's status back to New. Thanks and good luck! [This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.] ** Changed in: ubiquity (Ubuntu) Status: New => Incomplete ** Tags added: ident-mismatch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1882465 Title: trying to install win10 ubuntu 20 dual boot on a partition on an HP Pavilion DV4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1882465/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1882470] [NEW] installation failed while installing grub loader
Public bug reported: tring to install ubuntu 64bit 20.04 on my acer 110 ict tablet with bootia32.efi replaced for ubuntu to boot properly. after installation start, at the last moment below error received. "the 'grub-efi-ia32' package failed to install into /target/. without the GRUB bootloader, the installed system will not boot." ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubiquity 20.04.15 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CasperVersion: 1.445 CurrentDesktop: ubuntu:GNOME Date: Sun Jun 7 16:02:43 2020 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed maybe-ubiquity quiet splash --- LiveMediaBuild: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) 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 ubiquity-20.04.15 ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1882470 Title: installation failed while installing grub loader To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1882470/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1851898] Re: kpat stuffs hard drive
** Changed in: kpat Status: Unknown => 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/1851898 Title: kpat stuffs hard drive To manage notifications about this bug go to: https://bugs.launchpad.net/kpat/+bug/1851898/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1851898]
Git commit 9b1d9abdc56f5037e713e1fdefa22e58d5c2087a by Albert Astals Cid. Committed on 30/05/2020 at 17:16. Pushed by aacid into branch 'release/20.04'. Change some verbose debugs from using ifndef NDEBUG Lots of distributions are building with DebugAndRelease configurations to have better symbols and it seems this debug is *so* verbose that floods people's disks with data M +1-1dealer.cpp M +1-1patsolve/patsolve.cpp https://invent.kde.org/games/kpat/commit/9b1d9abdc56f5037e713e1fdefa22e58d5c2087a -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1851898 Title: kpat stuffs hard drive To manage notifications about this bug go to: https://bugs.launchpad.net/kpat/+bug/1851898/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1882418] Re: spamprobe crashes on email containing images
Here's a patch that at least catches and discards the segfaults. Image processing shouldn't fault to begin with, but this patch at least makes spamprobe usable again. ** Patch added: "Workaround for images crashing spamprobe" https://bugs.launchpad.net/ubuntu/+source/spamprobe/+bug/1882418/+attachment/5381417/+files/spamprobe-img-workaround.patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1882418 Title: spamprobe crashes on email containing images To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/spamprobe/+bug/1882418/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1882466] [NEW] mythtv frontend crash when calling glClear in iris driver
Public bug reported: on startup, mythfrontend crashes repeatedly when calling glClear - the following traceback: Core was generated by `/usr/bin/mythfrontend.real'. Program terminated with signal SIGSEGV, Segmentation fault. #0 0x7f9495ca0838 in ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so [Current thread is 1 (Thread 0x7f9551e59940 (LWP 4164))] (gdb) bt #0 0x7f9495ca0838 in ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so #1 0x7f9495ca2ebf in ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so #2 0x7f9495e65de4 in ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so #3 0x7f9495c7ce5d in ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so #4 0x7f9495c7da95 in ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so #5 0x7f94952bc774 in ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so #6 0x7f955f79e713 in QOpenGLFunctions::glClear (this=0x555cb36e8160, mask=16384) at /usr/include/x86_64-linux-gnu/qt5/QtGui/qopenglfunctions.h:628 #7 0x7f955f798090 in MythRenderOpenGL::ClearFramebuffer ( this=0x555cb36e8150) at opengl/mythrenderopengl.cpp:801 #8 0x7f955f78a3f2 in MythOpenGLPainter::Begin (this=0x555cb398dac0, Parent=0x555cb399d1d0) at opengl/mythpainteropengl.cpp:136 I can work around this problem with this: export MESA_LOADER_DRIVER_OVERRIDE=i965 (then running mythfrontend works fine) sorry for the lack of debug symbols in iris_dri.so if there is a .deb around with a debug version i can generate the traceback again not sure if the problem belongs to iris_dri.so or to mythfrontend but I put it here due to the workaround. $ lsb_release -rd Description:Ubuntu 20.04 LTS Release:20.04 $ apt-cache policy libgl1-mesa-dri libgl1-mesa-dri: Installed: 20.0.4-2ubuntu1 Candidate: 20.0.4-2ubuntu1 Version table: *** 20.0.4-2ubuntu1 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status ** Affects: mesa (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/1882466 Title: mythtv frontend crash when calling glClear in iris driver To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1882466/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1882465] [NEW] trying to install win10 ubuntu 20 dual boot on a partition on an HP Pavilion DV4
Public bug reported: going from full windows 10 to dual boot win 10 / unbuntu 20.04 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubiquity 20.04.15 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.445 CurrentDesktop: ubuntu:GNOME Date: Sun Jun 7 19:07:51 2020 InstallCmdLine: file=/cdrom/preseed/ubuntu.seed initrd=/casper/initrd quiet splash --- maybe-ubiquity LiveMediaBuild: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcEnviron: LANGUAGE=en_US.UTF-8 PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 LC_NUMERIC=C.UTF-8 SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ubiquity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ubiquity-20.04.15 ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1882465 Title: trying to install win10 ubuntu 20 dual boot on a partition on an HP Pavilion DV4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1882465/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1880441] Re: nvidia-driver-390 - brightness control not working for NVIDIA GeForce GTX 670 mx
** Description changed: The same case on Ubuntu 20.04 as on the start of 16.04 for my ASUS Notebook (G75VX): - No brightness control over the Keyboard - No brightness control over the systemsettings - - Screenbrightness what ever i try still on 100% + - Screenbrightness what ever i try is still on 100% - - The Problem is the same at my second System Kubuntu 20.04. - + The Problem is the same at my second System Kubuntu 20.04; + with the nouveau driver the adjustment over the system settings is working. Here some details about my System: - lspci -nnk | grep -i VGA -A2 + lspci -nnk | grep -i VGA -A2 01:00.0 VGA compatible controller [0300]: NVIDIA Corporation GK104M [GeForce GTX 670MX] [10de:11a1] (rev a1) - Subsystem: ASUSTeK Computer Inc. GK104M [GeForce GTX 670MX] [1043:21ab] - Kernel driver in use: nvidia + Subsystem: ASUSTeK Computer Inc. GK104M [GeForce GTX 670MX] [1043:21ab] + Kernel driver in use: nvidia - grep nvidia_drv.so /var/log/Xorg.0.log + grep nvidia_drv.so /var/log/Xorg.0.log [13.808] (II) Loading /usr/lib/x86_64-linux-gnu/nvidia/xorg/nvidia_drv.so - dpkg -l nvidia* + dpkg -l nvidia* Gewünscht=Unbekannt/Installieren/R=Entfernen/P=Vollständig Löschen/Halten | Status=Nicht/Installiert/Config/U=Entpackt/halb konFiguriert/ - Halb installiert/Trigger erWartet/Trigger anhängig + Halb installiert/Trigger erWartet/Trigger anhängig |/ Fehler?=(kein)/R=Neuinstallation notwendig (Status, Fehler: GROSS=schlecht) ||/ Name Version Architektur Beschreibung +++----=> un nvidia-304 (keine Beschreibung vorhanden) un nvidia-340 (keine Beschreibung vorhanden) un nvidia-384 (keine Beschreibung vorhanden) un nvidia-390 (keine Beschreibung vorhanden) un nvidia-common(keine Beschreibung vorhanden) ii nvidia-compute-utils-390 390.132-0ubuntu2 amd64NVIDIA compute utilities un nvidia-dkms-390 (keine Beschreibung vorhanden) ii nvidia-driver-390390.132-0ubuntu2 amd64NVIDIA driver metapackage un nvidia-driver-binary (keine Beschreibung vorhanden) un nvidia-kernel-common (keine Beschreibung vorhanden) ii nvidia-kernel-common-390 390.132-0ubuntu2 amd64Shared files used with the kernel module un nvidia-kernel-source (keine Beschreibung vorhanden) ii nvidia-kernel-source-390 390.132-0ubuntu2 amd64NVIDIA kernel source package un nvidia-legacy-304xx-vdpau-driver (keine Beschreibung vorhanden) un nvidia-legacy-340xx-vdpau-driver (keine Beschreibung vorhanden) un nvidia-libopencl1-dev(keine Beschreibung vorhanden) un nvidia-opencl-icd(keine Beschreibung vorhanden) un nvidia-persistenced (keine Beschreibung vorhanden) ii nvidia-prime 0.8.14 all Tools to enable NVIDIA's Prime ii nvidia-settings 440.64-0ubuntu1 amd64Tool for configuring the NVIDIA graphics driv> un nvidia-settings-binary (keine Beschreibung vorhanden) un nvidia-smi (keine Beschreibung vorhanden) un nvidia-utils (keine Beschreibung vorhanden) ii nvidia-utils-390 390.132-0ubuntu2 amd64NVIDIA driver support binaries un nvidia-vdpau-driver (keine Beschreibung vorhanden) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1880441 Title: nvidia-driver-390 - brightness control not working for NVIDIA GeForce GTX 670 mx To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1880441/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1881401] Re: HPLIP, hp-doctor, hp-check should support Ubuntu 20.04 LTS with its package base
I second this, if there is something included in the lts, it should work, and HPLIP clearly doesn't. Besides that, the new version cannot be installed either because it cannot find several dependencies, including a required one (pyqt5). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1881401 Title: HPLIP, hp-doctor, hp-check should support Ubuntu 20.04 LTS with its package base To manage notifications about this bug go to: https://bugs.launchpad.net/hplip/+bug/1881401/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1881401] Re: HPLIP, hp-doctor, hp-check should support Ubuntu 20.04 LTS with its package base
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: hplip (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/1881401 Title: HPLIP, hp-doctor, hp-check should support Ubuntu 20.04 LTS with its package base To manage notifications about this bug go to: https://bugs.launchpad.net/hplip/+bug/1881401/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1859308] Re: software-properties-gtk erroneously reports that certain Intel wireless adapter cards are not working
I have the same issue with 8260 on 20.04. Without backports installed the wi-fi worked but there was often a very long delay when connecting to or loading a site. Ran speed test (google speed test) and there was a 15 - 20-second delay connecting to the server, but then good speed (around 40 MBPS) was reported. This was repeatable. Installed backports and selected it as the driver and the delay disappeared. Now connects instantly and reports the same good speed. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1859308 Title: software-properties-gtk erroneously reports that certain Intel wireless adapter cards are not working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1859308/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1327801] Re: Bightness and contrast settings have no effect
I can confirm this issue with Epson Workforce WF-2835. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1327801 Title: Bightness and contrast settings have no effect To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/simple-scan/+bug/1327801/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
