[Ubuntu-x-swat] [Bug 1845541] [NEW] OS becomes unresponsive when power is plugged in and battery is low
Public bug reported: Occasionally when I plug in my laptop at low (close to shut-down levels, <10%) battery, the OS becomes unresponsive. The GUI doesn't work, Ctrl+Alt+T doesn't work, nothing works. This makes it difficult to collect information about the problem, since I basically have to shutdown with the power button and reboot. It is probably related to whichever processes monitor the battery and put the computer to sleep when the battery gets low. Almost like it wants to put the computer to sleep since the battery is at critical levels, but it just stalls since the power is plugged in. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xserver-xorg-core 2:1.19.6-1ubuntu4.3 ProcVersionSignature: Ubuntu 4.15.0-62.69-generic 4.15.18 Uname: Linux 4.15.0-62-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Sep 26 11:41:31 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: virtualbox, 5.2.32, 4.15.0-58-generic, x86_64: installed virtualbox, 5.2.32, 4.15.0-62-generic, x86_64: installed ExecutablePath: /usr/lib/xorg/Xorg ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Skylake GT2 [HD Graphics 520] [8086:1916] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Skylake GT2 [HD Graphics 520] [103c:81cb] InstallationDate: Installed on 2019-01-28 (241 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2a Intel Corp. Bus 001 Device 002: ID 1bcf:2c83 Sunplus Innovation Technology Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP ENVY Notebook MonitorsUser.xml: ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/usr/bin/fish ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-62-generic root=UUID=fcfb9abf-573d-4d5e-bc54-c8a65f678302 ro quiet splash vt.handoff=1 SourcePackage: xorg-server UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/17/2016 dmi.bios.vendor: Insyde dmi.bios.version: F.22 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 81CB dmi.board.vendor: HP dmi.board.version: KBC Version 60.26 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.22:bd08/17/2016:svnHP:pnHPENVYNotebook:pvrType1ProductConfigId:rvnHP:rn81CB:rvrKBCVersion60.26:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP S=ENV dmi.product.name: HP ENVY Notebook dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.8-0ubuntu0~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.8-0ubuntu0~18.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 ** Affects: xorg-server (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic ubuntu -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1845541 Title: OS becomes unresponsive when power is plugged in and battery is low To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1845541/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1845385] Re: Touchpad click-drag action broken after close-lid suspend, Lenovo X1C5, Bionic
** Description changed: Steps to reproduce: - - observe touchpad click-drag working normally (i.e. can click touchpad and drag an icon, or select text in any direction) + - observe touchpad click-drag* working normally (i.e. can click touchpad and drag an icon, or select text in any direction) - close lid to suspend (need to wait some time until red Thinkpad light above 'i' on lid starts to flash - open lid to resume - observe touchpad click-drag NOT working. Can click but not drag, or can only drag very short distance/awkwardly + + *depressing the touchpad surface until it clicks, with one finger (usually index) and with the touchpad clicked down, dragging on the touchpad with another finger (middle) to move the item selected via the click. + typical uses to test: click a window titlebar and move it using drag + click a desktop icon and move it using drag + click to being select in text area of an app and drag to extend selection + Also note: - sudo moidprobe -r psmouse - sudo modprobe psmouse restores expected functionaly Similar symptoms to several related bugs (see below) but reporting separately, since: - issue still present on later hardware and software than previously reported - issue still present despite full firmware updates - slightly different experience with workaround (i.e modprobe -r psmouse / modprobe psmouse does restore functionality Related bugs: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1791427 https://bugs.launchpad.net/ubuntu/+source/libinput/+bug/1727130 https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1728778 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xserver-xorg-input-libinput 0.27.1-1 ProcVersionSignature: Ubuntu 4.15.0-64.73-generic 4.15.18 Uname: Linux 4.15.0-64-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CurrentDesktop: ubuntu:GNOME Date: Wed Sep 25 21:29:07 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu InstallationDate: Installed on 2018-11-22 (306 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 138a:0097 Validity Sensors, Inc. Bus 001 Device 003: ID 13d3:5682 IMC Networks Bus 001 Device 002: ID 8087:0a2b Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 20HRCTO1WW ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-64-generic root=/dev/mapper/system-root ro quiet splash vt.handoff=1 SourcePackage: xserver-xorg-input-libinput UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/16/2019 dmi.bios.vendor: LENOVO dmi.bios.version: N1MET54W (1.39 ) dmi.board.asset.tag: Not Available dmi.board.name: 20HRCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN1MET54W(1.39):bd04/16/2019:svnLENOVO:pn20HRCTO1WW:pvrThinkPadX1Carbon5th:rvnLENOVO:rn20HRCTO1WW:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Carbon 5th dmi.product.name: 20HRCTO1WW dmi.product.version: ThinkPad X1 Carbon 5th dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.8-0ubuntu0~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.8-0ubuntu0~18.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-input-libinput in Ubuntu. https://bugs.launchpad.net/bugs/1845385 Title: Touchpad click-drag action broken after close-lid suspend, Lenovo X1C5, Bionic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-libinput/+bug/1845385/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1845501] Re: With NVS-510, screen resolution is locked at 800x600 after switching to intel graphic
** Description changed: Currently only see this on a machine with NVS-510. Can reproduce with both 430.26 and 430.50 driver. Screen resolution was fine before installing nvidia graphic driver. But it's locked at 800x600 after installing driver and switching to intel graphic. Steps: 1. Install 18.04.3 desktop on a machine with Nvidia GK107 [NVS 510] [10de:0ffd]. 2. Install nvidia-driver-430 package 3. Reboot 4. Switch to intel profile $ sudo prime-select intel 5. Reboot Expected result: Desktop shows up in correct resolution got from edid. Actual result: Desktop shows up in 800x600, and there's no other resolution can be set. + + Hardware infomation: + Model: Dell Precision Tower 7810 + GPU: NVIDIA Corporation GK107 [NVS 510] [10de:0ffd] (rev a1) -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to nvidia-graphics-drivers-430 in Ubuntu. https://bugs.launchpad.net/bugs/1845501 Title: With NVS-510, screen resolution is locked at 800x600 after switching to intel graphic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-430/+bug/1845501/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1845502] Re: With NVS-510, screen stuck at CLI console after switching to intel graphic and switching back to nvidia
** Description changed: Currently only see this on a machine with NVS-510. Can reproduce with both 430.26 and 430.50 driver. Screen stuck at CLI console after switching to intel graphic and switching back to nvidia. The system still looks running, can access it through ssh or other CLI console. Steps: 1. Install 18.04.3 desktop on a machine with Nvidia GK107 [NVS 510] [10de:0ffd]. 2. Install nvidia-driver-430 package 3. Reboot 4. Switch to intel profile -$ sudo prime-select intel + $ sudo prime-select intel 5. Reboot 6. Switch to nvidia profile -$ sudo prime-select nvidia + $ sudo prime-select nvidia 5. Reboot Expected result: System boot into desktop correctly. Actual result: Screen stuck at CLI console. + + Hardware infomation: + Model: Dell Precision Tower 7810 + GPU: NVIDIA Corporation GK107 [NVS 510] [10de:0ffd] (rev a1) -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to nvidia-graphics-drivers-430 in Ubuntu. https://bugs.launchpad.net/bugs/1845502 Title: With NVS-510, screen stuck at CLI console after switching to intel graphic and switching back to nvidia To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-430/+bug/1845502/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1845502] Re: With NVS-510, screen stuck at CLI console after switching to intel graphic and switching back to nvidia
Please find test report here: https://drive.google.com/open?id=1DfY6Tt8jUjL2jkBIhxOIB9fsiohXxTJ_fotvGPHpwVg -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to nvidia-graphics-drivers-430 in Ubuntu. https://bugs.launchpad.net/bugs/1845502 Title: With NVS-510, screen stuck at CLI console after switching to intel graphic and switching back to nvidia To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-430/+bug/1845502/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1845502] Re: With NVS-510, screen stuck at CLI console after switching to intel graphic and switching back to nvidia
** Attachment added: "20190926_111242.jpg" https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-430/+bug/1845502/+attachment/5291479/+files/20190926_111242.jpg -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to nvidia-graphics-drivers-430 in Ubuntu. https://bugs.launchpad.net/bugs/1845502 Title: With NVS-510, screen stuck at CLI console after switching to intel graphic and switching back to nvidia To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-430/+bug/1845502/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1845502] [NEW] With NVS-510, screen stuck at CLI console after switching to intel graphic and switching back to nvidia
Public bug reported: Currently only see this on a machine with NVS-510. Can reproduce with both 430.26 and 430.50 driver. Screen stuck at CLI console after switching to intel graphic and switching back to nvidia. The system still looks running, can access it through ssh or other CLI console. Steps: 1. Install 18.04.3 desktop on a machine with Nvidia GK107 [NVS 510] [10de:0ffd]. 2. Install nvidia-driver-430 package 3. Reboot 4. Switch to intel profile $ sudo prime-select intel 5. Reboot 6. Switch to nvidia profile $ sudo prime-select nvidia 5. Reboot Expected result: System boot into desktop correctly. Actual result: Screen stuck at CLI console. ** Affects: nvidia-graphics-drivers-430 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to nvidia-graphics-drivers-430 in Ubuntu. https://bugs.launchpad.net/bugs/1845502 Title: With NVS-510, screen stuck at CLI console after switching to intel graphic and switching back to nvidia To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-430/+bug/1845502/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1845501] Re: With NVS-510, screen resolution is locked at 800x600 after switching to intel graphic
Please find test report here: https://drive.google.com/open?id=1DfY6Tt8jUjL2jkBIhxOIB9fsiohXxTJ_fotvGPHpwVg ** Description changed: - Currently only see this on a machine with NVS-510 currently. + Currently only see this on a machine with NVS-510. Can reproduce with both 430.26 and 430.50 driver. Screen resolution was fine before installing nvidia graphic driver. But it's locked at 800x600 after installing driver and switching to intel graphic. Steps: 1. Install 18.04.3 desktop on a machine with Nvidia GK107 [NVS 510] [10de:0ffd]. 2. Install nvidia-driver-430 package 3. Reboot 4. Switch to intel profile -$ sudo prime-select intel + $ sudo prime-select intel 5. Reboot Expected result: Desktop shows up in correct resolution got from edid. Actual result: Desktop shows up in 800x600, and there's no other resolution can be set. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to nvidia-graphics-drivers-430 in Ubuntu. https://bugs.launchpad.net/bugs/1845501 Title: With NVS-510, screen resolution is locked at 800x600 after switching to intel graphic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-430/+bug/1845501/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1845501] [NEW] With NVS-510, screen resolution is locked at 800x600 after switching to intel graphic
Public bug reported: Currently only see this on a machine with NVS-510. Can reproduce with both 430.26 and 430.50 driver. Screen resolution was fine before installing nvidia graphic driver. But it's locked at 800x600 after installing driver and switching to intel graphic. Steps: 1. Install 18.04.3 desktop on a machine with Nvidia GK107 [NVS 510] [10de:0ffd]. 2. Install nvidia-driver-430 package 3. Reboot 4. Switch to intel profile $ sudo prime-select intel 5. Reboot Expected result: Desktop shows up in correct resolution got from edid. Actual result: Desktop shows up in 800x600, and there's no other resolution can be set. ** Affects: nvidia-graphics-drivers-430 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to nvidia-graphics-drivers-430 in Ubuntu. https://bugs.launchpad.net/bugs/1845501 Title: With NVS-510, screen resolution is locked at 800x600 after switching to intel graphic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-430/+bug/1845501/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1845501] Re: With NVS-510, screen resolution is locked at 800x600 after switching to intel graphic
** Attachment added: "20190926_164510.jpg" https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-430/+bug/1845501/+attachment/5291478/+files/20190926_164510.jpg -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to nvidia-graphics-drivers-430 in Ubuntu. https://bugs.launchpad.net/bugs/1845501 Title: With NVS-510, screen resolution is locked at 800x600 after switching to intel graphic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-430/+bug/1845501/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1222602] Re: [regression] [gen3] Mesa 9.2 makes Unity unusable on Atom class hardware and 943/945 graphics controllers
** Changed in: mesa Status: Unknown => New -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1222602 Title: [regression] [gen3] Mesa 9.2 makes Unity unusable on Atom class hardware and 943/945 graphics controllers To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/1222602/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1794033] Re: i965: Failed to submit batchbuffer: Bad address
** Changed in: xserver-xorg-video-intel (Fedora) Status: Incomplete => Unknown ** Bug watch added: gitlab.freedesktop.org/mesa/mesa/issues #1680 https://gitlab.freedesktop.org/mesa/mesa/issues/1680 -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1794033 Title: i965: Failed to submit batchbuffer: Bad address To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1794033/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1794033]
-- GitLab Migration Automatic Message -- This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/mesa/mesa/issues/1680. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1794033 Title: i965: Failed to submit batchbuffer: Bad address To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1794033/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
