[Bug 2062951] Re: Random flickering with i915 on Linux 6.8
@Davron - downgrading the kernel to 6.7 should work for now, but I just went back to 22.04 as I also had issues with laptop shutdown state etc Also worth clicking the "this bug affects me" thing at the top as I don't think devs will bother unless the issue gets some visibility. Seen quite a few others on Reddit with same or similar issues so it definitely affects more than is showing here. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2062951 Title: Random flickering with i915 on Linux 6.8 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2062951/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2063228] Re: Screen sometimes blinking (since 6.7.7, but 6.7.6 works)
I would suggest that this is related to https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2062951 It's happening on very similar hardware, with these more recent kernel versions. Back on kernel 6.5.0-35 on the old LTS with no issues. I was running 23.10 until the 24.04 release with no issues too. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2063228 Title: Screen sometimes blinking (since 6.7.7, but 6.7.6 works) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2063228/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2062951] Re: Random flickering with i915 on Linux 6.8
This seems to be related to the newer Intel Xe driver included with kernel 6.8.x as it only occurs when the driver is enabled. When using nomodeset in grub, there are no issues (besides losing brightness controls etc from no driver being loaded). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2062951 Title: Random flickering with i915 on Linux 6.8 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2062951/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2065139] [NEW] nvidia-dkms-545 545.29.06-0ubuntu0.22.04.2: nvidia kernel module failed to build
Public bug reported: An update failed with the following error: ERROR: modpost: GPL-incompatible module nvidia.ko uses GPL-only symbol 'rcu_read_unlock_strict' The tail of the crash report follows: sh ./scripts/modules-check.sh /var/lib/dkms/nvidia/545.29.06/build/modules.order make -f ./scripts/Makefile.modpost sed 's/\.ko$/\.o/' /var/lib/dkms/nvidia/545.29.06/build/modules.order | scripts/mod/modpost -m -a -o /var/lib/dkms/nvidia/545.29.06/build/Module.symvers -e -i Module.symvers -T - ERROR: modpost: GPL-incompatible module nvidia.ko uses GPL-only symbol 'rcu_read_unlock_strict' make[2]: *** [scripts/Makefile.modpost:133: /var/lib/dkms/nvidia/545.29.06/build/Module.symvers] Error 1 make[2]: *** Deleting file '/var/lib/dkms/nvidia/545.29.06/build/Module.symvers' make[1]: *** [Makefile:1830: modules] Error 2 make[1]: Leaving directory '/usr/src/linux-headers-5.15.0-106-generic' make: *** [Makefile:82: modules] Error 2 DKMSKernelVersion: 5.15.0-106-generic Date: Wed May 8 09:58:50 2024 Package: nvidia-dkms-545 545.29.06-0ubuntu0.22.04.2 PackageVersion: 545.29.06-0ubuntu0.22.04.2 SourcePackage: nvidia-graphics-drivers-545 Title: nvidia-dkms-545 545.29.06-0ubuntu0.22.04.2: nvidia kernel module failed to build ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown Dependencies: adduser 3.118ubuntu5 apt 2.4.12 apt-utils 2.4.12 binutils 2.38-4ubuntu2.6 binutils-common 2.38-4ubuntu2.6 binutils-x86-64-linux-gnu 2.38-4ubuntu2.6 build-essential 12.9ubuntu3 bzip2 1.0.8-5build1 ca-certificates 20230311ubuntu0.22.04.1 coreutils 8.32-4.1ubuntu1.2 cpp 4:11.2.0-1ubuntu1 cpp-11 11.4.0-1ubuntu1~22.04 cpp-12 12.3.0-1ubuntu1~22.04 dctrl-tools 2.24-3build2 debconf 1.5.79ubuntu1 debconf-i18n 1.5.79ubuntu1 dirmngr 2.2.27-3ubuntu2.1 distro-info-data 0.52ubuntu0.7 dkms 2.8.7-2ubuntu2.2 dpkg 1.21.1ubuntu2.3 dpkg-dev 1.21.1ubuntu2.3 fakeroot 1.28-1ubuntu1 g++ 4:11.2.0-1ubuntu1 g++-11 11.4.0-1ubuntu1~22.04 gcc 4:11.2.0-1ubuntu1 gcc-11 11.4.0-1ubuntu1~22.04 gcc-11-base 11.4.0-1ubuntu1~22.04 gcc-12 12.3.0-1ubuntu1~22.04 gcc-12-base 12.3.0-1ubuntu1~22.04 gnupg 2.2.27-3ubuntu2.1 gnupg-l10n 2.2.27-3ubuntu2.1 gnupg-utils 2.2.27-3ubuntu2.1 gpg 2.2.27-3ubuntu2.1 gpg-agent 2.2.27-3ubuntu2.1 gpg-wks-client 2.2.27-3ubuntu2.1 gpg-wks-server 2.2.27-3ubuntu2.1 gpgconf 2.2.27-3ubuntu2.1 gpgsm 2.2.27-3ubuntu2.1 gpgv 2.2.27-3ubuntu2.1 init-system-helpers 1.62 kmod 29-1ubuntu1 krb5-locales 1.19.2-2ubuntu0.3 libacl1 2.3.1-1 libalgorithm-diff-perl 1.201-1 libalgorithm-diff-xs-perl 0.04-6build3 libalgorithm-merge-perl 0.08-3 libapt-pkg6.0 2.4.12 libasan6 11.4.0-1ubuntu1~22.04 libasan8 12.3.0-1ubuntu1~22.04 libassuan0 2.5.5-1build1 libatomic1 12.3.0-1ubuntu1~22.04 libattr1 1:2.5.1-1build1 libaudit-common 1:3.0.7-1build1 libaudit1 1:3.0.7-1build1 libbinutils 2.38-4ubuntu2.6 libbz2-1.0 1.0.8-5build1 libc-dev-bin 2.35-0ubuntu3.7 libc6 2.35-0ubuntu3.7 libc6-dev 2.35-0ubuntu3.7 libcap-ng0 0.7.9-2.2build3 libcap2 1:2.44-1ubuntu0.22.04.1 libcc1-0 12.3.0-1ubuntu1~22.04 libcom-err2 1.46.5-2ubuntu1.1 libcrypt-dev 1:4.4.27-1 libcrypt1 1:4.4.27-1 libctf-nobfd0 2.38-4ubuntu2.6 libctf0 2.38-4ubuntu2.6 libdb5.3 5.3.28+dfsg1-0.8ubuntu3 libdpkg-perl 1.21.1ubuntu2.3 libfakeroot 1.28-1ubuntu1 libffi8 3.4.2-4 libfile-fcntllock-perl 0.22-3build7 libgcc-11-dev 11.4.0-1ubuntu1~22.04 libgcc-12-dev 12.3.0-1ubuntu1~22.04 libgcc-s1 12.3.0-1ubuntu1~22.04 libgcrypt20 1.9.4-3ubuntu3 libgdbm-compat4 1.23-1 libgdbm6 1.23-1 libgmp10 2:6.2.1+dfsg-3ubuntu1 libgnutls30 3.7.3-4ubuntu1.5 libgomp1 12.3.0-1ubuntu1~22.04 libgpg-error-l10n 1.43-3 libgpg-error0 1.43-3 libgpm2 1.20.7-10build1 libgssapi-krb5-2 1.19.2-2ubuntu0.3 libhogweed6 3.7.3-1build2 libidn2-0 2.3.2-2build1 libisl23 0.24-2build1 libitm1 12.3.0-1ubuntu1~22.04 libk5crypto3 1.19.2-2ubuntu0.3 libkeyutils1 1.6.1-2ubuntu3 libkmod2 29-1ubuntu1 libkrb5-3 1.19.2-2ubuntu0.3 libkrb5support0 1.19.2-2ubuntu0.3 libksba8 1.6.0-2ubuntu0.2 libldap-2.5-0 2.5.17+dfsg-0ubuntu0.22.04.1 libldap-common 2.5.17+dfsg-0ubuntu0.22.04.1 liblocale-gettext-perl 1.07-4build3 liblsan0 12.3.0-1ubuntu1~22.04 liblz4-1 1.9.3-2build2 liblzma5 5.2.5-2ubuntu1 libmpc3 1.2.1-2build1 libmpfr6 4.1.0-3build3 libncursesw6 6.3-2ubuntu0.1 libnettle8 3.7.3-1build2 libnpth0 1.6-3build2 libnsl-dev 1.3.0-2build2 libnsl2 1.3.0-2build2 libnss-nis 3.1-0ubuntu6 libnss-nisplus 1.3-0ubuntu6 libp11-kit0 0.24.0-6build1 libpam-modules 1.4.0-11ubuntu2.4 libpam-modules-bin 1.4.0-11ubuntu2.4 libpam0g 1.4.0-11ubuntu2.4 libpciaccess0 0.16-3 libpcre2-8-0 10.39-3ubuntu0.1 libperl5.34 5.34.0-3ubuntu1.3 libquadmath0 12.3.0-1ubuntu1~22.04 libreadline8 8.1.2-1 libsasl2-2 2.1.27+dfsg2-3ubuntu1.2 libsasl2-modules 2.1.27+dfsg2-3ubuntu1.2 libsasl2-modules-db 2.1.27+dfsg2-3ubuntu1.2 libseccomp2 2.5.3-2ubuntu2 libselinux1 3.3-1build2 libsemanage-common 3.3-1build2 libsemanage2 3.3-1build2 libsepol2 3.3-1build1
[Bug 2062951] Re: Random flickering with i915 on Linux 6.8
I've tried adding "intel_idle.max_cstate=4" too but it didn't fix anything for me. Both KDE Plasma and Xfce have the same behavior. I'm also on a Skylake GT2 [HD Graphics 520] - no issues on 23.10 as I didn't change kernel, but 24.04 with kernel 6.8 is where I'm experiencing this. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2062951 Title: Random flickering with i915 on Linux 6.8 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2062951/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1972762] Re: Firefox and Chromium snaps preventing apps and devices from working correctly.
also affects me -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1972762 Title: Firefox and Chromium snaps preventing apps and devices from working correctly. To manage notifications about this bug go to: https://bugs.launchpad.net/chromium-browser/+bug/1972762/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1958021] [NEW] Ubuntu Software Center doesn't work with local/mirrored repositories
Public bug reported: Ubuntu Software Center doesn't work with local/mirrored repositories. I mirror the entire Ubuntu repositories to a hard drive every month to use it with a local HTTP server to serve some Ubuntu PCs that have no access to the Internet at all, just to an air-gapped local network. When using the command line via "apt update" and "apt upgrade", everything works perfectly fine, I'm able to update, upgrade, install and remove packages like if I were connected directly to Canonical servers. The problem is that the Ubuntu Software Center doesn't work in this setting. It only says that I'm disconnected from the Internet and it doesn't recognize the local HTTP repository that's configured and the rest of the system uses just fine. Users complain because they prefer to use the more intuitive GUI and that's understandable, but I don't know what else to do so I think this is a bug and no Google result seems to know how to fix this. OS: Ubuntu 20.04.3 LTS right now, but the problem was present in past versions also. What I expect to happen: the Ubuntu Software Center recognizes the local HTTP repositories and works. What instead happens: the Ubuntu Software Center doesn't work because it says I'm disconnected from the Internet. ** Affects: ubuntu Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1958021 Title: Ubuntu Software Center doesn't work with local/mirrored repositories To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1958021/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1926678] Re: Selecting text within Geany then middle clicking into another application (or vice-versa) has stopped working.
Bug not present in Ubunutu 21.10, so I've changed status to 'Fix Released'. ** Changed in: geany (Ubuntu) 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/1926678 Title: Selecting text within Geany then middle clicking into another application (or vice-versa) has stopped working. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/geany/+bug/1926678/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1882291] Re: Gnome Shell clock is truncated/corrupt on the right side
Just posting to update that this still occurs for me in Ubuntu Impish 21.10 (which ships with Mutter 40.5), looks like the fix will arrive in the next major version of Mutter? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1882291 Title: Gnome Shell clock is truncated/corrupt on the right side To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1882291/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1946257] [NEW] package nvidia-340 340.108-0ubuntu5.20.04.2 failed to install/upgrade: trying to overwrite '/usr/bin/nvidia-bug-report.sh', which is also in package nvidia-utils-460 460.91.03-0ubu
Public bug reported: system is running screen resolution is fine using nvidia driver 340. Just error report ProblemType: Package DistroRelease: Ubuntu 20.04 Package: nvidia-340 340.108-0ubuntu5.20.04.2 ProcVersionSignature: Ubuntu 5.8.0-63.71~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-63-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 CasperMD5CheckResult: skip Date: Wed Oct 6 21:10:32 2021 DuplicateSignature: package:nvidia-340:340.108-0ubuntu5.20.04.2 Unpacking nvidia-340 (340.108-0ubuntu5.20.04.2) ... dpkg: error processing archive /var/cache/apt/archives/nvidia-340_340.108-0ubuntu5.20.04.2_amd64.deb (--unpack): trying to overwrite '/usr/bin/nvidia-bug-report.sh', which is also in package nvidia-utils-460 460.91.03-0ubuntu0.20.04.1 ErrorMessage: trying to overwrite '/usr/bin/nvidia-bug-report.sh', which is also in package nvidia-utils-460 460.91.03-0ubuntu0.20.04.1 Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python3.8, Python 3.8.10, unpackaged RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.6 SourcePackage: nvidia-graphics-drivers-340 Title: package nvidia-340 340.108-0ubuntu5.20.04.2 failed to install/upgrade: trying to overwrite '/usr/bin/nvidia-bug-report.sh', which is also in package nvidia-utils-460 460.91.03-0ubuntu0.20.04.1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: nvidia-graphics-drivers-340 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal need-duplicate-check package-conflict -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1946257 Title: package nvidia-340 340.108-0ubuntu5.20.04.2 failed to install/upgrade: trying to overwrite '/usr/bin/nvidia-bug-report.sh', which is also in package nvidia-utils-460 460.91.03-0ubuntu0.20.04.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1946257/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1813441] Re: Can no longer drag and drop files between desktop and applications
Hi everyone, i worked for a while in an OSS called Spinnaker.io. I understand is annoying to deal with so many approaches and personalities. This message is just to say thank you for all the support to the ubuntu distro. I really like using ubuntu and yes there are changes and improvements but to me is a good challenge to learn something new and try something else. Kepp up the good work God bless -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1813441 Title: Can no longer drag and drop files between desktop and applications To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell-extension-desktop-icons/+bug/1813441/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1928744] Re: Disk IO very slow on kernel 4.15.0-142-generic
I have also been running 4.15.0-144-generic for three weeks so far without the issue occurring. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1928744 Title: Disk IO very slow on kernel 4.15.0-142-generic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1928744/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1928744] Re: Disk IO very slow on kernel 4.15.0-142-generic
Hi, We think we are affected by the same bug. We were on version 4.15.0-139 and upgraded to 144 before finding this post. Is there any confirmation that this issue also occurs in 4.15.0-144? I have have installed version 4.15.0-136 in the meantime to allow us to reboot and select that kernel, incase the issue is present. Hope to see a fix for this issue soon. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1928744 Title: Disk IO very slow on kernel 4.15.0-142-generic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1928744/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1926678] Re: Selecting text within Geany then middle clicking into another application (or vice-versa) has stopped working.
I forgot to add that everything works as expected under a Xorg session. ** Description changed: + Problem started after upgrade to Ubuntu 21.04 and only occurs when + running a Wayland session. + I use Geany all day, every day. It's a wonderfully light-weight editor with enough IDE functionality to keep me productive without getting in my way. I generally work with a Geany window on one side of my monitor, a Gnome Terminal window on the other. Something I do all the time is to select some text in Geany (a variable name, say) then middle click into the terminal. For example I might type 'grep' (or the superb 'ag') into the terminal, then middle-click to append the variable name to search for. Since upgrading to Ubuntu 21.04, this has stopped working [1]. Trying to copy in the opposite direction, from the terminal into Geany, has also stopped working [2]. Oddly, I still the expected behaviour as long as I stay *within* a Geany window: I can double-click on a word to select it, then middle-click to paste what was just selected. The normal ctrl+c, ctrl+v clipboard works just fine. [1] Something does get pasted, but not what I selected in Geany. Instead, it is whatever I last selected from within another application, eg. Firefox. [2] What does get pasted in this case is more complicated. If I haven't selected anything in a while I will actually get the expected behaviour: the terminal selection will pasted into Geany. Usually though, I'll just get whatever I last highlighted in the Geany window instead. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1926678 Title: Selecting text within Geany then middle clicking into another application (or vice-versa) has stopped working. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/geany/+bug/1926678/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1926678] [NEW] Selecting text within Geany then middle clicking into another application (or vice-versa) has stopped working.
Public bug reported: I use Geany all day, every day. It's a wonderfully light-weight editor with enough IDE functionality to keep me productive without getting in my way. I generally work with a Geany window on one side of my monitor, a Gnome Terminal window on the other. Something I do all the time is to select some text in Geany (a variable name, say) then middle click into the terminal. For example I might type 'grep' (or the superb 'ag') into the terminal, then middle-click to append the variable name to search for. Since upgrading to Ubuntu 21.04, this has stopped working [1]. Trying to copy in the opposite direction, from the terminal into Geany, has also stopped working [2]. Oddly, I still the expected behaviour as long as I stay *within* a Geany window: I can double-click on a word to select it, then middle-click to paste what was just selected. The normal ctrl+c, ctrl+v clipboard works just fine. [1] Something does get pasted, but not what I selected in Geany. Instead, it is whatever I last selected from within another application, eg. Firefox. [2] What does get pasted in this case is more complicated. If I haven't selected anything in a while I will actually get the expected behaviour: the terminal selection will pasted into Geany. Usually though, I'll just get whatever I last highlighted in the Geany window instead. ** Affects: geany (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1926678 Title: Selecting text within Geany then middle clicking into another application (or vice-versa) has stopped working. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/geany/+bug/1926678/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1882291] Re: Gnome Shell clock is truncated/corrupt on the right side
I'm experiencing this in Ubuntu Groovy 20.10 as well, but I generally only notice it in the gnome top panel. Moving the mouse over the clock or attempting to take a screenshot clears the display error. I've attached photos of my screen and submitted details from `apport- collect`, let me know if I can provide anything else. ** Attachment added: "combined.jpg" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1882291/+attachment/5493313/+files/combined.jpg -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1882291 Title: Gnome Shell clock is truncated/corrupt on the right side To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1882291/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1882291] monitors.xml.txt
apport information ** Attachment added: "monitors.xml.txt" https://bugs.launchpad.net/bugs/1882291/+attachment/5493312/+files/monitors.xml.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1882291 Title: Gnome Shell clock is truncated/corrupt on the right side To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1882291/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1882291] ShellJournal.txt
apport information ** Attachment added: "ShellJournal.txt" https://bugs.launchpad.net/bugs/1882291/+attachment/5493311/+files/ShellJournal.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1882291 Title: Gnome Shell clock is truncated/corrupt on the right side To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1882291/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1882291] GsettingsChanges.txt
apport information ** Attachment added: "GsettingsChanges.txt" https://bugs.launchpad.net/bugs/1882291/+attachment/5493309/+files/GsettingsChanges.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1882291 Title: Gnome Shell clock is truncated/corrupt on the right side To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1882291/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1882291] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1882291/+attachment/5493310/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1882291 Title: Gnome Shell clock is truncated/corrupt on the right side To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1882291/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1882291] Dependencies.txt
apport information ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1882291/+attachment/5493308/+files/Dependencies.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1882291 Title: Gnome Shell clock is truncated/corrupt on the right side To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1882291/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1882291] Re: Gnome Shell clock is truncated/corrupt on the right side
ProblemType: Bug ApportVersion: 2.20.11-0ubuntu50.5 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 20.10 InstallationDate: Installed on 2021-01-16 (102 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) NonfreeKernelModules: nvidia_modeset nvidia Package: gnome-shell 3.38.2-1ubuntu1~20.10.1 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.8.0-50.56-generic 5.8.18 RelatedPackageVersions: mutter-common 3.38.2-1ubuntu1~20.10.1 Tags: groovy Uname: Linux 5.8.0-50-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker lpadmin lxd nordvpn plugdev sambashare sudo _MarkForUpload: True ** Tags added: apport-collected groovy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1882291 Title: Gnome Shell clock is truncated/corrupt on the right side To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1882291/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1915762] [NEW] package linux-image-4.4.0-198-generic 4.4.0-198.230 failed to install/upgrade: run-parts: /etc/kernel/postrm.d/zz-update-grub exited with return code 1
Public bug reported: I am trying to install the aduini IDE and also some serial libraries for the communication between arduino and the system and in both occasions I get this error ProblemType: Package DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-198-generic 4.4.0-198.230 ProcVersionSignature: Ubuntu 4.4.0-201.233-generic 4.4.247 Uname: Linux 4.4.0-201-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.30 Architecture: amd64 Date: Thu Feb 11 13:49:25 2021 ErrorMessage: run-parts: /etc/kernel/postrm.d/zz-update-grub exited with return code 1 InstallationDate: Installed on 2021-01-06 (40 days ago) InstallationMedia: Ubuntu 14.04.6 LTS "Trusty Tahr" - Release amd64 (20190304.5) RelatedPackageVersions: dpkg 1.18.4ubuntu1.6 apt 1.2.32ubuntu0.2 SourcePackage: grub Title: package linux-image-4.4.0-198-generic 4.4.0-198.230 failed to install/upgrade: run-parts: /etc/kernel/postrm.d/zz-update-grub exited with return code 1 UpgradeStatus: Upgraded to xenial on 2021-01-06 (40 days ago) ** Affects: grub (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1915762 Title: package linux-image-4.4.0-198-generic 4.4.0-198.230 failed to install/upgrade: run-parts: /etc/kernel/postrm.d/zz-update-grub exited with return code 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub/+bug/1915762/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1871268] Re: Installation fails due to useless immediate configuration error when "Install Third-Party Drivers" is selected
I went along withe the whole mokutil route to get the NVidia drivers to work but that failed to rectify the problem. The GUI started having huge issues (Second monitor stopped working. GUI would freeze and need a reboot). Tried reverting back to Nouveau and in the process lost my server.. Gui stopped working completely. Luckily I could still access the drive contents. and installed on a new drive. Still not working 100% Second screen is detected but does not work. I get a black screen with a white mouse pointer. I can drag a window onto the monitor but if I release it it's gone. (I can't see where it is to drag it back) On 2021/02/04 20:37, Alf Haakon Lund wrote: > Even though the installer crashed, powering off the machine and > restarting sent me to a 'Perform MOK management' menu where I had to > input my chosen password from the relevant step in the installation > process. After that rebooting took me to the Grub menu and I could > successfully start Ubuntu Studio. > > After login there was a short flickering on the screen which I suspect > could be the NVIDIA driver failing and falling back to the intel HD > Graphics 530. > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1871268 Title: Installation fails due to useless immediate configuration error when "Install Third-Party Drivers" is selected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-cdimage/+bug/1871268/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1912993] [NEW] Error installing python-sklearn-doc
Public bug reported: # apt install python-sklearn-doc Reading package lists... Done Building dependency tree Reading state information... Done Suggested packages: python-sklearn The following NEW packages will be installed: python-sklearn-doc 0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded. Need to get 227 kB of archives. After this operation, 1,200 kB of additional disk space will be used. Get:1 http://ph.archive.ubuntu.com/ubuntu focal/universe amd64 python-sklearn-doc all 0.22.2.post1+dfsg-5 [227 kB] Fetched 227 kB in 0s (1,232 kB/s) Selecting previously unselected package python-sklearn-doc. (Reading database ... 672827 files and directories currently installed.) Preparing to unpack .../python-sklearn-doc_0.22.2.post1+dfsg-5_all.deb ... Unpacking python-sklearn-doc (0.22.2.post1+dfsg-5) ... Setting up python-sklearn-doc (0.22.2.post1+dfsg-5) ... Processing triggers for doc-base (0.10.9) ... Processing 1 added doc-base file... Error in `/usr/share/doc-base/scikit-learn', line 10: all `Format' sections are invalid. Note: `install-docs --verbose --check file_name' may give more details about the above error. Registering documents with dwww... `install-docs` check gives: # install-docs --verbose --check /usr/share/doc-base/scikit-learn Warning in `/usr/share/doc-base/scikit-learn', line 10: file `/usr/share/doc/python-sklearn-doc/stable/index.html' does not exist. Error in `/usr/share/doc-base/scikit-learn', line 10: all `Format' sections are invalid. /usr/share/doc-base/scikit-learn: Fatal error found, the file won't be registered. Thanks for any help you can extend in this regard! ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: python-sklearn-doc 0.22.2.post1+dfsg-5 ProcVersionSignature: Ubuntu 5.8.0-40.45~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: LXQt Date: Mon Jan 25 10:09:17 2021 Dependencies: fonts-glyphicons-halflings 1.009~3.4.1+dfsg-1 fonts-mathjax 2.7.4+dfsg-1 libjs-bootstrap 3.4.1+dfsg-1 libjs-mathjax 2.7.4+dfsg-1 InstallationDate: Installed on 2020-07-13 (195 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) PackageArchitecture: all SourcePackage: scikit-learn UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: scikit-learn (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1912993 Title: Error installing python-sklearn-doc To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/scikit-learn/+bug/1912993/+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 think I am having a related problem, Ubuntu 20.10 with all updates installed, nvidia-driver-418-server driver. Lenovo W540 i7-4810MQ Nvidia K2100M + Intel HD 4600 Built-in display 2880x1620 native External display 1920x1080 native I want to set 200% scaling on the built-in display and 100% on the external display, but this is not possible. I can set 100% or 200% for both displays: - 100%: external display looks fine, built-in display too small - 200%: built-in display looks fine, external display too large If I enable fractional scaling then I can set different scaling for each display. The size of everything now looks good on both displays, but every second pixel on the external display looks blurry at 100%. This is particularly noticeable when moving the I-bar cursor of the mouse horizontally over text. This is not the case when fractional scaling is not enabled, so I think it is rendering the external display at double the resolution and scaling down with an inappropriate algorithm. How can I set different scaling on different displays without enabling fractional scaling? I wasn't able to try nightwing666's solution because /etc/modprobe.d/nvidia-modeset.conf does not exist for me, but `sudo cat /sys/module/nvidia_drm/parameters/modeset` returns Y so I think it is enabled anyway. It's a relatively old GPU and the nvidia site claims 340 is the right driver to use, but Ubuntu offered drivers up to 418 so I am using that. I don't mind using the intel GPU, some other driver or figuring out GPU switching, I just want it to work. Really appreciate any help, thanks! -- 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 1912710] [NEW] install interferes with WeBWorK 2.15 install; Apache2 fails to start
Public bug reported: Installing w3c-markup-validator rendered the Apache2 to fail to start; problems related to webworkk2 install. Please see details below. # apt install w3-recs w3c-linkchecker w3c-markup-validator Reading package lists... Done Building dependency tree Reading state information... Done The following packages were automatically installed and are no longer required: libllvm10:i386 linux-headers-5.4.0-52 linux-headers-5.4.0-52-generic linux-headers-5.4.0-54 linux-headers-5.4.0-54-generic linux-headers-5.4.0-58 linux-headers-5.4.0-58-generic linux-image-5.4.0-52-generic linux-image-5.4.0-54-generic linux-image-5.4.0-58-generic linux-modules-5.4.0-52-generic linux-modules-5.4.0-54-generic linux-modules-5.4.0-58-generic linux-modules-extra-5.4.0-52-generic linux-modules-extra-5.4.0-54-generic linux-modules-extra-5.4.0-58-generic Use 'apt autoremove' to remove them. The following additional packages will be installed: libcss-dom-perl libencode-hanextra-perl libencode-jis2k-perl libhtml-encoding-perl libhtml-tidy-perl liblocale-codes-perl libosp5 libset-intspan-perl libsgml-parser-opensp-perl libterm-readkey-perl libtidy5deb1 w3c-sgml-lib Suggested packages: libwebservice-validator-html-w3c-perl libtest-html-w3c-perl The following NEW packages will be installed: libcss-dom-perl libencode-hanextra-perl libencode-jis2k-perl libhtml-encoding-perl libhtml-tidy-perl liblocale-codes-perl libosp5 libset-intspan-perl libsgml-parser-opensp-perl libterm-readkey-perl libtidy5deb1 w3-recs w3c-linkchecker w3c-markup-validator w3c-sgml-lib 0 upgraded, 15 newly installed, 0 to remove and 0 not upgraded. Need to get 37.7 MB of archives. After this operation, 225 MB of additional disk space will be used. Do you want to continue? [Y/n] Get:1 http://ph.archive.ubuntu.com/ubuntu focal/universe amd64 libcss-dom-perl all 0.17-1 [107 kB] Get:2 http://ph.archive.ubuntu.com/ubuntu focal/universe amd64 libencode-hanextra-perl amd64 0.23-5build2 [1,493 kB] Get:3 http://ph.archive.ubuntu.com/ubuntu focal/universe amd64 libencode-jis2k-perl amd64 0.03-1build5 [305 kB] Get:4 http://ph.archive.ubuntu.com/ubuntu focal/universe amd64 libhtml-encoding-perl all 0.61-2 [19.1 kB] Get:5 http://ph.archive.ubuntu.com/ubuntu focal/main amd64 libtidy5deb1 amd64 2:5.6.0-11 [203 kB] Get:6 http://ph.archive.ubuntu.com/ubuntu focal/universe amd64 libhtml-tidy-perl amd64 1.60-4build1 [20.3 kB] Get:7 http://ph.archive.ubuntu.com/ubuntu focal/universe amd64 liblocale-codes-perl all 3.62-1 [246 kB] Get:8 http://ph.archive.ubuntu.com/ubuntu focal/universe amd64 libosp5 amd64 1.5.2-13ubuntu3 [652 kB] Get:9 http://ph.archive.ubuntu.com/ubuntu focal/universe amd64 libset-intspan-perl all 1.19-1 [27.8 kB] Get:10 http://ph.archive.ubuntu.com/ubuntu focal/universe amd64 libsgml-parser-opensp-perl amd64 0.994-3build7 [47.6 kB] Get:11 http://ph.archive.ubuntu.com/ubuntu focal/main amd64 libterm-readkey-perl amd64 2.38-1build1 [24.6 kB] Get:12 http://ph.archive.ubuntu.com/ubuntu focal/multiverse amd64 w3-recs all 20110107-1 [32.4 MB] Get:13 http://ph.archive.ubuntu.com/ubuntu focal/universe amd64 w3c-linkchecker all 4.81-10 [57.3 kB] Get:14 http://ph.archive.ubuntu.com/ubuntu focal/universe amd64 w3c-sgml-lib all 1.3-2 [277 kB] Get:15 http://ph.archive.ubuntu.com/ubuntu focal/universe amd64 w3c-markup-validator all 1.3+dfsg-4 [1,784 kB] Fetched 37.7 MB in 37s (1,022 kB/s) Preconfiguring packages ... Selecting previously unselected package libcss-dom-perl. (Reading database ... 722766 files and directories currently installed.) Preparing to unpack .../00-libcss-dom-perl_0.17-1_all.deb ... Unpacking libcss-dom-perl (0.17-1) ... Selecting previously unselected package libencode-hanextra-perl. Preparing to unpack .../01-libencode-hanextra-perl_0.23-5build2_amd64.deb ... Unpacking libencode-hanextra-perl (0.23-5build2) ... Selecting previously unselected package libencode-jis2k-perl. Preparing to unpack .../02-libencode-jis2k-perl_0.03-1build5_amd64.deb ... Unpacking libencode-jis2k-perl (0.03-1build5) ... Selecting previously unselected package libhtml-encoding-perl. Preparing to unpack .../03-libhtml-encoding-perl_0.61-2_all.deb ... Unpacking libhtml-encoding-perl (0.61-2) ... Selecting previously unselected package libtidy5deb1:amd64. Preparing to unpack .../04-libtidy5deb1_2%3a5.6.0-11_amd64.deb ... Unpacking libtidy5deb1:amd64 (2:5.6.0-11) ... Selecting previously unselected package libhtml-tidy-perl. Preparing to unpack .../05-libhtml-tidy-perl_1.60-4build1_amd64.deb ... Unpacking libhtml-tidy-perl (1.60-4build1) ... Selecting previously unselected package liblocale-codes-perl. Preparing to unpack .../06-liblocale-codes-perl_3.62-1_all.deb ... Unpacking liblocale-codes-perl (3.62-1) ... Selecting previously unselected package libosp5. Preparing to unpack .../07-libosp5_1.5.2-13ubuntu3_amd64.deb ... Unpacking libosp5 (1.5.2-13ubuntu3) ... Selecting previously unselected package libset-intspan-perl. Preparing
Re: [Bug 1871268] Re: Installation fails due to useless immediate configuration error when "Install Third-Party Drivers" is selected
I don't believe that this is fixed. I am still getting errors: [ 88.448840] [ cut here ] [ 88.448842] nouveau :01:00.0: timeout [ 88.448887] WARNING: CPU: 3 PID: 1177 at /build/linux-hwe-5.4-hNUtrM/linux-hwe-5.4-5.4.0/drivers/gpu/drm/nouveau/nvkm/falcon/v1.c:313 nvkm_falcon_v1_clear_interrupt+0xe6/0x100 [nouveau] [ 88.448887] Modules linked in: cmac bnep snd_hda_codec_hdmi snd_soc_hdac_hdmi snd_hda_codec_realtek snd_hda_codec_generic snd_soc_dmic snd_sof_pci snd_sof_intel_hda_common snd_soc_hdac_hda snd_sof_intel_hda snd_sof_intel_byt snd_sof_intel_ipc snd_sof snd_sof_xtensa_dsp snd_hda_ext_core snd_soc_acpi_intel_match snd_soc_acpi ledtrig_audio snd_soc_core snd_compress ac97_bus snd_pcm_dmaengine nls_iso8859_1 joydev hid_multitouch 8250_dw mei_hdcp intel_rapl_msr x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel snd_hda_intel snd_intel_dspcfg uvcvideo kvm iwlmvm snd_seq_midi snd_seq_midi_event snd_hda_codec videobuf2_vmalloc rapl input_leds snd_hda_core snd_rawmidi mac80211 videobuf2_memops btusb snd_hwdep videobuf2_v4l2 btrtl videobuf2_common asus_nb_wmi btbcm asus_wmi btintel intel_cstate libarc4 serio_raw sparse_keymap wmi_bmof videodev snd_seq snd_pcm bluetooth iwlwifi mc snd_seq_device snd_timer snd processor_thermal_device mei_me ecdh_generic intel_rapl_common intel_lpss_pci ecc [ 88.448901] cfg80211 intel_lpss idma64 mei virt_dma soundcore intel_soc_dts_iosf intel_pch_thermal int3403_thermal int340x_thermal_zone mac_hid int3400_thermal acpi_pad asus_wireless acpi_thermal_rel sch_fq_codel parport_pc ppdev lp parport ip_tables x_tables autofs4 algif_skcipher af_alg dm_crypt hid_generic usbhid nouveau i915 crct10dif_pclmul crc32_pclmul mxm_wmi ghash_clmulni_intel ttm i2c_algo_bit aesni_intel drm_kms_helper crypto_simd syscopyarea sysfillrect nvme sysimgblt cryptd fb_sys_fops glue_helper drm r8169 ahci nvme_core realtek libahci i2c_hid wmi video hid pinctrl_cannonlake pinctrl_intel [ 88.448913] CPU: 3 PID: 1177 Comm: gnome-shell Not tainted 5.4.0-62-generic #70~18.04.1-Ubuntu [ 88.448914] Hardware name: ASUSTeK COMPUTER INC. TUF Gaming FX705GE_FX705GE/FX705GE, BIOS FX705GE.302 11/16/2018 [ 88.448929] RIP: 0010:nvkm_falcon_v1_clear_interrupt+0xe6/0x100 [nouveau] [ 88.448930] Code: 45 b0 48 8b 40 10 48 8b 78 10 48 8b 5f 50 48 85 db 74 1b e8 3c 35 d6 c7 48 89 da 48 89 c6 48 c7 c7 ba c7 af c0 e8 2a 7f 70 c7 <0f> 0b eb a8 48 8b 1f eb e0 e8 fc 81 70 c7 66 90 66 2e 0f 1f 84 00 [ 88.448930] RSP: 0018:b912c1447a08 EFLAGS: 00010282 [ 88.448931] RAX: RBX: 9b3ad8cfdb70 RCX: 0006 [ 88.448931] RDX: 0007 RSI: 0096 RDI: 9b3add8d78c0 [ 88.448932] RBP: b912c1447a58 R08: 03e9 R09: 0004 [ 88.448932] R10: 002c R11: 0001 R12: 9b3aca5aab00 [ 88.448933] R13: 0010 R14: ff92 R15: [ 88.448933] FS: 7ff79ae03ac0() GS:9b3add8c() knlGS: [ 88.448934] CS: 0010 DS: ES: CR0: 80050033 [ 88.448934] CR2: 00c42085b000 CR3: 000850710002 CR4: 003606e0 [ 88.448935] Call Trace: [ 88.448950] nvkm_falcon_clear_interrupt+0x15/0x20 [nouveau] [ 88.448972] acr_r352_bootstrap+0x9f/0x290 [nouveau] [ 88.448993] acr_r352_reset+0x39/0x250 [nouveau] [ 88.449014] nvkm_secboot_reset+0x31/0x70 [nouveau] [ 88.449037] gf100_gr_init_ctxctl+0x268/0x700 [nouveau] [ 88.449060] gf100_gr_init+0x563/0x590 [nouveau] [ 88.449082] gf100_gr_init_+0x90/0x120 [nouveau] [ 88.449104] nvkm_gr_init+0x1d/0x20 [nouveau] [ 88.449117] nvkm_engine_init+0x6b/0x1d0 [nouveau] [ 88.449131] nvkm_subdev_init+0xb3/0x1d0 [nouveau] [ 88.449133] ? _cond_resched+0x19/0x40 [ 88.449146] nvkm_engine_ref.part.0+0x4a/0x70 [nouveau] [ 88.449159] nvkm_engine_ref+0x13/0x20 [nouveau] [ 88.449171] nvkm_ioctl_new+0x277/0x2c0 [nouveau] [ 88.449194] ? nvkm_fifo_chan_child_del+0xa0/0xa0 [nouveau] [ 88.449216] ? gf100_gr_dtor+0xe0/0xe0 [nouveau] [ 88.449229] nvkm_ioctl+0x11d/0x280 [nouveau] [ 88.449252] nvkm_client_ioctl+0x12/0x20 [nouveau] [ 88.449264] nvif_client_ioctl+0x2c/0x30 [nouveau] [ 88.449286] usif_ioctl+0x657/0x760 [nouveau] [ 88.449307] nouveau_drm_ioctl+0xac/0xc0 [nouveau] [ 88.449309] do_vfs_ioctl+0xa9/0x640 [ 88.449310] ? handle_mm_fault+0xcb/0x210 [ 88.449311] ksys_ioctl+0x75/0x80 [ 88.449312] __x64_sys_ioctl+0x1a/0x20 [ 88.449313] do_syscall_64+0x57/0x190 [ 88.449315] entry_SYSCALL_64_after_hwframe+0x44/0xa9 [ 88.449316] RIP: 0033:0x7ff797ec0317 [ 88.449317] Code: b3 66 90 48 8b 05 71 4b 2d 00 64 c7 00 26 00 00 00 48 c7 c0 ff ff ff ff c3 66 2e 0f 1f 84 00 00 00 00 00 b8 10 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d 41 4b 2d 00 f7 d8 64 89 01 48 [ 88.449317] RSP: 002b:7ffe9a44a418 EFLAGS: 0246 ORIG_RAX: 0010 [ 88.449318] RAX: ffda RBX: 0038 RCX:
Re: [Bug 1871268] Re: Installation fails due to useless immediate configuration error when "Install Third-Party Drivers" is selected
There definitely seems to be an issue here: [ 88.448840] [ cut here ] [ 88.448842] nouveau :01:00.0: timeout [ 88.448887] WARNING: CPU: 3 PID: 1177 at /build/linux-hwe-5.4-hNUtrM/linux-hwe-5.4-5.4.0/drivers/gpu/drm/nouveau/nvkm/falcon/v1.c:313 nvkm_falcon_v1_clear_interrupt+0xe6/0x100 [nouveau] [ 88.448887] Modules linked in: cmac bnep snd_hda_codec_hdmi snd_soc_hdac_hdmi snd_hda_codec_realtek snd_hda_codec_generic snd_soc_dmic snd_sof_pci snd_sof_intel_hda_common snd_soc_hdac_hda snd_sof_intel_hda snd_sof_intel_byt snd_sof_intel_ipc snd_sof snd_sof_xtensa_dsp snd_hda_ext_core snd_soc_acpi_intel_match snd_soc_acpi ledtrig_audio snd_soc_core snd_compress ac97_bus snd_pcm_dmaengine nls_iso8859_1 joydev hid_multitouch 8250_dw mei_hdcp intel_rapl_msr x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel snd_hda_intel snd_intel_dspcfg uvcvideo kvm iwlmvm snd_seq_midi snd_seq_midi_event snd_hda_codec videobuf2_vmalloc rapl input_leds snd_hda_core snd_rawmidi mac80211 videobuf2_memops btusb snd_hwdep videobuf2_v4l2 btrtl videobuf2_common asus_nb_wmi btbcm asus_wmi btintel intel_cstate libarc4 serio_raw sparse_keymap wmi_bmof videodev snd_seq snd_pcm bluetooth iwlwifi mc snd_seq_device snd_timer snd processor_thermal_device mei_me ecdh_generic intel_rapl_common intel_lpss_pci ecc [ 88.448901] cfg80211 intel_lpss idma64 mei virt_dma soundcore intel_soc_dts_iosf intel_pch_thermal int3403_thermal int340x_thermal_zone mac_hid int3400_thermal acpi_pad asus_wireless acpi_thermal_rel sch_fq_codel parport_pc ppdev lp parport ip_tables x_tables autofs4 algif_skcipher af_alg dm_crypt hid_generic usbhid nouveau i915 crct10dif_pclmul crc32_pclmul mxm_wmi ghash_clmulni_intel ttm i2c_algo_bit aesni_intel drm_kms_helper crypto_simd syscopyarea sysfillrect nvme sysimgblt cryptd fb_sys_fops glue_helper drm r8169 ahci nvme_core realtek libahci i2c_hid wmi video hid pinctrl_cannonlake pinctrl_intel [ 88.448913] CPU: 3 PID: 1177 Comm: gnome-shell Not tainted 5.4.0-62-generic #70~18.04.1-Ubuntu [ 88.448914] Hardware name: ASUSTeK COMPUTER INC. TUF Gaming FX705GE_FX705GE/FX705GE, BIOS FX705GE.302 11/16/2018 [ 88.448929] RIP: 0010:nvkm_falcon_v1_clear_interrupt+0xe6/0x100 [nouveau] [ 88.448930] Code: 45 b0 48 8b 40 10 48 8b 78 10 48 8b 5f 50 48 85 db 74 1b e8 3c 35 d6 c7 48 89 da 48 89 c6 48 c7 c7 ba c7 af c0 e8 2a 7f 70 c7 <0f> 0b eb a8 48 8b 1f eb e0 e8 fc 81 70 c7 66 90 66 2e 0f 1f 84 00 [ 88.448930] RSP: 0018:b912c1447a08 EFLAGS: 00010282 [ 88.448931] RAX: RBX: 9b3ad8cfdb70 RCX: 0006 [ 88.448931] RDX: 0007 RSI: 0096 RDI: 9b3add8d78c0 [ 88.448932] RBP: b912c1447a58 R08: 03e9 R09: 0004 [ 88.448932] R10: 002c R11: 0001 R12: 9b3aca5aab00 [ 88.448933] R13: 0010 R14: ff92 R15: [ 88.448933] FS: 7ff79ae03ac0() GS:9b3add8c() knlGS: [ 88.448934] CS: 0010 DS: ES: CR0: 80050033 [ 88.448934] CR2: 00c42085b000 CR3: 000850710002 CR4: 003606e0 [ 88.448935] Call Trace: [ 88.448950] nvkm_falcon_clear_interrupt+0x15/0x20 [nouveau] [ 88.448972] acr_r352_bootstrap+0x9f/0x290 [nouveau] [ 88.448993] acr_r352_reset+0x39/0x250 [nouveau] [ 88.449014] nvkm_secboot_reset+0x31/0x70 [nouveau] [ 88.449037] gf100_gr_init_ctxctl+0x268/0x700 [nouveau] [ 88.449060] gf100_gr_init+0x563/0x590 [nouveau] [ 88.449082] gf100_gr_init_+0x90/0x120 [nouveau] [ 88.449104] nvkm_gr_init+0x1d/0x20 [nouveau] [ 88.449117] nvkm_engine_init+0x6b/0x1d0 [nouveau] [ 88.449131] nvkm_subdev_init+0xb3/0x1d0 [nouveau] [ 88.449133] ? _cond_resched+0x19/0x40 [ 88.449146] nvkm_engine_ref.part.0+0x4a/0x70 [nouveau] [ 88.449159] nvkm_engine_ref+0x13/0x20 [nouveau] [ 88.449171] nvkm_ioctl_new+0x277/0x2c0 [nouveau] [ 88.449194] ? nvkm_fifo_chan_child_del+0xa0/0xa0 [nouveau] [ 88.449216] ? gf100_gr_dtor+0xe0/0xe0 [nouveau] [ 88.449229] nvkm_ioctl+0x11d/0x280 [nouveau] [ 88.449252] nvkm_client_ioctl+0x12/0x20 [nouveau] [ 88.449264] nvif_client_ioctl+0x2c/0x30 [nouveau] [ 88.449286] usif_ioctl+0x657/0x760 [nouveau] [ 88.449307] nouveau_drm_ioctl+0xac/0xc0 [nouveau] [ 88.449309] do_vfs_ioctl+0xa9/0x640 [ 88.449310] ? handle_mm_fault+0xcb/0x210 [ 88.449311] ksys_ioctl+0x75/0x80 [ 88.449312] __x64_sys_ioctl+0x1a/0x20 [ 88.449313] do_syscall_64+0x57/0x190 [ 88.449315] entry_SYSCALL_64_after_hwframe+0x44/0xa9 [ 88.449316] RIP: 0033:0x7ff797ec0317 [ 88.449317] Code: b3 66 90 48 8b 05 71 4b 2d 00 64 c7 00 26 00 00 00 48 c7 c0 ff ff ff ff c3 66 2e 0f 1f 84 00 00 00 00 00 b8 10 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d 41 4b 2d 00 f7 d8 64 89 01 48 [ 88.449317] RSP: 002b:7ffe9a44a418 EFLAGS: 0246 ORIG_RAX: 0010 [ 88.449318] RAX: ffda RBX: 0038 RCX: 7ff797ec0317 [
[Bug 1910155] Re: Installation manual network config fails with "x.x.x.x is not in contained in x.x.x.x/yy"
Figured out it's not looking for the subnet MASK but just the net cidr (xxx.xxx.16.0/23 in my case) IMHO this is the stupidest way to do this. I don't understand why you have chosen to do this in a completely unintuitive way to how every other operating system is configured using the netmask. ** Changed in: subiquity (Ubuntu) Status: New => Opinion ** Changed in: subiquity (Ubuntu) Status: Opinion => Invalid ** Converted to question: https://answers.launchpad.net/ubuntu/+source/subiquity/+question/694799 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1910155 Title: Installation manual network config fails with "x.x.x.x is not in contained in x.x.x.x/yy" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/subiquity/+bug/1910155/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1910155] [NEW] Installation manual network config fails with "x.x.x.x is not in contained in x.x.x.x/yy"
Public bug reported: 1) lsb_release -rd Description:Ubuntu 20.04.1 LTS Release:20.04 2) Package version Unknown. Whatever version is part of ubuntu-20.04.1-live-server-amd64.iso 2020-07-31 17:35 3) What I expected For valid manual network settings to work. 4) What happened instead Manual network configuration fails saying: "'xxx.xxx.17.114' is not contained in '255.255.254.0/23'" With network settings: Subnet: 255.255.254.0/23 Address: xxx.xxx.17.114 Gateway: xxx.xxx.16.1 Subnet certainly contains xxx.xxx.16.1 - xxx.xxx.17.254 We attempted to define /23 on Address instead, but that is not allowed. I work for NASA GSFC and we're having to proceed without network and then manually edit /etc/netplan/*.yaml after install. If this is an error on our part, can you please clarify what we were supposed to enter for subnet? Since Subnet line requires an entry in CIDR form with error "should be in CIDR form (xx.xx.xx.xx/yy)" Manual network config works fine with: # This is the network config written by 'subiquity' network: version: 2 renderer: networkd ethernets: enp49s0f1: dhcp4: no addresses: - xxx.xxx.17.114/23 gateway4: xxx.xxx.16.1 nameservers: addresses: [xxx.xxx.10.134, xxx.xxx.50.17] **IPs redacted for security purposes ** Affects: subiquity (Ubuntu) Importance: Undecided Status: New ** Attachment added: "Subnet calculation error" https://bugs.launchpad.net/bugs/1910155/+attachment/5449278/+files/Ubuntu-installer-subnet-error.jpg -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1910155 Title: Installation manual network config fails with "x.x.x.x is not in contained in x.x.x.x/yy" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/subiquity/+bug/1910155/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1908992] Re: SYNA30B4:00 06CB:CE09 Mouse on HP EliteBook 850 G7 not working at all
Exact same system model and Synaptics device. We're interested in getting the top two physical buttons working. xev does not even register anything when the buttons are pressed. List of things attempted: 1. xserver-xorg-input-synaptics breaks the touchpad altogether when installed, under-touchpad ones no longer register a central button 2. With xserver-xorg-input-synaptics installed and x.org using, "Using input driver 'synaptics' for 'SYNA30B4:00 06CB:CE09 Touchpad'", ⎡ Virtual core pointer id=2 [master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4 [slave pointer (2)] ⎜ ↳ SYNA30B4:00 06CB:CE09 Mouse id=12 [slave pointer (2)] ⎜ ↳ SYNA30B4:00 06CB:CE09 Touchpad id=13 [slave pointer (2)] ⎜ ↳ Kensington Kensington Expert Mouse id=14 [slave pointer (2)] ⎜ ↳ HID 0566:3013 Consumer Control id=16 [slave pointer (2)] ⎜ ↳ Generic USB Audio Consumer Control id=19 [slave pointer (2)] ⎜ ↳ Generic USB Audio Consumer Control id=21 [slave pointer (2)] ⎣ Virtual core keyboard id=3 [master keyboard (2)] ↳ Virtual core XTEST keyboard id=5 [slave keyboard (3)] ↳ Power Button id=6 [slave keyboard (3)] ↳ Video Bus id=7 [slave keyboard (3)] ↳ Power Button id=8 [slave keyboard (3)] ↳ Sleep Button id=9 [slave keyboard (3)] ↳ HP HD Camera: HP HD Camera id=10 [slave keyboard (3)] ↳ HP HD Camera: HP IR Camera id=11 [slave keyboard (3)] ↳ HID 0566:3013 id=15 [slave keyboard (3)] ↳ HID 0566:3013 System Control id=17 [slave keyboard (3)] ↳ HID 0566:3013 id=18 [slave keyboard (3)] ↳ Generic USB Audio id=20 [slave keyboard (3)] ↳ Generic USB Audio id=22 [slave keyboard (3)] ↳ Intel HID events id=23 [slave keyboard (3)] ↳ Intel HID 5 button array id=24 [slave keyboard (3)] ↳ AT Translated Set 2 keyboard id=25 [slave keyboard (3)] ↳ HP Wireless hotkeys id=26 [slave keyboard (3)] ↳ HP WMI hotkeys id=27 [slave keyboard (3)] ↳ HID 0566:3013 Consumer Control id=28 [slave keyboard (3)] ↳ Generic USB Audio Consumer Control id=29 [slave keyboard (3)] ↳ Generic USB Audio Consumer Control id=30 [slave keyboard (3)] Using input driver 'libinput' for 'SYNA30B4:00 06CB:CE09 Touchpad'", ⎡ Virtual core pointer id=2 [master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4 [slave pointer (2)] ⎜ ↳ KEYBOARD Consumer Control id=11 [slave pointer (2)] ⎜ ↳ HID 0566:3013 Consumer Control id=14 [slave pointer (2)] ⎜ ↳ SYNA30B4:00 06CB:CE09 Mouse id=19 [slave pointer (2)] ⎜ ↳ SYNA30B4:00 06CB:CE09 Touchpad id=20 [slave pointer (2)] ⎜ ↳ Kensington Kensington Expert Mouse id=21 [slave pointer (2)] ⎜ ↳ Generic USB Audio Consumer Control id=22 [slave pointer (2)] ⎜ ↳ Generic USB Audio Consumer Control id=24 [slave pointer (2)] ⎣ Virtual core keyboard id=3 [master keyboard (2)] ↳ Virtual core XTEST keyboard id=5 [slave keyboard (3)] ↳ Power Button id=6 [slave keyboard (3)] ↳ Video Bus id=7 [slave keyboard (3)] ↳ Power Button id=8 [slave keyboard (3)] ↳ Sleep Button id=9 [slave keyboard (3)] ↳ KEYBOARD id=10 [slave keyboard (3)] ↳ KEYBOARD System Control id=12 [slave keyboard (3)] ↳ HID 0566:3013 id=13 [slave keyboard (3)] ↳ HID 0566:3013 System Control id=15 [slave keyboard (3)] ↳ HID 0566:3013 id=16 [slave keyboard (3)] ↳ HP HD Camera: HP HD Camera id=17 [slave keyboard (3)] ↳ HP HD Camera: HP IR Camera id=18 [slave keyboard (3)] ↳ Generic USB Audio id=23 [slave keyboard (3)] ↳ Generic USB Audio id=25 [slave keyboard (3)] ↳ Intel HID events id=26 [slave keyboard (3)] ↳ Intel HID 5 button array id=27 [slave keyboard (3)] ↳ AT Translated Set 2 keyboard id=28 [slave keyboard (3)] ↳ HP Wireless hotkeys id=29 [slave keyboard (3)] ↳ HP WMI hotkeys id=30 [slave keyboard (3)] ↳ KEYBOARD Consumer Control id=31 [slave keyboard (3)] ↳ HID 0566:3013 Consumer Control id=32 [slave keyboard (3)] ↳ Generic USB Audio Consumer Control id=33 [slave keyboard (3)] ↳ Generic USB Audio Consumer Control id=34 [slave keyboard (3)] 2. sudo rmmod i2c_hid sudo modprobe i2c_hid No change in behavior. 3. blacklisting of driver provided no relief. sudo vi /etc/modprobe.d/blacklist.conf (likely a new file) install i2c_hid /bin/true Then, update initramfs and reboot... sudo update-initramfs -u sudo reboot 4. Reinstall of xserver-xorg-input-libinput provided no relief. 5. Back to original config original configuration (no synaptics or blacklist, all 3 buttons working in touchpad), it appears as two devices -- Device 'SYNA30B4:00 06CB:CE09 Mouse': Device Enabled (174): 1 Coordinate Transformation Matrix (176): 1.00, 0.00, 0.00, 0.00, 1.00, 0.00, 0.00, 0.00, 1.00 libinput Natural Scrolling Enabled (309): 0 libinput Natural Scrolling Enabled Default (310): 0 libinput Scroll Methods Available (311): 0, 0, 1 libinput Scroll Method Enabled (312): 0, 0, 1 libinput Scroll Method Enabled Default (313): 0, 0, 1 libinput Button Scrolling Button (314): 2 libinput Button Scrolling Button Default (315): 2 libinput Middle Emulation Enabled (316): 0 libinput Middle Emulation Enabled Default (317): 0 libinput Accel Speed (318): 0.00 libinput Accel Speed
[Bug 1903230] Re: Mutter release 3.36.7
@Timo, Could we wait for bug 1905825? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1903230 Title: Mutter release 3.36.7 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1903230/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1891632] Re: The network manager does not check the NM_SETTING_WIRELESS_WAKE_ON_WLAN_IGNORE bit
** Changed in: oem-priority Status: New => Fix Committed ** Changed in: oem-priority 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/1891632 Title: The network manager does not check the NM_SETTING_WIRELESS_WAKE_ON_WLAN_IGNORE bit To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1891632/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1907441] [NEW] fibre channel driver can not disconnet volume when VM to be evacuated
Public bug reported: When a vm is evacuated, the old node will delete the remaining vm after booting, os-brick cannot obtain the correct multipath, resulting in multipath remaining。 ** Affects: python-os-brick (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1907441 Title: fibre channel driver can not disconnet volume when VM to be evacuated To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-os-brick/+bug/1907441/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1902093] Re: Introduce the new NVIDIA 455 series
The 10DE:1F9D and 10DE:2520 are not included in the modaliases of the nvidia-driver-455. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1902093 Title: Introduce the new NVIDIA 455 series To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1902093/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1891632] Re: The network manager does not check the NM_SETTING_WIRELESS_WAKE_ON_WLAN_IGNORE bit
Hi, I updated the description of the regression potential. Please check it. Thanks. ** Description changed: [Impact] In some cases, the wow is not configured and the NM_SETTING_WIRELESS_WAKE_ON_WLAN_IGNORE is set (for to disable management of wake-on-LAN in NetworkManager). The network manager only checks the NM_SETTING_WIRELESS_WAKE_ON_WLAN_NONE bit. But, the NM_SETTING_WIRELESS_WAKE_ON_WLAN_IGNORE does not be check. So, the management of wake-on-LAN still is done by NetworkManager. - The killer 500s Wi-Fi does not want the network-manger to manager the + The killer 500s Wi-Fi does not want the network-manger to manager the wake-on-LAN so the NM_SETTING_WIRELESS_WAKE_ON_WLAN_IGNORE is set. (The driver will manager itself.) When the network-manager managers the wake- on-LAN, all of the Wi-Fi functions will be lost after the OS resumed from suspend. [Test Case] On a machine with killer 500s Wi-Fi and install the Qualcomm's driver. Step 1. Enter suspend (s2idle) Setp 2. Resume from suspend After resume from suspend, the Wi-Fi function still is normal. You can download the kernel and linux-firmware that backport the Qucalcomm's dirver fro focal from below link: https://launchpad.net/~vicamo/+archive/ubuntu/ppa-1879633 [Regression Potential] - * This patch modifies the wake on lan parameters, please test that the + * This patch modifies the wake on lan parameters, please test that the corresponding feature still works fine with the different configuration values. + + 1. Magic packet test: + Set Wake on Wireless to off + Send magic packet to the system + Ensure it does not wake up + + Set Wake on Wirless to on + Send magic packet to the system + Ensure it does wake up + + 2. Wi-Fi function test after resumed from suspend: + After resume from suspend, the Wi-Fi should work normally. + Scan APs. + Connect to an AP. [Other Info] * None ** Changed in: network-manager (Ubuntu Focal) Status: Incomplete => 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/1891632 Title: The network manager does not check the NM_SETTING_WIRELESS_WAKE_ON_WLAN_IGNORE bit To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1891632/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1] Re: Microsoft has a majority market share
** No longer affects: oem-priority -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1 Title: Microsoft has a majority market share To manage notifications about this bug go to: https://bugs.launchpad.net/clubdistro/+bug/1/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1897551] Re: [MIR] oem-somerville-bronn-meta
** No longer affects: ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1897551 Title: [MIR] oem-somerville-bronn-meta To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1897551/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1896435] Re: [MIR] oem-somerville-sambernardino-meta
** No longer affects: ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1896435 Title: [MIR] oem-somerville-sambernardino-meta To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1896435/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1895278] Re: [MIR] oem-somerville-shireen-meta
** No longer affects: ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1895278 Title: [MIR] oem-somerville-shireen-meta To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1895278/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1899968] Re: samba SMB share certain operations fail
It is ZFS with activated encryption and ACLs. However, the error also occurs with a "normal" ext4 in the same constellation as described above. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1899968 Title: samba SMB share certain operations fail To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1899968/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1899968] Re: samba SMB share certain operations fail
I may have written this a bit unclear, the client is a windows machine. Using Ubuntu as a client works perfectly. One scenario that reproduces the problem: __ Server: Ubuntu 20.04.1 LTS (Ubuntu 5.4.0-51.56-generic 5.4.65) with Samba 4.11.6-Ubuntu Client: Windows 10 (10.0.18363) Mounted a share from the server with the native windows smb client. The server displays this connection with the following parameters (smbstatus): Protocol SMB3_11, no encryption, signing partial(AES-128-CMAC) Action: Running git clone on the client in a shared directory Result: git console out: fatal: cannot create directory at 'images': Directory not empty git fails. Switching servers: __ When i switch the Server to a Ubuntu 18.04 with Samba 4.7.6 or a CentOS with Samba 4.11 and leave the client configuration as-is, the git clone action on the client does NOT fail. I also tried setting the smb server log level to debug, but it does not log anything when the error on the client occurs. Below here is my smb.conf: ___ #=== Global Settings === [global] ## Browsing/Identification ### workgroup = WORKGROUP server string = nas dns proxy = no Debugging/Accounting log file = /var/log/samba/log.%m max log size = 50 syslog = 0 panic action = /usr/share/samba/panic-action %d guest ok = no load printers = no ### Authentication ### server role = standalone server passdb backend = tdbsam obey pam restrictions = yes unix password sync = yes passwd program = /usr/bin/passwd %u passwd chat = *Enter\snew\s*\spassword:* %n\n *Retype\snew\s*\spassword:* %n\n *password\supdated\ssuccessfully* . pam password change = yes map to guest = never security = user Misc usershare allow guests = no [data] comment = "Data Storage" path = /media/data writeable = yes browseable = yes read only = no guest ok = no valid users = @shareadmins vfs objects = recycle recycle:keeptree = Yes force create mode = 0770 force directory mode = 0770 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1899968 Title: samba SMB share certain operations fail To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1899968/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1899968] [NEW] samba SMB share certain operations fail
Public bug reported: Samba SMB shares accessed from Windows or Mac OS don't work as expected when using tools like Git or npm (node package manager). Expected: For example, Git clones to a folder mounted via SMB, as it did with previous ubuntu versions What happened: When using git clone in an smb mounted directory, git throws the following errors: warning: unable to unlink 'images': Directory not empty fatal: cannot create directory at 'images': Directory not empty The errors vary a bit every run (stops at different files/dirs) when extracting or doing other operations. Copying and writing from files via the file browser works without a problem. I could reproduce the error in the following environment with the latest updates applied: Ubuntu 20.04.1 LTS (Ubuntu 5.4.0-51.56-generic 5.4.65) Ubuntu 20.04.1 LTS (Ubuntu 5.4.0-48.52-generic 5.4.60) Samba version 4.11.6-Ubuntu Clients: Windows 10 Version 10.0.18363 Build 18363, Mac OS 10.13.6 On a fresh install with Ubuntu 18.04 (Samba 4.7.6) and CentOS 7 (Samba 4.11) as SMB servers the error does NOT occur, with the same standard smb.conf. Also, setting the following options in smb.conf did NOT help: mangled names = Yes oplocks = False level2 oplocks = False I will happily provide any information/testing that is necessary. Thank you ** Affects: samba (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1899968 Title: samba SMB share certain operations fail To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1899968/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1896435] Re: [MIR] oem-somerville-sambernardino-meta
** Summary changed: - [Draft][MIR] oem-somerville-sambernardino-meta + [MIR] oem-somerville-sambernardino-meta -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1896435 Title: [MIR] oem-somerville-sambernardino-meta To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1896435/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1897551] Re: [MIR] oem-somerville-bronn-meta
** Summary changed: - [Draft][MIR] oem-somerville-bronn-meta + [MIR] oem-somerville-bronn-meta -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1897551 Title: [MIR] oem-somerville-bronn-meta To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1897551/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1897551] Re: [Draft][MIR] oem-somerville-bronn-meta
** Information type changed from Proprietary to Public ** Also affects: ubuntu Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1897551 Title: [Draft][MIR] oem-somerville-bronn-meta To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1897551/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1891632] Re: The network manager does not check the NM_SETTING_WIRELESS_WAKE_ON_WLAN_IGNORE bit
** Changed in: network-manager (Ubuntu Focal) Status: Incomplete => 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/1891632 Title: The network manager does not check the NM_SETTING_WIRELESS_WAKE_ON_WLAN_IGNORE bit To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1891632/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1891632] Re: The network manager does not check the NM_SETTING_WIRELESS_WAKE_ON_WLAN_IGNORE bit
** Description changed: [Impact] In some cases, the wow is not configured and the NM_SETTING_WIRELESS_WAKE_ON_WLAN_IGNORE is set (for to disable management of wake-on-LAN in NetworkManager). The network manager only checks the NM_SETTING_WIRELESS_WAKE_ON_WLAN_NONE bit. But, the NM_SETTING_WIRELESS_WAKE_ON_WLAN_IGNORE does not be check. So, the management of wake-on-LAN still is done by NetworkManager. + The killer 500s Wi-Fi does not want the network-manger to manager the + wake-on-LAN so the NM_SETTING_WIRELESS_WAKE_ON_WLAN_IGNORE is set. (The + driver will manager itself.) When the network-manager managers the wake- + on-LAN, all of the Wi-Fi functions will be lost after the OS resumed + from suspend. + [Test Case] On a machine with killer 500s Wi-Fi and install the Qualcomm's driver. Step 1. Enter suspend (s2idle) Setp 2. Resume from suspend - After resume from suspend, the Wi-Fi functiall still is normal. + After resume from suspend, the Wi-Fi function still is normal. You can download the kernel and linux-firmware that backport the Qucalcomm's dirver fro focal from below link: https://launchpad.net/~vicamo/+archive/ubuntu/ppa-1879633 [Regression Potential] - * When the NM_SETTING_WIRELESS_WAKE_ON_WLAN_IGNORE is set, the network - won't management the WOW function forever. The WOW function totally - depend on device driver. + * This patch modifies the wake on lan parameters, please test that the + corresponding feature still works fine with the different configuration + values. [Other Info] * None -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1891632 Title: The network manager does not check the NM_SETTING_WIRELESS_WAKE_ON_WLAN_IGNORE bit To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1891632/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1891632] Re: The network manager does not check the NM_SETTING_WIRELESS_WAKE_ON_WLAN_IGNORE bit
** Description changed: [Impact] - In some cases, the wow is not configured and the + In some cases, the wow is not configured and the NM_SETTING_WIRELESS_WAKE_ON_WLAN_IGNORE is set (for to disable management of wake-on-LAN in NetworkManager). - The network manager only checks the NM_SETTING_WIRELESS_WAKE_ON_WLAN_NONE bit. - But, the NM_SETTING_WIRELESS_WAKE_ON_WLAN_IGNORE does not be check. - So, the management of wake-on-LAN still is done by NetworkManager. + The network manager only checks the NM_SETTING_WIRELESS_WAKE_ON_WLAN_NONE bit. + But, the NM_SETTING_WIRELESS_WAKE_ON_WLAN_IGNORE does not be check. + So, the management of wake-on-LAN still is done by NetworkManager. [Test Case] - On a machine with killer 500s Wi-Fi and install the Qualcomm's driver. - Step 1. Enter suspend (s2idle) - Setp 2. Resume from suspend + On a machine with killer 500s Wi-Fi and install the Qualcomm's driver. + Step 1. Enter suspend (s2idle) + Setp 2. Resume from suspend - After resume from suspend, the Wi-Fi functiall still is normal. + After resume from suspend, the Wi-Fi functiall still is normal. - You can download the kernel and linux-firmware that backport the Qucalcomm's dirver fro focal from below link: - https://launchpad.net/~vicamo/+archive/ubuntu/ppa-1879633 + You can download the kernel and linux-firmware that backport the Qucalcomm's dirver fro focal from below link: + https://launchpad.net/~vicamo/+archive/ubuntu/ppa-1879633 [Regression Potential] - * No potential regressions. + * When the NM_SETTING_WIRELESS_WAKE_ON_WLAN_IGNORE is set, the network + won't management the WOW forever. [Other Info] - - * None + + * None ** Description changed: [Impact] In some cases, the wow is not configured and the NM_SETTING_WIRELESS_WAKE_ON_WLAN_IGNORE is set (for to disable management of wake-on-LAN in NetworkManager). The network manager only checks the NM_SETTING_WIRELESS_WAKE_ON_WLAN_NONE bit. But, the NM_SETTING_WIRELESS_WAKE_ON_WLAN_IGNORE does not be check. So, the management of wake-on-LAN still is done by NetworkManager. [Test Case] On a machine with killer 500s Wi-Fi and install the Qualcomm's driver. Step 1. Enter suspend (s2idle) Setp 2. Resume from suspend After resume from suspend, the Wi-Fi functiall still is normal. You can download the kernel and linux-firmware that backport the Qucalcomm's dirver fro focal from below link: https://launchpad.net/~vicamo/+archive/ubuntu/ppa-1879633 [Regression Potential] * When the NM_SETTING_WIRELESS_WAKE_ON_WLAN_IGNORE is set, the network - won't management the WOW forever. + won't management the WOW function forever. The WOW function totally + depend on device driver. [Other Info] * None -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1891632 Title: The network manager does not check the NM_SETTING_WIRELESS_WAKE_ON_WLAN_IGNORE bit To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1891632/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1896435] Re: [Draft][MIR] oem-somerville-sambernardino-meta
** Information type changed from Proprietary to Public ** Also affects: ubuntu Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1896435 Title: [Draft][MIR] oem-somerville-sambernardino-meta To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1896435/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1896419] Re: Comet Lake CPUID family:model:stepping 0x6:a5:2 (6:165:2) is not included
I verified this bug on Dell G5-5500. $ systemctl is-active thermald active $ sudo dpkg -l | grep thermald ii thermald 1.9.1-1ubuntu0.3 [..skip..] ** Tags removed: verification-needed-focal ** Tags added: verification-done-focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1896419 Title: Comet Lake CPUID family:model:stepping 0x6:a5:2 (6:165:2) is not included To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1896419/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1895278] Re: [Draft][MIR] oem-somerville-shireen-meta
The attached file is the debdiff file that generated by the oem- metapackage-mir-check script. ** Patch added: "oem-somerville-shireen-meta_20.04~ubuntu1.debdiff" https://bugs.launchpad.net/oem-priority/+bug/1895278/+attachment/5411633/+files/oem-somerville-shireen-meta_20.04~ubuntu1.debdiff ** Summary changed: - [Draft][MIR] oem-somerville-shireen-meta + [MIR] oem-somerville-shireen-meta ** Information type changed from Proprietary to Public ** Also affects: ubuntu Importance: Undecided Status: New ** Changed in: oem-priority 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/1895278 Title: [MIR] oem-somerville-shireen-meta To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1895278/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1891632] Re: The network manager does not check the NM_SETTING_WIRELESS_WAKE_ON_WLAN_IGNORE bit
** Merge proposal linked: https://code.launchpad.net/~lihow731/network-manager/+git/network-manager/+merge/390544 ** Merge proposal unlinked: https://code.launchpad.net/~lihow731/network-manager/+git/network-manager/+merge/388865 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1891632 Title: The network manager does not check the NM_SETTING_WIRELESS_WAKE_ON_WLAN_IGNORE bit To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1891632/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1893004] Re: [SRU]alsa-ucm-conf: the volume can't be adjusted on the usb audio of the Dell WD15/WD19 dock
I verified the alsa-ucm-conf 1.2.2-1ubuntu0.3 on WD19 Dock station. After applied new UCM configure, the volume of the headset microphone can be adjusted via the input device volume in Settings. ** Tags removed: verification-needed-focal ** Tags added: verification-done-focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1893004 Title: [SRU]alsa-ucm-conf: the volume can't be adjusted on the usb audio of the Dell WD15/WD19 dock To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1893004/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1889367] Re: [MIR] oem-somerville-metapod-meta
** Description changed: [Availability] This is a meta package for https://wiki.ubuntu.com/MIRTeam/Exceptions/OEM that means the package doesn't exist in Debian or Ubuntu archive yet. The source code of the oem-somerville-metapod-meta for focal: git clone -b metapod-focal-ubuntu https://git.launchpad.net/~oem-solutions-engineers/pc-enablement/+git/oem-somerville-projects-meta [Rationale] We want to improve the hardware support for some Dell laptops. [Security] No CVE/known security issue. [Quality assurance] I have used ppa:oem-solutions-engineers/oem-projects-meta to check this package on Dell laptops. - oem-somerville-somerville-metapod-meta will be upgraded to 20.04ubuntu2 from OEM archive. + oem-somerville-metapod-meta will be upgraded to 20.04ubuntu2 from OEM archive. [Dependencies] It only depends on ubuntu-oem-keyring. [Standards compliance] This package should have met all requirements of https://wiki.ubuntu.com/MIRTeam/Exceptions/OEM. [Maintenance] Canonical OEM Enablement Team will take care of the maintenance. [Background information] Please check https://wiki.ubuntu.com/MIRTeam/Exceptions/OEM for details. Please use "oem-metapackage-mir-check" in lp:ubuntu-archive-tools to verify this MIR against the reference package in the archive. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1889367 Title: [MIR] oem-somerville-metapod-meta To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1889367/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1888599] Re: [MIR] oem-somerville-caterpie-meta
** Changed in: oem-priority Status: Confirmed => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1888599 Title: [MIR] oem-somerville-caterpie-meta To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1888599/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1888599] Re: [MIR] oem-somerville-caterpie-meta
After installed ubuntu 20.04.1 and enabled "Pre-released updates(focal- proposed)", the oem-somerville-caterpie-meta can be installed and upgraded normally. ** Tags removed: verification-needed-focal ** Tags added: verification-done-focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1888599 Title: [MIR] oem-somerville-caterpie-meta To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1888599/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1893044] Re: pitiv-0.999-2: Missing soft dependencies `GSound`, `libav` (Ubuntu 20.04 LTS focal fossa)
Should this be considered a bug? ** Changed in: pitivi (Ubuntu) Status: New => Invalid ** Converted to question: https://answers.launchpad.net/ubuntu/+source/pitivi/+question/692615 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1893044 Title: pitiv-0.999-2: Missing soft dependencies `GSound`, `libav` (Ubuntu 20.04 LTS focal fossa) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pitivi/+bug/1893044/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1893044] [NEW] pitiv-0.999-2: Missing soft dependencies `GSound`, `libav` (Ubuntu 20.04 LTS focal fossa)
Public bug reported: Fresh install of pitivi (pitivi/focal,now 0.999-2 amd64) gives missing (soft) dependency messages: Missing soft dependency: - GSound not found on the system -> enables sound notifications when rendering is complete Missing soft dependency: - libav not found on the system -> additional multimedia codecs through the GStreamer Libav library I had to install: * gir1.2-gsound-1.0 * gstreamer1.0-libav FYI. ** Affects: pitivi (Ubuntu) Importance: Undecided Status: Invalid ** Attachment added: "Missing dependencies message box" https://bugs.launchpad.net/bugs/1893044/+attachment/5404745/+files/pitivi-0.999-2.jpg ** Description changed: - Fresh install of pitivi gives a missing (soft) dependencies message: + Fresh install of pitivi (pitivi/focal,now 0.999-2 amd64) gives a missing + (soft) dependencies message: Missing soft dependency: - GSound not found on the system - -> enables sound notifications when rendering is complete + -> enables sound notifications when rendering is complete Missing soft dependency: - libav not found on the system - -> additional multimedia codecs through the GStreamer Libav library + -> additional multimedia codecs through the GStreamer Libav library I had to install: - * gir1.2-gsound-1.0 + * gir1.2-gsound-1.0 * gstreamer1.0-libav FYI. ** Package changed: ubiquity (Ubuntu) => pitivi (Ubuntu) ** Description changed: - Fresh install of pitivi (pitivi/focal,now 0.999-2 amd64) gives a missing - (soft) dependencies message: + Fresh install of pitivi (pitivi/focal,now 0.999-2 amd64) gives missing + (soft) dependency messages: Missing soft dependency: - GSound not found on the system -> enables sound notifications when rendering is complete Missing soft dependency: - libav not found on the system -> additional multimedia codecs through the GStreamer Libav library I had to install: * gir1.2-gsound-1.0 * gstreamer1.0-libav FYI. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1893044 Title: pitiv-0.999-2: Missing soft dependencies `GSound`, `libav` (Ubuntu 20.04 LTS focal fossa) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pitivi/+bug/1893044/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1891632] Re: The network manager does not check the NM_SETTING_WIRELESS_WAKE_ON_WLAN_IGNORE bit
The patch was merged into debian network-manager repository in https://salsa.debian.org/utopia-team/network-manager/-/commit/e7b44ef4c80907346ec7492a09c45277459924fc. For Groovy, when network-manager version >= 1.26.2, this patch will be included. For Focal, the network-manager (1.22.10) needs to carry on this patch. Append the debdiff for focal. ** Patch added: "network-manager_1.22.10-1ubuntu2.2.debdiff" https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1891632/+attachment/5404329/+files/network-manager_1.22.10-1ubuntu2.2.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1891632 Title: The network manager does not check the NM_SETTING_WIRELESS_WAKE_ON_WLAN_IGNORE bit To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1891632/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1891632] Re: The network manager does not check the NM_SETTING_WIRELESS_WAKE_ON_WLAN_IGNORE bit
** Also affects: oem-priority/focal Importance: Undecided Status: New ** No longer affects: oem-priority/focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1891632 Title: The network manager does not check the NM_SETTING_WIRELESS_WAKE_ON_WLAN_IGNORE bit To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1891632/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1888599] Re: [MIR] oem-somerville-caterpie-meta
The public archive issue was solved. ** Also affects: ubuntu Importance: Undecided Status: New ** No longer affects: oem-priority/focal ** Changed in: oem-priority Status: In Progress => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1888599 Title: [MIR] oem-somerville-caterpie-meta To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1888599/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1889367] Re: [MIR] oem-somerville-metapod-meta
** Changed in: oem-priority Status: In Progress => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1889367 Title: [MIR] oem-somerville-metapod-meta To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1889367/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1857496] Re: usb-audio: the mic can't record any sound after resume on Dell Dock WD19
Changed this bug status to fix released. Because of the original bug 1849812 has been fix released. ** Changed in: oem-priority 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/1857496 Title: usb-audio: the mic can't record any sound after resume on Dell Dock WD19 To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1857496/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1891632] Re: The network manager does not check the NM_SETTING_WIRELESS_WAKE_ON_WLAN_IGNORE bit
** Description changed: - In some cases, the wow is not configured and the + [Impact] + + In some cases, the wow is not configured and the NM_SETTING_WIRELESS_WAKE_ON_WLAN_IGNORE is set (for to disable management of wake-on-LAN in NetworkManager). - The network manager only checks the NM_SETTING_WIRELESS_WAKE_ON_WLAN_NONE bit. - But, the NM_SETTING_WIRELESS_WAKE_ON_WLAN_IGNORE does not be check. - So, the management of wake-on-LAN still is done by NetworkManager. + The network manager only checks the NM_SETTING_WIRELESS_WAKE_ON_WLAN_NONE bit. + But, the NM_SETTING_WIRELESS_WAKE_ON_WLAN_IGNORE does not be check. + So, the management of wake-on-LAN still is done by NetworkManager. + + [Test Case] + + On a machine with killer 500s Wi-Fi and install the Qualcomm's driver. + Step 1. Enter suspend (s2idle) + Setp 2. Resume from suspend + + After resume from suspend, the Wi-Fi functiall still is normal. + + You can download the kernel and linux-firmware that backport the Qucalcomm's dirver fro focal from below link: + https://launchpad.net/~vicamo/+archive/ubuntu/ppa-1879633 + + [Regression Potential] + + * No potential regressions. + + [Other Info] + + * None -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1891632 Title: The network manager does not check the NM_SETTING_WIRELESS_WAKE_ON_WLAN_IGNORE bit To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1891632/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1891632] [NEW] The network manager does not check the NM_SETTING_WIRELESS_WAKE_ON_WLAN_IGNORE bit
Public bug reported: In some cases, the wow is not configured and the NM_SETTING_WIRELESS_WAKE_ON_WLAN_IGNORE is set (for to disable management of wake-on-LAN in NetworkManager). The network manager only checks the NM_SETTING_WIRELESS_WAKE_ON_WLAN_NONE bit. But, the NM_SETTING_WIRELESS_WAKE_ON_WLAN_IGNORE does not be check. So, the management of wake-on-LAN still is done by NetworkManager. ** Affects: oem-priority Importance: Critical Assignee: Leon Liao (lihow731) Status: New ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New ** Information type changed from Proprietary to Public ** Also affects: network-manager (Ubuntu) Importance: Undecided Status: New ** Changed in: oem-priority Assignee: (unassigned) => Leon Liao (lihow731) ** Merge proposal linked: https://code.launchpad.net/~lihow731/network-manager/+git/network-manager/+merge/388865 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1891632 Title: The network manager does not check the NM_SETTING_WIRELESS_WAKE_ON_WLAN_IGNORE bit To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1891632/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1888101] Re: 'unsupported protocol' error when using PyMySQL
Hi Seth,
first install the server:
sudo apt install mariadb-server
then the PyMySQL:
python3 -m pip install PyMySQL
then create a ca-cert:
openssl genrsa 2048 > ca-key.pem
openssl req -new -x509 -nodes -days 3600 -key ca-key.pem -out ca-cert.pem
then run this python-test-script:
import os
import pymysql
#pymysql.connections.DEBUG = True
#pymysql._auth.DEBUG = True
host = "127.0.0.1"
port = 3306
ca = os.path.expanduser("~/ca-cert.pem")
ssl = {'ca': ca, 'check_hostname': False}
user = 'user'
passwd = 'passwd'
def test_ssl():
con = pymysql.connect(user=user, password=passwd, host=host, port=port,
ssl=ssl)
con.close()
test_ssl()
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1888101
Title:
'unsupported protocol' error when using PyMySQL
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1888101/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1888599] Re: [MIR] oem-somerville-fossa-caterpie-meta
** Also affects: oem-priority Importance: Undecided Status: New ** No longer affects: oem-somerville-three-eyed-raven-meta (Ubuntu) ** Also affects: oem-priority/focal Importance: Undecided Status: New ** Also affects: ubuntu Importance: Undecided Status: New ** No longer affects: ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1888599 Title: [MIR] oem-somerville-fossa-caterpie-meta To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1888599/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1888599] [NEW] [MIR] oem-somerville-fossa-caterpie-meta
Public bug reported: [Availability] This is a meta package for https://wiki.ubuntu.com/MIRTeam/Exceptions/OEM that means the package doesn't exist in Debian or Ubuntu archive yet. oem-somerville-fossa-catepie-meta 20.04~ubuntu1 for focal in https://launchpad.net/~oem-solutions-engineers/+archive/ubuntu/oem-projects-meta/+packages [Rationale] We want to improve the hardware support for some Dell platforms on focal. [Security] No CVE/known security issue. [Quality assurance] I have used https://launchpad.net/~oem-solutions-engineers/+archive/ubuntu/oem-projects-meta/+packages to check this package on some Dell Platforms and it works as expected. oem-somerville-fossa-catepie-meta will be upgraded to 20.04ubuntu1 from OEM archive. [Dependencies] It only depends on ubuntu-oem-keyring. [Standards compliance] This package should have met all requirements of https://wiki.ubuntu.com/MIRTeam/Exceptions/OEM. [Maintenance] Canonical OEM Enablement Team will take care of the maintenance. [Background information] Please check https://wiki.ubuntu.com/MIRTeam/Exceptions/OEM for details. Please use "oem-metapackage-mir-check" in lp:ubuntu-archive-tools to verify this MIR against the reference package in the archive. ** Affects: oem-somerville-three-eyed-raven-meta (Ubuntu) Importance: Undecided Status: Invalid ** Tags: oem-meta-packages ** Changed in: oem-somerville-three-eyed-raven-meta (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1888599 Title: [MIR] oem-somerville-fossa-caterpie-meta To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/oem-somerville-three-eyed-raven-meta/+bug/1888599/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1888101] [NEW] 'unsupported protocol' error when using PyMySQL
Public bug reported: 1) Description:Ubuntu 20.04 LTS Release:20.04 2) openssl: Installiert: 1.1.1f-1ubuntu2 Installationskandidat: 1.1.1f-1ubuntu2 Versionstabelle: *** 1.1.1f-1ubuntu2 500 500 http://de.archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status 3) + 4) I am trying to connect to my MariaDB with python package "PyMySQL" and SSL enabled. On my old installation (Kubuntu 19.10) this worked. With the new installation (also new PC: Xubuntu 20.04) I get this error message: ssl.SSLError: [SSL: UNSUPPORTED_PROTOCOL] unsupported protocol (_ssl.c:1108) Here are my installation details: Old installation: python 3.7.5, pymysql 0.9.3, ssl.OPENSSL_VERSION = 1.1.1c 28 May 2019 New installation: python 3.8.2, pymysql 0.9.3, ssl.OPENSSL_VERSION = 1.1.1f 31 Mar 2020 When I use python with a different SSL version...: this works: python 3.7.5, ssl.OPENSSL_VERSION = OpenSSL 1.1.0m-dev xx XXX this works: python 3.7.5, ssl.OPENSSL_VERSION = OpenSSL 1.1.1h-dev xx XXX this works: python 3.8.2, ssl.OPENSSL_VERSION = OpenSSL 1.1.1h-dev xx XXX It seems, like the one specific version of openSSL (1.1.1f 31 Mar 2020) does not work together with PyMySQL. Some more details I have posted here: https://stackoverflow.com/questions/62964998/unsupported-protocol-error-when-using-pymysql ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: openssl 1.1.1f-1ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Sat Jul 18 15:42:27 2020 InstallationDate: Installed on 2020-07-13 (4 days ago) InstallationMedia: Xubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: openssl UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: openssl (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1888101 Title: 'unsupported protocol' error when using PyMySQL To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1888101/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1885349] Re: Upgrading to 5.4.0-39-generic kernel causes GPU to crash shortly after logging in
** Description changed: I upgraded my kids' computer to the 5.4.0-39-generic kernel today. - Afterwards, the screen started freezing after a couple of minutes of - use. + Afterwards, the screen started freezing very shortly after logging in. + + When choosing the older 5.4.0-37-generic from the grub menu I see no + crashes at all. I could login over SSH from my computer without difficulty. Running dmesg showed some variation of the following. For example, just now it crashed when my daughter tried to launch Firefox after logging in, and the following appeared while I was watching the output of 'dmesg -w': 68.824967] NVRM: GPU at PCI::01:00: GPU-7f44f739-3c25-c282-d7a3-c4ec7c79e755 - [ 68.824970] NVRM: GPU Board Serial Number: + [ 68.824970] NVRM: GPU Board Serial Number: [ 68.824974] NVRM: Xid (PCI::01:00): 79, pid=926, GPU has fallen off the bus. [ 68.824976] NVRM: GPU :01:00.0: GPU has fallen off the bus. [ 68.824977] NVRM: GPU :01:00.0: GPU is on Board . [ 68.826134] NVRM: A GPU crash dump has been created. If possible, please run -NVRM: nvidia-bug-report.sh as root to collect this data before -NVRM: the NVIDIA kernel module is unloaded + NVRM: nvidia-bug-report.sh as root to collect this data before + NVRM: the NVIDIA kernel module is unloaded The system has been running beautifully up until today. Installing the other driver versions listed below didn't help any. $ sudo ubuntu-drivers devices == /sys/devices/pci:00/:00:01.0/:01:00.0 == modalias : pci:v10DEd1C82sv1458sd3746bc03sc00i00 vendor : NVIDIA Corporation model: GP107 [GeForce GTX 1050 Ti] driver : nvidia-driver-390 - distro non-free driver : nvidia-driver-435 - distro non-free driver : nvidia-driver-440 - distro non-free recommended driver : xserver-xorg-video-nouveau - distro free builtin ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-39-generic 5.4.0-39.43 ProcVersionSignature: Ubuntu 5.4.0-39.43-generic 5.4.41 Uname: Linux 5.4.0-39-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-id', '/dev/snd/controlC2', '/dev/snd/pcmC2D0c', '/dev/snd/controlC1', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D9p', '/dev/snd/pcmC1D8p', '/dev/snd/pcmC1D7p', '/dev/snd/pcmC1D3p', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D2', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip Date: Sat Jun 27 16:27:12 2020 HibernationDevice: RESUME=UUID=447e6756-8310-4bc0-9ccc-108f1df5019b InstallationDate: Installed on 2014-07-08 (2180 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: Gigabyte Technology Co., Ltd. Z97N-WIFI ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-39-generic root=UUID=464ea2d6-bc69-4340-88ed-33902e231ef3 ro mds=off mitigations=off quiet splash vt.handoff=7 RelatedPackageVersions: - linux-restricted-modules-5.4.0-39-generic N/A - linux-backports-modules-5.4.0-39-generic N/A - linux-firmware1.187 + linux-restricted-modules-5.4.0-39-generic N/A + linux-backports-modules-5.4.0-39-generic N/A + linux-firmware1.187 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/18/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F7 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z97N-WIFI dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF7:bd09/18/2015:svnGigabyteTechnologyCo.,Ltd.:pnZ97N-WIFI:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ97N-WIFI:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: Z97N-WIFI dmi.product.sku: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1885349 Title: Upgrading to 5.4.0-39-generic kernel causes GPU to crash shortly after logging in To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1885349/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1885349] [NEW] Upgrading to 5.4.0-39-generic kernel causes GPU to crash shortly after logging in
Public bug reported: I upgraded my kids' computer to the 5.4.0-39-generic kernel today. Afterwards, the screen started freezing after a couple of minutes of use. I could login over SSH from my computer without difficulty. Running dmesg showed some variation of the following. For example, just now it crashed when my daughter tried to launch Firefox after logging in, and the following appeared while I was watching the output of 'dmesg -w': 68.824967] NVRM: GPU at PCI::01:00: GPU-7f44f739-3c25-c282-d7a3-c4ec7c79e755 [ 68.824970] NVRM: GPU Board Serial Number: [ 68.824974] NVRM: Xid (PCI::01:00): 79, pid=926, GPU has fallen off the bus. [ 68.824976] NVRM: GPU :01:00.0: GPU has fallen off the bus. [ 68.824977] NVRM: GPU :01:00.0: GPU is on Board . [ 68.826134] NVRM: A GPU crash dump has been created. If possible, please run NVRM: nvidia-bug-report.sh as root to collect this data before NVRM: the NVIDIA kernel module is unloaded The system has been running beautifully up until today. Installing the other driver versions listed below didn't help any. $ sudo ubuntu-drivers devices == /sys/devices/pci:00/:00:01.0/:01:00.0 == modalias : pci:v10DEd1C82sv1458sd3746bc03sc00i00 vendor : NVIDIA Corporation model: GP107 [GeForce GTX 1050 Ti] driver : nvidia-driver-390 - distro non-free driver : nvidia-driver-435 - distro non-free driver : nvidia-driver-440 - distro non-free recommended driver : xserver-xorg-video-nouveau - distro free builtin ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-39-generic 5.4.0-39.43 ProcVersionSignature: Ubuntu 5.4.0-39.43-generic 5.4.41 Uname: Linux 5.4.0-39-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-id', '/dev/snd/controlC2', '/dev/snd/pcmC2D0c', '/dev/snd/controlC1', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D9p', '/dev/snd/pcmC1D8p', '/dev/snd/pcmC1D7p', '/dev/snd/pcmC1D3p', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D2', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip Date: Sat Jun 27 16:27:12 2020 HibernationDevice: RESUME=UUID=447e6756-8310-4bc0-9ccc-108f1df5019b InstallationDate: Installed on 2014-07-08 (2180 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: Gigabyte Technology Co., Ltd. Z97N-WIFI ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-39-generic root=UUID=464ea2d6-bc69-4340-88ed-33902e231ef3 ro mds=off mitigations=off quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-39-generic N/A linux-backports-modules-5.4.0-39-generic N/A linux-firmware1.187 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/18/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F7 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z97N-WIFI dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF7:bd09/18/2015:svnGigabyteTechnologyCo.,Ltd.:pnZ97N-WIFI:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ97N-WIFI:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: Z97N-WIFI dmi.product.sku: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ** Summary changed: - System with 1050Ti suffers GPU crash shortly after logging in + Upgrading to 5.4.0-39-generic kernel causes GPU to crash shortly after logging in -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1885349 Title: Upgrading to 5.4.0-39-generic kernel causes GPU to crash shortly after logging in To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1885349/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1883444] [NEW] upgrade from 18.04 to 20.04
Public bug reported: cant upgrade to 20.04, crashes with error ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ubuntu-release-upgrader-core 1:18.04.37 ProcVersionSignature: Ubuntu 5.3.0-7648.41~1586790036~18.04~600aeb5-generic 5.3.18 Uname: Linux 5.3.0-7648-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.15 Architecture: amd64 CrashDB: ubuntu Date: Sun Jun 14 19:27:54 2020 InstallationDate: Installed on 2018-07-14 (701 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader UpgradeStatus: Upgraded to bionic on 2020-06-14 (0 days ago) VarLogDistupgradeAptlog: Log time: 2020-06-14 19:25:41.898117 Log time: 2020-06-14 19:25:46.570275 Log time: 2020-06-14 19:26:41.970307 Log time: 2020-06-14 19:27:57.186729 VarLogDistupgradeTermlog: ** Affects: ubuntu-release-upgrader (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic dist-upgrade -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1883444 Title: upgrade from 18.04 to 20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1883444/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1876020] Re: Old IP does not go away
The second IP address was caused by DHCPCD running and assigning address via DHCP. This seems to the bug, because via netplan I have assigned static IP -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1876020 Title: Old IP does not go away To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/netplan.io/+bug/1876020/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1883399] [NEW] ip address in the netplan is ignored
Public bug reported: >From Netplan: leonbrag@minivm:/etc/netplan$ cat 00-installer-config.yaml # This is the network config written by 'subiquity' network: version: 2 renderer: networkd ethernets: eth0: dhcp4: no addresses: [192.168.4.5/24] gateway4: 192.168.4.1 nameservers: addresses: [192.168.4.1] Real Address that system got from somewhere, which is obviously wrong 2: eth0: mtu 1500 qdisc mq state UP group default qlen 1000 link/ether 00:15:5d:91:c9:00 brd ff:ff:ff:ff:ff:ff inet 192.168.4.55/24 brd 192.168.4.255 scope global noprefixroute eth0 valid_lft forever preferred_lft forever inet6 2601:600:9480:1e4:6b2b:1db2:658b:e692/64 scope global dynamic mngtmpaddr noprefixroute valid_lft 2591701sec preferred_lft 604501sec inet6 fe80::215:5dff:fe91:c900/64 scope link valid_lft forever preferred_lft forever ** Affects: systemd (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1883399 Title: ip address in the netplan is ignored To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1883399/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1883107] Re: Desktop continues to suspend automatically despite attempts to disable it
Screenshot of the graphical configurator ** Attachment added: "Settings.png" https://bugs.launchpad.net/ubuntu/+source/ubuntu-unity-meta/+bug/1883107/+attachment/5383278/+files/Settings.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1883107 Title: Desktop continues to suspend automatically despite attempts to disable it To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-unity-meta/+bug/1883107/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1883107] Re: Desktop continues to suspend automatically despite attempts to disable it
Yes, I did restart this desktop after upgrade. This graphical configurator: (it's not obvious to me how to determine which one this actually is: will post another screen capture of the configurator that opens up. ** Attachment added: "Top right corner.png" https://bugs.launchpad.net/ubuntu/+source/ubuntu-unity-meta/+bug/1883107/+attachment/5383277/+files/Top%20right%20corner.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1883107 Title: Desktop continues to suspend automatically despite attempts to disable it To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-unity-meta/+bug/1883107/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1883107] [NEW] Desktop continues to suspend automatically despite attempts to disable it
Public bug reported: Before upgrading to 20.04 from 19.10 recently, my desktop would not automatically suspend when idle. After upgrading, it started suspending automatically. First thing I did was try to use the graphical configurator: but this continued to suspend. Then I started investigating gsettings: it turns out that the configurator was changing org.gnome.settings- daemon.plugins.power but not com.canonical.unity.settings- daemon.plugins.power. So the second time I changed the latter settings using the command line. Unless I'm mistaken, this appears to prevented my desktop from suspending as long as I don't lock the screen. However, if I lock the screen, then it continues to suspend itself even after my command-line attempt at disabling suspend. lpsmith@kleene:~$ gsettings list-recursively | grep -i "suspend\|sleep" org.cinnamon.desktop.keybindings.media-keys suspend ['XF86Sleep'] org.cinnamon.desktop.keybindings.media-keys hibernate ['XF86Suspend', 'XF86Hibernate'] org.gnome.settings-daemon.plugins.media-keys suspend [''] org.gnome.settings-daemon.plugins.media-keys hibernate-static ['XF86Suspend', 'XF86Hibernate'] org.gnome.settings-daemon.plugins.media-keys suspend-static ['XF86Sleep'] com.canonical.unity.settings-daemon.plugins.power lid-close-ac-action 'suspend' com.canonical.unity.settings-daemon.plugins.power power-button-action 'suspend' com.canonical.unity.settings-daemon.plugins.power lid-close-suspend-with-external-monitor false com.canonical.unity.settings-daemon.plugins.power button-power 'suspend' com.canonical.unity.settings-daemon.plugins.power lid-close-battery-action 'suspend' com.canonical.unity.settings-daemon.plugins.power button-suspend 'suspend' com.canonical.unity.settings-daemon.plugins.power button-sleep 'hibernate' com.canonical.unity.settings-daemon.plugins.power sleep-inactive-ac-timeout 1200 com.canonical.unity.settings-daemon.plugins.power sleep-inactive-ac-type 'nothing' com.canonical.unity.settings-daemon.plugins.power sleep-inactive-battery-type 'nothing' com.canonical.unity.settings-daemon.plugins.power sleep-inactive-battery-timeout 1200 org.gnome.settings-daemon.plugins.power lid-close-ac-action 'suspend' org.gnome.settings-daemon.plugins.power lid-close-suspend-with-external-monitor false org.gnome.settings-daemon.plugins.power lid-close-battery-action 'suspend' org.gnome.settings-daemon.plugins.power critical-battery-action 'suspend' org.gnome.settings-daemon.plugins.power button-suspend 'suspend' org.gnome.settings-daemon.plugins.power button-sleep 'suspend' org.gnome.settings-daemon.plugins.power sleep-inactive-ac-timeout 3600 org.gnome.settings-daemon.plugins.power sleep-inactive-ac-type 'suspend' org.gnome.settings-daemon.plugins.power sleep-inactive-battery-type 'nothing' org.gnome.settings-daemon.plugins.power sleep-inactive-battery-timeout 1200 org.gnome.desktop.screensaver ubuntu-lock-on-suspend true org.freedesktop.Tracker.Miner.Files initial-sleep 15 org.gnome.Music inhibit-suspend false Honestly what I'd really like to do, eventually, is plug my desktop back into the usbconnection that my UPS provides, and don't suspend while on battery power, but rather hibernate or shutdown cleanly when the battery power becomes critically low. I didn't put a lot of effort into this previously, but I was never able to get this working on previous versions of ubuntu. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubuntu-unity-desktop (not installed) ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Uname: Linux 5.4.0-33-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Jun 11 08:58:38 2020 SourcePackage: ubuntu-unity-meta UpgradeStatus: Upgraded to focal on 2020-06-01 (10 days ago) ** Affects: ubuntu Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ** Description changed: Before upgrading to 20.04 from 19.10 recently, my desktop would not automatically suspend when idle. After upgrading, it started suspending automatically. First thing I did was try to use the graphical configurator: but this continued to suspend. Then I started investigating gsettings: it turns out that the configurator was changing org.gnome.settings- daemon.plugins.power but not com.canonical.unity.settings- daemon.plugins.power. So the second time I changed the latter settings using the command line. Unless I'm mistaken, this appears to prevented my desktop from suspending as long as I don't lock the screen. However, if I lock the screen, then it continues to suspend itself even after my command-line attempt at disabling suspend. lpsmith@kleene:~$ gsettings list-recursively | grep -i "suspend\|sleep" org.cinnamon.desktop.keybindings.media-keys suspend ['XF86Sleep'] org.cinnamon.desktop.keybindings.media-keys hibernate
[Bug 1878670] Re: [Ice Lake] WARN_ON(intel_wait_for_register(dev_priv, regs->driver, (0x1 << ((pw_idx) * 2)), (0x1 << ((pw_idx) * 2)), 1)) [from i915/intel_runtime_pm.c:308]
** Also affects: linux-oem-osp1 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1878670 Title: [Ice Lake] WARN_ON(intel_wait_for_register(dev_priv, regs->driver, (0x1 << ((pw_idx) * 2)), (0x1 << ((pw_idx) * 2)), 1)) [from i915/intel_runtime_pm.c:308] To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1878670/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1878670] Re: [Ice Lake] i915 crashes in hsw_power_well_enable() from icl_tc_phy_aux_power_well_enable()
In Xorg.0.log, there is below error message: [29.334] (EE) modeset(0): [DRI2] No driver mapping found for PCI device 0x8086 / 0x9bf6 [29.334] (EE) modeset(0): Failed to initialize the DRI2 extension. After upgraded last kernel 5.0.0-1052-oem-osp1 and xserver-xorg-video- intel-hwe-18.04 2:2.99.917+git20171229-1ubuntu1~18.04.1, the error still exist. @Acelan, We need HWE's support if the driver is missed. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1878670 Title: [Ice Lake] i915 crashes in hsw_power_well_enable() from icl_tc_phy_aux_power_well_enable() To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1878670/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1878670] Re: [Ice Lake] i915 crashes in hsw_power_well_enable() from icl_tc_phy_aux_power_well_enable()
@Kurt, If you can not use the apport, do you mind to upload the output of sosreport. We need to remind you the sosreport will collect personal information. We need your help to upload below logs for us to debug, thank you: 1. /var/log/kern.log 2. /var/log/syslog 3. dpkg -l > dpkg-l.log 4. sosreport -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1878670 Title: [Ice Lake] i915 crashes in hsw_power_well_enable() from icl_tc_phy_aux_power_well_enable() To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1878670/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1878670] Re: [Ice Lake] i915 crashes in hsw_power_well_enable() from icl_tc_phy_aux_power_well_enable()
@Gilbertf, Could you use apport to file another new bug for tracing your bug? Let we focus on Mr. Kurt's bug on this bug, 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/1878670 Title: [Ice Lake] i915 crashes in hsw_power_well_enable() from icl_tc_phy_aux_power_well_enable() To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1878670/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1878670] Re: [Ice Lake] i915 crashes in hsw_power_well_enable() from icl_tc_phy_aux_power_well_enable()
@Gilbertf, I got a XPS 13 9300 (not sure it is the same SKU). I saw the i915 crashes dump, but I don't reproduce the xwindow crash issue. And, I tried the `apport-collect`, the apport-collect works well. We really need the information collected by apport, could you try to reinstall the apport and re-run the `apport-collect`? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1878670 Title: [Ice Lake] i915 crashes in hsw_power_well_enable() from icl_tc_phy_aux_power_well_enable() To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1878670/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1879014] [NEW] Trying to install Ubuntu for the first time.
Public bug reported: Trying to install Ubuntu for the first time. I keep getting ACPI errors, so I set ACPI to strict, and to off. Either way, I make to to the start of installing the OS, then it fails and doesn't give me any error code to search. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubiquity 20.04.15 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CasperVersion: 1.445 CurrentDesktop: ubuntu:GNOME Date: Fri May 15 20:28:56 2020 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed maybe-ubiquity quiet splash --- acpi=strict LiveMediaBuild: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcEnviron: LANGUAGE=en_US.UTF-8 PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 LC_NUMERIC=C.UTF-8 SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ubiquity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ubiquity-20.04.15 ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1879014 Title: Trying to install Ubuntu for the first time. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1879014/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1877814] [NEW] Lubuntu laptop fails to hybernate 20.04
Public bug reported: Laptop does not hybernate (HP Stream laptop) and following message is reported: [ 8028.414283] Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7 [ 8028.432816] Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7 ** Affects: perf-tools-unstable (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1877814 Title: Lubuntu laptop fails to hybernate 20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/perf-tools-unstable/+bug/1877814/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1875797] Re: [MIR] oem-somerville-melisa-meta
** Changed in: oem-priority Status: Invalid => New ** Changed in: ubuntu Status: Invalid => New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1875797 Title: [MIR] oem-somerville-melisa-meta To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1875797/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1876020] [NEW] Old IP does not go away
Public bug reported: Version: Description:Ubuntu 20.04 LTS Release:20.04 Codename: focal I have changed machine's IP from 192.168.4.55 to 192.168.4.5 in the netplan config file: leonbrag@minivm:/etc/network$ cat /etc/netplan/00-installer-config.yaml # This is the network config written by 'subiquity' network: version: 2 renderer: networkd ethernets: eth0: dhcp4: no addresses: [192.168.4.5/24] gateway4: 192.168.4.1 nameservers: addresses: [192.168.4.1] However old IP did not go away and machine can be pinged using old IP as well. leonbrag@minivm:/etc/network$ ip addr 1: lo: mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: eth0: mtu 1500 qdisc mq state UP group default qlen 1000 link/ether 00:15:5d:91:c9:00 brd ff:ff:ff:ff:ff:ff inet 192.168.4.5/24 brd 192.168.4.255 scope global eth0 valid_lft forever preferred_lft forever inet 192.168.4.55/24 brd 192.168.4.255 scope global secondary noprefixroute eth0 valid_lft forever preferred_lft forever inet6 2601:600:9480:1e4:6b2b:1db2:658b:e692/64 scope global dynamic mngtmpaddr noprefixroute valid_lft 2591616sec preferred_lft 604416sec inet6 2601:600:9480:1e4:215:5dff:fe91:c900/64 scope global dynamic mngtmpaddr noprefixroute valid_lft 2591616sec preferred_lft 604416sec inet6 fe80::215:5dff:fe91:c900/64 scope link valid_lft forever preferred_lft forever leonbrag@minivm:/etc/network$ machine was rebooted more then once. ** Affects: ubuntu Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1876020 Title: Old IP does not go away To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1876020/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1835660] Re: initramfs unpacking failed
regarding #58 - ignore the last line. That's a copy-paste fail on my part. Sorry. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1835660 Title: initramfs unpacking failed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1835660/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1835660] Re: initramfs unpacking failed
I've been experiencing this for several months now (not exactly sure when it started). For me, the error leads to a hard stop and the option to Ctrl-D to continue or ENTER for maintenance. I followed the process from #47 (Saroumane wrote on 2020-04-06:) Adding COMPRESS=gzip to /etc/initramfs-tools/initramfs.conf (instead of lz4) then: sudo update-grub;sudo update-initramfs -c -k all;sudo update-grub Reboot. Still got error message. I restored COMPRESS=lz4 then sudo update-grub;sudo update-initramfs -c -k all;sudo update-grub Reboot Still failed systemd-analyse says : Startup finished in 158us (firmware) + 568us (loader) + 2.027s (kernel) + 1min 31.97s (userspace) = 1min 33.999s graphical.target never reached I can eventually get back into the system through a combination of multiple reboots and dumb luck, but this is pretty annoying. I rebooted a 3rd time : no change, still no more Decoding errors. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1835660 Title: initramfs unpacking failed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1835660/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1875797] [NEW] [MIR] oem-somerville-melisa-meta
Public bug reported: [Availability] This is a pilot running meta package for https://wiki.ubuntu.com/MIRTeam/Exceptions/OEM that means the package doesn't exist in Debian or Ubuntu archive yet. oem-somerville-melisa-meta 20.04~ubuntu2 for focal in ppa:lihow731/staging-ubuntu-metapkg-ppa [Rationale] We want to improve the hardware support for Dell XPS 13 9300 on focal. [Security] No CVE/known security issue. [Quality assurance] I have used ppa:lihow731/staging-ubuntu-metapkg-ppa to check this package on Dell XPS 13 9300 and it works as expected. oem-somerville-melisa-meta will be upgraded to 20.04ubuntu2 from OEM archive. [Dependencies] It only depends on ubuntu-oem-keyring. [Standards compliance] This package should have met all requirements of https://wiki.ubuntu.com/MIRTeam/Exceptions/OEM. [Maintenance] Canonical OEM Enablement Team will take care of the maintenance. [Background information] Please check https://wiki.ubuntu.com/MIRTeam/Exceptions/OEM for details. Please use "oem-metapackage-mir-check" in lp:ubuntu-archive-tools to verify this MIR against the reference package in the archive. ** Affects: oem-priority Importance: High Assignee: Leon Liao (lihow731) Status: Invalid ** Affects: ubuntu Importance: Undecided Status: Invalid ** Changed in: oem-priority Status: New => Invalid ** Information type changed from Proprietary to Public ** Also affects: ubuntu Importance: Undecided Status: New ** Changed in: ubuntu Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1875797 Title: [MIR] oem-somerville-melisa-meta To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1875797/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 222126] Re: Partition Table is cleared during install on Intel Macs
Why is it still not fixed in Ubuntu Server 18.04? Is there ETA for a fix? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/222126 Title: Partition Table is cleared during install on Intel Macs To manage notifications about this bug go to: https://bugs.launchpad.net/grub-installer/+bug/222126/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1873369] [NEW] Python2 virtualenv installs broken pip command
Public bug reported: I've been contracted to upgrade some legacy systems to Python 3. I know Python 2 is EOL, but I do need to be able to run the old system under a virtualenv while I'm working on it. These are the steps I expect to work, and their erroneous output: $ sudo apt install python-virtualenv $ virtualenv -p python2 test2 $ cd test2 $ . bin/activate $ pip /home/leon/Temp/test2/lib/python2.7/site-packages/pkg_resources/py2_warn.py:22: UserWarning: Setuptools will stop working on Python 2 You are running Setuptools on Python 2, which is no longer supported and >>> SETUPTOOLS WILL STOP WORKING <<< in a subsequent release (no sooner than 2020-04-20). Please ensure you are installing Setuptools using pip 9.x or later or pin to `setuptools<45` in your environment. If you have done those things and are still encountering this message, please comment in https://github.com/pypa/setuptools/issues/1458 about the steps that led to this unsupported combination. sys.version_info < (3,) and warnings.warn(pre + "*" * 60 + msg + "*" * 60) Traceback (most recent call last): File "/home/leon/Temp/test2/bin/pip", line 5, in from pip._internal.cli.main import main File "/home/leon/Temp/test2/lib/python2.7/site-packages/pip/_internal/cli/main.py", line 10, in from pip._internal.cli.autocompletion import autocomplete File "/home/leon/Temp/test2/lib/python2.7/site-packages/pip/_internal/cli/autocompletion.py", line 9, in from pip._internal.cli.main_parser import create_main_parser File "/home/leon/Temp/test2/lib/python2.7/site-packages/pip/_internal/cli/main_parser.py", line 7, in from pip._internal.cli import cmdoptions File "/home/leon/Temp/test2/lib/python2.7/site-packages/pip/_internal/cli/cmdoptions.py", line 25, in from pip._internal.locations import USER_CACHE_DIR, get_src_prefix File "/home/leon/Temp/test2/lib/python2.7/site-packages/pip/_internal/locations.py", line 20, in from pip._internal.utils.compat import WINDOWS File "/home/leon/Temp/test2/lib/python2.7/site-packages/pip/_internal/utils/compat.py", line 29, in import ipaddr as ipaddress # type: ignore ImportError: No module named ipaddr ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: python-virtualenv 15.1.0+ds-2ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-24.28-generic 5.4.30 Uname: Linux 5.4.0-24-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Apr 17 11:06:19 2020 InstallationDate: Installed on 2020-01-11 (96 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) PackageArchitecture: all SourcePackage: python-virtualenv UpgradeStatus: Upgraded to focal on 2020-04-11 (5 days ago) ** Affects: python-virtualenv (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1873369 Title: Python2 virtualenv installs broken pip command To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-virtualenv/+bug/1873369/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1872861] Re: Sound applet won't change output device
** Description changed: Using the gnome-control-centre sound applet to change the output device from the motherboard's default to an external USB device used to work well on 19.10, but does not work on 20.04 Beta. I use a USB headphone DAC/amp on my desktop (Schiit Modi/Magni combo). Under Ubuntu 19.10 I could use the sound applet in the gnome-control- center to select either that USB device or basic audio through the HDMI cable on my monitor (it would always default to the basic audio on reboot, but that's another story) then use my headphones happily. Using Ubuntu 20.04 Beta the sound applet shows all of the expected devices, but choosing different devices has no effect - any music then played continues to come only from the monitor. Using the 'Test' button plays sound only through the monitor also. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-control-center 1:3.36.1-1ubuntu4 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Apr 15 11:44:27 2020 InstallationDate: Installed on 2020-01-11 (94 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) SourcePackage: gnome-control-center UpgradeStatus: Upgraded to focal on 2020-04-11 (3 days ago) In case this is useful at all, I've playing around on the command prompt:: - $ pactl list sinks short - 0 alsa_output.pci-_03_00.1.hdmi-stereo-extra3\ - module-alsa-card.c s16le 2ch 44100Hz SUSPENDED - 1 alsa_output.usb-Schiit_Schiit_USB_Audio_Device-00.iec958-stereo\ - module-alsa-card.c s16le 2ch 44100Hz SUSPENDED + $ pactl list sinks short + 0 alsa_output.pci-_03_00.1.hdmi-stereo-extra3\ + module-alsa-card.c s16le 2ch 44100Hz SUSPENDED + 1 alsa_output.usb-Schiit_Schiit_USB_Audio_Device-00.iec958-stereo\ + module-alsa-card.c s16le 2ch 44100Hz SUSPENDED - $ pacmd set-default-sink 1 - $ paplay Chicken\ Cluck.wav # Headphone output working! - $ pacmd set-default-sink 0 - $ paplay Chicken\ Cluck.wav # Monitor output + $ pacmd set-default-sink 1 + $ paplay Chicken\ Cluck.wav # Headphone output working! + $ pacmd set-default-sink 0 + $ paplay Chicken\ Cluck.wav # Monitor output Unfortunately, the command that let me listen to chickens on my headphones (pacmd set-default-sink 1) had no effect on sounds from the rest of the system (mpv and Rhythmbox tested). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1872861 Title: Sound applet won't change output device To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1872861/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1872861] Re: Sound applet won't change output device
** Description changed: Using the gnome-control-centre sound applet to change the output device from the motherboard's default to an external USB device used to work well on 19.10, but does not work on 20.04 Beta. I use a USB headphone DAC/amp on my desktop (Schiit Modi/Magni combo). Under Ubuntu 19.10 I could use the sound applet in the gnome-control- center to select either that USB device or basic audio through the HDMI cable on my monitor (it would always default to the basic audio on reboot, but that's another story) then use my headphones happily. Using Ubuntu 20.04 Beta the sound applet shows all of the expected devices, but choosing different devices has no effect - any music then played continues to come only from the monitor. Using the 'Test' button plays sound only through the monitor also. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-control-center 1:3.36.1-1ubuntu4 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Apr 15 11:44:27 2020 InstallationDate: Installed on 2020-01-11 (94 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) SourcePackage: gnome-control-center UpgradeStatus: Upgraded to focal on 2020-04-11 (3 days ago) + + In case this is useful at all, I've playing around on the command + prompt:: + + $ pactl list sinks short + 0 alsa_output.pci-_03_00.1.hdmi-stereo-extra3\ + module-alsa-card.c s16le 2ch 44100Hz SUSPENDED + 1 alsa_output.usb-Schiit_Schiit_USB_Audio_Device-00.iec958-stereo\ + module-alsa-card.c s16le 2ch 44100Hz SUSPENDED + + $ pacmd set-default-sink 1 + $ paplay Chicken\ Cluck.wav # Headphone output working! + $ pacmd set-default-sink 0 + $ paplay Chicken\ Cluck.wav # Monitor output + + Unfortunately, the command that let me listen to chickens on my + headphones (pacmd set-default-sink 1) had no effect on sounds from the + rest of the system (mpv and Rhythmbox tested). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1872861 Title: Sound applet won't change output device To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1872861/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1872861] [NEW] Sound applet won't change output device
Public bug reported: Using the gnome-control-centre sound applet to change the output device from the motherboard's default to an external USB device used to work well on 19.10, but does not work on 20.04 Beta. I use a USB headphone DAC/amp on my desktop (Schiit Modi/Magni combo). Under Ubuntu 19.10 I could use the sound applet in the gnome-control- center to select either that USB device or basic audio through the HDMI cable on my monitor (it would always default to the basic audio on reboot, but that's another story) then use my headphones happily. Using Ubuntu 20.04 Beta the sound applet shows all of the expected devices, but choosing different devices has no effect - any music then played continues to come only from the monitor. Using the 'Test' button plays sound only through the monitor also. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-control-center 1:3.36.1-1ubuntu4 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Apr 15 11:44:27 2020 InstallationDate: Installed on 2020-01-11 (94 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) SourcePackage: gnome-control-center UpgradeStatus: Upgraded to focal on 2020-04-11 (3 days ago) ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal third-party-packages -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1872861 Title: Sound applet won't change output device To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1872861/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1871563] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1871563/+attachment/5349395/+files/UdevDb.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1871563 Title: The window is frozen 3~10 seconds when swipe, pinch and zoom on the google-map via touchscreen for a while. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1871563/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1871563] Snap.Info.core18.txt
apport information ** Attachment added: "Snap.Info.core18.txt" https://bugs.launchpad.net/bugs/1871563/+attachment/5349393/+files/Snap.Info.core18.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1871563 Title: The window is frozen 3~10 seconds when swipe, pinch and zoom on the google-map via touchscreen for a while. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1871563/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1871563] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1871563/+attachment/5349388/+files/ProcModules.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1871563 Title: The window is frozen 3~10 seconds when swipe, pinch and zoom on the google-map via touchscreen for a while. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1871563/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1871563] Snap.Info.core.txt
apport information ** Attachment added: "Snap.Info.core.txt" https://bugs.launchpad.net/bugs/1871563/+attachment/5349392/+files/Snap.Info.core.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1871563 Title: The window is frozen 3~10 seconds when swipe, pinch and zoom on the google-map via touchscreen for a while. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1871563/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
