[Bug 1741074] Re: [snap] chrome-gnome-shell extension fails to detect native host connector
For Ubuntu 20.04, I have also noticed that both snap installed Chromium and Brave Web browsers fails to work with the gnome-shell-integration extension. In the case of Brave, this issue can be overcome by following their instruction on installing the .deb versions of brave-browser and brave-keyring files. $ sudo apt install apt-transport-https curl $ sudo curl -fsSLo /usr/share/keyrings/brave-browser-archive-keyring.gpg https://brave-browser-apt-release.s3.brave.com/brave-browser-archive-keyring.gpg $ echo "deb [signed-by=/usr/share/keyrings/brave-browser-archive-keyring.gpg arch=amd64] https://brave-browser-apt-release.s3.brave.com/ stable main"|sudo tee /etc/apt/sources.list.d/brave-browser-release.list $ sudo apt update $ sudo apt install brave-browser However, the chromium-browser does not have a .deb version to fix this issue. If one does issue the command: sudo apt install chromium-browser, this command will instead instruct snap to install chromium. Hope the Chromium developer community can fix this issue given it was first reported in 2018-01-03. Chroumium adoption would be made easier too. 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/1741074 Title: [snap] chrome-gnome-shell extension fails to detect native host connector To manage notifications about this bug go to: https://bugs.launchpad.net/keepassxc-snap/+bug/1741074/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1872950] Re: Nvidia 340.108 fails to install with kernels 5.5 onward
Some of the error Msg in nvidia-340.0.crash ProblemType: Package DKMSBuildLog: DKMS make.log for nvidia-340-340.108 for kernel 5.11.0-25-generic (x86_64) Mon 02 Aug 2021 04:20:03 PM +08 NVIDIA: calling KBUILD... make[1]: Entering directory '/usr/src/linux-headers-5.11.0-25-generic' test -e include/generated/autoconf.h -a -e include/config/auto.conf || ( \ echo >&2; \ echo >&2 " ERROR: Kernel configuration is invalid."; \ echo >&2 " include/generated/autoconf.h or include/config/auto.conf are missing.";\ echo >&2 " Run 'make oldconfig && make prepare' on kernel src to fix it."; \ echo >&2 ; \ /bin/false) make -f ./scripts/Makefile.build obj=/var/lib/dkms/nvidia-340/340.108/build \ single-build= \ . . . In file included from /var/lib/dkms/nvidia-340/340.108/build/nv-frontend.c:13: /var/lib/dkms/nvidia-340/340.108/build/nv-linux.h: At top level: /var/lib/dkms/nvidia-340/340.108/build/nv-linux.h:122:10: fatal error: asm/kmap_types.h: No such file or directory 122 | #include /* page table entry lookup */ | ^~ compilation terminated. make[2]: *** [scripts/Makefile.build:287: /var/lib/dkms/nvidia-340/340.108/build/nv-frontend.o] Error 1 make[2]: Target '__build' not remade because of errors. make[1]: *** [Makefile:1848: /var/lib/dkms/nvidia-340/340.108/build] Error 2 make[1]: Target 'modules' not remade because of errors. make[1]: Leaving directory '/usr/src/linux-headers-5.11.0-25-generic' NVIDIA: left KBUILD. nvidia.ko failed to build! make: *** [Makefile:202: nvidia.ko] Error 1 make: Target 'module' not remade because of errors. make: Entering directory '/var/lib/dkms/nvidia-340/340.108/build/uvm' cd ./..; make module SYSSRC=/lib/modules/5.11.0-25-generic/build SYSOUT=/lib/modules/5.11.0-25-generic/build KBUILD_EXTMOD=./.. make[1]: Entering directory '/var/lib/dkms/nvidia-340/340.108/build' NVIDIA: calling KBUILD... make[2]: Entering directory '/usr/src/linux-headers-5.11.0-25-generic' test -e include/generated/autoconf.h -a -e include/config/auto.conf || ( \ echo >&2; \ echo >&2 " ERROR: Kernel configuration is invalid."; \ echo >&2 " include/generated/autoconf.h or include/config/auto.conf are missing.";\ echo >&2 " Run 'make oldconfig && make prepare' on kernel src to fix it."; \ echo >&2 ; \ /bin/false) make -f ./scripts/Makefile.build obj=.. \ single-build= \ need-builtin=1 need-modorder=1 scripts/Makefile.build:44: ../Makefile: No such file or directory make[3]: *** No rule to make target '../Makefile'. Stop. make[2]: *** [Makefile:1848: ..] Error 2 make[2]: Leaving directory '/usr/src/linux-headers-5.11.0-25-generic' NVIDIA: left KBUILD. nvidia.ko failed to build! make[1]: *** [Makefile:202: nvidia.ko] Error 1 make[1]: Leaving directory '/var/lib/dkms/nvidia-340/340.108/build' make: *** [Makefile:222: ../Module.symvers] Error 2 make: Leaving directory '/var/lib/dkms/nvidia-340/340.108/build/uvm' DKMSKernelVersion: 5.11.0-25-generic Date: Mon Aug 2 16:20:23 2021 Package: nvidia-340 340.108-0ubuntu5.20.04.2 PackageVersion: 340.108-0ubuntu5.20.04.2 SourcePackage: nvidia-graphics-drivers-340 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1872950 Title: Nvidia 340.108 fails to install with kernels 5.5 onward To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1872950/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1872950] Re: Nvidia 340.108 fails to install with kernels 5.5 onward
@xnox The nvidia-340 driver can't seem to work with 5.11.0-25-generic that is presently used by Ubuntu Focal LTS. How should I resolve this issue? ~$ sudo dpkg --configure -a [sudo] password for master: Sorry, try again. [sudo] password for master: Setting up nvidia-340 (340.108-0ubuntu5.20.04.2) ... dpkg: error: version '-' has bad syntax: revision number is empty dpkg: error: version '-' has bad syntax: revision number is empty update-initramfs: deferring update (trigger activated) INFO:Enable nvidia-340 DEBUG:Parsing /usr/share/ubuntu-drivers-common/quirks/lenovo_thinkpad DEBUG:Parsing /usr/share/ubuntu-drivers-common/quirks/put_your_quirks_here DEBUG:Parsing /usr/share/ubuntu-drivers-common/quirks/dell_latitude Removing old nvidia-340-340.108 DKMS files... -- Deleting module version: 340.108 completely from the DKMS tree. -- Done. Loading new nvidia-340-340.108 DKMS files... Building for 5.11.0-25-generic Building for architecture x86_64 Building initial module for 5.11.0-25-generic ERROR: Cannot create report: [Errno 17] File exists: '/var/crash/nvidia-340.0.crash' Error! Bad return status for module build on kernel: 5.11.0-25-generic (x86_64) Consult /var/lib/dkms/nvidia-340/340.108/build/make.log for more information. dpkg: error processing package nvidia-340 (--configure): installed nvidia-340 package post-installation script subprocess returned error exit status 10 Processing triggers for libc-bin (2.31-0ubuntu9.2) ... Processing triggers for initramfs-tools (0.136ubuntu6.6) ... update-initramfs: Generating /boot/initrd.img-5.11.0-25-generic I: The initramfs will attempt to resume from /dev/nvme0n1p2 I: (UUID=107580ad-2775-4369-953e-7b873462c121) I: Set the RESUME variable to override this. Errors were encountered while processing: nvidia-340 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1872950 Title: Nvidia 340.108 fails to install with kernels 5.5 onward To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1872950/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1830914] Re: software-properties-gtk does not run at all!
I enquired about this issue in Aug 2020 (see https://askubuntu.com/q/1271611/541417). @SteveLanders solution worked for me. https://askubuntu.com/a/1312345/541417. The following reinstallation procedure that he had shared worked for me: sudo apt install --reinstall python3-six python3-certifi python3-requests python3-idna sudo apt install --reinstall software-properties-gtk software-properties-gtk -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1830914 Title: software-properties-gtk does not run at all! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1830914/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1769221] Re: "Switch User" fails, gives a blank screen with a mouse cursor.
*** This bug is a duplicate of bug 1766137 *** https://bugs.launchpad.net/bugs/1766137 ** Summary changed: - switching user fails + "Switch User" fails, gives a blank screen with a mouse cursor. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1769221 Title: "Switch User" fails, gives a blank screen with a mouse cursor. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1769221/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1769221] Re: switching user fails
*** This bug is a duplicate of bug 1766137 *** https://bugs.launchpad.net/bugs/1766137 On several occasions, when I click on "Switch User" I would be directed to a black screen with a mouse cursor where the mouse cursor may work in a very lagging manner and nothing else seems to work(no keyboard response). To get out of this situation, I needed to manually power off my system and power it up again to boot the system up again. This recovery procedure is bad for my system. Sometimes this bad situation happens and sometimes I would successfully be directed to the login screen to switch users successfully. Any idea what is causing this issue or how I can fix this issue? [Update:] On my next bootup, I re-tried using the "Switch User" button. I got the same black screen and mouse cursor. But this time around, the default Ubuntu screensaver or screen shield appeared ( after several seconds of delay) instead of the background that I had set previously. After pressing any keyboard key, the screen shield goes away and the Login screen appears. I am able to login as myself or as another user. It was mentioned here that this situation is a duplicate of bug #1766137 and in that report a fixed had already been issued. But I still encounter this issue. There I like to reopen this issue. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1769221 Title: "Switch User" fails, gives a blank screen with a mouse cursor. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1769221/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1841130] Re: idle, idle-python is missing from Apps Store
I think this issue is fixed. I can now find IDLE (using Python-3.6) in gnome-software. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1841130 Title: idle, idle-python is missing from Apps Store To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1841130/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1840398] Re: idle-python3.6 is not detectable by Ubuntu Software and does not appear in Nautilus
IDLE (using Python-3.6) can be found in gnome-software. But it cannot be found in Nautilus. Is it because of this issue? http://appstream.ubuntu.com/bionic/universe/issues/idle-python3.6.html? @Matthias Klumpp mentioned that Python upstream needs to add a metainfo file for IDLE (see https://bugs.launchpad.net/ubuntu/+source/gnome- software/+bug/1841130/comments/2) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1840398 Title: idle-python3.6 is not detectable by Ubuntu Software and does not appear in Nautilus To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python3.6/+bug/1840398/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1841130] Re: idle, idle-python is missing from Apps Store
@Matthias. In Ubuntu18.04, after pressing the "Super" key on the keyboard and typing "idle" in the search box, a python icon does appear. Also, after selecting it and python-idle does appear, in the dash-to- dock a different icon is used to represent python-idle. So there are available and suitable icons that can be used to represent python-idle. Since there are available icons for representing python-idle, can you tell me what must I do to point to these icons? Thanks. I don't recall having this issue in Ubuntu 16.04. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1841130 Title: idle, idle-python is missing from Apps Store To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1841130/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1840398] Re: idle-python3.6 is not detectable by Ubuntu Software and does not appear in Nautilus
All these packages are having the above mentioned issues: idle/bionic-updates,bionic-updates 3.6.7-1~18.04 all idle-python2.7/bionic-updates,bionic-updates,bionic-security,bionic-security 2.7.15-4ubuntu4~18.04 all idle-python3.6/bionic-updates,bionic-updates,bionic-security,bionic-security 3.6.8-1~18.04.1 all idle-python3.7/bionic-updates,bionic-updates,bionic-security,bionic-security 3.7.3-2~18.04.1 all idle3/bionic-updates,bionic-updates 3.6.7-1~18.04 all -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1840398 Title: idle-python3.6 is not detectable by Ubuntu Software and does not appear in Nautilus To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python3.6/+bug/1840398/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1743908] Re: MODSIGN: Couldn't get UEFI db list
Error "Couldn't get size: 0x800e" has resurfaced despite of the released fix. I found this error in latest Ubuntu 18.04 install. Release fix needs to be re-evaluated. $ dmesg . [0.933031] Loading compiled-in X.509 certificates [0.934003] Loaded X.509 cert 'Build time autogenerated kernel key: x...' [0.936201] Loaded UEFI:db cert 'ASUSTeK MotherBoard SW Key Certificate: x...' linked to secondary sys keyring [0.936320] Loaded UEFI:db cert 'ASUSTeK Notebook SW Key Certificate: x...' linked to secondary sys keyring [0.936331] Loaded UEFI:db cert 'Microsoft Corporation UEFI CA 2011: x...' linked to secondary sys keyring [0.936340] Loaded UEFI:db cert 'Microsoft Windows Production PCA 2011: x...' linked to secondary sys keyring [0.936461] Loaded UEFI:db cert 'Canonical Ltd. Master Certificate Authority: x...' linked to secondary sys keyring [0.936838] Couldn't get size: 0x800e [0.936839] MODSIGN: Couldn't get UEFI MokListRT $ uname -a Linux Machine 5.0.0-25-generic #26~18.04.1-Ubuntu SMP Thu Aug 1 13:51:02 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux $ dpkg -l | grep linux-generic-hwe- ii linux-generic-hwe-18.04 5.0.0.25.82 amd64 Complete Generic Linux kernel and headers $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 18.04.3 LTS Release: 18.04 Codename: bionic $ efibootmgr BootCurrent: Timeout: 1 seconds BootOrder: ,0001 Boot* ubuntu Boot0001* Hard Drive Fast Boot -- Disabled Secure Boot -- Disabled CSM -- Disabled -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1743908 Title: MODSIGN: Couldn't get UEFI db list To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1743908/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1841130] Re: idle, idle-python is missing from Apps Store
The question https://askubuntu.com/questions/1120736/idle-for-python-3-6 -cant-open-py-files-on-ubuntu-18-04 shows evidence that idle was available in App Store 6 months. Evidence seems to show this issue had occurred 1yr 3mths ago, The situation seem to have been fixed 6 mths ago, and presently the bug has re-occurred. Something causing this regression. Hope the cause of this issue can be discovered and nipped out soon. Thanks. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1841130 Title: idle, idle-python is missing from Apps Store To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1841130/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1841130] [NEW] idle, idle-python is missing from Apps Store
Public bug reported: The following packages cannot be found in the Apps Store in Ubuntu 18.04 and 19.04: idle/bionic-updates,bionic-updates 3.6.7-1~18.04 all idle-python2.7/bionic-updates,bionic-updates,bionic-security,bionic-security 2.7.15-4ubuntu4~18.04 all idle-python3.6/bionic-updates,bionic-updates,bionic-security,bionic-security 3.6.8-1~18.04.1 all idle-python3.7/bionic-updates,bionic-updates,bionic-security,bionic-security 3.7.3-2~18.04.1 all idle3/bionic-updates,bionic-updates 3.6.7-1~18.04 all They used to be available. These are default tools for python scripting and should be made available. $ uname -a Linux Machine 5.0.0-25-generic #26~18.04.1-Ubuntu SMP Thu Aug 1 13:51:02 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux $ dpkg -l | grep linux-generic-hwe- ii linux-generic-hwe-18.04 5.0.0.25.82amd64 Complete Generic Linux kernel and headers $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 18.04.3 LTS Release:18.04 Codename: bionic $ dpkg -l | grep ubuntu-software ii ubuntu-software3.28.1-0ubuntu4.18.04.10 all Utility for browsing, installing, and removing software $ dpkg -l | grep gnome-software ii gnome-software 3.28.1-0ubuntu4.18.04.10 amd64 Software Center for GNOME ii gnome-software-common 3.28.1-0ubuntu4.18.04.10all Software Center for GNOME (common files) ii gnome-software-plugin-snap 3.28.1-0ubuntu4.18.04.10 amd64 Snap support for GNOME Software $ grep -r --include '*.list' '^deb ' /etc/apt/sources.list /etc/apt/sources.list.d/ /etc/apt/sources.list:deb http://archive.ubuntu.com/ubuntu bionic main restricted /etc/apt/sources.list:deb http://archive.ubuntu.com/ubuntu bionic-updates main restricted /etc/apt/sources.list:deb http://archive.ubuntu.com/ubuntu bionic universe /etc/apt/sources.list:deb http://archive.ubuntu.com/ubuntu bionic-updates universe /etc/apt/sources.list:deb http://archive.ubuntu.com/ubuntu bionic multiverse /etc/apt/sources.list:deb http://archive.ubuntu.com/ubuntu bionic-updates multiverse /etc/apt/sources.list:deb http://archive.ubuntu.com/ubuntu bionic-backports main restricted universe multiverse /etc/apt/sources.list:deb http://archive.canonical.com/ubuntu bionic partner /etc/apt/sources.list:deb http://archive.ubuntu.com/ubuntu bionic-security main restricted /etc/apt/sources.list:deb http://archive.ubuntu.com/ubuntu bionic-security universe /etc/apt/sources.list:deb http://archive.ubuntu.com/ubuntu bionic-security multiverse https://askubuntu.com/questions/1167734/where-is-idle-python3-6 Asked today https://askubuntu.com/questions/1057574/software-centre-how-does-it-choose-what-to-show Asked 1 year, 1 month ago https://askubuntu.com/questions/1029872/where-is-idle-18-04 Asked 1 year, 3 months ago ** Affects: gnome-software (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/1841130 Title: idle, idle-python is missing from Apps Store To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1841130/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1840890] [NEW] PKCS#7 signature not signed with a trusted key
Public bug reported: After making nvidia drivers available in Ubuntu 18.04 via Ubuntu's StableReleaseUpdates (SRU), I expected that all the usual error and warning messages reported by `dmesg -l err` and `dmes -l warn` before the nvidia drivers's transition to SRU should no longer appear. However, I still find them. See below. $ dmesg -l err [2.322549] PKCS#7 signature not signed with a trusted key [2.438684] PKCS#7 signature not signed with a trusted key [2.439332] PKCS#7 signature not signed with a trusted key [2.439727] PKCS#7 signature not signed with a trusted key [2.445846] PKCS#7 signature not signed with a trusted key $ dmesg -l warn [2.322558] nvidia: loading out-of-tree module taints kernel. [2.322565] nvidia: module license 'NVIDIA' taints kernel. [2.322566] Disabling lock debugging due to kernel taint [2.433159] NVRM: loading NVIDIA UNIX x86_64 Kernel Module 430.26 Tue Jun 4 17:40:52 CDT 2019 Expected outcome: The above error and warning msgs should no longer show in dmesg. $ uname -a Linux Machine 5.0.0-25-generic #26~18.04.1-Ubuntu SMP Thu Aug 1 13:51:02 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux $ dpkg -l | grep nvidia ii libnvidia-cfg1-430:amd64 430.26-0ubuntu0.18.04.2 amd64NVIDIA binary OpenGL/GLX configuration library ii libnvidia-common-430 430.40-0ubuntu0~gpu18.04.1 all Shared files used by the NVIDIA libraries ii libnvidia-compute-430:amd64430.26-0ubuntu0.18.04.2 amd64NVIDIA libcompute package ii libnvidia-compute-430:i386 430.26-0ubuntu0.18.04.2 i386 NVIDIA libcompute package ii libnvidia-decode-430:amd64 430.26-0ubuntu0.18.04.2 amd64NVIDIA Video Decoding runtime libraries ii libnvidia-decode-430:i386 430.26-0ubuntu0.18.04.2 i386 NVIDIA Video Decoding runtime libraries ii libnvidia-encode-430:amd64 430.26-0ubuntu0.18.04.2 amd64NVENC Video Encoding runtime library ii libnvidia-encode-430:i386 430.26-0ubuntu0.18.04.2 i386 NVENC Video Encoding runtime library ii libnvidia-fbc1-430:amd64 430.26-0ubuntu0.18.04.2 amd64NVIDIA OpenGL-based Framebuffer Capture runtime library ii libnvidia-fbc1-430:i386430.26-0ubuntu0.18.04.2 i386 NVIDIA OpenGL-based Framebuffer Capture runtime library ii libnvidia-gl-430:amd64 430.26-0ubuntu0.18.04.2 amd64NVIDIA OpenGL/GLX/EGL/GLES GLVND libraries and Vulkan ICD ii libnvidia-gl-430:i386 430.26-0ubuntu0.18.04.2 i386 NVIDIA OpenGL/GLX/EGL/GLES GLVND libraries and Vulkan ICD ii libnvidia-ifr1-430:amd64 430.26-0ubuntu0.18.04.2 amd64NVIDIA OpenGL-based Inband Frame Readback runtime library ii libnvidia-ifr1-430:i386430.26-0ubuntu0.18.04.2 i386 NVIDIA OpenGL-based Inband Frame Readback runtime library ii nvidia-compute-utils-430 430.26-0ubuntu0.18.04.2 amd64NVIDIA compute utilities ii nvidia-dkms-430430.26-0ubuntu0.18.04.2 amd64NVIDIA DKMS package ii nvidia-driver-430 430.26-0ubuntu0.18.04.2 amd64NVIDIA driver metapackage ii nvidia-kernel-common-430 430.26-0ubuntu0.18.04.2 amd64Shared files used with the kernel module ii nvidia-kernel-source-430 430.26-0ubuntu0.18.04.2 amd64NVIDIA kernel source package ii nvidia-prime 0.8.8.2 all Tools to enable NVIDIA's Prime ii nvidia-settings390.77-0ubuntu0.18.04.1 amd64Tool for configuring the NVIDIA graphics driver ii nvidia-utils-430 430.26-0ubuntu0.18.04.2 amd64NVIDIA driver support binaries ii xserver-xorg-video-nvidia-430 430.26-0ubuntu0.18.04.2 amd64NVIDIA binary Xorg driver ** Affects: nvidia-graphics-drivers-430 (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/1840890 Title: PKCS#7 signature not signed with a trusted key To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-430/+bug/1840890/+subscr
[Bug 1727908] Re: Software & Updates application does not permit changes on the "Other Software" tab
I discovered that the Software & Updates application "Authentication" tab's "Remove" button does not work properly too. After pressing the "Remove" button, pkexec was called. After submitting the password for administration level, nothing happens, i.e. Trusted software keys that was selected for deletion do not get removed. Not error was shown in terminal. $ dpkg -l | grep software-properties ii python3-software-properties0.96.24.32.11 all manage the repositories that you install software from ii software-properties-common 0.96.24.32.11 all manage the repositories that you install software from (common) ii software-properties-gtk0.96.24.32.11 all manage the repositories that you install software from (gtk) I had filed a bug report (see https://bugs.launchpad.net/ubuntu/+source /software-properties/+bug/1840624). Should it fall under this bug report too and this bug report's title be amended to include the "Authentication" Tab? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1727908 Title: Software & Updates application does not permit changes on the "Other Software" tab To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1727908/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1840624] [NEW] Ubuntu 18.04: Can't remove software key via software-properties package GUI
Public bug reported: I have these packages installed: ii python3-software-properties0.96.24.32.11 all manage the repositories that you install software from ii software-properties-common 0.96.24.32.11 all manage the repositories that you install software from (common) ii software-properties-gtk0.96.24.32.11 all manage the repositories that you install software from (gtk) However, after calling out `Software & Updates` GUI and clicking the `Authenication` tab, I found the `Remove` button there does not work. It does not delete any trusted software keys. I had to resort to using cli cmds as given in https://askubuntu.com/questions/107177/how-can-i -remove-gpg-key-that-i-added-using-apt-key-add/846877#846877 to remove any trusted software keys. The 'Remove' button needs to work; it needs to be fixed. **System information:** $ lsb_release -rd Description: Ubuntu 18.04.3 LTS Release: 18.04 $ uname -a Linux Machine 5.0.0-25-generic #26~18.04.1-Ubuntu SMP Thu Aug 1 13:51:02 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux ** Affects: software-properties (Ubuntu) Importance: Undecided Status: New ** Summary changed: - Can't remove software key via its GUI + Can't remove software key via software-properties package GUI ** Summary changed: - Can't remove software key via software-properties package GUI + Ubuntu 18.04: Can't remove software key via software-properties package GUI -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1840624 Title: Ubuntu 18.04: Can't remove software key via software-properties package GUI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1840624/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1837326] Re: platform eisa.0: EISA: Cannot allocate resource for mainboard
Ubuntu 18.04 also need a fix for this bug. [0.884817] usb: port power management may be unreliable [0.889745] platform eisa.0: EISA: Cannot allocate resource for mainboard [0.889746] platform eisa.0: Cannot allocate resource for EISA slot 1 [0.889746] platform eisa.0: Cannot allocate resource for EISA slot 2 [0.889747] platform eisa.0: Cannot allocate resource for EISA slot 3 [0.889747] platform eisa.0: Cannot allocate resource for EISA slot 4 [0.889748] platform eisa.0: Cannot allocate resource for EISA slot 5 [0.889748] platform eisa.0: Cannot allocate resource for EISA slot 6 [0.889749] platform eisa.0: Cannot allocate resource for EISA slot 7 [0.889749] platform eisa.0: Cannot allocate resource for EISA slot 8 $ uname -a Linux Machine 5.0.0-25-generic #26~18.04.1-Ubuntu SMP Thu Aug 1 13:51:02 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux $ lsb_release -rd Description:Ubuntu 18.04.3 LTS Release:18.04 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1837326 Title: platform eisa.0: EISA: Cannot allocate resource for mainboard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1837326/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1553802] Re: Date and time jump around on locked screen when showing seconds (and also sometimes display strange shadows behind them)
:) All the more reason for Ubuntu 18.04 to receive the fix? Any timeline planned? My bad for mixing 16.04 end of life with 18.04. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1553802 Title: Date and time jump around on locked screen when showing seconds (and also sometimes display strange shadows behind them) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1553802/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1553802] Re: Date and time jump around on locked screen when showing seconds (and also sometimes display strange shadows behind them)
Any chance that this bug will be fixed for Ubuntu 18.04? It still has about 1.5 years of support life to it? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1553802 Title: Date and time jump around on locked screen when showing seconds (and also sometimes display strange shadows behind them) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1553802/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1553802] Re: Date and time jump around on locked screen when showing seconds (and also sometimes display strange shadows behind them)
I would like to nominate the fix be made available to Ubuntu 18.04. It seems strange the fix isn't made available to a LTS version which is more highly used than a .10 version. I tried pressing the nomination button, but it complained that: "You do not have permission to nominate this bug." I had filed a similar bug report here https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1840265. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1553802 Title: Date and time jump around on locked screen when showing seconds (and also sometimes display strange shadows behind them) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1553802/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1840398] [NEW] idle-python3.6 is not detectable by Ubuntu Software and does not appear in Nautilus
Public bug reported: idle-python3.6 is not detectable by Ubuntu Software nor is it detectable by Nautilus as an application that can be used to open .py files. This should not be the case. It used to be available in Ubuntu 16.04.Users will need these features to improve work productivity. **System information:** $ lsb_release -rd Description: Ubuntu 18.04.3 LTS Release: 18.04 $ uname -a Linux Machine 5.0.0-25-generic #26~18.04.1-Ubuntu SMP Thu Aug 1 13:51:02 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux $ apt-cache policy idle-python3.6 idle-python3.6: Installed: 3.6.8-1~18.04.1 Candidate: 3.6.8-1~18.04.1 Version table: *** 3.6.8-1~18.04.1 500 500 http://sg.archive.ubuntu.com/ubuntu bionic-updates/universe amd64 Packages 500 http://sg.archive.ubuntu.com/ubuntu bionic-updates/universe i386 Packages 100 /var/lib/dpkg/status 3.6.5-3 500 500 http://sg.archive.ubuntu.com/ubuntu bionic/universe amd64 Packages 500 http://sg.archive.ubuntu.com/ubuntu bionic/universe i386 Packages ** Affects: python3.6 (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/1840398 Title: idle-python3.6 is not detectable by Ubuntu Software and does not appear in Nautilus To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python3.6/+bug/1840398/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1727908] Re: Software & Updates application does not permit changes on the "Other Software" tab
I encountered this same issue in a freshly installed Ubuntu 18.04 system. $ uname -a Linux Machine 5.0.0-25-generic #26~18.04.1-Ubuntu SMP Thu Aug 1 13:51:02 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux $ lsb_release -rd Description:Ubuntu 18.04.3 LTS Release:18.04 $ gnome-shell --version GNOME Shell 3.28.4 To discover the error, I ran this app via command line: $ /usr/bin/python3 /usr/bin/software-properties-gtk ERROR:root:Authentication canceled, changes have not been saved ERROR:root:Authentication canceled, changes have not been saved ERROR:root:Authentication canceled, changes have not been saved ERROR:root:Authentication canceled, changes have not been saved ERROR:root:Authentication canceled, changes have not been saved ERROR:root:Authentication canceled, changes have not been saved The above errors appear every time the mouse arrow left-clicks on the checkbox. I circumvent this issue by: 1. left-click on Canonical Partners to select it. 2. left click on the edit button. 3. after the Edit Source GUI appeared, I left-clicked on the "OK" button. 4. finally when I left-click on the checkbox of Canonical Partners, the checkbox becomes selected. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1727908 Title: Software & Updates application does not permit changes on the "Other Software" tab To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1727908/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1840265] Re: "Date" in Ubuntu 18.04 Lock Screen is not always center aligned when "Tweaks-->Top Bar-->Seconds" is set to be "True".
** Summary changed: - "Date" in Ubuntu 18.04 Lock Screen is not always center aligned. + "Date" in Ubuntu 18.04 Lock Screen is not always center aligned when "Tweaks-->Top Bar-->Seconds" is set to be "True". -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1840265 Title: "Date" in Ubuntu 18.04 Lock Screen is not always center aligned when "Tweaks-->Top Bar-->Seconds" is set to be "True". To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1840265/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1840265] Re: "Date" in Ubuntu 18.04 Lock Screen is not always center aligned.
I discovered the trigger for the misalignment, i.e. it occurs when `Tweaks-->Top Bar-->Seconds` is set to be `True`. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1840265 Title: "Date" in Ubuntu 18.04 Lock Screen is not always center aligned when "Tweaks-->Top Bar-->Seconds" is set to be "True". To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1840265/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1840265] [NEW] "Date" in Ubuntu 18.04 Lock Screen is not always center aligned.
Public bug reported:
Issue:
In Ubuntu 18.04, there appears to be an issue with the alignment of the
shown "Date" in the locked screen, i.e. `.screen-shield-clock-date{}` in
`/usr/share/gnome-shell/theme/ubuntu.css`. It sometimes appear center-
aligned and sometimes left-aligned w.r.t `.screen-shield-clock{}`. It
seems that `.screen-shield-clock-date{}` is a child of
.screen-shield-clock {
color: white;
text-shadow: 0px 1px 2px rgba(0, 0, 0, 0.6);
font-weight: bold;
text-align: center;
padding-bottom: 1.5em; }
which already contains the `text-align: center` argument to require center
alignment.
I have tried adding `margin: auto; width: 100%;` in both
`.screen-shield-clock{}` and `.screen-shield-clock-date{}`, and also adding
`text-align: center` in `.screen-shield-clock-date{}` but these approaches
don't seem to work?
How can a user fix this date alignment issue or is this a bug with gdm3?
**System information:**
$ lsb_release -rd
Description:Ubuntu 18.04.3 LTS
Release:18.04
$ dpkg -l | grep gdm
ii gdm3 3.28.3-0ubuntu18.04.4 amd64 GNOME Display Manager
ii gir1.2-gdm-1.0 3.28.3-0ubuntu18.04.4 amd64 GObject introspection
data for the GNOME Display Manager
ii libgdm13.28.3-0ubuntu18.04.4 amd64 GNOME Display Manager
(shared library)
$ apt-cache policy gdm3
gdm3:
Installed: 3.28.3-0ubuntu18.04.4
Candidate: 3.28.3-0ubuntu18.04.4
Version table:
*** 3.28.3-0ubuntu18.04.4 500
500 http://sg.archive.ubuntu.com/ubuntu bionic-updates/main amd64
Packages
500 http://security.ubuntu.com/ubuntu bionic-security/main amd64
Packages
100 /var/lib/dpkg/status
3.28.0-0ubuntu1 500
500 http://sg.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
$ apt-cache policy gir1.2-gdm-1.0
gir1.2-gdm-1.0:
Installed: 3.28.3-0ubuntu18.04.4
Candidate: 3.28.3-0ubuntu18.04.4
Version table:
*** 3.28.3-0ubuntu18.04.4 500
500 http://sg.archive.ubuntu.com/ubuntu bionic-updates/main amd64
Packages
500 http://security.ubuntu.com/ubuntu bionic-security/main amd64
Packages
100 /var/lib/dpkg/status
3.28.0-0ubuntu1 500
500 http://sg.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
$ apt-cache policy libgdm1
libgdm1:
Installed: 3.28.3-0ubuntu18.04.4
Candidate: 3.28.3-0ubuntu18.04.4
Version table:
*** 3.28.3-0ubuntu18.04.4 500
500 http://sg.archive.ubuntu.com/ubuntu bionic-updates/main amd64
Packages
500 http://security.ubuntu.com/ubuntu bionic-security/main amd64
Packages
100 /var/lib/dpkg/status
3.28.0-0ubuntu1 500
500 http://sg.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
** Affects: gdm3 (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1840265
Title:
"Date" in Ubuntu 18.04 Lock Screen is not always center aligned.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1840265/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1807416] Re: secureboot: Secure boot could not be determined (mode 0)
I see the same in Ubuntu 18.04.2. $ dmesg -l warn | grep secureboot [0.00] secureboot: Secure boot could not be determined (mode 0) $ uname -rv 4.18.0-17-generic #18~18.04.1-Ubuntu SMP Fri Mar 15 15:27:12 UTC 2019 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1807416 Title: secureboot: Secure boot could not be determined (mode 0) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1807416/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1644498] Re: apt-get update returns "AppStream cache update completed, but some metadata was ignored due to errors." periodically
My system had the following packages upgraded: Upgrade: linux-headers-generic:amd64 (4.4.0.130.136, 4.4.0.131.137), linux-libc-dev:amd64 (4.4.0-130.156, 4.4.0-131.157), linux-image- generic:amd64 (4.4.0.130.136, 4.4.0.131.137), linux-generic:amd64 (4.4.0.130.136, 4.4.0.131.137) After that, there were errors again whenever I did `sudo apt update`. I opened `/var/cache/app-info/xmls/fwupd.xml` as `sudo`, went to line 256 and changed symbol `&` to `&`, saved the changes, and ran command `sudo appstreamcli refresh --force`. Thereafter, no errors appeared during `sudo apt update`. W/o running command `sudo appstreamcli refresh --force` the error persisted. Hope this finding will be helpful to others in the same situation. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1644498 Title: apt-get update returns "AppStream cache update completed, but some metadata was ignored due to errors." periodically To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/appstream/+bug/1644498/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1644498] Re: apt-get update returns "AppStream cache update completed, but some metadata was ignored due to errors." periodically
I am encountering the same after sudo apt update. . AppStream system cache was updated, but problems were found: Metadata files have errors: /var/cache/app-info/xmls/fwupd.xml Reading package lists... Done E: Problem executing scripts APT::Update::Post-Invoke-Success 'if /usr/bin/test -w /var/cache/app-info -a -e /usr/bin/appstreamcli; then appstreamcli refresh-cache > /dev/null; fi' E: Sub-process returned an error code After reading the solution from https://askubuntu.com/a/1053844/541417, I did the following: 1. Backed up `fwupd.xml` and `50appstream`. 2. Performed the procedure mentioned in the link. I found the above mentioned errors disappeared during `sudo apt update` (tested for a few reboots). 3. I reinserted `50appstream` to it's original location, ran `sudo appstreamcli refresh --force` followed by `sudo apt update`; no error msg appeared. 4. After reinserting `fwupd.xml` to its original location, and running `sudo appstreamcli refresh --force` followed by `sudo apt update`, I found the above mentioned error reappearing. Specifically, `AppStream system cache was updated, but problems were found: Metadata files have errors: /var/cache/app-info/xmls/fwupd.xml.` So `fwupd.xml` really caused the error. Opening the file, the document mentioned the error was in line 265. Reading https://askubuntu.com/a/1053018/541417 and https://github.com/hughsie /8bitdo-firmware/commit/7b8eff0c8bb75336c6fd8aca13f9f5093abc5fd7#diff- 81541301f84363c9ec1c910b8b45cdb8R32. I concluded the issue is really caused by the typo in line 265 of `fwupd.xml`. Need to change to . That is symbol `&` should change to `&`. Then save the file. After this fix, when I run 'sudo apt update', every thing works again. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1644498 Title: apt-get update returns "AppStream cache update completed, but some metadata was ignored due to errors." periodically To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/appstream/+bug/1644498/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1400470] Re: cannot download photos using shotwell via usb
I see the following message from Shotwell 0.22.0 in Ubuntu 16.04 every time a iPhone4s is plugged in to my computer usb: Shotwell Unable to fetch previews from the camera: Could not claim the USB device (-53) I have to click "Ok" to remove this message before I can access Shotwell. This warning has always appeared for a few years. Annoying. It will be great that this warning be removed. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1400470 Title: cannot download photos using shotwell via usb To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shotwell/+bug/1400470/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1776145] [NEW] Transition Up issue
Public bug reported: I noticed that there is an issue for a transition that is applied from a lower track to an upper track direction. The image in the lower track will always reappear at the end of the applied transition. That means the image in the lower track first appears. During transition, the image in the lower track changes to the image in the upper track. However, at the end of the transition, the image in the lower track will reappear and then it disappears the and image in the upper track will reappear again. Even if I make the transition duration surpass the end of the image in the lower track, this issue cannot be resolved. This issue did not occur for transitions in the "down" direction. This is a bug in Openshot 1.4.3 that I hope it can be fixed. Cheers ** Affects: openshot (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/1776145 Title: Transition Up issue To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openshot/+bug/1776145/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1074035] Re: openshot crashes on startup with "cannot import name main"
I have similar issue on when starting Openshot on terminal in Ubuntu
16.04.4.
In addition, there is also a mlt_repository_init failure.
However, Openshot does start up and can be used. Also, Openshot can be started
from Ubuntu 16.04 GUI Icon.
Error:
$ openshot
Added /usr/share/openshot to system path
- ERROR 1 --
Failed to import 'from openshot import main'
Error Message: cannot import name main
OpenShot (version 1.4.3)
mlt_repository_init: failed to dlopen /usr/lib/x86_64-linux-gnu/mlt/libmltqt.so
(/usr/lib/x86_64-linux-gnu/libQt5Xml.so.5: undefined symbol:
_ZNK7QString10startqWithE5QCharN2Qt35CaseSelsitivit{E)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1074035
Title:
openshot crashes on startup with "cannot import name main"
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openshot/+bug/1074035/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 988224] Re: Exported webm/ogg videos are shorter than original
I have exported a 7 mins Openshot video project to webm, ogg, and mov(mp4) formats. mov video was stable. size 775MB ogg video had some audio shuttering. size 687MB webm video had large sections missing. size 219MB I concur with @DavidPlanella observation that there are issues with exporting to webm and ogg formats. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/988224 Title: Exported webm/ogg videos are shorter than original To manage notifications about this bug go to: https://bugs.launchpad.net/openshot/+bug/988224/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1758681] [NEW] sqlitebrowser Segmentation fault (core dumped)
Public bug reported: After installing sqlitebrowser, I tried to launch it by clicking on it's icon and nothing happens. I then opened a terminal to launch it but instead of seeing the launched application I see nothing except the following in the terminal $ sqlitebrowser Segmentation fault (core dumped) Pls advise what is the issue and how to fix it. Thanks. $ lsb_release -rd Description:Ubuntu 16.04.4 LTS Release:16.04 $ dpkg -l | grep sqlitebrowser ii sqlitebrowser3.7.0-1amd64GUI editor for SQLite databases ** Affects: sqlitebrowser (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/1758681 Title: sqlitebrowser Segmentation fault (core dumped) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sqlitebrowser/+bug/1758681/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1577168] Re: Browser hangs Ubuntu 16.04
Previous error was from pressing the Browser Application button on Unity. Below are the errors from running Browser from terminal. So many errors. ~$ webbrowser-app (webbrowser-app:6684): dconf-CRITICAL **: unable to create file '/run/user/1000/dconf/user': Permission denied. dconf will not work properly. (webbrowser-app:6684): dconf-CRITICAL **: unable to create file '/run/user/1000/dconf/user': Permission denied. dconf will not work properly. (webbrowser-app:6684): dconf-CRITICAL **: unable to create file '/run/user/1000/dconf/user': Permission denied. dconf will not work properly. unity::action::ActionManager::ActionManager(QObject*): Could not determine application identifier. HUD will not work properly. Provide your application identifier in $APP_ID environment variable. UCUriHandler: Empty "APP_ID" environment variable, ignoring. file:///usr/share/webbrowser-app/webbrowser/ContentPickerDialog.qml:22:1: module "Ubuntu.Content" is not installed file:///usr/share/webbrowser-app/webbrowser/ContentDownloadDialog.qml:22:1: module "Ubuntu.Content" is not installed file:///usr/share/webbrowser-app/ContentHandler.qml:20:1: module "Ubuntu.Content" is not installed file:///usr/share/webbrowser-app/webbrowser/DownloadHandler.qml:20:1: module "Ubuntu.DownloadManager" is not installed (webbrowser-app:6684): IBUS-WARNING **: Unable to connect to ibus: Could not connect: Permission denied [0102/085135.047971:ERROR:oxide_qt_gl_context_dependent.cc(82)] Unable to create adopted GL context for platform: xcb - unexpected result from QPlatformNativeInterface::nativeResourceForContext (webbrowser-app:6684): dconf-CRITICAL **: unable to create file '/run/user/1000/dconf/user': Permission denied. dconf will not work properly. (webbrowser-app:6684): dconf-CRITICAL **: unable to create file '/run/user/1000/dconf/user': Permission denied. dconf will not work properly. (webbrowser-app:6684): dconf-CRITICAL **: unable to create file '/run/user/1000/dconf/user': Permission denied. dconf will not work properly. (webbrowser-app:6684): dconf-CRITICAL **: unable to create file '/run/user/1000/dconf/user': Permission denied. dconf will not work properly. (webbrowser-app:6684): dconf-CRITICAL **: unable to create file '/run/user/1000/dconf/user': Permission denied. dconf will not work properly. (webbrowser-app:6684): dconf-CRITICAL **: unable to create file '/run/user/1000/dconf/user': Permission denied. dconf will not work properly. (webbrowser-app:6684): dconf-CRITICAL **: unable to create file '/run/user/1000/dconf/user': Permission denied. dconf will not work properly. (webbrowser-app:6684): dconf-CRITICAL **: unable to create file '/run/user/1000/dconf/user': Permission denied. dconf will not work properly. (webbrowser-app:6684): dconf-CRITICAL **: unable to create file '/run/user/1000/dconf/user': Permission denied. dconf will not work properly. (webbrowser-app:6684): dconf-CRITICAL **: unable to create file '/run/user/1000/dconf/user': Permission denied. dconf will not work properly. shm_open() failed: Permission denied (webbrowser-app:6684): dconf-CRITICAL **: unable to create file '/run/user/1000/dconf/user': Permission denied. dconf will not work properly. (webbrowser-app:6684): dconf-CRITICAL **: unable to create file '/run/user/1000/dconf/user': Permission denied. dconf will not work properly. (webbrowser-app:6684): dconf-CRITICAL **: unable to create file '/run/user/1000/dconf/user': Permission denied. dconf will not work properly. [0102/085135.153682:ERROR:gl_context_glx.cc(196)] Failed to create GL context with glXCreateContextAttribsARB. [0102/085135.153701:ERROR:gpu_info_collector.cc(50)] gl::init::CreateGLContext failed [0102/085135.153706:ERROR:gpu_info_collector.cc(118)] Could not create context for info collection. [0102/085135.153713:ERROR:oxide_browser_main_parts.cc(327)] gpu::CollectContextGraphicsInfo failed [0102/085135.228622:ERROR:gl_context_glx.cc(196)] Failed to create GL context with glXCreateContextAttribsARB. [0102/085135.228648:ERROR:gpu_info_collector.cc(50)] gl::init::CreateGLContext failed [0102/085135.228651:ERROR:gpu_info_collector.cc(118)] Could not create context for info collection. [0102/085135.229021:ERROR:child_thread_impl.cc(762)] Request for unknown Channel-associated interface: ui::mojom::GpuMain qml: Loaded 8 UA override(s) from file:///usr/lib/x86_64-linux-gnu/qt5/qml/Ubuntu/Web/ua-overrides-mobile.js OxideQQuickWebView: canGoForward is deprecated. Please use the API provided by OxideQQuickNavigationHistory instead OxideQQuickWebView: canGoBack is deprecated. Please use the API provided by OxideQQuickNavigationHistory instead TouchSelectionController::active is deprecated, use TouchSelectionController::status instead file:///usr/share/webbrowser-app/Downloader.qml:23:1: module "Ubuntu.Content" is not installed file:///usr/share/webbrowser-app/Downloader.qml:22:1: module "Ubuntu.DownloadManager" is not install
[Bug 1726851] Re: Unable to install Ubuntu 16.04.3
I have recreated the installer several times. Check disc always report there is 1 error. Do not know why this is the case. I have made several attempts making a USB installer and several DVD installers. Check disk on all these installer reported there is one error. 1st time to have so much difficulties making an installer. How do I overcome these issues? Prior to recreating the installer, Ubuntu 16.04.3 was downloaded from https://www.ubuntu.com/download/desktop/thank- you?country=SG&version=16.04.3&architecture=amd64 and I have performed all the verification steps mentioned in https://tutorials.ubuntu.com/tutorial/tutorial-how-to-verify- ubuntu?_ga=2.6684148.713873019.1510186123-1841260143.1510186123#0 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1726851 Title: Unable to install Ubuntu 16.04.3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1726851/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1726809] Re: Vulkan does not work on nvidia-384 due to incorrect nvidia_icd.json
Thanks for posting the solution to the typo. Gratitude kudos Alex (and anyone else if you have contributed to this solution). I found the file /usr/share/vulkan/icd.d/nvidia_icd.json and from it replaced the string "libGL.so.1" with "libGLX_nvidia.so.0" and Vulkan works again. My system had upgraded to this driver at the start of this week. I had a new system installed 1 day ago and have the same issue. Hope the Maintainer can quickly correct the typo to avoid unnecessary user panic attacks. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1726809 Title: Vulkan does not work on nvidia-384 due to incorrect nvidia_icd.json To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-384/+bug/1726809/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1726851] [NEW] Unable to install Ubuntu 16.04.3
Public bug reported: Unable to install Ubuntu 16.04.3 on NVME ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: ubiquity 2.21.63.4 [modified: lib/partman/automatically_partition/question] ProcVersionSignature: Ubuntu 4.10.0-28.32~16.04.2-generic 4.10.17 Uname: Linux 4.10.0-28-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 CasperVersion: 1.376.2 Date: Tue Oct 24 20:38:56 2017 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi file=/cdrom/preseed/ubuntu.seed boot=casper only-ubiquity quiet splash --- LiveMediaBuild: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) ProcEnviron: LANGUAGE=en_SG.UTF-8 PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_SG.UTF-8 SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ubiquity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug ubiquity-2.21.63.4 ubuntu xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1726851 Title: Unable to install Ubuntu 16.04.3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1726851/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 292676] Re: Thunderbird doesn't play any sound on notification
Problem: I just discovered that thunderbird 52.4.0 (64bit) on Ubuntu Xenial can't play a wav file for new mail. The default new mail sound can be play though. Solution: I installed "Sound Converter" from Ubuntu Software and used it to covert my .wav file to .ogg format (mentioned by @doxland) and tried it on Thunderbird. It works...:) Thanks @doxland for sharing about .ogg format. I did not know such a sound format had existed. Hope the Thunderbird team could make this fix seamless or at least inform user to use only .ogg format sound file in Thunderbird. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/292676 Title: Thunderbird doesn't play any sound on notification To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/292676/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1721277] [NEW] pip3 version 8.1.1. is dated, version 9.0.1 is needed for Ubuntu 16.04 Xenial LTS
Public bug reported: pip3 version 8.1.1 was released on 2016-03-17. It's latest version 9.0.1 was released on 2016-11-06, and there have been many bug fixes to version 8.1.1 since then. It is now 2017-1-04. I like to make the point here that Ubuntu 16.04 being the present LTS version should now (if not soon) have pip version 9.0.1 as it's stable release. This will greatly benefit Xenial users. ** Affects: python-pip (Ubuntu) Importance: Undecided Status: New ** Summary changed: - pip3 version 8.1.1. is dated, version 9.0.1 is needed for Ubuntu 16.04 Xenia LTSl + pip3 version 8.1.1. is dated, version 9.0.1 is needed for Ubuntu 16.04 Xenial LTS -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1721277 Title: pip3 version 8.1.1. is dated, version 9.0.1 is needed for Ubuntu 16.04 Xenial LTS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-pip/+bug/1721277/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1720964] [NEW] gcc 5.4 Segmentation fault while making Vulkan 1.0.61.1 example
Public bug reported: I am using Ubuntu 16.04 with kernel 4.10.0-33-generic and gcc version 5.4.0-6ubuntu1~16.04.4. I did a local install of Vulkan 1.0.61.1 and tried to build and make one of it's example with the following commands: cd examples cmake -H. -Bbuild cmake -H. -Bdbuild -DCMAKE_BUILD_TYPE=Debug make -C build make -C dbuild During "make -C build" command, I encountered an error that asked me to make a full bug report. How can I overcome the issue? $ make -C build make: Entering directory '$HOME/Vulkan/VulkanSDK/1.0.61.1/examples/build' make[1]: Entering directory ''$HOME/Vulkan/VulkanSDK/1.0.61.1/examples/build' make[2]: Entering directory ''$HOME/Vulkan/VulkanSDK/1.0.61.1/examples/build' Scanning dependencies of target vulkaninfo make[2]: Leaving directory ''$HOME/Vulkan/VulkanSDK/1.0.61.1/examples/build' make[2]: Entering directory ''$HOME/Vulkan/VulkanSDK/1.0.61.1/examples/build' [ 10%] Building C object CMakeFiles/vulkaninfo.dir/vulkaninfo.c.o [ 20%] Linking C executable vulkaninfo make[2]: Leaving directory ''$HOME/Vulkan/VulkanSDK/1.0.61.1/examples/build' [ 20%] Built target vulkaninfo make[2]: Entering directory ''$HOME/Vulkan/VulkanSDK/1.0.61.1/examples/build' [ 30%] Generating cube-frag.spv [ 40%] Generating cube-vert.spv Scanning dependencies of target cubepp make[2]: Leaving directory ''$HOME/Vulkan/VulkanSDK/1.0.61.1/examples/build' make[2]: Entering directory ''$HOME/Vulkan/VulkanSDK/1.0.61.1/examples/build' [ 50%] Building CXX object CMakeFiles/cubepp.dir/cube.cpp.o In file included from '$HOME/Vulkan/VulkanSDK/1.0.61.1/examples/cube.cpp:39:0: '$HOME/Vulkan/VulkanSDK/1.0.61.1/x86_64/include/vulkan/vulkan.hpp:18745:11: internal compiler error: Segmentation fault && ( maxTessellationGenerationLevel == rhs.maxTessellationGenerationLevel ) ^ Please submit a full bug report, with preprocessed source if appropriate. See for instructions. CMakeFiles/cubepp.dir/build.make:72: recipe for target 'CMakeFiles/cubepp.dir/cube.cpp.o' failed make[2]: *** [CMakeFiles/cubepp.dir/cube.cpp.o] Error 1 make[2]: Leaving directory ''$HOME/Vulkan/VulkanSDK/1.0.61.1/examples/build' CMakeFiles/Makefile2:104: recipe for target 'CMakeFiles/cubepp.dir/all' failed make[1]: *** [CMakeFiles/cubepp.dir/all] Error 2 make[1]: Leaving directory ''$HOME/Vulkan/VulkanSDK/1.0.61.1/examples/build' Makefile:83: recipe for target 'all' failed make: *** [all] Error 2 make: Leaving directory ''$HOME/Vulkan/VulkanSDK/1.0.61.1/examples/build' ** Affects: gcc-5 (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/1720964 Title: gcc 5.4 Segmentation fault while making Vulkan 1.0.61.1 example To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gcc-5/+bug/1720964/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1703962] Re: (NULL device *): hwmon_device_register() is deprecated. Please convert the driver to use hwmon_device_register_with_info().
I have also noticed this error in output from dmesg. (NULL device *): hwmon_device_register() is deprecated. Please convert the driver to use hwmon_device_register_with_info(). $ uname -r 4.10.0-33-generic I am using Ubuntu 16.04 The hwmon is a generic Linux kernel subsystem, providing access to hardware monitoring components like temperature or voltage/current sensors. Is there a way to find out which device driver needs updating? Why does it say (NULL device *)? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1703962 Title: (NULL device *): hwmon_device_register() is deprecated. Please convert the driver to use hwmon_device_register_with_info(). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1703962/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1667158] Re: Regression: Borders of windows and desktop background are displayed badly after suspend/resume
Agree. On 05/06/2017 22:31, Mike Gresens wrote: > So this bug should be closed?! > > ** Description changed: > > + == Update4: == > + > + The nvidia driver 375.66 is now part of the default repo. > + Since the bugfix is contained in this driver, we should close the bug?! > + >== Update3: == > >nvidia delivered a new driver: 375.66 > >Contains the same bugfix as 381.09 beta > >This driver can now be installed via ppa from Graphics Drivers Team and >sudo apt-get update (see comment #54). > >See https://launchpad.net/~graphics-drivers/+archive/ubuntu/ppa > >Should driver 375.66 become the default driver for Ubuntu 17.04 - >available without PPA ?! > >== Update2: == > >nvidia delivered a new driver: 381.09 beta >https://devtalk.nvidia.com/default/topic/1002788 > >From release notes: > >"Fixed a regression that caused corruption in certain applications, such >as window border shadows in Unity, after resuming from suspend." >(nvidia) > >This driver can now be downloaded and installed manually from Nvidia >link, or via ppa from Graphics Drivers Team and sudo apt-get update (see >comment #54). > >See https://launchpad.net/~graphics-drivers/+archive/ubuntu/ppa > >== Update1: == > >Nvidia states that the bug will be fixed in the next release: >https://devtalk.nvidia.com/default/topic/990898/linux/suspend-corrupts- >window-manager-after-upgrade-to-378-09/2. However no timeline for the >next release was mentioned. > >Meanwhile workarounds have to be used to alleviate/overcome the bad >window borders and title bar caused by driver version 375.39. > >-- Possible workarounds for the time being -- > >- Alternative A: Keep using nvidia-375.39 with workarounds. > E.g. kill or replace compiz process. See comments #13 and > #44 given below for implementation details. Beware, > some users found the command killed applications > like Firefox or Thunderbird on resume while others > did not. > E.g. Use "unity" command (see comments #4 and #23) > E.g. Click an effect in CompizConfig Setting Manager > (CCSM) --> Effects. (see comment $5) >- Alternative B: Use alternative graphic drivers. > E.g. Install nvidia-340 package if that versions supports > your graphic card: sudo apt install nvidia-340. Or > use Nouveau display driver or other suitable drivers > available in System Settings --> Software & Updates > --> Additional Drivers. >- Alternative C: Downgrade to earlier driver versions that worked before > the updgrade occurred. E.g. use nvidia-367 package. > Beware, that this driver version has unfixed security > holes! Downgrading works in Yakkety, possibly also in > Xenial, but likely not in Zesty. Command to downgrade: > sudo apt install nvidia-367=367.57-0ubuntu3 libcuda1- > 367=367.57-0ubuntu3 nvidia-opencl-icd-367=367.57-0ubuntu3 > > >Original text of this bug report: > >My system graphic driver had just updated to 375.39 but Borders of pop- >up windows are displayed badly. This is especially true after waking up >from suspend mode. this driver is buggy. I am using Ubuntu 16.04. Any >way to rectify this display problem? > > ** Changed in: nvidia-graphics-drivers-375 (Ubuntu) > Status: Confirmed => 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/1667158 Title: Regression: Borders of windows and desktop background are displayed badly after suspend/resume To manage notifications about this bug go to: https://bugs.launchpad.net/linuxmint/+bug/1667158/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1667158] Re: Regression: Borders of windows and desktop background are displayed badly after suspend/resume
I am using cairo-dock alongside unity launcher. An issue I do encounter with using 381.09, is that after waking, certain icons/applet like gnome terminal, idle_python, gedit, Pidgin, musicplayer would not appear correctly unless a new GUI of these app is created/deleted. For music player I have to activate a function like play a song before the icon appearance is refreshed to appear correctly. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1667158 Title: Regression: Borders of windows and desktop background are displayed badly after suspend/resume To manage notifications about this bug go to: https://bugs.launchpad.net/linuxmint/+bug/1667158/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1667158] Re: Regression: Borders of windows and desktop background are displayed badly after suspend/resume
@kcm. I tried both scenario. Before and after suspend. GPU performances are similar. I have tried another test. While running the nbody simulation, I went into suspend mode. After waking, i found the nobody simulation stopped. However, i could not restart it because: "Error: only 0 Devices available, 1 requested. Exiting." The GPU was not freed up on waking from suspend mode although the cpu process was terminated when going into suspend mode. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1667158 Title: Regression: Borders of windows and desktop background are displayed badly after suspend/resume To manage notifications about this bug go to: https://bugs.launchpad.net/linuxmint/+bug/1667158/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1667158] Re: Regression: Borders of windows and desktop background are displayed badly after suspend/resume
@experimencer Thanks again. It helped me tied over this period. ;) @huiprobable To solve your issue, I think you have to run the script after passing password authentication. You might want to try driver 381.09 instead since it is now available. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1667158 Title: Regression: Borders of windows and desktop background are displayed badly after suspend/resume To manage notifications about this bug go to: https://bugs.launchpad.net/linuxmint/+bug/1667158/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1667158] Re: Regression: Borders of windows and desktop background are displayed badly after suspend/resume
@kcm. I ran GPU calculations /NVIDIA_CUDA-8.0_Samples/5_Simulations/nbody/nbody and also https://www.airtightinteractive.com/demos/ribbons/ for about 20 mins. Nvidia X Server Setting --> GPU 0 - (GForce GTX Titan) --> Thermal Setting showed: Temperature = 72 to 75 degrees C, Fan speed = ~1737rpm, 44%, Control type = variable, Cooling target = GPU, Memory & Power supply. --> PowerMizer performance level=3, graphic clock = 536 to 1202 MHz, Memory Transfer Rate = 6008 to 6008 MHz set at maximum performance mode. These results look ok, no overheating. I physically touched my GPU fan and it is running. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1667158 Title: Regression: Borders of windows and desktop background are displayed badly after suspend/resume To manage notifications about this bug go to: https://bugs.launchpad.net/linuxmint/+bug/1667158/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1667158] Re: Regression: Borders of windows and desktop background are displayed badly after suspend/resume
I have updated to Nvidia 381.09 driver via the ppa update route. The bad window borders caused by drivers 375.39 and 378.13 do not appear in this new driver. In my system, on the first reboot(after installing 381.09), I did get a black screen partially obscuring my unity desktop for a short while before the desktop wallpaper and menu bar appeared. On the next reboot, everything was back to normal again; desktop bootup was fast again. For those who used the workaround described in comment #13, do remember to remove the "fixbadborders" file from directory "/lib/systemd/system- sleep" after you have installed the new 381.09 driver. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1667158 Title: Regression: Borders of windows and desktop background are displayed badly after suspend/resume To manage notifications about this bug go to: https://bugs.launchpad.net/linuxmint/+bug/1667158/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1667158] Re: Regression: Borders of windows and desktop background are displayed badly after suspend/resume
** Description changed: == Update2: == nvidia delivered a new driver: 381.09 beta https://devtalk.nvidia.com/default/topic/1002788 From release notes: "Fixed a regression that caused corruption in certain applications, such as window border shadows in Unity, after resuming from suspend." (nvidia) + + This driver can now be downloaded and installed manually from Nvidia + link, or via ppa from Graphics Drivers Team and sudo apt-get update (see + comment #54). == Update1: == Nvidia states that the bug will be fixed in the next release: https://devtalk.nvidia.com/default/topic/990898/linux/suspend-corrupts- window-manager-after-upgrade-to-378-09/2. However no timeline for the next release was mentioned. Meanwhile workarounds have to be used to alleviate/overcome the bad window borders and title bar caused by driver version 375.39. -- Possible workarounds for the time being -- - Alternative A: Keep using nvidia-375.39 with workarounds.  E.g. kill or replace compiz process. See comments #13 and   #44 given below for implementation details. Beware,   some users found the command killed applications   like Firefox or Thunderbird on resume while others   did not.  E.g. Use "unity" command (see comments #4 and #23)  E.g. Click an effect in CompizConfig Setting Manager   (CCSM) --> Effects. (see comment $5) - Alternative B: Use alternative graphic drivers.  E.g. Install nvidia-340 package if that versions supports   your graphic card: sudo apt install nvidia-340. Or   use Nouveau display driver or other suitable drivers   available in System Settings --> Software & Updates   --> Additional Drivers. - Alternative C: Downgrade to earlier driver versions that worked before  the updgrade occurred. E.g. use nvidia-367 package.  Beware, that this driver version has unfixed security  holes! Downgrading works in Yakkety, possibly also in  Xenial, but likely not in Zesty. Command to downgrade:  sudo apt install nvidia-367=367.57-0ubuntu3 libcuda1-  367=367.57-0ubuntu3 nvidia-opencl-icd-367=367.57-0ubuntu3 Original text of this bug report: My system graphic driver had just updated to 375.39 but Borders of pop- up windows are displayed badly. This is especially true after waking up from suspend mode. this driver is buggy. I am using Ubuntu 16.04. Any way to rectify this display problem? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1667158 Title: Regression: Borders of windows and desktop background are displayed badly after suspend/resume To manage notifications about this bug go to: https://bugs.launchpad.net/linuxmint/+bug/1667158/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1667158] Re: Regression: Borders of windows and desktop background are displayed badly after suspend/resume
Michael from the "Graphics Drivers" Team has already uploaded the new 381.09 beta driver in their ppa 2 hours ago. So those using this ppa select this driver update soon. For those not using it, this is the simplest way to have your nvidia graphic driver updated with the latest. You can access it via: sudo add-apt-repository ppa:graphics-drivers/ppa sudo apt-get update sudo apt-get install nvidia-381 Thanks Michael. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1667158 Title: Regression: Borders of windows and desktop background are displayed badly after suspend/resume To manage notifications about this bug go to: https://bugs.launchpad.net/linuxmint/+bug/1667158/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1667158] Re: Regression: Borders of windows and desktop background are displayed badly after suspend/resume
@Pavel Thank you for the reminder. ;) Yes, I agree with you. Do manual installation if you are prepared to spend quite a bit of time tinkering about. Else, a user will find themselves having to go through a steep learning curve about lightdm, systemd, Xorg, Grub2, kdms and administrator bash commands, and heartaches if some issues arise after installation. Be Warned. Do take this route if you need to or are prepared to tinker. For users who want to avoid any tinkering, it may be better to use the workarounds until a non-beta driver version get released and the ppa team updates their driver. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1667158 Title: Regression: Borders of windows and desktop background are displayed badly after suspend/resume To manage notifications about this bug go to: https://bugs.launchpad.net/linuxmint/+bug/1667158/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1667158] Re: Regression: Borders of windows and desktop background are displayed badly after suspend/resume
@MikeGresens Thanks for updating. According to the Nvidia update note on 381.09, it is suppose to fix the badborder issue. However, the ppa :graphics-drivers/ppa team has not uploaded it yet. To use it, the appropriate driver has to be manually downloaded (use the hyperlink provided in the webpage you provided) and installed. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1667158 Title: Regression: Borders of windows and desktop background are displayed badly after suspend/resume To manage notifications about this bug go to: https://bugs.launchpad.net/linuxmint/+bug/1667158/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1667158] Re: Regression: Borders of windows and desktop background are displayed badly after suspend/resume
** Description changed: - == Update: == + == Update2: == nvidia delivered a new driver: 381.09 beta https://devtalk.nvidia.com/default/topic/1002788 From release notes: "Fixed a regression that caused corruption in certain applications, such as window border shadows in Unity, after resuming from suspend." (nvidia) - -- + == Update1: == Nvidia states that the bug will be fixed in the next release: https://devtalk.nvidia.com/default/topic/990898/linux/suspend-corrupts- window-manager-after-upgrade-to-378-09/2. However no timeline for the next release was mentioned. Meanwhile workarounds have to be used to alleviate/overcome the bad window borders and title bar caused by driver version 375.39. - == Possible workarounds for the time being == + -- Possible workarounds for the time being -- - Alternative A: Keep using nvidia-375.39 with workarounds.  E.g. kill or replace compiz process. See comments #13 and   #44 given below for implementation details. Beware,   some users found the command killed applications   like Firefox or Thunderbird on resume while others   did not.  E.g. Use "unity" command (see comments #4 and #23)  E.g. Click an effect in CompizConfig Setting Manager   (CCSM) --> Effects. (see comment $5) - Alternative B: Use alternative graphic drivers.  E.g. Install nvidia-340 package if that versions supports   your graphic card: sudo apt install nvidia-340. Or   use Nouveau display driver or other suitable drivers   available in System Settings --> Software & Updates   --> Additional Drivers. - Alternative C: Downgrade to earlier driver versions that worked before  the updgrade occurred. E.g. use nvidia-367 package.  Beware, that this driver version has unfixed security  holes! Downgrading works in Yakkety, possibly also in  Xenial, but likely not in Zesty. Command to downgrade:  sudo apt install nvidia-367=367.57-0ubuntu3 libcuda1-  367=367.57-0ubuntu3 nvidia-opencl-icd-367=367.57-0ubuntu3 Original text of this bug report: My system graphic driver had just updated to 375.39 but Borders of pop- up windows are displayed badly. This is especially true after waking up from suspend mode. this driver is buggy. I am using Ubuntu 16.04. Any way to rectify this display problem? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1667158 Title: Regression: Borders of windows and desktop background are displayed badly after suspend/resume To manage notifications about this bug go to: https://bugs.launchpad.net/linuxmint/+bug/1667158/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1680433] Re: Flash: This plugin is not supported.
@Chad I checked my /var/log/apt/history.log. It showed that the following chromium role-commit-package upgrades were performed: chromium-browser:amd64 (56.0.2924.76-0ubuntu0.16.04.1268, 57.0.2987.98-0ubuntu0.16.04.1276), chromium-codecs-ffmpeg-extra:amd64 (56.0.2924.76-0ubuntu0.16.04.1268, 57.0.2987.98-0ubuntu0.16.04.1276), chromium-browser-l10n:amd64 (56.0.2924.76-0ubuntu0.16.04.1268, 57.0.2987.98-0ubuntu0.16.04.1276) Also, a day before this upgrade, my kernel was upgraded: linux-headers-generic-hwe-16.04:amd64 (4.8.0.45.17, 4.8.0.46.18) I don't know which adobe-flashplugin I had initially. To fix it, I had to issue the following command: apt-get install browser-plugin-freshplayer-pepperflash -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1680433 Title: Flash: This plugin is not supported. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1680433/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1680433] Re: Flash: This plugin is not supported.
$ apt policy adobe-flashplugin adobe-flashplugin: Installed: 1:20170314.1-0ubuntu0.16.04.1 Candidate: 1:20170314.1-0ubuntu0.16.04.1 Version table: *** 1:20170314.1-0ubuntu0.16.04.1 500 500 http://archive.canonical.com/ubuntu xenial/partner amd64 Packages 100 /var/lib/dpkg/status -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1680433 Title: Flash: This plugin is not supported. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1680433/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1584407] Re: ACPI Error: [\_SB_.PCI0.XHC_.RHUB.HS11] Namespace lookup failure, AE_NOT_FOUND (20150930/dswload-210)
I had reported this bug error. However, i don't have this error anymore on a same system using Ubuntu16.04.2 with kernel 4.4.0-6x and kernel 4.8.0-xx. I suspect it is related to changes in UEFI/BIOS and using the more updated UEFI/BIOS driver versions. Below are my UEFI settings and hope it help you (I don't know if they are correct for you or not). I am using ASUS Z170M-Plus motherboard. Advance Setting -->Platform Misc Configuration Platform Misc Configuration --PCI Express Native Power Management (Enabled) --Native ASPM (Enabled) PCH-PCI Express --PCH DMI ASPM(Enabled) --ASPM(Auto) SA-PCI Express --DMI Link ASPM Control (L1) --PEG-ASPM (Auto) Advance Setting -->USB Configuration Legacy USB Support(Enabled) XHCI Hand-off (Enable) Advance --> Boot Fast Boot (Disabled) CSM(Compatibility Support Module) --> Launch CSM (Disabled) Secure Boot (Other OS) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1584407 Title: ACPI Error: [\_SB_.PCI0.XHC_.RHUB.HS11] Namespace lookup failure, AE_NOT_FOUND (20150930/dswload-210) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1584407/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1667158] Re: Regression: Borders of windows and desktop background are displayed badly after suspend/resume
** Description changed: == Update: == - Nvidia states that the bug will be fixed in the next release: https://devtalk.nvidia.com/default/topic/990898/linux/suspend-corrupts-window-manager-after-upgrade-to-378-09/2. However no timeline for the next release was mentioned. + Nvidia states that the bug will be fixed in the next release: https://devtalk.nvidia.com/default/topic/990898/linux/suspend-corrupts-window-manager-after-upgrade-to-378-09/2. However no timeline for the next release was mentioned. Meanwhile workarounds have to be used to alleviate/overcome the bad window borders and title bar caused by driver version 375.39. == Possible workarounds for the time being == - Alternative A: Keep using nvidia-375.39 with workarounds. - E.g. kill or replace compiz process. See comments #13 and - #44 given below for implementation details. Beware, - some users found the command killed applications - like Firefox or Thunderbird on resume while others - did not. - E.g. Use "unity" command (see comments #4 and #23) - E.g. Click an effect in CompizConfig Setting Manager - (CCSM) --> Effects. (see comment $5) - - Alternative B: Use alternative graphic drivers. - E.g. Install nvidia-340 package if that versions supports - your graphic card: sudo apt install nvidia-340. Or - use Nouveau display driver or other suitable drivers - available in System Settings --> Software & Updates - --> Additional Drivers. - - Alternative C: Downgrade to earlier driver versions that worked before - the updgrade occurred. E.g. use nvidia-367 package. - Beware, that this driver version has unfixed security - holes! Downgrading works in Yakkety, possibly also in - Xenial, but likely not in Zesty. Command to downgrade: - sudo apt install nvidia-367=367.57-0ubuntu3 libcuda1- - 367=367.57-0ubuntu3 nvidia-opencl-icd-367=367.57-0ubuntu3 - (375.26 may also be used if it worked for you previously) + Â E.g. kill or replace compiz process. See comments #13 and + Â Â #44 given below for implementation details. Beware, + Â Â some users found the command killed applications + Â Â like Firefox or Thunderbird on resume while others + Â Â did not. + Â E.g. Use "unity" command (see comments #4 and #23) + Â E.g. Click an effect in CompizConfig Setting Manager + Â Â (CCSM) --> Effects. (see comment $5) + - Alternative B: Use alternative graphic drivers. + Â E.g. Install nvidia-340 package if that versions supports + Â Â your graphic card: sudo apt install nvidia-340. Or + Â Â use Nouveau display driver or other suitable drivers + Â Â available in System Settings --> Software & Updates + Â Â --> Additional Drivers. + - Alternative C: Downgrade to earlier driver versions that worked before + Â the updgrade occurred. E.g. use nvidia-367 package. + Â Beware, that this driver version has unfixed security + Â holes! Downgrading works in Yakkety, possibly also in + Â Xenial, but likely not in Zesty. Command to downgrade: + Â sudo apt install nvidia-367=367.57-0ubuntu3 libcuda1- + Â 367=367.57-0ubuntu3 nvidia-opencl-icd-367=367.57-0ubuntu3 - Originial text of this bug report: + Original text of this bug report: My system graphic driver had just updated to 375.39 but Borders of pop- up windows are displayed badly. This is especially true after waking up from suspend mode. this driver is buggy. I am using Ubuntu 16.04. Any way to rectify this display problem? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1667158 Title: Regression: Borders of windows and desktop background are displayed badly after suspend/resume To manage notifications about this bug go to: https://bugs.launchpad.net/linuxmint/+bug/1667158/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1680433] [NEW] Flash: This plugin is not supported.
Public bug reported:
$ lsb_release -rd
Description:Ubuntu 16.04.2 LTS
Release:16.04
$ apt-cache policy chromium-browser
chromium-browser:
Installed: 57.0.2987.98-0ubuntu0.16.04.1276
Candidate: 57.0.2987.98-0ubuntu0.16.04.1276
Version table:
*** 57.0.2987.98-0ubuntu0.16.04.1276 500
500 http://sg.archive.ubuntu.com/ubuntu xenial-updates/universe amd64
Packages
500 http://security.ubuntu.com/ubuntu xenial-security/universe amd64
Packages
100 /var/lib/dpkg/status
49.0.2623.108-0ubuntu1.1233 500
500 http://sg.archive.ubuntu.com/ubuntu xenial/universe amd64 Packages
My system was just updated with chromium-browser
57.0.2987.98-0ubuntu0.16.04.1276 amd64 today. However, this resulted in
breaking the flash plugin. When I open a webpage requiring flash, the webpage
returned
"This plugin is not supported".
When i inspected the code, the failure appears to be related to:
http://www.mconline.sg/nres1/{F639486D-19A1-43EE-919E-
AD353407EDE1}/skin/scorm_topbar.swf" quality="high" bgcolor="#ff"
width="100%" height="100%" name="topNav" id="topNav" scale="exactfit"
align="middle" allowscriptaccess="sameDomain" type="application/x
-shockwave-flash"
pluginspage="http://www.macromedia.com/go/getflashplayer";
title="undefined">
How can this issue be fixed?
** Affects: chromium-browser (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1680433
Title:
Flash: This plugin is not supported.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1680433/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1667158] Re: Regression: Borders of windows and desktop background are displayed badly after suspend/resume
** Description changed: == Update: == - Nvidia states that the bug will be fixed in the next release: https://devtalk.nvidia.com/default/topic/990898/linux/suspend-corrupts-window-manager-after-upgrade-to-378-09/2 + Nvidia states that the bug will be fixed in the next release: https://devtalk.nvidia.com/default/topic/990898/linux/suspend-corrupts-window-manager-after-upgrade-to-378-09/2. However no timeline for the next release was mentioned. + + Meanwhile workarounds have to be used to alleviate/overcome the bad + window borders and title bar caused by driver version 375.39. == Possible workarounds for the time being == - - Alternative A: Install nvidia-340 package if that versions supports your card: sudo apt install nvidia-340 - - Alternative B: Keep nvidia-375 and use the shell script described in comment #13: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-375/+bug/1667158/comments/13 - Beware, this might kill applications like Firefox or Thunderbird on resume! - - Alternative C: Downgrade to the nvidia-367 package. Beware, that this driver version has unfixed security holes! Downgrading works in Yakkety, possibly also in Xenial, but likely not in Zesty. Command to downgrade: sudo apt install nvidia-367=367.57-0ubuntu3 libcuda1-367=367.57-0ubuntu3 nvidia-opencl-icd-367=367.57-0ubuntu3 + - Alternative A: Keep using nvidia-375.39 with workarounds. + E.g. kill or replace compiz process. See comments #13 and + #44 given below for implementation details. Beware, + some users found the command killed applications + like Firefox or Thunderbird on resume while others + did not. + E.g. Use "unity" command (see comments #4 and #23) + E.g. Click an effect in CompizConfig Setting Manager + (CCSM) --> Effects. (see comment $5) + - Alternative B: Use alternative graphic drivers. + E.g. Install nvidia-340 package if that versions supports + your graphic card: sudo apt install nvidia-340. Or + use Nouveau display driver or other suitable drivers + available in System Settings --> Software & Updates + --> Additional Drivers. + - Alternative C: Downgrade to earlier driver versions that worked before + the updgrade occurred. E.g. use nvidia-367 package. + Beware, that this driver version has unfixed security + holes! Downgrading works in Yakkety, possibly also in + Xenial, but likely not in Zesty. Command to downgrade: + sudo apt install nvidia-367=367.57-0ubuntu3 libcuda1- + 367=367.57-0ubuntu3 nvidia-opencl-icd-367=367.57-0ubuntu3 + (375.26 may also be used if it worked for you previously) Originial text of this bug report: My system graphic driver had just updated to 375.39 but Borders of pop- up windows are displayed badly. This is especially true after waking up from suspend mode. this driver is buggy. I am using Ubuntu 16.04. Any way to rectify this display problem? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1667158 Title: Regression: Borders of windows and desktop background are displayed badly after suspend/resume To manage notifications about this bug go to: https://bugs.launchpad.net/linuxmint/+bug/1667158/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1667158] Re: Regression: Borders of windows and desktop background are displayed badly after suspend/resume
Hi Jan. I saw your email summarising the alternative solutions. Note, it was email to me instead of appearing in launchpad bug report. Maybe you can fix that so others can read? On 03/04/2017 14:02, Jan Rathmann wrote: > ** Description changed: > > + == Update: == > + Nvidia states that the bug will be fixed in the next release: > https://devtalk.nvidia.com/default/topic/990898/linux/suspend-corrupts-window-manager-after-upgrade-to-378-09/2 > + > + == Possible workarounds for the time being == > + > + - Install nvidia-340 package if that versions supports your card: sudo apt > install nvidia-340 > + - Downgrade nvidia-367 package. Beware, that this driver version has > unfixed security holes! Downgrading works in Yakkety, possibly also in > Xenial, but likely not in Zesty. Command to downgrade: sudo apt install > nvidia-367=367.57-0ubuntu3 libcuda1-367=367.57-0ubuntu3 > nvidia-opencl-icd-367=367.57-0ubuntu3 > + - Keep nvidia-375 and use the shell script described in comment #13: > https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-375/+bug/1667158/comments/13 > + Beware, this might kill applications like Firefox or Thunderbird on resume! > + > + > + Originial text of this bug report: > + >My system graphic driver had just updated to 375.39 but Borders of pop- >up windows are displayed badly. This is especially true after waking up >from suspend mode. this driver is buggy. I am using Ubuntu 16.04. Any >way to rectify this display problem? > > ** Description changed: > >== Update: == >Nvidia states that the bug will be fixed in the next release: > https://devtalk.nvidia.com/default/topic/990898/linux/suspend-corrupts-window-manager-after-upgrade-to-378-09/2 > >== Possible workarounds for the time being == > > - - Install nvidia-340 package if that versions supports your card: sudo apt > install nvidia-340 > - - Downgrade nvidia-367 package. Beware, that this driver version has > unfixed security holes! Downgrading works in Yakkety, possibly also in > Xenial, but likely not in Zesty. Command to downgrade: sudo apt install > nvidia-367=367.57-0ubuntu3 libcuda1-367=367.57-0ubuntu3 > nvidia-opencl-icd-367=367.57-0ubuntu3 > - - Keep nvidia-375 and use the shell script described in comment #13: > https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-375/+bug/1667158/comments/13 > + - Alternative A: Install nvidia-340 package if that versions supports your > card: sudo apt install nvidia-340 > + - Alternative B: Keep nvidia-375 and use the shell script described in > comment #13: > https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-375/+bug/1667158/comments/13 >Beware, this might kill applications like Firefox or Thunderbird on resume! > + - Alternative C: Downgrade to the nvidia-367 package. Beware, that this > driver version has unfixed security holes! Downgrading works in Yakkety, > possibly also in Xenial, but likely not in Zesty. Command to downgrade: sudo > apt install nvidia-367=367.57-0ubuntu3 libcuda1-367=367.57-0ubuntu3 > nvidia-opencl-icd-367=367.57-0ubuntu3 > > >Originial text of this bug report: > >My system graphic driver had just updated to 375.39 but Borders of pop- >up windows are displayed badly. This is especially true after waking up >from suspend mode. this driver is buggy. I am using Ubuntu 16.04. Any >way to rectify this display problem? > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1667158 Title: Regression: Borders of windows and desktop background are displayed badly after suspend/resume To manage notifications about this bug go to: https://bugs.launchpad.net/linuxmint/+bug/1667158/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1165087] Re: compiz assert failure: *** Error in `compiz': double free or corruption (out): 0x000000000340e0c0 ***
I am experiencing this error when I issue this command "compiz --replace &": compiz assert failure: *** Error in `compiz': double free or corruption (!In): 0x026562b0 *** .proc.driver.nvidia.gpus.:01:00.0. Error:[Error21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0.' System info: Ubuntu 16.04.2 with Linux Kernel 4.8.0-45-generic. Nvidia driver 375.39 A background on why this command is used is given in https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics- drivers-375/+bug/1667158. Brief explanation, after the introduction of the new Nvidia driver 375.39, which is a long live version, all GUIs will show bad borders and title/menu bars after waking up from suspend mode. For system based on Ubuntu 16.04.2 with Linux Kernel 4.8.0-xx-generic, "compiz --replace &" is so far the only command I found to be able to temporarily solve the problem. However, after running the command, the above mentioned crash report will be report by ubuntu-bug (apport). The Warnings and Error appearing on my terminal is shown below. $ compiz --replace & [1] 29676 $ compiz (core) - Info: Loading plugin: core compiz (core) - Info: Starting plugin: core compiz (core) - Info: Loading plugin: ccp compiz (core) - Info: Starting plugin: ccp compizconfig - Info: Backend : gsettings compizconfig - Info: Integration : true compizconfig - Info: Profile : unity compiz (core) - Info: Loading plugin: composite compiz (core) - Info: Starting plugin: composite compiz (core) - Info: Loading plugin: opengl compiz (core) - Info: Starting plugin: opengl Compiz (opengl) - Info: GLX_EXT_buffer_age is supported compiz (core) - Info: Loading plugin: imgpng compiz (core) - Info: Starting plugin: imgpng compiz (core) - Info: Loading plugin: move compiz (core) - Info: Starting plugin: move compiz (core) - Info: Loading plugin: wall compiz (core) - Info: Starting plugin: wall compiz (core) - Info: Loading plugin: copytex compiz (core) - Info: Starting plugin: copytex compiz (core) - Info: Loading plugin: vpswitch compiz (core) - Info: Starting plugin: vpswitch compiz (core) - Info: Loading plugin: unitymtgrabhandles compiz (core) - Info: Starting plugin: unitymtgrabhandles compiz (core) - Info: Loading plugin: resize compiz (core) - Info: Starting plugin: resize compiz (core) - Info: Loading plugin: regex compiz (core) - Info: Starting plugin: regex compiz (core) - Info: Loading plugin: mousepoll compiz (core) - Info: Starting plugin: mousepoll compiz (core) - Info: Loading plugin: scale compiz (core) - Info: Starting plugin: scale compiz (core) - Info: Loading plugin: grid compiz (core) - Info: Starting plugin: grid compiz (core) - Info: Loading plugin: animation compiz (core) - Info: Starting plugin: animation compiz (core) - Info: Loading plugin: place compiz (core) - Info: Starting plugin: place compiz (core) - Info: Loading plugin: compiztoolbox compiz (core) - Info: Starting plugin: compiztoolbox compiz (core) - Info: Loading plugin: commands compiz (core) - Info: Starting plugin: commands compiz (core) - Info: Loading plugin: workarounds compiz (core) - Info: Starting plugin: workarounds compiz (core) - Info: Loading plugin: session compiz (core) - Info: Starting plugin: session I/O warning : failed to load external entity "$HOME.compiz/session/1088929cdfe95d66514911185186930160015020004" compiz (core) - Info: Loading plugin: expo compiz (core) - Info: Starting plugin: expo compiz (core) - Info: Loading plugin: ezoom compiz (core) - Info: Starting plugin: ezoom compiz (core) - Info: Loading plugin: unityshell compiz (core) - Info: Starting plugin: unityshell WARN 2017-04-03 10:06:38 unity.glib.dbus.server GLibDBusServer.cpp:593 Can't register object 'org.gnome.Shell' yet as we don't have a connection, waiting for it... WARN 2017-04-03 10:06:38 unity.debug.interface DebugDBusInterface.cpp:217 Unable to load entry point in libxpathselect: libxpathselect.so.1.4: cannot open shared object file: No such file or directory -- full D-Bus introspection will not be available WARN 2017-04-03 10:06:38 xim.controller XIMController.cpp:103 IBus natively supported. WARN 2017-04-03 10:06:38 unity.dash.gsettingsscopereader GSettingsScopes.cpp:108 Error fetching protocol metadata for scope: social.scope : Valid key file could not be found in search dirs WARN 2017-04-03 10:06:38 unity.glib.dbus.server GLibDBusServer.cpp:593 Can't register object 'com.canonical.Unity.Launcher' yet as we don't have a connection, waiting for it... WARN 2017-04-03 10:06:38 unity.glib.dbus.server GLibDBusServer.cpp:593 Can't register object 'com.canonical.Unity.Dash' yet as we don't have a connection, waiting for it... WARN 2017-04-03 10:06:38 unity.glib.dbus.server GLibDBusServer.cpp:593 Can't register object 'org.gnome.SessionManager.EndSessionDialog' yet as we don't have a connection, waiting for it... WARN 2017-04-03 10:06:38 unity.glib.dbus.server GLibDBusServer.cpp:593 Can't register object 'com.canonical.Unity.Session
[Bug 1667158] Re: Regression: Borders of windows and desktop background are displayed badly after suspend/resume
Update on my findings: There are 3 versions of Ubuntu 16.04 LTS to date: 1. Ubuntu 16.04 LTS (released on 21st Apr 2016) 2. Ubuntu 16.04.1 LTS (Released on 21st Jul 2016) 3. Ubuntu 16.04.2 LTS (Released on 16th Feb 2017) However, there appear to be two major versions of Linux kernel used for these Ubuntu releases. I have one version lock onto 4.4.0-64 and another system presently using 4.8.0-45 (recently installed using Ubuntu 16.04.2 Installer) To see Linux Kernel version, run this command: uname -r Based on my systems, I suggest the following temporary solutions: Linux Kernel 4.4.0-xx --- refer to to comment 13. https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics- drivers-375/+bug/1667158/comments/13 Linux kernel 4.8.0-xx --- After waking from suspend, manually issue this command in a terminal: compriz --replace & If you have a way to automate the tmp solution for Linux Kernel 4.8.0-xx(Ubuntu 16.04.2) or have a better solutions, pls share. Appreciate. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1667158 Title: Regression: Borders of windows and desktop background are displayed badly after suspend/resume To manage notifications about this bug go to: https://bugs.launchpad.net/linuxmint/+bug/1667158/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1667158] Re: Regression: Borders of windows and desktop background are displayed badly after suspend/resume
Update on my findings: There are 2 versions of Ubuntu 16.04 LTS to date: 1. Ubuntu 16.04.1 LTS (Released on 21st Jul 2016) 2. Ubuntu 16.04.2 LTS (Released on 16th Feb 2017) Temporary Solution that worked on my system: Ubuntu 16.04.1 --- refer to to comment 13. https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics- drivers-375/+bug/1667158/comments/13 Ubuntu 16.04.2 --- After waking from suspend, manually issue this command in a terminal: compriz --replace & If you found a way to automate the tmp solution for Ubuntu 16.04.2 or have a better solution, pls share. Appreciate. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1667158 Title: Regression: Borders of windows and desktop background are displayed badly after suspend/resume To manage notifications about this bug go to: https://bugs.launchpad.net/linuxmint/+bug/1667158/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1667158] Re: Regression: Borders of windows and desktop background are displayed badly after suspend/resume
Correction. Try compiz --replace & Note: 1. w/o the '&' symbol, the command runs in the foreground and if you press Ctrl+C to terminate it accidentally, all windows title and menu bar disappears, and keyboard input to terminal can become unresponsive. Have to reboot system. 2. with the '&' symbol, commands runs in the background of the terminal. When terminal is closed, the old compiz is closed too and a new compiz process gets started. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1667158 Title: Regression: Borders of windows and desktop background are displayed badly after suspend/resume To manage notifications about this bug go to: https://bugs.launchpad.net/linuxmint/+bug/1667158/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1667158] Re: Regression: Borders of windows and desktop background are displayed badly after suspend/resume
I have tried the below command on command line. compiz --replace I got a lot of warnings and 2 errors, namely: ERROR 2017-04-01 02:04:52 unity.glib.dbus.server GLibDBusServer.cpp:538 DBus name lost 'org.gnome.Shell' ERROR 2017-04-01 02:04:52 unity.glib.dbus.server GLibDBusServer.cpp:538 DBus name lost 'com.canonical.Unity' Other than that, bad borders are removed. Try that to see if it help. Pls share your findings on whether it works for you or not. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1667158 Title: Regression: Borders of windows and desktop background are displayed badly after suspend/resume To manage notifications about this bug go to: https://bugs.launchpad.net/linuxmint/+bug/1667158/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1667158] Re: Regression: Borders of windows and desktop background are displayed badly after suspend/resume
@SvenNeuhaus Hello. Did you save the fixbadborders script in folder /lib/systemd/system-sleep and make the file executable as mentioned in comment #13? On 30/03/2017 18:13, Sven Neuhaus wrote: > Same here. When I kill compiz it does not get started again > automatically.. how come? (I'm on 16.04) > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1667158 Title: Regression: Borders of windows and desktop background are displayed badly after suspend/resume To manage notifications about this bug go to: https://bugs.launchpad.net/linuxmint/+bug/1667158/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1676102] Re: 375.39 cannot install on EFI booted ubuntu 16.04 kernel 4.8.0-41-generic
I used the nvidia drivers from graphics-drivers/ppa repository (correction to my earlier post). However, the bad window borders arising from waking up from suspend mode still persist (not fixed yet). Fortunately, the temporary solution mentioned in https://bugs.launchpad.net/linuxmint/+bug/1667158/comments/13 still works for now. I recommend the developing team rolling out the latest Ubuntu 16.04.2 LTS installer ensure that the nvidia 375.39 driver accompanying it works robustly. This will allow Ubuntu users to be more productive and encourage more folks to use Ubuntu. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1676102 Title: 375.39 cannot install on EFI booted ubuntu 16.04 kernel 4.8.0-41-generic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-375/+bug/1676102/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1676102] Re: 375.39 cannot install on EFI booted ubuntu 16.04 kernel 4.8.0-41-generic
I found a way to fix my issue. I ran the following commands to remove pre-existing nvidia drivers and downloaded and installed the drivers from your repository. After rebooting, Xsession became visible. Finally a success. Press Ctrl+Alt+F1 to go into tty1. Login to tty1. sudo apt-get purge nvidia-* sudo add-apt-repository ppa:graphics-drivers/ppa -y sudo apt-get update sudo apt-get install nvidia-375 -y -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1676102 Title: 375.39 cannot install on EFI booted ubuntu 16.04 kernel 4.8.0-41-generic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-375/+bug/1676102/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1676102] Re: 375.39 cannot install on EFI booted ubuntu 16.04 kernel 4.8.0-41-generic
Below is a section of the dpkg.log. I noticed that the installation is talking about using linux-image-4.4.0-66-generic:amd64 4.4.0-66.87 and linux-image-generic:amd64 4.4.0.66.70. But they aren't the 4.8.0-41-generic kernel that came with Ubuntu. Is this conflict preventing the installation? 2017-03-26 06:33:34 startup archives unpack 2017-03-26 06:33:34 install dkms:all 2.2.0.3-2ubuntu11.3 2017-03-26 06:33:34 status half-installed dkms:all 2.2.0.3-2ubuntu11.3 2017-03-26 06:33:34 status triggers-pending man-db:amd64 2.7.5-1 2017-03-26 06:33:34 status unpacked dkms:all 2.2.0.3-2ubuntu11.3 2017-03-26 06:33:34 status unpacked dkms:all 2.2.0.3-2ubuntu11.3 2017-03-26 06:33:34 install libc6-i386:amd64 2.23-0ubuntu7 2017-03-26 06:33:34 status triggers-pending libc-bin:amd64 2.23-0ubuntu7 2017-03-26 06:33:34 status half-installed libc6-i386:amd64 2.23-0ubuntu7 2017-03-26 06:33:34 status unpacked libc6-i386:amd64 2.23-0ubuntu7 2017-03-26 06:33:34 status unpacked libc6-i386:amd64 2.23-0ubuntu7 2017-03-26 06:33:34 install lib32gcc1:amd64 1:6.0.1-0ubuntu1 2017-03-26 06:33:34 status half-installed lib32gcc1:amd64 1:6.0.1-0ubuntu1 2017-03-26 06:33:34 status unpacked lib32gcc1:amd64 1:6.0.1-0ubuntu1 2017-03-26 06:33:34 status unpacked lib32gcc1:amd64 1:6.0.1-0ubuntu1 2017-03-26 06:33:35 install nvidia-375:amd64 375.39-0ubuntu0.16.04.1 2017-03-26 06:33:35 status half-installed nvidia-375:amd64 375.39-0ubuntu0.16.04.1 2017-03-26 06:33:36 status triggers-pending ureadahead:amd64 0.100.0-19 2017-03-26 06:33:41 status unpacked nvidia-375:amd64 375.39-0ubuntu0.16.04.1 2017-03-26 06:33:41 status unpacked nvidia-375:amd64 375.39-0ubuntu0.16.04.1 2017-03-26 06:33:41 install libcuda1-375:amd64 375.39-0ubuntu0.16.04.1 2017-03-26 06:33:41 status half-installed libcuda1-375:amd64 375.39-0ubuntu0.16.04.1 2017-03-26 06:33:41 status unpacked libcuda1-375:amd64 375.39-0ubuntu0.16.04.1 2017-03-26 06:33:41 status unpacked libcuda1-375:amd64 375.39-0ubuntu0.16.04.1 2017-03-26 06:33:41 install libjansson4:amd64 2.7-3 2017-03-26 06:33:41 status half-installed libjansson4:amd64 2.7-3 2017-03-26 06:33:41 status unpacked libjansson4:amd64 2.7-3 2017-03-26 06:33:41 status unpacked libjansson4:amd64 2.7-3 2017-03-26 06:33:41 install libvdpau1:amd64 1.1.1-3ubuntu1 2017-03-26 06:33:41 status half-installed libvdpau1:amd64 1.1.1-3ubuntu1 2017-03-26 06:33:41 status unpacked libvdpau1:amd64 1.1.1-3ubuntu1 2017-03-26 06:33:41 status unpacked libvdpau1:amd64 1.1.1-3ubuntu1 2017-03-26 06:33:41 install libxnvctrl0:amd64 361.42-0ubuntu1 2017-03-26 06:33:41 status half-installed libxnvctrl0:amd64 361.42-0ubuntu1 2017-03-26 06:33:41 status unpacked libxnvctrl0:amd64 361.42-0ubuntu1 2017-03-26 06:33:41 status unpacked libxnvctrl0:amd64 361.42-0ubuntu1 2017-03-26 06:33:41 install linux-image-4.4.0-66-generic:amd64 4.4.0-66.87 2017-03-26 06:33:41 status half-installed linux-image-4.4.0-66-generic:amd64 4.4.0-66.87 2017-03-26 06:33:43 status unpacked linux-image-4.4.0-66-generic:amd64 4.4.0-66.87 2017-03-26 06:33:43 status unpacked linux-image-4.4.0-66-generic:amd64 4.4.0-66.87 2017-03-26 06:33:43 install linux-image-extra-4.4.0-66-generic:amd64 4.4.0-66.87 2017-03-26 06:33:43 status half-installed linux-image-extra-4.4.0-66-generic:amd64 4.4.0-66.87 2017-03-26 06:33:46 status unpacked linux-image-extra-4.4.0-66-generic:amd64 4.4.0-66.87 2017-03-26 06:33:46 status unpacked linux-image-extra-4.4.0-66-generic:amd64 4.4.0-66.87 2017-03-26 06:33:46 install linux-image-generic:amd64 4.4.0.66.70 2017-03-26 06:33:46 status half-installed linux-image-generic:amd64 4.4.0.66.70 2017-03-26 06:33:46 status unpacked linux-image-generic:amd64 4.4.0.66.70 2017-03-26 06:33:46 status unpacked linux-image-generic:amd64 4.4.0.66.70 2017-03-26 06:33:46 install linux-headers-4.4.0-66:all 4.4.0-66.87 2017-03-26 06:33:46 status half-installed linux-headers-4.4.0-66:all 4.4.0-66.87 2017-03-26 06:33:48 status unpacked linux-headers-4.4.0-66:all 4.4.0-66.87 2017-03-26 06:33:48 status unpacked linux-headers-4.4.0-66:all 4.4.0-66.87 2017-03-26 06:33:48 install linux-headers-4.4.0-66-generic:amd64 4.4.0-66.87 2017-03-26 06:33:48 status half-installed linux-headers-4.4.0-66-generic:amd64 4.4.0-66.87 2017-03-26 06:33:48 status unpacked linux-headers-4.4.0-66-generic:amd64 4.4.0-66.87 2017-03-26 06:33:48 status unpacked linux-headers-4.4.0-66-generic:amd64 4.4.0-66.87 2017-03-26 06:33:48 install linux-headers-generic:amd64 4.4.0.66.70 2017-03-26 06:33:48 status half-installed linux-headers-generic:amd64 4.4.0.66.70 2017-03-26 06:33:48 status unpacked linux-headers-generic:amd64 4.4.0.66.70 2017-03-26 06:33:48 status unpacked linux-headers-generic:amd64 4.4.0.66.70 2017-03-26 06:33:48 install linux-generic:amd64 4.4.0.66.70 2017-03-26 06:33:48 status half-installed linux-generic:amd64 4.4.0.66.70 2017-03-26 06:33:48 status unpacked linux-generic:amd64 4.4.0.66.70 2017-03-26 06:33:48 status unpacked linux-generic:amd64 4.4.0.66.70 2017-03-26 06:33:48 install mesa-
[Bug 1676102] Re: 375.39 cannot install on EFI booted ubuntu 16.04 kernel 4.8.0-41-generic
** Description changed: I have been trying to install the default nvidia 375.39 driver that is provided in the latest Ubuntu 16.04.2 LTS iso for a few days. The installed Ubuntu 16.04 is EFI booted from a M.2 NVME BPX SSD attached to a ASUS Z170M-Plus mob. $ uname -r returns 4.8.0-41-generic $ uname -v returns #44~16.04.1-Ubuntu SMP Fri Mar 3 17:11:16 UTC 2017 $ [ -d /sys/firmware/efi ] && echo "EFI boot on HDD" || echo "Legacy boot on HDD" returns EFI boot on HDD - mob uefi settings: Fast Boot[Disabled], tried CSM [Enabled] and [Disabled], + mob uefi settings: Fast Boot[Disabled], tried CSM [Enabled] and [Disabled], After many installation attempts over a few days, I always found that the nvidia installation simply cannot complete the installation - procedure and run "forever" on a single processor; I have allowed the + procedure and runs "forever" on a single processor; I have allowed the installation to run through the night and it was still installing the next day. - Is there a bug preventing the installation? + Is there a bug preventing the installation or is there some settings I + need to perform to get it to complete the installation? Has anyone successfully installed the 375.39 driver on the 4.8.0-41-generic kernel for EFI booted Ubuntu 16.04? If yes, can you share how you achieve it? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1676102 Title: 375.39 cannot install on EFI booted ubuntu 16.04 kernel 4.8.0-41-generic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-375/+bug/1676102/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1676102] [NEW] 375.39 cannot install on EFI booted ubuntu 16.04 kernel 4.8.0-41-generic
Public bug reported: I have been trying to install the default nvidia 375.39 driver that is provided in the latest Ubuntu 16.04.2 LTS iso for a few days. The installed Ubuntu 16.04 is EFI booted from a M.2 NVME BPX SSD attached to a ASUS Z170M-Plus mob. $ uname -r returns 4.8.0-41-generic $ uname -v returns #44~16.04.1-Ubuntu SMP Fri Mar 3 17:11:16 UTC 2017 $ [ -d /sys/firmware/efi ] && echo "EFI boot on HDD" || echo "Legacy boot on HDD" returns EFI boot on HDD mob uefi settings: Fast Boot[Disabled], tried CSM [Enabled] and [Disabled], After many installation attempts over a few days, I always found that the nvidia installation simply cannot complete the installation procedure and run "forever" on a single processor; I have allowed the installation to run through the night and it was still installing the next day. Is there a bug preventing the installation? Has anyone successfully installed the 375.39 driver on the 4.8.0-41-generic kernel for EFI booted Ubuntu 16.04? If yes, can you share how you achieve it? ** Affects: nvidia-graphics-drivers-375 (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/1676102 Title: 375.39 cannot install on EFI booted ubuntu 16.04 kernel 4.8.0-41-generic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-375/+bug/1676102/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1582496] Re: GLib-GObject-CRITICAL failures during Ubuntu 16.04 bootup
It's coming to a year since I reported this issue. Below are the messages plaguing my syslog when Nautilus is started and when I press the items on the left are pressed. The look to be the same issues. I am using: kernel 4.4.0-64-generic nautilus 1:3.18.4.is.3.14.3-0ubuntu5. libglib-perl 3:1.320-2 libglib2.0-0:amd64 2.48.2-0ubuntu1 Can an importance be defined and someone fix them? Mar 12 22:14:46 Eliot gnome-session[2264]: message repeated 5 times: [ (nautilus:2558): Gtk-CRITICAL **: gtk_container_foreach: assertion 'GTK_IS_CONTAINER (container)' failed] Mar 12 22:15:05 Eliot gnome-session[2264]: (nautilus:26639): GLib-GIO-CRITICAL **: g_dbus_interface_skeleton_unexport: assertion 'interface_->priv->connections != NULL' failed Mar 12 22:15:05 Eliot gnome-session[2264]: (nautilus:26639): GLib-GIO-CRITICAL **: g_dbus_interface_skeleton_unexport: assertion 'interface_->priv->connections != NULL' failed Mar 12 22:15:05 Eliot gnome-session[2264]: (nautilus:26639): Gtk-CRITICAL **: gtk_icon_theme_get_for_screen: assertion 'GDK_IS_SCREEN (screen)' failed Mar 12 22:15:05 Eliot gnome-session[2264]: (nautilus:26639): GLib-GObject-WARNING **: invalid (NULL) pointer instance Mar 12 22:15:05 Eliot gnome-session[2264]: (nautilus:26639): GLib-GObject-CRITICAL **: g_signal_connect_object: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed Mar 12 22:15:05 Eliot dbus[1432]: [system] Activating via systemd: service name='org.freedesktop.hostname1' unit='dbus-org.freedesktop.hostname1.service' Mar 12 22:15:05 Eliot gnome-session[2264]: ** (nautilus:2558): CRITICAL **: nautilus_menu_provider_get_background_items: assertion 'NAUTILUS_IS_MENU_PROVIDER (provider)' failed Mar 12 22:15:05 Eliot systemd[1]: Starting Hostname Service... Mar 12 22:15:05 Eliot dbus[1432]: [system] Successfully activated service 'org.freedesktop.hostname1' Mar 12 22:15:05 Eliot systemd[1]: Started Hostname Service. Mar 12 22:15:13 Eliot gnome-session[2264]: ** (nautilus:2558): CRITICAL **: nautilus_menu_provider_get_background_items: assertion 'NAUTILUS_IS_MENU_PROVIDER (provider)' failed Mar 12 22:15:15 Eliot gnome-session[2264]: message repeated 2 times: [ ** (nautilus:2558): CRITICAL **: nautilus_menu_provider_get_background_items: assertion 'NAUTILUS_IS_MENU_PROVIDER (provider)' failed] Mar 12 22:15:16 Eliot gnome-session[2264]: ** (nautilus:2558): CRITICAL **: nautilus_menu_provider_get_background_items: assertion 'NAUTILUS_IS_MENU_PROVIDER (provider)' failed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1582496 Title: GLib-GObject-CRITICAL failures during Ubuntu 16.04 bootup To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1582496/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1553690] Re: Lenovo Y700-17ISK: ACPI Errors
I don't have this error anymore with kernel 4.4.0-64-generic. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1553690 Title: Lenovo Y700-17ISK: ACPI Errors To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1553690/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1667158] Re: Borders of pop-up windows are displayed badly
@claraferreira6 I tested my script on 16.04 with 375.39. Gratitude to @experimancer for sharing his solution. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1667158 Title: Borders of pop-up windows are displayed badly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-375/+bug/1667158/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1575484] Re: "Set document metadata failed"
(gedit:3616): Gtk-WARNING **: Theme parsing error: gtk.css:4:12: 'min- height' is not a valid property name (gedit:3616): Gtk-WARNING **: Theme parsing error: gtk.css:10:12: 'min- height' is not a valid property name (gedit:3616): Gtk-WARNING **: Calling Inhibit failed: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.gnome.SessionManager was not provided by any .service files ** (gedit:3616): WARNING **: Set document metadata failed: Setting attribute metadata::gedit-spell-enabled not supported ** (gedit:3616): WARNING **: Set document metadata failed: Setting attribute metadata::gedit-encoding not supported ** (gedit:3616): WARNING **: Set document metadata failed: Setting attribute metadata::gedit-position not supported In Ubuntu 16.04, First 2 warning/error --- appears when gedit starts. 3rd warning/error --- don't know the reason Last 3 warnings --- appears when save button was pressed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1575484 Title: "Set document metadata failed" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1575484/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1667158] Re: Borders of pop-up windows are displayed badly
A better temporary solution until Nvidia fixes the real issue... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1667158 Title: Borders of pop-up windows are displayed badly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-375/+bug/1667158/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1667158] Re: Borders of pop-up windows are displayed badly
@experimancer Thank you for sharing. Given that simply killing compiz process fixes the bad border problem, I have tested a solution that works on my Ubuntu 16.04 system every time after the system wakes. 2 steps solution. Hope it can help others. Step 1: === I created a script called "fixbadborders" in the directory /lib/systemd/system-sleep. It contained the following: #!/bin/sh ## This file (or a link to it) must be in the folder /lib/systemd/system-sleep/ ## Purpose: Kill compiz after system wakes up from sleep. ## This will fix bad window borders caused by Nvidia driver 375.39. kill $(ps -C compiz -o pid=) Step 2: === Allowed the script to have executable permission with: sudo chmod +x fixbadborders -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1667158 Title: Borders of pop-up windows are displayed badly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-375/+bug/1667158/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1349740] Re: acpi PNP0A08:00: _OSC failed (AE_ERROR); disabling ASPM
I found the reason for error message. It was caused by my system BIOS setting. Motherboard: ASUS Z170M-Plus Driver: Z170M-PLUS BIOS 3301 updated 2017/03/02 (latest driver when posting this comment) In BIOS main, I went to Advanced --> Platform Msc Configuration. In this page, I had to set: - PCI Express Native Power Management Enabled - Native ASPM Enabled Enabling the latter parameter allowed OS to managed ASPM while disabling it meant that BIOS managed ASPM of PCIe. In my case, Native ASPM was Disabled and this caused the error. [0.201657], acpi PNP0A08:00: _OSC: OS now controls [PCIeHotplug PME AER PCIeCapability] now replaced [ 0.186376] acpi PNP0A08:00: _OSC failed (AE_ERROR); disabling ASPM $ dmesg | grep acpi [0.00] ACPI: LAPIC_NMI (acpi_id[0x01] high edge lint[0x1]) [0.00] ACPI: LAPIC_NMI (acpi_id[0x02] high edge lint[0x1]) [0.00] ACPI: LAPIC_NMI (acpi_id[0x03] high edge lint[0x1]) [0.00] ACPI: LAPIC_NMI (acpi_id[0x04] high edge lint[0x1]) [0.00] ACPI: LAPIC_NMI (acpi_id[0x05] high edge lint[0x1]) [0.00] ACPI: LAPIC_NMI (acpi_id[0x06] high edge lint[0x1]) [0.00] ACPI: LAPIC_NMI (acpi_id[0x07] high edge lint[0x1]) [0.00] ACPI: LAPIC_NMI (acpi_id[0x08] high edge lint[0x1]) [0.157543] acpiphp: ACPI Hot Plug PCI Controller Driver version: 0.5 [0.200629] acpi PNP0A08:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI] [0.201657] acpi PNP0A08:00: _OSC: OS now controls [PCIeHotplug PME AER PCIeCapability] [0.209567] acpiphp: Slot [1] registered [0.209618] acpiphp: Slot [1-1] registered [0.234384] clocksource: acpi_pm: mask: 0xff max_cycles: 0xff, max_idle_ns: 2085701024 ns sunbear1604@Eliot:~$ dmesg | grep ASPM [0.200629] acpi PNP0A08:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI] -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1349740 Title: acpi PNP0A08:00: _OSC failed (AE_ERROR); disabling ASPM To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1349740/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1349740] Re: acpi PNP0A08:00: _OSC failed (AE_ERROR); disabling ASPM
@colin-king. Noted. So what is causing the "acpi PNP0A08:00: _OSC failed (AE_ERROR); disabling ASPM"? Btw, what is a FADT? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1349740 Title: acpi PNP0A08:00: _OSC failed (AE_ERROR); disabling ASPM To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1349740/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1349740] Re: acpi PNP0A08:00: _OSC failed (AE_ERROR); disabling ASPM
I am reporting the same issue in UBUNTU 16.04 LTS 4.4.0-64-generic. [0.186376] acpi PNP0A08:00: _OSC failed (AE_ERROR); disabling ASPM I noticed the following messages preceding this error message. [0.144970] ACPI FADT declares the system doesn't support PCIe ASPM, so disable it [0.172842] ACPI: Interpreter enabled [0.172864] ACPI: (supports S0 S3 S4 S5) [0.172865] ACPI: Using IOAPIC for interrupt routing [0.172885] PCI: Using host bridge windows from ACPI; if necessary, use "pci=nocrs" and report a bug In my BIOS setting, I have "Charging USB devices in Power State S5" as "Enabled". However, my USB still do not have power. I would like to know if the error is the reason for why I can't get power from my USB during suspend/hibernation mode. $ dmesg | grep acpi [0.00] ACPI: LAPIC_NMI (acpi_id[0x01] high edge lint[0x1]) [0.00] ACPI: LAPIC_NMI (acpi_id[0x02] high edge lint[0x1]) [0.00] ACPI: LAPIC_NMI (acpi_id[0x03] high edge lint[0x1]) [0.00] ACPI: LAPIC_NMI (acpi_id[0x04] high edge lint[0x1]) [0.00] ACPI: LAPIC_NMI (acpi_id[0x05] high edge lint[0x1]) [0.00] ACPI: LAPIC_NMI (acpi_id[0x06] high edge lint[0x1]) [0.00] ACPI: LAPIC_NMI (acpi_id[0x07] high edge lint[0x1]) [0.00] ACPI: LAPIC_NMI (acpi_id[0x08] high edge lint[0x1]) [0.144971] acpiphp: ACPI Hot Plug PCI Controller Driver version: 0.5 [0.186356] acpi PNP0A08:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI] [0.186376] acpi PNP0A08:00: _OSC failed (AE_ERROR); disabling ASPM [0.198599] acpiphp: Slot [1] registered [0.198650] acpiphp: Slot [1-1] registered [0.198695] acpiphp: Slot [1-2] registered [0.222862] clocksource: acpi_pm: mask: 0xff max_cycles: 0xff, max_idle_ns: 2085701024 ns $ dmesg | grep ACPI [0.00] BIOS-e820: [mem 0xb295f000-0xb2994fff] ACPI data [0.00] BIOS-e820: [mem 0xb2d37000-0xb2d37fff] ACPI NVS [0.00] BIOS-e820: [mem 0xc2546000-0xc2558fff] ACPI data [0.00] BIOS-e820: [mem 0xc2a14000-0xc2d3bfff] ACPI NVS [0.00] efi: ACPI 2.0=0xb295f000 ACPI=0xb295f000 SMBIOS=0xc3205000 SMBIOS 3.0=0xc3204000 ESRT=0xbe11a098 [0.00] ACPI: Early table checksum verification disabled [0.00] ACPI: RSDP 0xB295F000 24 (v02 ALASKA) [0.00] ACPI: XSDT 0xB295F0A8 CC (v01 ALASKA A M I 01072009 AMI 00010013) [0.00] ACPI: FACP 0xB2988600 000114 (v06 ALASKA A M I 01072009 AMI 00010013) [0.00] ACPI: DSDT 0xB295F210 0293EF (v02 ALASKA A M I 01072009 INTL 20160422) [0.00] ACPI: FACS 0xC2D3BC40 40 [0.00] ACPI: APIC 0xB2988718 BC (v03 ALASKA A M I 01072009 AMI 00010013) [0.00] ACPI: FPDT 0xB29887D8 44 (v01 ALASKA A M I 01072009 AMI 00010013) [0.00] ACPI: DMAR 0xB2993F68 A8 (v01 INTEL SKL 0001 INTL 0001) [0.00] ACPI: MCFG 0xB2988878 3C (v01 ALASKA A M I 01072009 MSFT 0097) [0.00] ACPI: SSDT 0xB29888B8 000390 (v01 SataRe SataTabl 1000 INTL 20160422) [0.00] ACPI: FIDT 0xB2988C48 9C (v01 ALASKA A M I 01072009 AMI 00010013) [0.00] ACPI: SSDT 0xB2988CE8 003041 (v02 SaSsdt SaSsdt 3000 INTL 20160422) [0.00] ACPI: SSDT 0xB298BD30 002544 (v02 PegSsd PegSsdt 1000 INTL 20160422) [0.00] ACPI: HPET 0xB298E278 38 (v01 INTEL SKL 0001 MSFT 005F) [0.00] ACPI: SSDT 0xB298E2B0 000E3B (v02 INTEL Ther_Rvp 1000 INTL 20160422) [0.00] ACPI: SSDT 0xB298F0F0 000B1D (v02 INTEL xh_rvp08 INTL 20160422) [0.00] ACPI: UEFI 0xB298FC10 42 (v01 INTEL EDK2 0002 0113) [0.00] ACPI: SSDT 0xB298FC58 000EDE (v02 CpuRef CpuSsdt 3000 INTL 20160422) [0.00] ACPI: LPIT 0xB2990B38 94 (v01 INTEL SKL MSFT 005F) [0.00] ACPI: WSMT 0xB2990BD0 28 (v01 INTEL SKL MSFT 005F) [0.00] ACPI: SSDT 0xB2990BF8 00029F (v02 INTEL sensrhub INTL 20160422) [0.00] ACPI: SSDT 0xB2990E98 003002 (v02 INTEL PtidDevc 1000 INTL 20160422) [0.00] ACPI: DBGP 0xB2993EA0 34 (v01 INTEL 0002 MSFT 005F) [0.00] ACPI: DBG2 0xB2993ED8 54 (v00 INTEL 0002 MSFT 005F) [0.00] ACPI: BGRT 0xB2993F30 38 (v01 ALASKA A M I 01072009 AMI 00010013) [0.00] ACPI: Local APIC address 0xfee0 [0.00] ACPI: PM-Timer IO Port: 0x1808 [0.00] ACPI: Local APIC address 0xfee0 [0.00] ACPI: LAPIC_NMI (acpi_id[0x01] high edge lint[0x1]) [0.00] ACPI: LAPIC_NMI (acpi_id[0x02] high edge lint[0x1]) [0.00
[Bug 1668101] Re: Graphical artifacts after resuming from sleep mode with nvidia drivers
*** This bug is a duplicate of bug 1667158 *** https://bugs.launchpad.net/bugs/1667158 This bug is the same as https://bugs.launchpad.net/ubuntu/+source /nvidia-graphics-drivers-375/+bug/1667158. I had reported this bug previously but so far the maintainer of this package has not assigned the issue to anyone to follow up. Is there a way to link your report to mine? You can also see some temporary workarounds discussed there. ** This bug has been marked a duplicate of bug 1667158 Borders of pop-up windows are displayed badly -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1668101 Title: Graphical artifacts after resuming from sleep mode with nvidia drivers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-375/+bug/1668101/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1661287] Re: Canon printer failed to connect with CUPS
I found the answer. I checked "apt" history log in /var/log/apt and discovered that when I executed the "apt-get install ubuntu-desktop", the "ubuntu-desktop" package installed many cups packages (see below). These installations fixed whatever problems cups had previously. Wish someone could have just told me about this simple solution to fixing cups. Start-Date: 2017-02-25 19:10:43 Commandline: apt-get install ubuntu-desktop Requested-By: sunbear (1000) Install: python3-pexpect:amd64 (4.0.1-1, automatic), hplip-data:amd64 (3.16.3+repack0-1, automatic), libqpdf17:amd64 (6.0.0-2, automatic), liblouisutdml-data:amd64 (2.5.0-3, automatic), printer-driver-splix:amd64 (2.0.0+svn315-4fakesync1, automatic), bluez-cups:amd64 (5.37-0ubuntu5, automatic), printer-driver-hpcups:amd64 (3.16.3+repack0-1, automatic), printer-driver-postscript-hp:amd64 (3.16.3+repack0-1, automatic), libsnmp-base:amd64 (5.7.3+dfsg-1ubuntu4, automatic), python3-reportlab-accel:amd64 (3.3.0-1, automatic), ubuntu-desktop:amd64 (1.361), printer-driver-pxljr:amd64 (1.4+repack0-4, automatic), cups-server-common:amd64 (2.1.3-4, automatic), ssl-cert:amd64 (1.0.37, automatic), python3-renderpm:amd64 (3.3.0-1, automatic), cups-filters:amd64 (1.8.3-2ubuntu3.1, automatic), libsnmp30:amd64 (5.7.3+dfsg-1ubuntu4, automatic), libcupsmime1:amd64 (2.1.3-4, automatic), hplip:amd64 (3.16.3+repack0-1, automatic), liblouisutdml6:amd64 (2.5.0-3, automatic), libhpmud0:amd64 (3.16.3+repack0- 1, automatic), printer-driver-gutenprint:amd64 (5.2.11-1, automatic), libfontembed1:amd64 (1.8.3-2ubuntu3.1, automatic), libgutenprint2:amd64 (5.2.11-1, automatic), liblouisutdml-bin:amd64 (2.5.0-3, automatic), libsane-hpaio:amd64 (3.16.3+repack0-1, automatic), qpdf:amd64 (6.0.0-2, automatic), cups-filters-core-drivers:amd64 (1.8.3-2ubuntu3.1, automatic), python3-ptyprocess:amd64 (0.5-1, automatic), cups-core-drivers:amd64 (2.1.3-4, automatic), cups-daemon:amd64 (2.1.3-4, automatic), python3-reportlab:amd64 (3.3.0-1, automatic), cups:amd64 (2.1.3-4, automatic), libcupscgi1:amd64 (2.1.3-4, automatic), cups-browsed:amd64 (1.8.3-2ubuntu3.1, automatic) Remove: foomatic-filters:amd64 (4.0.17-8) End-Date: 2017-02-25 19:11:16 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1661287 Title: Canon printer failed to connect with CUPS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1661287/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1661287] Re: Canon printer failed to connect with CUPS
After switching the connection of the printer in the printer properties, from USB type to using the printer DNNS, my Canon printer is able to print again. In the make and mode, it shows Canon MG5300 series - CUPS+Gutenprint v5.2.11. It is puzzling how cups is not able to detect my printer. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1661287 Title: Canon printer failed to connect with CUPS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1661287/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1667158] Re: Borders of pop-up windows are displayed badly
I uninstalled this ppa and the 375.39 driver. In it's place, I ran the NVIDIA-Linux-x86_64-375.39.run (NVIDIA's installation file) to install the 375.39 driver to see if these problems would go away or still occur. Verdict, the same driver issues I had described previously also occurs. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1667158 Title: Borders of pop-up windows are displayed badly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-375/+bug/1667158/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1667158] Re: Borders of pop-up windows are displayed badly
The other work around I found was to click an effect in CompizConfig Setting Manager --> Effects. Some command is run at the backend which fixes the bad borders. I also notice another issue with the new driver. The minimise button of the widow can fail to work. Also, sometimes the mouse click becomes unresponsive. I have to click the maximise button twice (i.e. the window will maximise and then revert to its normal size before it can work again) to resolve these issues. Hope these findings can give insights to fix these bugs. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1667158 Title: Borders of pop-up windows are displayed badly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-375/+bug/1667158/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1667158] Re: Borders of pop-up windows are displayed badly
I just had my system awaken from suspend mode and bad borders around pop up windows reappeared again. I confirm that my issue has not been resolved by what i did earlier. Attached image shows my issue. ** Attachment added: "bad_borders cause by NV graphic driver upgrade to 375.39 .png" https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-375/+bug/1667158/+attachment/4825174/+files/bad_borders%20cause%20by%20NV%20graphic%20driver%20upgrade%20to%20375.39%20.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1667158 Title: Borders of pop-up windows are displayed badly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-375/+bug/1667158/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1667158] Re: Borders of pop-up windows are displayed badly
I found a way to eliminate the problem (I think). I went into CompizConfig Setting Manager --> Effects and turned off all the effects like wobbling, water effect, motion blur and fading window). I don't not if the problem will reoccur but so far the border problems have stopped appearing and every thing is good again. Monitoring the situation. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1667158 Title: Borders of pop-up windows are displayed badly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-375/+bug/1667158/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1667158] [NEW] Borders of pop-up windows are displayed badly
Public bug reported: My system graphic driver had just updated to 375.39 but Borders of pop- up windows are displayed badly. This is especially true after waking up from suspend mode. this driver is buggy. I am using Ubuntu 16.04. Any way to rectify this display problem? ** Affects: nvidia-graphics-drivers-375 (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/1667158 Title: Borders of pop-up windows are displayed badly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-375/+bug/1667158/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1661287] Re: Canon printer failed to connect with CUPS
I have gone into https://wiki.ubuntu.com/DebuggingPrintingProblems and tried to follow the instructions of the "CUPS error_log" section. Step 1. I can't do it. Can't find "Save debugging information for troubleshooting" on "System" -> "Administration" -> "Printing". I have System Setting --> Printers --> Help --> Troubleshoot --> Forward. I get the message CUPS Service Stopped The CUPS print speel does not appear to be running. To correct this, choose System-Administration-Services from main menu and look for 'cups' service. My difficulty is there isn't such a path to follow. The is no Administration icon. Step 2: @Eliot:~$ cupsctl LogLevel=debug cupsctl: Unable to connect to server: Bad file descriptor Step 3: Skipped - Not applicable. Step4: I have gone into /etc/cups/cupsd.conf and manually uncommented LogLevel Original: # Deactivate CUPS' internal logrotating, as we provide a better one, especially # LogLevel debug2 gets usable now MaxLogSize 0 Presently: # Deactivate CUPS' internal logrotating, as we provide a better one, especially LogLevel debug2 gets usable now MaxLogSize 0 @Eliot:~$ $ sudo /etc/init.d/cups restart $: command not found The file is there. I believe Ubuntu16.04 is using systemd. I tried this and got the below failure message. @Eliot:~$ sudo systemctl restart /etc/systemd/system/cups.service Failed to restart etc-systemd-system-cups.service.mount: Unit etc-systemd-system-cups.service.mount not found. Unable to do Step 5,6, 7, 8. On 03/02/2017 05:32, Till Kamppeter wrote: > Your syslog contains: > > Feb 2 22:36:43 Eliot udev-configure-printer[5761]: failed to connect to > CUPS server; giving up > > and you also get > > @Eliot:~$ lpinfo -v > lpinfo: Bad file descriptor > > Seems that there is a problem with the CUPS daemon not starting. > > Please run the command > > ls -l /var/run/cups/cups.sock > > and post the output here. > > Also attach your files /etc/cups/cupsd.conf and /etc/cups/cups- > files.conf. > > Go to > > https://wiki.ubuntu.com/DebuggingPrintingProblems > > and follow the instructions of the "CUPS error_log" section. > > Please attach the files one by one, do not compress them and do not > package them together, thanks. > > ** Changed in: cups (Ubuntu) > Status: New => Incomplete > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1661287 Title: Canon printer failed to connect with CUPS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1661287/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1661287] Re: Canon printer failed to connect with CUPS
/etc/cups/cupsd.conf attached. On 03/02/2017 05:32, Till Kamppeter wrote: > Your syslog contains: > > Feb 2 22:36:43 Eliot udev-configure-printer[5761]: failed to connect to > CUPS server; giving up > > and you also get > > @Eliot:~$ lpinfo -v > lpinfo: Bad file descriptor > > Seems that there is a problem with the CUPS daemon not starting. > > Please run the command > > ls -l /var/run/cups/cups.sock > > and post the output here. > > Also attach your files /etc/cups/cupsd.conf and /etc/cups/cups- > files.conf. > > Go to > > https://wiki.ubuntu.com/DebuggingPrintingProblems > > and follow the instructions of the "CUPS error_log" section. > > Please attach the files one by one, do not compress them and do not > package them together, thanks. > > ** Changed in: cups (Ubuntu) > Status: New => Incomplete > ** Attachment added: "cupsd.conf" https://bugs.launchpad.net/bugs/1661287/+attachment/4813838/+files/cupsd.conf -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1661287 Title: Canon printer failed to connect with CUPS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1661287/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1661287] Re: Canon printer failed to connect with CUPS
/etc/cups/cups-files.conf attached. On 03/02/2017 05:32, Till Kamppeter wrote: > /etc/cups/cups- > files.conf. ** Attachment added: "cups-files.conf" https://bugs.launchpad.net/bugs/1661287/+attachment/4813839/+files/cups-files.conf -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1661287 Title: Canon printer failed to connect with CUPS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1661287/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1661287] Re: Canon printer failed to connect with CUPS
@Eliot:/media$ ls -l /var/run/cups/cups.sock ls: cannot access '/var/run/cups/cups.sock': No such file or directory However, I found /etc/systemd/system/cups.socket /var/lib/systemd/deb-systemd-helper-masked/cups.socket /etc/systemd/system/sockets.target.wants/cups.socket /var/lib/systemd/deb-systemd-helper-enabled/cups.socket.dsh-also /var/lib/systemd/deb-systemd-helper- enabled/sockets.target.wants/cups.socket On 03/02/2017 05:32, Till Kamppeter wrote: > Your syslog contains: > > Feb 2 22:36:43 Eliot udev-configure-printer[5761]: failed to connect to > CUPS server; giving up > > and you also get > > @Eliot:~$ lpinfo -v > lpinfo: Bad file descriptor > > Seems that there is a problem with the CUPS daemon not starting. > > Please run the command > > ls -l /var/run/cups/cups.sock > > and post the output here. > > Also attach your files /etc/cups/cupsd.conf and /etc/cups/cups- > files.conf. > > Go to > > https://wiki.ubuntu.com/DebuggingPrintingProblems > > and follow the instructions of the "CUPS error_log" section. > > Please attach the files one by one, do not compress them and do not > package them together, thanks. > > ** Changed in: cups (Ubuntu) > Status: New => Incomplete > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1661287 Title: Canon printer failed to connect with CUPS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1661287/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1661305] [NEW] Many Gtk-CRITICAL and GLib-GIO-CRITICAL failures in syslog during startup and shutdown of nautilus
Public bug reported: I have this installed: nautilus 1:3.18.4.is.3.14.3-0ubuntu5 Is there a way to resolve these many critical failure messages by nautilus. I get them whenever I start or close nautilus. See below: Feb 2 23:41:59 Eliot gnome-session[2247]: (nautilus:2465): Gtk-CRITICAL **: gtk_container_foreach: assertion 'GTK_IS_CONTAINER (container)' failed Feb 2 23:41:59 Eliot gnome-session[2247]: message repeated 5 times: [ (nautilus:2465): Gtk-CRITICAL **: gtk_container_foreach: assertion 'GTK_IS_CONTAINER (container)' failed] Feb 2 23:42:17 Eliot gnome-session[2247]: (nautilus:7279): GLib-GIO-CRITICAL **: g_dbus_interface_skeleton_unexport: assertion 'interface_->priv->connections != NULL' failed Feb 2 23:42:17 Eliot gnome-session[2247]: (nautilus:7279): GLib-GIO-CRITICAL **: g_dbus_interface_skeleton_unexport: assertion 'interface_->priv->connections != NULL' failed Feb 2 23:42:17 Eliot gnome-session[2247]: (nautilus:7279): Gtk-CRITICAL **: gtk_icon_theme_get_for_screen: assertion 'GDK_IS_SCREEN (screen)' failed Feb 2 23:42:17 Eliot gnome-session[2247]: (nautilus:7279): GLib-GObject-WARNING **: invalid (NULL) pointer instance Feb 2 23:42:17 Eliot gnome-session[2247]: (nautilus:7279): GLib-GObject-CRITICAL **: g_signal_connect_object: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed Feb 2 23:42:17 Eliot dbus[1469]: [system] Activating via systemd: service name='org.freedesktop.hostname1' unit='dbus-org.freedesktop.hostname1.service' Feb 2 23:42:17 Eliot systemd[1]: Starting Hostname Service... Feb 2 23:42:17 Eliot gnome-session[2247]: ** (nautilus:2465): CRITICAL **: nautilus_menu_provider_get_background_items: assertion 'NAUTILUS_IS_MENU_PROVIDER (provider)' failed Feb 2 23:42:17 Eliot dbus[1469]: [system] Successfully activated service 'org.freedesktop.hostname1' Feb 2 23:42:17 Eliot systemd[1]: Started Hostname Service. Feb 2 23:43:28 Eliot gnome-session[2247]: (nautilus:2465): Gtk-CRITICAL **: gtk_container_foreach: assertion 'GTK_IS_CONTAINER (container)' failed I also get many other failure messages in syslogs just by clicking different parts of nautilus. For example: Feb 2 23:41:59 Eliot gnome-session[2247]: (nautilus:2465): Gtk-CRITICAL **: gtk_container_foreach: assertion 'GTK_IS_CONTAINER (container)' failed Feb 2 23:41:59 Eliot gnome-session[2247]: message repeated 5 times: [ (nautilus:2465): Gtk-CRITICAL **: gtk_container_foreach: assertion 'GTK_IS_CONTAINER (container)' failed] Feb 2 23:42:17 Eliot gnome-session[2247]: (nautilus:7279): GLib-GIO-CRITICAL **: g_dbus_interface_skeleton_unexport: assertion 'interface_->priv->connections != NULL' failed Feb 2 23:42:17 Eliot gnome-session[2247]: (nautilus:7279): GLib-GIO-CRITICAL **: g_dbus_interface_skeleton_unexport: assertion 'interface_->priv->connections != NULL' failed Feb 2 23:42:17 Eliot gnome-session[2247]: (nautilus:7279): Gtk-CRITICAL **: gtk_icon_theme_get_for_screen: assertion 'GDK_IS_SCREEN (screen)' failed Feb 2 23:42:17 Eliot gnome-session[2247]: (nautilus:7279): GLib-GObject-WARNING **: invalid (NULL) pointer instance Feb 2 23:42:17 Eliot gnome-session[2247]: (nautilus:7279): GLib-GObject-CRITICAL **: g_signal_connect_object: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed Feb 2 23:42:17 Eliot gnome-session[2247]: ** (nautilus:2465): CRITICAL **: nautilus_menu_provider_get_background_items: assertion 'NAUTILUS_IS_MENU_PROVIDER (provider)' failed Feb 2 23:43:28 Eliot gnome-session[2247]: (nautilus:2465): Gtk-CRITICAL **: gtk_container_foreach: assertion 'GTK_IS_CONTAINER (container)' failed ** Affects: nautilus (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/1661305 Title: Many Gtk-CRITICAL and GLib-GIO-CRITICAL failures in syslog during startup and shutdown of nautilus To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1661305/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1661287] [NEW] Canon printer failed to connect with CUPS
Public bug reported: My canon printer has been working with Ubuntu 16.04 for quite sometime. Presently, for no reason, it now cannot be recognised. I have checked that the USB connections are working fine. When I unplug and replug the printer usb connection to my computer the syslog reflects it's present. However, it shows that it failed to connect with CUPS. udev-configure- printer[5761]: failed to connect to CUPS server; giving up I have provide the results to my printer checks below. Appreciate help to reestablish the proper connection of my printer and get it working with Ubuntu 16.04. tail -f /var/log/syslog Feb 2 22:36:38 Eliot kernel: [95807.581378] usb 1-14: New USB device found, idVendor=04a9, idProduct=1754 Feb 2 22:36:38 Eliot kernel: [95807.581387] usb 1-14: New USB device strings: Mfr=1, Product=2, SerialNumber=3 Feb 2 22:36:38 Eliot kernel: [95807.581391] usb 1-14: Product: MG5300 series Feb 2 22:36:38 Eliot kernel: [95807.581395] usb 1-14: Manufacturer: Canon Feb 2 22:36:38 Eliot kernel: [95807.581399] usb 1-14: SerialNumber: 20EE62 Feb 2 22:36:38 Eliot kernel: [95807.591385] usblp 1-14:1.1: usblp0: USB Bidirectional printer dev 42 if 1 alt 0 proto 2 vid 0x04A9 pid 0x1754 Feb 2 22:36:38 Eliot kernel: [95807.591527] usb-storage 1-14:1.2: USB Mass Storage device detected Feb 2 22:36:38 Eliot kernel: [95807.593328] scsi host13: usb-storage 1-14:1.2 Feb 2 22:36:38 Eliot systemd[1]: Starting Automatic USB/Bluetooth printer setup (-devices-pci:00-:00:14.0-usb1-1\x2d14)... Feb 2 22:36:38 Eliot udev-configure-printer[5761]: add /devices/pci:00/:00:14.0/usb1/1-14 Feb 2 22:36:38 Eliot udev-configure-printer[5761]: device devpath is /devices/pci:00/:00:14.0/usb1/1-14 Feb 2 22:36:38 Eliot udev-configure-printer[5761]: MFG:Canon MDL:MG5300 series SERN:- serial:20EE62 Feb 2 22:36:39 Eliot kernel: [95808.591918] scsi 13:0:0:0: Direct-Access CanonMG5300 series0103 PQ: 0 ANSI: 2 Feb 2 22:36:39 Eliot kernel: [95808.592839] sd 13:0:0:0: Attached scsi generic sg6 type 0 Feb 2 22:36:39 Eliot kernel: [95808.597229] sd 13:0:0:0: [sdf] Attached SCSI removable disk Feb 2 22:36:43 Eliot udev-configure-printer[5761]: failed to connect to CUPS server; giving up Feb 2 22:36:43 Eliot systemd[1]: udev-configure-printer@-devices-pci:00-:00:14.0-usb1-1\x2d14.service: Control process exited, code=exited status=1 Feb 2 22:36:43 Eliot systemd[1]: Failed to start Automatic USB/Bluetooth printer setup (-devices-pci:00-:00:14.0-usb1-1\x2d14). Feb 2 22:36:43 Eliot systemd[1]: udev-configure-printer@-devices-pci:00-:00:14.0-usb1-1\x2d14.service: Unit entered failed state. Feb 2 22:36:43 Eliot systemd[1]: udev-configure-printer@-devices-pci:00-:00:14.0-usb1-1\x2d14.service: Failed with result 'exit-code'. @Eliot:~$ lsusb Bus 001 Device 043: ID 04a9:1754 Canon, Inc. @Eliot:~$ ls -l /dev/usb/lp* /dev/bus/usb/*/* crw-rw-r--+ 1 root lp 189, 42 Feb 2 22:40 /dev/bus/usb/001/043 crw-rw 1 root lp 180, 0 Feb 2 22:39 /dev/usb/lp0 @Eliot:~$ sudo usb_printerid /dev/usb/lp0 GET_DEVICE_ID string: MFG:Canon;CMD:BJL,BJRaster3,BSCCe,NCCe,IVEC,IVECPLI;SOJ:BJNP2,BJNPe;MDL:MG5300 series;CLS:PRINTER;DES:Canon MG5300 series;VER:1.030;STA:10;FSI:03;HRI:7;MSI:B030,DAT,E3,HFSF,JON,K21000700;PDR:6;PSE:ACFJ03117; @Eliot:~$ sudo usb_printerid /dev/bus/usb/001/043 Error: Inappropriate ioctl for device: GET_DEVICE_ID on '/dev/bus/usb/001/043' @Eliot:~$ lpinfo -v lpinfo: Bad file descriptor ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: cups (not installed) ProcVersionSignature: Ubuntu 4.4.0-59.80-generic 4.4.35 Uname: Linux 4.4.0-59-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 CurrentDesktop: Unity Date: Thu Feb 2 23:17:01 2017 InstallationDate: Installed on 2016-05-01 (277 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: cups UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: cups (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1661287 Title: Canon printer failed to connect with CUPS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1661287/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1641417] [NEW] Ubuntu 16.04 unable to detect/connect to and work properly with iPhone 4.
Public bug reported: Action 1: Plug an iPhone 4 to a just booted up Ubuntu 16.04 workstation. Result 1: 2 iPhone connections appear in Nautilus. 1st connect is mount via gphoto2, where access is limited to viewing and copying photos and videos. The 2nd connection that is mounted via afc fail to work, hence other folders in iPhone are not accessible. Action 2: Unplugged and re-plugged iPhone 4 to the workstation. Result 2: iPhone 4 does not reappear in Nautilus at all. No iPhone mount point appear. Checks and Remedy used: 1. "ideviceinfo" and lsusb command show iPhone 4 is connected. 2. "idevicepair validate" command shows "SUCCESS: Validated pairing with device [UDID]" 3. After running "ifuse /media/iPhone" command, iPhone 4 reappears in Nautilus as mounted in /media/iPhone. Furthermore, all folders of iPhone 4 appears and are accessible. I believe the 1st mounting of iPhone 4 on Nautilus is due to the "gvfs- backends" package. W/o it, auto detection/connection of iPhone 4 would not occur and appear in Nautilus. However, the afc mount failed to work The 2nd mounting is caused by ifuse. This works perfectly but requires manual mounting and unmounting. Questions: 1. How to overcome issues/failures mentioned in Result 1 & 2? 2. Ideally, i would like the automatic detection-connection between Ubuntu and iPhone to work. If not, is there a way to automate connection via ifuse? System and package info: $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 16.04.1 LTS Release:16.04 Codename: xenial $ uname -or 4.4.0-47-generic GNU/Linux $ dpkg -l | grep iPhone ii ifuse1.1.2-0.1build3 amd64 FUSE module for iPhone and iPod Touch devices ii libimobiledevice-utils 1.2.0+dfsg-3~ubuntu0.2 amd64 Library for communicating with iPhone and iPod Touch devices ii libimobiledevice6:amd64 1.2.0+dfsg-3~ubuntu0.2 amd64 Library for communicating with the iPhone and iPod Touch ii libusbmuxd-tools 1.0.10-2ubuntu0.1 amd64 USB multiplexor daemon for iPhone and iPod Touch devices - tools ii libusbmuxd4:amd641.0.10-2ubuntu0.1 amd64 USB multiplexor daemon for iPhone and iPod Touch devices - library ii usbmuxd 1.1.0-2 amd64 USB multiplexor daemon for iPhone and iPod Touch devices $ dpkg -l | grep libusb ii libgusb2:amd64 0.2.9-0ubuntu1 amd64 GLib wrapper around libusb1 ii libusb-0.1-4:amd64 2:0.1.12-28 amd64 userspace USB programming library ii libusb-1.0-0:amd64 2:1.0.20-1 amd64 userspace USB programming library ii libusb-1.0-0:i3862:1.0.20-1 i386userspace USB programming library ii libusbmuxd-tools 1.0.10-2ubuntu0.1 amd64 USB multiplexor daemon for iPhone and iPod Touch devices - tools ii libusbmuxd4:amd641.0.10-2ubuntu0.1 amd64 USB multiplexor daemon for iPhone and iPod Touch devices - library ii libusbredirhost1:amd64 0.7.1-1 amd64 Implementing the usb-host (*) side of a usbredir connection (runtime) ii libusbredirparser1:amd64 0.7.1-1 amd64 Parser for the usbredir protocol (runtime) $ dpkg -l | grep gvfs ii gvfs:amd64 1.28.2-1ubuntu1~16.04.1amd64 userspace virtual filesystem - GIO module ii gvfs-backends 1.28.2-1ubuntu1~16.04.1amd64 userspace virtual filesystem - backends ii gvfs-bin1.28.2-1ubuntu1~16.04.1amd64 userspace virtual filesystem - binaries ii gvfs-common 1.28.2-1ubuntu1~16.04.1alluserspace virtual filesystem - common data files ii gvfs-daemons1.28.2-1ubuntu1~16.04.1amd64 userspace virtual filesystem - servers ii gvfs-fuse 1.28.2-1ubuntu1~16.04.1amd64 userspace virtual filesystem - fuse server ii gvfs-libs:amd64 1.28.2-1ubuntu1~16.04.1amd64 userspace virtual filesystem - private libraries ** Affects: libimobiledevice (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/1641417 Title: Ubuntu 16.04 unable to detect/connect to and work properly with iPhone 4. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libimobiledevice/+bug/1641417/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1577168] Re: Browser hangs Ubuntu 16.04
Apologies for the delayed reply. I can run Web Browser now w/o any issue. Just tested it. On Wed, Oct 5, 2016 at 1:00 PM, Olivier Tilloy wrote: > @SunBear: are you still seeing the issue as initially described here, > with an up-to-date system? > > ** Changed in: webbrowser-app (Ubuntu) >Status: Expired => Incomplete > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1577168 > > Title: > Browser hangs Ubuntu 16.04 > > Status in webbrowser-app package in Ubuntu: > Incomplete > > Bug description: > When I activate Browser or click on Amazon button (which activates > Browser), Ubuntu 16.04 hangs. This occurrence should not happen. > An exception to this problem is that the mouse pointer is movable > initially. In the extreme case, the mouse pointer hangs also. > > This problem does not occur when activating Firefox or Chromium. > Occurs in a freshly installed Ubuntu 16.04 system. > Description: Ubuntu 16.04 LTS > Release: 16.04 > N: Unable to locate package pkgname > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/webbrowser-app/ > +bug/1577168/+subscriptions > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1577168 Title: Browser hangs Ubuntu 16.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/webbrowser-app/+bug/1577168/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1582982] Re: thermald 1.5-2ubuntu1 failures in ubuntu16.04
@Colin I have managed to recover my system after executing the recovery steps by http://askubuntu.com/questions/137655/boot-drops-to-a-initramfs-prompts-busybox. Phew! :) Updating you with my latest thermald bootup log (see below). $ cat /var/log/syslog | grep thermald May 29 23:55:20 Eliot thermald[1039]: 22 CPUID levels; family:model:stepping 0x6:5e:3 (6:94:3) May 29 23:55:20 Eliot thermald[1039]: Polling mode is enabled: 4 May 29 23:55:20 Eliot thermald[1039]: sysfs read failed constraint_0_max_power_uw May 29 23:55:20 Eliot thermald[1039]: sysfs write failed trip_point_0_temp May 29 23:55:20 Eliot thermald[1039]: sysfs write failed trip_point_0_temp It shows your upstream commit to downgrade my earlier reported failures (as shown) is appllied succesfully. They no longer appears. May 19 08:17:42 Eliot thermald[1086]: failed to open /dev/acpi_thermal_rel May 19 08:17:42 Eliot thermald[1086]: failed to open /dev/acpi_thermal_rel May 19 08:17:42 Eliot thermald[1086]: TRT/ART read failed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1582982 Title: thermald 1.5-2ubuntu1 failures in ubuntu16.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thermald/+bug/1582982/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1582982] Re: thermald 1.5-2ubuntu1 failures in ubuntu16.04
I have done the above. However, this caused a major problem. I am unable to boot up my system. It is stuck in the initramfs mode. I don't know how to fix this and really appreciate any help to recover my system and restore it to it's previous working condition. Require urgent assistance. On Fri, May 27, 2016 at 12:50 AM, Colin Ian King <1582...@bugs.launchpad.net > wrote: > @SunBear, > > I've applied upstream commit > > https://github.com/01org/thermal_daemon/commit/8280fd7ec6cff6db6463c8a1b01d2e427e418226 > (as mentioned in comment #2) and prepared thermald for testing. > > https://launchpad.net/~colin-king/+archive/ubuntu/thermald-sru-1582982 > > to install this use: > > sudo add-apt-repository ppa:colin-king/thermald-sru-1582982 > sudo apt update > sudo apt upgrade > > And let me know if that helps > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1582982 > > Title: > thermald 1.5-2ubuntu1 failures in ubuntu16.04 > > Status in thermald package in Ubuntu: > In Progress > > Bug description: > Hi. I am still getting the same failure message despite using the > latest thermald version. Can you tell me how to solve these failures. > > May 18 10:08:11 Eliot thermald[1012]: failed to open > /dev/acpi_thermal_rel > May 18 10:08:11 Eliot thermald[1012]: failed to open > /dev/acpi_thermal_rel > May 18 10:08:11 Eliot thermald[1012]: TRT/ART read failed > May 18 10:08:12 Eliot thermald[1012]: sysfs read failed > constraint_0_max_power_uw > May 18 10:08:12 Eliot thermald[1012]: sysfs write failed > trip_point_0_temp > May 18 10:08:12 Eliot thermald[1012]: sysfs write failed > trip_point_0_temp > > $: dpkg -l thermald > Desired=Unknown/Install/Remove/Purge/Hold > | > Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend > |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) > ||/ Name Version Architecture Description > > +++-=-===-===-=== > ii thermald 1.5-2ubuntu1 amd64 Thermal monitoring and controlling daemon > > $ lsb_release -rd > Description: Ubuntu 16.04 LTS > Release: 16.04 > > $ apt-cache policy thermald > thermald: > Installed: 1.5-2ubuntu1 > Candidate: 1.5-2ubuntu1 > Version table: >*** 1.5-2ubuntu1 500 > 500 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 > Packages > 100 /var/lib/dpkg/status >1.5-2 500 > 500 http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages > > To manage notifications about this bug go to: > > https://bugs.launchpad.net/ubuntu/+source/thermald/+bug/1582982/+subscriptions > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1582982 Title: thermald 1.5-2ubuntu1 failures in ubuntu16.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thermald/+bug/1582982/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1584407] Re: ACPI Error: [\_SB_.PCI0.XHC_.RHUB.HS11] Namespace lookup failure, AE_NOT_FOUND (20150930/dswload-210)
Hi Christopher, I will give it a try but it may take some time. I have to learn to backup my system first. Appreciate if you can answer the 2 questions in my earlier post. This is to help me understand the error messages and how they affects my setup. Thanks. On 23/05/2016 19:34, Christopher M. Penalver wrote: > SunBear, in order to allow additional upstream developers to examine the > issue, at your earliest convenience, could you please test the latest > upstream kernel available from > http://kernel.ubuntu.com/~kernel-ppa/mainline/?C=N;O=D ? Please keep in mind > the following: > 1) The one to test is at the very top line at the top of the page (not the > daily folder). > 2) The release names are irrelevant. > 3) The folder time stamps aren't indicative of when the kernel actually was > released upstream. > 4) Install instructions are available at > https://wiki.ubuntu.com/Kernel/MainlineBuilds . > > If testing on your main install would be inconvenient, one may: > 1) Install Ubuntu to a different partition and then test this there. > 2) Backup, or clone the primary install. > > If the latest kernel did not allow you to test to the issue (ex. you couldn't > boot into the OS) please make a comment in your report about this, and > continue to test the next most recent kernel version until you can test to > the issue. Once you've tested the upstream kernel, please comment on which > kernel version specifically you tested. If this issue is fixed in the > mainline kernel, please add the following tags by clicking on the yellow > circle with a black pencil icon, next to the word Tags, located at the bottom > of the report description: > kernel-fixed-upstream > kernel-fixed-upstream-X.Y-rcZ > > Where X, and Y are the first two numbers of the kernel version, and Z is > the release candidate number if it exists. > > If the mainline kernel does not fix the issue, please add the following tags: > kernel-bug-exists-upstream > kernel-bug-exists-upstream-X.Y-rcZ > > Please note, an error to install the kernel does not fit the criteria of > kernel-bug-exists-upstream. > > Also, you don't need to apport-collect further unless specifically > requested to do so. > > Once testing of the latest upstream kernel is complete, please mark this > report Status Confirmed. Please let us know your results. > > Thank you for your understanding. > > ** Summary changed: > > - Ubuntu 16.04 LTS --> Kernal --> ACPI Errors: Namespace lookup failure and 1 > table load failures > + ACPI Error: [\_SB_.PCI0.XHC_.RHUB.HS11] Namespace lookup failure, > AE_NOT_FOUND (20150930/dswload-210) > > ** Changed in: linux (Ubuntu) > Status: Confirmed => Incomplete > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1584407 Title: ACPI Error: [\_SB_.PCI0.XHC_.RHUB.HS11] Namespace lookup failure, AE_NOT_FOUND (20150930/dswload-210) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1584407/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1582982] Re: thermald 1.5-2ubuntu1 failures in ubuntu16.04
Hi Colin, It's called q-fan. It comes with the asus bios. https://www.youtube.com/watch?v=qIBLJ7nG3KM Pardon me if the terminology i use may or may not be correct. Essentially, it has a wizard to tune/calibrate the speed (or voltage) to cooling fans as a function of temperature at different MB location and cpu. They also supply a ASUS Fan Xpert 2 for Win OS. https://www.youtube.com/watch?v=BdxlUEG1IZc. I think thermald function is similar to q-fan and fan Xpert2. Questions: 1. Given that thermald cannot read _TRT and _ART, am i correct to say that thermald is not managing the thermal state of my system? 2. Also, does this mean that thermal management in my system is only performed by ASUS UEFI/BIOS with no active involvement from the OS and Ubuntu? 3. Does this mean thermald is a redundancy on my system and I can uninstall it w/o harming my system? Appreciate your advice and help to answer these questions. On 23/05/2016 16:34, Colin Ian King wrote: > "@Colin I am using an ASUS Z170M-Plus MB > (https://www.asus.com/sg/Motherboards/Z170M-PLUS/specifications/). It's > UEFI is equip to perform active thermal management of the CPU and a few > other locations on the MB." > > ..I could not find the source of information you are referring to about > " UEFI is equip to perform active thermal management of the CPU and a > few other locations on the MB". Can you point me to that assertion? > > > "Is there a reason why the devices of TRT and ART are not detected? Are these > tables required to monitor and control temperatures on my CPU and MB?" > > _TRT and _ART are ACPI control objects, see sections 11.4.19 _TRT > (Thermal Relationship Table) and 11.4.3 _ART (Active Cooling > Relationship Table) of the ACPI specification, > http://www.uefi.org/sites/default/files/resources/ACPI_6_1.pdf > > The kernel driver (drivers/thermal/int340x_thermal/acpi_thermal_rel.c) > attempts to evaluate these objects and these fail to evaluate (most > probably because they don't exist) hence these interfaces are not > exposed in a working state to user space programs such as thermald. It > is highly probably that the BIOS vendor just didn't implement these ACPI > objects. If they did not, well, that's the way it is. Debugging and > fixing the firmware is out of scope for this kind of bug report. > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1582982 Title: thermald 1.5-2ubuntu1 failures in ubuntu16.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thermald/+bug/1582982/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1584407] Re: Ubuntu 16.04 LTS --> Kernal --> ACPI Errors: Namespace lookup failure and 1 table load failures
Christoper, I reviewed my syslog concerning all Kernel-->ACPI logs via: cat /var/log/syslog | grep kernel | grep ACPI I have 2 questions and hope you can help me understand: 1. ACPI loaded the 8 SSDT tables. I assume these equate to the ssdt1.dat to ssdt8.dat files obtained from acpidump. However, ssdt9.dat to ssdt12.dat were not shown to be loaded. Why did it not report 4 table load failures but 1 in the ACPI Error? Below are the relevant tables reported in my syslogs? May 23 09:35:47 Eliot kernel: [0.00] ACPI: Early table checksum verification disabled May 23 09:35:47 Eliot kernel: [0.00] ACPI: RSDP 0xCDD39000 24 (v02 ALASKA) May 23 09:35:47 Eliot kernel: [0.00] ACPI: XSDT 0xCDD390A0 BC (v01 ALASKA A M I01072009 AMI 00010013) May 23 09:35:47 Eliot kernel: [0.00] ACPI: FACP 0xCDD5CB78 00010C (v05 ALASKA A M I01072009 AMI 00010013) May 23 09:35:47 Eliot kernel: [0.00] ACPI: DSDT 0xCDD391F8 02397B (v02 ALASKA A M I01072009 INTL 20120913) May 23 09:35:47 Eliot kernel: [0.00] ACPI: FACS 0xD751BF80 40 May 23 09:35:47 Eliot kernel: [0.00] ACPI: APIC 0xCDD5CC88 BC (v03 ALASKA A M I01072009 AMI 00010013) May 23 09:35:47 Eliot kernel: [0.00] ACPI: FPDT 0xCDD5CD48 44 (v01 ALASKA A M I01072009 AMI 00010013) May 23 09:35:47 Eliot kernel: [0.00] ACPI: FIDT 0xCDD5CD90 9C (v01 ALASKA A M I01072009 AMI 00010013) May 23 09:35:47 Eliot kernel: [0.00] ACPI: MCFG 0xCDD5CE30 3C (v01 ALASKA A M I01072009 MSFT 0097) May 23 09:35:47 Eliot kernel: [0.00] ACPI: HPET 0xCDD5CE70 38 (v01 ALASKA A M I01072009 AMI. 0005000B) May 23 09:35:47 Eliot kernel: [0.00] ACPI: SSDT 0xCDD5CEA8 00036D (v01 SataRe SataTabl 1000 INTL 20120913) May 23 09:35:47 Eliot kernel: [0.00] ACPI: LPIT 0xCDD5D218 94 (v01 INTEL SKL MSFT 005F) May 23 09:35:47 Eliot kernel: [0.00] ACPI: SSDT 0xCDD5D2B0 000248 (v02 INTEL sensrhub INTL 20120913) May 23 09:35:47 Eliot kernel: [0.00] ACPI: SSDT 0xCDD5D4F8 002BAE (v02 INTEL PtidDevc 1000 INTL 20120913) May 23 09:35:47 Eliot kernel: [0.00] ACPI: SSDT 0xCDD600A8 000BE3 (v02 INTEL Ther_Rvp 1000 INTL 20120913) May 23 09:35:47 Eliot kernel: [0.00] ACPI: SSDT 0xCDD60C90 0004A3 (v02 INTEL zpodd1000 INTL 20120913) May 23 09:35:47 Eliot kernel: [0.00] ACPI: DBGP 0xCDD61138 34 (v01 INTEL MSFT 005F) May 23 09:35:47 Eliot kernel: [0.00] ACPI: DBG2 0xCDD61170 54 (v00 INTEL MSFT 005F) May 23 09:35:47 Eliot kernel: [0.00] ACPI: SSDT 0xCDD611C8 000705 (v02 INTEL xh_rvp08 INTL 20120913) May 23 09:35:47 Eliot kernel: [0.00] ACPI: SSDT 0xCDD618D0 005359 (v02 SaSsdt SaSsdt 3000 INTL 20120913) May 23 09:35:47 Eliot kernel: [0.00] ACPI: UEFI 0xCDD66C30 42 (v01 ) May 23 09:35:47 Eliot kernel: [0.00] ACPI: SSDT 0xCDD66C78 000E73 (v02 CpuRef CpuSsdt 3000 INTL 20120913) May 23 09:35:47 Eliot kernel: [0.00] ACPI: BGRT 0xCDD67B48 38 (v01 ALASKA A M I01072009 AMI 00010013) 2. The ACPI Error concerning \_SB_.PCI0.XHC_.RHUB.HS11 Namespace lookup failure said dswload is affected. I understand dsw to mean "Device Sleep Wake". Does this mean the Namespace lookup failure caused the following pci device System wakeup to be disabled? May 23 10:43:10 Eliot kernel: [0.183971] pci :00:01.0: System wakeup disabled by ACPI May 23 10:43:10 Eliot kernel: [0.184348] pci :00:14.0: System wakeup disabled by ACPI May 23 10:43:10 Eliot kernel: [0.184828] pci :00:1b.0: System wakeup disabled by ACPI May 23 10:43:10 Eliot kernel: [0.184979] pci :00:1c.0: System wakeup disabled by ACPI May 23 10:43:10 Eliot kernel: [0.185130] pci :00:1d.0: System wakeup disabled by ACPI May 23 10:43:10 Eliot kernel: [0.185618] pci :00:1f.3: System wakeup disabled by ACPI May 23 10:43:10 Eliot kernel: [0.186086] pci :00:1f.6: System wakeup disabled by ACPI May 23 10:43:10 Eliot kernel: [0.186230] pci :01:00.0: System wakeup disabled by ACPI Based on lspci, these device appears to be: 00:01.0 PCI bridge: Intel Corporation Sky Lake PCIe Controller (x16) (rev 07) 00:14.0 USB controller: Intel Corporation Sunrise Point-H USB 3.0 xHCI Controller (rev 31) 00:1b.0 PCI bridge: Intel Corporation Sunrise Point-H PCI Root Port #17 (rev f1) 00:1c.0 PCI bridge: Intel Corporation Sunrise Point-H PCI Express Root Port #1 (rev f1) 00:1d.0 PCI bridge: Intel Corporation Sunrise Point-H PCI Express Root Port #9 (rev f1) 00:1f.3 Audio device: Intel Corporation Sunrise Point-H HD Au
