[Desktop-packages] [Bug 1960747] Re: [Lenovo Yoga 7] Autorotation of screen does not work on wayland, but on X
If you are able to wipe the machine and test 22.04 early then it can be downloaded here: http://cdimage.ubuntu.com/daily-live/current/ -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1960747 Title: [Lenovo Yoga 7] Autorotation of screen does not work on wayland, but on X Status in mutter package in Ubuntu: New Bug description: When physically rotating my 2-in-1 laptop Lenovo Yoga 7 Gen 6 AMD - 14ACN6, screen rotates properly under X, but not under Wayland. Also the lock screen rotation option is missing in the top-right menu under Wayland. It exists in X. iio-sensor-proxy is being loaded correctly: --- $ systemctl status iio-sensor-proxy.service ● iio-sensor-proxy.service - IIO Sensor Proxy service Loaded: loaded (/lib/systemd/system/iio-sensor-proxy.service; static) Active: active (running) since Sun 2022-02-13 15:43:37 CET; 2h 12min ago Main PID: 787 (iio-sensor-prox) Tasks: 3 (limit: 16544) Memory: 1.4M CPU: 5.688s CGroup: /system.slice/iio-sensor-proxy.service └─787 /usr/libexec/iio-sensor-proxy Feb 13 15:43:36 michaels-yoga systemd[1]: Starting IIO Sensor Proxy service... Feb 13 15:43:37 michaels-yoga systemd[1]: Started IIO Sensor Proxy service. --- monitor-sensor detects the physical rotation: --- $ monitor-sensor Waiting for iio-sensor-proxy to appear +++ iio-sensor-proxy appeared === Has accelerometer (orientation: normal) === Has ambient light sensor (value: 70,29, unit: lux) === No proximity sensor Light changed: 65,27 (lux) Light changed: 160,66 (lux) Accelerometer orientation changed: right-up Light changed: 40,16 (lux) Light changed: 45,18 (lux) Light changed: 40,16 (lux) Light changed: 25,10 (lux) Accelerometer orientation changed: left-up Light changed: 20,08 (lux) Light changed: 25,10 (lux) Light changed: 35,14 (lux) Accelerometer orientation changed: normal Light changed: 155,64 (lux) Accelerometer orientation changed: bottom-up Light changed: 30,12 (lux) Light changed: 40,16 (lux) Light changed: 30,12 (lux) Light changed: 145,60 (lux) Accelerometer orientation changed: normal --- Putting the laptop in tablet mode disables keyboard and touchpad correctly both under Wayland and X. So obviously the sensors are working correctly, but signals are not being interpreted correctly in Wayland? --- ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: xorg 1:7.7+22ubuntu2 Uname: Linux 5.15.0-051500-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 BootLog: Error: [Errno 13] Keine Berechtigung: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Feb 13 17:46:51 2022 DistUpgraded: Fresh install DistroCodename: impish DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Cezanne [1002:1638] (rev c1) (prog-if 00 [VGA controller]) Subsystem: Lenovo Cezanne [17aa:3813] InstallationDate: Installed on 2022-02-11 (1 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) MachineType: LENOVO 82N7 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.15.0-051500-generic root=UUID=d1796991-349c-4784-b8c3-e0a2eb2fc132 ro rootflags=subvol=@ quiet splash mem_sleep_default=deep vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/12/2021 dmi.bios.release: 1.25 dmi.bios.vendor: LENOVO dmi.bios.version: H9CN25WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0T76463 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: LENOVO dmi.chassis.version: Yoga 7 14ACN6 dmi.ec.firmware.release: 1.25 dmi.modalias: dmi:bvnLENOVO:bvrH9CN25WW:bd11/12/2021:br1.25:efr1.25:svnLENOVO:pn82N7:pvrYoga714ACN6:rvnLENOVO:rnLNVNB161216:rvrSDK0T76463WIN:cvnLENOVO:ct31:cvrYoga714ACN6:skuLENOVO_MT_82N7_BU_idea_FM_Yoga714ACN6: dmi.product.family: Yoga 7 14ACN6 dmi.product.name: 82N7 dmi.product.sku: LENOVO_MT_82N7_BU_idea_FM_Yoga 7 14ACN6 dmi.product.version: Yoga 7 14ACN6 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.107-8ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.6-0ubuntu0.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
[Desktop-packages] [Bug 1960747] Re: [Lenovo Yoga 7] Autorotation of screen does not work on wayland, but on X
It looks like there were a few rotation fixes upstream in mutter in the past year or so, so maybe this has been fixed already. Unfortunately you can't test it in a live session because live sessions use Xorg still. We'll need to wait until you are able and willing to try Ubuntu 22.04, which will be formally released in April. ** Tags added: amdgpu -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1960747 Title: [Lenovo Yoga 7] Autorotation of screen does not work on wayland, but on X Status in mutter package in Ubuntu: New Bug description: When physically rotating my 2-in-1 laptop Lenovo Yoga 7 Gen 6 AMD - 14ACN6, screen rotates properly under X, but not under Wayland. Also the lock screen rotation option is missing in the top-right menu under Wayland. It exists in X. iio-sensor-proxy is being loaded correctly: --- $ systemctl status iio-sensor-proxy.service ● iio-sensor-proxy.service - IIO Sensor Proxy service Loaded: loaded (/lib/systemd/system/iio-sensor-proxy.service; static) Active: active (running) since Sun 2022-02-13 15:43:37 CET; 2h 12min ago Main PID: 787 (iio-sensor-prox) Tasks: 3 (limit: 16544) Memory: 1.4M CPU: 5.688s CGroup: /system.slice/iio-sensor-proxy.service └─787 /usr/libexec/iio-sensor-proxy Feb 13 15:43:36 michaels-yoga systemd[1]: Starting IIO Sensor Proxy service... Feb 13 15:43:37 michaels-yoga systemd[1]: Started IIO Sensor Proxy service. --- monitor-sensor detects the physical rotation: --- $ monitor-sensor Waiting for iio-sensor-proxy to appear +++ iio-sensor-proxy appeared === Has accelerometer (orientation: normal) === Has ambient light sensor (value: 70,29, unit: lux) === No proximity sensor Light changed: 65,27 (lux) Light changed: 160,66 (lux) Accelerometer orientation changed: right-up Light changed: 40,16 (lux) Light changed: 45,18 (lux) Light changed: 40,16 (lux) Light changed: 25,10 (lux) Accelerometer orientation changed: left-up Light changed: 20,08 (lux) Light changed: 25,10 (lux) Light changed: 35,14 (lux) Accelerometer orientation changed: normal Light changed: 155,64 (lux) Accelerometer orientation changed: bottom-up Light changed: 30,12 (lux) Light changed: 40,16 (lux) Light changed: 30,12 (lux) Light changed: 145,60 (lux) Accelerometer orientation changed: normal --- Putting the laptop in tablet mode disables keyboard and touchpad correctly both under Wayland and X. So obviously the sensors are working correctly, but signals are not being interpreted correctly in Wayland? --- ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: xorg 1:7.7+22ubuntu2 Uname: Linux 5.15.0-051500-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 BootLog: Error: [Errno 13] Keine Berechtigung: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Feb 13 17:46:51 2022 DistUpgraded: Fresh install DistroCodename: impish DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Cezanne [1002:1638] (rev c1) (prog-if 00 [VGA controller]) Subsystem: Lenovo Cezanne [17aa:3813] InstallationDate: Installed on 2022-02-11 (1 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) MachineType: LENOVO 82N7 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.15.0-051500-generic root=UUID=d1796991-349c-4784-b8c3-e0a2eb2fc132 ro rootflags=subvol=@ quiet splash mem_sleep_default=deep vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/12/2021 dmi.bios.release: 1.25 dmi.bios.vendor: LENOVO dmi.bios.version: H9CN25WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0T76463 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: LENOVO dmi.chassis.version: Yoga 7 14ACN6 dmi.ec.firmware.release: 1.25 dmi.modalias: dmi:bvnLENOVO:bvrH9CN25WW:bd11/12/2021:br1.25:efr1.25:svnLENOVO:pn82N7:pvrYoga714ACN6:rvnLENOVO:rnLNVNB161216:rvrSDK0T76463WIN:cvnLENOVO:ct31:cvrYoga714ACN6:skuLENOVO_MT_82N7_BU_idea_FM_Yoga714ACN6: dmi.product.family: Yoga 7 14ACN6 dmi.product.name: 82N7 dmi.product.sku: LENOVO_MT_82N7_BU_idea_FM_Yoga 7 14ACN6 dmi.product.version: Yoga 7 14ACN6 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.107-8ubuntu1 version.libgl1-mesa-dri:
[Desktop-packages] [Bug 1484039] Re: yoga 3 screen does not rotate
Thank you for reporting this bug to Ubuntu. Ubuntu 15.04 (vivid) reached end-of-life on February 4, 2016. See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases We appreciate that this bug may be old and you might not be interested in discussing it any more. But if you are then please upgrade to the latest Ubuntu version and re-test. If you then find the bug is still present in the newer Ubuntu version, please add a comment here telling us which new version it is in. ** Changed in: unity-settings-daemon (Ubuntu) Status: Confirmed => Won't Fix -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1484039 Title: yoga 3 screen does not rotate Status in unity-settings-daemon package in Ubuntu: Won't Fix Bug description: Hi Developer Team! i don't know if you have developed it as a feature or not, but Lenovo Yoga 3's screen rotates while flipping the screen back or holding it vertivalli - just like a pad. Are you about to develop this feature? I love Ubuntu! Thank you. Seal ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: unity 7.3.2+15.04.20150420-0ubuntu1 ProcVersionSignature: Ubuntu 3.19.0-25.26-generic 3.19.8-ckt2 Uname: Linux 3.19.0-25-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.17.2-0ubuntu1.2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Wed Aug 12 11:06:19 2015 InstallationDate: Installed on 2015-07-27 (15 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-settings-daemon/+bug/1484039/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1960742] Re: System freeze
Thanks for the bug report. Next time the freeze happens please: 1. Wait 10 seconds. 2. Reboot. 3. Run: journalctl -b-1 > prevboot.txt 4. Attach the resulting text file here. ** Summary changed: - Xorg freeze + System freeze ** Package changed: xorg (Ubuntu) => linux-hwe-5.13 (Ubuntu) ** Changed in: linux-hwe-5.13 (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1960742 Title: System freeze Status in linux-hwe-5.13 package in Ubuntu: Incomplete Bug description: before it crashes, 3 LEDs (Power, mayus,block number) turn on and turn off about 3 times.. And all will be freeze it needs to shutdown keeping pressed the I/O button ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.13.0-28.31~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-28-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 BootLog: Error: [Errno 13] Permiso denegado: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Feb 13 11:03:30 2022 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GpuHangFrequency: Continuously GpuHangReproducibility: Seems to happen randomly GpuHangStarted: Immediately after installing this version of Ubuntu GraphicsCard: Intel Corporation Device [8086:4e55] (rev 01) (prog-if 00 [VGA controller]) Subsystem: Intel Corporation Device [8086:2212] InstallationDate: Installed on 2022-02-09 (4 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) MachineType: INTEL V14 ProcEnviron: LANGUAGE=es_EC:es PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_EC.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-28-generic root=UUID=31ee87c2-d9b1-413d-bc93-15224f6ba1ec ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/25/2021 dmi.bios.release: 5.19 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: WZ362D.fBNAPLL02.2105061 dmi.board.asset.tag: Default string dmi.board.name: V14 dmi.board.vendor: INET dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 10 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.ec.firmware.release: 1.2 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrWZ362D.fBNAPLL02.2105061:bd05/25/2021:br5.19:efr1.2:svnINTEL:pnV14:pvrDefaultstring:rvnINET:rnV14:rvrDefaultstring:cvnDefaultstring:ct10:cvrDefaultstring:sku2105061: dmi.product.family: Jasper lake dmi.product.name: V14 dmi.product.sku: 2105061 dmi.product.version: Default string dmi.sys.vendor: INTEL version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.107-8ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.6-0ubuntu0.1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 21.2.6-0ubuntu0.1~20.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.13/+bug/1960742/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1960747] Re: Autorotation of screen does not work on wayland, but on X
** Package changed: xorg (Ubuntu) => mutter (Ubuntu) ** Summary changed: - Autorotation of screen does not work on wayland, but on X + [Lenovo Yoga 7] Autorotation of screen does not work on wayland, but on X -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1960747 Title: [Lenovo Yoga 7] Autorotation of screen does not work on wayland, but on X Status in mutter package in Ubuntu: New Bug description: When physically rotating my 2-in-1 laptop Lenovo Yoga 7 Gen 6 AMD - 14ACN6, screen rotates properly under X, but not under Wayland. Also the lock screen rotation option is missing in the top-right menu under Wayland. It exists in X. iio-sensor-proxy is being loaded correctly: --- $ systemctl status iio-sensor-proxy.service ● iio-sensor-proxy.service - IIO Sensor Proxy service Loaded: loaded (/lib/systemd/system/iio-sensor-proxy.service; static) Active: active (running) since Sun 2022-02-13 15:43:37 CET; 2h 12min ago Main PID: 787 (iio-sensor-prox) Tasks: 3 (limit: 16544) Memory: 1.4M CPU: 5.688s CGroup: /system.slice/iio-sensor-proxy.service └─787 /usr/libexec/iio-sensor-proxy Feb 13 15:43:36 michaels-yoga systemd[1]: Starting IIO Sensor Proxy service... Feb 13 15:43:37 michaels-yoga systemd[1]: Started IIO Sensor Proxy service. --- monitor-sensor detects the physical rotation: --- $ monitor-sensor Waiting for iio-sensor-proxy to appear +++ iio-sensor-proxy appeared === Has accelerometer (orientation: normal) === Has ambient light sensor (value: 70,29, unit: lux) === No proximity sensor Light changed: 65,27 (lux) Light changed: 160,66 (lux) Accelerometer orientation changed: right-up Light changed: 40,16 (lux) Light changed: 45,18 (lux) Light changed: 40,16 (lux) Light changed: 25,10 (lux) Accelerometer orientation changed: left-up Light changed: 20,08 (lux) Light changed: 25,10 (lux) Light changed: 35,14 (lux) Accelerometer orientation changed: normal Light changed: 155,64 (lux) Accelerometer orientation changed: bottom-up Light changed: 30,12 (lux) Light changed: 40,16 (lux) Light changed: 30,12 (lux) Light changed: 145,60 (lux) Accelerometer orientation changed: normal --- Putting the laptop in tablet mode disables keyboard and touchpad correctly both under Wayland and X. So obviously the sensors are working correctly, but signals are not being interpreted correctly in Wayland? --- ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: xorg 1:7.7+22ubuntu2 Uname: Linux 5.15.0-051500-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 BootLog: Error: [Errno 13] Keine Berechtigung: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Feb 13 17:46:51 2022 DistUpgraded: Fresh install DistroCodename: impish DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Cezanne [1002:1638] (rev c1) (prog-if 00 [VGA controller]) Subsystem: Lenovo Cezanne [17aa:3813] InstallationDate: Installed on 2022-02-11 (1 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) MachineType: LENOVO 82N7 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.15.0-051500-generic root=UUID=d1796991-349c-4784-b8c3-e0a2eb2fc132 ro rootflags=subvol=@ quiet splash mem_sleep_default=deep vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/12/2021 dmi.bios.release: 1.25 dmi.bios.vendor: LENOVO dmi.bios.version: H9CN25WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0T76463 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: LENOVO dmi.chassis.version: Yoga 7 14ACN6 dmi.ec.firmware.release: 1.25 dmi.modalias: dmi:bvnLENOVO:bvrH9CN25WW:bd11/12/2021:br1.25:efr1.25:svnLENOVO:pn82N7:pvrYoga714ACN6:rvnLENOVO:rnLNVNB161216:rvrSDK0T76463WIN:cvnLENOVO:ct31:cvrYoga714ACN6:skuLENOVO_MT_82N7_BU_idea_FM_Yoga714ACN6: dmi.product.family: Yoga 7 14ACN6 dmi.product.name: 82N7 dmi.product.sku: LENOVO_MT_82N7_BU_idea_FM_Yoga 7 14ACN6 dmi.product.version: Yoga 7 14ACN6 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.107-8ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.6-0ubuntu0.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core
[Desktop-packages] [Bug 1960709] Re: Recent bluez update broke Bluetooth for setups using a BT dongle
BTW, "ConditionPathIsDirectory" is not new. It's been there for two years already in Ubuntu 20.04. If you have experienced a regression then more often that would come from a kernel update so please try some different kernel versions. ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1960709 Title: Recent bluez update broke Bluetooth for setups using a BT dongle Status in bluez package in Ubuntu: Incomplete Status in linux package in Ubuntu: Incomplete Bug description: A recent upgrade (seemingly 5.53-0ubuntu3.5) broke Bluetooth functionality for certain setups. Specifically, the `ConditionPathIsDirectory=` parameter has been added to the `bluetooth` Systemd unit. This breaks setups where users use a Bluetooth dongle, since when the system starts, the BT device may not be connected, and due to the condition, the `bluetooth` unit won't start at all. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1960709/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1960605] Re: Xorg freeze
Thanks for the bug report. I can see two problems here, though am not sure if either is the main issue: * Timeout, server 21.0.0.52 not responding. Whatever that is, if it's a server the machine depends on then it might cause a startup failure. * CurrentDmesg.txt seems to suggest file system corruption on /dev/sdb1. If that's something the machine depends on then it might cause a startup failure. ** Summary changed: - Xorg freeze + System freeze ** Package changed: xorg (Ubuntu) => ubuntu -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1960605 Title: System freeze Status in Ubuntu: New Bug description: When booting the system, sometimes the system freezes (HP logo, Ubuntu logo and stopped rotating symbol), and can't do anything not even ping the system. After zero or a few re-try's I get to the login screen. It is then possible to log in via ssh from another system. Everything looks OK. Then I can select the user give her password and then one of two things happens. one: Ubuntu starts and works OK. two: the system freezes (black screen) and nothing works not even the ssh session. I've tried looking at syslog and other files, but can't make any sense of it. I also attached the last lines of the syslog wich ended in a crash/hangup. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.13.0-28.31~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-28-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 470.86 Tue Oct 26 21:55:45 UTC 2021 GCC version: ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 BootLog: Error: [Errno 13] Toegang geweigerd: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Feb 11 10:29:20 2022 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GpuHangFrequency: Several times a day GpuHangReproducibility: Occurs more often under certain circumstances GpuHangStarted: Since a couple weeks or more GraphicsCard: Intel Corporation UHD Graphics [8086:9bc4] (rev 05) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Device [103c:8745] NVIDIA Corporation Device [10de:1f95] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Device [103c:8745] InstallationDate: Installed on 2021-12-04 (69 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: HP HP Pavilion Gaming Laptop 17-cd1xxx ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=nl_NL.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-28-generic root=UUID=84ab800e-9239-453f-8f4a-dc7e4377e5ad ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/08/2021 dmi.bios.release: 15.21 dmi.bios.vendor: Insyde dmi.bios.version: F.21 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 8745 dmi.board.vendor: HP dmi.board.version: 03.34 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 3.34 dmi.modalias: dmi:bvnInsyde:bvrF.21:bd01/08/2021:br15.21:efr3.34:svnHP:pnHPPavilionGamingLaptop17-cd1xxx:pvrType1ProductConfigId:rvnHP:rn8745:rvr03.34:cvnHP:ct10:cvrChassisVersion:sku1C4U6EA#ABH: dmi.product.family: 103C_5335KV HP Pavilion dmi.product.name: HP Pavilion Gaming Laptop 17-cd1xxx dmi.product.sku: 1C4U6EA#ABH dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.105-3~20.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.3-0ubuntu0.3~20.04.5 version.libgl1-mesa-glx: libgl1-mesa-glx 21.0.3-0ubuntu0.3~20.04.5 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to:
[Desktop-packages] [Bug 1960602] Re: Ubuntu 20.04 shows blank upon resuming from resume. Requires hard shutdown using the h/w power button
Thanks for the bug report. The final entry in your kernel log shows that the Intel GPU tried and failed to update the screen: [ 1216.206745] i915 :00:02.0: [drm] *ERROR* Atomic update failure on pipe A (start=73567 end=73568) time 940 us, min 1073, max 1079, scanline start 1033, end 1097 So maybe that's the issue... Please try (separately): 1. Selecting 'Ubuntu on Wayland' on the login screen just before logging in. 2. Edit /etc/environment and add a line: MUTTER_DEBUG_ENABLE_ATOMIC_KMS=0 Then reboot and select 'Ubuntu on Wayland' again. ** Tags added: resume suspend-resume ** Package changed: xorg (Ubuntu) => linux-hwe-5.13 (Ubuntu) ** Changed in: linux-hwe-5.13 (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1960602 Title: Ubuntu 20.04 shows blank upon resuming from resume. Requires hard shutdown using the h/w power button Status in linux-hwe-5.13 package in Ubuntu: Incomplete Bug description: After installing Ubuntu 20.04 on my laptop, if the laptop suspends due to closing the lid or not using the laptop for some time and once I press any key to resume from the suspend, the laptop shows a blank screen and is unresponsive to any button presses. This problem happens sometimes though. There have been times that I resume from suspend successfully. But more often it will fail to resume from suspend completely and I will need to use the hardware power button to hard shutdown and restart. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.13.0-28.31~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-28-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Feb 11 14:23:17 2022 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GpuHangFrequency: Several times a week GpuHangReproducibility: Occurs more often under certain circumstances GpuHangStarted: Immediately after installing this version of Ubuntu GraphicsCard: Intel Corporation UHD Graphics 620 (Whiskey Lake) [8086:3ea0] (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company UHD Graphics 620 (Whiskey Lake) [103c:84c1] Subsystem: Hewlett-Packard Company GM108M [GeForce MX130] [103c:84c1] InstallationDate: Installed on 2021-09-10 (153 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 05c8:03bc Cheng Uei Precision Industry Co., Ltd (Foxlink) HP Wide Vision HD Camera Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP Pavilion Laptop 15-cs1xxx ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-28-generic root=UUID=a6c8900d-2dd5-4390-a3c8-c0865429d620 ro nouveau.blacklist=1 quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/25/2020 dmi.bios.release: 15.23 dmi.bios.vendor: Insyde dmi.bios.version: F.23 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 84C1 dmi.board.vendor: HP dmi.board.version: 15.32 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 15.32 dmi.modalias: dmi:bvnInsyde:bvrF.23:bd12/25/2020:br15.23:efr15.32:svnHP:pnHPPavilionLaptop15-cs1xxx:pvrType1ProductConfigId:rvnHP:rn84C1:rvr15.32:cvnHP:ct10:cvrChassisVersion:sku5FP53PA#ACJ: dmi.product.family: 103C_5335KV HP Pavilion dmi.product.name: HP Pavilion Laptop 15-cs1xxx dmi.product.sku: 5FP53PA#ACJ dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.105-3~20.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.3-0ubuntu0.3~20.04.5 version.libgl1-mesa-glx: libgl1-mesa-glx 21.0.3-0ubuntu0.3~20.04.5 version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.13/+bug/1960602/+subscriptions -- Mailing list:
[Desktop-packages] [Bug 1946476] Re: New on-demand default causes RTD3 never to be enabled
** Description changed: [Steps to reproduce] 1. Install 20.04.3 with "Third-party packages" on a system which containing a RTD3 supported nvidia card. 2. After the installation, press enter to reboot system 3. prime-select query [Expected result] on-demand [Actual result] performance --- It's because ubiquity launches `ubuntu-drivers install --packages-list ...` in live system but install each package to target storage. When installing nvidia-prime, the preinst set "on" to "/etc/prime- discrete" which will be referred by gpu-manager. The gpu-manager will set to performance mode. After confirming with Alberto on Mattermost, since we don't have a nvidia driver which lower than 450 version since focal. I think we are ok to switch to on-demand mode. --- [Impact] * Ubuntu will set GPU mode to performance as default which may use more power * User can't use GPU for other purpose (eg: deep-learning) if RTD3 is not supported * According to Nvidia README, the RTD3 doesn't support on non-laptop machine [Test Plan] * Install Ubuntu, and then execute 'ubuntu-drivers install' to install GPU driver. After the installation, reboot the system. Execute "prime-select query" should get "on-demand" + * Old GPU (which supported by nvidia-390 only) will keep in performance mode, refer LP:1957094. Execute "prime-select query" should get "nvidia" * On non-laptop machine. Can set GPU mode to on-demand * On laptop with GPU in runtime PM support list. Set GPU mode to on-demand and Nvidia driver is loaded with "NVreg_DynamicPowerManagement=0x02" [Where problems could occur] - * on-demand mode combined two features which are GPU offloading and RTD3. Nvidia driver lower then 450 (nvidia-driver-390) does not supported RTD3 and only have GPU offloading feature. - * With GPU supported RTD3 not able enable runtime PM on non-laptop. But based on the Nvidia README, this case shall not happened. + * With GPU supported RTD3 not able enable runtime PM on non-laptop. But + based on the Nvidia README, this case shall not happened. [Other Info] - - X-HWE-Bug: Bug #1946434 Changelogs: nvidia-prime (0.8.16~0.20.04.2) focal; urgency=medium [ Jeremy Szu ] * Set on-demand mode as default nvidia mode (LP: #1942307) [ Alberto Milone ] * prime-select: - Detect chassis type and enable RTD3 only on laptops (LP: #1942788). - on-demand mode doesn't need to depend on RTD3 (LP: #1942789). - Use bootvga detection when last_gfx_boot is not available. - Don't check the current profile when setting a profile (LP: #1946476). - Catch BrokenPipeError. - Use bootvga detection when last_gfx_boot is not available. nvidia-prime (0.8.16.2~0.21.04.1) hirsute; urgency=medium [ Jeremy Szu ] * Set on-demand mode as default nvidia mode (LP: #1942307) [ Alberto Milone ] * prime-select: - Detect chassis type and enable RTD3 only on laptops (LP: #1942788). - on-demand mode doesn't need to depend on RTD3 (LP: #1942789). - Use bootvga detection when last_gfx_boot is not available. - Don't check the current profile when setting a profile (LP: #1946476). ** Changed in: oem-priority Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-prime in Ubuntu. https://bugs.launchpad.net/bugs/1946476 Title: New on-demand default causes RTD3 never to be enabled Status in OEM Priority Project: Confirmed Status in nvidia-prime package in Ubuntu: Fix Released Status in nvidia-prime source package in Focal: Incomplete Status in nvidia-prime source package in Hirsute: Incomplete Status in nvidia-prime source package in Impish: Fix Released Bug description: [Steps to reproduce] 1. Install 20.04.3 with "Third-party packages" on a system which containing a RTD3 supported nvidia card. 2. After the installation, press enter to reboot system 3. prime-select query [Expected result] on-demand [Actual result] performance --- It's because ubiquity launches `ubuntu-drivers install --packages-list ...` in live system but install each package to target storage. When installing nvidia-prime, the preinst set "on" to "/etc/prime- discrete" which will be referred by gpu-manager. The gpu-manager will set to performance mode. After confirming with Alberto on Mattermost, since we don't have a nvidia driver which lower than 450 version since focal. I think we are ok to switch to on-demand mode. --- [Impact] * Ubuntu will set GPU mode to performance as default which may use more power * User can't use GPU for other purpose (eg: deep-learning) if RTD3 is not supported * According to Nvidia README, the RTD3 doesn't support on non-laptop machine
[Desktop-packages] [Bug 1942789] Re: On-demand and RTD3 need to be separated
** Description changed: [Steps to reproduce] 1. Install 20.04.3 with "Third-party packages" on a system which containing a RTD3 supported nvidia card. 2. After the installation, press enter to reboot system 3. prime-select query [Expected result] on-demand [Actual result] performance --- It's because ubiquity launches `ubuntu-drivers install --packages-list ...` in live system but install each package to target storage. When installing nvidia-prime, the preinst set "on" to "/etc/prime- discrete" which will be referred by gpu-manager. The gpu-manager will set to performance mode. After confirming with Alberto on Mattermost, since we don't have a nvidia driver which lower than 450 version since focal. I think we are ok to switch to on-demand mode. --- [Impact] - * Ubuntu will set GPU mode to performance as default which may use more power - * User can't use GPU for other purpose (eg: deep-learning) if RTD3 is not supported - * According to Nvidia README, the RTD3 doesn't support on non-laptop machine + * Ubuntu will set GPU mode to performance as default which may use more power + * User can't use GPU for other purpose (eg: deep-learning) if RTD3 is not supported + * According to Nvidia README, the RTD3 doesn't support on non-laptop machine [Test Plan] - * Install Ubuntu, and then execute 'ubuntu-drivers install' to install GPU driver. After the installation, reboot the system. Execute "prime-select query" should get "on-demand" - * On non-laptop machine. Can set GPU mode to on-demand - * On laptop with GPU in runtime PM support list. Set GPU mode to on-demand and Nvidia driver is loaded with "NVreg_DynamicPowerManagement=0x02" + * Install Ubuntu, and then execute 'ubuntu-drivers install' to install GPU driver. After the installation, reboot the system. Execute "prime-select query" should get "on-demand" + * Old GPU (which supported by nvidia-390 only) will keep in performance mode, refer LP:1957094. Execute "prime-select query" should get "nvidia" + * On non-laptop machine. Can set GPU mode to on-demand + * On laptop with GPU in runtime PM support list. Set GPU mode to on-demand and Nvidia driver is loaded with "NVreg_DynamicPowerManagement=0x02" [Where problems could occur] - * on-demand mode combined two features which are GPU offloading and RTD3. Nvidia driver lower then 450 (nvidia-driver-390) does not supported RTD3 and only have GPU offloading feature. - * With GPU supported RTD3 not able enable runtime PM on non-laptop. But based on the Nvidia README, this case shall not happened. + * With GPU supported RTD3 not able enable runtime PM on non-laptop. But + based on the Nvidia README, this case shall not happened. [Other Info] - - X-HWE-Bug: Bug #1946434 Changelogs: nvidia-prime (0.8.16~0.20.04.2) focal; urgency=medium - [ Jeremy Szu ] - * Set on-demand mode as default nvidia mode (LP: #1942307) + [ Jeremy Szu ] + * Set on-demand mode as default nvidia mode (LP: #1942307) - [ Alberto Milone ] - * prime-select: - - Detect chassis type and enable RTD3 only - on laptops (LP: #1942788). - - on-demand mode doesn't need to depend on - RTD3 (LP: #1942789). - - Use bootvga detection when last_gfx_boot - is not available. - - Don't check the current profile when setting - a profile (LP: #1946476). - - Catch BrokenPipeError. - - Use bootvga detection when last_gfx_boot is - not available. + [ Alberto Milone ] + * prime-select: + - Detect chassis type and enable RTD3 only + on laptops (LP: #1942788). + - on-demand mode doesn't need to depend on + RTD3 (LP: #1942789). + - Use bootvga detection when last_gfx_boot + is not available. + - Don't check the current profile when setting + a profile (LP: #1946476). + - Catch BrokenPipeError. + - Use bootvga detection when last_gfx_boot is + not available. nvidia-prime (0.8.16.2~0.21.04.1) hirsute; urgency=medium - [ Jeremy Szu ] - * Set on-demand mode as default nvidia mode (LP: #1942307) + [ Jeremy Szu ] + * Set on-demand mode as default nvidia mode (LP: #1942307) - [ Alberto Milone ] - * prime-select: - - Detect chassis type and enable RTD3 only - on laptops (LP: #1942788). - - on-demand mode doesn't need to depend on - RTD3 (LP: #1942789). - - Use bootvga detection when last_gfx_boot - is not available. - - Don't check the current profile when setting - a profile (LP: #1946476). + [ Alberto Milone ] + * prime-select: + - Detect chassis type and enable RTD3 only + on laptops (LP: #1942788). + - on-demand mode doesn't need to depend on + RTD3 (LP: #1942789). + - Use bootvga detection when last_gfx_boot + is not available. + - Don't check the current profile when setting + a profile (LP: #1946476). ** Changed
[Desktop-packages] [Bug 1942307] Re: ubiquity uses performance mode for nvidia driver
** Description changed: [Steps to reproduce] 1. Install 20.04.3 with "Third-party packages" on a system which containing a RTD3 supported nvidia card. 2. After the installation, press enter to reboot system 3. prime-select query [Expected result] on-demand [Actual result] performance --- It's because ubiquity launches `ubuntu-drivers install --packages-list ...` in live system but install each package to target storage. When installing nvidia-prime, the preinst set "on" to "/etc/prime- discrete" which will be referred by gpu-manager. The gpu-manager will set to performance mode. After confirming with Alberto on Mattermost, since we don't have a nvidia driver which lower than 450 version since focal. I think we are ok to switch to on-demand mode. --- [Impact] - * Ubuntu will set GPU mode to performance as default which may use more power - * User can't use GPU for other purpose (eg: deep-learning) if RTD3 is not supported - * According to Nvidia README, the RTD3 doesn't support on non-laptop machine + * Ubuntu will set GPU mode to performance as default which may use more power + * User can't use GPU for other purpose (eg: deep-learning) if RTD3 is not supported + * According to Nvidia README, the RTD3 doesn't support on non-laptop machine [Test Plan] - * Install Ubuntu, and then execute 'ubuntu-drivers install' to install GPU driver. After the installation, reboot the system. Execute "prime-select query" should get "on-demand" - * On non-laptop machine. Can set GPU mode to on-demand - * On laptop with GPU in runtime PM support list. Set GPU mode to on-demand and Nvidia driver is loaded with "NVreg_DynamicPowerManagement=0x02" + * Install Ubuntu, and then execute 'ubuntu-drivers install' to install GPU driver. After the installation, reboot the system. Execute "prime-select query" should get "on-demand" + * Old GPU (which supported by nvidia-390 only) will keep in performance mode, refer LP:1957094. Execute "prime-select query" should get "nvidia" + * On non-laptop machine. Can set GPU mode to on-demand + * On laptop with GPU in runtime PM support list. Set GPU mode to on-demand and Nvidia driver is loaded with "NVreg_DynamicPowerManagement=0x02" [Where problems could occur] - * on-demand mode combined two features which are GPU offloading and RTD3. Nvidia driver lower then 450 (nvidia-driver-390) does not supported RTD3 and only have GPU offloading feature. - * With GPU supported RTD3 not able enable runtime PM on non-laptop. But based on the Nvidia README, this case shall not happened. + * With GPU supported RTD3 not able enable runtime PM on non-laptop. But + based on the Nvidia README, this case shall not happened. [Other Info] - - X-HWE-Bug: Bug #1946434 Changelogs: nvidia-prime (0.8.16~0.20.04.2) focal; urgency=medium - [ Jeremy Szu ] - * Set on-demand mode as default nvidia mode (LP: #1942307) + [ Jeremy Szu ] + * Set on-demand mode as default nvidia mode (LP: #1942307) - [ Alberto Milone ] - * prime-select: - - Detect chassis type and enable RTD3 only - on laptops (LP: #1942788). - - on-demand mode doesn't need to depend on - RTD3 (LP: #1942789). - - Use bootvga detection when last_gfx_boot - is not available. - - Don't check the current profile when setting - a profile (LP: #1946476). - - Catch BrokenPipeError. - - Use bootvga detection when last_gfx_boot is - not available. + [ Alberto Milone ] + * prime-select: + - Detect chassis type and enable RTD3 only + on laptops (LP: #1942788). + - on-demand mode doesn't need to depend on + RTD3 (LP: #1942789). + - Use bootvga detection when last_gfx_boot + is not available. + - Don't check the current profile when setting + a profile (LP: #1946476). + - Catch BrokenPipeError. + - Use bootvga detection when last_gfx_boot is + not available. nvidia-prime (0.8.16.2~0.21.04.1) hirsute; urgency=medium - [ Jeremy Szu ] - * Set on-demand mode as default nvidia mode (LP: #1942307) + [ Jeremy Szu ] + * Set on-demand mode as default nvidia mode (LP: #1942307) - [ Alberto Milone ] - * prime-select: - - Detect chassis type and enable RTD3 only - on laptops (LP: #1942788). - - on-demand mode doesn't need to depend on - RTD3 (LP: #1942789). - - Use bootvga detection when last_gfx_boot - is not available. - - Don't check the current profile when setting - a profile (LP: #1946476). + [ Alberto Milone ] + * prime-select: + - Detect chassis type and enable RTD3 only + on laptops (LP: #1942788). + - on-demand mode doesn't need to depend on + RTD3 (LP: #1942789). + - Use bootvga detection when last_gfx_boot + is not available. + - Don't check the current profile when setting + a profile (LP: #1946476). -- You
[Desktop-packages] [Bug 1960768] Re: fwupd crash on stop
** Also affects: libusb (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libusb in Ubuntu. https://bugs.launchpad.net/bugs/1960768 Title: fwupd crash on stop Status in OEM Priority Project: In Progress Status in fwupd package in Ubuntu: New Status in libusb package in Ubuntu: New Bug description: I can reproduce crash with a similar stack as below as I stop fwupd service. https://errors.ubuntu.com/problem/4bfcf571c017010afe4775687ff2a9ca7ff79661 also test fwupd 1.7.5 (https://launchpad.net/~ycheng-twn/+archive/ubuntu/fwupd175) still can reproduce this issue. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1960768/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1960569] Re: Screen goes dim
Nothing in regular Ubuntu calls 'xrandr --brightness' that I know of. Hence I recommend uninstalling 'brightness-controller' because it's the most suspicious package right now. Also I would expect 'GNOME' to avoid the problem more than 'GNOME on Xorg' because 'GNOME' has no Xorg server and no support for 'xrandr --brightness'. But still it would be very helpful to test both 'GNOME' and 'GNOME on Xorg'. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1960569 Title: Screen goes dim Status in xorg-server package in Ubuntu: Incomplete Bug description: I walk away from the machine; come back hours later to find that the screen is dim. The following command confirms that the cause is something in Ubuntu xrandr --listmonitors --verbose | egrep -3 -i 'gamma|backl|brightn' Has shown value for "Brightness" of 0.11, 0.18, 0.0018, 0.20, and possibly other values. (Gamma is all 1.0.) This occurs on both monitors that I have hooked up, but the values are usually different. I like a Brightness of 0.80, I know how to manually change with xrandr or a brightness-controller app. When the brightness is too low it is very hard to fix things without rebooting. I am currently running 21.10, but I have had mysterious crashes in older versions of Ubuntu; I now wonder if the was going all the way to zero in some of those crashes. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: xorg 1:7.7+22ubuntu2 ProcVersionSignature: Ubuntu 5.13.0-28.31-generic 5.13.19 Uname: Linux 5.13.0-28-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: MATE Date: Thu Feb 10 15:32:43 2022 DistUpgraded: 2022-02-03 15:56:57,188 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: impish DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation CoffeeLake-H GT2 [UHD Graphics 630] [8086:3e9b] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Intel Corporation CoffeeLake-H GT2 [UHD Graphics 630] [8086:2088] InstallationDate: Installed on 2021-01-25 (381 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: Intel(R) Client Systems NUC9V7QNX ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-28-generic root=UUID=7374319a-8421-4977-a836-6882e295d7ca ro quiet splash crashkernel=512M-:192M vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to impish on 2022-02-03 (6 days ago) dmi.bios.date: 11/30/2020 dmi.bios.release: 5.13 dmi.bios.vendor: Intel Corp. dmi.bios.version: QNCFLX70.0059.2020.1130.2122 dmi.board.name: NUC9V7QNB dmi.board.vendor: Intel Corporation dmi.board.version: K47180-402 dmi.chassis.type: 35 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 2.0 dmi.ec.firmware.release: 24.39 dmi.modalias: dmi:bvnIntelCorp.:bvrQNCFLX70.0059.2020.1130.2122:bd11/30/2020:br5.13:efr24.39:svnIntel(R)ClientSystems:pnNUC9V7QNX:pvrK47174-402:rvnIntelCorporation:rnNUC9V7QNB:rvrK47180-402:cvnIntelCorporation:ct35:cvr2.0:skuBKNUC9V7QNX: dmi.product.family: QN dmi.product.name: NUC9V7QNX dmi.product.sku: BKNUC9V7QNX dmi.product.version: K47174-402 dmi.sys.vendor: Intel(R) Client Systems version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.107-8ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 21.2.2-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1ubuntu2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1960569/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1960403] Re: Kubuntu constantly freezing on ThinkPad T510
Jonas, In comment #5 do you mean the fix was released to Ubuntu, or the fix is only in the Mesa PPA from comment #3? ** No longer affects: xserver-xorg-video-intel (Ubuntu) ** No longer affects: linux (Ubuntu) ** No longer affects: kubuntu-meta (Ubuntu) ** No longer affects: xorg (Ubuntu) ** Tags added: arrandale i915 ** Changed in: mesa (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1960403 Title: Kubuntu constantly freezing on ThinkPad T510 Status in mesa package in Ubuntu: Incomplete Bug description: This happens either during SDDM, or on the desktop, but Kubuntu's constantly freezing up. I tried disabling the compositor, but it doesn't seem to help. Also, I removed the external monitor, but that doesn't seem to help. I've installed Lubuntu, and so far it's been fine. However, when I tried to change the SDDM theme via KDE's System Settings, the laptop locked up. I'll keep Kubuntu on it for now, but I'm gonna have to switch this to Lubuntu in the meantime. Specs: * Core i7-640M * 8GB RAM ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: kubuntu-desktop 1.416 ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12 Uname: Linux 5.15.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu76 Architecture: amd64 CasperMD5CheckResult: unknown Date: Wed Feb 9 05:58:18 2022 InstallationDate: Installed on 2021-08-07 (186 days ago) InstallationMedia: Kubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) SourcePackage: kubuntu-meta UpgradeStatus: Upgraded to jammy on 2022-02-09 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1960403/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1767542] Re: Turning off WiFi enables Airplane mode
Same issue in home desktop computer. Wifi not turn on. I have to restart wifi-dongle and computer. Ubuntu 18.04 LTS. I dont find any options in turned to off. Settings are same. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1767542 Title: Turning off WiFi enables Airplane mode Status in gnome-control-center: Confirmed Status in gnome-control-center package in Ubuntu: Triaged Bug description: Turning off the WiFi from the top right control enables Airplane mode (see screenshots). Also after turning off airplane mode, the Wi-Fi is not turned back on, rather the Bluetooth is. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-control-center 1:3.28.1-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Apr 27 17:46:34 2018 InstallationDate: Installed on 2018-04-27 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1767542/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1949075] Re: Sony WI-C310 Bluetooth headset not autoconnecting on power-on on 21.10
Given the message in your kernel log: Bluetooth: hci0: Ignoring error of Inquiry Cancel command A similar problem with the same message was a kernel regression: https://bbs.archlinux.org/viewtopic.php?id=259954 Maybe not related to this bug, but still a reminder that it might be a kernel regression. ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Summary changed: - Sony WI-C310 Bluetooth headset not autoconnecting on power-on on 21.10 + [Sony WI-C310] [Intel Wireless 8260] Bluetooth headset not autoconnecting on power-on on 21.10 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1949075 Title: [Sony WI-C310] [Intel Wireless 8260] Bluetooth headset not autoconnecting on power-on on 21.10 Status in bluez package in Ubuntu: New Status in linux package in Ubuntu: New Bug description: After moving to Impish, my bluetooth headset doesn't automatically connect when I power it on (it was working fine on hirsute). When I go to the bluetooth settings, select it and click connect, the first time it disconnects immediately and I see this line in bluetoothd log: Oct 28 13:57:11 arrakis bluetoothd[1106]: src/profile.c:record_cb() Unable to get Hands-Free Voice gateway SDP record: Host is down After that, clicking the connect button again makes it work. I'm not sure where to find info to debug this furhter ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: bluetooth (not installed) ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14 Uname: Linux 5.13.0-19-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Oct 28 13:57:34 2021 InstallationDate: Installed on 2021-10-16 (11 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) InterestingModules: rfcomm bnep btusb bluetooth MachineType: LENOVO 20F6CTO1WW ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-19-generic root=/dev/mapper/ubuntu-root ro rootflags=subvol=@ quiet splash vt.handoff=7 RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/08/2019 dmi.bios.release: 1.44 dmi.bios.vendor: LENOVO dmi.bios.version: R02ET71W (1.44 ) dmi.board.asset.tag: Not Available dmi.board.name: 20F6CTO1WW dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.12 dmi.modalias: dmi:bvnLENOVO:bvrR02ET71W(1.44):bd05/08/2019:br1.44:efr1.12:svnLENOVO:pn20F6CTO1WW:pvrThinkPadX260:skuLENOVO_MT_20F6_BU_Think_FM_ThinkPadX260:rvnLENOVO:rn20F6CTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X260 dmi.product.name: 20F6CTO1WW dmi.product.sku: LENOVO_MT_20F6_BU_Think_FM_ThinkPad X260 dmi.product.version: ThinkPad X260 dmi.sys.vendor: LENOVO hciconfig: hci0:Type: Primary Bus: USB BD Address: E4:A7:A0:01:19:D5 ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING RX bytes:56756 acl:285 sco:0 events:6453 errors:0 TX bytes:3721263 acl:3477 sco:0 commands:2751 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1949075/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1960448] Re: Sony WF-XB700 Bluetooth headset not detected
** Changed in: bluez (Ubuntu) Status: Incomplete => New ** Changed in: gnome-bluetooth (Ubuntu) Status: Incomplete => New ** Also affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-bluetooth in Ubuntu. https://bugs.launchpad.net/bugs/1960448 Title: Sony WF-XB700 Bluetooth headset not detected Status in bluez package in Ubuntu: New Status in gnome-bluetooth package in Ubuntu: New Status in linux package in Ubuntu: New Bug description: Gnome-bluetooth does not detect Sony WF-XB700 bluetooth headset. Installed blueman to try to figure out if this is related to gnome- bluetooth - the results are the same. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-bluetooth 3.34.5-4 ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12 Uname: Linux 5.15.0-18-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu76 Architecture: amd64 CasperMD5CheckResult: unknown Date: Wed Feb 9 22:01:56 2022 InstallationDate: Installed on 2021-09-09 (153 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) SourcePackage: gnome-bluetooth UpgradeStatus: Upgraded to jammy on 2022-01-13 (27 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1960448/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1876632] Re: [nvidia] Corrupted/missing shell textures when switching users or resuming from suspend
** Bug watch added: gitlab.gnome.org/GNOME/mutter/-/issues #1942 https://gitlab.gnome.org/GNOME/mutter/-/issues/1942 ** Also affects: mutter via https://gitlab.gnome.org/GNOME/mutter/-/issues/1942 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1876632 Title: [nvidia] Corrupted/missing shell textures when switching users or resuming from suspend Status in GNOME Shell: Unknown Status in Mutter: Unknown Status in gnome-shell package in Ubuntu: Triaged Status in mutter package in Ubuntu: Triaged Status in nvidia-graphics-drivers-440 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-460 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-470 package in Ubuntu: Confirmed Bug description: I recently installed ubuntu 20.04 on my computer, and I am running into an issue when I do the following: * Login with a user on desktop * Select switch user, and login as second user * Switch user again, and return to original user At this point, text and icons in the menubar / sidebar are corrupted. Text and icons in normal windows appear correctly. I have attached a screenshot of what this looks like. Screenshots: https://imgur.com/a/3ZFDLMc ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30 Uname: Linux 5.4.0-28-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..09.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:09:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 440.64 Fri Feb 21 01:17:26 UTC 2020 GCC version: ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun May 3 18:12:45 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GP104 [GeForce GTX 1070] [10de:1b81] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. GP104 [GeForce GTX 1070] [1043:85a0] InstallationDate: Installed on 2020-05-03 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Gigabyte Technology Co., Ltd. AX370-Gaming ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-28-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/19/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F3 dmi.board.asset.tag: Default string dmi.board.name: AX370-Gaming-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: se1 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF3:bd06/19/2017:svnGigabyteTechnologyCo.,Ltd.:pnAX370-Gaming:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnAX370-Gaming-CF:rvrse1:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: AX370-Gaming dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.4-2ubuntu1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1876632/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1676203] Re: Strange pixels after wakeup
*** This bug is a duplicate of bug 1876632 *** https://bugs.launchpad.net/bugs/1876632 This is an ongoing problem with the Nvidia drivers. Now tracking in bug 1876632. ** This bug has been marked a duplicate of bug 1876632 [nvidia] Corrupted/missing shell textures when switching users or resuming from suspend -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1676203 Title: Strange pixels after wakeup Status in xorg package in Ubuntu: Invalid Bug description: After ubuntu wakeup I experience a lot of pixels on desktop and on every context menu (after right click). You can see the problem in the attached screenshoot. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-67.88-generic 4.4.49 Uname: Linux 4.4.0-67-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia .proc.driver.nvidia.gpus..04.00.0: Error: [Errno 21] Jest katalogiem: '/proc/driver/nvidia/gpus/:04:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 375.39 Tue Jan 31 20:47:00 PST 2017 GCC version: gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.4) .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Sun Mar 26 19:55:41 2017 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Broadwell-U Integrated Graphics [8086:1616] (rev 09) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Broadwell-U Integrated Graphics [1043:1a6d] Subsystem: ASUSTeK Computer Inc. GK208M [GeForce 920M] [1043:1a6d] InstallationDate: Installed on 2016-10-06 (170 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) LightdmLog: [+17450.89s] DEBUG: User /org/freedesktop/Accounts/User126 added Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller Bus 001 Device 007: ID 13d3:3423 IMC Networks Bus 001 Device 002: ID 0bda:57b5 Realtek Semiconductor Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. X555LJ ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-67-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/04/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X555LJ.504 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X555LJ dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX555LJ.504:bd08/04/2015:svnASUSTeKCOMPUTERINC.:pnX555LJ:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX555LJ:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: X555LJ dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.70-1~ubuntu16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.6-0ubuntu0.16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.6-0ubuntu0.16.04.1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Sun Mar 26 07:58:24 2017 xserver.configfile: /etc/X11/xorg.conf xserver.errors: evdev: BluetoothMouse3600: Unable to open evdev device "/dev/input/event13". xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.18.4-0ubuntu0.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1676203/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 980519] Re: Random log off in Ubuntu 12.04 LTS
Sorry, this bug is very old and this version of Ubuntu isn't supported any more. If you think you have a similar issue, please file a new bug. ** Package changed: fedora => libgweather4 (Ubuntu) ** No longer affects: libgweather4 (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/980519 Title: Random log off in Ubuntu 12.04 LTS Status in Unity: Fix Released Status in gnome-desktop package in Ubuntu: Invalid Status in nvidia-graphics-drivers package in Ubuntu: Fix Released Status in unity package in Ubuntu: Fix Released Status in xorg package in Ubuntu: Fix Released Bug description: I get logged off from Ubuntu sometimes. There is no error message or any indication that it is going to log off. The screen goes black, and after 2-4 seconds, i get presented with the Ubuntu Log On Screen. There is no clear pattern (or at least if have not noticed any). One time i am working with Netbeans, another time i am using firefox. This also means that at present i can not clearly say what package might be causing this behaviour. I am fairly sure the problem lies in 12.04 (or more precise - the combination of 12.04 and the hardware i am using). I do not have the same problem running 11.04 or 11.10. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/980519/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 980519] Re: Random log off in Ubuntu 12.04 LTS
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: libgweather4 (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/980519 Title: Random log off in Ubuntu 12.04 LTS Status in Unity: Fix Released Status in gnome-desktop package in Ubuntu: Invalid Status in nvidia-graphics-drivers package in Ubuntu: Fix Released Status in unity package in Ubuntu: Fix Released Status in xorg package in Ubuntu: Fix Released Bug description: I get logged off from Ubuntu sometimes. There is no error message or any indication that it is going to log off. The screen goes black, and after 2-4 seconds, i get presented with the Ubuntu Log On Screen. There is no clear pattern (or at least if have not noticed any). One time i am working with Netbeans, another time i am using firefox. This also means that at present i can not clearly say what package might be causing this behaviour. I am fairly sure the problem lies in 12.04 (or more precise - the combination of 12.04 and the hardware i am using). I do not have the same problem running 11.04 or 11.10. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/980519/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 980519] Re: Random log off in Ubuntu 12.04 LTS
** Changed in: gnome-desktop (Ubuntu) Status: Confirmed => Fix Released ** Changed in: gnome-desktop (Ubuntu) Status: Fix Released => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/980519 Title: Random log off in Ubuntu 12.04 LTS Status in Unity: Fix Released Status in gnome-desktop package in Ubuntu: Invalid Status in nvidia-graphics-drivers package in Ubuntu: Fix Released Status in unity package in Ubuntu: Fix Released Status in xorg package in Ubuntu: Fix Released Bug description: I get logged off from Ubuntu sometimes. There is no error message or any indication that it is going to log off. The screen goes black, and after 2-4 seconds, i get presented with the Ubuntu Log On Screen. There is no clear pattern (or at least if have not noticed any). One time i am working with Netbeans, another time i am using firefox. This also means that at present i can not clearly say what package might be causing this behaviour. I am fairly sure the problem lies in 12.04 (or more precise - the combination of 12.04 and the hardware i am using). I do not have the same problem running 11.04 or 11.10. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/980519/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1960753] Re: Remove the gnome-user-guide binary from jammy
The Ubuntu Archive team will remove gnome-user-guide soon since it's in green at https://people.canonical.com/~ubuntu-archive/nbs.html ** Changed in: gnome-user-docs (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-user-docs in Ubuntu. https://bugs.launchpad.net/bugs/1960753 Title: Remove the gnome-user-guide binary from jammy Status in gnome-user-docs package in Ubuntu: Invalid Bug description: Not sure if this needs to be dealt with manually, but to be safe: The gnome-user-guide binary is a transitional dummy package which has been built by the gnome-user-docs source package and which is not longer needed. It was not built by the latest gnome-user-docs upload (41.2-1ubuntu1). But even if gnome-user-docs 41.2-1ubuntu1 migrated successfully, gnome-user-guide 41.1-1ubuntu1 seems to be kept in the jammy archive. So I'm asking for the removal of the latter. $ apt rdepends gnome-user-guide gnome-user-guide Reverse Depends: |Suggests: unity-control-center It's my understanding that no explicit request is needed for the equivalent removal at Debian: https://www.debian.org/doc/manuals/developers- reference/pkgs.en.html#removing-packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-user-docs/+bug/1960753/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1960756] [NEW] VNC connection to Wayland / PipeWire aborts
Public bug reported: Connecting to a modern installation of Ubuntu 21.10 Impish Indri using the Wayland display server (and PipeWire / gnome-remote-desktop) does not work from the current LTS release 20.04 Focal Fossa. It aborts immediately after authentication. The bug appears directly related to the version 1.4.2 in focal, as building the up-to-date remmina version 1.4.23 package (from jammy) under focal does not exhibit the faulty behavior. Since future versions of Ubuntu itself will likely stick with Wayland and therefore cannot be used with Remmina from the LTS release anymore, I think an SRU might be in order. As a workaround, other VNC viewers such as Vinagre are able to connect to the same server under focal. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: remmina-plugin-vnc 1.4.2+dfsg-1ubuntu1 ProcVersionSignature: Ubuntu 5.13.0-28.31~20.04.1-lowlatency 5.13.19 Uname: Linux 5.13.0-28-lowlatency x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: GNOME Date: Sun Feb 13 21:17:06 2022 InstallationDate: Installed on 2012-10-22 (3400 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5) SourcePackage: remmina UpgradeStatus: Upgraded to focal on 2020-08-30 (531 days ago) ** Affects: remmina (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to remmina in Ubuntu. https://bugs.launchpad.net/bugs/1960756 Title: VNC connection to Wayland / PipeWire aborts Status in remmina package in Ubuntu: New Bug description: Connecting to a modern installation of Ubuntu 21.10 Impish Indri using the Wayland display server (and PipeWire / gnome-remote-desktop) does not work from the current LTS release 20.04 Focal Fossa. It aborts immediately after authentication. The bug appears directly related to the version 1.4.2 in focal, as building the up-to-date remmina version 1.4.23 package (from jammy) under focal does not exhibit the faulty behavior. Since future versions of Ubuntu itself will likely stick with Wayland and therefore cannot be used with Remmina from the LTS release anymore, I think an SRU might be in order. As a workaround, other VNC viewers such as Vinagre are able to connect to the same server under focal. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: remmina-plugin-vnc 1.4.2+dfsg-1ubuntu1 ProcVersionSignature: Ubuntu 5.13.0-28.31~20.04.1-lowlatency 5.13.19 Uname: Linux 5.13.0-28-lowlatency x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: GNOME Date: Sun Feb 13 21:17:06 2022 InstallationDate: Installed on 2012-10-22 (3400 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5) SourcePackage: remmina UpgradeStatus: Upgraded to focal on 2020-08-30 (531 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/remmina/+bug/1960756/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1960753] [NEW] Remove the gnome-user-guide binary from jammy
Public bug reported: Not sure if this needs to be dealt with manually, but to be safe: The gnome-user-guide binary is a transitional dummy package which has been built by the gnome-user-docs source package and which is not longer needed. It was not built by the latest gnome-user-docs upload (41.2-1ubuntu1). But even if gnome-user-docs 41.2-1ubuntu1 migrated successfully, gnome- user-guide 41.1-1ubuntu1 seems to be kept in the jammy archive. So I'm asking for the removal of the latter. $ apt rdepends gnome-user-guide gnome-user-guide Reverse Depends: |Suggests: unity-control-center It's my understanding that no explicit request is needed for the equivalent removal at Debian: https://www.debian.org/doc/manuals/developers- reference/pkgs.en.html#removing-packages ** Affects: gnome-user-docs (Ubuntu) Importance: Undecided Status: New ** Tags: jammy -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-user-docs in Ubuntu. https://bugs.launchpad.net/bugs/1960753 Title: Remove the gnome-user-guide binary from jammy Status in gnome-user-docs package in Ubuntu: New Bug description: Not sure if this needs to be dealt with manually, but to be safe: The gnome-user-guide binary is a transitional dummy package which has been built by the gnome-user-docs source package and which is not longer needed. It was not built by the latest gnome-user-docs upload (41.2-1ubuntu1). But even if gnome-user-docs 41.2-1ubuntu1 migrated successfully, gnome-user-guide 41.1-1ubuntu1 seems to be kept in the jammy archive. So I'm asking for the removal of the latter. $ apt rdepends gnome-user-guide gnome-user-guide Reverse Depends: |Suggests: unity-control-center It's my understanding that no explicit request is needed for the equivalent removal at Debian: https://www.debian.org/doc/manuals/developers- reference/pkgs.en.html#removing-packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-user-docs/+bug/1960753/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1954429] Re: The required package for GNOME Classic not mentioned in docs
Fixed through gnome-user-docs 41.2-1ubuntu1. ** Changed in: gnome-user-docs (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-user-docs in Ubuntu. https://bugs.launchpad.net/bugs/1954429 Title: The required package for GNOME Classic not mentioned in docs Status in Gnome Documentation: Unknown Status in gnome-user-docs package in Ubuntu: Fix Released Bug description: On this page https://help.ubuntu.com/stable/ubuntu-help/gnome- classic.html.en is described how to switch between user interfaces, but instead of "Switch to and from GNOME Classic" I can choose to switch between Ubuntu and Ubuntu Xorg, that actually doesn't make any changes at my system's interface. I'm using Ubuntu 21.10 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-user-docs/+bug/1954429/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1960751] Re: upower hogs CPU (50%, 27% etc, laptop lags)
capture of top output, such CPU use seems suspicious ** Attachment added: "Peek 2022-02-13 18-50.gif" https://bugs.launchpad.net/ubuntu/+source/upower/+bug/1960751/+attachment/5560703/+files/Peek%202022-02-13%2018-50.gif -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to upower in Ubuntu. https://bugs.launchpad.net/bugs/1960751 Title: upower hogs CPU (50%, 27% etc, laptop lags) Status in upower package in Ubuntu: New Bug description: `upower --monitor-detail` has shown noninsane battery info twice and is silent otherwise, `upowerd` appears in `top` as eating 27%, 50% CPU (not all the time, but most of the time it is somehow top user of CPU) Computer become noticeably laggy recently, `upowerd` is so far sole abnormal symptom I was advised to file bug by people from Lubuntu Telegram channel. I would be happy to provide more info, but plan to reinstall OS soon due to macabre lagginess. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: upower 0.99.11-1build2 ProcVersionSignature: Ubuntu 5.4.0-99.112-lowlatency 5.4.162 Uname: Linux 5.4.0-99-lowlatency x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: LXQt Date: Sun Feb 13 18:42:10 2022 InstallationDate: Installed on 2021-01-06 (403 days ago) InstallationMedia: Lubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) SourcePackage: upower UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/upower/+bug/1960751/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1960751] Re: upower hogs CPU (50%, 27% etc, laptop lags)
https://bugs.launchpad.net/ubuntu/+source/upower/+bug/1420395 is similar but with distinct symptoms - here too many updates appear to be not the cause of insane CPU use -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to upower in Ubuntu. https://bugs.launchpad.net/bugs/1960751 Title: upower hogs CPU (50%, 27% etc, laptop lags) Status in upower package in Ubuntu: New Bug description: `upower --monitor-detail` has shown noninsane battery info twice and is silent otherwise, `upowerd` appears in `top` as eating 27%, 50% CPU (not all the time, but most of the time it is somehow top user of CPU) Computer become noticeably laggy recently, `upowerd` is so far sole abnormal symptom I was advised to file bug by people from Lubuntu Telegram channel. I would be happy to provide more info, but plan to reinstall OS soon due to macabre lagginess. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: upower 0.99.11-1build2 ProcVersionSignature: Ubuntu 5.4.0-99.112-lowlatency 5.4.162 Uname: Linux 5.4.0-99-lowlatency x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: LXQt Date: Sun Feb 13 18:42:10 2022 InstallationDate: Installed on 2021-01-06 (403 days ago) InstallationMedia: Lubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) SourcePackage: upower UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/upower/+bug/1960751/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1960751] [NEW] upower hogs CPU (50%, 27% etc, laptop lags)
Public bug reported: `upower --monitor-detail` has shown noninsane battery info twice and is silent otherwise, `upowerd` appears in `top` as eating 27%, 50% CPU (not all the time, but most of the time it is somehow top user of CPU) Computer become noticeably laggy recently, `upowerd` is so far sole abnormal symptom I was advised to file bug by people from Lubuntu Telegram channel. I would be happy to provide more info, but plan to reinstall OS soon due to macabre lagginess. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: upower 0.99.11-1build2 ProcVersionSignature: Ubuntu 5.4.0-99.112-lowlatency 5.4.162 Uname: Linux 5.4.0-99-lowlatency x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: LXQt Date: Sun Feb 13 18:42:10 2022 InstallationDate: Installed on 2021-01-06 (403 days ago) InstallationMedia: Lubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) SourcePackage: upower UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: upower (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to upower in Ubuntu. https://bugs.launchpad.net/bugs/1960751 Title: upower hogs CPU (50%, 27% etc, laptop lags) Status in upower package in Ubuntu: New Bug description: `upower --monitor-detail` has shown noninsane battery info twice and is silent otherwise, `upowerd` appears in `top` as eating 27%, 50% CPU (not all the time, but most of the time it is somehow top user of CPU) Computer become noticeably laggy recently, `upowerd` is so far sole abnormal symptom I was advised to file bug by people from Lubuntu Telegram channel. I would be happy to provide more info, but plan to reinstall OS soon due to macabre lagginess. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: upower 0.99.11-1build2 ProcVersionSignature: Ubuntu 5.4.0-99.112-lowlatency 5.4.162 Uname: Linux 5.4.0-99-lowlatency x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: LXQt Date: Sun Feb 13 18:42:10 2022 InstallationDate: Installed on 2021-01-06 (403 days ago) InstallationMedia: Lubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) SourcePackage: upower UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/upower/+bug/1960751/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1874120] Re: package chromium-browser 80.0.3987.163-0ubuntu0.18.04.1 failed to install/upgrade: new chromium-browser package pre-installation script subprocess returned error e
I do not need chromium--just getting notifications and that red minus sign RT -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1874120 Title: package chromium-browser 80.0.3987.163-0ubuntu0.18.04.1 failed to install/upgrade: new chromium-browser package pre-installation script subprocess returned error exit status 1 Status in chromium-browser package in Ubuntu: Expired Bug description: error appeared when opening chrome ProblemType: Package DistroRelease: Ubuntu 20.04 Package: chromium-browser 80.0.3987.163-0ubuntu0.18.04.1 ProcVersionSignature: Ubuntu 4.15.0-96.97-generic 4.15.18 Uname: Linux 4.15.0-96-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 DRM.card0-HDMI-A-1: enabled: enabled dpms: On status: connected edid-base64: AP///wAEaTDjAQEBAQkXAQOAMBt47umEpVVImyYSUFQBAQEBAQEBAQEBAQEBAQEBAjqAGHE4LUBYLEUA3w0RAAAe/QAwTBhkCgAKICAgICAg/ABFVDIyMjFJCiAgICAg/wBBU1VTMjAxMzAzMDEKAEI= modes: 1920x1080 DRM.card0-HDMI-A-2: enabled: disabled dpms: Off status: disconnected edid-base64: modes: DRM.card0-VGA-1: enabled: disabled dpms: Off status: disconnected edid-base64: modes: Date: Tue Apr 21 23:33:33 2020 Desktop-Session: 'None' 'None' 'None' Env: 'None' 'None' ErrorMessage: new chromium-browser package pre-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2015-03-28 (1851 days ago) InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1) Load-Avg-1min: 3.38 Load-Processes-Running-Percent: 0.2% MachineType: ASUSTeK COMPUTER INC. ET2221I-B85 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-96-generic root=UUID=e54296a0-874c-412b-9fc6-092c89bdfa74 ro quiet splash vt.handoff=7 Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18rc1, python-is-python2, 2.7.17-4 SourcePackage: chromium-browser Title: package chromium-browser 80.0.3987.163-0ubuntu0.18.04.1 failed to install/upgrade: new chromium-browser package pre-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to focal on 2020-04-21 (0 days ago) dmi.bios.date: 11/05/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0503 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: ET2221I-B85 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0503:bd11/05/2013:svnASUSTeKCOMPUTERINC.:pnET2221I-B85:pvr0503:rvnASUSTeKCOMPUTERINC.:rnET2221I-B85:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: All-In-One dmi.product.name: ET2221I-B85 dmi.product.version: 0503 dmi.sys.vendor: ASUSTeK COMPUTER INC. modified.conffile..etc.default.chromium-browser: [deleted] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1874120/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1574154] Re: xorg.conf changed on start of lightdm service
Wow, a reply on a bug report after 6 years! I did not mean this to be negative, just surprised that I got a response this late. I forgot all about it, but this brings a lot back. Back then, I was mostly wondering what was in the mind of someone to change a user-modifiable config file.. But anyway, the T540 is running 20.04 now, and I dont see that problem anymore; maybe because I dont use a xorg.conf currently. And, the T540 is currently retiring ;-) Anyway, No problem for me anymore. Status can be changed to 'Time made us forget this' ;-) Btw: I'm still proud of my quick fix: 'chattr +i xorg.conf' ;-) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1574154 Title: xorg.conf changed on start of lightdm service Status in xorg package in Ubuntu: Incomplete Bug description: After upgrading from 15.10 (Wily) to 16.04 (Xenial), X wont start. It appears that my xorg.conf is modified such that I get a non-working way (I get a coredump in the video driver I think). I have a Thinkpad T530 with dual video cards, so I change the from the nvidia that is somewere(?) auto selected back to intel. Alas, restarting of lightdm service does not work: xorg.conf is re-modified. Manually starting a X session with 'startx' (after correcting xorg.conf) works as expected. Alas, nobody logs about this; that would have helped me find the culprit.. Who modifies my xorg.conf? Why? This never happened before, and should IMHO not be done. Temporary solution: 'chattr +i /etc/X11/xorg.conf'. This makes auto- changing impossible. But this is a hack. I should be allowed to change my system such that it works the way I want. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg (not installed) ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CurrentDesktop: MATE Date: Sun Apr 24 05:45:17 2016 SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: Upgraded to xenial on 2016-04-21 (2 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1574154/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1960747] Re: Autorotation of screen does not work on wayland, but on X
** Description changed: When physically rotating my 2-in-1 laptop Lenovo Yoga 7 Gen 6 AMD - 14ACN6, screen rotates properly under X, but not under Wayland. Also the lock screen rotation option is missing in the top-right menu under Wayland. It exists in X. - `iio-sensor-proxy` is loaded correctly: - ``` - systemctl status iio-sensor-proxy.service + + iio-sensor-proxy is being loaded correctly: + + --- + $ systemctl status iio-sensor-proxy.service ● iio-sensor-proxy.service - IIO Sensor Proxy service - Loaded: loaded (/lib/systemd/system/iio-sensor-proxy.service; static) - Active: active (running) since Sun 2022-02-13 15:43:37 CET; 2h 12min ago -Main PID: 787 (iio-sensor-prox) - Tasks: 3 (limit: 16544) - Memory: 1.4M - CPU: 5.688s - CGroup: /system.slice/iio-sensor-proxy.service - └─787 /usr/libexec/iio-sensor-proxy + Loaded: loaded (/lib/systemd/system/iio-sensor-proxy.service; static) + Active: active (running) since Sun 2022-02-13 15:43:37 CET; 2h 12min ago + Main PID: 787 (iio-sensor-prox) + Tasks: 3 (limit: 16544) + Memory: 1.4M + CPU: 5.688s + CGroup: /system.slice/iio-sensor-proxy.service + └─787 /usr/libexec/iio-sensor-proxy Feb 13 15:43:36 michaels-yoga systemd[1]: Starting IIO Sensor Proxy service... Feb 13 15:43:37 michaels-yoga systemd[1]: Started IIO Sensor Proxy service. - ``` - and `monitor-sensor` detects the physical rotation: - ``` - monitor-sensor - Waiting for iio-sensor-proxy to appear + --- + + monitor-sensor detects the physical rotation: + + --- + $ monitor-sensor + Waiting for iio-sensor-proxy to appear +++ iio-sensor-proxy appeared === Has accelerometer (orientation: normal) === Has ambient light sensor (value: 70,29, unit: lux) === No proximity sensor - Light changed: 65,27 (lux) - Light changed: 160,66 (lux) - Accelerometer orientation changed: right-up - Light changed: 40,16 (lux) - Light changed: 45,18 (lux) - Light changed: 40,16 (lux) - Light changed: 25,10 (lux) - Accelerometer orientation changed: left-up - Light changed: 20,08 (lux) - Light changed: 25,10 (lux) - Light changed: 35,14 (lux) - Accelerometer orientation changed: normal - Light changed: 155,64 (lux) - Accelerometer orientation changed: bottom-up - Light changed: 30,12 (lux) - Light changed: 40,16 (lux) - Light changed: 30,12 (lux) - Light changed: 145,60 (lux) - Accelerometer orientation changed: normal - ``` - Putting the laptop in tablet mode disables keyboard and touchpad correctly both under Wayland and X. - So obviously the sensors are working correctly, but signals are not being interpreted correctly in Wayland? + Light changed: 65,27 (lux) + Light changed: 160,66 (lux) + Accelerometer orientation changed: right-up + Light changed: 40,16 (lux) + Light changed: 45,18 (lux) + Light changed: 40,16 (lux) + Light changed: 25,10 (lux) + Accelerometer orientation changed: left-up + Light changed: 20,08 (lux) + Light changed: 25,10 (lux) + Light changed: 35,14 (lux) + Accelerometer orientation changed: normal + Light changed: 155,64 (lux) + Accelerometer orientation changed: bottom-up + Light changed: 30,12 (lux) + Light changed: 40,16 (lux) + Light changed: 30,12 (lux) + Light changed: 145,60 (lux) + Accelerometer orientation changed: normal + --- + + Putting the laptop in tablet mode disables keyboard and touchpad + correctly both under Wayland and X. + + So obviously the sensors are working correctly, but signals are not + being interpreted correctly in Wayland? + + --- ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: xorg 1:7.7+22ubuntu2 Uname: Linux 5.15.0-051500-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 BootLog: Error: [Errno 13] Keine Berechtigung: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Feb 13 17:46:51 2022 DistUpgraded: Fresh install DistroCodename: impish DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: - Advanced Micro Devices, Inc. [AMD/ATI] Cezanne [1002:1638] (rev c1) (prog-if 00 [VGA controller]) -Subsystem: Lenovo Cezanne [17aa:3813] + Advanced Micro Devices, Inc. [AMD/ATI] Cezanne [1002:1638] (rev c1) (prog-if 00 [VGA controller]) + Subsystem: Lenovo Cezanne [17aa:3813] InstallationDate: Installed on 2022-02-11 (1 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) MachineType: LENOVO 82N7 ProcEnviron: - TERM=xterm-256color - PATH=(custom, no user) - XDG_RUNTIME_DIR= - LANG=de_DE.UTF-8 - SHELL=/bin/bash + TERM=xterm-256color + PATH=(custom, no user) + XDG_RUNTIME_DIR= +
[Desktop-packages] [Bug 1960747] [NEW] Autorotation of screen does not work on wayland, but on X
Public bug reported: When physically rotating my 2-in-1 laptop Lenovo Yoga 7 Gen 6 AMD - 14ACN6, screen rotates properly under X, but not under Wayland. Also the lock screen rotation option is missing in the top-right menu under Wayland. It exists in X. `iio-sensor-proxy` is loaded correctly: ``` systemctl status iio-sensor-proxy.service ● iio-sensor-proxy.service - IIO Sensor Proxy service Loaded: loaded (/lib/systemd/system/iio-sensor-proxy.service; static) Active: active (running) since Sun 2022-02-13 15:43:37 CET; 2h 12min ago Main PID: 787 (iio-sensor-prox) Tasks: 3 (limit: 16544) Memory: 1.4M CPU: 5.688s CGroup: /system.slice/iio-sensor-proxy.service └─787 /usr/libexec/iio-sensor-proxy Feb 13 15:43:36 michaels-yoga systemd[1]: Starting IIO Sensor Proxy service... Feb 13 15:43:37 michaels-yoga systemd[1]: Started IIO Sensor Proxy service. ``` and `monitor-sensor` detects the physical rotation: ``` monitor-sensor Waiting for iio-sensor-proxy to appear +++ iio-sensor-proxy appeared === Has accelerometer (orientation: normal) === Has ambient light sensor (value: 70,29, unit: lux) === No proximity sensor Light changed: 65,27 (lux) Light changed: 160,66 (lux) Accelerometer orientation changed: right-up Light changed: 40,16 (lux) Light changed: 45,18 (lux) Light changed: 40,16 (lux) Light changed: 25,10 (lux) Accelerometer orientation changed: left-up Light changed: 20,08 (lux) Light changed: 25,10 (lux) Light changed: 35,14 (lux) Accelerometer orientation changed: normal Light changed: 155,64 (lux) Accelerometer orientation changed: bottom-up Light changed: 30,12 (lux) Light changed: 40,16 (lux) Light changed: 30,12 (lux) Light changed: 145,60 (lux) Accelerometer orientation changed: normal ``` Putting the laptop in tablet mode disables keyboard and touchpad correctly both under Wayland and X. So obviously the sensors are working correctly, but signals are not being interpreted correctly in Wayland? ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: xorg 1:7.7+22ubuntu2 Uname: Linux 5.15.0-051500-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 BootLog: Error: [Errno 13] Keine Berechtigung: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Feb 13 17:46:51 2022 DistUpgraded: Fresh install DistroCodename: impish DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Cezanne [1002:1638] (rev c1) (prog-if 00 [VGA controller]) Subsystem: Lenovo Cezanne [17aa:3813] InstallationDate: Installed on 2022-02-11 (1 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) MachineType: LENOVO 82N7 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.15.0-051500-generic root=UUID=d1796991-349c-4784-b8c3-e0a2eb2fc132 ro rootflags=subvol=@ quiet splash mem_sleep_default=deep vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/12/2021 dmi.bios.release: 1.25 dmi.bios.vendor: LENOVO dmi.bios.version: H9CN25WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0T76463 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: LENOVO dmi.chassis.version: Yoga 7 14ACN6 dmi.ec.firmware.release: 1.25 dmi.modalias: dmi:bvnLENOVO:bvrH9CN25WW:bd11/12/2021:br1.25:efr1.25:svnLENOVO:pn82N7:pvrYoga714ACN6:rvnLENOVO:rnLNVNB161216:rvrSDK0T76463WIN:cvnLENOVO:ct31:cvrYoga714ACN6:skuLENOVO_MT_82N7_BU_idea_FM_Yoga714ACN6: dmi.product.family: Yoga 7 14ACN6 dmi.product.name: 82N7 dmi.product.sku: LENOVO_MT_82N7_BU_idea_FM_Yoga 7 14ACN6 dmi.product.version: Yoga 7 14ACN6 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.107-8ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.6-0ubuntu0.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1ubuntu2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1build1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug impish ubuntu wayland-session ** Summary changed: - Autorotation of screen does not work on wayland, but on xorg + Autorotation of screen does not work on wayland, but on X -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu.
[Desktop-packages] [Bug 1960742] [NEW] Xorg freeze
Public bug reported: before it crashes, 3 LEDs (Power, mayus,block number) turn on and turn off about 3 times.. And all will be freeze it needs to shutdown keeping pressed the I/O button ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.13.0-28.31~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-28-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 BootLog: Error: [Errno 13] Permiso denegado: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Feb 13 11:03:30 2022 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GpuHangFrequency: Continuously GpuHangReproducibility: Seems to happen randomly GpuHangStarted: Immediately after installing this version of Ubuntu GraphicsCard: Intel Corporation Device [8086:4e55] (rev 01) (prog-if 00 [VGA controller]) Subsystem: Intel Corporation Device [8086:2212] InstallationDate: Installed on 2022-02-09 (4 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) MachineType: INTEL V14 ProcEnviron: LANGUAGE=es_EC:es PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_EC.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-28-generic root=UUID=31ee87c2-d9b1-413d-bc93-15224f6ba1ec ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/25/2021 dmi.bios.release: 5.19 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: WZ362D.fBNAPLL02.2105061 dmi.board.asset.tag: Default string dmi.board.name: V14 dmi.board.vendor: INET dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 10 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.ec.firmware.release: 1.2 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrWZ362D.fBNAPLL02.2105061:bd05/25/2021:br5.19:efr1.2:svnINTEL:pnV14:pvrDefaultstring:rvnINET:rnV14:rvrDefaultstring:cvnDefaultstring:ct10:cvrDefaultstring:sku2105061: dmi.product.family: Jasper lake dmi.product.name: V14 dmi.product.sku: 2105061 dmi.product.version: Default string dmi.sys.vendor: INTEL version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.107-8ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.6-0ubuntu0.1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 21.2.6-0ubuntu0.1~20.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal freeze ubuntu -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1960742 Title: Xorg freeze Status in xorg package in Ubuntu: New Bug description: before it crashes, 3 LEDs (Power, mayus,block number) turn on and turn off about 3 times.. And all will be freeze it needs to shutdown keeping pressed the I/O button ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.13.0-28.31~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-28-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 BootLog: Error: [Errno 13] Permiso denegado: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Feb 13 11:03:30 2022 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GpuHangFrequency: Continuously GpuHangReproducibility: Seems to happen randomly GpuHangStarted: Immediately after installing this version of Ubuntu GraphicsCard: Intel Corporation Device [8086:4e55] (rev 01) (prog-if 00 [VGA controller]) Subsystem: Intel Corporation Device [8086:2212] InstallationDate: Installed on 2022-02-09 (4 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) MachineType: INTEL V14 ProcEnviron: LANGUAGE=es_EC:es PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_EC.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-28-generic root=UUID=31ee87c2-d9b1-413d-bc93-15224f6ba1ec ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/25/2021 dmi.bios.release: 5.19 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: WZ362D.fBNAPLL02.2105061 dmi.board.asset.tag:
[Desktop-packages] [Bug 1875845] Re: keyring cannot be unlocked if used fingerprint to login gnome session
Same here Description:Pop!_OS 20.04 LTS Release:20.04 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-keyring in Ubuntu. https://bugs.launchpad.net/bugs/1875845 Title: keyring cannot be unlocked if used fingerprint to login gnome session Status in GNOME Keyring: Unknown Status in gnome-keyring package in Ubuntu: Triaged Bug description: I upgraded to Ubuntu 20.04 and setup the fingerprint login. Today when I tried to launch remmina it didn't show up for a long time. I launch Gnome Password and Keys > Passwords > Login I see there's a button to click to unlock. Clicking the unlock button is still waiting forever. A moment later I logout current session and type in the user password to login. Then I could launch remmina and unlock the Gnome Password and Keys. System info ❯ lsb_release -rd Description: Ubuntu 20.04 LTS Release: 20.04 ~ ❯ apt-cache policy gnome-keyring gnome-keyring: Installed: 3.36.0-1ubuntu1 Candidate: 3.36.0-1ubuntu1 Version table: *** 3.36.0-1ubuntu1 500 500 http://ftp.cuhk.edu.hk/pub/Linux/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-keyring/+bug/1875845/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1960737] [NEW] /usr/lib/x86_64-linux-gnu/libgtk-3-0/gtk-query-immodules-3.0: symbol lookup error: /usr/lib/x86_64-linux-gnu/libgdk-3.so.0: undefined symbol: wl_proxy_marshal_fl
Public bug reported: /usr/lib/x86_64-linux-gnu/libgtk-3-0/gtk-query-immodules-3.0: symbol lookup error: /usr/lib/x86_64-linux-gnu/libgdk-3.so.0: undefined symbol: wl_proxy_marshal_flags ** Affects: gtk+3.0 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1960737 Title: /usr/lib/x86_64-linux-gnu/libgtk-3-0/gtk-query-immodules-3.0: symbol lookup error: /usr/lib/x86_64-linux-gnu/libgdk-3.so.0: undefined symbol: wl_proxy_marshal_flags Status in gtk+3.0 package in Ubuntu: New Bug description: /usr/lib/x86_64-linux-gnu/libgtk-3-0/gtk-query-immodules-3.0: symbol lookup error: /usr/lib/x86_64-linux-gnu/libgdk-3.so.0: undefined symbol: wl_proxy_marshal_flags To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1960737/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1955904] Re: Sync glibmm2.4 2.66.2-1 (main) from Debian unstable (main)
** Changed in: glibmm2.4 (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to glibmm2.4 in Ubuntu. https://bugs.launchpad.net/bugs/1955904 Title: Sync glibmm2.4 2.66.2-1 (main) from Debian unstable (main) Status in glibmm2.4 package in Ubuntu: Fix Released Bug description: Please sync glibmm2.4 2.66.2-1 (main) from Debian unstable (main) The version 2.66.1 has an important fix of #1955044 Upstream discussion of the issue: https://mail.gnome.org/archives/gtkmm-list/2021-May/msg7.html Changelog entries since current jammy version 2.64.2-2build1: glibmm2.4 (2.66.2-1) unstable; urgency=high * New upstream release - Fix jackd segfault (Closes: #994969) -- Jeremy Bicha Sun, 10 Oct 2021 20:58:47 -0400 glibmm2.4 (2.66.1-1) unstable; urgency=medium * New upstream release * Build with meson * Build-Depend on glib-networking * debian/rules: Drop unneeded -Wl,--as-needed * Bump debhelper-compat to 13 -- Jeremy Bicha Sun, 19 Sep 2021 09:22:18 -0400 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glibmm2.4/+bug/1955904/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
