[Bug 1902829] [NEW] Missing "Mobile Broadband" menu item
Public bug reported: [Impact] gnome-shell does not show the "Mobile Broadband" menu item in Ubuntu 20.10, which practically prevents net access for users who depend on mobile broadband. An upstream fix has recently been pushed. [Test case] * Install the binaries built by the gnome-shell source package from groovy-proposed * Reboot * Confirm with a USB dongle for mobile broadband that it's recognized in the system menu and allows you to connect. [Regression risk] The issue was triggered by a change to gjs, and the fix simply adds two property getters. Low regression risk. ** Affects: gnome-shell Importance: Unknown Status: Unknown ** Affects: gnome-shell (Ubuntu) Importance: High Status: Triaged ** Affects: gnome-shell (Ubuntu Groovy) Importance: High Status: Triaged ** Tags: groovy regression-release ** Also affects: gnome-shell (Ubuntu Groovy) Importance: Undecided Status: New ** Changed in: gnome-shell (Ubuntu Groovy) Importance: Undecided => High ** Changed in: gnome-shell (Ubuntu Groovy) Status: New => Triaged ** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/-/issues #3203 https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/3203 ** Also affects: gnome-shell via https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/3203 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/1902829 Title: Missing "Mobile Broadband" menu item To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1902829/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1879711] Re: aws: disable CONFIG_DMA_CMA
** Also affects: linux-aws (Ubuntu Groovy) 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/1879711 Title: aws: disable CONFIG_DMA_CMA To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/1879711/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1732512] Re: xen hibernation support for linux-aws
** Also affects: linux-aws (Ubuntu Groovy) 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/1732512 Title: xen hibernation support for linux-aws To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/1732512/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1902797] Re: zsys unable to save state since upgrade to 20.10
Looking at your datasets, you have some that are expected like: rpool/ROOT/ubuntu_mj0kfs/var/www and associated snapshots: rpool/ROOT/ubuntu_mj0kfs/var/www@autozsys_17e8fr However, you have others that are not produced by ZSys, creating a lot of duplications: rpool/ROOT/ubuntu_mj0kfs/var/www_autozsys_ly64kj (which are then taken as snapshots by ZSys rpool/ROOT/ubuntu_mj0kfs/var/www_autozsys_ly64kj@autozsys_ly64kj) Where all those *_autozsys_ are coming from, do you have any tool copying ZFS snapshots and creating clones from them without cleaning? I think this is the source of the timeout you are seeing, as you have too many datasets to be handled by ZSys right now. Please remove all of those *_autozsys_* datasets and associated snapshots, and find the source of what is creating those clones. ** Changed in: zsys (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/1902797 Title: zsys unable to save state since upgrade to 20.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zsys/+bug/1902797/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1901690] Re: Ubuntu20.04 system permissions problem of networkmanager
When I create a new APN profile via the mobile broadband UI，I found my Internet APN "apn" couldn't set to file /etc/NetworkManager/system- connections/. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1901690 Title: Ubuntu20.04 system permissions problem of networkmanager To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/compiz-plugins-main/+bug/1901690/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1898905] Re: Unfunctional plustek scanner in Ubuntu 20.10
libsane1 1.0.31-2ubuntu0.20.10 from groovy-proposed fixes the problem for me. Thx for taking care of this -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1898905 Title: Unfunctional plustek scanner in Ubuntu 20.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1898905/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1902519] Re: [nvidia] KDE shows bad pixels after hibernate
** Tags added: nvidia-corruption -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1902519 Title: [nvidia] KDE shows bad pixels after hibernate To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kwin/+bug/1902519/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1855757] Re: [nvidia] Background image corrupted after standby or resume from suspend
** Tags added: nvidia-corruption -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1855757 Title: [nvidia] Background image corrupted after standby or resume from suspend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1855757/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1894627] Re: [nvidia] Web browser distorted after hibernation/power save when idle
** Tags added: nvidia-corruption -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1894627 Title: [nvidia] Web browser distorted after hibernation/power save when idle To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1894627/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1901242] Re: virt-manager local directory storage failing
FYI - Uploaded the fix to Hirsute (a bit slow due to the test queue being rather full atm) and to groovy-unapproved for the SRU process. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1901242 Title: virt-manager local directory storage failing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1901242/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1901585] Re: [nvidia] Ubuntu 20.04 LTS Desktop Screen blinking/flickering black and side menu bar turn upsidedown
This sounds like another Nvidia issue related to: https://www.khronos.org/registry/OpenGL/extensions/NV/NV_robustness_video_memory_purge.txt which mentions "VT switches", so that can include user switching. There is no workaround right now, other than to avoid the Nvidia driver, or to avoid user switching and suspend/resume etc :( ** Tags added: nvidia-corruption -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1901585 Title: [nvidia] Ubuntu 20.04 LTS Desktop Screen blinking/flickering black and side menu bar turn upsidedown To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1901585/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1890435] Re: gcc-10 breaks on armhf (flaky): internal compiler error: Segmentation fault
FYI - Started a build run with 10.2.0-16ubuntu1.2 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1890435 Title: gcc-10 breaks on armhf (flaky): internal compiler error: Segmentation fault To manage notifications about this bug go to: https://bugs.launchpad.net/groovy/+bug/1890435/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1877089] Re: zfcpdump kernel can not be IPLed, wrong file name
@brian-murray and @acb This bug is in between 'Fix Released' for groovy. Please see also zfcpdump-kernel changelog: zfcpdump-kernel (5.4-0ubuntu2) groovy; urgency=medium * Switch to 5.4 base from focal (5.4.0-49.53). * Drop fix to zfcpdump config, included in 5.4. * Rename zfcpdump_part.image, to zfcpdump-image, to match current s390-tools expectations. LP: #1877089 The zfcpdump kernel got now updated to the focal kernel. I think that this bug was raised right after focal was released (and probably before groovy development was really open) - it had initially only a series entry for focal and it was at the beginning assumed that only focal is affected (groovy s390-tool was not there yet). It took a while to get this topics discussed and achieve more clarification (and the bug states changed quite a bit). At some point in time a first upload was done on focal - that got dropped then and replaced by a revised version that still sits in focal unapproved (since 2020-09-17) https://launchpad.net/ubuntu/focal/+queue?queue_state=1_text=zfcpdump-kernel Meanwhile groovy evolved and it became clear that this needs to be tacked too, but the first focal upload was already out. Hence the groovy upload came late, means after focal (so too late according to the SRU process, hence comment #15). Since the zfcpdump-kernel package/image is quite self sufficient and static, the regression risk is very low, since the zfcpdump-kernel image is even independent from the OS series, hence it can be build in one series (now focal) and then be used in focal or newer. Please see also bug description: [Publication] and [Regression Potential] -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1877089 Title: zfcpdump kernel can not be IPLed, wrong file name To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1877089/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1896167] Re: Heavy screen tearing in Wayland sessions on Raspberry Pi 4-B
I've read a suggestion this is fixed in later kernels like 5.9. Need to test. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1896167 Title: Heavy screen tearing in Wayland sessions on Raspberry Pi 4-B To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1896167/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1896171] Re: Wayland 3D apps appear corrupt on Raspberry Pi 4B (v3d driver)
** Bug watch added: gitlab.gnome.org/GNOME/mutter/-/issues #1520 https://gitlab.gnome.org/GNOME/mutter/-/issues/1520 ** Also affects: mutter via https://gitlab.gnome.org/GNOME/mutter/-/issues/1520 Importance: Unknown Status: Unknown ** Changed in: mutter (Ubuntu) Status: New => Confirmed ** Changed in: mesa (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/1896171 Title: Wayland 3D apps appear corrupt on Raspberry Pi 4B (v3d driver) To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1896171/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1870886] Re: Window scales to 200% after screen unlocked, on desktop with external monitor
Ok, appears to be fixed in Hirsute. There's a brief period that the 2x sized window "wiggles" to the correct size. ** Changed in: gnome-shell (Ubuntu) Status: Incomplete => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1870886 Title: Window scales to 200% after screen unlocked, on desktop with external monitor To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1870886/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1902825] Re: High CPU usage just moving the mouse
Also I am reminded of an issue that was fixed upstream recently... Do you find the high CPU only comes *after* the lock screen has been used? Does it happen on a fresh boot when no lock screen has ever been used? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1902825 Title: High CPU usage just moving the mouse To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1902825/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 795997] Re: 8086:4238 [HP EliteBook 8540w] wifi led indicator blinks
Mark, can you please attach output of `nmcli`? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/795997 Title: 8086:4238 [HP EliteBook 8540w] wifi led indicator blinks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/795997/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1902694] Re: Undetected Data corruption in MPI workloads that use VSX for reductions on POWER9 DD2.1 systems
SRU submission: https://lists.ubuntu.com/archives/kernel-team/2020-November/thread.html#114535 ** Changed in: linux (Ubuntu Hirsute) Assignee: Ubuntu on IBM Power Systems Bug Triage (ubuntu-power-triage) => (unassigned) ** Changed in: linux (Ubuntu Focal) Status: New => In Progress ** Changed in: linux (Ubuntu Groovy) Status: New => In Progress ** Changed in: linux (Ubuntu Hirsute) Status: New => In Progress ** Changed in: ubuntu-power-systems Status: New => In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1902694 Title: Undetected Data corruption in MPI workloads that use VSX for reductions on POWER9 DD2.1 systems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1902694/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1895905] Re: lubuntu groovy; flashing of sddm greeter
I tried each of sddm-theme-debian-elarun - 'Debian Elarun' Theme for SDDM X11 display manager sddm-theme-debian-maui - 'Debian Maui' theme for SDDM X11 display manager sddm-theme-elarun - 'Elarun' Theme for SDDM X11 display manager sddm-theme-lubuntu - Lubuntu theme for SDDM X11 display manager sddm-theme-maldives - 'Maldives' theme for SDDM X11 display manager sddm-theme-maui - 'Maui' theme for SDDM X11 display manager sddm-theme-maya - 'Maya' theme for SDDM X11 display manager and it was the same (flashing effect) for each theme (I skipped trying `sddm-theme-breeze` as it was going to pull in a lot of KF5 etc, I can’t see why it would be different, let me know if it’s worth trying) I added & made default `xdm` and the login flashing disappeared. This however had the effect of changing the theme used by the panel (I noticed it too on *hp dc7700*). I don’t consider this an issue though; they are easily changed back in *Appearances*. Changes are – sddm * qt style - breeze * lxqt-theme - Lubuntu Arc – xdm * qt style - fusion * lxqt-theme - frost -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1895905 Title: lubuntu groovy; flashing of sddm greeter To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1895905/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1902825] Re: High CPU usage just moving the mouse
Please: * Run 'top' to confirm which process is using the most CPU. * After the problem happens again run: lsusb > lsusb.txt lspci -kv > lspci.txt journalctl -b0 > journal.txt gsettings list-recursively org.gnome.shell > shellsettings.txt xrandr --verbose > xrandr.txt and attach the resulting text files here. ** 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/1902825 Title: High CPU usage just moving the mouse To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1902825/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1902694] Re: Undetected Data corruption in MPI workloads that use VSX for reductions on POWER9 DD2.1 systems
** Also affects: linux (Ubuntu Groovy) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Hirsute) Importance: Undecided Assignee: Ubuntu on IBM Power Systems Bug Triage (ubuntu-power-triage) Status: New ** Also affects: linux (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/1902694 Title: Undetected Data corruption in MPI workloads that use VSX for reductions on POWER9 DD2.1 systems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1902694/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1902825] [NEW] High CPU usage just moving the mouse
Public bug reported: high cpu usage just moving the mouse removed appindicator extension .. the cpu load is very high. running strace -c -p while moving mouse % time seconds usecs/call callserrors syscall -- --- --- - - 36.740.103852 103 1000 8 futex 31.300.088469 8 10366 8750 recvmsg 15.530.043901 11 3925 poll 10.100.028550 10 2776 write 4.330.012232 7 1537 writev 1.600.004533 4 932 read 0.390.001092 3 337 getpid 0.000.01 0 2 getrusage 0.000.01 1 1 restart_syscall 0.000.00 0 4 mprotect -- --- --- - - 100.000.282631 20880 8758 total ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: gnome-shell 3.38.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.8.0-26.27-generic 5.8.14 Uname: Linux 5.8.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: GNOME-Classic:GNOME Date: Wed Nov 4 10:49:20 2020 DisplayManager: gdm3 RelatedPackageVersions: mutter-common 3.38.1-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug groovy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1902825 Title: High CPU usage just moving the mouse To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1902825/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1899460] Re: tpm2_nvdefine without specifying the size issue
** Description changed: nvdefind tool takes the size MAX_NV_INDEX_SIZE(2048) as default, but got errors(0x2D5) returned on those platforms which don't have the size as default. https://github.com/tpm2-software/tpm2-tools/issues/2171 [Impact] - Some machines which don't have enough MAX_NV_INDEX_SIZE as default will got "the structure is the wrong size(0x2D5)" error when using tpm2_nvdefine without specifying the size of data area + Some machines which don't have enough MAX_NV_INDEX_SIZE as default will get "the structure is the wrong size(0x2D5)" error when using tpm2_nvdefine without specifying the size of data area [Test cases] run nvdefine without specifying the size of data area [Solution] A fix patch has been committed and accepted by maintainer https://github.com/tpm2-software/tpm2-tools/commit/48594efa6f1faca50c73ce0d88f6e99eb0f5005c [Regression Potential] Minimal, it fixed the issue by checking the platform capabilities instead of using default. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1899460 Title: tpm2_nvdefine without specifying the size issue To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tpm2-tools/+bug/1899460/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1874464] Re: NETDEV WATCHDOG: enp5s0 (r8169): transmit queue 0 timed out
Dan, Given that it's a kernel regression, would it be possible to try mainline kernel and do a kernel bisection if issue persists? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1874464 Title: NETDEV WATCHDOG: enp5s0 (r8169): transmit queue 0 timed out To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1874464/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1897501] Re: HP Zbook Studio G7 boots into corrupted screen with PSR featured panel
** Changed in: hwe-next Status: New => 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/1897501 Title: HP Zbook Studio G7 boots into corrupted screen with PSR featured panel To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1897501/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1884634] Re: backport-iwlwifi-dkms 8324-0ubuntu3 ADT test failure with linux-5.8 5.8.0-1.2
Updated commits to include only necessary changes backported from upstream backport-iwlwifi, mainline kernel, and backports project. Need review & submit. ** Description changed: [SRU Justifcation] [Impact] - When compiled against linux-oem-5.6 kernels on Focal, backport-iwlwifi-dkms gives numerous errors and fails the installation. Although the current version 8324 has been marked obsoleted by 5.4 or newer in bug 1863583 and bug 1869587, this still happens during the installation of either kernel headers packages or backport-iwlwifi-dkms because dkms will still build but skip installing dkms modules. So far this doesn't bring critical errors, but as a LTS series Focal will receive more and more kernel version bumps as Bionic does, such build failure will be a problem that can't be avoid. + When compiled against linux-oem-5.6/linux-5.8 kernels on Focal, backport-iwlwifi-dkms gives numerous errors due to in kernel interface changes and fails the installation. [Fix] - This backports rev 8613, which fixed compilation against v5.8, that is already in Groovy to Focal along with necessary changes (Depends: flex, bison). + This backports several patches from upstream backport-iwlwifi, mainline kernel, and backports project. [Test Case] - Tested on 5.4.0-40-generic and 5.6.0-1018-oem on Focal. + Tested build on 5.4.0-52-generic, 5.6.0-1032-oem and 5.8.0-25-generic on Focal. Since the current version 8324 has been marked obsoleted by 5.4 or newer in bug 1863583 and bug 1869587, built modules are not installed currently so no runtime tests are required. [Regression Potential] Low. So far backport-iwlwifi-dkms is still marked OBSOLETED_BY=5.4.0, so it has totally no effect in the runtime system. This will only change when future enablements based on LTS series Focal that relies on out-of-tree driver support from this package. === Original Bug Description === Testing failed on: amd64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-groovy-canonical-kernel-team-bootstrap/groovy/amd64/b/backport-iwlwifi-dkms/20200619_205606_7a677@/log.gz arm64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-groovy-canonical-kernel-team-bootstrap/groovy/arm64/b/backport-iwlwifi-dkms/20200619_210720_cf76d@/log.gz ppc64el: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-groovy-canonical-kernel-team-bootstrap/groovy/ppc64el/b/backport-iwlwifi-dkms/20200619_205835_f474a@/log.gz -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1884634 Title: backport-iwlwifi-dkms 8324-0ubuntu3 ADT test failure with linux-5.8 5.8.0-1.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/backport-iwlwifi-dkms/+bug/1884634/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1871794] Re: [Bluetooth] No audio output/input in HSP/HFP mode
@smurf, What is generated after building? If it is *.deb file, just need to run 'sudo dpkg -i *.deb; reboot' -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1871794 Title: [Bluetooth] No audio output/input in HSP/HFP mode To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1871794/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1902694] Re: Ubuntu 20.10- Undetected Data corruption in MPI workloads that use VSX for reductions on POWER9 DD2.1 systems
** Description changed:
- == Comment: #0 - Waiki Wright - 2020-11-02 17:00:07
- ==
+ SRU Justification:
- ---Problem Description---
+ [Impact]
- A data integrity issue was observed with the Ubuntu 20.04 - 5.4.0-52 and
- 20.10 - 5.8.0-26 kernel on Power 9. The root cause is found in the
- compiling of p9_hmi_special_emu(). When doing a VMX store (in
- __get_user_atomic_128_aligned()) to a buffer (vbuf), the buffer is not
- 128 bit aligned.
+ * A data integrity issue was observed on POWER 9 (DD2.1) systems.
- The fixes of this bug are accepted upstream:
- 1.
-
https://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux.git/commit/?h=fixes=1da4a0272c5469169f78cd76cf175ff984f52f06
- ("powerpc: Fix undetected data corruption with P9N DD2.1 VSX CI load
emulation")
- 2.
-
https://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux.git/commit/?h=fixes=d1781f23704707d350b8c9006e2bdf5394bf91b2
- ("selftests/powerpc: Make alignment handler test P9N DD2.1 vector CI load
workaround")
+ * It affects Ubuntu 20.04 with kernel 5.4.0-52 and Ubuntu 20.10 with
+ kernel 5.8.0-26 kernel.
+
+ * The root cause is found in the compiling of p9_hmi_special_emu().
+
+ * When doing a VMX store (in __get_user_atomic_128_aligned()) to a
+ buffer (vbuf), the buffer is not 128 bit aligned.
+
+ [Fix]
+
+ * 1da4a0272c54 "powerpc: Fix undetected data corruption with P9N DD2.1
+ VSX CI load emulation"
+
+ * d1781f237047 "selftests/powerpc: Make alignment handler test P9N DD2.1
+ vector CI load workaround"
+
+ [Test Case]
+
+ * A POWER 9 (DD2.1) bare metal system is needed that has either Ubuntu
+ 20.04, 20.10 or 21.04 installed.
+
+ * It's best to test this based on a sample application and test case
+ "selftests/powerpc: Make alignment handler test P9N DD2.1 vector CI load
workaround"
+
+ [Regression Potential]
+
+ * The regression risk is relatively moderate, because:
+
+ * it only happens with special VSX (vector) instructions in use, e.g. in
+ p9_hmi_special_emu
+
+ * it happens on bare metal only and only on POWER 9 (DD2.1)
+
+ * and the changes are very overseeable (in total one effective code line
+ per patch/commit)
+
+ * Since only p9_hmi_special_emu is touched, this will break in case of
+ any regressions, but this is already broken based on this bug.
+
+ [Other]
+
+ * According to the reporter this affects Ubuntu 20.04 / 5.4.0-52 and
+ 20.10 / 5.8.0-26.
+
+ * Since the development of Hirsute is already open the SRU is requested
+ for Hirsute, too.
+
+ * Patches got upstream accepted in v5.10-rc1 and v5.10-rc2.
** Summary changed:
- Ubuntu 20.10- Undetected Data corruption in MPI workloads that use VSX for
reductions on POWER9 DD2.1 systems
+ Undetected Data corruption in MPI workloads that use VSX for reductions on
POWER9 DD2.1 systems
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1902694
Title:
Undetected Data corruption in MPI workloads that use VSX for
reductions on POWER9 DD2.1 systems
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1902694/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1902783] Re: Super key is not working
Actually regarding comment #2, your setting: b'org.gnome.mutter' b'overlay-key' b"''" shows the Super key is disabled and not expected to work. So that makes this bug invalid. To get it back, run: gsettings set org.gnome.mutter overlay-key 'Super_L' ** Changed in: gnome-shell (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1902783 Title: Super key is not working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1902783/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1900438] Re: Bcache bypasse writeback on caching device with fragmentation
I've just submitted a patch[1] to upstream for review to help with this problem. The key is to speed up the writeback rate when the fragmentation is high. Here are the comments from the patch: Current way to calculate the writeback rate only considered the dirty sectors, this usually works fine when the fragmentation is not high, but it will give us unreasonable small rate when we are under a situation that very few dirty sectors consumed a lot dirty buckets. In some case, the dirty bucekts can reached to CUTOFF_WRITEBACK_SYNC while the dirty data(sectors) noteven reached the writeback_percent, the writeback rate will still be the minimum value (4k), thus it will cause all the writes to be stucked in a non-writeback mode because of the slow writeback. This patch will try to accelerate the writeback rate when the fragmentation is high. It calculate the propotional_scaled value based on below: (dirty_sectors / writeback_rate_p_term_inverse) * fragment As we can see, the higher fragmentation will result a larger proportional_scaled value, thus cause a larger writeback rate. The fragment value is calculated based on below: (dirty_buckets * bucket_size) / dirty_sectors If you think about it, the value of fragment will be always inside [1, bucket_size]. This patch only considers the fragmentation when the number of dirty_buckets reached to a dirty threshold(configurable by writeback_fragment_percent, default is 50), so bcache will remain the original behaviour before the dirty buckets reached the threshold. [1] https://marc.info/?l=linux-bcache=160441418209114=1 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1900438 Title: Bcache bypasse writeback on caching device with fragmentation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1900438/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1898325] Re: Gnome calendar is not syncing with Google calendar online account.
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gnome-calendar (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/1898325 Title: Gnome calendar is not syncing with Google calendar online account. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-calendar/+bug/1898325/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1895905] Re: lubuntu groovy; flashing of sddm greeter
Lubuntu hirsute install on dell [optiplex] 990 (i7-2600, 16gb, nvidia geforce gt 6600 gt) wxl suggested (https://discourse.lubuntu.me/t/login-screen- flashes/1634/14?u=guiverc) exploration of this, so I did a clean install so I can play It's worse than any groovy install, something may have changed, as the response is different (& worse) .. the whole screen is flashing (except for top panel) [instead of just small portions of the screen] -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1895905 Title: lubuntu groovy; flashing of sddm greeter To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1895905/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1899304] Re: Linux 5.4.0-48 (and later) causes GPU lockup, huge performance drop, makes GNOME desktop fail to start and games going from 70fps to 7fps, slow file loading, audio issues
So, the 5.4.0-48 error is the same as the one that appears with 5.9 (and the one we see with PCI GPUs): ``` [0.00] Linux version 5.4.0-48-generic (buildd@lcy01-amd64-010) (gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2)) #52-Ubuntu SMP Thu Sep 10 10:58:49 UTC 2020 (Ubuntu 5.4.0-48.52-generic 5.4.60) … [3.366387] PCI Interrupt Link [LKLN] enabled at IRQ 21 [3.426007] [drm] radeon kernel modesetting enabled. [3.435680] radeon :01:00.0: remove_conflicting_pci_framebuffers: bar 0: 0xe000 -> 0xefff [3.456237] radeon :01:00.0: remove_conflicting_pci_framebuffers: bar 2: 0xfebe -> 0xfebe [3.478847] checking generic (e000 13) vs hw (e000 1000) [3.478853] fb0: switching to radeondrmfb from VESA VGA [3.490892] Console: switching to colour dummy device 80x25 [3.490909] radeon :01:00.0: vgaarb: deactivate vga console [3.491182] PCI Interrupt Link [LNKD] enabled at IRQ 19 [3.491321] [drm] initializing kernel modesetting (RV730 0x1002:0x9495 0x1002:0x0028 0x00). [3.491325] [drm] Forcing AGP to PCIE mode [3.491353] resource sanity check: requesting [mem 0x000c-0x000d], which spans more than PCI Bus :00 [mem 0x000d-0x000d window] [3.491359] caller pci_map_rom+0x71/0x18c mapping multiple BARs [3.492982] ATOM BIOS: RV730XT [3.493101] radeon :01:00.0: VRAM: 1024M 0x - 0x3FFF (1024M used) [3.493104] radeon :01:00.0: GTT: 1024M 0x4000 - 0x7FFF [3.493108] [drm] Detected VRAM RAM=1024M, BAR=256M [3.493110] [drm] RAM width 128bits DDR [3.493193] [TTM] Zone kernel: Available graphics memory: 8231890 KiB [3.493195] [TTM] Zone dma32: Available graphics memory: 2097152 KiB [3.493198] [TTM] Initializing pool allocator [3.493203] [TTM] Initializing DMA pool allocator [3.493221] [drm] radeon: 1024M of VRAM memory ready [3.493223] [drm] radeon: 1024M of GTT memory ready. [3.493230] [drm] Loading RV730 Microcode [3.493316] [drm] Internal thermal controller without fan control [3.512582] [drm] radeon: dpm initialized [3.512696] [drm] GART: num cpu pages 262144, num gpu pages 262144 [3.534540] [drm] PCIE GART of 1024M enabled (table at 0x0014C000). [3.534726] radeon :01:00.0: WB enabled [3.534730] radeon :01:00.0: fence driver on ring 0 use gpu addr 0x4c00 and cpu addr 0x(ptrval) [3.534733] radeon :01:00.0: fence driver on ring 3 use gpu addr 0x4c0c and cpu addr 0x(ptrval) [3.541143] radeon :01:00.0: fence driver on ring 5 use gpu addr 0x0005c598 and cpu addr 0x(ptrval) [3.541147] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013). [3.541149] [drm] Driver supports precise vblank timestamp query. [3.541151] radeon :01:00.0: radeon: MSI limited to 32-bit [3.541204] [drm] radeon: irq initialized. … [5.677888] [drm:r600_ring_test [radeon]] *ERROR* radeon: ring 0 test failed (scratch(0x8504)=0xCAFEDEAD) [5.677934] radeon :01:00.0: disabling GPU acceleration [5.696050] [drm] Radeon Display Connectors [5.696054] [drm] Connector 0: [5.696055] [drm] VGA-1 [5.696057] [drm] DDC: 0x7e40 0x7e40 0x7e44 0x7e44 0x7e48 0x7e48 0x7e4c 0x7e4c [5.696059] [drm] Encoders: [5.696061] [drm] CRT2: INTERNAL_KLDSCP_DAC2 [5.696062] [drm] Connector 1: [5.696063] [drm] HDMI-A-1 [5.696064] [drm] HPD2 [5.696066] [drm] DDC: 0x7f10 0x7f10 0x7f14 0x7f14 0x7f18 0x7f18 0x7f1c 0x7f1c [5.696068] [drm] Encoders: [5.696069] [drm] DFP2: INTERNAL_UNIPHY1 [5.696070] [drm] Connector 2: [5.696072] [drm] DVI-I-1 [5.696073] [drm] HPD1 [5.696074] [drm] DDC: 0x7e20 0x7e20 0x7e24 0x7e24 0x7e28 0x7e28 0x7e2c 0x7e2c [5.696076] [drm] Encoders: [5.696077] [drm] CRT1: INTERNAL_KLDSCP_DAC1 [5.696079] [drm] DFP1: INTERNAL_UNIPHY … [5.905120] [drm] fb mappable at 0xE034D000 [5.905124] [drm] vram apper at 0xE000 [5.905126] [drm] size 8294400 [5.905127] [drm] fb depth is 24 [5.905129] [drm]pitch is 7680 [5.905201] fbcon: radeondrmfb (fb0) is primary device [5.933430] Console: switching to colour frame buffer device 240x67 … [5.983571] radeon :01:00.0: fb0: radeondrmfb frame buffer device [5.996432] [drm] Initialized radeon 2.50.0 20080528 for :01:00.0 on minor 0 … … [ 36.254301] [ cut here ] [ 36.254305] trying to bind memory to uninitialized GART ! [ 36.254467] WARNING: CPU: 3 PID: 2559 at drivers/gpu/drm/radeon/radeon_gart.c:299 radeon_gart_bind+0xef/0x100 [radeon] [ 36.254469] Modules linked in: zram snd_hda_intel snd_intel_dspcfg snd_usb_audio snd_hda_codec snd_hda_core snd_usbmidi_lib snd_hwdep mc snd_pcm snd_seq_midi joydev input_leds snd_seq_midi_event snd_rawmidi snd_seq edac_mce_amd snd_seq_device
[Bug 1901355] Re: Groovy: libsmbclient users FTBFS against Samba 4.12.5
The attachment "add-missing-time-h-include.patch" 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/1901355 Title: Groovy: libsmbclient users FTBFS against Samba 4.12.5 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1901355/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1505961] Re: Internal Server Error: /dashboard/admin/volumes/ in Horizon
[Expired for python-cinderclient (Ubuntu) because there has been no activity for 60 days.] ** Changed in: python-cinderclient (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/1505961 Title: Internal Server Error: /dashboard/admin/volumes/ in Horizon To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-cinderclient/+bug/1505961/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1893833] Re: grub does not initialize display
[Expired for grub2 (Ubuntu) because there has been no activity for 60 days.] ** Changed in: grub2 (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/1893833 Title: grub does not initialize display To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1893833/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1835654] Re: Extracting a zip archieve creates a new unwanted folder
[Expired for file-roller (Ubuntu) because there has been no activity for 60 days.] ** Changed in: file-roller (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/1835654 Title: Extracting a zip archieve creates a new unwanted folder To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/file-roller/+bug/1835654/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1848559] Re: i couldn't access into settings and tweaks, when i clicked to them, it was setup and about 5 seconds later, they're disappeared
[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/1848559 Title: i couldn't access into settings and tweaks, when i clicked to them, it was setup and about 5 seconds later, they're disappeared To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1848559/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1864244] Re: Text selection in address bar does not work as expected
[Expired for nautilus (Ubuntu) because there has been no activity for 60 days.] ** Changed in: nautilus (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/1864244 Title: Text selection in address bar does not work as expected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1864244/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1899304] Re: Linux 5.4.0-48 (and later) causes GPU lockup, huge performance drop, makes GNOME desktop fail to start and games going from 70fps to 7fps, slow file loading, audio issues
** Attachment added: "dmesg on Linux 5.4.0-48-generic on Ubuntu 20.04, K10 platform, ATI Radeon HD 4670 (truncated because it was weighting 62MB)" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1899304/+attachment/5430878/+files/dmesg.ubuntu-20.04.linux-5.4.0-48-generic_ASRock-AM2NF3-VSTA+K10_ATI-Radeon-HD-4670-AGP.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1899304 Title: Linux 5.4.0-48 (and later) causes GPU lockup, huge performance drop, makes GNOME desktop fail to start and games going from 70fps to 7fps, slow file loading, audio issues To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1899304/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1898905] Autopkgtest regression report (sane-backends/1.0.31-2ubuntu0.20.10)
All autopkgtests for the newly accepted sane-backends (1.0.31-2ubuntu0.20.10) for groovy have finished running. The following regressions have been reported in tests triggered by the package: gscan2pdf/2.8.2-1ubuntu2 (arm64, armhf) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/groovy/update_excuses.html#sane-backends [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1898905 Title: Unfunctional plustek scanner in Ubuntu 20.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1898905/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1894160] Re: package nvidia-340 (not installed) failed to install/upgrade: intentando sobreescribir `/lib/udev/rules.d/71-nvidia.rules', que está también en el paquete nvidia-kernel-common-450 45
[Expired for nvidia-graphics-drivers-340 (Ubuntu) because there has been no activity for 60 days.] ** Changed in: nvidia-graphics-drivers-340 (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/1894160 Title: package nvidia-340 (not installed) failed to install/upgrade: intentando sobreescribir `/lib/udev/rules.d/71-nvidia.rules', que está también en el paquete nvidia-kernel-common-450 450.66-0ubuntu0.20.04.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1894160/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1894232] Re: blank black screen or cursor on top left corner on a black screen problem
[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/1894232 Title: blank black screen or cursor on top left corner on a black screen problem To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1894232/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1902810] Re: Video Flicker
Next time the problem starts happening please run: journalctl -b0 > journal.txt and attach the resulting text file here. Separately, please also try selecting 'Ubuntu on Wayland' from the login screen, just before you enter your password. ** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu) ** Changed in: xorg-server (Ubuntu) Status: New => Incomplete ** Summary changed: - Video Flicker + [i915] Video Flicker ** Summary changed: - [i915] Video Flicker + [i915] Dell Latitude 5285 video flicker when an external monitor is connected -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1902810 Title: [i915] Dell Latitude 5285 video flicker when an external monitor is connected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1902810/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1902783] Re: Super key is not working
It looks like you have lost your overlay key setting. Please try this to restore it: gsettings set org.gnome.mutter overlay-key 'Super_L' -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1902783 Title: Super key is not working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1902783/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1902783] Re: Super key is not working
If the above command does not fix the problem then next please try uninstalling these extensions: 'extension-shortc...@shs-schubert.de', 'transparenttop...@peclu.net', 'openweather-extens...@jenslody.de', 'systemMonitor@gnome-shell- extensions.gcampax.github.com', 'drawonyourscr...@abakkk.framagit.org', 'applications-overview-tooltip@RaphaelRochet', 'apt-update- indica...@franglais125.gmail.com', 'caffe...@patapon.info', 'gsconn...@andyholmes.github.io', 'drop-down-termina...@bigbn.pro', 'places-m...@gnome-shell-extensions.gcampax.github.com', 'screenshot- window-si...@gnome-shell-extensions.gcampax.github.com', 'windowsnaviga...@gnome-shell-extensions.gcampax.github.com', 'apps-menu @gnome-shell-extensions.gcampax.github.com', 'pomod...@arun.codito.in', 'amdtool...@zerosubnet.com', 'radeon-dpm-control@s3rius', 'freon@Veske', 'auto-move-wind...@gnome-shell-extensions.gcampax.github.com', 'custom- hot-corn...@janrunx.gmail.com', 'extensi...@abteil.org', 'drive-menu @gnome-shell-extensions.gcampax.github.com', 'system- moni...@paradoxxx.zero.gmail.com' ** 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/1902783 Title: Super key is not working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1902783/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1902766] Re: Automatic suspend when idle not working in 20.10
Please also try waiting over 30 minutes, because I notice your idle- delay is set to 10 minutes so maybe they are additive... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1902766 Title: Automatic suspend when idle not working in 20.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1902766/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1902766] Re: Automatic suspend when idle not working in 20.10
Please try: * Uninstalling these extensions: 'mprisindicatorbut...@jasonlg1979.github.io', 'bat...@martin.zurowietz.de', 'multi-volume@tigersoldier', 'd...@rastersoft.com' and then reboot. * Running these commands: gsettings get org.gnome.desktop.lockdown disable-lock-screen > lockscreen.txt systemd-inhibit --list --mode=block > inhibit.txt and attach the resulting text files here. ** 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/1902766 Title: Automatic suspend when idle not working in 20.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1902766/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1902766] Re: Automatic suspend when idle not working in 20.10
Please also try removing or turning off any Bluetooth or wireless peripherals you may have. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1902766 Title: Automatic suspend when idle not working in 20.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1902766/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1902749] Re: Log in screen flashes on and off until I log in
Please try (in this order): * Selecting 'Ubuntu on Wayland' from the login screen before you enter your password (the icon in the bottom right corner). Now does the flashing also happen on the desktop? * The official Ubuntu kernel, which is version 5.4. * A slightly older kernel like 5.8. * Editing /etc/gdm3/custom.conf and uncomment: #WaylandEnable=false to: WaylandEnable=false ** Tags added: amdgpu hybrid nvidia ** Summary changed: - Log in screen flashes on and off until I log in + [amdgpu] [nvidia] Log in screen flashes on and off until I log in ** Package changed: xorg (Ubuntu) => xserver-xorg-video-amdgpu (Ubuntu) ** Summary changed: - [amdgpu] [nvidia] Log in screen flashes on and off until I log in + [amdgpu] Log in screen flashes on and off until I log in ** Also affects: mutter (Ubuntu) Importance: Undecided Status: New ** Changed in: mutter (Ubuntu) Status: New => Incomplete ** Changed in: xserver-xorg-video-amdgpu (Ubuntu) Status: New => Incomplete ** No longer affects: xserver-xorg-video-amdgpu (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1902749 Title: [amdgpu] Log in screen flashes on and off until I log in To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1902749/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1902813] [NEW] obex-data-server not supported in 20.04 Focal Fossa
Public bug reported: [Summary] obex-data-server not supported in 20.04 Focal Fossa Publishing history of obex-data-server 0.4.6-1build1 source package in Ubuntu: https://launchpad.net/ubuntu/+source/obex-data- server/0.4.6-1build1/+publishinghistory Publishing history of obex-data-server 0.4.6-1 source package in Ubuntu: https://launchpad.net/ubuntu/+source/obex-data- server/0.4.6-1/+publishinghistory [Expected] obex-data-server support to 20.04 ** Affects: obex-data-server (Ubuntu) Importance: Undecided Status: New ** Tags: focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1902813 Title: obex-data-server not supported in 20.04 Focal Fossa To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/obex-data-server/+bug/1902813/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1899304] Re: Linux 5.4.0-48 (and later) causes GPU lockup, huge performance drop, makes GNOME desktop fail to start and games going from 70fps to 7fps, slow file loading, audio issues
Related and similar issue with PCI graphic cards (not AGP ones): https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1902795 While PCI graphic cards are broken on AMD K8/K10 platform for years (I've reproduced on Linux 4.4, 4.8 and 4.15 from Ubuntu 16.04 Xenial), AGP cards started to break on Ubuntu with 5.4.0-48-generic (was still working with 5.4.0-47-generic). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1899304 Title: Linux 5.4.0-48 (and later) causes GPU lockup, huge performance drop, makes GNOME desktop fail to start and games going from 70fps to 7fps, slow file loading, audio issues To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1899304/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1899304] Re: Linux 5.4.0-48 (and later) causes GPU lockup, huge performance drop, makes GNOME desktop fail to start and games going from 70fps to 7fps, slow file loading, audio issues
** Attachment added: "dmesg on Linux 5.10.0-051000rc1-generic on Ubuntu 20.04, K10 platform, ATI Radeon HD 4670 AGP" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1899304/+attachment/5430875/+files/dmesg.ubuntu-20.04.linux-5.10.0-051000rc1-generic_ASRock-AM2NF3-VSTA+K10_ATI-Radeon-HD-4670-AGP.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1899304 Title: Linux 5.4.0-48 (and later) causes GPU lockup, huge performance drop, makes GNOME desktop fail to start and games going from 70fps to 7fps, slow file loading, audio issues To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1899304/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1899304] Re: Linux 5.4.0-48 (and later) causes GPU lockup, huge performance drop, makes GNOME desktop fail to start and games going from 70fps to 7fps, slow file loading, audio issues
** Attachment added: "dmesg on Linux 5.9 vanilla on Ubuntu 20.04, K10 platform, ATI Radeon HD 4670 AGP" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1899304/+attachment/5430874/+files/dmesg.ubuntu-20.04.linux-5.9-vanilla_ASRock-AM2NF3-VSTA+K10_ATI-Radeon-HD-4670-AGP.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1899304 Title: Linux 5.4.0-48 (and later) causes GPU lockup, huge performance drop, makes GNOME desktop fail to start and games going from 70fps to 7fps, slow file loading, audio issues To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1899304/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1899304] Re: Linux 5.4.0-48 (and later) causes GPU lockup, huge performance drop, makes GNOME desktop fail to start and games going from 70fps to 7fps, slow file loading, audio issues
For some reason I was able to compile v5.4 and v5.5 from torvalds branchs with `make -j$(nproc) deb-pkg` but starting with v5.6 I had to use `make -j$(nproc) bindeb-pkg`, in the end I lacked some modules (like my network driver, that did not helped me) but radeon one was there so tests could have been done. The GNOME desktop opened properly with 5.4, 5.5, 5.6, 5.7 and 5.8. But when v5.9, I just got the desktop (GDM is configured to autologin) restarting again and again, only showing me a mouse cursor before dying. The errors in dmesg were similar to the one I found with PCI devices (not AGP ones!) on the same AMD K8 or K10-based motherboard I reproduce issue with AGP devices. Also, the errors in vanilla 5.9 look to be the same as the one seen in 5.10-rc1 from mainline PPA. Here is a sample of captured dmesg error on vanilla 5.9: ``` [5.242322] [drm:r600_ring_test [radeon]] *ERROR* radeon: ring 0 test failed (scratch(0x8504)=0xCAFEDEAD) [5.242359] radeon :01:00.0: disabling GPU acceleration … [ 34.558885] [ cut here ] [ 34.558889] trying to bind memory to uninitialized GART ! [ 34.559048] WARNING: CPU: 1 PID: 2516 at drivers/gpu/drm/radeon/radeon_gart.c:299 radeon_gart_bind+0xdf/0xf0 [radeon] [ 34.559050] Modules linked in: zram snd_usb_audio snd_hda_intel snd_intel_dspcfg snd_hda_codec snd_usbmidi_lib snd_hda_core snd_hwdep snd_pcm snd_seq_midi kvm_amd snd_seq_midi_event ccp joydev kvm snd_seq snd_rawmidi input_leds snd_timer snd_seq_device snd soundcore k10temp mac_hid serio_raw binfmt_misc sch_fq_codel parport_pc ppdev lp parport ip_tables x_tables btrfs blake2b_generic zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx libcrc32c xor raid6_pq raid1 raid0 multipath linear uas usb_storage hid_generic usbhid hid radeon i2c_algo_bit drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops ttm drm psmouse forcedeth i2c_nforce2 [ 34.559107] CPU: 1 PID: 2516 Comm: gnome-shell Not tainted 5.9.0 #1 [ 34.559109] Hardware name: To Be Filled By O.E.M. To Be Filled By O.E.M./AM2NF3-VSTA, BIOS P3.20 10/09/2009 [ 34.559178] RIP: 0010:radeon_gart_bind+0xdf/0xf0 [radeon] [ 34.559184] Code: 00 48 89 ef 48 8b 40 60 e8 0e 2f 44 df 31 c0 48 83 c4 08 5b 5d 41 5c 41 5d 41 5e 41 5f c3 48 c7 c7 38 6f 6b c0 e8 23 0c 6d de <0f> 0b b8 ea ff ff ff eb dc 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 [ 34.559187] RSP: 0018:c030838f7a28 EFLAGS: 00010282 [ 34.559191] RAX: RBX: a0cf6b88eb80 RCX: 0027 [ 34.559193] RDX: 0027 RSI: 0086 RDI: a0cf6fc98d08 [ 34.559196] RBP: c030838f7b28 R08: a0cf6fc98d00 R09: 0004 [ 34.559198] R10: R11: 0001 R12: c030838f7b28 [ 34.559201] R13: a0cf6a622868 R14: a0cf6c7cc6e8 R15: c030838f7b28 [ 34.559204] FS: 7f46ae245cc0() GS:a0cf6fc8() knlGS: [ 34.559207] CS: 0010 DS: ES: CR0: 80050033 [ 34.559210] CR2: 56494261c1c8 CR3: 00040bfe6000 CR4: 06e0 [ 34.559212] Call Trace: [ 34.559286] radeon_ttm_backend_bind+0x58/0x210 [radeon] [ 34.559305] ttm_tt_bind+0x32/0x60 [ttm] [ 34.559321] ttm_bo_handle_move_mem+0x236/0x590 [ttm] [ 34.559339] ttm_bo_validate+0x16c/0x180 [ttm] [ 34.559407] ? drm_ioctl_kernel+0xe9/0xf0 [drm] [ 34.559422] ttm_bo_init_reserved+0x2ae/0x320 [ttm] [ 34.559438] ttm_bo_init+0x6d/0xf0 [ttm] [ 34.559504] ? radeon_update_memory_usage.isra.0+0x50/0x50 [radeon] [ 34.559569] radeon_bo_create+0x184/0x210 [radeon] [ 34.559634] ? radeon_update_memory_usage.isra.0+0x50/0x50 [radeon] [ 34.559703] radeon_gem_object_create+0xa9/0x180 [radeon] [ 34.559773] ? radeon_gem_pwrite_ioctl+0x20/0x20 [radeon] [ 34.559840] radeon_gem_create_ioctl+0x66/0x120 [radeon] [ 34.559850] ? tomoyo_path_number_perm+0x66/0x1d0 [ 34.559918] ? radeon_gem_pwrite_ioctl+0x20/0x20 [radeon] [ 34.559968] drm_ioctl_kernel+0xaa/0xf0 [drm] [ 34.560021] drm_ioctl+0x1ec/0x390 [drm] [ 34.560090] ? radeon_gem_pwrite_ioctl+0x20/0x20 [radeon] [ 34.560152] radeon_drm_ioctl+0x49/0x80 [radeon] [ 34.560160] __x64_sys_ioctl+0x83/0xb0 [ 34.560167] do_syscall_64+0x33/0x80 [ 34.560174] entry_SYSCALL_64_after_hwframe+0x44/0xa9 [ 34.560179] RIP: 0033:0x7f46b369550b [ 34.560183] Code: 0f 1e fa 48 8b 05 85 39 0d 00 64 c7 00 26 00 00 00 48 c7 c0 ff ff ff ff c3 66 0f 1f 44 00 00 f3 0f 1e fa b8 10 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d 55 39 0d 00 f7 d8 64 89 01 48 [ 34.560186] RSP: 002b:7ffdb7421658 EFLAGS: 0246 ORIG_RAX: 0010 [ 34.560189] RAX: ffda RBX: 7ffdb74216d0 RCX: 7f46b369550b [ 34.560192] RDX: 7ffdb74216d0 RSI: c020645d RDI: 000e [ 34.560194] RBP: c020645d R08: 0011 R09: 0005 [ 34.560197] R10: 56494245c010 R11: 0246 R12:
[Bug 1893300] Re: The status of cups still shows idle when the printer has been unplugged
** Changed in: oem-priority Status: In Progress => Triaged -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1893300 Title: The status of cups still shows idle when the printer has been unplugged To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1893300/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1893300] Re: The status of cups still shows idle when the printer has been unplugged
** Tags added: verification-needed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1893300 Title: The status of cups still shows idle when the printer has been unplugged To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1893300/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1893300] Re: The status of cups still shows idle when the printer has been unplugged
And this is the package diff for focal ** Patch added: "system-config-printer-focal.diff" https://bugs.launchpad.net/oem-priority/+bug/1893300/+attachment/5430871/+files/system-config-printer-focal.diff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1893300 Title: The status of cups still shows idle when the printer has been unplugged To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1893300/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1893300] Re: The status of cups still shows idle when the printer has been unplugged
Here is the package diff for groovy ** Patch added: "system-config-printer-groovy.diff" https://bugs.launchpad.net/oem-priority/+bug/1893300/+attachment/5430870/+files/system-config-printer-groovy.diff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1893300 Title: The status of cups still shows idle when the printer has been unplugged To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1893300/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1899460] Re: tpm2_nvdefine without specifying the size issue
** Description changed: nvdefind tool takes the size MAX_NV_INDEX_SIZE(2048) as default, but got errors(0x2D5) returned on those platforms which don't have the size as default. https://github.com/tpm2-software/tpm2-tools/issues/2171 [Impact] - Some machines which don't have enough MAX_NV_INDEX_SIZE as defaule will got "the structure is the wrong size(0x2D5)" error when using tpm2_nvdefine without specifying the size of data area + Some machines which don't have enough MAX_NV_INDEX_SIZE as default will got "the structure is the wrong size(0x2D5)" error when using tpm2_nvdefine without specifying the size of data area [Test cases] run nvdefine without specifying the size of data area [Solution] A fix patch has been committed and accepted by maintainer https://github.com/tpm2-software/tpm2-tools/commit/48594efa6f1faca50c73ce0d88f6e99eb0f5005c [Regression Potential] Minimal, it fixed the issue by checking the platform capabilities instead of using default. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1899460 Title: tpm2_nvdefine without specifying the size issue To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tpm2-tools/+bug/1899460/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1902578] Re: Ethernet no link lights after reboot (Intel i225-v 2.5G)
** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1902578 Title: Ethernet no link lights after reboot (Intel i225-v 2.5G) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1902578/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1868207] Re: Fractional scaling window sizes incorrect after resume from suspend
Thanks. I should have said "hear back"... In that case this bug should be closed and anyone like krul still experiencing issues, please open a new bug by running: ubuntu-bug mutter ** Changed in: mutter (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1868207 Title: Fractional scaling window sizes incorrect after resume from suspend To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1868207/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1902578] Re: Ethernet no link lights after reboot (Intel i225-v 2.5G)
I believe the bisect is done: Building this commit causes the ethernet to work after reboots. (a PHY problem seems to make sense as there's no link lights). bcb3244ccdc4cebb6ed3d47d973da7b1a03837c0 is the first new commit commit bcb3244ccdc4cebb6ed3d47d973da7b1a03837c0 Author: Sasha Neftin Date: Wed Jan 8 10:19:24 2020 +0200 igc: Add PHY power management control PHY power management control should provide a reliable and accurate indication of PHY reset completion and decrease the delay time after a PHY reset Signed-off-by: Sasha Neftin Tested-by: Aaron Brown Signed-off-by: Jeff Kirsher drivers/net/ethernet/intel/igc/igc_defines.h | 1 + drivers/net/ethernet/intel/igc/igc_phy.c | 16 +++- drivers/net/ethernet/intel/igc/igc_regs.h| 1 + 3 files changed, 17 insertions(+), 1 deletion(-) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1902578 Title: Ethernet no link lights after reboot (Intel i225-v 2.5G) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1902578/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1902721] Re: xrandr fails to set screen size while starting X11
In theory you should never need to use 'xrandr' at all... I've decoded your monitor's EDID data and got: EDID version: 1.3 Manufacturer: PHL Model 2290 Serial Number 174 Made in week 46 of 2016 Digital display Maximum image size: 62 cm x 34 cm Gamma: 2.20 DPMS levels: Off RGB color display First detailed timing is preferred timing Color Characteristics Red: 0.6298, 0.3408 Green: 0.3095, 0.6259 Blue: 0.1562, 0.0605 White: 0.3134, 0.3291 Established Timings I & II 720x40070.082 Hz 9:531.467 kHz 28.320 MHz (IBM) 640x48059.940 Hz 4:331.469 kHz 25.175 MHz (DMT) 640x48066.667 Hz 4:335.000 kHz 30.240 MHz (Apple) 640x48072.809 Hz 4:337.861 kHz 31.500 MHz (DMT) 640x48075.000 Hz 4:337.500 kHz 31.500 MHz (DMT) 800x60060.317 Hz 4:337.879 kHz 40.000 MHz (DMT) 800x60075.000 Hz 4:346.875 kHz 49.500 MHz (DMT) 1024x76860.004 Hz 4:348.363 kHz 65.000 MHz (DMT) 1024x76875.029 Hz 4:360.023 kHz 78.750 MHz (DMT) 1280x1024 75.025 Hz 5:479.976 kHz 135.000 MHz (DMT) Standard Timings 1920x1080 60.000 Hz 16:967.500 kHz 148.500 MHz (DMT) 1280x1024 60.020 Hz 5:463.981 kHz 108.000 MHz (DMT) 1280x96060.000 Hz 4:360.000 kHz 108.000 MHz (DMT) 1440x90074.984 Hz 16:10 70.635 kHz 136.750 MHz (DMT) 1440x90059.887 Hz 16:10 55.935 kHz 106.500 MHz (DMT) 1680x1050 59.954 Hz 16:10 65.290 kHz 146.250 MHz (DMT) 1280x72060.000 Hz 16:945.000 kHz 74.250 MHz (DMT) Detailed mode: Clock 533.250 MHz, 621 mm x 341 mm 3840 3888 3920 4000 ( 48 32 80) 2160 2163 2168 ( 3 5 54) +hsync -vsync VertFreq: 59.997 Hz, HorFreq: 133.312 kHz Detailed mode: Clock 262.750 MHz, 621 mm x 341 mm 3840 3888 3920 4000 ( 48 32 80) 2160 2163 2168 2191 ( 3 5 23) +hsync -vsync VertFreq: 29.981 Hz, HorFreq: 65.688 kHz Display Product Name: PHL 288P6L Display Range Limits Monitor ranges (GTF): 23-80 Hz V, 30-99 kHz H, max dotclock 600 MHz Has 1 extension block Checksum: 0x4c CTA-861 Extension Block Revision 3 Underscans PC formats by default Basic audio support Supports YCbCr 4:4:4 Supports YCbCr 4:2:2 1 native detailed modes 47 bytes of CTA data blocks Video Data Block 1920x1080 60.000 Hz 16:967.500 kHz 148.500 MHz (VIC 16, native) 1280x72060.000 Hz 16:945.000 kHz 74.250 MHz (VIC 4) 720x48059.940 Hz 16:931.469 kHz 27.000 MHz (VIC 3) 1920x1080 50.000 Hz 16:956.250 kHz 148.500 MHz (VIC 31) 1280x72050.000 Hz 16:937.500 kHz 74.250 MHz (VIC 19) 640x48059.940 Hz 4:331.469 kHz 25.175 MHz (VIC 1) 720x57650.000 Hz 16:931.250 kHz 27.000 MHz (VIC 18) 3840x2160 24.000 Hz 16:954.000 kHz 297.000 MHz (VIC 93) 3840x2160 25.000 Hz 16:956.250 kHz 297.000 MHz (VIC 94) 3840x2160 30.000 Hz 16:967.500 kHz 297.000 MHz (VIC 95) 3840x2160 50.000 Hz 16:9 112.500 kHz 594.000 MHz (VIC 96) 3840x2160 60.000 Hz 16:9 135.000 kHz 594.000 MHz (VIC 97) Audio Data Block Linear PCM, max channels 2 Supported sample rates (kHz): 48 44.1 32 Supported sample sizes (bits): 24 20 16 Speaker Allocation Data Block Speaker map: FL/FR - Front Left/Right Vendor-Specific Data Block, OUI 0x000c03 (HDMI) Source physical address 1.4.0.0 DC_36bit DC_30bit DC_Y444 DVI_Dual Maximum TMDS clock: 600 MHz Extended HDMI video details: HDMI VICs: 3840x2160 30.000 Hz 16:967.500 kHz 297.000 MHz (HDMI VIC 1) 3840x2160 25.000 Hz 16:956.250 kHz 297.000 MHz (HDMI VIC 2) 3840x2160 24.000 Hz 16:954.000 kHz 297.000 MHz (HDMI VIC 3) Vendor-Specific Data Block, OUI 0xc45dd8 (HDMI Forum) Version: 1 Maximum TMDS Character Rate: 600 MHz SCDC Present Supports 12-bits/component Deep Color 4:2:0 Pixel Encoding Supports 10-bits/component Deep Color 4:2:0 Pixel Encoding Extended tag: YCbCr 4:2:0 Capability Map Data Block 3840x2160 50.000 Hz 16:9 112.500 kHz 594.000 MHz (VIC 96) 3840x2160 60.000 Hz 16:9 135.000 kHz 594.000 MHz (VIC 97) Detailed mode: Clock 74.250 MHz, 621 mm x 341 mm 1280 1390 1430 1650 (110 40 220) 720 725 730 750 ( 5 5 20) +hsync +vsync VertFreq: 60.000 Hz, HorFreq: 45.000 kHz Detailed mode: Clock 27.000 MHz, 621 mm x 341 mm 720 736 798 858 ( 16 62 60) 480 489 495 525 ( 9 6 30) -hsync -vsync VertFreq: 59.940 Hz, HorFreq: 31.469 kHz Detailed mode: Clock 277.250 MHz, 621 mm x 341 mm 1920 1968 2000 2080 ( 48 32 80) 2160 2163 2173 ( 3 10 49)
[Bug 1893300] Re: The status of cups still shows idle when the printer has been unplugged
** Description changed: [ Impact ] After printers (non-ippusb protocal) have been disconnected, the status of cups still shows "idle" instead of "disabled", so seems the disconnected procedure hasn't worked well. [ Test Case ] 1. Connect the printer (non-ippusb protocal)(which isn't 070104) with any 20.04 machine 2. Wait for the status of cups became "Idle" (lpstat -p) 3. Unplug the cable of the printer 4. Check the status of cups again. (lpstat -p) + + [ Regression potential ] + Low, the change just makes "strcmp" to "srtsrt" and has more checks on the existing of device path. [Expected result] The status should show disabled. [Actual result] The status shows idle. [info] Target: HP LaserJet Pro203dw HP Officejet 100 Mobile Printer HP Officeject 200 Mobile Printer Brother HL-2250DN Samsung ML-331x Upstream Bug: https://github.com/OpenPrinting/system-config- printer/issues/182 PPA: https://launchpad.net/~hugh712/+archive/ubuntu/sru-1893300 ** Also affects: oem-priority/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/1893300 Title: The status of cups still shows idle when the printer has been unplugged To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1893300/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1902721] Re: xrandr fails to set screen size while starting X11
I would like to find out if the missing mode problem originates from the kernel. Please run: grep . /sys/class/drm/*/modes > drmmodes.txt and attach the resulting text file here. ** Changed in: xorg-server (Ubuntu) Status: New => Incomplete ** Changed in: x11-xserver-utils (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/1902721 Title: xrandr fails to set screen size while starting X11 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/x11-xserver-utils/+bug/1902721/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1902810] [NEW] Video Flicker
Public bug reported: The display on this Dell Latitude 5285 with detachable keyboard flickers when an external monitor is connected. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.8.0-7625.26~1603389471~20.04~f6b125f-generic 5.8.14 Uname: Linux 5.8.0-7625-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.10 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read kernel buffer failed: Operation not permitted Date: Tue Nov 3 18:38:42 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: I just need to know a workaround GraphicsCard: Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Dell HD Graphics 620 [1028:07a4] InstallationDate: Installed on 2020-07-01 (125 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bus 001 Device 022: ID 044e:1218 Alps Electric Co., Ltd Alps Touchpad Bus 001 Device 004: ID 0a5c:5834 Broadcom Corp. 5880 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Latitude 5285 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-7625-generic root=UUID=f22e0756-4530-44bf-8da3-d0ed47ef183a ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/24/2020 dmi.bios.release: 1.10 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.10.1 dmi.board.vendor: Dell Inc. dmi.chassis.type: 32 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.10.1:bd07/24/2020:br1.10:svnDellInc.:pnLatitude5285:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct32:cvr: dmi.product.family: Latitude dmi.product.name: Latitude 5285 dmi.product.sku: 07A4 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.4 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: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal third-party-packages ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1902810 Title: Video Flicker To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1902810/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1868207] Re: Fractional scaling window sizes incorrect after resume from suspend
Nothing extra to report - haven't seen it again. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1868207 Title: Fractional scaling window sizes incorrect after resume from suspend To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1868207/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1868207] Re: Fractional scaling window sizes incorrect after resume from suspend
Thanks krul, that confirms fractional scaling for you. I am still curious to also here back from Michael Gratton. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1868207 Title: Fractional scaling window sizes incorrect after resume from suspend To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1868207/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1868207] Re: Fractional scaling window sizes incorrect after resume from suspend
Also Michael logged this bug from a Wayland session. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1868207 Title: Fractional scaling window sizes incorrect after resume from suspend To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1868207/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1902652] Re: [arm64] [Libre Computer Board AML-S805X-AC] 3D rendering is very slow
Please run these commands: ls -l /dev/dri/* > dri.txt glxinfo > glx.txt and attach the resulting text files here. ** Changed in: mesa (Ubuntu) Status: New => Incomplete ** Changed in: xf86-video-armsoc (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/1902652 Title: [arm64] [Libre Computer Board AML-S805X-AC] 3D rendering is very slow To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1902652/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1902652] Re: [arm64] [Libre Computer Board AML-S805X-AC] 3D rendering is very slow
I think this should work in theory, but yeah it's not specific to a machine type: http://cdimage.ubuntu.com/releases/20.04.1/release/ubuntu-20.04.1-live- server-arm64.iso -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1902652 Title: [arm64] [Libre Computer Board AML-S805X-AC] 3D rendering is very slow To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1902652/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1878293] Re: xterm resize is wonky
** Also affects: xterm (Ubuntu Hirsute) Importance: Low Status: Invalid ** Also affects: mutter (Ubuntu Hirsute) Importance: Undecided Status: 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/1878293 Title: xterm resize is wonky To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1878293/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1870736] Re: [nvidia] Screen scaling 125% gives 200%
I have to rectify a little bit my affirmation above, everything I said about the video issues is right, but the problem with the video lagging and blinking and re-scalling specially when you move the cursor while watching in full screen mode look like a GNOME problem, not a NVIDIA proprietary driver problem, because after setting up the Nouveau open source driver again, the same problem happens when watching video in full screen, so better to setup the Nvidia driver with the workaround than use the open source drive that does not enable all the acceleration features your video hardware has. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1870736 Title: [nvidia] Screen scaling 125% gives 200% To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1870736/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1895157] Re: Boinc cannot enable RPC access to start client or manager
Tried the suggestion in comment #9 and that produced the error message "Invalid client RPC password. Try reinstalling BOINC." I already did a reinstall using aptitude. I also found a version of the file at a higher level, but messing with that one didn't help, either. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1895157 Title: Boinc cannot enable RPC access to start client or manager To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/boinc/+bug/1895157/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1902694] Re: Ubuntu 20.10- Undetected Data corruption in MPI workloads that use VSX for reductions on POWER9 DD2.1 systems
** Tags removed: severity-medium ** Tags added: severity-high -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1902694 Title: Ubuntu 20.10- Undetected Data corruption in MPI workloads that use VSX for reductions on POWER9 DD2.1 systems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1902694/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1885424] Re: Create package for Thor 1.0.1
** Also affects: ruby-bundler (Ubuntu) Importance: Undecided Status: New ** No longer affects: ruby-bundler (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1885424 Title: Create package for Thor 1.0.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ruby-thor/+bug/1885424/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1901355] Re: Groovy: libsmbclient users FTBFS against Samba 4.12.5
Patch fixes issue with libsmbclient users FTBFS against Samba 4.12.5 in Groovy. ** Patch added: "add-missing-time-h-include.patch" https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1901355/+attachment/5430848/+files/add-missing-time-h-include.patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1901355 Title: Groovy: libsmbclient users FTBFS against Samba 4.12.5 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1901355/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1899745] Re: [SRU] alsa-utils: let alsactl support _boot section defined in ucm
This bug was fixed in the package alsa-utils - 1.2.2-1ubuntu2 --- alsa-utils (1.2.2-1ubuntu2) focal; urgency=medium * d/p/0001-alsactl-init-iterate-through-all-cards-for-the-initi.patch * d/p/0002-alsactl-add-initial-support-for-UCM-init.patch * d/p/0003-alsactl-redirect-alsa-lib-errors.patch * d/p/0004-alsactl-add-D-argument-to-execute-also-the-UCM-defau.patch * d/p/0005-alsactl-use-the-right-priority-for-syslog-messages.patch * d/p/0006-alsactl-allow-to-compile-alsactl-without-UCM-support.patch * d/p/0007-alsactl-ucm-rename-_once-command-to-_boot-command.patch * d/p/0008-alsaucm-remove-custom-rules-alsactl-is-UCM-aware-now.patch Make alsactl support _boot section defined in the ucm, then the mixer values defined in the _boot section for Dell soundwire audio machines could be executed at the first booting. (LP: #1899745) -- Hui Wang Fri, 16 Oct 2020 17:50:30 +0200 ** Changed in: alsa-utils (Ubuntu Focal) Status: Fix Committed => 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/1899745 Title: [SRU] alsa-utils: let alsactl support _boot section defined in ucm To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1899745/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1899745] Update Released
The verification of the Stable Release Update for alsa-utils has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1899745 Title: [SRU] alsa-utils: let alsactl support _boot section defined in ucm To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1899745/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1900170] Re: apport hook looks for snap profile folder in the wrong place
This bug was fixed in the package chromium-browser - 1:85.0.4183.83-0ubuntu0.20.04.2 --- chromium-browser (1:85.0.4183.83-0ubuntu0.20.04.2) focal; urgency=medium [ Sébastien Bacher ] * debian/apport/chromium-browser.py: - the profile is now installed in the common directory (LP: #1900170) -- Olivier Tilloy Thu, 22 Oct 2020 18:07:20 +0200 ** Changed in: chromium-browser (Ubuntu Focal) Status: Fix Committed => 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/1900170 Title: apport hook looks for snap profile folder in the wrong place To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1900170/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1901355] Re: Groovy: libsmbclient users FTBFS against Samba 4.12.5
The new ceph 15.2.5-0ubuntu1.1 package (https://launchpad.net/~ubuntu- security/+archive/ubuntu/ppa/+build/20200352) fixes the issue, published a few days after I submitted the above bug report. Renaming bug report to "Groovy: libsmbclient users FTBFS against Samba 4.12.5" due that bug still being in the Groovy Samba package. See last paragraph and then link in above report. Software including FFmpeg 4.3.1 (if smbclient support is enabled) FTBFS against Samba 4.12.5 due the missing time.h header issue. ** Summary changed: - Groovy: Samba 4.12.5 FTBFS against Ceph 15.2.5 + Groovy: libsmbclient users FTBFS against Samba 4.12.5 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1901355 Title: Groovy: libsmbclient users FTBFS against Samba 4.12.5 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1901355/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1902808] [NEW] Upgrade sssd in 20.04 to the version in 20.10 as the 20.04 version crashes
Public bug reported: The sssd daemon is crashing when under heavy load on ubuntu 20.04. I have created a python script that will log into an Ubuntu 20.04 ever second to test logging in via sssd. In my configuration, sssd is configured to authenticate LDAP requests. When I run this script against 20.04, it will randomly fail to log in and my script will exit. This can happen anywhere from the first login attempt to the 100th login attempt. When I run this same script again Ubuntu 18.04 and 20.10, it runs without any issues. I took my server running 20.04 and did a release upgrade to 20.10 and the script runs without issues. Because of this, I believe the version of sssd included with 20.04 at the time of this bug: sssd/focal,now 2.2.3-3 amd64 [installed] is unstable and will crash causing some logins to fail. When I upgraded to 20.10 and the version became: sssd/groovy,now 2.3.1-3 amd64 [installed] I no longer see any issues. Due to policies at my company, I am only able to run LTS version of Ubuntu, so I am requesting that the newer version of sssd in 20.10 be ported to 20.04. Thanks ** Affects: sssd (Ubuntu) Importance: Undecided Status: New ** Tags: upgrade-software-version -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1902808 Title: Upgrade sssd in 20.04 to the version in 20.10 as the 20.04 version crashes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sssd/+bug/1902808/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1900170] Update Released
The verification of the Stable Release Update for chromium-browser has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1900170 Title: apport hook looks for snap profile folder in the wrong place To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1900170/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1898997] Re: MAAS cannot deploy/boot if OVS bridge is configured on a single PXE NIC
This bug was fixed in the package netplan.io - 0.100-0ubuntu4~20.04.3 --- netplan.io (0.100-0ubuntu4~20.04.3) focal; urgency=medium * debian/control:netplan.io: Suggest openvswitch-switch runtime dependency - Do not suggest on riscv64, where OVS isn't available in Focal * Add d/p/0003-tests-tunnels-improve-WG-handshake-regex.patch and d/p/0004-tests-ovs-fix-OVS-timeouts.patch - Improve stability of autopkgtests * Add d/p/0005-Fix-MAAS-OVS-first-boot-for-single-NIC-PXE-systems-1.patch - Setup OVS early in network-pre.target to avoid delays (LP: #1898997) -- Lukas Märdian Mon, 19 Oct 2020 14:49:52 +0200 ** Changed in: netplan.io (Ubuntu Focal) Status: Fix Committed => 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/1898997 Title: MAAS cannot deploy/boot if OVS bridge is configured on a single PXE NIC To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1898997/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1897934] Re: [SRU][Intel HDA] The initial sound level is set to zero (muted)
This bug was fixed in the package alsa-lib - 1.2.2-2.1ubuntu2.1 --- alsa-lib (1.2.2-2.1ubuntu2.1) focal; urgency=medium * d/p/0001-ucm-add-a-check-for-the-empty-configuration.patch - Fix the failure on init the HDA-Intel sound card, because there is no init mixer values in the ucm, the alsa-lib should return error and then let alsautils init this sound card in the legacy HDA way. (LP: #1897934) -- Hui Wang Thu, 22 Oct 2020 11:50:50 +0100 ** Changed in: alsa-lib (Ubuntu Focal) Status: Fix Committed => 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/1897934 Title: [SRU][Intel HDA] The initial sound level is set to zero (muted) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-notes/+bug/1897934/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1902795] Re: PCI graphics broken on AMD K8/K10 platform (while it works on Intel) verified from Linux 4.4 to 5.10-rc1
** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1902795 Title: PCI graphics broken on AMD K8/K10 platform (while it works on Intel) verified from Linux 4.4 to 5.10-rc1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1902795/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1897934] Update Released
The verification of the Stable Release Update for alsa-lib has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1897934 Title: [SRU][Intel HDA] The initial sound level is set to zero (muted) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-notes/+bug/1897934/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1899304] Re: Linux 5.4.0-48 (and later) causes GPU lockup, huge performance drop, makes GNOME desktop fail to start and games going from 70fps to 7fps, slow file loading, audio issues
** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1899304 Title: Linux 5.4.0-48 (and later) causes GPU lockup, huge performance drop, makes GNOME desktop fail to start and games going from 70fps to 7fps, slow file loading, audio issues To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1899304/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1898997] Update Released
The verification of the Stable Release Update for netplan.io has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1898997 Title: MAAS cannot deploy/boot if OVS bridge is configured on a single PXE NIC To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1898997/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1902760] Re: Please merge linker bugfix into Ubuntu 20.04 LTS
Launchpad has imported 11 comments from the remote bug at
https://sourceware.org/bugzilla/show_bug.cgi?id=26262.
If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.
On 2020-07-18T23:56:26+00:00 D-i-j wrote:
This can be reproduced with clang 10 (likely also 9; and all master
commits before https://reviews.llvm.org/D83967 ). LLVMgold.so is needed.
% cat a.c
int main() {}
% /tmp/Debug/bin/clang -fuse-ld=bfd -fprofile-generate -flto a.c
-Wl,-plugin-opt=save-temps -Wl,-y,__llvm_profile_raw_version
-Wl,-plugin-opt=save-temps
/usr/bin/ld.bfd: /tmp/a-e575a9.o (symbol from plugin): definition of
__llvm_profile_raw_version
/usr/bin/ld.bfd:
/tmp/Debug/lib/clang/12.0.0/lib/linux/libclang_rt.profile-x86_64.a(InstrProfiling.c.o):
definition of __llvm_profile_raw_version
/tmp/a-e575a9.o (symbol from plugin) provides a definition in a prevailing
comdat group.
libclang_rt.profile-x86_64.a(InstrProfiling.c.o) is an weak definition which
should not override the IR definition.
% cat a.out.resolution.txt
/tmp/a-e575a9.o
-r=/tmp/a-e575a9.o,main,plx
-r=/tmp/a-e575a9.o,__llvm_profile_raw_version,l # should be 'plx' instead of
'l'
-r=/tmp/a-e575a9.o,__llvm_profile_filename,plx
Gold and LLD are correct.
% /tmp/Debug/bin/clang -fuse-ld=gold -fprofile-generate -flto a.c
-Wl,-plugin-opt=save-temps -Wl,-y,__llvm_profile_raw_version
/tmp/a-668c9c.o: definition of __llvm_profile_raw_version
/tmp/Debug/lib/clang/12.0.0/lib/linux/libclang_rt.profile-x86_64.a(InstrProfiling.c.o):
definition of __llvm_profile_raw_version
a.out.o: definition of __llvm_profile_raw_version
% cat a.out.resolution.txt
/tmp/a-668c9c.o
-r=/tmp/a-668c9c.o,main,plx
-r=/tmp/a-668c9c.o,__llvm_profile_raw_version,plx
-r=/tmp/a-668c9c.o,__llvm_profile_filename,plx
% /tmp/Debug/bin/clang -fuse-ld=lld -fprofile-generate -flto a.c
-Wl,-plugin-opt=save-temps -Wl,-y,__llvm_profile_raw_version
/tmp/a-afb841.o: definition of __llvm_profile_raw_version
: reference to __llvm_profile_raw_version
lto.tmp: definition of __llvm_profile_raw_version
% cat a.out.resolution.txt
/tmp/a-afb841.o
-r=/tmp/a-afb841.o,main,plx
-r=/tmp/a-afb841.o,__llvm_profile_raw_version,plx
-r=/tmp/a-afb841.o,__llvm_profile_filename,plx
The ld bug is in ld/plugin.c:plugin_notice . ld somehow drops
bfd_link_hash_defined (provided by "/tmp/a-e575a9.o (symbol from plugin)") in
favor of bfd_link_hash_undefweak. Then bfd_link_hash_undefweak is overridden by
the weak definition in libclang_rt.profile-x86_64.a(InstrProfiling.c.o)
/* Otherwise, it must be a new def.
Ensure any symbol defined in an IR dummy BFD takes on a
new value from a real BFD. Weak symbols are not normally
overridden by a new weak definition, and strong symbols
will normally cause multiple definition errors. Avoid
this by making the symbol appear to be undefined. */
else if (((h->type == bfd_link_hash_defweak
|| h->type == bfd_link_hash_defined)
&& is_ir_dummy_bfd (sym_bfd = h->u.def.section->owner))
|| (h->type == bfd_link_hash_common
&& is_ir_dummy_bfd (sym_bfd = h->u.c.p->section->owner)))
{
h->type = bfd_link_hash_undefweak;
h->u.undef.abfd = sym_bfd;
}
The intended behavior is to let "/tmp/a-e575a9.o (symbol from plugin)"
provide the definition.
Reply at:
https://bugs.launchpad.net/ubuntu/+source/binutils/+bug/1902760/comments/0
On 2020-07-19T12:25:08+00:00 Hjl-tools wrote:
clang has different behavior depending on -fuse-ld=XXX:
[hjl@gnu-cfl-2 pr26262]$ clang -fuse-ld=gold -Wl,-y,__llvm_profile_raw_version
-Wl,-plugin-opt=save-temps -fprofile-generate -flto -o a a.c -save-temps
a.o: definition of __llvm_profile_raw_version
/usr/lib64/clang/10.0.0/lib/linux/libclang_rt.profile-x86_64.a(InstrProfiling.c.o):
definition of __llvm_profile_raw_version
a.o: definition of __llvm_profile_raw_version
[hjl@gnu-cfl-2 pr26262]$ clang -fuse-ld=bfd -Wl,-y,__llvm_profile_raw_version
-Wl,-plugin-opt=save-temps -fprofile-generate -flto -o a a.o
/usr/bin/ld.bfd: a.o: definition of __llvm_profile_raw_version
[hjl@gnu-cfl-2 pr26262]$ clang -fuse-ld=bfd -Wl,-y,__llvm_profile_raw_version
-Wl,-plugin-opt=save-temps -fprofile-generate -flto -o a a.c -save-temps
/usr/bin/ld.bfd: a.o (symbol from plugin): definition of
__llvm_profile_raw_version
/usr/bin/ld.bfd:
/usr/lib64/clang/10.0.0/lib/linux/libclang_rt.profile-x86_64.a(InstrProfiling.c.o):
definition of __llvm_profile_raw_version
[hjl@gnu-cfl-2 pr26262]$ clang -fuse-ld=gold -Wl,-y,__llvm_profile_raw_version
-Wl,-plugin-opt=save-temps -fprofile-generate -flto -o a a.o
Re: [Bug 1890365] Re: [snap] Web Serial fails to access local device
Made no difference. Tried before or after launching the browser. By the way, this bug is not there in edge. Only Chromium. On 10/30/20 12:27 PM, Olivier Tilloy wrote: > Does the following help? > > sudo snap connect chromium:raw-usb > > ** Changed in: chromium-browser (Ubuntu) > Status: Expired => New > -- - Edward Sternin, Physics Department, Brock U, St.Catharines, Ontario, L2S 3A1 http://www.physics.brocku.ca/People/Faculty/Sternin/ voice: (905)688-5550x3414 FAX:(905)984-4857 email: edward.ster...@brocku.ca -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1890365 Title: [snap] Web Serial fails to access local device To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1890365/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1894942] Re: [UBUNTU 20.04] Lost virtio host --> guest notifications cause devices to cease normal operation
This bug was fixed in the package qemu - 1:4.2-3ubuntu6.8 --- qemu (1:4.2-3ubuntu6.8) focal; urgency=medium * d/p/u/lp-1894942-*: fix virtio-ccw host/guest notification (LP: #1894942) -- Christian Ehrhardt Mon, 21 Sep 2020 15:35:30 +0200 ** Changed in: qemu (Ubuntu Focal) Status: Fix Committed => 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/1894942 Title: [UBUNTU 20.04] Lost virtio host --> guest notifications cause devices to cease normal operation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1894942/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1901286] Re: gnome-disk-image-mounter fails after upgrade to 20.10
Mapped file virtio-win-0.1.185.iso as /dev/loop0. and then the ISO shows as mounted in nautilus. so I guess it's not a problem with the ISO itself, but with whatever nautilus+gnome is doing to try and mount it. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1901286 Title: gnome-disk-image-mounter fails after upgrade to 20.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-disk-utility/+bug/1901286/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1894942] Update Released
The verification of the Stable Release Update for qemu has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1894942 Title: [UBUNTU 20.04] Lost virtio host --> guest notifications cause devices to cease normal operation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1894942/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1902148] Re: [snap] launchers in app's dock menu do launch general LO
Yeah.. I was sure this would work because i tested my addition locally in a little quick script. I reran the lp build and it failed in the same way (good to know it's consistent). I did a local build last night and ran out of memory becuase libreoffice is a beast so I'll try again on an unused system to try and debug why it's failing.. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1902148 Title: [snap] launchers in app's dock menu do launch general LO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1902148/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1870736] Re: [nvidia] Screen scaling 125% gives 200%
As @vsulimov mention, the solution from @nightwing666 works, in my case in a ThinkPad X1 Gen 2, but the video scaling in full screen doesn't, it makes any video you try to reproduce in full screen to blink, and if you set the video again in not fullscreen mode the video is scaled x2, or it makes the video player to crash. I tried with the default video player from Ubuntu, with VLC Player and even with Firefox reproducing a video from Youtube, in all the cases the result is the same: the video is reproduced well as long you don't enable full screen video reproduction. I tried with scalling at 125% and 150% and it failed in both cases. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1870736 Title: [nvidia] Screen scaling 125% gives 200% To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1870736/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1830746] Re: memlock setting in systemd (pid 1) too low for containers (bionic)
This bug was fixed in the package systemd - 237-3ubuntu10.43 --- systemd (237-3ubuntu10.43) bionic; urgency=medium [ Guilherme G. Piccoli ] * d/p/lp1830746-bump-mlock-ulimit-to-64Mb.patch: - Bump the memlock limit to match Focal and newer releases (LP: #1830746) https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=61adb797642f3dd2e5c14f7914c2949c665cefe8 [ Victor Manuel Tapia King ] * d/p/lp1896614-core-Avoid-race-when-starting-dbus-services.patch: - Fix race when starting dbus services (LP: #1896614) https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=373cb6ccd6978a7112bbfd7e5cf4f703a9f8448e [ Dan Streetman ] * d/t/*, d/p/lp1892358/0001-test-increase-qemu-timeout-for-TEST-08-and-TEST-09.patch, d/p/lp1892358/0002-test-increase-timeout-for-TEST-17-UDEV-WANTS.patch, d/p/lp1892358/0003-test-increase-qemu-timeout-for-TEST-18-and-TEST-19.patch: - Increase QEMU_TIMEOUT on 'upstream' autopkgtest tests - Pull latest tests from newer releases to fix false negatives - Blacklist flaky 'upstream' TEST-03 (LP: #1892358) https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=9fd8391c2499e163515b629a8ca5790898fc599d https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=d1756b3e1c3e625ed7162cff4909e7a29c315051 https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=37f8d73516a84e85e4057d6a92204b4a174af718 https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=229ed2076eb773efc548035262b8b8009bf89207 https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=f2d7b1f952667316cc07a4b3c5010e66ace07a90 https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=659befe61bbfeb7afc9efa24458c9745412d7c6d -- Victor Manuel Tapia King Wed, 07 Oct 2020 16:30:03 -0400 ** Changed in: systemd (Ubuntu Bionic) Status: Fix Committed => 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/1830746 Title: memlock setting in systemd (pid 1) too low for containers (bionic) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1830746/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1891718] Re: [Regression] breaks GRUB install on an nvme device
And regression tested on an NVMe (but non-nvme-subsys) device on an ARM server: ubuntu@d05-4:~$ mount | grep /boot/efi /dev/nvme0n1p1 on /boot/efi type vfat (rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro) ubuntu@d05-4:~$ ls -l /dev/nvme0n1p1 brw-rw 1 root disk 259, 1 Nov 3 23:40 /dev/nvme0n1p1 ubuntu@d05-4:~$ readlink /sys/dev/block/259\:1 ../../devices/pci000d:30/000d:30:00.0/000d:31:00.0/nvme/nvme0/nvme0n1/nvme0n1p1 ubuntu@d05-4:~$ sudo grub-install Installing for arm64-efi platform. Installation finished. No error reported. ubuntu@d05-4:~$ sudo apt install libefivar1 libefiboot1 Reading package lists... Done Building dependency tree Reading state information... Done The following packages will be upgraded: libefiboot1 libefivar1 2 upgraded, 0 newly installed, 0 to remove and 60 not upgraded. Need to get 78.2 kB of archives. After this operation, 8192 B of additional disk space will be used. Get:1 http://ports.ubuntu.com/ubuntu-ports focal-proposed/main arm64 libefivar1 arm64 37-2ubuntu2.1 [42.5 kB] Get:2 http://ports.ubuntu.com/ubuntu-ports focal-proposed/main arm64 libefiboot1 arm64 37-2ubuntu2.1 [35.7 kB] Fetched 78.2 kB in 0s (233 kB/s) (Reading database ... 77021 files and directories currently installed.) Preparing to unpack .../libefivar1_37-2ubuntu2.1_arm64.deb ... Unpacking libefivar1:arm64 (37-2ubuntu2.1) over (37-2ubuntu2) ... Preparing to unpack .../libefiboot1_37-2ubuntu2.1_arm64.deb ... Unpacking libefiboot1:arm64 (37-2ubuntu2.1) over (37-2ubuntu2) ... Setting up libefivar1:arm64 (37-2ubuntu2.1) ... Setting up libefiboot1:arm64 (37-2ubuntu2.1) ... Processing triggers for libc-bin (2.31-0ubuntu9.1) ... ubuntu@d05-4:~$ sudo grub-install Installing for arm64-efi platform. Installation finished. No error reported. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1891718 Title: [Regression] breaks GRUB install on an nvme device To manage notifications about this bug go to: https://bugs.launchpad.net/efivar/+bug/1891718/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
