[Desktop-packages] [Bug 1977986] Re: UPower and battery indicator show update in 2 minutes when connecting power cable ThinkPad
** Tags added: originate-from-2063092 -- 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/1977986 Title: UPower and battery indicator show update in 2 minutes when connecting power cable ThinkPad Status in OEM Priority Project: In Progress Status in upower package in Ubuntu: New Bug description: We found this issue on several ThinkPad. The upower will change 'pending-charge' to 'charging' after 2 minutes later, but the /sys/class/power_supply/BAT0/status changes to 'Charging' immediately when connecting the power cable. $ upower -i /org/freedesktop/UPower/devices/battery_BAT0 native-path: BAT0 vendor: Sunwoda model:5B10W13975 serial: 34226 power supply: yes updated: Wed 08 Jun 2022 11:42:02 PM CST (1 seconds ago) has history: yes has statistics: yes battery present: yes rechargeable:yes state: pending-charge warning-level: none energy: 55.94 Wh energy-empty:0 Wh energy-full: 57 Wh energy-full-design: 57 Wh energy-rate: 5.79 W voltage: 16.688 V percentage: 98% capacity:100% technology: lithium-polymer icon-name: 'battery-full-charging-symbolic' History (charge): 1654702882 98.000 pending-charge 1654702863 97.000 pending-charge History (rate): 1654702863 5.790 pending-charge 1654702863 6.171 pending-charge $ cat /sys/class/power_supply/BAT0/status Charging To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1977986/+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 2014954] Re: Backport Intel Mutual Authentications - FCC Lock
** Changed in: libmbim (Ubuntu Jammy) Status: New => Invalid ** Changed in: libmbim (Ubuntu) Status: In Progress => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libmbim in Ubuntu. https://bugs.launchpad.net/bugs/2014954 Title: Backport Intel Mutual Authentications - FCC Lock Status in OEM Priority Project: Won't Fix Status in libmbim package in Ubuntu: Invalid Status in libmbim source package in Jammy: Invalid Status in libmbim source package in Lunar: Won't Fix Bug description: [ Impact ] There exist no formal API to do the FCC unlock procedure[1] in the latest version of the modemmanger. But there is a merged commit[2] that provide this functionality for intel WWAN cards in the upstream project. Lenovo have several laptops using the Fibocom WWAN cards (Intel XMM 7560), and Lenovo are struggling to give a decent way to run the FCC unlock service without this. Until the device is unlocked, the end users are not able to use the SIM cards, and some of the affected devices have already been shipped. The end users now have to go to the Lenovo support website and download a few scripts and binaries to unlock the device to make their SIM cards work. The Lenovo wants this patch to be included in jammy, then they can provide the FCC unlock service and manage it in OEM-archive, so the end users can use SIM cards as soon as they receive the laptop. [ Test Plan ] OEM enablement engineers and Lenovo engineers will help to test if the FCC unlock would work on certain laptops with the help of a custom package[1] provided by Lenovo which contains the FCC unlock script. [ Where problems could occur ] This is a completely new feature to support Intel WWAN cards mutal authentication, which does not affect other existing features. But the feature itself might have bugs and glitches since it is a brand new one and is not widely tested by the laptop vendors, still it is better than nothing. [ Other Info ] [1] FCC unlock procedure: https://modemmanager.org/docs/modemmanager/fcc-unlock/ [2] intel-mutual-authentication: new service, fcc-lock: https://gitlab.freedesktop.org/mobile-broadband/libmbim/-/merge_requests/157 - when the device is first shipped or comes out of the factory, it should be protected with a lock till the device reaches the end user. This FCC lock feature will ensure the device is secured till its unlocked. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/2014954/+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 2051074] Re: Mirror mode doesn't work when panel only supports one refresh rate with reduced blanking
** Tags added: originate-from-2047204 sutton -- 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/2051074 Title: Mirror mode doesn't work when panel only supports one refresh rate with reduced blanking Status in HWE Next: New Status in OEM Priority Project: New Status in mutter package in Ubuntu: Fix Committed Status in mutter source package in Jammy: Fix Released Status in mutter source package in Mantic: Fix Released Status in mutter source package in Noble: Fix Committed Bug description: [Impact] On systems equipped with reduced blanking panel, mirror mode can result to no image on external monitor. The reason is due to current fallback modes don't have pixelclock for reduced blanking, so inadequate refresh rate is used to mode set, and result with atomic commit failure. [Fix] https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/3449 Add reduced blanking (RB) to fallback modes, so mutter can use RB mode to meet pixelclock requirement in order to pick the right refresh rate. [Test] Connect an external monitor to affected system. Use the monitor hotkey to switch to mirror mode or use GNOME control center to choose mirror mode. With the patch included, the issue is no longer observed. [Where problems could occur] The modelines of reduced blanking have reversed Hsync and Vsync flags, so if the driver doesn't handle those flags correctly, the atomic modeset/commit may fail. I haven't observe any issue on Intel/AMD/Nvidia GPU so far. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2051074/+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 2058202] [NEW] Support Goodix MoC fingerprint[27C6:659A]
Public bug reported: commit 489332c07da4092adf75e28d86e1c9dad744af7a Author: yangdi Date: Tue Jul 19 11:37:09 2022 +0800 goodixmoc: add PID 0x659A ** Affects: libfprint (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libfprint in Ubuntu. https://bugs.launchpad.net/bugs/2058202 Title: Support Goodix MoC fingerprint[27C6:659A] Status in libfprint package in Ubuntu: New Bug description: commit 489332c07da4092adf75e28d86e1c9dad744af7a Author: yangdi Date: Tue Jul 19 11:37:09 2022 +0800 goodixmoc: add PID 0x659A To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libfprint/+bug/2058202/+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 2058013] [NEW] Support Elan fp device [04F3:0C8C]
Public bug reported: This patch is upstreamed: - https://gitlab.freedesktop.org/libfprint/libfprint/-/merge_requests/374 [Impact] * Support Elan [04f3:0c8c] fingerprint component. [Test Plan] * Find a machine with this fingerprint device * Find a machine with other fingerprint device (e.g. 04f3:0c8c) * Launch `settings` and enable `Fingerprint Login` * Enroll finger and then logout on both machines. * Login system with enrolled finger on both machines. [Where problems could occur] * The patch also includes part for [04f3:0c8d]. * We did the similar support for 04f3:0c99. Bug #2031872 , the risk is low. ** Affects: oem-priority Importance: Undecided Status: New ** Affects: libfprint (Ubuntu) Importance: Undecided Status: New ** Tags: oem-priority originate-from-2058001 sutton ** Tags added: oem-priority originate-from-2058001 sutton -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libfprint in Ubuntu. https://bugs.launchpad.net/bugs/2058013 Title: Support Elan fp device [04F3:0C8C] Status in OEM Priority Project: New Status in libfprint package in Ubuntu: New Bug description: This patch is upstreamed: - https://gitlab.freedesktop.org/libfprint/libfprint/-/merge_requests/374 [Impact] * Support Elan [04f3:0c8c] fingerprint component. [Test Plan] * Find a machine with this fingerprint device * Find a machine with other fingerprint device (e.g. 04f3:0c8c) * Launch `settings` and enable `Fingerprint Login` * Enroll finger and then logout on both machines. * Login system with enrolled finger on both machines. [Where problems could occur] * The patch also includes part for [04f3:0c8d]. * We did the similar support for 04f3:0c99. Bug #2031872 , the risk is low. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/2058013/+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 2054538] [NEW] Support FPC MOC fingerprint [10a5:d805]
Public bug reported: The finger print device cannot work. $ lsusb -s 003 -vv Bus 003 Device 003: ID 10a5:d805 FPC FPC L:0002 FW:2127051 Couldn't open device, some information will be missing Device Descriptor: bLength 18 bDescriptorType 1 bcdUSB 2.00 bDeviceClass 0 bDeviceSubClass 0 bDeviceProtocol 0 bMaxPacketSize0 64 idVendor 0x10a5 idProduct 0xd805 bcdDevice 0.51 iManufacturer 1 FPC iProduct 2 FPC L:0002 FW:2127051 iSerial 0 bNumConfigurations 1 Configuration Descriptor: bLength 9 bDescriptorType 2 wTotalLength 0x0019 bNumInterfaces 1 bConfigurationValue 1 iConfiguration 4 bmAttributes 0xa0 (Bus Powered) Remote Wakeup MaxPower 100mA Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber 0 bAlternateSetting 0 bNumEndpoints 1 bInterfaceClass 255 Vendor Specific Class bInterfaceSubClass 255 Vendor Specific Subclass bInterfaceProtocol 255 Vendor Specific Protocol iInterface 5 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x81 EP 1 IN bmAttributes 2 Transfer Type Bulk Synch Type None Usage Type Data wMaxPacketSize 0x0040 1x 64 bytes bInterval 0 [Steps to reproduce] Boot up the system, try to use the finger print related function. [Expected result] The FPR should work [Actual result] The FPR doesn't work [Failure rate] 100% [Additional information] Ubuntu: 22.04 kernel-version: 6.5.0-1014-oem ** Affects: oem-priority Importance: Undecided Status: New ** Affects: libfprint (Ubuntu) Importance: Undecided Status: New ** Tags: oem-priority originate-from-2054422 sutton ** Tags added: oem-priority originate-from-2054422 sutton -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libfprint in Ubuntu. https://bugs.launchpad.net/bugs/2054538 Title: Support FPC MOC fingerprint [10a5:d805] Status in OEM Priority Project: New Status in libfprint package in Ubuntu: New Bug description: The finger print device cannot work. $ lsusb -s 003 -vv Bus 003 Device 003: ID 10a5:d805 FPC FPC L:0002 FW:2127051 Couldn't open device, some information will be missing Device Descriptor: bLength 18 bDescriptorType 1 bcdUSB 2.00 bDeviceClass 0 bDeviceSubClass 0 bDeviceProtocol 0 bMaxPacketSize0 64 idVendor 0x10a5 idProduct 0xd805 bcdDevice 0.51 iManufacturer 1 FPC iProduct 2 FPC L:0002 FW:2127051 iSerial 0 bNumConfigurations 1 Configuration Descriptor: bLength 9 bDescriptorType 2 wTotalLength 0x0019 bNumInterfaces 1 bConfigurationValue 1 iConfiguration 4 bmAttributes 0xa0 (Bus Powered) Remote Wakeup MaxPower 100mA Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber 0 bAlternateSetting 0 bNumEndpoints 1 bInterfaceClass 255 Vendor Specific Class bInterfaceSubClass 255 Vendor Specific Subclass bInterfaceProtocol 255 Vendor Specific Protocol iInterface 5 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x81 EP 1 IN bmAttributes 2 Transfer Type Bulk Synch Type None Usage Type Data wMaxPacketSize 0x0040 1x 64 bytes bInterval 0 [Steps to reproduce] Boot up the system, try to use the finger print related function. [Expected result] The FPR should work [Actual result] The FPR doesn't work [Failure rate] 100% [Additional information] Ubuntu: 22.04 kernel-version: 6.5.0-1014-oem To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/2054538/+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 2037604] Re: Backport packages for 22.04.4 HWE stack
** Tags added: originate-from-2046930 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/2037604 Title: Backport packages for 22.04.4 HWE stack Status in directx-headers package in Ubuntu: Invalid Status in mesa package in Ubuntu: Invalid Status in rust-bindgen package in Ubuntu: Invalid Status in rust-clang-sys package in Ubuntu: Invalid Status in directx-headers source package in Jammy: Fix Committed Status in mesa source package in Jammy: Fix Committed Status in rust-bindgen source package in Jammy: Invalid Status in rust-clang-sys source package in Jammy: Invalid Bug description: [Impact] The graphics HWE stack from mantic needs to be backported for 22.04.4 directx-headers - build-dep of the new Mesa mesa - new major release (23.2.x) - new HW support, Meteor Lake.. [Test case] We want to cover at least 2-3 different, widely used and already previously supported GPU generations from both AMD and Intel which are supported by this release, as those are the ones that cover most bases; nouveau users tend to switch to the NVIDIA blob after installation. No need to test ancient GPU's supported by mesa-amber. And best to focus on the newer generations (~5y and newer) as the older ones are less likely to break at this point. - AMD: Vega, Navi1x (RX5000*), Navi2x (RX6000*), Navi3x (RX7000*) - Intel: gen9 (SKL/APL/KBL/CFL/WHL/CML), gen11 (ICL), gen12 (TGL/RKL/RPL/DG2) Install the new packages and run some tests: - check that the desktop is still using hw acceleration and hasn't fallen back to swrast/llvmpipe - run freely available benchmarks that torture the GPU (Unigine Heaven/Valley/Superposition) - run some games from Steam if possible and in each case check that there is no gfx corruption happening or worse. Note that upstream releases have already been tested for OpenGL and Vulkan conformance by their CI. [Where things could go wrong] This is a major update of Mesa, there could be regressions but we'll try to catch any with testing. And since it shares bugs with mantic, we'd already know if there are serious issues. We will backport the final 23.2.x at a later stage, the first backport is needed for enabling Intel Meteor Lake. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/directx-headers/+bug/2037604/+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 2037604] Re: Backport packages for 22.04.4 HWE stack
After enabled the proposed, updated the mesa packages, it works perfectly on ThinkPad MTL platforms. Thanks! Before: $ /usr/lib/nux/unity_support_test -p OpenGL vendor string: Mesa OpenGL renderer string: llvmpipe (LLVM 15.0.7, 256 bits) OpenGL version string: 4.5 (Compatibility Profile) Mesa 23.0.4-0ubuntu1~22.04.1 After: $ /usr/lib/nux/unity_support_test -p OpenGL vendor string: Intel OpenGL renderer string: Mesa Intel(R) Graphics (MTL) OpenGL version string: 4.6 (Compatibility Profile) Mesa 23.2.1-1ubuntu3.1~22.04.1 ** Tags added: originate-from-2046909 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/2037604 Title: Backport packages for 22.04.4 HWE stack Status in directx-headers package in Ubuntu: Invalid Status in mesa package in Ubuntu: Invalid Status in rust-bindgen package in Ubuntu: Invalid Status in rust-clang-sys package in Ubuntu: Invalid Status in directx-headers source package in Jammy: Fix Committed Status in mesa source package in Jammy: Fix Committed Status in rust-bindgen source package in Jammy: Invalid Status in rust-clang-sys source package in Jammy: Invalid Bug description: [Impact] The graphics HWE stack from mantic needs to be backported for 22.04.4 directx-headers - build-dep of the new Mesa mesa - new major release (23.2.x) - new HW support, Meteor Lake.. [Test case] We want to cover at least 2-3 different, widely used and already previously supported GPU generations from both AMD and Intel which are supported by this release, as those are the ones that cover most bases; nouveau users tend to switch to the NVIDIA blob after installation. No need to test ancient GPU's supported by mesa-amber. And best to focus on the newer generations (~5y and newer) as the older ones are less likely to break at this point. - AMD: Vega, Navi1x (RX5000*), Navi2x (RX6000*), Navi3x (RX7000*) - Intel: gen9 (SKL/APL/KBL/CFL/WHL/CML), gen11 (ICL), gen12 (TGL/RKL/RPL/DG2) Install the new packages and run some tests: - check that the desktop is still using hw acceleration and hasn't fallen back to swrast/llvmpipe - run freely available benchmarks that torture the GPU (Unigine Heaven/Valley/Superposition) - run some games from Steam if possible and in each case check that there is no gfx corruption happening or worse. Note that upstream releases have already been tested for OpenGL and Vulkan conformance by their CI. [Where things could go wrong] This is a major update of Mesa, there could be regressions but we'll try to catch any with testing. And since it shares bugs with mantic, we'd already know if there are serious issues. We will backport the final 23.2.x at a later stage, the first backport is needed for enabling Intel Meteor Lake. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/directx-headers/+bug/2037604/+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 2042421] Re: When turn on/off "Fractional Scaling", desktop display size is smaller than screen size
** Also affects: mutter (Ubuntu) Importance: Undecided Status: New -- 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/2042421 Title: When turn on/off "Fractional Scaling", desktop display size is smaller than screen size Status in OEM Priority Project: Confirmed Status in gnome-control-center package in Ubuntu: New Status in mutter package in Ubuntu: New Bug description: Produce step: 1. Install 22.04 or 23.10 image 2. enter the systeam open display Settings 3. turn on "Fractional Scaling" and set Scale 125% and click aply 4. turn off "Fractional Scaling" and click aply [Expected result] display normal. [Actual result] display abnormal Fail rate: 100% More info: 1. Cannot be reproduced on X11, it only happens on Xwayland. 2. It will be normal after shut down or log out To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/2042421/+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 2042421] Re: When turn on/off "Fractional Scaling", desktop display size is smaller than screen size
** Changed in: oem-priority Status: New => Confirmed -- 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/2042421 Title: When turn on/off "Fractional Scaling", desktop display size is smaller than screen size Status in OEM Priority Project: Confirmed Status in gnome-control-center package in Ubuntu: New Bug description: Produce step: 1. Install 22.04 or 23.10 image 2. enter the systeam open display Settings 3. turn on "Fractional Scaling" and set Scale 125% and click aply 4. turn off "Fractional Scaling" and click aply [Expected result] display normal. [Actual result] display abnormal Fail rate: 100% More info: 1. Cannot be reproduced on X11, it only happens on Xwayland. 2. It will be normal after shut down or log out To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/2042421/+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 2042421] Re: When turn on/off "Fractional Scaling", desktop display size is smaller than screen size
Here is the video to reproduce this issue. ** Attachment added: "scale_125.mp4" https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2042421/+attachment/5714924/+files/scale_125.mp4 -- 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/2042421 Title: When turn on/off "Fractional Scaling", desktop display size is smaller than screen size Status in OEM Priority Project: New Status in gnome-control-center package in Ubuntu: New Bug description: Produce step: 1. Install 22.04 or 23.10 image 2. enter the systeam open display Settings 3. turn on "Fractional Scaling" and set Scale 125% and click aply 4. turn off "Fractional Scaling" and click aply [Expected result] display normal. [Actual result] display abnormal Fail rate: 100% More info: 1. Cannot be reproduced on X11, it only happens on Xwayland. 2. It will be normal after shut down or log out To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/2042421/+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 2042421] Re: When turn on/off "Fractional Scaling", desktop display size is smaller than screen size
** Changed in: oem-priority Assignee: (unassigned) => Bin Li (binli) ** Changed in: oem-priority Importance: Undecided => High ** Attachment added: "screen_size.jpg" https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2042421/+attachment/5714923/+files/screen_size.jpg -- 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/2042421 Title: When turn on/off "Fractional Scaling", desktop display size is smaller than screen size Status in OEM Priority Project: New Status in gnome-control-center package in Ubuntu: New Bug description: Produce step: 1. Install 22.04 or 23.10 image 2. enter the systeam open display Settings 3. turn on "Fractional Scaling" and set Scale 125% and click aply 4. turn off "Fractional Scaling" and click aply [Expected result] display normal. [Actual result] display abnormal Fail rate: 100% More info: 1. Cannot be reproduced on X11, it only happens on Xwayland. 2. It will be normal after shut down or log out To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/2042421/+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 2042421] [NEW] When turn on/off "Fractional Scaling", desktop display size is smaller than screen size
Public bug reported: Produce step: 1. Install 22.04 or 23.10 image 2. enter the systeam open display Settings 3. turn on "Fractional Scaling" and set Scale 125% and click aply 4. turn off "Fractional Scaling" and click aply [Expected result] display normal. [Actual result] display abnormal Fail rate: 100% More info: 1. Cannot be reproduced on X11, it only happens on Xwayland. 2. It will be normal after shut down or log out ** Affects: oem-priority Importance: High Assignee: Bin Li (binli) Status: New ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New ** Tags: oem-priority originate-from-2039756 sutton ** Tags added: oem-priority originate-from-2039756 sutton -- 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/2042421 Title: When turn on/off "Fractional Scaling", desktop display size is smaller than screen size Status in OEM Priority Project: New Status in gnome-control-center package in Ubuntu: New Bug description: Produce step: 1. Install 22.04 or 23.10 image 2. enter the systeam open display Settings 3. turn on "Fractional Scaling" and set Scale 125% and click aply 4. turn off "Fractional Scaling" and click aply [Expected result] display normal. [Actual result] display abnormal Fail rate: 100% More info: 1. Cannot be reproduced on X11, it only happens on Xwayland. 2. It will be normal after shut down or log out To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/2042421/+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 2042394] [NEW] Support goodix fingerprint [27c6:6582]
Public bug reported: [27c6:6582] include in https://gitlab.freedesktop.org/libfprint/libfprint/-/merge_requests/447 [Impact] * Support goodix [27c6:6582] fingerprint component. [Test Plan] * Find a machine with this fingerprint device * Launch `settings` and enable `Fingerprint Login` * Enroll finger and then logout * Login system with enrolled finger [Where problems could occur] * The patch add new ids to id_table. Should not affect previous supported device. ** Affects: libfprint (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libfprint in Ubuntu. https://bugs.launchpad.net/bugs/2042394 Title: Support goodix fingerprint [27c6:6582] Status in libfprint package in Ubuntu: New Bug description: [27c6:6582] include in https://gitlab.freedesktop.org/libfprint/libfprint/-/merge_requests/447 [Impact] * Support goodix [27c6:6582] fingerprint component. [Test Plan] * Find a machine with this fingerprint device * Launch `settings` and enable `Fingerprint Login` * Enroll finger and then logout * Login system with enrolled finger [Where problems could occur] * The patch add new ids to id_table. Should not affect previous supported device. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libfprint/+bug/2042394/+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 2033590] Re: random crashes of gnome-characters
The "MEMORY-ERROR" message appears in ~/.xsession-errors rather than syslog for me, but it's also the same random crashing of gnome- characters that causes the application to suddenly exit; relevant lines in ~/.xsession-errors: Gjs-Message: 17:38:44.610: JS LOG: Characters Application started Gjs-Message: 17:38:44.782: JS LOG: Characters Application activated Gjs-Message: 17:38:54.534: JS LOG: Failed to search: search step already started Gjs-Message: 17:38:55.994: JS LOG: Failed to search: search step already started Gjs-Message: 17:38:57.856: JS LOG: Failed to search: search step already started Gjs-Message: 17:38:58.958: JS LOG: Failed to search: search step already started ***MEMORY-ERROR***: org.gnome.Characters[4302]: GSlice: assertion failed: sinfo->n_allocated > 0 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-characters in Ubuntu. https://bugs.launchpad.net/bugs/2033590 Title: random crashes of gnome-characters Status in gnome-characters package in Ubuntu: Confirmed Bug description: Usually just a one-line record in syslog: Aug 30 19:10:45 COLOSSUS org.gnome.Characters[11012]: ***MEMORY- ERROR***: org.gnome.Characters[11012]: GSlice: assertion failed: sinfo->n_allocated > 0 Aug 30 19:12:38 COLOSSUS org.gnome.Characters[11134]: ***MEMORY- ERROR***: org.gnome.Characters[11134]: GSlice: assertion failed: sinfo->n_allocated > 0 Aug 30 19:17:29 COLOSSUS kernel: [ 2840.611031] pool- org.gnome.[11513]: segfault at 1c8 ip 7fd1854d1ae3 sp 7fd1794ca9d8 error 6 in libglib-2.0.so.0.7200.4[7fd18547a000+8f000] Aug 30 22:44:26 COLOSSUS kernel: [15257.581416] gnome- character[18769]: segfault at 18 ip 7fb24db9eae3 sp 7ffc99c29ca8 error 6 in libglib-2.0.so.0.7200.4[7fb24db47000+8f000] ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-characters 41.0-4 ProcVersionSignature: Ubuntu 5.15.0-82.91-generic 5.15.111 Uname: Linux 5.15.0-82-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: GNOME Date: Wed Aug 30 22:52:57 2023 InstallationDate: Installed on 2020-05-03 (1215 days ago) InstallationMedia: Xubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: gnome-characters UpgradeStatus: Upgraded to jammy on 2022-07-15 (412 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-characters/+bug/2033590/+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 2039235] [NEW] gnome-online-accounts -> when signing into google account, infinite loading after entering password
Public bug reported: 1) What you expected to happen - sign in is successful, which will allow google services to populate the appropriate applications (calendar, mail, google drive) 2) What actually happened - sign in hangs infinitely after entering the password - the process is able to detect that the password is correct or incorrect. When entering an incorrect password, it will correctly and quickly complain that the password is incorrect. When entering the correct password, the bug will occur. 3) Steps to reproduce a) start the program b) select online accounts c) select google d) enter email e) enter password f) loads forever ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: gnome-online-accounts 3.48.0-2 ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3 Uname: Linux 6.5.0-9-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.27.0-0ubuntu5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Oct 12 22:27:59 2023 InstallationDate: Installed on 2023-10-12 (0 days ago) InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Release amd64 (20231011) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: gnome-online-accounts UpgradeStatus: No upgrade log present (probably fresh install) Hardware info (not sure if relevant): cpu: intel gpu: nvidia (driver version: "Using NVIDIA driver metapackage from nvidia-driver-535(proprietary, tested)") ** Affects: gnome-online-accounts (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug mantic ** Description changed: 1) What you expected to happen - sign in is successful, which will allow google services to populate the appropriate applications (calendar, mail, google drive) 2) What actually happened - sign in hangs infinitely after entering the password - the process is able to detect that the password is correct or incorrect. When entering an incorrect password, it will correctly and quickly complain that the password is incorrect. When entering the correct password, the bug will occur. 3) Steps to reproduce - a) start the program - b) select online accounts - c) select google - d) enter email - e) enter password - f) loads forever + a) start the program + b) select online accounts + c) select google + d) enter email + e) enter password + f) loads forever ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: gnome-online-accounts 3.48.0-2 ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3 Uname: Linux 6.5.0-9-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.27.0-0ubuntu5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Oct 12 22:27:59 2023 InstallationDate: Installed on 2023-10-12 (0 days ago) InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Release amd64 (20231011) ProcEnviron: - LANG=en_US.UTF-8 - PATH=(custom, no user) - SHELL=/bin/bash - TERM=xterm-256color - XDG_RUNTIME_DIR= + LANG=en_US.UTF-8 + PATH=(custom, no user) + SHELL=/bin/bash + TERM=xterm-256color + XDG_RUNTIME_DIR= SourcePackage: gnome-online-accounts UpgradeStatus: No upgrade log present (probably fresh install) + + Hardware info (not sure if relevant): + cpu: intel + gpu: nvidia (driver version: "Using NVIDIA driver metapackage from nvidia-driver-535(proprietary, tested)") -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-online-accounts in Ubuntu. https://bugs.launchpad.net/bugs/2039235 Title: gnome-online-accounts -> when signing into google account, infinite loading after entering password Status in gnome-online-accounts package in Ubuntu: New Bug description: 1) What you expected to happen - sign in is successful, which will allow google services to populate the appropriate applications (calendar, mail, google drive) 2) What actually happened - sign in hangs infinitely after entering the password - the process is able to detect that the password is correct or incorrect. When entering an incorrect password, it will correctly and quickly complain that the password is incorrect. When entering the correct password, the bug will occur. 3) Steps to reproduce a) start the program b) select online accounts c) select google d) enter email e) enter password f) loads forever ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: gnome-online-accounts 3.48.0-2 ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3 Uname: Linux 6.5.0-9-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.27.0-0ubuntu5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Oct 12 22:27:59 2023 InstallationDate: Installed on 2023-10-12 (0 days ago) InstallationMedia: Ubuntu 23.10 "Mantic
[Desktop-packages] [Bug 2011770] Re: [gsd-rfkill] WwanEnabled never get synced
@seb128, Could you help review it or have someone help it? This issue will block our OEM schedule on 31th Mar. Thanks for your time. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/2011770 Title: [gsd-rfkill] WwanEnabled never get synced Status in OEM Priority Project: Triaged Status in gnome-settings-daemon package in Ubuntu: Confirmed Bug description: [ Impact ] * Sometimes on devices with WWAN card, whenever user presses the wireless function key (Fn+F8) or turn on the airplane mode radio button in Settings, the airplane mode will not be enabled, and the airplane mode icon is not shown in the status bar. * There is a unmerged upstream merge request that delivers the fix: https://gitlab.gnome.org/GNOME/gnome-settings- daemon/-/merge_requests/310 It works perfectly well on several Lenovo laptops with WWAN cards. The root causes is that the value of "WwanEnabled" under "org.freedesktop.NetworkManager" is not synced correctly, gsd-rfkill should listen to "g-properties-changed" instead of "g-signal" now. [ Test Plan ] 1. Find a machine which has WWAN card. 2. Boot the machine, and run rfkill list to see if WWAN is unblocked. if not use rfkill to unblock the WWAN, and reboot. 3. Press the wireless media key (Fn+F8) or turn on the airplane mode radio button in Settings. 4. The airplane mode should be enabled, but actually not. [ Where problems could occur ] * When user is using a very low version network-manager that still broadcasting DBUS "PropertiesChanged" events on "g-signal" instead of the concurrent "g-properties-changed", the airplane mode will sometimes not be able to enable. [ Other Info ] 1. About Ubuntu Description:Ubuntu 22.04.2 LTS Release:22.04 Kernel: 6.1.0-1007-oem 2. The version of packages: gnome-settings-daemon: Installed: 42.1-1ubuntu2.1 network-manager: Installed: 1.36.6-0ubuntu2 3. Expect: The function nm_signal(plugins/rfkill/gsd-rfkill-manager.c) is called, and manager->wwan_enabled is set to the correct value. 4. Actual: The function nm_signal(plugins/rfkill/gsd-rfkill-manager.c) is never called, so manager->wwan_enabled is not synced, If machine has WWAN device(s), and the initial value of manager->wwan_enabled is true, it will never be able to switch to airplane mode. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/2011770/+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 2011770] Re: [gsd-rfkill] WwanEnabled never get synced
On Lunar(23.04), I could reproduce this issue too. With upstream's patch, this issue is fixed on ThinkPad T14s. gnome-settings-daemon 44~rc-1ubuntu1 network-manager 1.40.12-1ubuntu1 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/2011770 Title: [gsd-rfkill] WwanEnabled never get synced Status in OEM Priority Project: Triaged Status in gnome-settings-daemon package in Ubuntu: Confirmed Bug description: The value of "WwanEnabled" under "org.freedesktop.NetworkManager" is not synced correctly, which will lead to a airplane mode switching failure when host has WWAN device(s). There is a MR on the upstream project, which can solve this bug. https://gitlab.gnome.org/GNOME/gnome-settings-daemon/-/merge_requests/310 The description copied from the MR: g-signal is not fired on property changes, so nm_signal is never called, and all changes of NetworkManager's WwanEnabled property are missed. That leads to an inability to disable the airplane mode on laptops with WWAN after the airplane mode was once enabled by button. Fix this by subscribing to g-properties-changed to actually listen to the updates of WwanEnabled. It also makes the code simpler. == 1. About Ubuntu Description:Ubuntu 22.04.2 LTS Release:22.04 2. The version of packages: gnome-settings-daemon: Installed: 42.1-1ubuntu2.1 network-manager: Installed: 1.36.6-0ubuntu2 3. Expect: The function nm_signal(plugins/rfkill/gsd-rfkill-manager.c) is called, and manager->wwan_enabled is set to the correct value. 4. Actual: The function nm_signal(plugins/rfkill/gsd-rfkill-manager.c) is never called, so manager->wwan_enabled is not synced, If machine has WWAN device(s), and the initial value of manager->wwan_enabled is true, it will never be able to switch to airplane mode. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/2011770/+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 1985057] Re: Camera output freeze when using pipewiresrc
The below two patches in Description could cause the screencast regression, so they were reverted, if we want add them again we need two gstreamer's patches in comment #51. * d/p/0001-buffers-ensure-buffer-size-does-not-exceed-maxsize.patch d/p/0002-gst-dequeue-a-shared-buffer-instead-of-original-pool.patch - Camera output freeze when using pipewiresrc (LP: #1985057) I also added another pipewire patch, d/p/0003-gst-copy-buffer-memory-in- dequeue_buffer-using-gst_m.patch from comment #51 . ** Also affects: gst-plugins-base1.0 (Ubuntu) Importance: Undecided Status: New ** Also affects: gstreamer1.0 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gst-plugins-base1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1985057 Title: Camera output freeze when using pipewiresrc Status in OEM Priority Project: New Status in gst-plugins-base1.0 package in Ubuntu: New Status in gstreamer1.0 package in Ubuntu: New Status in pipewire package in Ubuntu: Fix Released Status in gst-plugins-base1.0 source package in Jammy: New Status in gstreamer1.0 source package in Jammy: New Status in pipewire source package in Jammy: Triaged Bug description: [Impact] On Dell platform with Microdia Integrated webcam, the Cheese preview is stuck on jammy. The gst-launch-1.0 command suggested by gst-device-monitor-1.0 can reproduce it too. [Test Plan] 1. Install Jammy on the hardware issue reported, and hardware didn't report the issue to avoid the regression hardware list: a. 0bda:58ff Realtek Semiconductor Corp. Integrated_Webcam_HD b. 0c45:6747 Microdia Integrated_Webcam_HD c. 0c45:6a14 Microdia Integrated_Webcam_HD d. 1bcf:28d0 Sunplus Innovation Technology Inc. Integrated_Webcam_5M e. 04f2:b76b Chicony Electronics Co., Ltd HP HD Camera f. 0408:545a Quanta Computer, Inc. HP 5MP Camera g. 0408:5483 Quanta Computer, Inc. HP HD Camera h. 174f:2459 Syntek Integrated Camera (ThinkBook 14 Gen 4) i. 5986:116d Acer, Inc Integrated Camera (ThinkCentre Neo 50a) j. 0bda:5556 Realtek Semiconductor Corp. Integrated_Webcam_FHD 2. try to install the updated pipewire packages (= 0.3.48-1ubuntu2) 3. $ sudo reboot 4. Check if gst-launch-1.0 work a. $ gst-device-monitor-1.0 Video/Source to get caps and suggest gst-launch-1.0 command b. $ gst-launch-1.0 pipewiresrc path= ! ! decodebin ! videoconvert ! glimagesink c. Check if the result ok 5. Check the screencast function by pressing 'prt sc' a. the screenshot of all screen/selected region should work good b. the screenrecord of all screen/selected region should work good 6. Check that video recording in gnome-shell works - use Ctrl+Shift+Alt+R to start a recording, stop it from the indicator, verify that there is a new entry in ~/Video 7. Check that screen sharing is working - go to settings, screen sharing and enable the feature - try to connect using rdp/vnc from another client do those steps under wayland and unset X [Where problems could occur] The patches try to dequeue the shared buffer, instead of pool buffer to prevent the pool buffer being corrupted. it might cause some camera preview failed if shared buffer is corrupted. It is in upstream from 0.3.52 to 0.3.56, and there is no regression found, so the risk is low. [Other Info] Upstream commits: https://gitlab.freedesktop.org/pipewire/pipewire/-/commit/7cc509b117a6db66c395fb56ac4f17fb8cbd0c92 https://gitlab.freedesktop.org/pipewire/pipewire/-/commit/a1f33a99df5756c3dedd68f5ba2690819098d14f To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1985057/+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 1987631] Re: Screencast only records one second
For comment #38, currently it sounds good, if we upgrade the gstreamer
to 1.20.4, we need backport below patch.
commit d7b443197bcc0789305d6a8722bca1fdd182070b
Author: Sebastian Keller
Date: Thu Oct 6 00:20:16 2022 +0200
screencast: Don't force buffer copies on recent gstreamer versions
Gstreamer 1.20.4 includes a fix in the videoconvert element that makes
it no longer necessary to always copy buffers in pipewiresrc to have
smooth recordings. This change now skips those otherwise unnecessary
copies when using a new enough videoconvert.
Related:
https://gitlab.freedesktop.org/gstreamer/gstreamer/-/merge_requests/2928
Part-of: <https://gitlab.gnome.org/GNOME/gnome-shell/-/merge_requests/2503>
diff --git a/js/dbusServices/screencast/screencastService.js
b/js/dbusServices/screencast/screencastService.js
index 5ff5aff52..bb5387428 100644
--- a/js/dbusServices/screencast/screencastService.js
+++ b/js/dbusServices/screencast/screencastService.js
@@ -231,7 +231,8 @@ var Recorder = class {
_ensurePipeline(nodeId) {
const framerate = this._framerate;
const needsCopy =
-Gst.Registry.get().check_feature_version('pipewiresrc', 0, 3, 57);
+Gst.Registry.get().check_feature_version('pipewiresrc', 0, 3, 57)
&&
+!Gst.Registry.get().check_feature_version('videoconvert', 1, 20,
4);
** Changed in: oem-priority
Status: In Progress => Fix Released
** Changed in: oem-priority
Assignee: Bin Li (binli) => (unassigned)
** No longer affects: gst-plugins-base1.0 (Ubuntu)
** No longer affects: gst-plugins-base1.0 (Ubuntu Jammy)
** No longer affects: gstreamer1.0 (Ubuntu Jammy)
** No longer affects: gstreamer1.0 (Ubuntu)
** Changed in: pipewire (Ubuntu Jammy)
Assignee: Bin Li (binli) => (unassigned)
** Changed in: pipewire (Ubuntu Jammy)
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gst-plugins-base1.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1987631
Title:
Screencast only records one second
Status in GNOME Shell:
Fix Released
Status in OEM Priority Project:
Fix Released
Status in gnome-shell package in Ubuntu:
Fix Released
Status in pipewire package in Ubuntu:
Fix Released
Status in gnome-shell source package in Jammy:
Fix Released
Status in pipewire source package in Jammy:
Fix Released
Bug description:
[Impact]
When recording a screencast with gnome on kinetic the resulting video will
play for one second and then freeze. It looks like the same bug was discussed
upstream at https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/5585
This issue is caused by the new two patches in 0.3.48-1ubuntu2 which is fixed
the Cheese preview stuck issue on jammy
* d/p/0001-buffers-ensure-buffer-size-does-not-exceed-maxsize.patch
d/p/0002-gst-dequeue-a-shared-buffer-instead-of-original-pool.patch
- Camera output freeze when using pipewiresrc (LP: #1985057)
Here is a comment from
https://bugs.launchpad.net/ubuntu/+source/pipewire/+bug/1985057/comments/51 .
===
So that's a regression of one of the cherrypicked commits, details are in
https://gitlab.gnome.org/GNOME/gnome-shell/-/commit/d32c03488
the issue is fixed in Kinetic through a combination of the shell fix
and a new pipewire.
In 22.04 the shell issue is fixed in the recent 42.5 update but we will need
to cherrypick
https://gitlab.freedesktop.org/pipewire/pipewire/-/commit/1ea1d525 in pipewire
to be working.
===
[Test Plan]
1. Install Jammy on the hardware issue reported, and hardware didn't report
the issue to avoid the regression
hardware list:
a. 0bda:58ff Realtek Semiconductor Corp. Integrated_Webcam_HD
b. 0c45:6747 Microdia Integrated_Webcam_HD
c. 0c45:6a14 Microdia Integrated_Webcam_HD
d. 1bcf:28d0 Sunplus Innovation Technology Inc. Integrated_Webcam_5M
e. 04f2:b76b Chicony Electronics Co., Ltd HP HD Camera
f. 0408:545a Quanta Computer, Inc. HP 5MP Camera
g. 0408:5483 Quanta Computer, Inc. HP HD Camera
h. 174f:2459 Syntek Integrated Camera (ThinkBook 14 Gen 4)
i. 5986:116d Acer, Inc Integrated Camera (ThinkCentre Neo 50a)
j. 0bda:5556 Realtek Semiconductor Corp. Integrated_Webcam_FHD
2. try to install the updated pipewire packages (= 0.3.48-1ubuntu2)
3. $ sudo reboot
4. Check if gst-launch-1.0 work
a. $ gst-device-monitor-1.0 Video/Source to get caps and suggest
gst-launch-1.0 command
b. $ gst-launch-1.0 pipewiresrc path= ! ! decodebin !
videoconvert ! glimagesink
c. Check if the result ok
5. Check the screencast function by pressing 'prt sc'
a. the screenshot of all screen/selected region should work good
b. the screenrecord of all screen/selected region should work good
6. Check that video recording in gnome-shell works
- use Ctrl+Shift+Alt+R to start
[Desktop-packages] [Bug 1987631] Re: Screencast only records one second
@seb128, I went through this issue again. On 22.04.2, it works fine. With pipewire 0.3.48-1ubuntu3, because it revert the patches for Bug #1985057 , so currently we don't need to do SRU for this issue. To make this issue clear, let's focus on the SRU process on Bug #1985057. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gst-plugins-base1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1987631 Title: Screencast only records one second Status in GNOME Shell: Fix Released Status in OEM Priority Project: In Progress Status in gnome-shell package in Ubuntu: Fix Released Status in gst-plugins-base1.0 package in Ubuntu: Fix Released Status in gstreamer1.0 package in Ubuntu: Fix Released Status in pipewire package in Ubuntu: Fix Released Status in gnome-shell source package in Jammy: Fix Released Status in gst-plugins-base1.0 source package in Jammy: In Progress Status in gstreamer1.0 source package in Jammy: In Progress Status in pipewire source package in Jammy: In Progress Bug description: [Impact] When recording a screencast with gnome on kinetic the resulting video will play for one second and then freeze. It looks like the same bug was discussed upstream at https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/5585 This issue is caused by the new two patches in 0.3.48-1ubuntu2 which is fixed the Cheese preview stuck issue on jammy * d/p/0001-buffers-ensure-buffer-size-does-not-exceed-maxsize.patch d/p/0002-gst-dequeue-a-shared-buffer-instead-of-original-pool.patch - Camera output freeze when using pipewiresrc (LP: #1985057) Here is a comment from https://bugs.launchpad.net/ubuntu/+source/pipewire/+bug/1985057/comments/51 . === So that's a regression of one of the cherrypicked commits, details are in https://gitlab.gnome.org/GNOME/gnome-shell/-/commit/d32c03488 the issue is fixed in Kinetic through a combination of the shell fix and a new pipewire. In 22.04 the shell issue is fixed in the recent 42.5 update but we will need to cherrypick https://gitlab.freedesktop.org/pipewire/pipewire/-/commit/1ea1d525 in pipewire to be working. === [Test Plan] 1. Install Jammy on the hardware issue reported, and hardware didn't report the issue to avoid the regression hardware list: a. 0bda:58ff Realtek Semiconductor Corp. Integrated_Webcam_HD b. 0c45:6747 Microdia Integrated_Webcam_HD c. 0c45:6a14 Microdia Integrated_Webcam_HD d. 1bcf:28d0 Sunplus Innovation Technology Inc. Integrated_Webcam_5M e. 04f2:b76b Chicony Electronics Co., Ltd HP HD Camera f. 0408:545a Quanta Computer, Inc. HP 5MP Camera g. 0408:5483 Quanta Computer, Inc. HP HD Camera h. 174f:2459 Syntek Integrated Camera (ThinkBook 14 Gen 4) i. 5986:116d Acer, Inc Integrated Camera (ThinkCentre Neo 50a) j. 0bda:5556 Realtek Semiconductor Corp. Integrated_Webcam_FHD 2. try to install the updated pipewire packages (= 0.3.48-1ubuntu2) 3. $ sudo reboot 4. Check if gst-launch-1.0 work a. $ gst-device-monitor-1.0 Video/Source to get caps and suggest gst-launch-1.0 command b. $ gst-launch-1.0 pipewiresrc path= ! ! decodebin ! videoconvert ! glimagesink c. Check if the result ok 5. Check the screencast function by pressing 'prt sc' a. the screenshot of all screen/selected region should work good b. the screenrecord of all screen/selected region should work good 6. Check that video recording in gnome-shell works - use Ctrl+Shift+Alt+R to start a recording, stop it from the indicator, verify that there is a new entry in ~/Video 7. Check that screen sharing is working - go to settings, screen sharing and enable the feature - try to connect using rdp/vnc from another client do those steps under wayland and unset X [Where problems could occur] The patches try to dequeue the shared buffer, instead of pool buffer to prevent the pool buffer being corrupted. it might cause some camera preview failed if shared buffer is corrupted. It is from upstream and there is no regression found, so the risk is low. [Other Info] Upstream commits for pipewire: https://gitlab.freedesktop.org/pipewire/pipewire/-/commit/7cc509b117a6db66c395fb56ac4f17fb8cbd0c92 https://gitlab.freedesktop.org/pipewire/pipewire/-/commit/a1f33a99df5756c3dedd68f5ba2690819098d14f https://gitlab.freedesktop.org/pipewire/pipewire/-/commit/1ea1d525c1ac946a915599c6bee813e88e8cee12 Upstream commits for gstreamer: https://gitlab.freedesktop.org/gstreamer/gstreamer/-/commit/3b900e1fa4fd888012dc005fa26ae2532a89b7a7 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1987631/+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 1966635] Re: can't move file/directory by drag and drop by using touch monitor
** Tags added: originate-from-2006685 sutton -- 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/1966635 Title: can't move file/directory by drag and drop by using touch monitor Status in Mutter: New Status in OEM Priority Project: Confirmed Status in mutter package in Ubuntu: New Status in nautilus package in Ubuntu: Incomplete Bug description: Can't move file/directory by drag and drop by using a touch monitor OS: 22.04, up to date @ Mar 28, 2022. nautilus: 1:42~rc-1-ubuntu1 mode: wayland To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1966635/+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 1997532] Re: Traffic leaks from the cellular when WIFI and cellular are opned at the same time;
** Package changed: compiz-plugins-main (Ubuntu) => modemmanager (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to modemmanager in Ubuntu. https://bugs.launchpad.net/bugs/1997532 Title: Traffic leaks from the cellular when WIFI and cellular are opned at the same time; Status in modemmanager package in Ubuntu: New Bug description: 1.Environment FW Packkage=18601.5001.00.01.16.30 Enumeration Port：wwan0at0,wwan0at1,wwan0mbim0 OS: Ubuntu22.04.1 Test SIM Card: Unicom Module IMEI: 863714050025511 ModemManager：1.19.1； Libmbim:1.27.9 IOSM: 8.06.13 Kernel: 6.0 2. Test Steps 1). Open WIFI and connect available network; 2). Ping baidu.com always; 3). Send watch more /proc/net/dev to view WIFI traffic； 4). Insert SIM card; 5). Wait cellular connect successfully； 6). Send watch more /proc/net/dev to view WIFI and cellular traffic； 3. Expected Result Traffic only takes alway WIFI channel when WIFI and cellular opened at the same time. 4. Actual Result Traffic leaks from the cellular when WIFI and cellular are opned at the same time. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/1997532/+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 2007564] [NEW] Kernel livepatch option coundn't be enabled after 'Enable Ubuntu Pro'
Public bug reported: 'Kernel Livepatch' should be displayed an enabled from below bug. But the check button is in 'Disabled' status with gray color. https://bugs.launchpad.net/ubuntu/+source/software- properties/+bug/2003527 ** Affects: software-properties (Ubuntu) Importance: Undecided Status: New ** Tags: originate-from-2007068 sutton -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/2007564 Title: Kernel livepatch option coundn't be enabled after 'Enable Ubuntu Pro' Status in software-properties package in Ubuntu: New Bug description: 'Kernel Livepatch' should be displayed an enabled from below bug. But the check button is in 'Disabled' status with gray color. https://bugs.launchpad.net/ubuntu/+source/software- properties/+bug/2003527 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/2007564/+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 1987631] Re: Screencast only records one second
@seb128, The situation is a bit unclear there, the pipewire SRU got superseeded by a revert right, does that resolve the issue? -> Yes, the revert one the pipewrie(0.3.48-1ubuntu3) could resolve this issue. Or is the request still trying to address the initially problem? -> Yes, our OEM projects need the reverted SRU patchtes for Bug #1985057, so I added them back, but these patches also need change gstreamer at the same time. Which component do you request to be updated exactly? pipewire with the previous failed SRU + extra fixes and gstreamers? -> Yes, pipewire and gstreamers. Did anyone verify the impact on gnome-shell as pointed in #38? -> I could check it, reply you later. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gst-plugins-base1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1987631 Title: Screencast only records one second Status in GNOME Shell: Fix Released Status in OEM Priority Project: In Progress Status in gnome-shell package in Ubuntu: Fix Released Status in gst-plugins-base1.0 package in Ubuntu: Fix Released Status in gstreamer1.0 package in Ubuntu: Fix Released Status in pipewire package in Ubuntu: Fix Released Status in gnome-shell source package in Jammy: Fix Released Status in gst-plugins-base1.0 source package in Jammy: In Progress Status in gstreamer1.0 source package in Jammy: In Progress Status in pipewire source package in Jammy: In Progress Bug description: [Impact] When recording a screencast with gnome on kinetic the resulting video will play for one second and then freeze. It looks like the same bug was discussed upstream at https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/5585 This issue is caused by the new two patches in 0.3.48-1ubuntu2 which is fixed the Cheese preview stuck issue on jammy * d/p/0001-buffers-ensure-buffer-size-does-not-exceed-maxsize.patch d/p/0002-gst-dequeue-a-shared-buffer-instead-of-original-pool.patch - Camera output freeze when using pipewiresrc (LP: #1985057) Here is a comment from https://bugs.launchpad.net/ubuntu/+source/pipewire/+bug/1985057/comments/51 . === So that's a regression of one of the cherrypicked commits, details are in https://gitlab.gnome.org/GNOME/gnome-shell/-/commit/d32c03488 the issue is fixed in Kinetic through a combination of the shell fix and a new pipewire. In 22.04 the shell issue is fixed in the recent 42.5 update but we will need to cherrypick https://gitlab.freedesktop.org/pipewire/pipewire/-/commit/1ea1d525 in pipewire to be working. === [Test Plan] 1. Install Jammy on the hardware issue reported, and hardware didn't report the issue to avoid the regression hardware list: a. 0bda:58ff Realtek Semiconductor Corp. Integrated_Webcam_HD b. 0c45:6747 Microdia Integrated_Webcam_HD c. 0c45:6a14 Microdia Integrated_Webcam_HD d. 1bcf:28d0 Sunplus Innovation Technology Inc. Integrated_Webcam_5M e. 04f2:b76b Chicony Electronics Co., Ltd HP HD Camera f. 0408:545a Quanta Computer, Inc. HP 5MP Camera g. 0408:5483 Quanta Computer, Inc. HP HD Camera h. 174f:2459 Syntek Integrated Camera (ThinkBook 14 Gen 4) i. 5986:116d Acer, Inc Integrated Camera (ThinkCentre Neo 50a) j. 0bda:5556 Realtek Semiconductor Corp. Integrated_Webcam_FHD 2. try to install the updated pipewire packages (= 0.3.48-1ubuntu2) 3. $ sudo reboot 4. Check if gst-launch-1.0 work a. $ gst-device-monitor-1.0 Video/Source to get caps and suggest gst-launch-1.0 command b. $ gst-launch-1.0 pipewiresrc path= ! ! decodebin ! videoconvert ! glimagesink c. Check if the result ok 5. Check the screencast function by pressing 'prt sc' a. the screenshot of all screen/selected region should work good b. the screenrecord of all screen/selected region should work good 6. Check that video recording in gnome-shell works - use Ctrl+Shift+Alt+R to start a recording, stop it from the indicator, verify that there is a new entry in ~/Video 7. Check that screen sharing is working - go to settings, screen sharing and enable the feature - try to connect using rdp/vnc from another client do those steps under wayland and unset X [Where problems could occur] The patches try to dequeue the shared buffer, instead of pool buffer to prevent the pool buffer being corrupted. it might cause some camera preview failed if shared buffer is corrupted. It is from upstream and there is no regression found, so the risk is low. [Other Info] Upstream commits for pipewire: https://gitlab.freedesktop.org/pipewire/pipewire/-/commit/7cc509b117a6db66c395fb56ac4f17fb8cbd0c92 https://gitlab.freedesktop.org/pipewire/pipewire/-/commit/a1f33a99df5756c3dedd68f5ba2690819098d14f https://gitlab.freedesktop.org/pipewire/pipewire/-/commit/1ea1d525c1ac946a915599c6bee813e88e8cee12 Upstream commits for gstreamer:
[Desktop-packages] [Bug 1994027] Re: Can't move window by drag and drop by using touch screen
** Changed in: oem-priority Status: Fix Committed => Fix Released -- 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/1994027 Title: Can't move window by drag and drop by using touch screen Status in OEM Priority Project: Fix Released Status in XServer: Fix Released Status in xorg-server package in Ubuntu: Fix Released Status in xorg-server source package in Jammy: Fix Released Bug description: [Impact] Users using touch screen could not move windows with 'Drag-n-drop'. This SRU fixes the issue. [Test Plan] 1. Install the 22.04 2. Boot and login 3. Open a folder or terminal 4. Drag-n-drop the title bar of nautilus or terminal windows with finger touch 5. Drag-n-drop the title bar of nautilus or terminal windows with the Wacom Pen Expected: Both finger touch and wacom pen work normally. Actual: Wacom Pen works normally, finger touch can not move the windows. [Where problems could occur] It's a regression of upstream packages, https://gitlab.freedesktop.org/xorg/xserver/-/merge_requests/866 It reverts f682e0563f736ed2c2c612ed575e05b6e3db945e. [Version] xserver-xorg-core 2:21.1.3-2ubuntu2.2 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1994027/+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 2006586] [NEW] Ubuntu Pro: Segmentation faults when quit gnome-initial-setup
Public bug reported: Click 'Quit' from applications menu directly after the gnome-initial-setup show, then this issue will be reproduced. ubuntu: 22.04.1 gnome-initial-setup: 42.0.1-1ubuntu2.1 ** Affects: gnome-initial-setup (Ubuntu) Importance: Undecided Status: New ** Description changed: - Click 'Quit' from applications menu directly after the gnome-initial- - setup show, then this issue will be reproduced. + Click 'Quit' from applications menu directly after the gnome-initial-setup show, then this issue will be reproduced. + ubuntu: 22.04.1 + gnome-initial-setup: 42.0.1-1ubuntu2.1 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-initial-setup in Ubuntu. https://bugs.launchpad.net/bugs/2006586 Title: Ubuntu Pro: Segmentation faults when quit gnome-initial-setup Status in gnome-initial-setup package in Ubuntu: New Bug description: Click 'Quit' from applications menu directly after the gnome-initial-setup show, then this issue will be reproduced. ubuntu: 22.04.1 gnome-initial-setup: 42.0.1-1ubuntu2.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-initial-setup/+bug/2006586/+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 2000459] Re: Only shows half of menu if right-clicks mouse on the desktop if scaling screen
I reported a bug in desktop-icons-ng. https://gitlab.com/rastersoft/desktop-icons- ng/-/issues/265#note_1222933950 -- 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/2000459 Title: Only shows half of menu if right-clicks mouse on the desktop if scaling screen Status in OEM Priority Project: In Progress Status in gnome-shell-extension-desktop-icons-ng package in Ubuntu: New Status in mutter package in Ubuntu: New Bug description: [Steps] 1. Cold boot with 4K monitor 2. Open Settings -> Display (Current resolution is 3840x2160, scaling: 100%) 3. Right click, the menu is well 4. Adjust the scaling to be 200%, 300%, 400% 5. Right click, the menu is broken [Actual behavior] Issue can be observed in the following combination - 36840x2160 - scaling: 200%, 300%, 400% - 2560x1440 - scaling: 200%, 300% - 1920x1080 - scaling: 200% To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/2000459/+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 2000459] Re: Only shows half of menu if right-clicks mouse on the desktop if scaling screen
On ubuntu 22.04, I could reproduce this issue on Xorg, but it couldn't be reproduced on Xwayland. If I removed the gnome-shell-extension-desktop-icons-ng, the original right-click menu of gnome-shell works fine. I also tried latest version gnome-shell-extension-desktop-icons-ng 46+really47-1, this issue still exists. After changing the scale, kill the ding.js to relaunch it, then this issue is gone. ** Changed in: oem-priority Assignee: (unassigned) => Bin Li (binli) ** Changed in: oem-priority Importance: Undecided => Medium ** Changed in: oem-priority Status: New => In Progress ** Also affects: gnome-shell-extension-desktop-icons-ng (Ubuntu) Importance: Undecided Status: New ** Bug watch added: gitlab.com/rastersoft/desktop-icons-ng/-/issues #265 https://gitlab.com/rastersoft/desktop-icons-ng/-/issues/265 -- 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/2000459 Title: Only shows half of menu if right-clicks mouse on the desktop if scaling screen Status in OEM Priority Project: In Progress Status in gnome-shell-extension-desktop-icons-ng package in Ubuntu: New Status in mutter package in Ubuntu: New Bug description: [Steps] 1. Cold boot with 4K monitor 2. Open Settings -> Display (Current resolution is 3840x2160, scaling: 100%) 3. Right click, the menu is well 4. Adjust the scaling to be 200%, 300%, 400% 5. Right click, the menu is broken [Actual behavior] Issue can be observed in the following combination - 36840x2160 - scaling: 200%, 300%, 400% - 2560x1440 - scaling: 200%, 300% - 1920x1080 - scaling: 200% To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/2000459/+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 1987631] Re: Screencast only records one second
@mdmower, Thanks, in your comment this issue could be fixed with gstreamer's patch, so the root cause is from gstreamer. I prefer to add the pipewire's patch, cause it's also from James Hilliard, it might help avoid the potential issue without deepcopy. Could you help upgrade the new pipewire from comments #25 and check this issue again? BTW, we also need test the cheese's preview issue (lp:1985057) at the same time. https://gitlab.freedesktop.org/pipewire/pipewire/-/commit/1ea1d525c1ac946a915599c6bee813e88e8cee12 https://gitlab.freedesktop.org/gstreamer/gstreamer/-/commit/3b900e1fa4fd888012dc005fa26ae2532a89b7a7 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gst-plugins-base1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1987631 Title: Screencast only records one second Status in GNOME Shell: Fix Released Status in OEM Priority Project: In Progress Status in gnome-shell package in Ubuntu: Fix Released Status in gst-plugins-base1.0 package in Ubuntu: New Status in gstreamer1.0 package in Ubuntu: New Status in pipewire package in Ubuntu: Fix Released Status in gnome-shell source package in Jammy: Fix Released Status in gst-plugins-base1.0 source package in Jammy: New Status in gstreamer1.0 source package in Jammy: New Status in pipewire source package in Jammy: Confirmed Bug description: [Impact] When recording a screencast with gnome on kinetic the resulting video will play for one second and then freeze. It looks like the same bug was discussed upstream at https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/5585 This issue is caused by the new two patches in 0.3.48-1ubuntu2 which is fixed the Cheese preview stuck issue on jammy * d/p/0001-buffers-ensure-buffer-size-does-not-exceed-maxsize.patch d/p/0002-gst-dequeue-a-shared-buffer-instead-of-original-pool.patch - Camera output freeze when using pipewiresrc (LP: #1985057) Here is a comment from https://bugs.launchpad.net/ubuntu/+source/pipewire/+bug/1985057/comments/51 . === So that's a regression of one of the cherrypicked commits, details are in https://gitlab.gnome.org/GNOME/gnome-shell/-/commit/d32c03488 the issue is fixed in Kinetic through a combination of the shell fix and a new pipewire. In 22.04 the shell issue is fixed in the recent 42.5 update but we will need to cherrypick https://gitlab.freedesktop.org/pipewire/pipewire/-/commit/1ea1d525 in pipewire to be working. === [Test Plan] 1. Install Jammy on the hardware issue reported, and hardware didn't report the issue to avoid the regression hardware list: a. 0bda:58ff Realtek Semiconductor Corp. Integrated_Webcam_HD b. 0c45:6747 Microdia Integrated_Webcam_HD c. 0c45:6a14 Microdia Integrated_Webcam_HD d. 1bcf:28d0 Sunplus Innovation Technology Inc. Integrated_Webcam_5M e. 04f2:b76b Chicony Electronics Co., Ltd HP HD Camera f. 0408:545a Quanta Computer, Inc. HP 5MP Camera g. 0408:5483 Quanta Computer, Inc. HP HD Camera h. 174f:2459 Syntek Integrated Camera (ThinkBook 14 Gen 4) i. 5986:116d Acer, Inc Integrated Camera (ThinkCentre Neo 50a) j. 0bda:5556 Realtek Semiconductor Corp. Integrated_Webcam_FHD 2. try to install the updated pipewire packages (= 0.3.48-1ubuntu2) 3. $ sudo reboot 4. Check if gst-launch-1.0 work a. $ gst-device-monitor-1.0 Video/Source to get caps and suggest gst-launch-1.0 command b. $ gst-launch-1.0 pipewiresrc path= ! ! decodebin ! videoconvert ! glimagesink c. Check if the result ok 5. Check the screencast function by pressing 'prt sc' a. the screenshot of all screen/selected region should work good b. the screenrecord of all screen/selected region should work good 6. Check that video recording in gnome-shell works - use Ctrl+Shift+Alt+R to start a recording, stop it from the indicator, verify that there is a new entry in ~/Video 7. Check that screen sharing is working - go to settings, screen sharing and enable the feature - try to connect using rdp/vnc from another client do those steps under wayland and unset X [Where problems could occur] The patches try to dequeue the shared buffer, instead of pool buffer to prevent the pool buffer being corrupted. it might cause some camera preview failed if shared buffer is corrupted. It is from upstream and there is no regression found, so the risk is low. [Other Info] Upstream commits for pipewire: https://gitlab.freedesktop.org/pipewire/pipewire/-/commit/7cc509b117a6db66c395fb56ac4f17fb8cbd0c92 https://gitlab.freedesktop.org/pipewire/pipewire/-/commit/a1f33a99df5756c3dedd68f5ba2690819098d14f https://gitlab.freedesktop.org/pipewire/pipewire/-/commit/1ea1d525c1ac946a915599c6bee813e88e8cee12 Upstream commits for gstreamer: https://gitlab.freedesktop.org/gstreamer/gstreamer/-/commit/3b900e1fa4fd888012dc005fa26ae2532a89b7a7 To manage notifications
[Desktop-packages] [Bug 1987631] Re: Screencast only records one second
@seb128, Could you help review and sponsor the 3 debdiff when you are available? Thanks! https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1987631/comments/27 https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1987631/comments/28 https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1987631/comments/30 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gst-plugins-base1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1987631 Title: Screencast only records one second Status in GNOME Shell: Fix Released Status in OEM Priority Project: In Progress Status in gnome-shell package in Ubuntu: Fix Released Status in gst-plugins-base1.0 package in Ubuntu: New Status in gstreamer1.0 package in Ubuntu: New Status in pipewire package in Ubuntu: Fix Released Status in gnome-shell source package in Jammy: Fix Released Status in gst-plugins-base1.0 source package in Jammy: New Status in gstreamer1.0 source package in Jammy: New Status in pipewire source package in Jammy: Confirmed Bug description: [Impact] When recording a screencast with gnome on kinetic the resulting video will play for one second and then freeze. It looks like the same bug was discussed upstream at https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/5585 This issue is caused by the new two patches in 0.3.48-1ubuntu2 which is fixed the Cheese preview stuck issue on jammy * d/p/0001-buffers-ensure-buffer-size-does-not-exceed-maxsize.patch d/p/0002-gst-dequeue-a-shared-buffer-instead-of-original-pool.patch - Camera output freeze when using pipewiresrc (LP: #1985057) Here is a comment from https://bugs.launchpad.net/ubuntu/+source/pipewire/+bug/1985057/comments/51 . === So that's a regression of one of the cherrypicked commits, details are in https://gitlab.gnome.org/GNOME/gnome-shell/-/commit/d32c03488 the issue is fixed in Kinetic through a combination of the shell fix and a new pipewire. In 22.04 the shell issue is fixed in the recent 42.5 update but we will need to cherrypick https://gitlab.freedesktop.org/pipewire/pipewire/-/commit/1ea1d525 in pipewire to be working. === [Test Plan] 1. Install Jammy on the hardware issue reported, and hardware didn't report the issue to avoid the regression hardware list: a. 0bda:58ff Realtek Semiconductor Corp. Integrated_Webcam_HD b. 0c45:6747 Microdia Integrated_Webcam_HD c. 0c45:6a14 Microdia Integrated_Webcam_HD d. 1bcf:28d0 Sunplus Innovation Technology Inc. Integrated_Webcam_5M e. 04f2:b76b Chicony Electronics Co., Ltd HP HD Camera f. 0408:545a Quanta Computer, Inc. HP 5MP Camera g. 0408:5483 Quanta Computer, Inc. HP HD Camera h. 174f:2459 Syntek Integrated Camera (ThinkBook 14 Gen 4) i. 5986:116d Acer, Inc Integrated Camera (ThinkCentre Neo 50a) j. 0bda:5556 Realtek Semiconductor Corp. Integrated_Webcam_FHD 2. try to install the updated pipewire packages (= 0.3.48-1ubuntu2) 3. $ sudo reboot 4. Check if gst-launch-1.0 work a. $ gst-device-monitor-1.0 Video/Source to get caps and suggest gst-launch-1.0 command b. $ gst-launch-1.0 pipewiresrc path= ! ! decodebin ! videoconvert ! glimagesink c. Check if the result ok 5. Check the screencast function by pressing 'prt sc' a. the screenshot of all screen/selected region should work good b. the screenrecord of all screen/selected region should work good 6. Check that video recording in gnome-shell works - use Ctrl+Shift+Alt+R to start a recording, stop it from the indicator, verify that there is a new entry in ~/Video 7. Check that screen sharing is working - go to settings, screen sharing and enable the feature - try to connect using rdp/vnc from another client do those steps under wayland and unset X [Where problems could occur] The patches try to dequeue the shared buffer, instead of pool buffer to prevent the pool buffer being corrupted. it might cause some camera preview failed if shared buffer is corrupted. It is from upstream and there is no regression found, so the risk is low. [Other Info] Upstream commits for pipewire: https://gitlab.freedesktop.org/pipewire/pipewire/-/commit/7cc509b117a6db66c395fb56ac4f17fb8cbd0c92 https://gitlab.freedesktop.org/pipewire/pipewire/-/commit/a1f33a99df5756c3dedd68f5ba2690819098d14f https://gitlab.freedesktop.org/pipewire/pipewire/-/commit/1ea1d525c1ac946a915599c6bee813e88e8cee12 Upstream commits for gstreamer: https://gitlab.freedesktop.org/gstreamer/gstreamer/-/commit/3b900e1fa4fd888012dc005fa26ae2532a89b7a7 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1987631/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help :
[Desktop-packages] [Bug 1987631] Re: Screencast only records one second
** Description changed: - When recording a screencast with gnome on kinetic the resulting video - will play for one second and then freeze. It looks like the same bug was - discussed upstream at https://gitlab.gnome.org/GNOME/gnome- - shell/-/issues/5585 + [Impact] + When recording a screencast with gnome on kinetic the resulting video will play for one second and then freeze. It looks like the same bug was discussed upstream at https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/5585 + + This issue is caused by the new two patches in 0.3.48-1ubuntu2 which is fixed the Cheese preview stuck issue on jammy + * d/p/0001-buffers-ensure-buffer-size-does-not-exceed-maxsize.patch + d/p/0002-gst-dequeue-a-shared-buffer-instead-of-original-pool.patch + - Camera output freeze when using pipewiresrc (LP: #1985057) + + Here is a comment from https://bugs.launchpad.net/ubuntu/+source/pipewire/+bug/1985057/comments/51 . + === + So that's a regression of one of the cherrypicked commits, details are in https://gitlab.gnome.org/GNOME/gnome-shell/-/commit/d32c03488 + + the issue is fixed in Kinetic through a combination of the shell fix and + a new pipewire. + + In 22.04 the shell issue is fixed in the recent 42.5 update but we will need to cherrypick https://gitlab.freedesktop.org/pipewire/pipewire/-/commit/1ea1d525 in pipewire to be working. + === + + [Test Plan] + 1. Install Jammy on the hardware issue reported, and hardware didn't report the issue to avoid the regression +hardware list: +a. 0bda:58ff Realtek Semiconductor Corp. Integrated_Webcam_HD +b. 0c45:6747 Microdia Integrated_Webcam_HD +c. 0c45:6a14 Microdia Integrated_Webcam_HD +d. 1bcf:28d0 Sunplus Innovation Technology Inc. Integrated_Webcam_5M +e. 04f2:b76b Chicony Electronics Co., Ltd HP HD Camera +f. 0408:545a Quanta Computer, Inc. HP 5MP Camera +g. 0408:5483 Quanta Computer, Inc. HP HD Camera +h. 174f:2459 Syntek Integrated Camera (ThinkBook 14 Gen 4) +i. 5986:116d Acer, Inc Integrated Camera (ThinkCentre Neo 50a) +j. 0bda:5556 Realtek Semiconductor Corp. Integrated_Webcam_FHD + 2. try to install the updated pipewire packages (= 0.3.48-1ubuntu2) + 3. $ sudo reboot + 4. Check if gst-launch-1.0 work +a. $ gst-device-monitor-1.0 Video/Source to get caps and suggest gst-launch-1.0 command +b. $ gst-launch-1.0 pipewiresrc path= ! ! decodebin ! videoconvert ! glimagesink +c. Check if the result ok + 5. Check the screencast function by pressing 'prt sc' +a. the screenshot of all screen/selected region should work good +b. the screenrecord of all screen/selected region should work good + 6. Check that video recording in gnome-shell works +- use Ctrl+Shift+Alt+R to start a recording, stop it from the indicator, verify that there is a new entry in ~/Video + 7. Check that screen sharing is working +- go to settings, screen sharing and enable the feature +- try to connect using rdp/vnc from another client + + do those steps under wayland and unset X + + [Where problems could occur] + The patches try to dequeue the shared buffer, instead of pool buffer to prevent the pool buffer being corrupted. it might cause some camera preview failed if shared buffer is corrupted. + It is from upstream and there is no regression found, so the risk is low. + + [Other Info] + Upstream commits for pipewire: + https://gitlab.freedesktop.org/pipewire/pipewire/-/commit/7cc509b117a6db66c395fb56ac4f17fb8cbd0c92 + https://gitlab.freedesktop.org/pipewire/pipewire/-/commit/a1f33a99df5756c3dedd68f5ba2690819098d14f + https://gitlab.freedesktop.org/pipewire/pipewire/-/commit/1ea1d525c1ac946a915599c6bee813e88e8cee12 + Upstream commits for gstreamer: + https://gitlab.freedesktop.org/gstreamer/gstreamer/-/commit/3b900e1fa4fd888012dc005fa26ae2532a89b7a7 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gst-plugins-base1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1987631 Title: Screencast only records one second Status in GNOME Shell: Fix Released Status in OEM Priority Project: In Progress Status in gnome-shell package in Ubuntu: Fix Released Status in gst-plugins-base1.0 package in Ubuntu: New Status in gstreamer1.0 package in Ubuntu: New Status in pipewire package in Ubuntu: Fix Released Status in gnome-shell source package in Jammy: Fix Released Status in gst-plugins-base1.0 source package in Jammy: New Status in gstreamer1.0 source package in Jammy: New Status in pipewire source package in Jammy: Confirmed Bug description: [Impact] When recording a screencast with gnome on kinetic the resulting video will play for one second and then freeze. It looks like the same bug was discussed upstream at https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/5585 This issue is caused by the new two patches in 0.3.48-1ubuntu2 which is fixed the Cheese preview stuck issue on jammy *
[Desktop-packages] [Bug 1987631] Re: Screencast only records one second
** Patch added: "pipewire_0.3.48-1ubuntu4.debdiff" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1987631/+attachment/5638528/+files/pipewire_0.3.48-1ubuntu4.debdiff -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gst-plugins-base1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1987631 Title: Screencast only records one second Status in GNOME Shell: Fix Released Status in OEM Priority Project: In Progress Status in gnome-shell package in Ubuntu: Fix Released Status in gst-plugins-base1.0 package in Ubuntu: New Status in gstreamer1.0 package in Ubuntu: New Status in pipewire package in Ubuntu: Fix Released Status in gnome-shell source package in Jammy: Fix Released Status in gst-plugins-base1.0 source package in Jammy: New Status in gstreamer1.0 source package in Jammy: New Status in pipewire source package in Jammy: Confirmed Bug description: When recording a screencast with gnome on kinetic the resulting video will play for one second and then freeze. It looks like the same bug was discussed upstream at https://gitlab.gnome.org/GNOME/gnome- shell/-/issues/5585 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1987631/+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 1987631] Re: Screencast only records one second
@mdmower, What's the version of pipewire in your side? This issue is caused by new patches in 0.3.48-1ubuntu2 which is fixed lp:1985057 . * d/p/0001-buffers-ensure-buffer-size-does-not-exceed-maxsize.patch d/p/0002-gst-dequeue-a-shared-buffer-instead-of-original-pool.patch - Camera output freeze when using pipewiresrc (LP: #1985057) In proposed channel, it's 0.3.48-1ubuntu3, just revert these two patches. Now with the two gstreamer's patches, we want add these two patches back, and from https://bugs.launchpad.net/ubuntu/+source/pipewire/+bug/1985057/comments/51 I added another patch, d/p/0003-gst-copy-buffer-memory-in-dequeue_buffer-using-gst_m.patch. $ rmadison pipewire pipewire | 0.3.48-1ubuntu2 | jammy-updates | source, amd64, arm64, armhf, i386, ppc64el, riscv64, s390x pipewire | 0.3.48-1ubuntu3 | jammy-proposed | source, amd64, arm64, armhf, i386, ppc64el, riscv64, s390x -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gst-plugins-base1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1987631 Title: Screencast only records one second Status in GNOME Shell: Fix Released Status in OEM Priority Project: In Progress Status in gnome-shell package in Ubuntu: Fix Released Status in gst-plugins-base1.0 package in Ubuntu: New Status in gstreamer1.0 package in Ubuntu: New Status in pipewire package in Ubuntu: Fix Released Status in gnome-shell source package in Jammy: Fix Released Status in gst-plugins-base1.0 source package in Jammy: New Status in gstreamer1.0 source package in Jammy: New Status in pipewire source package in Jammy: Confirmed Bug description: When recording a screencast with gnome on kinetic the resulting video will play for one second and then freeze. It looks like the same bug was discussed upstream at https://gitlab.gnome.org/GNOME/gnome- shell/-/issues/5585 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1987631/+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 1987631] Re: Screencast only records one second
** Patch added: "gst-plugins-base1.0_1.20.1-2.debdiff" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1987631/+attachment/5638525/+files/gst-plugins-base1.0_1.20.1-2.debdiff -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gst-plugins-base1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1987631 Title: Screencast only records one second Status in GNOME Shell: Fix Released Status in OEM Priority Project: In Progress Status in gnome-shell package in Ubuntu: Fix Released Status in gst-plugins-base1.0 package in Ubuntu: New Status in gstreamer1.0 package in Ubuntu: New Status in pipewire package in Ubuntu: Fix Released Status in gnome-shell source package in Jammy: Fix Released Status in gst-plugins-base1.0 source package in Jammy: New Status in gstreamer1.0 source package in Jammy: New Status in pipewire source package in Jammy: Confirmed Bug description: When recording a screencast with gnome on kinetic the resulting video will play for one second and then freeze. It looks like the same bug was discussed upstream at https://gitlab.gnome.org/GNOME/gnome- shell/-/issues/5585 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1987631/+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 1987631] Re: Screencast only records one second
** Patch added: "gstreamer1.0_1.20.3-0ubuntu2.debdiff" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1987631/+attachment/5638524/+files/gstreamer1.0_1.20.3-0ubuntu2.debdiff -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gst-plugins-base1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1987631 Title: Screencast only records one second Status in GNOME Shell: Fix Released Status in OEM Priority Project: In Progress Status in gnome-shell package in Ubuntu: Fix Released Status in gst-plugins-base1.0 package in Ubuntu: New Status in gstreamer1.0 package in Ubuntu: New Status in pipewire package in Ubuntu: Fix Released Status in gnome-shell source package in Jammy: Fix Released Status in gst-plugins-base1.0 source package in Jammy: New Status in gstreamer1.0 source package in Jammy: New Status in pipewire source package in Jammy: Confirmed Bug description: When recording a screencast with gnome on kinetic the resulting video will play for one second and then freeze. It looks like the same bug was discussed upstream at https://gitlab.gnome.org/GNOME/gnome- shell/-/issues/5585 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1987631/+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 2000459] Re: Only shows half of menu if right-clicks mouse on the desktop if scaling screen
** Tags added: originate-from-1993491 -- 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/2000459 Title: Only shows half of menu if right-clicks mouse on the desktop if scaling screen Status in OEM Priority Project: New Status in mutter package in Ubuntu: New Bug description: [Steps] 1. Cold boot with 4K monitor 2. Open Settings -> Display (Current resolution is 3840x2160, scaling: 100%) 3. Right click, the menu is well 4. Adjust the scaling to be 200%, 300%, 400% 5. Right click, the menu is broken [Actual behavior] Issue can be observed in the following combination - 36840x2160 - scaling: 200%, 300%, 400% - 2560x1440 - scaling: 200%, 300% - 1920x1080 - scaling: 200% To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/2000459/+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 1977986] Re: UPower and battery indicator show update in 2 minutes when connecting power cable ThinkPad
This patch could help set the initial status correctly. commit 792fc7bb1bd4c7bf4b779106329aa4487bfa0386 Author: Benjamin Berg Date: Thu Jun 2 18:29:50 2022 +0200 supply: Consistently use 90% threshold to consider a battery full ** Patch added: "0001-supply-Consistently-use-90-threshold-to-consider-a-b.patch" https://bugs.launchpad.net/ubuntu/+source/upower/+bug/1977986/+attachment/5638073/+files/0001-supply-Consistently-use-90-threshold-to-consider-a-b.patch -- 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/1977986 Title: UPower and battery indicator show update in 2 minutes when connecting power cable ThinkPad Status in OEM Priority Project: In Progress Status in upower package in Ubuntu: New Bug description: We found this issue on several ThinkPad. The upower will change 'pending-charge' to 'charging' after 2 minutes later, but the /sys/class/power_supply/BAT0/status changes to 'Charging' immediately when connecting the power cable. $ upower -i /org/freedesktop/UPower/devices/battery_BAT0 native-path: BAT0 vendor: Sunwoda model:5B10W13975 serial: 34226 power supply: yes updated: Wed 08 Jun 2022 11:42:02 PM CST (1 seconds ago) has history: yes has statistics: yes battery present: yes rechargeable:yes state: pending-charge warning-level: none energy: 55.94 Wh energy-empty:0 Wh energy-full: 57 Wh energy-full-design: 57 Wh energy-rate: 5.79 W voltage: 16.688 V percentage: 98% capacity:100% technology: lithium-polymer icon-name: 'battery-full-charging-symbolic' History (charge): 1654702882 98.000 pending-charge 1654702863 97.000 pending-charge History (rate): 1654702863 5.790 pending-charge 1654702863 6.171 pending-charge $ cat /sys/class/power_supply/BAT0/status Charging To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1977986/+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 1987631] Re: Screencast only records one second
@mdmower, Yes, the patch for pipewire is not enough, the deep copy need another 2 packages, gstreamer1.0 and gst-plugins-base1.0. I built the deb packages in my ppa. The screencast works fine with below packages. https://launchpad.net/~binli/+archive/ubuntu/gnome/ gstreamer1.0 - 1.20.3-0ubuntu1binli2 gst-plugins-base1.0 - 1.20.1-2binli1 pipewire - 0.3.48-1ubuntu2binli1 * d/p/0003-gst-copy-buffer-memory-in-dequeue_buffer-using-gst_m.patch - Fixed Screencast only records few seconds issue (LP: #1995358) ** Also affects: gstreamer1.0 (Ubuntu) Importance: Undecided Status: New ** Also affects: gst-plugins-base1.0 (Ubuntu) Importance: Undecided Status: New -- 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/1987631 Title: Screencast only records one second Status in GNOME Shell: Fix Released Status in OEM Priority Project: In Progress Status in gnome-shell package in Ubuntu: Fix Released Status in gst-plugins-base1.0 package in Ubuntu: New Status in gstreamer1.0 package in Ubuntu: New Status in pipewire package in Ubuntu: Fix Released Status in gnome-shell source package in Jammy: Fix Released Status in gst-plugins-base1.0 source package in Jammy: New Status in gstreamer1.0 source package in Jammy: New Status in pipewire source package in Jammy: Confirmed Bug description: When recording a screencast with gnome on kinetic the resulting video will play for one second and then freeze. It looks like the same bug was discussed upstream at https://gitlab.gnome.org/GNOME/gnome- shell/-/issues/5585 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1987631/+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 1987631] Re: Screencast only records one second
It's still in proposed. Missing tags? $ rmadison pipewire pipewire | 0.3.48-1ubuntu2 | jammy-updates | source, amd64, arm64, armhf, i386, ppc64el, riscv64, s390x pipewire | 0.3.48-1ubuntu3 | jammy-proposed | source, amd64, arm64, armhf, i386, ppc64el, riscv64, s390x ** Tags added: verification-done verification-done-jammy -- 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/1987631 Title: Screencast only records one second Status in GNOME Shell: Fix Released Status in OEM Priority Project: In Progress Status in gnome-shell package in Ubuntu: Fix Released Status in pipewire package in Ubuntu: Fix Released Status in gnome-shell source package in Jammy: Fix Released Status in pipewire source package in Jammy: Confirmed Bug description: When recording a screencast with gnome on kinetic the resulting video will play for one second and then freeze. It looks like the same bug was discussed upstream at https://gitlab.gnome.org/GNOME/gnome- shell/-/issues/5585 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1987631/+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 1977986] Re: UPower and battery indicator show update in 2 minutes when connecting power cable ThinkPad
** Changed in: oem-priority Assignee: (unassigned) => Bin Li (binli) ** Changed in: oem-priority Importance: Undecided => High ** Changed in: oem-priority Status: New => In Progress -- 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/1977986 Title: UPower and battery indicator show update in 2 minutes when connecting power cable ThinkPad Status in OEM Priority Project: In Progress Status in upower package in Ubuntu: New Bug description: We found this issue on several ThinkPad. The upower will change 'pending-charge' to 'charging' after 2 minutes later, but the /sys/class/power_supply/BAT0/status changes to 'Charging' immediately when connecting the power cable. $ upower -i /org/freedesktop/UPower/devices/battery_BAT0 native-path: BAT0 vendor: Sunwoda model:5B10W13975 serial: 34226 power supply: yes updated: Wed 08 Jun 2022 11:42:02 PM CST (1 seconds ago) has history: yes has statistics: yes battery present: yes rechargeable:yes state: pending-charge warning-level: none energy: 55.94 Wh energy-empty:0 Wh energy-full: 57 Wh energy-full-design: 57 Wh energy-rate: 5.79 W voltage: 16.688 V percentage: 98% capacity:100% technology: lithium-polymer icon-name: 'battery-full-charging-symbolic' History (charge): 1654702882 98.000 pending-charge 1654702863 97.000 pending-charge History (rate): 1654702863 5.790 pending-charge 1654702863 6.171 pending-charge $ cat /sys/class/power_supply/BAT0/status Charging To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1977986/+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 1994027] Re: Can't move window by drag and drop by using touch screen
After upgraded to 2:21.1.3-2ubuntu2.4, I could move window by drag and drop with touch screen on ThinkPad P1 Gen 3. Thanks! Start-Date: 2022-11-28 20:27:46 Commandline: apt install xserver-xorg-core Requested-By: binli (1000) Upgrade: xserver-xorg-core:amd64 (2:21.1.3-2ubuntu2.3, 2:21.1.3-2ubuntu2.4), xserver-common:amd64 (2:21.1.3-2ubuntu2.3, 2:21.1.3-2ubuntu2.4) End-Date: 2022-11-28 20:27:48 ** Tags removed: verification-needed verification-needed-jammy ** Tags added: verification-done verification-done-jammy -- 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/1994027 Title: Can't move window by drag and drop by using touch screen Status in OEM Priority Project: Fix Committed Status in XServer: Fix Released Status in xorg-server package in Ubuntu: Fix Released Status in xorg-server source package in Jammy: Fix Committed Bug description: [Impact] Users using touch screen could not move windows with 'Drag-n-drop'. This SRU fixes the issue. [Test Plan] 1. Install the 22.04 2. Boot and login 3. Open a folder or terminal 4. Drag-n-drop the title bar of nautilus or terminal windows with finger touch 5. Drag-n-drop the title bar of nautilus or terminal windows with the Wacom Pen Expected: Both finger touch and wacom pen work normally. Actual: Wacom Pen works normally, finger touch can not move the windows. [Where problems could occur] It's a regression of upstream packages, https://gitlab.freedesktop.org/xorg/xserver/-/merge_requests/866 It reverts f682e0563f736ed2c2c612ed575e05b6e3db945e. [Version] xserver-xorg-core 2:21.1.3-2ubuntu2.2 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1994027/+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 1994027] Re: Can't move window by drag and drop by using touch screen
Our OEM project would like this to be included in -proposed before this weekend(2022-11-25). -- 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/1994027 Title: Can't move window by drag and drop by using touch screen Status in OEM Priority Project: Fix Committed Status in XServer: Fix Released Status in xorg package in Ubuntu: New Bug description: [Impact] Users using touch screen could not move windows with 'Drag-n-drop'. This SRU fixes the issue. [Test Plan] 1. Install the 22.04 2. Boot and login 3. Open a folder or terminal 4. Drag-n-drop the title bar of nautilus or terminal windows with finger touch 5. Drag-n-drop the title bar of nautilus or terminal windows with the Wacom Pen Expected: Both finger touch and wacom pen work normally. Actual: Wacom Pen works normally, finger touch can not move the windows. [Where problems could occur] It's a regression of upstream packages, https://gitlab.freedesktop.org/xorg/xserver/-/merge_requests/866 It reverts f682e0563f736ed2c2c612ed575e05b6e3db945e. [Version] xserver-xorg-core 2:21.1.3-2ubuntu2.2 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1994027/+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 1994027] Re: Can't move window by drag and drop by using touch screen
Built a new packages for testing in my ppa. This issue is fixed with xserver-xorg-core 2:21.1.3-2ubuntu2.2binli1. https://launchpad.net/~binli/+archive/ubuntu/gnome/ ** Changed in: oem-priority Status: In Progress => Triaged -- 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/1994027 Title: Can't move window by drag and drop by using touch screen Status in OEM Priority Project: Triaged Status in XServer: Unknown Status in xorg package in Ubuntu: New Bug description: [Impact] Users using touch screen could not move windows with 'Drag-n-drop'. This SRU fixes the issue. [Test Plan] 1. Install the 22.04 2. Boot and login 3. Open a folder or terminal 4. Drag-n-drop the title bar of nautilus or terminal windows with finger touch 5. Drag-n-drop the title bar of nautilus or terminal windows with the Wacom Pen Expected: Both finger touch and wacom pen work normally. Actual: Wacom Pen works normally, finger touch can not move the windows. [Where problems could occur] It's a regression of upstream packages, https://gitlab.freedesktop.org/xorg/xserver/-/merge_requests/866 It reverts f682e0563f736ed2c2c612ed575e05b6e3db945e. [Version] xserver-xorg-core 2:21.1.3-2ubuntu2.2 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1994027/+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 1994027] Re: Can't move window by drag and drop by using touch screen
** Patch added: "xorg-server_21.1.3-2ubuntu2.3.debdiff" https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1994027/+attachment/5631780/+files/xorg-server_21.1.3-2ubuntu2.3.debdiff -- 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/1994027 Title: Can't move window by drag and drop by using touch screen Status in OEM Priority Project: In Progress Status in XServer: Unknown Status in xorg package in Ubuntu: New Bug description: [Impact] Users using touch screen could not move windows with 'Drag-n-drop'. This SRU fixes the issue. [Test Plan] 1. Install the 22.04 2. Boot and login 3. Open a folder or terminal 4. Drag-n-drop the title bar of nautilus or terminal windows with finger touch 5. Drag-n-drop the title bar of nautilus or terminal windows with the Wacom Pen Expected: Both finger touch and wacom pen work normally. Actual: Wacom Pen works normally, finger touch can not move the windows. [Where problems could occur] It's a regression of upstream packages, https://gitlab.freedesktop.org/xorg/xserver/-/merge_requests/866 It reverts f682e0563f736ed2c2c612ed575e05b6e3db945e. [Version] xserver-xorg-core 2:21.1.3-2ubuntu2.2 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1994027/+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 1994027] Re: Can't move window by drag and drop by using touch screen
Here is the patch from upstream. ** Patch added: "dix-Don-t-send-touch-end-to-clients-that-do-async-grab.patch" https://bugs.launchpad.net/xserver/+bug/1994027/+attachment/5631766/+files/dix-Don-t-send-touch-end-to-clients-that-do-async-grab.patch -- 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/1994027 Title: Can't move window by drag and drop by using touch screen Status in OEM Priority Project: In Progress Status in XServer: Unknown Status in xorg package in Ubuntu: New Bug description: [Impact] Users using touch screen could not move windows with 'Drag-n-drop'. This SRU fixes the issue. [Test Plan] 1. Install the 22.04 2. Boot and login 3. Open a folder or terminal 4. Drag-n-drop the title bar of nautilus or terminal windows with finger touch 5. Drag-n-drop the title bar of nautilus or terminal windows with the Wacom Pen Expected: Both finger touch and wacom pen work normally. Actual: Wacom Pen works normally, finger touch can not move the windows. [Where problems could occur] It's a regression of upstream packages, https://gitlab.freedesktop.org/xorg/xserver/-/merge_requests/866 It reverts f682e0563f736ed2c2c612ed575e05b6e3db945e. [Version] xserver-xorg-core 2:21.1.3-2ubuntu2.2 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1994027/+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 1994027] Re: Can't move window by drag and drop by using touch screen
** Description changed: - [Summary] - For the test case 'Drag-n-drop' of testscreen,the Finger touch is failed. + [Impact] + Users using touch screen could not move windows with 'Drag-n-drop'. + This SRU fixes the issue. - [Steps to reproduce] + [Test Plan] 1. Install the 22.04 2. Boot and login 3. Open a folder or terminal 4. Drag-n-drop the title bar of nautilus or terminal windows with finger touch 5. Drag-n-drop the title bar of nautilus or terminal windows with the Wacom Pen - [Expected result] - Both finger touch and wacom pen work normally. + Expected: Both finger touch and wacom pen work normally. - [Actual result] - Wacom Pen works normally, finger touch can not move the windows. + Actual: Wacom Pen works normally, finger touch can not move the windows. - [Failure rate] - 100% + [Where problems could occur] + It's a regression of upstream packages, https://gitlab.freedesktop.org/xorg/xserver/-/merge_requests/866 - [Checkbox job `com.canonical.certification::touchscreen/drag-n-drop` - output] + It reverts f682e0563f736ed2c2c612ed575e05b6e3db945e. - [Other Information] - xorg 1:7.7+23ubuntu2 - mutter-common 42.2-0ubuntu1 - gnome-shell 42.4-0ubuntu0.22.04.1 + [Version] + xserver-xorg-core 2:21.1.3-2ubuntu2.2 -- 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/1994027 Title: Can't move window by drag and drop by using touch screen Status in OEM Priority Project: In Progress Status in XServer: Unknown Status in xorg package in Ubuntu: New Bug description: [Impact] Users using touch screen could not move windows with 'Drag-n-drop'. This SRU fixes the issue. [Test Plan] 1. Install the 22.04 2. Boot and login 3. Open a folder or terminal 4. Drag-n-drop the title bar of nautilus or terminal windows with finger touch 5. Drag-n-drop the title bar of nautilus or terminal windows with the Wacom Pen Expected: Both finger touch and wacom pen work normally. Actual: Wacom Pen works normally, finger touch can not move the windows. [Where problems could occur] It's a regression of upstream packages, https://gitlab.freedesktop.org/xorg/xserver/-/merge_requests/866 It reverts f682e0563f736ed2c2c612ed575e05b6e3db945e. [Version] xserver-xorg-core 2:21.1.3-2ubuntu2.2 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1994027/+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 1994027] Re: Can't move window by drag and drop by using touch screen
** No longer affects: gtk+3.0 (Ubuntu) ** Changed in: oem-priority Status: New => In Progress ** Changed in: oem-priority Assignee: (unassigned) => Bin Li (binli) ** Bug watch added: gitlab.freedesktop.org/xorg/xserver/-/issues #1255 https://gitlab.freedesktop.org/xorg/xserver/-/issues/1255 ** Project changed: mutter => xserver ** Changed in: xserver Status: New => Unknown ** Changed in: xserver Remote watch: gitlab.gnome.org/GNOME/mutter/-/issues #2057 => gitlab.freedesktop.org/xorg/xserver/-/issues #1255 -- 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/1994027 Title: Can't move window by drag and drop by using touch screen Status in OEM Priority Project: In Progress Status in XServer: Unknown Status in xorg package in Ubuntu: New Bug description: [Summary] For the test case 'Drag-n-drop' of testscreen,the Finger touch is failed. [Steps to reproduce] 1. Install the 22.04 2. Boot and login 3. Open a folder or terminal 4. Drag-n-drop the title bar of nautilus or terminal windows with finger touch 5. Drag-n-drop the title bar of nautilus or terminal windows with the Wacom Pen [Expected result] Both finger touch and wacom pen work normally. [Actual result] Wacom Pen works normally, finger touch can not move the windows. [Failure rate] 100% [Checkbox job `com.canonical.certification::touchscreen/drag-n-drop` output] [Other Information] xorg 1:7.7+23ubuntu2 mutter-common 42.2-0ubuntu1 gnome-shell 42.4-0ubuntu0.22.04.1 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1994027/+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 1994027] Re: Can't move window by drag and drop by using touch screen
** Description changed: [Summary] For the test case 'Drag-n-drop' of testscreen,the Finger touch is failed. [Steps to reproduce] 1. Install the 22.04 2. Boot and login 3. Open a folder - 4. Drag-n-drop the folder with finger touch - 5. Drag-n-drop the folder with the Wacom Pen + 4. Drag-n-drop the title bar of nautilus or terminal windows with finger touch + 5. Drag-n-drop the title bar of nautilus or terminal windows with the Wacom Pen [Expected result] Both finger touch and wacom pen work normally. [Actual result] - Wacom Pen works normally, finger touch can not move the folder. + Wacom Pen works normally, finger touch can not move the windows. [Failure rate] 100% [Checkbox job `com.canonical.certification::touchscreen/drag-n-drop` output] [Other Information] xorg 1:7.7+23ubuntu2 mutter-common 42.2-0ubuntu1 gnome-shell 42.4-0ubuntu0.22.04.1 ** Description changed: [Summary] For the test case 'Drag-n-drop' of testscreen,the Finger touch is failed. [Steps to reproduce] 1. Install the 22.04 2. Boot and login - 3. Open a folder + 3. Open a folder or terminal 4. Drag-n-drop the title bar of nautilus or terminal windows with finger touch 5. Drag-n-drop the title bar of nautilus or terminal windows with the Wacom Pen [Expected result] Both finger touch and wacom pen work normally. [Actual result] Wacom Pen works normally, finger touch can not move the windows. [Failure rate] 100% [Checkbox job `com.canonical.certification::touchscreen/drag-n-drop` output] [Other Information] xorg 1:7.7+23ubuntu2 mutter-common 42.2-0ubuntu1 gnome-shell 42.4-0ubuntu0.22.04.1 -- 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/1994027 Title: Can't move window by drag and drop by using touch screen Status in Mutter: New Status in OEM Priority Project: New Status in gtk+3.0 package in Ubuntu: New Status in xorg package in Ubuntu: New Bug description: [Summary] For the test case 'Drag-n-drop' of testscreen,the Finger touch is failed. [Steps to reproduce] 1. Install the 22.04 2. Boot and login 3. Open a folder or terminal 4. Drag-n-drop the title bar of nautilus or terminal windows with finger touch 5. Drag-n-drop the title bar of nautilus or terminal windows with the Wacom Pen [Expected result] Both finger touch and wacom pen work normally. [Actual result] Wacom Pen works normally, finger touch can not move the windows. [Failure rate] 100% [Checkbox job `com.canonical.certification::touchscreen/drag-n-drop` output] [Other Information] xorg 1:7.7+23ubuntu2 mutter-common 42.2-0ubuntu1 gnome-shell 42.4-0ubuntu0.22.04.1 To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1994027/+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 1987631] Re: Screencast only records one second
Our customer did more test with my built packages in #11, and the screencast issue is still reproduced, it looks like the below patch is not enough. https://gitlab.freedesktop.org/pipewire/pipewire/-/commit/1ea1d525 -- 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/1987631 Title: Screencast only records one second Status in GNOME Shell: Fix Released Status in OEM Priority Project: In Progress Status in gnome-shell package in Ubuntu: Fix Released Status in pipewire package in Ubuntu: Fix Released Status in gnome-shell source package in Jammy: Fix Released Status in pipewire source package in Jammy: New Bug description: When recording a screencast with gnome on kinetic the resulting video will play for one second and then freeze. It looks like the same bug was discussed upstream at https://gitlab.gnome.org/GNOME/gnome- shell/-/issues/5585 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1987631/+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 1987631] Re: Screencast only records one second
Yes, with the pipewire in proposed channel, we tested screencast 10 times, and couldn't reproduce this issue again. Thanks! pipewire 0.3.48-1ubuntu3 -- 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/1987631 Title: Screencast only records one second Status in GNOME Shell: Fix Released Status in OEM Priority Project: In Progress Status in gnome-shell package in Ubuntu: Fix Released Status in pipewire package in Ubuntu: Fix Released Status in gnome-shell source package in Jammy: Fix Released Status in pipewire source package in Jammy: New Bug description: When recording a screencast with gnome on kinetic the resulting video will play for one second and then freeze. It looks like the same bug was discussed upstream at https://gitlab.gnome.org/GNOME/gnome- shell/-/issues/5585 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1987631/+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 1987631] Re: Screencast only records one second
On 22.10, our customer could not reproduce this issue. I picked the patch in pipewire, the screencast becomes stable, the fail rate is lower than before, although it would skip frames for seconds. I will let our customer do more test. https://gitlab.freedesktop.org/pipewire/pipewire/-/commit/1ea1d525 https://people.canonical.com/~binli/pipewire/ -- 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/1987631 Title: Screencast only records one second Status in GNOME Shell: Fix Released Status in OEM Priority Project: In Progress Status in gnome-shell package in Ubuntu: Fix Released Status in pipewire package in Ubuntu: Fix Released Status in gnome-shell source package in Jammy: Fix Released Status in pipewire source package in Jammy: New Bug description: When recording a screencast with gnome on kinetic the resulting video will play for one second and then freeze. It looks like the same bug was discussed upstream at https://gitlab.gnome.org/GNOME/gnome- shell/-/issues/5585 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1987631/+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 1987631] Re: Screencast only records one second
** Tags added: oem-priority originate-from-1994117 sutton ** Changed in: oem-priority Assignee: (unassigned) => Bin Li (binli) ** Changed in: oem-priority Importance: Undecided => High ** Changed in: oem-priority Status: New => In Progress -- 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/1987631 Title: Screencast only records one second Status in GNOME Shell: Fix Released Status in OEM Priority Project: In Progress Status in gnome-shell package in Ubuntu: Fix Released Status in pipewire package in Ubuntu: Fix Released Status in gnome-shell source package in Jammy: Fix Released Status in pipewire source package in Jammy: New Bug description: When recording a screencast with gnome on kinetic the resulting video will play for one second and then freeze. It looks like the same bug was discussed upstream at https://gitlab.gnome.org/GNOME/gnome- shell/-/issues/5585 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1987631/+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 1995358] [NEW] Screencast only records few seconds
Public bug reported: Hi guys, Found a regression of pipewire on ThinkCentre Neo 50a, the screencast(Ctrl + Alt + Shift + R) could not record video correctly. The version 0.3.48-1ubuntu1 of pipewire works fine. After upgraded to 0.3.48-1ubuntu2, it's very easy to reproduce this issue. https://bugs.launchpad.net/ubuntu/+source/pipewire/+bug/1985057 ** Affects: oem-priority Importance: Undecided Status: New ** Affects: pipewire (Ubuntu) Importance: Undecided Status: New ** Tags: oem-priority originate-from-1994117 sutton ** Attachment added: "screencast.webm" https://bugs.launchpad.net/bugs/1995358/+attachment/5628254/+files/screencast.webm ** Tags added: oem-priority originate-from-1994117 sutton -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pipewire in Ubuntu. https://bugs.launchpad.net/bugs/1995358 Title: Screencast only records few seconds Status in OEM Priority Project: New Status in pipewire package in Ubuntu: New Bug description: Hi guys, Found a regression of pipewire on ThinkCentre Neo 50a, the screencast(Ctrl + Alt + Shift + R) could not record video correctly. The version 0.3.48-1ubuntu1 of pipewire works fine. After upgraded to 0.3.48-1ubuntu2, it's very easy to reproduce this issue. https://bugs.launchpad.net/ubuntu/+source/pipewire/+bug/1985057 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1995358/+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 1992752] Re: The length of video is inconsistent with the actual when using Cheese to record video
It's related to pipewire. lp:1994928 If I disabled the pipewire services, this issue is gone. $ systemctl --user disable --now pipewire pipewire-media-session pipewire.socket ** Also affects: pipewire (Ubuntu) Importance: Undecided Status: New ** Also affects: pipewire-media-session (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cheese in Ubuntu. https://bugs.launchpad.net/bugs/1992752 Title: The length of video is inconsistent with the actual when using Cheese to record video Status in OEM Priority Project: New Status in cheese package in Ubuntu: Confirmed Status in pipewire package in Ubuntu: New Status in pipewire-media-session package in Ubuntu: New Bug description: [steps reproduce] 1. Preload Ubuntu system 22.04.1 2. Lanuch Cheese to record video; 3. Found that the length of video is inconsistent with the actual recorded time. 4. It can pause when play the record video and play time exceeds record time. [failure rate] 100% [expected result] The video time should align with actual cost [actual result] The video play time exceeds record time [addtional infromation] CPU: Intel i5-12500H 2.5G Video: Intel® Iris® Xe Graphics Memory: 2x 8GB Storage: 512GB SSD To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1992752/+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 1994928] [NEW] Cheese freeze when recording video with pipewiresrc
Public bug reported: [Question Summary] Use Cheese to record video, and screen will hang during recording. [Reproduce steps] 1.Preload Ubuntu 22.04.1 LTS. 2.Open Cheese and start to record video. 3.Stop recording. [Expected result] Record video smoothly and play video in Cheese. [Actual result] The recorded video page stops, recording is often different from the actual. ** Affects: oem-priority Importance: Undecided Status: New ** Affects: pipewire (Ubuntu) Importance: Undecided Status: New ** Tags: oem-priority originate-from-1993784 sutton ** Tags added: oem-priority originate-from-1993784 sutton -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pipewire in Ubuntu. https://bugs.launchpad.net/bugs/1994928 Title: Cheese freeze when recording video with pipewiresrc Status in OEM Priority Project: New Status in pipewire package in Ubuntu: New Bug description: [Question Summary] Use Cheese to record video, and screen will hang during recording. [Reproduce steps] 1.Preload Ubuntu 22.04.1 LTS. 2.Open Cheese and start to record video. 3.Stop recording. [Expected result] Record video smoothly and play video in Cheese. [Actual result] The recorded video page stops, recording is often different from the actual. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1994928/+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 1994027] Re: Can't move window by drag and drop by using touch screen
It looks like related to mutter and gtk3. https://gitlab.gnome.org/GNOME/mutter/-/issues/2057 ** Bug watch added: gitlab.gnome.org/GNOME/mutter/-/issues #2057 https://gitlab.gnome.org/GNOME/mutter/-/issues/2057 ** Also 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 xorg in Ubuntu. https://bugs.launchpad.net/bugs/1994027 Title: Can't move window by drag and drop by using touch screen Status in OEM Priority Project: New Status in gtk+3.0 package in Ubuntu: New Status in xorg package in Ubuntu: New Bug description: [Summary] For the test case 'Drag-n-drop' of testscreen,the Finger touch is failed. [Steps to reproduce] 1. Install the 22.04 2. Boot and login 3. Open a folder 4. Drag-n-drop the folder with finger touch 5. Drag-n-drop the folder with the Wacom Pen [Expected result] Both finger touch and wacom pen work normally. [Actual result] Wacom Pen works normally, finger touch can not move the folder. [Failure rate] 100% [Checkbox job `com.canonical.certification::touchscreen/drag-n-drop` output] [Other Information] xorg 1:7.7+23ubuntu2 mutter-common 42.2-0ubuntu1 gnome-shell 42.4-0ubuntu0.22.04.1 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1994027/+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 1992752] Re: The length of video is inconsistent with the actual when using Cheese to record video
It should be same issue with lp:1949183 . ** Tags added: originate-from-1993784 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cheese in Ubuntu. https://bugs.launchpad.net/bugs/1992752 Title: The length of video is inconsistent with the actual when using Cheese to record video Status in OEM Priority Project: New Status in cheese package in Ubuntu: New Bug description: [steps reproduce] 1. Preload Ubuntu system 22.04.1 2. Lanuch Cheese to record video; 3. Found that the length of video is inconsistent with the actual recorded time. 4. It can pause when play the record video and play time exceeds record time. [failure rate] 100% [expected result] The video time should align with actual cost [actual result] The video play time exceeds record time [addtional infromation] CPU: Intel i5-12500H 2.5G Video: Intel® Iris® Xe Graphics Memory: 2x 8GB Storage: 512GB SSD To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1992752/+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 1949183] Re: Cheese screenshot white screen and video freezes
** Tags added: originate-from-1990246 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cheese in Ubuntu. https://bugs.launchpad.net/bugs/1949183 Title: Cheese screenshot white screen and video freezes Status in OEM Priority Project: New Status in cheese package in Ubuntu: Confirmed Bug description: Ubuntu 22.04 development branch with kernel 5.13.0-19-generic on wayland and Xorg When taking webcam pictures with cheese on wayland and xorg, it takes the picture but gives me a few seconds of white screen after the shot When taking a webcam video it takes a freezed picture instead of a video and has problems to push the stop recording button --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu70 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 MachineType: Notebook N7x0WU Package: cheese 3.38.0-4 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14 RelatedPackageVersions: cheese3.38.0-4 cheese-common 3.38.0-4 Tags: wayland-session jammy gstreamer-error Uname: Linux 5.13.0-19-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/07/2019 dmi.bios.release: 7.13 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 7.13 dmi.board.asset.tag: Tag 12345 dmi.board.name: N7x0WU dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.type: 10 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.ec.firmware.release: 7.14 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr7.13:bd01/07/2019:br7.13:efr7.14:svnNotebook:pnN7x0WU:pvrNotApplicable:skuNotApplicable:rvnNotebook:rnN7x0WU:rvrNotApplicable:cvnNoEnclosure:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: N7x0WU dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: Notebook lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0025 Intel Corp. Wireless-AC 9260 Bluetooth Adapter Bus 001 Device 003: ID 04f2:b59e Chicony Electronics Co., Ltd Chicony USB2.0 Camera Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu70 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 MachineType: Notebook N7x0WU Package: cheese 3.38.0-4 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14 RelatedPackageVersions: cheese3.38.0-4 cheese-common 3.38.0-4 Tags: wayland-session jammy gstreamer-error Uname: Linux 5.13.0-19-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/07/2019 dmi.bios.release: 7.13 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 7.13 dmi.board.asset.tag: Tag 12345 dmi.board.name: N7x0WU dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.type: 10 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.ec.firmware.release: 7.14 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr7.13:bd01/07/2019:br7.13:efr7.14:svnNotebook:pnN7x0WU:pvrNotApplicable:skuNotApplicable:rvnNotebook:rnN7x0WU:rvrNotApplicable:cvnNoEnclosure:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: N7x0WU dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: Notebook lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0025 Intel Corp. Wireless-AC 9260 Bluetooth Adapter Bus 001 Device 003: ID 04f2:b59e Chicony Electronics Co., Ltd Chicony USB2.0 Camera Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1949183/+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 1949183] Re: Cheese screenshot white screen and video freezes
** Tags added: originate-from-1993784 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cheese in Ubuntu. https://bugs.launchpad.net/bugs/1949183 Title: Cheese screenshot white screen and video freezes Status in OEM Priority Project: New Status in cheese package in Ubuntu: Confirmed Bug description: Ubuntu 22.04 development branch with kernel 5.13.0-19-generic on wayland and Xorg When taking webcam pictures with cheese on wayland and xorg, it takes the picture but gives me a few seconds of white screen after the shot When taking a webcam video it takes a freezed picture instead of a video and has problems to push the stop recording button --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu70 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 MachineType: Notebook N7x0WU Package: cheese 3.38.0-4 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14 RelatedPackageVersions: cheese3.38.0-4 cheese-common 3.38.0-4 Tags: wayland-session jammy gstreamer-error Uname: Linux 5.13.0-19-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/07/2019 dmi.bios.release: 7.13 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 7.13 dmi.board.asset.tag: Tag 12345 dmi.board.name: N7x0WU dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.type: 10 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.ec.firmware.release: 7.14 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr7.13:bd01/07/2019:br7.13:efr7.14:svnNotebook:pnN7x0WU:pvrNotApplicable:skuNotApplicable:rvnNotebook:rnN7x0WU:rvrNotApplicable:cvnNoEnclosure:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: N7x0WU dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: Notebook lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0025 Intel Corp. Wireless-AC 9260 Bluetooth Adapter Bus 001 Device 003: ID 04f2:b59e Chicony Electronics Co., Ltd Chicony USB2.0 Camera Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu70 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 MachineType: Notebook N7x0WU Package: cheese 3.38.0-4 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14 RelatedPackageVersions: cheese3.38.0-4 cheese-common 3.38.0-4 Tags: wayland-session jammy gstreamer-error Uname: Linux 5.13.0-19-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/07/2019 dmi.bios.release: 7.13 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 7.13 dmi.board.asset.tag: Tag 12345 dmi.board.name: N7x0WU dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.type: 10 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.ec.firmware.release: 7.14 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr7.13:bd01/07/2019:br7.13:efr7.14:svnNotebook:pnN7x0WU:pvrNotApplicable:skuNotApplicable:rvnNotebook:rnN7x0WU:rvrNotApplicable:cvnNoEnclosure:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: N7x0WU dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: Notebook lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0025 Intel Corp. Wireless-AC 9260 Bluetooth Adapter Bus 001 Device 003: ID 04f2:b59e Chicony Electronics Co., Ltd Chicony USB2.0 Camera Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1949183/+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 1994027] Re: Can't move window by drag and drop by using touch screen
Switch to wayland, this issue is gone. -- 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/1994027 Title: Can't move window by drag and drop by using touch screen Status in OEM Priority Project: New Status in xorg package in Ubuntu: New Bug description: [Summary] For the test case 'Drag-n-drop' of testscreen,the Finger touch is failed. [Steps to reproduce] 1. Install the 22.04 2. Boot and login 3. Open a folder 4. Drag-n-drop the folder with finger touch 5. Drag-n-drop the folder with the Wacom Pen [Expected result] Both finger touch and wacom pen work normally. [Actual result] Wacom Pen works normally, finger touch can not move the folder. [Failure rate] 100% [Checkbox job `com.canonical.certification::touchscreen/drag-n-drop` output] [Other Information] xorg 1:7.7+23ubuntu2 mutter-common 42.2-0ubuntu1 gnome-shell 42.4-0ubuntu0.22.04.1 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1994027/+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 1994027] Re: Can't move window by drag and drop by using touch screen
The touch screen works fine on 20.04 image. ** Description changed: [Summary] For the test case 'Drag-n-drop' of testscreen,the Finger touch is failed. [Steps to reproduce] 1. Install the 22.04 2. Boot and login 3. Open a folder 4. Drag-n-drop the folder with finger touch 5. Drag-n-drop the folder with the Wacom Pen [Expected result] Both finger touch and wacom pen work normally. [Actual result] Wacom Pen works normally, finger touch can not move the folder. [Failure rate] 100% [Checkbox job `com.canonical.certification::touchscreen/drag-n-drop` output] + + [Other Information] + xorg 1:7.7+23ubuntu2 + mutter-common 42.2-0ubuntu1 + gnome-shell 42.4-0ubuntu0.22.04.1 ** Tags added: oem-priority originate-from-1991363 sutton -- 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/1994027 Title: Can't move window by drag and drop by using touch screen Status in OEM Priority Project: New Status in xorg package in Ubuntu: New Bug description: [Summary] For the test case 'Drag-n-drop' of testscreen,the Finger touch is failed. [Steps to reproduce] 1. Install the 22.04 2. Boot and login 3. Open a folder 4. Drag-n-drop the folder with finger touch 5. Drag-n-drop the folder with the Wacom Pen [Expected result] Both finger touch and wacom pen work normally. [Actual result] Wacom Pen works normally, finger touch can not move the folder. [Failure rate] 100% [Checkbox job `com.canonical.certification::touchscreen/drag-n-drop` output] [Other Information] xorg 1:7.7+23ubuntu2 mutter-common 42.2-0ubuntu1 gnome-shell 42.4-0ubuntu0.22.04.1 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1994027/+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 1994027] [NEW] Can't move window by drag and drop by using touch screen
Public bug reported: [Summary] For the test case 'Drag-n-drop' of testscreen,the Finger touch is failed. [Steps to reproduce] 1. Install the 22.04 2. Boot and login 3. Open a folder 4. Drag-n-drop the folder with finger touch 5. Drag-n-drop the folder with the Wacom Pen [Expected result] Both finger touch and wacom pen work normally. [Actual result] Wacom Pen works normally, finger touch can not move the folder. [Failure rate] 100% [Checkbox job `com.canonical.certification::touchscreen/drag-n-drop` output] [Other Information] xorg 1:7.7+23ubuntu2 mutter-common 42.2-0ubuntu1 gnome-shell 42.4-0ubuntu0.22.04.1 ** Affects: oem-priority Importance: Undecided Status: New ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: oem-priority originate-from-1991363 sutton -- 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/1994027 Title: Can't move window by drag and drop by using touch screen Status in OEM Priority Project: New Status in xorg package in Ubuntu: New Bug description: [Summary] For the test case 'Drag-n-drop' of testscreen,the Finger touch is failed. [Steps to reproduce] 1. Install the 22.04 2. Boot and login 3. Open a folder 4. Drag-n-drop the folder with finger touch 5. Drag-n-drop the folder with the Wacom Pen [Expected result] Both finger touch and wacom pen work normally. [Actual result] Wacom Pen works normally, finger touch can not move the folder. [Failure rate] 100% [Checkbox job `com.canonical.certification::touchscreen/drag-n-drop` output] [Other Information] xorg 1:7.7+23ubuntu2 mutter-common 42.2-0ubuntu1 gnome-shell 42.4-0ubuntu0.22.04.1 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1994027/+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 1994007] Re: totem show black screen when playing video repeatedly [resource creation failed]
Daniel,
Thanks for the information.
The totem didn't crash in my side, just black screen, and there is not crash
file in /var/crash. And there is not gstreamer1.0-vaapi package currently.
And I made a script to play this file in gstreamer, it works fine. So I
doubt this issue is related totem. smplayer and vlc looks fine in my
side.
#!/bin/bash
for a in {1..100}
do
echo $a
gst-launch-1.0 filesrc location=Robotica_1080_convert.ogv ! oggdemux !
theoradec ! autovideosink
done
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to totem in Ubuntu.
https://bugs.launchpad.net/bugs/1994007
Title:
totem show black screen when playing video repeatedly [resource
creation failed]
Status in OEM Priority Project:
New
Status in totem package in Ubuntu:
New
Bug description:
[steps reproduce]
1. Install Ubuntu 22.04.1LTS.
2. Play Robotica_1080_convert.ogv with Videos(totem) with cycles.
3. some times after 10 mins, some times within 2 hours,find unit's videos
show a black screen.
Details please refer to the attachments.
[failure rate]
100
[expected result]
It should can play normally.
[actual result]
find unit's videos show blackscreen,
[addtional infromation]
totem: 42.0-1ubuntu1
gstreamer1.0-plugins-base 1.20.1-1
To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1994007/+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 1994007] Re: totem show blackscreen when playing video repeatedly
@Daniel, It should be Wayland, no nvidia card, and I could not find Xorg in 'ps -ef | grep X'. Please give it an hour or more when do testing. I could reproduce this issue on ThinkPad too. ** Attachment added: "lspci.log" https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1994007/+attachment/5626378/+files/lspci.log -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to totem in Ubuntu. https://bugs.launchpad.net/bugs/1994007 Title: totem show blackscreen when playing video repeatedly Status in OEM Priority Project: New Status in totem package in Ubuntu: Incomplete Bug description: [steps reproduce] 1. Install Ubuntu 22.04.1LTS. 2. Play Robotica_1080_convert.ogv with Videos(totem) with cycles. 3. some times after 10 mins, some times within 2 hours,find unit's videos show a black screen. Details please refer to the attachments. [failure rate] 100 [expected result] It should can play normally. [actual result] find unit's videos show blackscreen, [addtional infromation] totem: 42.0-1ubuntu1 gstreamer1.0-plugins-base 1.20.1-1 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1994007/+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 1994007] Re: totem show blackscreen when playing video repeatedly
Screenshot of this issue. ** Attachment added: "blackscreen.png" https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1994007/+attachment/5626376/+files/blackscreen.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to totem in Ubuntu. https://bugs.launchpad.net/bugs/1994007 Title: totem show blackscreen when playing video repeatedly Status in OEM Priority Project: New Status in totem package in Ubuntu: Incomplete Bug description: [steps reproduce] 1. Install Ubuntu 22.04.1LTS. 2. Play Robotica_1080_convert.ogv with Videos(totem) with cycles. 3. some times after 10 mins, some times within 2 hours,find unit's videos show a black screen. Details please refer to the attachments. [failure rate] 100 [expected result] It should can play normally. [actual result] find unit's videos show blackscreen, [addtional infromation] totem: 42.0-1ubuntu1 gstreamer1.0-plugins-base 1.20.1-1 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1994007/+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 1994007] Re: totem show blackscreen when playing video repeatedly
I didn't find any errors with below debugging method. G_MESSAGES_DEBUG=all totem XXX.ogv GST_DEBUG_NO_COLOR=1 GST_DEBUG=*:2 totem XXX.ogv -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to totem in Ubuntu. https://bugs.launchpad.net/bugs/1994007 Title: totem show blackscreen when playing video repeatedly Status in OEM Priority Project: New Status in totem package in Ubuntu: New Bug description: [steps reproduce] 1. Install Ubuntu 22.04.1LTS. 2. Play Robotica_1080_convert.ogv with Videos(totem) with cycles. 3. some times after 10 mins, some times within 2 hours,find unit's videos show a black screen. Details please refer to the attachments. [failure rate] 100 [expected result] It should can play normally. [actual result] find unit's videos show blackscreen, [addtional infromation] totem: 42.0-1ubuntu1 gstreamer1.0-plugins-base 1.20.1-1 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1994007/+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 1994007] Re: totem show blackscreen when playing video repeatedly
Testing video ** Attachment added: "Robotica_1080_convert.ogv" https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1994007/+attachment/5626369/+files/Robotica_1080_convert.ogv ** Tags added: oem-priority originate-from-1992321 sutton -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to totem in Ubuntu. https://bugs.launchpad.net/bugs/1994007 Title: totem show blackscreen when playing video repeatedly Status in OEM Priority Project: New Status in totem package in Ubuntu: New Bug description: [steps reproduce] 1. Install Ubuntu 22.04.1LTS. 2. Play Robotica_1080_convert.ogv with Videos(totem) with cycles. 3. some times after 10 mins, some times within 2 hours,find unit's videos show a black screen. Details please refer to the attachments. [failure rate] 100 [expected result] It should can play normally. [actual result] find unit's videos show blackscreen, [addtional infromation] totem: 42.0-1ubuntu1 gstreamer1.0-plugins-base 1.20.1-1 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1994007/+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 1994007] [NEW] totem show blackscreen when playing video repeatedly
Public bug reported: [steps reproduce] 1. Install Ubuntu 22.04.1LTS. 2. Play Robotica_1080_convert.ogv with Videos(totem) with cycles. 3. some times after 10 mins, some times within 2 hours,find unit's videos show a black screen. Details please refer to the attachments. [failure rate] 100 [expected result] It should can play normally. [actual result] find unit's videos show blackscreen, [addtional infromation] totem: 42.0-1ubuntu1 gstreamer1.0-plugins-base 1.20.1-1 ** Affects: oem-priority Importance: Undecided Status: New ** Affects: totem (Ubuntu) Importance: Undecided Status: New ** Tags: oem-priority originate-from-1992321 sutton -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to totem in Ubuntu. https://bugs.launchpad.net/bugs/1994007 Title: totem show blackscreen when playing video repeatedly Status in OEM Priority Project: New Status in totem package in Ubuntu: New Bug description: [steps reproduce] 1. Install Ubuntu 22.04.1LTS. 2. Play Robotica_1080_convert.ogv with Videos(totem) with cycles. 3. some times after 10 mins, some times within 2 hours,find unit's videos show a black screen. Details please refer to the attachments. [failure rate] 100 [expected result] It should can play normally. [actual result] find unit's videos show blackscreen, [addtional infromation] totem: 42.0-1ubuntu1 gstreamer1.0-plugins-base 1.20.1-1 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1994007/+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 1992752] Re: The length of video is inconsistent with the actual when using Cheese to record video
Some upstream bugs might be related to this issue. https://askubuntu.com/questions/1392849/cheese-captures-long-corrupted- videos https://gitlab.gnome.org/GNOME/cheese/-/issues/98 https://gitlab.gnome.org/GNOME/cheese/-/issues/79 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cheese in Ubuntu. https://bugs.launchpad.net/bugs/1992752 Title: The length of video is inconsistent with the actual when using Cheese to record video Status in OEM Priority Project: New Status in cheese package in Ubuntu: New Bug description: [steps reproduce] 1. Preload Ubuntu system 22.04.1 2. Lanuch Cheese to record video; 3. Found that the length of video is inconsistent with the actual recorded time. 4. It can pause when play the record video and play time exceeds record time. [failure rate] 100% [expected result] The video time should align with actual cost [actual result] The video play time exceeds record time [addtional infromation] CPU: Intel i5-12500H 2.5G Video: Intel® Iris® Xe Graphics Memory: 2x 8GB Storage: 512GB SSD To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1992752/+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 1992752] Re: The length of video is inconsistent with the actual when using Cheese to record video
** Attachment added: "cheese-video-length.png" https://bugs.launchpad.net/ubuntu/+source/cheese/+bug/1992752/+attachment/5623824/+files/cheese-video-length.png ** Tags added: oem-priority originate-from-1990246 sutton ** Bug watch added: gitlab.gnome.org/GNOME/cheese/-/issues #98 https://gitlab.gnome.org/GNOME/cheese/-/issues/98 ** Bug watch added: gitlab.gnome.org/GNOME/cheese/-/issues #79 https://gitlab.gnome.org/GNOME/cheese/-/issues/79 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cheese in Ubuntu. https://bugs.launchpad.net/bugs/1992752 Title: The length of video is inconsistent with the actual when using Cheese to record video Status in OEM Priority Project: New Status in cheese package in Ubuntu: New Bug description: [steps reproduce] 1. Preload Ubuntu system 22.04.1 2. Lanuch Cheese to record video; 3. Found that the length of video is inconsistent with the actual recorded time. 4. It can pause when play the record video and play time exceeds record time. [failure rate] 100% [expected result] The video time should align with actual cost [actual result] The video play time exceeds record time [addtional infromation] CPU: Intel i5-12500H 2.5G Video: Intel® Iris® Xe Graphics Memory: 2x 8GB Storage: 512GB SSD To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1992752/+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 1992752] [NEW] The length of video is inconsistent with the actual when using Cheese to record video
Public bug reported: [steps reproduce] 1. Preload Ubuntu system 22.04.1 2. Lanuch Cheese to record video; 3. Found that the length of video is inconsistent with the actual recorded time. 4. It can pause when play the record video and play time exceeds record time. [failure rate] 100% [expected result] The video time should align with actual cost [actual result] The video play time exceeds record time [addtional infromation] CPU: Intel i5-12500H 2.5G Video: Intel® Iris® Xe Graphics Memory: 2x 8GB Storage: 512GB SSD ** Affects: oem-priority Importance: Undecided Status: New ** Affects: cheese (Ubuntu) Importance: Undecided Status: New ** Tags: oem-priority originate-from-1990246 sutton -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cheese in Ubuntu. https://bugs.launchpad.net/bugs/1992752 Title: The length of video is inconsistent with the actual when using Cheese to record video Status in OEM Priority Project: New Status in cheese package in Ubuntu: New Bug description: [steps reproduce] 1. Preload Ubuntu system 22.04.1 2. Lanuch Cheese to record video; 3. Found that the length of video is inconsistent with the actual recorded time. 4. It can pause when play the record video and play time exceeds record time. [failure rate] 100% [expected result] The video time should align with actual cost [actual result] The video play time exceeds record time [addtional infromation] CPU: Intel i5-12500H 2.5G Video: Intel® Iris® Xe Graphics Memory: 2x 8GB Storage: 512GB SSD To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1992752/+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 1977986] Re: UPower and battery indicator show update in 2 minutes when connecting power cable ThinkPad
** Tags added: originate-from-1991377 -- 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/1977986 Title: UPower and battery indicator show update in 2 minutes when connecting power cable ThinkPad Status in OEM Priority Project: New Status in upower package in Ubuntu: New Bug description: We found this issue on several ThinkPad. The upower will change 'pending-charge' to 'charging' after 2 minutes later, but the /sys/class/power_supply/BAT0/status changes to 'Charging' immediately when connecting the power cable. $ upower -i /org/freedesktop/UPower/devices/battery_BAT0 native-path: BAT0 vendor: Sunwoda model:5B10W13975 serial: 34226 power supply: yes updated: Wed 08 Jun 2022 11:42:02 PM CST (1 seconds ago) has history: yes has statistics: yes battery present: yes rechargeable:yes state: pending-charge warning-level: none energy: 55.94 Wh energy-empty:0 Wh energy-full: 57 Wh energy-full-design: 57 Wh energy-rate: 5.79 W voltage: 16.688 V percentage: 98% capacity:100% technology: lithium-polymer icon-name: 'battery-full-charging-symbolic' History (charge): 1654702882 98.000 pending-charge 1654702863 97.000 pending-charge History (rate): 1654702863 5.790 pending-charge 1654702863 6.171 pending-charge $ cat /sys/class/power_supply/BAT0/status Charging To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1977986/+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 1990456] Re: xorg reports bogus 1600x1024 resolution
With new packages,this issue is fixed on ThinkPad P16. Commandline: apt install xserver-common xserver-xephyr xserver-xorg-core xserver-xorg-legacy Requested-By: u (1001) Upgrade: xserver-xorg-core:amd64 (2:21.1.3-2ubuntu2.1, 2:21.1.3-2ubuntu2.2), xserver-xorg-legacy:amd64 (2:21.1.3-2ubuntu2.1, 2:21.1.3-2ubuntu2.2), xserver-common:amd64 (2:21.1.3-2ubuntu2.1, 2:21.1.3-2ubuntu2.2), xserver-xephyr:amd64 (2:21.1.3-2ubuntu2.1, 2:21.1.3-2ubuntu2.2) End-Date: 2022-09-28 05:15:30 -- 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/1990456 Title: xorg reports bogus 1600x1024 resolution Status in OEM Priority Project: New Status in xorg-server package in Ubuntu: Fix Released Status in xorg-server source package in Jammy: Fix Committed Bug description: xorg reports 1600x1024 bogus resolution [ Impact ] * User of NVIDIA GPU is able to switch to 1600x1024 resolution but cannot display anything under the resolution [ Fix ] Drop 001_fedora_extramodes.patch which was dropped from Fedora since xserver 1.5.0. [ Test Plan ] 1. Find a test unit with NVIDIA GPU, or anything but use Xorg mode to enter the desktop 2. Type `xrandr` in terminal Expected: The resolution 1600x1024 should not appear if the display does not support it. Actual: The resolution 1600x1024 appears. [ Where problems could occur ] * Lack of extra modes that the display might actually support. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1990456/+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 1949183] Re: Cheese screenshot white screen and video freezes
** Tags added: oem-priority originate-from-1990252 sutton -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cheese in Ubuntu. https://bugs.launchpad.net/bugs/1949183 Title: Cheese screenshot white screen and video freezes Status in OEM Priority Project: New Status in cheese package in Ubuntu: Confirmed Bug description: Ubuntu 22.04 development branch with kernel 5.13.0-19-generic on wayland and Xorg When taking webcam pictures with cheese on wayland and xorg, it takes the picture but gives me a few seconds of white screen after the shot When taking a webcam video it takes a freezed picture instead of a video and has problems to push the stop recording button --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu70 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 MachineType: Notebook N7x0WU Package: cheese 3.38.0-4 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14 RelatedPackageVersions: cheese3.38.0-4 cheese-common 3.38.0-4 Tags: wayland-session jammy gstreamer-error Uname: Linux 5.13.0-19-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/07/2019 dmi.bios.release: 7.13 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 7.13 dmi.board.asset.tag: Tag 12345 dmi.board.name: N7x0WU dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.type: 10 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.ec.firmware.release: 7.14 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr7.13:bd01/07/2019:br7.13:efr7.14:svnNotebook:pnN7x0WU:pvrNotApplicable:skuNotApplicable:rvnNotebook:rnN7x0WU:rvrNotApplicable:cvnNoEnclosure:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: N7x0WU dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: Notebook lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0025 Intel Corp. Wireless-AC 9260 Bluetooth Adapter Bus 001 Device 003: ID 04f2:b59e Chicony Electronics Co., Ltd Chicony USB2.0 Camera Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu70 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 MachineType: Notebook N7x0WU Package: cheese 3.38.0-4 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14 RelatedPackageVersions: cheese3.38.0-4 cheese-common 3.38.0-4 Tags: wayland-session jammy gstreamer-error Uname: Linux 5.13.0-19-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/07/2019 dmi.bios.release: 7.13 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 7.13 dmi.board.asset.tag: Tag 12345 dmi.board.name: N7x0WU dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.type: 10 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.ec.firmware.release: 7.14 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr7.13:bd01/07/2019:br7.13:efr7.14:svnNotebook:pnN7x0WU:pvrNotApplicable:skuNotApplicable:rvnNotebook:rnN7x0WU:rvrNotApplicable:cvnNoEnclosure:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: N7x0WU dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: Notebook lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0025 Intel Corp. Wireless-AC 9260 Bluetooth Adapter Bus 001 Device 003: ID 04f2:b59e Chicony Electronics Co., Ltd Chicony USB2.0 Camera Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1949183/+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 1990456] Re: xorg reports bogus 1600x1024 resolution
Great! Thanks. -- 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/1990456 Title: xorg reports bogus 1600x1024 resolution Status in OEM Priority Project: New Status in xorg-server package in Ubuntu: Fix Released Status in xorg-server source package in Jammy: Confirmed Bug description: xorg reports 1600x1024 bogus resolution [ Impact ] * User of NVIDIA GPU is able to switch to 1600x1024 resolution but cannot display anything under the resolution [ Fix ] Drop 001_fedora_extramodes.patch which was dropped from Fedora since xserver 1.5.0. [ Test Plan ] 1. Find a test unit with NVIDIA GPU, or anything but use Xorg mode to enter the desktop 2. Type `xrandr` in terminal Expected: The resolution 1600x1024 should not appear if the display does not support it. Actual: The resolution 1600x1024 appears. [ Where problems could occur ] * Lack of extra modes that the display might actually support. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1990456/+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 1990456] Re: xorg reports bogus 1600x1024 resolution
@timo, Could we SRU to jammy? Thanks! ** Tags added: originate-from-1990088 sutton ** Tags added: originate-from-1981532 -- 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/1990456 Title: xorg reports bogus 1600x1024 resolution Status in OEM Priority Project: New Status in xorg-server package in Ubuntu: Fix Released Status in xorg-server source package in Jammy: New Bug description: xorg reports 1600x1024 bogus resolution [ Impact ] * User of NVIDIA GPU is able to switch to 1600x1024 resolution but cannot display anything under the resolution [ Fix ] Drop 001_fedora_extramodes.patch which was dropped from Fedora since xserver 1.5.0. [ Test Plan ] 1. Find a test unit with NVIDIA GPU, or anything but use Xorg mode to enter the desktop 2. Type `xrandr` in terminal Expected: The resolution 1600x1024 should not appear if the display does not support it. Actual: The resolution 1600x1024 appears. [ Where problems could occur ] * Lack of extra modes that the display might actually support. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1990456/+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 1977986] Re: UPower and battery indicator show update in 2 minutes when connecting power cable ThinkPad
** Tags added: originate-from-1989447 -- 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/1977986 Title: UPower and battery indicator show update in 2 minutes when connecting power cable ThinkPad Status in OEM Priority Project: New Status in upower package in Ubuntu: New Bug description: We found this issue on several ThinkPad. The upower will change 'pending-charge' to 'charging' after 2 minutes later, but the /sys/class/power_supply/BAT0/status changes to 'Charging' immediately when connecting the power cable. $ upower -i /org/freedesktop/UPower/devices/battery_BAT0 native-path: BAT0 vendor: Sunwoda model:5B10W13975 serial: 34226 power supply: yes updated: Wed 08 Jun 2022 11:42:02 PM CST (1 seconds ago) has history: yes has statistics: yes battery present: yes rechargeable:yes state: pending-charge warning-level: none energy: 55.94 Wh energy-empty:0 Wh energy-full: 57 Wh energy-full-design: 57 Wh energy-rate: 5.79 W voltage: 16.688 V percentage: 98% capacity:100% technology: lithium-polymer icon-name: 'battery-full-charging-symbolic' History (charge): 1654702882 98.000 pending-charge 1654702863 97.000 pending-charge History (rate): 1654702863 5.790 pending-charge 1654702863 6.171 pending-charge $ cat /sys/class/power_supply/BAT0/status Charging To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1977986/+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
Re: [Desktop-packages] [Bug 1816497] Re: [snap] vaapi chromium no video hardware decoding
My T460P (nvida + intel GPU): snap X11 works. video decoder with
hardware acceleration.
ubuntu frame with WayLand test: proper display.
Only problem is no video hardware decode. (I think it is not the snap
problem, the native version is also not support.)
It is nearly a perfect build.
Hope the wayland hardware acceleration will work in near future.
Lee
On Thu, Aug 18, 2022 at 1:44 AM Nathan Teodosio <1816...@bugs.launchpad.net>
wrote:
> The snap in the hwacc channel has been updated. Now it automatically
> detects Wayland or Xorg and sets flags accordingly.
>
> ** Description changed:
>
> To test the snap with VA-API changes,
>
> 1. Install the Chromium snap,
>
> sudo snap install --channel candidate/hwacc chromium
>
> - 2. If on Xorg (`echo $WAYLAND_DISPLAY` is empty),
> + 2. Start Chromium,
>
> -snap run chromium --disable-features=UseChromeOSDirectVideoDecoder
> - --enable-features=VaapiVideoDecoder
> -
> -If on Wayland (`echo $WAYLAND_DISPLAY` is not empty),
> -
> - chromium --enable-features=VaapiVideoDecoder --disable-
> - features=UseChromeOSDirectVideoDecoder --ozone-platform=wayland
> +snap run chromium
>
> 3. Open a video, e.g. one from https://github.com/chthomos/video-media-
> samples
>
> - 4. Enter about:media-internals in the address bar and note what the page
> - says for kVideoDecoderName.
> + 4. Enter about:media-internals in the address bar, click the
> + corresponding box (if the video is playing, it will have the "(kPlay)"
> + identifier) and note what the page says for kVideoDecoderName.
>
> Please report
>
> - - The value for kVideoDecoderName from step 4. Success is typically
> {Vaapi,VDA,Mojo}VideoDecoder while failure is {FFMpeg,Vpx}VideoDecoder;
> - - If failed, the video used for testing, including codec and
> resolution if possible;
> + - The value for kVideoDecoderName from step 4. Success is typically
> {Vaapi,VDA,Mojo}VideoDecoder while failure is
> {FFMpeg,Vpx,Dav1d}VideoDecoder;
> - Xorg or Wayland (`echo $WAYLAND_DISPLAY`);
> - Distro version (`grep VERSION= /etc/os_release`);
> - GPU (`lscpu`);
> - CPU generation (`lscpu`).
>
> About the last point, it may be that unfortunately only those with newer
> generations of Intel CPUs will have luck with this, but it's still an
> uncertainty. So reports are highly welcome.
>
> --Original Bug report -
>
> Libva is no longer working for snap installed chromium 72.0.3626.109
> (Official Build) snap (64-bit)
>
> I followed this instruction
> sudo snap install --channel=candidate/vaapi chromium
>
> My amdgpu can use libva
>
> `vainfo: Driver version: Mesa Gallium driver 18.3.3 for AMD STONEY (DRM
> 3.27.0, 4.20.0-10.1-liquorix-amd64, LLVM 7.0.1)
> vainfo: Supported profile and entrypoints
> VAProfileMPEG2Simple: VAEntrypointVLD
> VAProfileMPEG2Main : VAEntrypointVLD
> VAProfileVC1Simple : VAEntrypointVLD
> VAProfileVC1Main: VAEntrypointVLD
> VAProfileVC1Advanced: VAEntrypointVLD
> VAProfileH264ConstrainedBaseline: VAEntrypointVLD
> VAProfileH264ConstrainedBaseline: VAEntrypointEncSlice
> VAProfileH264Main : VAEntrypointVLD
> VAProfileH264Main : VAEntrypointEncSlice
> VAProfileH264High : VAEntrypointVLD
> VAProfileH264High : VAEntrypointEncSlice
> VAProfileHEVCMain : VAEntrypointVLD
> VAProfileHEVCMain10 : VAEntrypointVLD
> VAProfileJPEGBaseline : VAEntrypointVLD
> VAProfileNone : VAEntrypointVideoProc`
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1816497
>
> Title:
> [snap] vaapi chromium no video hardware decoding
>
> Status in chromium-browser package in Ubuntu:
> In Progress
>
> Bug description:
> To test the snap with VA-API changes,
>
> 1. Install the Chromium snap,
>
> sudo snap install --channel candidate/hwacc chromium
>
> 2. Start Chromium,
>
> snap run chromium
>
> 3. Open a video, e.g. one from https://github.com/chthomos/video-
> media-samples
>
> 4. Enter about:media-internals in the address bar, click the
> corresponding box (if the video is playing, it will have the "(kPlay)"
> identifier) and note what the page says for kVideoDecoderName.
>
> Please report
>
> - The value for kVideoDecoderName from step 4. Success is typically
> {Vaapi,VDA,Mojo}VideoDecoder while failure is
> {FFMpeg,Vpx,Dav1d}VideoDecoder;
> - Xorg or Wayland (`echo $WAYLAND_DISPLAY`);
> - Distro version (`grep VERSION= /etc/os_release`);
> - GPU (`lscpu`);
> - CPU generation (`lscpu`).
>
> About the last point, it may be that unfortunately only those with
>
[Desktop-packages] [Bug 1984106] [NEW] "Position of new icons" can't work
Public bug reported: Our OEM vendor reported this issue. [Steps to reproduce] 1.Install Ubuntu 22.04 2.Enter OS 3.Click Settings->Appearance->Position of new icons [Expected result] Choose different position,folder will follow the command [Actual result] Choose different position,it is unchanged. [Failure rate] 100% ** Affects: gnome-shell-extension-desktop-icons-ng (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-desktop-icons-ng in Ubuntu. https://bugs.launchpad.net/bugs/1984106 Title: "Position of new icons" can't work Status in gnome-shell-extension-desktop-icons-ng package in Ubuntu: New Bug description: Our OEM vendor reported this issue. [Steps to reproduce] 1.Install Ubuntu 22.04 2.Enter OS 3.Click Settings->Appearance->Position of new icons [Expected result] Choose different position,folder will follow the command [Actual result] Choose different position,it is unchanged. [Failure rate] 100% To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-desktop-icons-ng/+bug/1984106/+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 1816497] Re: [snap] vaapi chromium no video hardware decoding
The native chromium works. So I did not think it is a ubuntu-frame bug.
I test the previous snap chromium version before, and it also works.
--
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/1816497
Title:
[snap] vaapi chromium no video hardware decoding
Status in chromium-browser package in Ubuntu:
In Progress
Bug description:
To test the snap with VA-API changes,
1. Install the Chromium snap,
sudo snap install --channel candidate/hwacc chromium
2. If on Xorg (`echo $WAYLAND_DISPLAY` is empty),
snap run chromium --disable-features=UseChromeOSDirectVideoDecoder
--enable-features=VaapiVideoDecoder
If on Wayland (`echo $WAYLAND_DISPLAY` is not empty),
chromium --enable-features=VaapiVideoDecoder --disable-
features=UseChromeOSDirectVideoDecoder --ozone-platform=wayland
3. Open a video, e.g. one from https://github.com/chthomos/video-
media-samples
4. Enter about:media-internals in the address bar and note what the
page says for kVideoDecoderName.
Please report
- The value for kVideoDecoderName from step 4. Success is typically
{Vaapi,VDA,Mojo}VideoDecoder while failure is {FFMpeg,Vpx}VideoDecoder;
- If failed, the video used for testing, including codec and resolution if
possible;
- Xorg or Wayland (`echo $WAYLAND_DISPLAY`);
- Distro version (`grep VERSION= /etc/os_release`);
- GPU (`lscpu`);
- CPU generation (`lscpu`).
About the last point, it may be that unfortunately only those with
newer generations of Intel CPUs will have luck with this, but it's
still an uncertainty. So reports are highly welcome.
--Original Bug report -
Libva is no longer working for snap installed chromium 72.0.3626.109
(Official Build) snap (64-bit)
I followed this instruction
sudo snap install --channel=candidate/vaapi chromium
My amdgpu can use libva
`vainfo: Driver version: Mesa Gallium driver 18.3.3 for AMD STONEY (DRM
3.27.0, 4.20.0-10.1-liquorix-amd64, LLVM 7.0.1)
vainfo: Supported profile and entrypoints
VAProfileMPEG2Simple: VAEntrypointVLD
VAProfileMPEG2Main : VAEntrypointVLD
VAProfileVC1Simple : VAEntrypointVLD
VAProfileVC1Main: VAEntrypointVLD
VAProfileVC1Advanced: VAEntrypointVLD
VAProfileH264ConstrainedBaseline: VAEntrypointVLD
VAProfileH264ConstrainedBaseline: VAEntrypointEncSlice
VAProfileH264Main : VAEntrypointVLD
VAProfileH264Main : VAEntrypointEncSlice
VAProfileH264High : VAEntrypointVLD
VAProfileH264High : VAEntrypointEncSlice
VAProfileHEVCMain : VAEntrypointVLD
VAProfileHEVCMain10 : VAEntrypointVLD
VAProfileJPEGBaseline : VAEntrypointVLD
VAProfileNone : VAEntrypointVideoProc`
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1816497/+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 1816497] Re: [snap] vaapi chromium no video hardware decoding
Sorry I did not make clear describe the problem. (I thought the previous
version is working, so the current is a small problem.)
I am using ubuntu-frame to make Wayland test:
https://github.com/MirServer/ubuntu-frame
If the ubnutu-frame is started, the Wayland display is ready. So I just
used native chromium and snap version chromium to confirm the display
result.
--
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/1816497
Title:
[snap] vaapi chromium no video hardware decoding
Status in chromium-browser package in Ubuntu:
In Progress
Bug description:
To test the snap with VA-API changes,
1. Install the Chromium snap,
sudo snap install --channel candidate/hwacc chromium
2. If on Xorg (`echo $WAYLAND_DISPLAY` is empty),
snap run chromium --disable-features=UseChromeOSDirectVideoDecoder
--enable-features=VaapiVideoDecoder
If on Wayland (`echo $WAYLAND_DISPLAY` is not empty),
chromium --enable-features=VaapiVideoDecoder --disable-
features=UseChromeOSDirectVideoDecoder --ozone-platform=wayland
3. Open a video, e.g. one from https://github.com/chthomos/video-
media-samples
4. Enter about:media-internals in the address bar and note what the
page says for kVideoDecoderName.
Please report
- The value for kVideoDecoderName from step 4. Success is typically
{Vaapi,VDA,Mojo}VideoDecoder while failure is {FFMpeg,Vpx}VideoDecoder;
- If failed, the video used for testing, including codec and resolution if
possible;
- Xorg or Wayland (`echo $WAYLAND_DISPLAY`);
- Distro version (`grep VERSION= /etc/os_release`);
- GPU (`lscpu`);
- CPU generation (`lscpu`).
About the last point, it may be that unfortunately only those with
newer generations of Intel CPUs will have luck with this, but it's
still an uncertainty. So reports are highly welcome.
--Original Bug report -
Libva is no longer working for snap installed chromium 72.0.3626.109
(Official Build) snap (64-bit)
I followed this instruction
sudo snap install --channel=candidate/vaapi chromium
My amdgpu can use libva
`vainfo: Driver version: Mesa Gallium driver 18.3.3 for AMD STONEY (DRM
3.27.0, 4.20.0-10.1-liquorix-amd64, LLVM 7.0.1)
vainfo: Supported profile and entrypoints
VAProfileMPEG2Simple: VAEntrypointVLD
VAProfileMPEG2Main : VAEntrypointVLD
VAProfileVC1Simple : VAEntrypointVLD
VAProfileVC1Main: VAEntrypointVLD
VAProfileVC1Advanced: VAEntrypointVLD
VAProfileH264ConstrainedBaseline: VAEntrypointVLD
VAProfileH264ConstrainedBaseline: VAEntrypointEncSlice
VAProfileH264Main : VAEntrypointVLD
VAProfileH264Main : VAEntrypointEncSlice
VAProfileH264High : VAEntrypointVLD
VAProfileH264High : VAEntrypointEncSlice
VAProfileHEVCMain : VAEntrypointVLD
VAProfileHEVCMain10 : VAEntrypointVLD
VAProfileJPEGBaseline : VAEntrypointVLD
VAProfileNone : VAEntrypointVideoProc`
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1816497/+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 1816497] Re: [snap] vaapi chromium no video hardware decoding
I already setup WAYLAND_DISPLAY=wayland-99. I setup a wayland display.
I confirmed the native chromium-browser did work with --enable-
features=VaapiVideoDecoder --disable-
features=UseChromeOSDirectVideoDecoder --ozone-platform=wayland. The
WAYLAND_DISPLAY will displayed chromium browser.
The only problem is using snap chromium. So I made a report this time.
--
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/1816497
Title:
[snap] vaapi chromium no video hardware decoding
Status in chromium-browser package in Ubuntu:
In Progress
Bug description:
To test the snap with VA-API changes,
1. Install the Chromium snap,
sudo snap install --channel candidate/hwacc chromium
2. If on Xorg (`echo $WAYLAND_DISPLAY` is empty),
snap run chromium --disable-features=UseChromeOSDirectVideoDecoder
--enable-features=VaapiVideoDecoder
If on Wayland (`echo $WAYLAND_DISPLAY` is not empty),
chromium --enable-features=VaapiVideoDecoder --disable-
features=UseChromeOSDirectVideoDecoder --ozone-platform=wayland
3. Open a video, e.g. one from https://github.com/chthomos/video-
media-samples
4. Enter about:media-internals in the address bar and note what the
page says for kVideoDecoderName.
Please report
- The value for kVideoDecoderName from step 4. Success is typically
{Vaapi,VDA,Mojo}VideoDecoder while failure is {FFMpeg,Vpx}VideoDecoder;
- If failed, the video used for testing, including codec and resolution if
possible;
- Xorg or Wayland (`echo $WAYLAND_DISPLAY`);
- Distro version (`grep VERSION= /etc/os_release`);
- GPU (`lscpu`);
- CPU generation (`lscpu`).
About the last point, it may be that unfortunately only those with
newer generations of Intel CPUs will have luck with this, but it's
still an uncertainty. So reports are highly welcome.
--Original Bug report -
Libva is no longer working for snap installed chromium 72.0.3626.109
(Official Build) snap (64-bit)
I followed this instruction
sudo snap install --channel=candidate/vaapi chromium
My amdgpu can use libva
`vainfo: Driver version: Mesa Gallium driver 18.3.3 for AMD STONEY (DRM
3.27.0, 4.20.0-10.1-liquorix-amd64, LLVM 7.0.1)
vainfo: Supported profile and entrypoints
VAProfileMPEG2Simple: VAEntrypointVLD
VAProfileMPEG2Main : VAEntrypointVLD
VAProfileVC1Simple : VAEntrypointVLD
VAProfileVC1Main: VAEntrypointVLD
VAProfileVC1Advanced: VAEntrypointVLD
VAProfileH264ConstrainedBaseline: VAEntrypointVLD
VAProfileH264ConstrainedBaseline: VAEntrypointEncSlice
VAProfileH264Main : VAEntrypointVLD
VAProfileH264Main : VAEntrypointEncSlice
VAProfileH264High : VAEntrypointVLD
VAProfileH264High : VAEntrypointEncSlice
VAProfileHEVCMain : VAEntrypointVLD
VAProfileHEVCMain10 : VAEntrypointVLD
VAProfileJPEGBaseline : VAEntrypointVLD
VAProfileNone : VAEntrypointVideoProc`
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1816497/+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 1816497] Re: [snap] vaapi chromium no video hardware decoding
does wayland mode conflict with vaapivdideodecoder feature ?
I know in the 22.04 version the default GUI mode is Wayland.
--
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/1816497
Title:
[snap] vaapi chromium no video hardware decoding
Status in chromium-browser package in Ubuntu:
In Progress
Bug description:
To test the snap with VA-API changes,
1. Install the Chromium snap,
sudo snap install --channel candidate/hwacc chromium
2. snap run chromium --disable-features=UseChromeOSDirectVideoDecoder
--enable-features=VaapiVideoDecoder
3. Open a video, e.g. one from https://github.com/chthomos/video-
media-samples
4. Enter about:media-internals in the address bar and note what the
page says for kVideoDecoderName.
Please report
- The value for kVideoDecoderName from step 4. Success is typically
{Vaapi,VDA,Mojo}VideoDecoder while failure is {FFMpeg,Vpx}VideoDecoder;
- If failed, the video used for testing, including codec and resolution if
possible;
- Xorg or Wayland (`echo $WAYLAND_DISPLAY`);
- Distro version (`grep VERSION= /etc/os_release`);
- GPU (`lscpu`);
- CPU generation (`lscpu`).
About the last point, it may be that unfortunately only those with
newer generations of Intel CPUs will have luck with this, but it's
still an uncertainty. So reports are highly welcome.
--Original Bug report -
Libva is no longer working for snap installed chromium 72.0.3626.109
(Official Build) snap (64-bit)
I followed this instruction
sudo snap install --channel=candidate/vaapi chromium
My amdgpu can use libva
`vainfo: Driver version: Mesa Gallium driver 18.3.3 for AMD STONEY (DRM
3.27.0, 4.20.0-10.1-liquorix-amd64, LLVM 7.0.1)
vainfo: Supported profile and entrypoints
VAProfileMPEG2Simple: VAEntrypointVLD
VAProfileMPEG2Main : VAEntrypointVLD
VAProfileVC1Simple : VAEntrypointVLD
VAProfileVC1Main: VAEntrypointVLD
VAProfileVC1Advanced: VAEntrypointVLD
VAProfileH264ConstrainedBaseline: VAEntrypointVLD
VAProfileH264ConstrainedBaseline: VAEntrypointEncSlice
VAProfileH264Main : VAEntrypointVLD
VAProfileH264Main : VAEntrypointEncSlice
VAProfileH264High : VAEntrypointVLD
VAProfileH264High : VAEntrypointEncSlice
VAProfileHEVCMain : VAEntrypointVLD
VAProfileHEVCMain10 : VAEntrypointVLD
VAProfileJPEGBaseline : VAEntrypointVLD
VAProfileNone : VAEntrypointVideoProc`
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1816497/+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 1816497] Re: [snap] vaapi chromium no video hardware decoding
I remember in previouse snap it is working, but withtout
vaapivideodecoder working. It is another problem, but the wayland is
sure working.
--
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/1816497
Title:
[snap] vaapi chromium no video hardware decoding
Status in chromium-browser package in Ubuntu:
In Progress
Bug description:
To test the snap with VA-API changes,
1. Install the Chromium snap,
sudo snap install --channel candidate/hwacc chromium
2. snap run chromium --disable-features=UseChromeOSDirectVideoDecoder
--enable-features=VaapiVideoDecoder
3. Open a video, e.g. one from https://github.com/chthomos/video-
media-samples
4. Enter about:media-internals in the address bar and note what the
page says for kVideoDecoderName.
Please report
- The value for kVideoDecoderName from step 4. Success is typically
{Vaapi,VDA,Mojo}VideoDecoder while failure is {FFMpeg,Vpx}VideoDecoder;
- If failed, the video used for testing, including codec and resolution if
possible;
- Xorg or Wayland (`echo $WAYLAND_DISPLAY`);
- Distro version (`grep VERSION= /etc/os_release`);
- GPU (`lscpu`);
- CPU generation (`lscpu`).
About the last point, it may be that unfortunately only those with
newer generations of Intel CPUs will have luck with this, but it's
still an uncertainty. So reports are highly welcome.
--Original Bug report -
Libva is no longer working for snap installed chromium 72.0.3626.109
(Official Build) snap (64-bit)
I followed this instruction
sudo snap install --channel=candidate/vaapi chromium
My amdgpu can use libva
`vainfo: Driver version: Mesa Gallium driver 18.3.3 for AMD STONEY (DRM
3.27.0, 4.20.0-10.1-liquorix-amd64, LLVM 7.0.1)
vainfo: Supported profile and entrypoints
VAProfileMPEG2Simple: VAEntrypointVLD
VAProfileMPEG2Main : VAEntrypointVLD
VAProfileVC1Simple : VAEntrypointVLD
VAProfileVC1Main: VAEntrypointVLD
VAProfileVC1Advanced: VAEntrypointVLD
VAProfileH264ConstrainedBaseline: VAEntrypointVLD
VAProfileH264ConstrainedBaseline: VAEntrypointEncSlice
VAProfileH264Main : VAEntrypointVLD
VAProfileH264Main : VAEntrypointEncSlice
VAProfileH264High : VAEntrypointVLD
VAProfileH264High : VAEntrypointEncSlice
VAProfileHEVCMain : VAEntrypointVLD
VAProfileHEVCMain10 : VAEntrypointVLD
VAProfileJPEGBaseline : VAEntrypointVLD
VAProfileNone : VAEntrypointVideoProc`
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1816497/+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 1816497] Re: [snap] vaapi chromium no video hardware decoding
sure, I already enable wayland.
chromium --enable-features=VaapiVideoDecoder
--disable-features=UseChromeOSDirectVideoDecoder --ozone-platform=wayland
[14225:14225:0807/073546.382350:ERROR:wayland_connection.cc(210)] Failed to
connect to Wayland display
[14225:14225:0807/073546.382387:ERROR:ozone_platform_wayland.cc(226)] Failed to
initialize Wayland platform
[14225:14225:0807/073546.382398:ERROR:env.cc(226)] The platform failed to
initialize. Exiting.
--
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/1816497
Title:
[snap] vaapi chromium no video hardware decoding
Status in chromium-browser package in Ubuntu:
In Progress
Bug description:
To test the snap with VA-API changes,
1. Install the Chromium snap,
sudo snap install --channel candidate/hwacc chromium
2. snap run chromium --disable-features=UseChromeOSDirectVideoDecoder
--enable-features=VaapiVideoDecoder
3. Open a video, e.g. one from https://github.com/chthomos/video-
media-samples
4. Enter about:media-internals in the address bar and note what the
page says for kVideoDecoderName.
Please report
- The value for kVideoDecoderName from step 4. Success is typically
{Vaapi,VDA,Mojo}VideoDecoder while failure is {FFMpeg,Vpx}VideoDecoder;
- If failed, the video used for testing, including codec and resolution if
possible;
- Xorg or Wayland (`echo $WAYLAND_DISPLAY`);
- Distro version (`grep VERSION= /etc/os_release`);
- GPU (`lscpu`);
- CPU generation (`lscpu`).
About the last point, it may be that unfortunately only those with
newer generations of Intel CPUs will have luck with this, but it's
still an uncertainty. So reports are highly welcome.
--Original Bug report -
Libva is no longer working for snap installed chromium 72.0.3626.109
(Official Build) snap (64-bit)
I followed this instruction
sudo snap install --channel=candidate/vaapi chromium
My amdgpu can use libva
`vainfo: Driver version: Mesa Gallium driver 18.3.3 for AMD STONEY (DRM
3.27.0, 4.20.0-10.1-liquorix-amd64, LLVM 7.0.1)
vainfo: Supported profile and entrypoints
VAProfileMPEG2Simple: VAEntrypointVLD
VAProfileMPEG2Main : VAEntrypointVLD
VAProfileVC1Simple : VAEntrypointVLD
VAProfileVC1Main: VAEntrypointVLD
VAProfileVC1Advanced: VAEntrypointVLD
VAProfileH264ConstrainedBaseline: VAEntrypointVLD
VAProfileH264ConstrainedBaseline: VAEntrypointEncSlice
VAProfileH264Main : VAEntrypointVLD
VAProfileH264Main : VAEntrypointEncSlice
VAProfileH264High : VAEntrypointVLD
VAProfileH264High : VAEntrypointEncSlice
VAProfileHEVCMain : VAEntrypointVLD
VAProfileHEVCMain10 : VAEntrypointVLD
VAProfileJPEGBaseline : VAEntrypointVLD
VAProfileNone : VAEntrypointVideoProc`
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1816497/+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 1816497] Re: [snap] vaapi chromium no video hardware decoding
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1897454
chrome://flags/#ozone-platform-hint , not work.
[30855:30855:0806/092525.830999:ERROR:wayland_connection.cc(210)] Failed to
connect to Wayland display
[30855:30855:0806/092525.831041:ERROR:ozone_platform_wayland.cc(226)] Failed to
initialize Wayland platform
[30855:30855:0806/092525.831051:ERROR:env.cc(226)] The platform failed to
initialize. Exiting.
--
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/1816497
Title:
[snap] vaapi chromium no video hardware decoding
Status in chromium-browser package in Ubuntu:
In Progress
Bug description:
To test the snap with VA-API changes,
0. If you have Nvidia GPU, you need Snapcraft >=7.1.1. Check `snap
info snapcraft`. At the time of writing,
sudo snap refresh --channel 7.x snapcraft
1. Install the Chromium snap,
sudo snap install --channel candidate/hwacc chromium
2. snap run chromium --disable-features=UseChromeOSDirectVideoDecoder
--enable-features=VaapiVideoDecoder
3. Open a video, e.g. one from https://github.com/chthomos/video-
media-samples
4. Enter about:media-internals in the address bar and note what the
page says for kVideoDecoderName.
Please report
- The value for kVideoDecoderName from step 4. Success is typically
{Vaapi,VDA,Mojo}VideoDecoder while failure is {FFMpeg,Vpx}VideoDecoder;
- If failed, the video used for testing, including codec and resolution if
possible;
- Xorg or Wayland (`echo $WAYLAND_DISPLAY`);
- Distro version (`grep VERSION= /etc/os_release`);
- GPU (`lscpu`);
- CPU generation (`lscpu`).
About the last point, it may be that unfortunately only those with
newer generations of Intel CPUs will have luck with this, but it's
still an uncertainty. So reports are highly welcome.
--Original Bug report -
Libva is no longer working for snap installed chromium 72.0.3626.109
(Official Build) snap (64-bit)
I followed this instruction
sudo snap install --channel=candidate/vaapi chromium
My amdgpu can use libva
`vainfo: Driver version: Mesa Gallium driver 18.3.3 for AMD STONEY (DRM
3.27.0, 4.20.0-10.1-liquorix-amd64, LLVM 7.0.1)
vainfo: Supported profile and entrypoints
VAProfileMPEG2Simple: VAEntrypointVLD
VAProfileMPEG2Main : VAEntrypointVLD
VAProfileVC1Simple : VAEntrypointVLD
VAProfileVC1Main: VAEntrypointVLD
VAProfileVC1Advanced: VAEntrypointVLD
VAProfileH264ConstrainedBaseline: VAEntrypointVLD
VAProfileH264ConstrainedBaseline: VAEntrypointEncSlice
VAProfileH264Main : VAEntrypointVLD
VAProfileH264Main : VAEntrypointEncSlice
VAProfileH264High : VAEntrypointVLD
VAProfileH264High : VAEntrypointEncSlice
VAProfileHEVCMain : VAEntrypointVLD
VAProfileHEVCMain10 : VAEntrypointVLD
VAProfileJPEGBaseline : VAEntrypointVLD
VAProfileNone : VAEntrypointVideoProc`
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1816497/+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 1816497] Re: [snap] vaapi chromium no video hardware decoding
Wao, perfecter build.
It is the first time my Nvidia/intel CPU, get a snap chromium support
video decoder.
I need not manually maintain my native chromium environment.
Thanks for your hardwarking.
--
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/1816497
Title:
[snap] vaapi chromium no video hardware decoding
Status in chromium-browser package in Ubuntu:
In Progress
Bug description:
To test the snap with VA-API changes,
0. If you have Nvidia GPU, you need Snapcraft >=7.1.1. Check `snap
info snapcraft`. At the time of writing,
sudo snap refresh --channel 7.x snapcraft
1. Install the Chromium snap,
sudo snap install --channel candidate/hwacc chromium
2. snap run chromium --disable-features=UseChromeOSDirectVideoDecoder
--enable-features=VaapiVideoDecoder
3. Open a video, e.g. one from https://github.com/chthomos/video-
media-samples
4. Enter about:media-internals in the address bar and note what the
page says for kVideoDecoderName.
Please report
- The value for kVideoDecoderName from step 4. Success is typically
{Vaapi,VDA,Mojo}VideoDecoder while failure is {FFMpeg,Vpx}VideoDecoder;
- If failed, the video used for testing, including codec and resolution if
possible;
- Xorg or Wayland (`echo $WAYLAND_DISPLAY`);
- Distro version (`grep VERSION= /etc/os_release`);
- GPU (`lscpu`);
- CPU generation (`lscpu`).
About the last point, it may be that unfortunately only those with
newer generations of Intel CPUs will have luck with this, but it's
still an uncertainty. So reports are highly welcome.
--Original Bug report -
Libva is no longer working for snap installed chromium 72.0.3626.109
(Official Build) snap (64-bit)
I followed this instruction
sudo snap install --channel=candidate/vaapi chromium
My amdgpu can use libva
`vainfo: Driver version: Mesa Gallium driver 18.3.3 for AMD STONEY (DRM
3.27.0, 4.20.0-10.1-liquorix-amd64, LLVM 7.0.1)
vainfo: Supported profile and entrypoints
VAProfileMPEG2Simple: VAEntrypointVLD
VAProfileMPEG2Main : VAEntrypointVLD
VAProfileVC1Simple : VAEntrypointVLD
VAProfileVC1Main: VAEntrypointVLD
VAProfileVC1Advanced: VAEntrypointVLD
VAProfileH264ConstrainedBaseline: VAEntrypointVLD
VAProfileH264ConstrainedBaseline: VAEntrypointEncSlice
VAProfileH264Main : VAEntrypointVLD
VAProfileH264Main : VAEntrypointEncSlice
VAProfileH264High : VAEntrypointVLD
VAProfileH264High : VAEntrypointEncSlice
VAProfileHEVCMain : VAEntrypointVLD
VAProfileHEVCMain10 : VAEntrypointVLD
VAProfileJPEGBaseline : VAEntrypointVLD
VAProfileNone : VAEntrypointVideoProc`
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1816497/+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 1816497] Re: [snap] vaapi chromium no video hardware decoding
##
snap info chromium
name: chromium
summary: Chromium web browser, open-source version of Chrome
publisher: Canonical✓
store-url: https://snapcraft.io/chromium
contact:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bugs?field.tag=snap
license: unset
description: |
An open-source browser project that aims to build a safer, faster, and more
stable way for all Internet users to experience the web.
commands:
- chromium.chromedriver
- chromium
snap-id: XKEcBqPM06H1Z7zGOdG5fbICuf8NWK5R
tracking: latest/candidate/hwacc
refresh-date: today at 18:55 CST
channels:
latest/stable:104.0.5112.79 2022-08-03 (2051) 148MB -
latest/candidate: 104.0.5112.79 2022-08-03 (2051) 148MB -
latest/beta: 104.0.5112.79 2022-08-02 (2051) 148MB -
latest/edge: 105.0.5195.19 2022-08-04 (2052) 148MB -
###
snap run --shell chromium
env | grep LIBVA
LIBVA_DRIVER_NAME=iHD
vainfo
bash: vainfo: command not found <<== ???
--
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/1816497
Title:
[snap] vaapi chromium no video hardware decoding
Status in chromium-browser package in Ubuntu:
In Progress
Bug description:
To test the snap with VA-API changes,
0. If you have Nvidia GPU, you need Snapcraft >=7.1.1. Check `snap
info snapcraft`. At the time of writing,
sudo snap refresh --channel 7.x snapcraft
1. Install the Chromium snap,
sudo snap install --channel candidate/hwacc chromium
2. snap run chromium --disable-features=UseChromeOSDirectVideoDecoder
--enable-features=VaapiVideoDecoder
3. Open a video, e.g. one from https://github.com/chthomos/video-
media-samples
4. Enter about:media-internals in the address bar and note what the
page says for kVideoDecoderName.
Please report
- The value for kVideoDecoderName from step 4. Success is typically
{Vaapi,VDA,Mojo}VideoDecoder while failure is {FFMpeg,Vpx}VideoDecoder;
- If failed, the video used for testing, including codec and resolution if
possible;
- Xorg or Wayland (`echo $WAYLAND_DISPLAY`);
- Distro version (`grep VERSION= /etc/os_release`);
- GPU (`lscpu`);
- CPU generation (`lscpu`).
About the last point, it may be that unfortunately only those with
newer generations of Intel CPUs will have luck with this, but it's
still an uncertainty. So reports are highly welcome.
--Original Bug report -
Libva is no longer working for snap installed chromium 72.0.3626.109
(Official Build) snap (64-bit)
I followed this instruction
sudo snap install --channel=candidate/vaapi chromium
My amdgpu can use libva
`vainfo: Driver version: Mesa Gallium driver 18.3.3 for AMD STONEY (DRM
3.27.0, 4.20.0-10.1-liquorix-amd64, LLVM 7.0.1)
vainfo: Supported profile and entrypoints
VAProfileMPEG2Simple: VAEntrypointVLD
VAProfileMPEG2Main : VAEntrypointVLD
VAProfileVC1Simple : VAEntrypointVLD
VAProfileVC1Main: VAEntrypointVLD
VAProfileVC1Advanced: VAEntrypointVLD
VAProfileH264ConstrainedBaseline: VAEntrypointVLD
VAProfileH264ConstrainedBaseline: VAEntrypointEncSlice
VAProfileH264Main : VAEntrypointVLD
VAProfileH264Main : VAEntrypointEncSlice
VAProfileH264High : VAEntrypointVLD
VAProfileH264High : VAEntrypointEncSlice
VAProfileHEVCMain : VAEntrypointVLD
VAProfileHEVCMain10 : VAEntrypointVLD
VAProfileJPEGBaseline : VAEntrypointVLD
VAProfileNone : VAEntrypointVideoProc`
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1816497/+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 1816497] Re: [snap] vaapi chromium no video hardware decoding
My t460p, Nvida, Intel GPU. Insalled with
sudo snap install --channel candidate/hwacc chromium
LIBVA_MESSAGING_LEVEL=2 chromium
--disable-features=UseChromeOSDirectVideoDecoder
--enable-features=VaapiVideoDecoder
```
Gtk-Message: 19:02:47.866: Failed to load module "canberra-gtk-module"
Gtk-Message: 19:02:47.868: Failed to load module "canberra-gtk-module"
WARNING: Kernel has no file descriptor comparison support: Operation not
permitted
[21291:21389:0805/190251.215417:ERROR:udev_watcher.cc(98)] Failed to begin udev
enumeration.
Warning: vkCreateInstance: Found no drivers!
Error: vkCreateInstance failed with VK_ERROR_INCOMPATIBLE_DRIVER
at CheckVkSuccessImpl
(../../third_party/dawn/src/dawn/native/vulkan/VulkanError.cpp:88)
at CreateVkInstance
(../../third_party/dawn/src/dawn/native/vulkan/BackendVk.cpp:383)
at Initialize
(../../third_party/dawn/src/dawn/native/vulkan/BackendVk.cpp:269)
at Create (../../third_party/dawn/src/dawn/native/vulkan/BackendVk.cpp:199)
at operator()
(../../third_party/dawn/src/dawn/native/vulkan/BackendVk.cpp:458)
```
There is no libva loading information. There is no video decoder. The
version is not work in my hardware.
--
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/1816497
Title:
[snap] vaapi chromium no video hardware decoding
Status in chromium-browser package in Ubuntu:
In Progress
Bug description:
To test the snap with VA-API changes,
0. If you have Nvidia GPU, you need Snapcraft >=7.1.1. Check `snap
info snapcraft`. At the time of writing,
sudo snap refresh --channel 7.x snapcraft
1. Install the Chromium snap,
sudo snap install --channel candidate/hwacc chromium
2. snap run chromium --disable-features=UseChromeOSDirectVideoDecoder
--enable-features=VaapiVideoDecoder
3. Open a video, e.g. one from https://github.com/chthomos/video-
media-samples
4. Enter about:media-internals in the address bar and note what the
page says for kVideoDecoderName.
Please report
- The value for kVideoDecoderName from step 4. Success is typically
{Vaapi,VDA,Mojo}VideoDecoder while failure is {FFMpeg,Vpx}VideoDecoder;
- If failed, the video used for testing, including codec and resolution if
possible;
- Xorg or Wayland (`echo $WAYLAND_DISPLAY`);
- Distro version (`grep VERSION= /etc/os_release`);
- GPU (`lscpu`);
- CPU generation (`lscpu`).
About the last point, it may be that unfortunately only those with
newer generations of Intel CPUs will have luck with this, but it's
still an uncertainty. So reports are highly welcome.
--Original Bug report -
Libva is no longer working for snap installed chromium 72.0.3626.109
(Official Build) snap (64-bit)
I followed this instruction
sudo snap install --channel=candidate/vaapi chromium
My amdgpu can use libva
`vainfo: Driver version: Mesa Gallium driver 18.3.3 for AMD STONEY (DRM
3.27.0, 4.20.0-10.1-liquorix-amd64, LLVM 7.0.1)
vainfo: Supported profile and entrypoints
VAProfileMPEG2Simple: VAEntrypointVLD
VAProfileMPEG2Main : VAEntrypointVLD
VAProfileVC1Simple : VAEntrypointVLD
VAProfileVC1Main: VAEntrypointVLD
VAProfileVC1Advanced: VAEntrypointVLD
VAProfileH264ConstrainedBaseline: VAEntrypointVLD
VAProfileH264ConstrainedBaseline: VAEntrypointEncSlice
VAProfileH264Main : VAEntrypointVLD
VAProfileH264Main : VAEntrypointEncSlice
VAProfileH264High : VAEntrypointVLD
VAProfileH264High : VAEntrypointEncSlice
VAProfileHEVCMain : VAEntrypointVLD
VAProfileHEVCMain10 : VAEntrypointVLD
VAProfileJPEGBaseline : VAEntrypointVLD
VAProfileNone : VAEntrypointVideoProc`
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1816497/+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 1982472] [NEW] Support A+N platform
Public bug reported: The 'Power Saving Mode' of Nvidia app should change to ATI when the integrated graphic is Advanced Micro Devices. [Steps to reproduce] 1. Install the OEM image 2. Boot and log 3. 'Dash' -> 'Nvidia Settings' 4. Verify the 'PRIME Profiles' [Expected result] Nvidia (Performance Mode) Nvidia On-Demand AMD (Power Saving Mode) u@Thor-P3-AMD-2:~$ prime-select Usage: /usr/bin/prime-select nvidia|AMD|on-demand|query [Actual result] Nvidia (Performance Mode) Nvidia On-Demand Intel (Power Saving Mode) u@Thor-P3-AMD-2:~$ prime-select Usage: /usr/bin/prime-select nvidia|intel|on-demand|query [Failure rate] 100% [Other Information] ubuntu 22.04 nvidia-prime 0.8.17.1 nvidia-settings 510.47.03-0ubuntu1 nvidia-driver 510.73.05-0ubuntu0.22.04.1 ** Affects: oem-priority Importance: Undecided Status: New ** Affects: nvidia-prime (Ubuntu) Importance: Undecided Status: New ** Tags: oem-priority originate-from-1981179 sutton ** Tags added: oem-priority originate-from-1981179 sutton -- 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/1982472 Title: Support A+N platform Status in OEM Priority Project: New Status in nvidia-prime package in Ubuntu: New Bug description: The 'Power Saving Mode' of Nvidia app should change to ATI when the integrated graphic is Advanced Micro Devices. [Steps to reproduce] 1. Install the OEM image 2. Boot and log 3. 'Dash' -> 'Nvidia Settings' 4. Verify the 'PRIME Profiles' [Expected result] Nvidia (Performance Mode) Nvidia On-Demand AMD (Power Saving Mode) u@Thor-P3-AMD-2:~$ prime-select Usage: /usr/bin/prime-select nvidia|AMD|on-demand|query [Actual result] Nvidia (Performance Mode) Nvidia On-Demand Intel (Power Saving Mode) u@Thor-P3-AMD-2:~$ prime-select Usage: /usr/bin/prime-select nvidia|intel|on-demand|query [Failure rate] 100% [Other Information] ubuntu 22.04 nvidia-prime 0.8.17.1 nvidia-settings 510.47.03-0ubuntu1 nvidia-driver 510.73.05-0ubuntu0.22.04.1 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1982472/+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 1816497] Re: [snap] vaapi chromium no video hardware decoding
Is it possible to add chromium-wayland-vaapi driver in the snap. Check
whether wayland mode works.
--
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/1816497
Title:
[snap] vaapi chromium no video hardware decoding
Status in chromium-browser package in Ubuntu:
In Progress
Bug description:
To test the snap with VA-API changes,
1. Install the snap with
sudo snap install --channel candidate/hwacc chromium
2. snap run chromium --disable-features=UseChromeOSDirectVideoDecoder
--enable-features=VaapiVideoDecoder
3. Open a video, e.g. one from https://github.com/chthomos/video-
media-samples
4. Enter about:media-internals in the address bar and note what the
page says for kVideoDecoderName.
Please report
- The value for kVideoDecoderName from step 4. Success is typically
{Vaapi,VDA,Mojo}VideoDecoder while failure is {FFMpeg,Vpx}VideoDecoder;
- If failed, the video used for testing, including codec and resolution if
possible;
- Distro version (if in doubt, `grep VERSION= /etc/os_release`);
- GPU (if in doubt, attach the output of `lscpu`);
- CPU generation (if in doubt, attach the output of `lscpu`).
About the last point, it may be that unfortunately only those with
newer generations of Intel CPUs will have luck with this, but it's
still an uncertainty. So reports are highly welcome.
--Original Bug report -
Libva is no longer working for snap installed chromium 72.0.3626.109
(Official Build) snap (64-bit)
I followed this instruction
sudo snap install --channel=candidate/vaapi chromium
My amdgpu can use libva
`vainfo: Driver version: Mesa Gallium driver 18.3.3 for AMD STONEY (DRM
3.27.0, 4.20.0-10.1-liquorix-amd64, LLVM 7.0.1)
vainfo: Supported profile and entrypoints
VAProfileMPEG2Simple: VAEntrypointVLD
VAProfileMPEG2Main : VAEntrypointVLD
VAProfileVC1Simple : VAEntrypointVLD
VAProfileVC1Main: VAEntrypointVLD
VAProfileVC1Advanced: VAEntrypointVLD
VAProfileH264ConstrainedBaseline: VAEntrypointVLD
VAProfileH264ConstrainedBaseline: VAEntrypointEncSlice
VAProfileH264Main : VAEntrypointVLD
VAProfileH264Main : VAEntrypointEncSlice
VAProfileH264High : VAEntrypointVLD
VAProfileH264High : VAEntrypointEncSlice
VAProfileHEVCMain : VAEntrypointVLD
VAProfileHEVCMain10 : VAEntrypointVLD
VAProfileJPEGBaseline : VAEntrypointVLD
VAProfileNone : VAEntrypointVideoProc`
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1816497/+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 1816497] Re: [snap] vaapi chromium no video hardware decoding
I tried this https://launchpad.net/~nteodosio/+snap/chromium-browser-
hwacc/+build/1821034
Good snap package, my old N3450 works.
##
Gtk-Message: 17:56:38.503: Failed to load module "canberra-gtk-module"
Gtk-Message: 17:56:38.507: Failed to load module "canberra-gtk-module"
[16395:16490:0715/175638.574596:ERROR:object_proxy.cc(623)] Failed to call
method: org.freedesktop.DBus.ListActivatableNames: object_path=
/org/freedesktop/DBus: org.freedesktop.DBus.Error.AccessDenied: An AppArmor
policy prevents this sender from sending this message to this recipient;
type="method_call", sender=":1.188" (uid=1000 pid=16395
comm="/snap/chromium/x1/usr/lib/chromium-browser/chrome "
label="snap.chromium.chromium (enforce)") interface="org.freedesktop.DBus"
member="ListActivatableNames" error name="(unset)" requested_reply="0"
destination="org.freedesktop.DBus" (bus)
[16395:16395:0715/175638.601987:WARNING:account_consistency_mode_manager.cc(70)]
Desktop Identity Consistency cannot be enabled as no OAuth client ID and
client secret have been configured.
libva info: VA-API version 1.14.0
libva info: Trying to open
/snap/chromium/x1/usr/lib/x86_64-linux-gnu/dri//iHD_drv_video.so
libva info: Found init function __vaDriverInit_1_14
libva info: va_openDriver() returns 0
[16503:16503:0715/175638.861107:WARNING:sandbox_linux.cc(376)]
InitializeSandbox() called with multiple threads in process gpu-process.
WARNING: Kernel has no file descriptor comparison support: Operation not
permitted
[16395:16395:0715/175639.046619:WARNING:bluez_dbus_manager.cc(247)] Floss
manager not present, cannot set Floss enable/disable.
[16503:16503:0715/175639.744267:WARNING:angle_platform_impl.cc(48)]
MemoryProgramCache.cpp:174 (getProgram): Failed to load binary from cache.
[16503:16503:0715/175639.748909:WARNING:angle_platform_impl.cc(48)]
MemoryProgramCache.cpp:174 (getProgram): Failed to load binary from cache.
[16395:16484:0715/175642.349375:ERROR:udev_watcher.cc(98)] Failed to begin udev
enumeration.
^C[16395:16395:0715/175649.380723:INFO:render_frame_host_impl.cc(11505)]
RenderFrameHostImpl::MaybeGenerateCrashReport url = , status = 4, exit_code = 0
[16395:16395:0715/175649.541305:WARNING:pref_notifier_impl.cc(41)] Pref
observer for media_router.cast_allow_all_ips found at shutdown.
###
My T460P because of Nvida CPU, does not work, the same as before.
Thank you for help. I at least do not need take time on the old PC.
Install and works, that is what I wanted.
--
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/1816497
Title:
[snap] vaapi chromium no video hardware decoding
Status in chromium-browser package in Ubuntu:
In Progress
Bug description:
To test the snap with VA-API changes,
1. Install the snap with
sudo snap install --channel candidate/hwacc chromium
2. snap run chromium --disable-features=UseChromeOSDirectVideoDecoder
--enable-features=VaapiVideoDecoder
3. Open a video, e.g. one from https://github.com/chthomos/video-
media-samples
4. Enter about:media-internals in the address bar and note what the
page says for kVideoDecoderName.
Please report
- The value for kVideoDecoderName from step 4. Success is typically
{Vaapi,VDA,Mojo}VideoDecoder while failure is {FFMpeg,Vpx}VideoDecoder;
- If failed, the video used for testing, including codec and resolution if
possible;
- Distro version (if in doubt, `grep VERSION= /etc/os_release`);
- GPU (if in doubt, attach the output of `lscpu`);
- CPU generation (if in doubt, attach the output of `lscpu`).
About the last point, it may be that unfortunately only those with
newer generations of Intel CPUs will have luck with this, but it's
still an uncertainty. So reports are highly welcome.
--Original Bug report -
Libva is no longer working for snap installed chromium 72.0.3626.109
(Official Build) snap (64-bit)
I followed this instruction
sudo snap install --channel=candidate/vaapi chromium
My amdgpu can use libva
`vainfo: Driver version: Mesa Gallium driver 18.3.3 for AMD STONEY (DRM
3.27.0, 4.20.0-10.1-liquorix-amd64, LLVM 7.0.1)
vainfo: Supported profile and entrypoints
VAProfileMPEG2Simple: VAEntrypointVLD
VAProfileMPEG2Main : VAEntrypointVLD
VAProfileVC1Simple : VAEntrypointVLD
VAProfileVC1Main: VAEntrypointVLD
VAProfileVC1Advanced: VAEntrypointVLD
VAProfileH264ConstrainedBaseline: VAEntrypointVLD
VAProfileH264ConstrainedBaseline: VAEntrypointEncSlice
VAProfileH264Main : VAEntrypointVLD
VAProfileH264Main : VAEntrypointEncSlice
VAProfileH264High : VAEntrypointVLD
VAProfileH264High :
[Desktop-packages] [Bug 1816497] Re: [snap] vaapi chromium no video hardware decoding
Thank you for your clear response. It means chromium is bind the old
libva 2.6. It is a little strange.
Current both my two machines are unable to work with the good snap
package. But the native chromium version could. It is a little sad.
--
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/1816497
Title:
[snap] vaapi chromium no video hardware decoding
Status in chromium-browser package in Ubuntu:
In Progress
Bug description:
To test the snap with VA-API changes,
1. Install the snap with
sudo snap install --channel candidate/hwacc chromium
2. snap run chromium --disable-features=UseChromeOSDirectVideoDecoder
--enable-features=VaapiVideoDecoder
3. Open a video, e.g. one from https://github.com/chthomos/video-
media-samples
4. Enter about:media-internals in the address bar and note what the
page says for kVideoDecoderName.
Please report
- The value for kVideoDecoderName from step 4. Success is typically
{Vaapi,VDA,Mojo}VideoDecoder while failure is {FFMpeg,Vpx}VideoDecoder;
- If failed, the video used for testing, including codec and resolution if
possible;
- Distro version (if in doubt, `grep VERSION= /etc/os_release`);
- GPU (if in doubt, attach the output of `lscpu`);
- CPU generation (if in doubt, attach the output of `lscpu`).
About the last point, it may be that unfortunately only those with
newer generations of Intel CPUs will have luck with this, but it's
still an uncertainty. So reports are highly welcome.
--Original Bug report -
Libva is no longer working for snap installed chromium 72.0.3626.109
(Official Build) snap (64-bit)
I followed this instruction
sudo snap install --channel=candidate/vaapi chromium
My amdgpu can use libva
`vainfo: Driver version: Mesa Gallium driver 18.3.3 for AMD STONEY (DRM
3.27.0, 4.20.0-10.1-liquorix-amd64, LLVM 7.0.1)
vainfo: Supported profile and entrypoints
VAProfileMPEG2Simple: VAEntrypointVLD
VAProfileMPEG2Main : VAEntrypointVLD
VAProfileVC1Simple : VAEntrypointVLD
VAProfileVC1Main: VAEntrypointVLD
VAProfileVC1Advanced: VAEntrypointVLD
VAProfileH264ConstrainedBaseline: VAEntrypointVLD
VAProfileH264ConstrainedBaseline: VAEntrypointEncSlice
VAProfileH264Main : VAEntrypointVLD
VAProfileH264Main : VAEntrypointEncSlice
VAProfileH264High : VAEntrypointVLD
VAProfileH264High : VAEntrypointEncSlice
VAProfileHEVCMain : VAEntrypointVLD
VAProfileHEVCMain10 : VAEntrypointVLD
VAProfileJPEGBaseline : VAEntrypointVLD
VAProfileNone : VAEntrypointVideoProc`
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1816497/+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 1816497] Re: [snap] vaapi chromium no video hardware decoding
snap run --shell chromium
LIBVA_DRIVERS_PATH=/snap/chromium/current/usr/local/lib/x86_64-linux-gnu/dri
vainfo
libva info: VA-API version 1.14.0
libva info: User environment variable requested driver 'iHD'
libva info: Trying to open
/snap/chromium/current/usr/local/lib/x86_64-linux-gnu/dri/iHD_drv_video.so
libva info: va_openDriver() returns -1
vaInitialize failed with error code -1 (unknown libva error),exit
Where is 2.14 libva driver path？
--
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/1816497
Title:
[snap] vaapi chromium no video hardware decoding
Status in chromium-browser package in Ubuntu:
In Progress
Bug description:
To test the snap with VA-API changes,
1. Install the snap with
sudo snap install --channel candidate/hwacc chromium
2. snap run chromium --disable-features=UseChromeOSDirectVideoDecoder
--enable-features=VaapiVideoDecoder
3. Open a video, e.g. one from https://github.com/chthomos/video-
media-samples
4. Enter about:media-internals in the address bar and note what the
page says for kVideoDecoderName.
Please report
- The value for kVideoDecoderName from step 4. Success is typically
{Vaapi,VDA,Mojo}VideoDecoder while failure is {FFMpeg,Vpx}VideoDecoder;
- If failed, the video used for testing, including codec and resolution if
possible;
- Distro version (if in doubt, `grep VERSION= /etc/os_release`);
- GPU (if in doubt, attach the output of `lscpu`);
- CPU generation (if in doubt, attach the output of `lscpu`).
About the last point, it may be that unfortunately only those with
newer generations of Intel CPUs will have luck with this, but it's
still an uncertainty. So reports are highly welcome.
--Original Bug report -
Libva is no longer working for snap installed chromium 72.0.3626.109
(Official Build) snap (64-bit)
I followed this instruction
sudo snap install --channel=candidate/vaapi chromium
My amdgpu can use libva
`vainfo: Driver version: Mesa Gallium driver 18.3.3 for AMD STONEY (DRM
3.27.0, 4.20.0-10.1-liquorix-amd64, LLVM 7.0.1)
vainfo: Supported profile and entrypoints
VAProfileMPEG2Simple: VAEntrypointVLD
VAProfileMPEG2Main : VAEntrypointVLD
VAProfileVC1Simple : VAEntrypointVLD
VAProfileVC1Main: VAEntrypointVLD
VAProfileVC1Advanced: VAEntrypointVLD
VAProfileH264ConstrainedBaseline: VAEntrypointVLD
VAProfileH264ConstrainedBaseline: VAEntrypointEncSlice
VAProfileH264Main : VAEntrypointVLD
VAProfileH264Main : VAEntrypointEncSlice
VAProfileH264High : VAEntrypointVLD
VAProfileH264High : VAEntrypointEncSlice
VAProfileHEVCMain : VAEntrypointVLD
VAProfileHEVCMain10 : VAEntrypointVLD
VAProfileJPEGBaseline : VAEntrypointVLD
VAProfileNone : VAEntrypointVideoProc`
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1816497/+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 1816497] Re: [snap] vaapi chromium no video hardware decoding
I make the same test as #139
libva is back for normal usage
LIBVA_MESSAGING_LEVEL=2 snap run chromium --enable-features=VaapiVideoDecoder
Gtk-Message: 07:25:45.539: Failed to load module "canberra-gtk-module"
Gtk-Message: 07:25:45.542: Failed to load module "canberra-gtk-module"
libva info: VA-API version 1.14.0
libva info: User environment variable requested driver 'iHD'
libva info: Trying to open /usr/local/lib/dri/iHD_drv_video.so
libva info: va_openDriver() returns -1
WARNING: Kernel has no file descriptor comparison support: Operation not
permitted
[19720:19941:0714/072549.476876:ERROR:udev_watcher.cc(98)] Failed to begin udev
enumeration.
whatever I override LIBVA_DRIVERS_PATH, the result is not changed. It is
because my NVIDA card.
snap run --shell chromium
LIBVA_DRIVERS_PATH=/snap/chromium/current/usr/lib/x86_64-linux-gnu/dri/ vainfo
libva info: VA-API version 1.14.0
libva info: User environment variable requested driver 'iHD'
libva info: Trying to open
/snap/chromium/current/usr/lib/x86_64-linux-gnu/dri//iHD_drv_video.so
libva info: Found init function __vaDriverInit_1_14
libva info: va_openDriver() returns 0
vainfo: VA-API version: 1.14 (libva 2.6.0)
vainfo: Driver version: Intel iHD driver for Intel(R) Gen Graphics - 22.4.3
(bbbf2cd)
vainfo: Supported profile and entrypoints
VAProfileNone : VAEntrypointVideoProc
VAProfileNone : VAEntrypointStats
VAProfileMPEG2Simple: VAEntrypointVLD
VAProfileMPEG2Simple: VAEntrypointEncSlice
VAProfileMPEG2Main : VAEntrypointVLD
VAProfileMPEG2Main : VAEntrypointEncSlice
VAProfileH264Main : VAEntrypointVLD
VAProfileH264Main : VAEntrypointEncSlice
VAProfileH264Main : VAEntrypointFEI
VAProfileH264Main : VAEntrypointEncSliceLP
VAProfileH264High : VAEntrypointVLD
VAProfileH264High : VAEntrypointEncSlice
VAProfileH264High : VAEntrypointFEI
VAProfileH264High : VAEntrypointEncSliceLP
VAProfileVC1Simple : VAEntrypointVLD
VAProfileVC1Main: VAEntrypointVLD
VAProfileVC1Advanced: VAEntrypointVLD
VAProfileJPEGBaseline : VAEntrypointVLD
VAProfileJPEGBaseline : VAEntrypointEncPicture
VAProfileH264ConstrainedBaseline: VAEntrypointVLD
VAProfileH264ConstrainedBaseline: VAEntrypointEncSlice
VAProfileH264ConstrainedBaseline: VAEntrypointFEI
VAProfileH264ConstrainedBaseline: VAEntrypointEncSliceLP
VAProfileVP8Version0_3 : VAEntrypointVLD
VAProfileHEVCMain : VAEntrypointVLD
VAProfileHEVCMain : VAEntrypointEncSlice
VAProfileHEVCMain : VAEntrypointFEI
The libva is still using old libva 2.6 driver. (It is not expected
result)
--
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/1816497
Title:
[snap] vaapi chromium no video hardware decoding
Status in chromium-browser package in Ubuntu:
In Progress
Bug description:
To test the snap with VA-API changes,
1. Install the snap with
sudo snap install --channel candidate/hwacc chromium
2. snap run chromium --disable-features=UseChromeOSDirectVideoDecoder
--enable-features=VaapiVideoDecoder
3. Open a video, e.g. one from https://github.com/chthomos/video-
media-samples
4. Enter about:media-internals in the address bar and note what the
page says for kVideoDecoderName.
Please report
- The value for kVideoDecoderName from step 4. Success is typically
{Vaapi,VDA,Mojo}VideoDecoder while failure is {FFMpeg,Vpx}VideoDecoder;
- If failed, the video used for testing, including codec and resolution if
possible;
- Distro version (if in doubt, `grep VERSION= /etc/os_release`);
- GPU (if in doubt, attach the output of `lscpu`);
- CPU generation (if in doubt, attach the output of `lscpu`).
About the last point, it may be that unfortunately only those with
newer generations of Intel CPUs will have luck with this, but it's
still an uncertainty. So reports are highly welcome.
--Original Bug report -
Libva is no longer working for snap installed chromium 72.0.3626.109
(Official Build) snap (64-bit)
I followed this instruction
sudo snap install --channel=candidate/vaapi chromium
My amdgpu can use libva
`vainfo: Driver version: Mesa Gallium driver 18.3.3 for AMD STONEY (DRM
3.27.0, 4.20.0-10.1-liquorix-amd64, LLVM 7.0.1)
vainfo: Supported profile and entrypoints
VAProfileMPEG2Simple: VAEntrypointVLD
VAProfileMPEG2Main : VAEntrypointVLD
VAProfileVC1Simple : VAEntrypointVLD
VAProfileVC1Main
[Desktop-packages] [Bug 1816497] Re: [snap] vaapi chromium no video hardware decoding
>>It shouldn't matter where the libva is built, only where it is
installed, which is usr/lib/$ARCH_TRIPLET/.
What you said is correct. (I did not make a clear expression.)
In post #110
./autogen.sh --prefix=/usr <<== give the install path so driver
will search from this path.
I build libva in my notebook. if not using --prefix=/usr will cause
other library loading problem.
Use this prefix will solve uncertainty.
It is just keep the same as apt install libva-dev.
--
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/1816497
Title:
[snap] vaapi chromium no video hardware decoding
Status in chromium-browser package in Ubuntu:
In Progress
Bug description:
To test the snap with VA-API changes,
1. Install the snap with
sudo snap install --channel candidate/hwacc chromium
2. snap run chromium --disable-features=UseChromeOSDirectVideoDecoder
--enable-features=VaapiVideoDecoder
3. Open a video, e.g. one from https://github.com/chthomos/video-
media-samples
4. Enter about:media-internals in the address bar and note what the
page says for kVideoDecoderName.
Please report
- The value for kVideoDecoderName from step 4. Success is typically
{Vaapi,VDA,Mojo}VideoDecoder while failure is {FFMpeg,Vpx}VideoDecoder;
- If failed, the video used for testing, including codec and resolution if
possible;
- Distro version (if in doubt, `grep VERSION= /etc/os_release`);
- GPU (if in doubt, attach the output of `lscpu`);
- CPU generation (if in doubt, attach the output of `lscpu`).
About the last point, it may be that unfortunately only those with
newer generations of Intel CPUs will have luck with this, but it's
still an uncertainty. So reports are highly welcome.
--Original Bug report -
Libva is no longer working for snap installed chromium 72.0.3626.109
(Official Build) snap (64-bit)
I followed this instruction
sudo snap install --channel=candidate/vaapi chromium
My amdgpu can use libva
`vainfo: Driver version: Mesa Gallium driver 18.3.3 for AMD STONEY (DRM
3.27.0, 4.20.0-10.1-liquorix-amd64, LLVM 7.0.1)
vainfo: Supported profile and entrypoints
VAProfileMPEG2Simple: VAEntrypointVLD
VAProfileMPEG2Main : VAEntrypointVLD
VAProfileVC1Simple : VAEntrypointVLD
VAProfileVC1Main: VAEntrypointVLD
VAProfileVC1Advanced: VAEntrypointVLD
VAProfileH264ConstrainedBaseline: VAEntrypointVLD
VAProfileH264ConstrainedBaseline: VAEntrypointEncSlice
VAProfileH264Main : VAEntrypointVLD
VAProfileH264Main : VAEntrypointEncSlice
VAProfileH264High : VAEntrypointVLD
VAProfileH264High : VAEntrypointEncSlice
VAProfileHEVCMain : VAEntrypointVLD
VAProfileHEVCMain10 : VAEntrypointVLD
VAProfileJPEGBaseline : VAEntrypointVLD
VAProfileNone : VAEntrypointVideoProc`
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1816497/+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 1816497] Re: [snap] vaapi chromium no video hardware decoding
I still think the libva source build and install is not use the proper
default path, so the related app is unable to find driver from
/usr/local/, these apps only use /usr/ lib search path.
--
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/1816497
Title:
[snap] vaapi chromium no video hardware decoding
Status in chromium-browser package in Ubuntu:
In Progress
Bug description:
To test the snap with VA-API changes,
1. Install the snap with
sudo snap install --channel candidate/hwacc chromium
2. snap run chromium --disable-features=UseChromeOSDirectVideoDecoder
--enable-features=VaapiVideoDecoder
3. Open a video, e.g. one from https://github.com/chthomos/video-
media-samples
4. Enter about:media-internals in the address bar and note what the
page says for kVideoDecoderName.
Please report
- The value for kVideoDecoderName from step 4. Success is typically
{Vaapi,VDA,Mojo}VideoDecoder while failure is {FFMpeg,Vpx}VideoDecoder;
- If failed, the video used for testing, including codec and resolution if
possible;
- Distro version (if in doubt, `grep VERSION= /etc/os_release`);
- GPU (if in doubt, attach the output of `lscpu`);
- CPU generation (if in doubt, attach the output of `lscpu`).
About the last point, it may be that unfortunately only those with
newer generations of Intel CPUs will have luck with this, but it's
still an uncertainty. So reports are highly welcome.
--Original Bug report -
Libva is no longer working for snap installed chromium 72.0.3626.109
(Official Build) snap (64-bit)
I followed this instruction
sudo snap install --channel=candidate/vaapi chromium
My amdgpu can use libva
`vainfo: Driver version: Mesa Gallium driver 18.3.3 for AMD STONEY (DRM
3.27.0, 4.20.0-10.1-liquorix-amd64, LLVM 7.0.1)
vainfo: Supported profile and entrypoints
VAProfileMPEG2Simple: VAEntrypointVLD
VAProfileMPEG2Main : VAEntrypointVLD
VAProfileVC1Simple : VAEntrypointVLD
VAProfileVC1Main: VAEntrypointVLD
VAProfileVC1Advanced: VAEntrypointVLD
VAProfileH264ConstrainedBaseline: VAEntrypointVLD
VAProfileH264ConstrainedBaseline: VAEntrypointEncSlice
VAProfileH264Main : VAEntrypointVLD
VAProfileH264Main : VAEntrypointEncSlice
VAProfileH264High : VAEntrypointVLD
VAProfileH264High : VAEntrypointEncSlice
VAProfileHEVCMain : VAEntrypointVLD
VAProfileHEVCMain10 : VAEntrypointVLD
VAProfileJPEGBaseline : VAEntrypointVLD
VAProfileNone : VAEntrypointVideoProc`
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1816497/+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 1816497] Re: [snap] vaapi chromium no video hardware decoding
Try https://launchpad.net/~nteodosio/+snap/chromium-browser-
hwacc/+build/1819056
The libva seems not working.
run: LIBVA_MESSAGING_LEVEL=2 snap run chromium
--enable-features=VaapiVideoDecoder
log:
Gtk-Message: 07:27:15.926: Failed to load module "canberra-gtk-module"
Gtk-Message: 07:27:15.928: Failed to load module "canberra-gtk-module"
WARNING: Kernel has no file descriptor comparison support: Operation not
permitted
[26304:26523:0713/072719.712410:ERROR:udev_watcher.cc(98)] Failed to begin udev
enumeration.
Warning: /usr/lib/x86_64-linux-gnu/libvulkan_intel.so: cannot open shared
object file: No such file or directory
Warning: loader_icd_scan: Failed loading library associated with ICD JSON
/usr/lib/x86_64-linux-gnu/libvulkan_intel.so.Ignoring this JSON
Warning: /usr/lib/x86_64-linux-gnu/libvulkan_lvp.so: cannot open shared object
file: No such file or directory
Warning: loader_icd_scan: Failed loading library associated with ICD JSON
/usr/lib/x86_64-linux-gnu/libvulkan_lvp.so.Ignoring this JSON
Warning: /usr/lib/x86_64-linux-gnu/libvulkan_radeon.so: cannot open shared
object file: No such file or directory
Warning: loader_icd_scan: Failed loading library associated with ICD JSON
/usr/lib/x86_64-linux-gnu/libvulkan_radeon.so.Ignoring this JSON
Warning: vkCreateInstance: Found no drivers!
Error: vkCreateInstance failed with VK_ERROR_INCOMPATIBLE_DRIVER
at CheckVkSuccessImpl
(../../third_party/dawn/src/dawn/native/vulkan/VulkanError.cpp:88)
at CreateVkInstance
(../../third_party/dawn/src/dawn/native/vulkan/BackendVk.cpp:387)
at Initialize
(../../third_party/dawn/src/dawn/native/vulkan/BackendVk.cpp:263)
at Create (../../third_party/dawn/src/dawn/native/vulkan/BackendVk.cpp:193)
at operator()
(../../third_party/dawn/src/dawn/native/vulkan/BackendVk.cpp:462)
There is no any libva log output
run: snap run --shell chromium
run: LIBVA_DRIVERS_PATH=/snap/chromium/current/usr/lib/x86_64-linux-gnu/dri/
vainfo
vainfo: error while loading shared libraries: libva-x11.so.2: cannot
open shared object file: No such file or directory
From the source, it seems libva-dev is removed in default apt install.
--
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/1816497
Title:
[snap] vaapi chromium no video hardware decoding
Status in chromium-browser package in Ubuntu:
In Progress
Bug description:
To test the snap with VA-API changes,
1. Install the snap with
sudo snap install --channel candidate/hwacc chromium
2. snap run chromium --disable-features=UseChromeOSDirectVideoDecoder
--enable-features=VaapiVideoDecoder
3. Open a video, e.g. one from https://github.com/chthomos/video-
media-samples
4. Enter about:media-internals in the address bar and note what the
page says for kVideoDecoderName.
Please report
- The value for kVideoDecoderName from step 4. Success is typically
{Vaapi,VDA,Mojo}VideoDecoder while failure is {FFMpeg,Vpx}VideoDecoder;
- If failed, the video used for testing, including codec and resolution if
possible;
- Distro version (if in doubt, `grep VERSION= /etc/os_release`);
- GPU (if in doubt, attach the output of `lscpu`);
- CPU generation (if in doubt, attach the output of `lscpu`).
About the last point, it may be that unfortunately only those with
newer generations of Intel CPUs will have luck with this, but it's
still an uncertainty. So reports are highly welcome.
--Original Bug report -
Libva is no longer working for snap installed chromium 72.0.3626.109
(Official Build) snap (64-bit)
I followed this instruction
sudo snap install --channel=candidate/vaapi chromium
My amdgpu can use libva
`vainfo: Driver version: Mesa Gallium driver 18.3.3 for AMD STONEY (DRM
3.27.0, 4.20.0-10.1-liquorix-amd64, LLVM 7.0.1)
vainfo: Supported profile and entrypoints
VAProfileMPEG2Simple: VAEntrypointVLD
VAProfileMPEG2Main : VAEntrypointVLD
VAProfileVC1Simple : VAEntrypointVLD
VAProfileVC1Main: VAEntrypointVLD
VAProfileVC1Advanced: VAEntrypointVLD
VAProfileH264ConstrainedBaseline: VAEntrypointVLD
VAProfileH264ConstrainedBaseline: VAEntrypointEncSlice
VAProfileH264Main : VAEntrypointVLD
VAProfileH264Main : VAEntrypointEncSlice
VAProfileH264High : VAEntrypointVLD
VAProfileH264High : VAEntrypointEncSlice
VAProfileHEVCMain : VAEntrypointVLD
VAProfileHEVCMain10 : VAEntrypointVLD
VAProfileJPEGBaseline : VAEntrypointVLD
VAProfileNone : VAEntrypointVideoProc`
To manage notifications about this bug go
[Desktop-packages] [Bug 1816497] Re: [snap] vaapi chromium no video hardware decoding
The libva 2.6 is not the my native ubunut. As many users reported: Post
#135, #134, #130, the libva 2.6 is comes from snap package. It is
default apt install libva version. In the snap build, there is libva
source build for latest 2.14, but the path is not overridden the default
install path. This is what I understand that there are two libva in the
snap: one is default libva 2.6, anther is libva 2.14 build from path.
In post #131, #110 I point this. I guess it is the root problem caused
my hardware configure has not been supported by current snap package.
--
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/1816497
Title:
[snap] vaapi chromium no video hardware decoding
Status in chromium-browser package in Ubuntu:
In Progress
Bug description:
To test the snap with VA-API changes,
1. Install the snap with
sudo snap install --channel candidate/hwacc chromium
2. snap run chromium --disable-features=UseChromeOSDirectVideoDecoder
--enable-features=VaapiVideoDecoder
3. Open a video, e.g. one from https://github.com/chthomos/video-
media-samples
4. Enter about:media-internals in the address bar and note what the
page says for kVideoDecoderName.
Please report
- The value for kVideoDecoderName from step 4. Success is typically
{Vaapi,VDA,Mojo}VideoDecoder while failure is {FFMpeg,Vpx}VideoDecoder;
- If failed, the video used for testing, including codec and resolution if
possible;
- Distro version (if in doubt, `grep VERSION= /etc/os_release`);
- GPU (if in doubt, attach the output of `lscpu`);
- CPU generation (if in doubt, attach the output of `lscpu`).
About the last point, it may be that unfortunately only those with
newer generations of Intel CPUs will have luck with this, but it's
still an uncertainty. So reports are highly welcome.
--Original Bug report -
Libva is no longer working for snap installed chromium 72.0.3626.109
(Official Build) snap (64-bit)
I followed this instruction
sudo snap install --channel=candidate/vaapi chromium
My amdgpu can use libva
`vainfo: Driver version: Mesa Gallium driver 18.3.3 for AMD STONEY (DRM
3.27.0, 4.20.0-10.1-liquorix-amd64, LLVM 7.0.1)
vainfo: Supported profile and entrypoints
VAProfileMPEG2Simple: VAEntrypointVLD
VAProfileMPEG2Main : VAEntrypointVLD
VAProfileVC1Simple : VAEntrypointVLD
VAProfileVC1Main: VAEntrypointVLD
VAProfileVC1Advanced: VAEntrypointVLD
VAProfileH264ConstrainedBaseline: VAEntrypointVLD
VAProfileH264ConstrainedBaseline: VAEntrypointEncSlice
VAProfileH264Main : VAEntrypointVLD
VAProfileH264Main : VAEntrypointEncSlice
VAProfileH264High : VAEntrypointVLD
VAProfileH264High : VAEntrypointEncSlice
VAProfileHEVCMain : VAEntrypointVLD
VAProfileHEVCMain10 : VAEntrypointVLD
VAProfileJPEGBaseline : VAEntrypointVLD
VAProfileNone : VAEntrypointVideoProc`
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1816497/+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
