[Touch-packages] [Bug 2078759] Re: debsums: changed file /lib/netplan/00-network-manager-all.yaml (from ubuntu-settings package)
@seb128,
I checked the history, and the comment line has been there since the
first commit. I'm not sure if there's a reason to keep it. Could we
remove the comment line in the YAML file? I just made a MR with the
suggestion from 'Danilo Egea Gondolfo'. Feel free to reject it if it's
not acceptable. Thanks!
commit 38a5c5b213120a2a8d96b3238e4e3f4566a13c4b
Author: Dave Jones
Date: Thu May 18 15:33:43 2023 +0100
Move 01-use-network-manager.yaml
To /lib/netplan/ and remove (or move, if modified) the original in
/etc/netplan. Use 00- prefix as agreed at the sprint to ensure it's
first in the configuration order. Finally, use 0600 mode to stop the
newer netplan complaining about the file mode.
diff --git a/data/ubuntu/00-network-manager-all.yaml
b/data/ubuntu/00-network-manager-all.yaml
new file mode 100644
index 000..4a8fd08
--- /dev/null
+++ b/data/ubuntu/00-network-manager-all.yaml
@@ -0,0 +1,4 @@
+# Let NetworkManager manage all devices on this system
+network:
+ version: 2
+ renderer: NetworkManager
** Changed in: oem-priority
Assignee: (unassigned) => Bin Li (binli)
** Changed in: oem-priority
Importance: Undecided => Medium
** Changed in: oem-priority
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-settings in Ubuntu.
https://bugs.launchpad.net/bugs/2078759
Title:
debsums: changed file /lib/netplan/00-network-manager-all.yaml (from
ubuntu-settings package)
Status in OEM Priority Project:
Confirmed
Status in netplan.io package in Ubuntu:
Triaged
Status in ubuntu-settings package in Ubuntu:
Invalid
Bug description:
On ubuntu desktop 24.04 image, run the operations below
1. $ nmcli d wifi connect password
2. $ nmcli c delete
3. $ sudo debsums -s
Then the error is happened debsums: changed file
/lib/netplan/00-network-manager-all.yaml (from ubuntu-settings
package)
it seems the netplan update the file belonged to ubuntu-settings that cause
the debsums failed.
---
ProblemType: Bug
ApportVersion: 2.28.1-0ubuntu3.1
Architecture: amd64
CasperMD5CheckMismatches: ./casper/initrd ./casper/vmlinuz
./casper/minimal.standard.live.hotfix.squashfs
./casper/minimal.standard.hotfix.squashfs ./casper/minimal.hotfix.squashfs
./boot/grub/grub.cfg
CasperMD5CheckResult: fail
DistributionChannelDescriptor:
# This is the distribution channel descriptor for Ubuntu 24.04 for Dell
# For more information see
http://wiki.ubuntu.com/DistributionChannelDescriptor
canonical-oem-somerville-noble-oem-24.04a-next-20240902-67
DistroRelease: Ubuntu 24.04
InstallationDate: Installed on 2024-09-02 (1 days ago)
InstallationMedia: Ubuntu OEM 24.04.1 LTS "Noble Numbat" - Release amd64
(20240829)
Package: netplan.io 1.0.1-1ubuntu2~24.04.1
PackageArchitecture: amd64
ProcVersionSignature: User Name 6.8.0-1012.12-oem 6.8.12
Tags: noble
Uname: Linux 6.8.0-1012-oem x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lxd sudo
_MarkForUpload: True
To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/2078759/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2078759] Re: debsums: changed file /lib/netplan/00-network-manager-all.yaml (from ubuntu-settings package)
With Danilo comment #4, it works fine if we could remove the comment. u@oak2-10:~$ nmcli connection add type dummy ifname d0 Connection 'dummy-d0' (2364f50d-72d5-4849-804d-f6d28467bf93) successfully added. u@oak2-10:~$ sudo cat /lib/netplan/00-network-manager-all.yaml· # Let NetworkManager manage all devices on this system network: version: 2 renderer: NetworkManager u@oak2-10:~$ sudo md5sum /lib/netplan/00-network-manager-all.yaml 81c200b0e29eeb56c518a23eb78777ab /lib/netplan/00-network-manager-all.yaml u@oak2-10:~$ nmcli connection delete dummy-d0· Connection 'dummy-d0' (2364f50d-72d5-4849-804d-f6d28467bf93) successfully deleted. u@oak2-10:~$ sudo md5sum /lib/netplan/00-network-manager-all.yaml 9b5681f7d3fc877b018790626772c504 /lib/netplan/00-network-manager-all.yaml u@oak2-10:~$ sudo cat /lib/netplan/00-network-manager-all.yaml network: version: 2 renderer: NetworkManager u@oak2-10:~$ nmcli connection add type dummy ifname d1 Connection 'dummy-d1' (f9e7f8f7-d685-4123-88e6-118f70342320) successfully added. u@oak2-10:~$ sudo md5sum /lib/netplan/00-network-manager-all.yaml 9b5681f7d3fc877b018790626772c504 /lib/netplan/00-network-manager-all.yaml u@oak2-10:~$ nmcli connection delete dummy-d1· Connection 'dummy-d1' (f9e7f8f7-d685-4123-88e6-118f70342320) successfully deleted. u@oak2-10:~$ sudo md5sum /lib/netplan/00-network-manager-all.yaml 9b5681f7d3fc877b018790626772c504 /lib/netplan/00-network-manager-all.yaml -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-settings in Ubuntu. https://bugs.launchpad.net/bugs/2078759 Title: debsums: changed file /lib/netplan/00-network-manager-all.yaml (from ubuntu-settings package) Status in OEM Priority Project: New Status in netplan.io package in Ubuntu: Triaged Status in ubuntu-settings package in Ubuntu: Invalid Bug description: On ubuntu desktop 24.04 image, run the operations below 1. $ nmcli d wifi connect password 2. $ nmcli c delete 3. $ sudo debsums -s Then the error is happened debsums: changed file /lib/netplan/00-network-manager-all.yaml (from ubuntu-settings package) it seems the netplan update the file belonged to ubuntu-settings that cause the debsums failed. --- ProblemType: Bug ApportVersion: 2.28.1-0ubuntu3.1 Architecture: amd64 CasperMD5CheckMismatches: ./casper/initrd ./casper/vmlinuz ./casper/minimal.standard.live.hotfix.squashfs ./casper/minimal.standard.hotfix.squashfs ./casper/minimal.hotfix.squashfs ./boot/grub/grub.cfg CasperMD5CheckResult: fail DistributionChannelDescriptor: # This is the distribution channel descriptor for Ubuntu 24.04 for Dell # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-noble-oem-24.04a-next-20240902-67 DistroRelease: Ubuntu 24.04 InstallationDate: Installed on 2024-09-02 (1 days ago) InstallationMedia: Ubuntu OEM 24.04.1 LTS "Noble Numbat" - Release amd64 (20240829) Package: netplan.io 1.0.1-1ubuntu2~24.04.1 PackageArchitecture: amd64 ProcVersionSignature: User Name 6.8.0-1012.12-oem 6.8.12 Tags: noble Uname: Linux 6.8.0-1012-oem x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lxd sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/2078759/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-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 Ubuntu Touch seeded 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/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-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 Ubuntu Touch seeded 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/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-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 Ubuntu Touch seeded 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/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-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 Ubuntu Touch seeded 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/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-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 Ubuntu
Touch seeded packages, which is subscribed to gstreamer1.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 gno
[Touch-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 Ubuntu Touch seeded packages, which is subscribed to gstreamer1.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/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-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 Ubuntu Touch seeded 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/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2007564] Re: Kernel livepatch option coundn't be enabled after 'Enable Ubuntu Pro'
** Attachment added: "ubuntupro.png" https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/2007564/+attachment/5647768/+files/ubuntupro.png ** Tags added: originate-from-2007068 ** Tags added: sutton -- You received this bug notification because you are a member of Ubuntu Touch seeded 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/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-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 Ubuntu Touch seeded 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/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-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 Ubuntu Touch seeded packages, which is subscribed to gstreamer1.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.freedes
[Touch-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 Ubuntu Touch seeded packages, which is subscribed to gstreamer1.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
[Touch-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 Ubuntu Touch seeded packages, which is subscribed to gstreamer1.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/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-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 Ubuntu Touch seeded packages, which is subscribed to gstreamer1.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-buffer
[Touch-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 Ubuntu Touch seeded packages, which is subscribed to gstreamer1.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/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-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 Ubuntu Touch seeded packages, which is subscribed to gstreamer1.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/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-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 Ubuntu Touch seeded packages, which is subscribed to gstreamer1.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/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-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 Ubuntu Touch seeded packages, which is subscribed to gstreamer1.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/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-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 Ubuntu Touch seeded 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/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-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 Ubuntu Touch seeded packages, which is subscribed to gstreamer1.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/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-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 Ubuntu Touch seeded 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/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-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 Ubuntu Touch seeded 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/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-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 Ubuntu Touch seeded 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/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-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 Ubuntu Touch seeded 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/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-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 Ubuntu Touch seeded 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/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-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 Ubuntu Touch seeded 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/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-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 Ubuntu Touch seeded 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/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-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 Ubuntu Touch seeded 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/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-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 Ubuntu Touch seeded 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/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-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 Ubuntu Touch seeded 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/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-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 Ubuntu Touch seeded 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/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-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 Ubuntu Touch seeded 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/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-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 Ubuntu Touch seeded 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/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-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 Ubuntu Touch seeded 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/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1978057] Re: [SRU] Support WWAN "type" attribute for 5.15 or 5.14-oem kernel
@seb128, Thanks for your feedback, I prefer to update to 1.18 than this fix, and as I know Stephane.Verdy has pushed 1.18 for long time to support more modem devices, so let's wait for the 1.18. IF the 1.18 was dropped in proposed, we could reconsider this fix. Thanks! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to modemmanager in Ubuntu. https://bugs.launchpad.net/bugs/1978057 Title: [SRU] Support WWAN "type" attribute for 5.15 or 5.14-oem kernel Status in modemmanager package in Ubuntu: New Bug description: [Impact] On 20.04.4, with modemmanager 1.16.6-2, the WWAN could be recognized correctly. With the new rules, the modem devices could be recognized correctly. And also could avoid wrong command for other protocols, like send 'AT' to wwan0mbim. [Where problems could occur] It's just a udev rules, no harm to the system. [Fix] https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/commit/1a5e0609dce59c0a49a8698f0e8cb198483124c8 udev: Match WWAN "type" attribute instead of device name Recent changes in the WWAN framework in the kernel changed the WWAN port names from e.g. "wwan0p1AT" and "wwan0p2QMI" to "wwan0at0" and "wwan0qmi0" [1, 2]. This means that the udev rules no longer match since AT/QMI are now lower-case and no longer at the end of the name. However, recently additionally a "type" sysfs attribute was added for all WWAN ports [3], which makes it much more reliable to match the WWAN port names without relying on their exact device name. Add some additional udev rules to apply the port hints based on the "type" sysfs attributes. This fixes the port enumeration on newer Linux kernels that include the aforementioned commits. Note that we still need to keep the old udev rules for now since Linux 5.13 does not have the "type" attribute yet. [1]: https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-next.git/commit/?id=392c26f7f133b9f09e5f58db1ce6ef4b3b4df49f [2]: https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-next.git/commit/?id=f458709ff40b0d992fec496952f79c7820dd3fde [3]: https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-next.git/commit/?id=b3e22e10fdda8e7be3830289a4a63ae8b88d450c (cherry picked from commit 4282c8d8) [Test] With new rule, like Fibcomm L860 (8086:7560) could be recognized and show 'Mobile Broadband' item in the top-right menu. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/1978057/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1978057] Re: [SRU] Support WWAN "type" attribute for 5.15 or 5.14-oem kernel
** Patch added: "udev-Match-WWAN-type-attribute-instead-of-device-nam.patch" https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/1978057/+attachment/5595791/+files/udev-Match-WWAN-type-attribute-instead-of-device-nam.patch ** Description changed: [Impact] On 20.04.4, with modemmanager 1.16.6-2, the WWAN could be recognized correctly. - With the new rules, the modem devices could be recognized correctly. And also could avoid wrong command for other protocols, like set 'AT' to wwan0mbim. + With the new rules, the modem devices could be recognized correctly. And also could avoid wrong command for other protocols, like send 'AT' to wwan0mbim. [Where problems could occur] It's just a udev rules, no harm to the system. [Fix] https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/commit/1a5e0609dce59c0a49a8698f0e8cb198483124c8 udev: Match WWAN "type" attribute instead of device name Recent changes in the WWAN framework in the kernel changed the WWAN port names from e.g. "wwan0p1AT" and "wwan0p2QMI" to "wwan0at0" and "wwan0qmi0" [1, 2]. This means that the udev rules no longer match since AT/QMI are now lower-case and no longer at the end of the name. However, recently additionally a "type" sysfs attribute was added for all WWAN ports [3], which makes it much more reliable to match the WWAN port names without relying on their exact device name. Add some additional udev rules to apply the port hints based on the "type" sysfs attributes. This fixes the port enumeration on newer Linux kernels that include the aforementioned commits. Note that we still need to keep the old udev rules for now since Linux 5.13 does not have the "type" attribute yet. [1]: https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-next.git/commit/?id=392c26f7f133b9f09e5f58db1ce6ef4b3b4df49f [2]: https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-next.git/commit/?id=f458709ff40b0d992fec496952f79c7820dd3fde [3]: https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-next.git/commit/?id=b3e22e10fdda8e7be3830289a4a63ae8b88d450c (cherry picked from commit 4282c8d8) [Test] With new rule, like Fibcomm L860 (8086:7560) could be recognized and show 'Mobile Broadband' item in the top-right menu. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to modemmanager in Ubuntu. https://bugs.launchpad.net/bugs/1978057 Title: [SRU] Support WWAN "type" attribute for 5.15 or 5.14-oem kernel Status in modemmanager package in Ubuntu: New Bug description: [Impact] On 20.04.4, with modemmanager 1.16.6-2, the WWAN could be recognized correctly. With the new rules, the modem devices could be recognized correctly. And also could avoid wrong command for other protocols, like send 'AT' to wwan0mbim. [Where problems could occur] It's just a udev rules, no harm to the system. [Fix] https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/commit/1a5e0609dce59c0a49a8698f0e8cb198483124c8 udev: Match WWAN "type" attribute instead of device name Recent changes in the WWAN framework in the kernel changed the WWAN port names from e.g. "wwan0p1AT" and "wwan0p2QMI" to "wwan0at0" and "wwan0qmi0" [1, 2]. This means that the udev rules no longer match since AT/QMI are now lower-case and no longer at the end of the name. However, recently additionally a "type" sysfs attribute was added for all WWAN ports [3], which makes it much more reliable to match the WWAN port names without relying on their exact device name. Add some additional udev rules to apply the port hints based on the "type" sysfs attributes. This fixes the port enumeration on newer Linux kernels that include the aforementioned commits. Note that we still need to keep the old udev rules for now since Linux 5.13 does not have the "type" attribute yet. [1]: https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-next.git/commit/?id=392c26f7f133b9f09e5f58db1ce6ef4b3b4df49f [2]: https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-next.git/commit/?id=f458709ff40b0d992fec496952f79c7820dd3fde [3]: https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-next.git/commit/?id=b3e22e10fdda8e7be3830289a4a63ae8b88d450c (cherry picked from commit 4282c8d8) [Test] With new rule, like Fibcomm L860 (8086:7560) could be recognized and show 'Mobile Broadband' item in the top-right menu. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/1978057/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1978057] Re: [SRU] Support WWAN "type" attribute for 5.15 or 5.14-oem kernel
And I knew there is a plan to upgrade MM to 1.18.6[1], and it's proposed channel, but it has been hold more than one month because of some risks. Is it possible that we merge this fix[2] into 1.16.6 first. [1] https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/1965901 [2] https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/commit/1a5e0609dce59c0a49a8698f0e8cb198483124c8 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to modemmanager in Ubuntu. https://bugs.launchpad.net/bugs/1978057 Title: [SRU] Support WWAN "type" attribute for 5.15 or 5.14-oem kernel Status in modemmanager package in Ubuntu: New Bug description: [Impact] On 20.04.4, with modemmanager 1.16.6-2, the WWAN could be recognized correctly. With the new rules, the modem devices could be recognized correctly. And also could avoid wrong command for other protocols, like set 'AT' to wwan0mbim. [Where problems could occur] It's just a udev rules, no harm to the system. [Fix] https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/commit/1a5e0609dce59c0a49a8698f0e8cb198483124c8 udev: Match WWAN "type" attribute instead of device name Recent changes in the WWAN framework in the kernel changed the WWAN port names from e.g. "wwan0p1AT" and "wwan0p2QMI" to "wwan0at0" and "wwan0qmi0" [1, 2]. This means that the udev rules no longer match since AT/QMI are now lower-case and no longer at the end of the name. However, recently additionally a "type" sysfs attribute was added for all WWAN ports [3], which makes it much more reliable to match the WWAN port names without relying on their exact device name. Add some additional udev rules to apply the port hints based on the "type" sysfs attributes. This fixes the port enumeration on newer Linux kernels that include the aforementioned commits. Note that we still need to keep the old udev rules for now since Linux 5.13 does not have the "type" attribute yet. [1]: https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-next.git/commit/?id=392c26f7f133b9f09e5f58db1ce6ef4b3b4df49f [2]: https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-next.git/commit/?id=f458709ff40b0d992fec496952f79c7820dd3fde [3]: https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-next.git/commit/?id=b3e22e10fdda8e7be3830289a4a63ae8b88d450c (cherry picked from commit 4282c8d8) [Test] With new rule, like Fibcomm L860 (8086:7560) could be recognized and show 'Mobile Broadband' item in the top-right menu. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/1978057/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1978057] [NEW] [SRU] Support WWAN "type" attribute for 5.15 or 5.14-oem kernel
Public bug reported: [Impact] On 20.04.4, with modemmanager 1.16.6-2, the WWAN could be recognized correctly. With the new rules, the modem devices could be recognized correctly. And also could avoid wrong command for other protocols, like set 'AT' to wwan0mbim. [Where problems could occur] It's just a udev rules, no harm to the system. [Fix] https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/commit/1a5e0609dce59c0a49a8698f0e8cb198483124c8 udev: Match WWAN "type" attribute instead of device name Recent changes in the WWAN framework in the kernel changed the WWAN port names from e.g. "wwan0p1AT" and "wwan0p2QMI" to "wwan0at0" and "wwan0qmi0" [1, 2]. This means that the udev rules no longer match since AT/QMI are now lower-case and no longer at the end of the name. However, recently additionally a "type" sysfs attribute was added for all WWAN ports [3], which makes it much more reliable to match the WWAN port names without relying on their exact device name. Add some additional udev rules to apply the port hints based on the "type" sysfs attributes. This fixes the port enumeration on newer Linux kernels that include the aforementioned commits. Note that we still need to keep the old udev rules for now since Linux 5.13 does not have the "type" attribute yet. [1]: https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-next.git/commit/?id=392c26f7f133b9f09e5f58db1ce6ef4b3b4df49f [2]: https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-next.git/commit/?id=f458709ff40b0d992fec496952f79c7820dd3fde [3]: https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-next.git/commit/?id=b3e22e10fdda8e7be3830289a4a63ae8b88d450c (cherry picked from commit 4282c8d8) [Test] With new rule, like Fibcomm L860 (8086:7560) could be recognized and show 'Mobile Broadband' item in the top-right menu. ** Affects: modemmanager (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to modemmanager in Ubuntu. https://bugs.launchpad.net/bugs/1978057 Title: [SRU] Support WWAN "type" attribute for 5.15 or 5.14-oem kernel Status in modemmanager package in Ubuntu: New Bug description: [Impact] On 20.04.4, with modemmanager 1.16.6-2, the WWAN could be recognized correctly. With the new rules, the modem devices could be recognized correctly. And also could avoid wrong command for other protocols, like set 'AT' to wwan0mbim. [Where problems could occur] It's just a udev rules, no harm to the system. [Fix] https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/commit/1a5e0609dce59c0a49a8698f0e8cb198483124c8 udev: Match WWAN "type" attribute instead of device name Recent changes in the WWAN framework in the kernel changed the WWAN port names from e.g. "wwan0p1AT" and "wwan0p2QMI" to "wwan0at0" and "wwan0qmi0" [1, 2]. This means that the udev rules no longer match since AT/QMI are now lower-case and no longer at the end of the name. However, recently additionally a "type" sysfs attribute was added for all WWAN ports [3], which makes it much more reliable to match the WWAN port names without relying on their exact device name. Add some additional udev rules to apply the port hints based on the "type" sysfs attributes. This fixes the port enumeration on newer Linux kernels that include the aforementioned commits. Note that we still need to keep the old udev rules for now since Linux 5.13 does not have the "type" attribute yet. [1]: https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-next.git/commit/?id=392c26f7f133b9f09e5f58db1ce6ef4b3b4df49f [2]: https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-next.git/commit/?id=f458709ff40b0d992fec496952f79c7820dd3fde [3]: https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-next.git/commit/?id=b3e22e10fdda8e7be3830289a4a63ae8b88d450c (cherry picked from commit 4282c8d8) [Test] With new rule, like Fibcomm L860 (8086:7560) could be recognized and show 'Mobile Broadband' item in the top-right menu. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/1978057/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1977986] Re: UPower and battery indicator show update in 2 minutes when connecting power cable ThinkPad
** Tags added: oem-priority originate-from-1975803 sutton -- You received this bug notification because you are a member of Ubuntu Touch seeded 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/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1977986] [NEW] UPower and battery indicator show update in 2 minutes when connecting power cable ThinkPad
Public bug reported: 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 ** Affects: upower (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded 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 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/ubuntu/+source/upower/+bug/1977986/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1970190] Re: [Feature]Wrong default value for Brazil Keyboard layout on ThinkPad
I checked the source code, it should be from console-setup which is installed by ubiquity, it will load the Keyboard/ckb/rules/base.xml, currently it will select the first one after choosing country or timezone. Maybe we could set 'thinkpad' if we could detect the type of laptop. thinkpad Portuguese (Brazil, IBM/Lenovo ThinkPad) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to console-setup in Ubuntu. https://bugs.launchpad.net/bugs/1970190 Title: [Feature]Wrong default value for Brazil Keyboard layout on ThinkPad Status in OEM Priority Project: New Status in console-setup package in Ubuntu: New Bug description: On ThinkPad, when I select 'Portuguese(Brazil)', it will use 'Portuguese(Brazil)' on second column, but the default value should be 'Portuguese(Brazil)-Portuguese(Brazil, IBM/Lenovo ThinkPad)'. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1970190/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1970190] Re: [Feature]Wrong default value for Brazil Keyboard layout on ThinkPad
** Summary changed: - [Feature]Wrong default vaule for Brazil Keyboard layout on ThinkPad + [Feature]Wrong default value for Brazil Keyboard layout on ThinkPad -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to console-setup in Ubuntu. https://bugs.launchpad.net/bugs/1970190 Title: [Feature]Wrong default value for Brazil Keyboard layout on ThinkPad Status in OEM Priority Project: New Status in console-setup package in Ubuntu: New Bug description: On ThinkPad, when I select 'Portuguese(Brazil)', it will use 'Portuguese(Brazil)' on second column, but the default value should be 'Portuguese(Brazil)-Portuguese(Brazil, IBM/Lenovo ThinkPad)'. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1970190/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1970190] Re: [Feature]Wrong default vaule for Brazil Keyboard layout on ThinkPad
** Summary changed: - Wrong default vaule for Brazil Keyboard layout on ThinkPad + [Feature]Wrong default vaule for Brazil Keyboard layout on ThinkPad -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to console-setup in Ubuntu. https://bugs.launchpad.net/bugs/1970190 Title: [Feature]Wrong default vaule for Brazil Keyboard layout on ThinkPad Status in console-setup package in Ubuntu: New Bug description: On ThinkPad, when I select 'Portuguese(Brazil)', it will use 'Portuguese(Brazil)' on second column, but the default value should be 'Portuguese(Brazil)-Portuguese(Brazil, IBM/Lenovo ThinkPad)'. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1970190/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1965901] Re: SRU the new 1.18 serie to focal for hwe
Fibocom L860-GL-16(8086:7560) could cause the ACPI reporting huge interrupts when modemmanager(1.16.6-2~20.04.1) was started at ThinkPad X1 Carbon and X13 Yoga. After upgrade to 1.18.6 from proposed channel, this issue is gone, although this type modem was not supported yet. ** Tags removed: verification-needed verification-needed-focal ** Tags added: verification-done verification-done-focal -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to modemmanager in Ubuntu. https://bugs.launchpad.net/bugs/1965901 Title: SRU the new 1.18 serie to focal for hwe Status in libmbim package in Ubuntu: New Status in libqmi package in Ubuntu: New Status in modemmanager package in Ubuntu: New Status in libmbim source package in Focal: Fix Committed Status in libqmi source package in Focal: Fix Committed Status in modemmanager source package in Focal: Fix Committed Bug description: [Impact] We want to update to the newer serie for better hardware support (support for Quectel EM120R-GL and EM160R-GL) [Test Plan] * install modemmanager, libmbim, and libqmi from -proposed * reboot and try WWAN function to see if any regression there. * perform general dogfooding of its reverse dependencies (network- manager, gnome-control-center etc.) [Where problems could occur] The new version no longer automatically performs the FCC unlock procedure by default, see details on https://modemmanager.org/docs/modemmanager/fcc-unlock/ It means some modem will stop working out of the box. Users can manually install the unlock utility as described in the "FCC unlock procedures in ModemManager >= 1.18.4" section in the page above. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libmbim/+bug/1965901/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1970190] Re: Wrong default vaule for Brazil Keyboard layout on ThinkPad
Here is the screenshot. ** Attachment added: "877976752.jpg" https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1970190/+attachment/5583454/+files/877976752.jpg -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to console-setup in Ubuntu. https://bugs.launchpad.net/bugs/1970190 Title: Wrong default vaule for Brazil Keyboard layout on ThinkPad Status in console-setup package in Ubuntu: New Bug description: On ThinkPad, when I select 'Portuguese(Brazil)', it will use 'Portuguese(Brazil)' on second column, but the default value should be 'Portuguese(Brazil)-Portuguese(Brazil, IBM/Lenovo ThinkPad)'. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1970190/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1970190] Re: Wrong default vaule for Brazil Keyboard layout on ThinkPad
This is a general issue on 20.04 and 22.04. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to console-setup in Ubuntu. https://bugs.launchpad.net/bugs/1970190 Title: Wrong default vaule for Brazil Keyboard layout on ThinkPad Status in console-setup package in Ubuntu: New Bug description: On ThinkPad, when I select 'Portuguese(Brazil)', it will use 'Portuguese(Brazil)' on second column, but the default value should be 'Portuguese(Brazil)-Portuguese(Brazil, IBM/Lenovo ThinkPad)'. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1970190/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1970190] [NEW] Wrong default vaule for Brazil Keyboard layout on ThinkPad
Public bug reported: On ThinkPad, when I select 'Portuguese(Brazil)', it will use 'Portuguese(Brazil)' on second column, but the default value should be 'Portuguese(Brazil)-Portuguese(Brazil, IBM/Lenovo ThinkPad)'. ** Affects: console-setup (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to console-setup in Ubuntu. https://bugs.launchpad.net/bugs/1970190 Title: Wrong default vaule for Brazil Keyboard layout on ThinkPad Status in console-setup package in Ubuntu: New Bug description: On ThinkPad, when I select 'Portuguese(Brazil)', it will use 'Portuguese(Brazil)' on second column, but the default value should be 'Portuguese(Brazil)-Portuguese(Brazil, IBM/Lenovo ThinkPad)'. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1970190/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1965901] Re: SRU the new 1.18 serie to focal for hwe
Hi seb128, Currently we met issue for Fibocom L860-GL-16(8086:7560) could cause the ACPI reporting huge interrupts when modemmanager(1.16.6-2~20.04.1) was started. After upgrade to 1.18.6 from https://launchpad.net/~ubuntu- desktop/+archive/ubuntu/transitions/ , this issue is gone, although this type modem was not supported yet. https://bugs.launchpad.net/bugs/1964767 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to modemmanager in Ubuntu. https://bugs.launchpad.net/bugs/1965901 Title: SRU the new 1.18 serie to focal for hwe Status in libmbim package in Ubuntu: New Status in libqmi package in Ubuntu: New Status in modemmanager package in Ubuntu: New Bug description: [Impact] We want to update to the newer serie for better hardware support (support for Quectel EM120R-GL and EM160R-GL) [Test Plan] * install modemmanager, libmbim, and libqmi from -proposed * reboot and try WWAN function to see if any regression there. * perform general dogfooding of its reverse dependencies (network- manager, gnome-control-center etc.) [Where problems could occur] The new version no longer automatically performs the FCC unlock procedure by default, see details on https://modemmanager.org/docs/modemmanager/fcc-unlock/ It means some modem will stop working out of the box. Users can manually install the unlock utility as described in the "FCC unlock procedures in ModemManager >= 1.18.4" section in the page above. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libmbim/+bug/1965901/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1928200] Re: Prompt error message "Failed to unmount /oldroot" when shutdown or reboot
@daniel, I reported a new issue. Let's focus on below links. Thanks! https://bugs.launchpad.net/ubuntu/+source/mdadm/+bug/1955690 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1928200 Title: Prompt error message "Failed to unmount /oldroot" when shutdown or reboot Status in OEM Priority Project: Fix Released Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Focal: Fix Released Bug description: [impact] root fs is not cleanly unmounted on shutdown [test case] create a file in /etc/binfmt.d/TestFormat.conf with the following content: :TestFormat:M::XX::/bin/true:F reboot the system, and then shutdown or reboot again, and watch the serial console for the error message: sd-umount[1334]: Failed to unmount /oldroot: Device or resource busy [regression potential] any regression would likely cause problems on shutdown and/or reboot, or may cause problems with unmounted root fs on shutdown/reboot [scope] this is needed only for f this is fixed upstream with PR 15566 which is included in v246, so this is fixed already in g and later this isn't reproducable on b [original description] On ubuntu 20.04, with latest kernel and systemd, it will show error on ThinkPad X1. sd-umount[1334]: Failed to unmount /oldroot: Device or resource busy systemd 245.4-4ubuntu3.6 kernel: 5.8.0-53 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1928200/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1928200] Re: Prompt error message "Failed to unmount /oldroot" when shutdown or reboot
@daniel, Thanks for the solution, and it sounds good, could you help make merge request to finalrd to ask the maintainer's idea? From my side, currently finalrd used by mdadm, I would like to remove the dependency cause mdadm. In systemd/mdadm.shutdown from mdadm, it also do "mdadm --wait-clean --scan". $ cat ./debian/mdadm.finalrd #!/bin/sh # SPDX-License-Identifier: GPL-3.0-only set -e if [ "$1" = "setup" ] then . /usr/share/initramfs-tools/hook-functions copy_exec /sbin/mdadm copy_exec /sbin/mdmon exit 0 fi mdmon --all --takeover mdadm -vv --wait-clean --scan mdadm -vv --stop --scan Thanks! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1928200 Title: Prompt error message "Failed to unmount /oldroot" when shutdown or reboot Status in OEM Priority Project: Fix Released Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Focal: Fix Released Bug description: [impact] root fs is not cleanly unmounted on shutdown [test case] create a file in /etc/binfmt.d/TestFormat.conf with the following content: :TestFormat:M::XX::/bin/true:F reboot the system, and then shutdown or reboot again, and watch the serial console for the error message: sd-umount[1334]: Failed to unmount /oldroot: Device or resource busy [regression potential] any regression would likely cause problems on shutdown and/or reboot, or may cause problems with unmounted root fs on shutdown/reboot [scope] this is needed only for f this is fixed upstream with PR 15566 which is included in v246, so this is fixed already in g and later this isn't reproducable on b [original description] On ubuntu 20.04, with latest kernel and systemd, it will show error on ThinkPad X1. sd-umount[1334]: Failed to unmount /oldroot: Device or resource busy systemd 245.4-4ubuntu3.6 kernel: 5.8.0-53 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1928200/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1951400] Re: chromium will be not responding after clicking the right mouse button
It works fine before 20.2.6, but after I upgrade to 21.0.3, we found this issue. Commandline: apt install libegl-mesa0 Requested-By: u (1001) Upgrade: libegl-mesa0:amd64 (20.2.6-0ubuntu0.20.04.1, 21.0.3-0ubuntu0.3~20.04.3), libglapi-mesa:amd64 (20.2.6-0ubuntu0.20.04.1, 21.0.3-0ubuntu0.3~20.04.3), libgbm1:amd64 (20.2.6-0ubuntu0.20.04.1, 21.0.3-0ubuntu0.3~20.04.3), libgl1-mesa-dri:amd64 (20.2.6-0ubuntu0.20.04.1, 21.0.3-0ubuntu0.3~20.04.3), libglx-mesa0:amd64 (20.2.6-0ubuntu0.20.04.1, 21.0.3-0ubuntu0.3~20.04.3) ** Changed in: oem-priority Importance: Undecided => High ** Changed in: oem-priority Assignee: (unassigned) => Bin Li (binli) ** Changed in: oem-priority Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1951400 Title: chromium will be not responding after clicking the right mouse button Status in OEM Priority Project: Confirmed Status in mesa package in Ubuntu: New Bug description: [Summary] chromium will be not responding after clicking the right mouse button and the right-click box is blank [Reproduce] 1. On ubuntu 20.04.3, open chromium. 2.click the right mouse button in the search box or above characters [Expected result] it will show copy paste…… pop-up menu [Actual result] the right-click box is blank and chromium will be not responding ,chromium will automatically close after a while [Additional information Platform:ThinkPad L15 CPU:Intel AMD Ryzen 5 PRO 5650U OS:Ubuntu 20.04.3 LTS Memory:16GB To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1951400/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1951400] [NEW] chromium will be not responding after clicking the right mouse button
Public bug reported: [Summary] chromium will be not responding after clicking the right mouse button and the right-click box is blank [Reproduce] 1. On ubuntu 20.04.3, open chromium. 2.click the right mouse button in the search box or above characters [Expected result] it will show copy paste…… pop-up menu [Actual result] the right-click box is blank and chromium will be not responding ,chromium will automatically close after a while [Additional information Platform:ThinkPad L15 CPU:Intel AMD Ryzen 5 PRO 5650U OS:Ubuntu 20.04.3 LTS Memory:16GB ** Affects: oem-priority Importance: High Assignee: Bin Li (binli) Status: Confirmed ** Affects: mesa (Ubuntu) Importance: Undecided Status: New ** Tags: oem-priority originate-from-1950402 sutton ** Tags added: oem-priority originate-from-1950402 sutton -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1951400 Title: chromium will be not responding after clicking the right mouse button Status in OEM Priority Project: Confirmed Status in mesa package in Ubuntu: New Bug description: [Summary] chromium will be not responding after clicking the right mouse button and the right-click box is blank [Reproduce] 1. On ubuntu 20.04.3, open chromium. 2.click the right mouse button in the search box or above characters [Expected result] it will show copy paste…… pop-up menu [Actual result] the right-click box is blank and chromium will be not responding ,chromium will automatically close after a while [Additional information Platform:ThinkPad L15 CPU:Intel AMD Ryzen 5 PRO 5650U OS:Ubuntu 20.04.3 LTS Memory:16GB To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1951400/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1940377] Re: The WWAN - Huawei Technologies Co., Ltd. [12d1:15c1] does not work after install Ubuntu Hirsute.
After debug, this issue is not related to kernel. cdc_ether was unregistered by usb-modeswitch. After I installed the old verison of usb-modeswitch, this issue is fixed, it looks like a regression. Aug 30 05:54:32 u-ThinkPad-L460 kernel: cdc_ether 1-9:2.0 wwan0: register 'cdc_ether' at usb-:00:14.0-9, Mobile Broadband Network Device, 02:1e:10:1f:00:00 Aug 30 05:54:32 u-ThinkPad-L460 kernel: usbcore: registered new interface driver cdc_ether Aug 30 05:54:32 u-ThinkPad-L460 kernel: cdc_ether 1-9:2.0 wwx021e101f: renamed from wwan0 Aug 30 05:54:33 u-ThinkPad-L460 kernel: cdc_ether 1-9:2.0 wwx021e101f: unregister 'cdc_ether' usb-:00:14.0-9, Mobile Broadband Network Device -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1940377 Title: The WWAN - Huawei Technologies Co., Ltd. [12d1:15c1] does not work after install Ubuntu Hirsute. Status in linux package in Ubuntu: Incomplete Status in network-manager package in Ubuntu: New Bug description: u@u-ThinkPad-L460:~$ uname -a Linux u-ThinkPad-L460 Kernel 5.11.0-16-generic #17-Ubuntu SMP Wed Apr 14 20:12:43 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux u@u-ThinkPad-L460:~$ cat /etc/issue Ubuntu 21.04 \n \l CPU : Intel(R) Core(TM) i7-6500U CPU @ 2.50GHz WWAN : 12d1:15c1 Huawei Technologies Co., Ltd. ME906s LTE M.2 Module [Steps] 1. Make a Live CD for Ubuntu Hirsute 2. Plug in the Live CD 3. Boot ThinkPad L460 4. Install Ubuntu Hirsute and completed all configurations 5. Make sure the installation done 6. Boot the system and log in 7. Enable the proposed channel 8. Do the update and upgrade 9. Reboot the system and check mmcli is upgraded to 1.16.6 7. Verify the WWAN working or not. [Actual result] The WWAN can not be detected. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: ubuntu-release-upgrader-core 1:21.04.16 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 Uname: Linux 5.11.0-16-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: pass CrashDB: ubuntu Date: Wed Aug 18 01:32:17 2021 InstallationDate: Installed on 2021-08-18 (0 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-release-upgrader Symptom: ubuntu-release-upgrader UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: pass DistroRelease: Ubuntu 21.04 InstallationDate: Installed on 2021-08-18 (0 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) IpRoute: default via 10.1.1.1 dev wlp3s0 proto dhcp metric 600 10.1.1.0/24 dev wlp3s0 proto kernel scope link src 10.1.1.106 metric 600 169.254.0.0/16 dev wlp3s0 scope link metric 1000 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true Package: network-manager 1.30.0-1ubuntu3 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 Tags: hirsute Uname: Linux 5.11.0-16-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.30.0 connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1940377/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1928200] Re: Prompt error message "Failed to unmount /oldroot" when shutdown or reboot
** Changed in: oem-priority Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1928200 Title: Prompt error message "Failed to unmount /oldroot" when shutdown or reboot Status in OEM Priority Project: Fix Released Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Focal: Fix Released Bug description: [impact] root fs is not cleanly unmounted on shutdown [test case] create a file in /etc/binfmt.d/TestFormat.conf with the following content: :TestFormat:M::XX::/bin/true:F reboot the system, and then shutdown or reboot again, and watch the serial console for the error message: sd-umount[1334]: Failed to unmount /oldroot: Device or resource busy [regression potential] any regression would likely cause problems on shutdown and/or reboot, or may cause problems with unmounted root fs on shutdown/reboot [scope] this is needed only for f this is fixed upstream with PR 15566 which is included in v246, so this is fixed already in g and later this isn't reproducable on b [original description] On ubuntu 20.04, with latest kernel and systemd, it will show error on ThinkPad X1. sd-umount[1334]: Failed to unmount /oldroot: Device or resource busy systemd 245.4-4ubuntu3.6 kernel: 5.8.0-53 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1928200/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1937988] Re: The image is distorted while use iGPU rendering and output via AMD GPU
Installed 21.04 on P348 and reproduced this issue, after upgraded to proposed packages, this issue is fixed. $ DRI_PRIME=1 glxgears -info Running synchronized to the vertical refresh. The framerate should be approximately the same as the monitor refresh rate. GL_RENDERER = Mesa Intel(R) Graphics (RKL GT1) GL_VERSION= 4.6 (Compatibility Profile) Mesa 21.0.3 GL_VENDOR = Intel GL_EXTENSIONS = GL_ARB_multisample ... VisualID 509, 0x1fd 305 frames in 5.0 seconds = 60.917 FPS 300 frames in 5.0 seconds = 59.809 FPS 301 frames in 5.0 seconds = 60.000 FPS $ glxgears -info Running synchronized to the vertical refresh. The framerate should be approximately the same as the monitor refresh rate. GL_RENDERER = AMD Radeon (TM) Pro WX 3200 Series (POLARIS12, DRM 3.40.0, 5.11.0-25-generic, LLVM 12.0.0) GL_VERSION= 4.6 (Compatibility Profile) Mesa 21.0.3 GL_VENDOR = AMD GL_EXTENSIONS = GL_ARB_multisample ... VisualID 509, 0x1fd 304 frames in 5.0 seconds = 60.782 FPS 300 frames in 5.0 seconds = 59.800 FPS ** Tags removed: verification-needed verification-needed-hirsute ** Tags added: verification-done verification-done-hirsute -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1937988 Title: The image is distorted while use iGPU rendering and output via AMD GPU Status in OEM Priority Project: Fix Committed Status in mesa package in Ubuntu: Fix Committed Status in mesa source package in Focal: Fix Committed Status in mesa source package in Hirsute: Fix Committed Bug description: [Impact] Image is distorted with PRIME, caused by mismatch in stride alignment between intel and amdgpu/nvidia after intel bumped the alignment to 256 bytes. [Fix] Upstream fixed it in 21.2-series, and backport to 21.0.x needs four commits in total. [Test case] 1. Connect a monitor on the AMD GPU. 2. Power on the system and boot into OS. 3. Run below command to launch glxgears Cmd> DRI_PRIME=1 glxgears -info * Expected result The image is not distorted while running the glxgears * Actual result The image is distorted while running the glxgears [Where things might go wrong] This is a regression caused by the intel driver, so the backports merely fix what got broken. Regressions would only manifest on hybrid graphics platforms. --- Here is the upstream bug for tracking this issue. https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/11942?commit_id=505f815e5ead8c9872bbda4c1ff3aeaee7223d64 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1937988/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1937988] Re: The image is distorted while use iGPU rendering and output via AMD GPU
After upgraded to latest mesa, this issue is fixed. Now it works fine on 5.10.0-oem or 5.13.0-oem kernel. Thanks! $ DRI_PRIME=1 glxgears -info Running synchronized to the vertical refresh. The framerate should be approximately the same as the monitor refresh rate. GL_RENDERER = Mesa Intel(R) Graphics (RKL GT1) GL_VERSION= 4.6 (Compatibility Profile) Mesa 21.0.3 GL_VENDOR = Intel GL_EXTENSIONS = GL_ARB_multisample ... VisualID 1337, 0x539 305 frames in 5.0 seconds = 60.916 FPS 300 frames in 5.0 seconds = 59.999 FPS 300 frames in 5.0 seconds = 59.986 FPS $ glxgears -info Running synchronized to the vertical refresh. The framerate should be approximately the same as the monitor refresh rate. GL_RENDERER = AMD Radeon (TM) Pro WX 3200 Series (POLARIS12, DRM 3.40.0, 5.10.0-1038-oem, LLVM 12.0.0) GL_VERSION= 4.6 (Compatibility Profile) Mesa 21.0.3 GL_VENDOR = AMD GL_EXTENSIONS = GL_ARB_multisample ... VisualID 1337, 0x539 350 frames in 5.0 seconds = 69.915 FPS 300 frames in 5.0 seconds = 59.959 FPS 300 frames in 5.0 seconds = 59.979 FPS ** Tags removed: verification-needed-focal ** Tags added: verification-done-focal ** Changed in: oem-priority Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1937988 Title: The image is distorted while use iGPU rendering and output via AMD GPU Status in OEM Priority Project: Fix Committed Status in mesa package in Ubuntu: Fix Committed Status in mesa source package in Focal: Fix Committed Status in mesa source package in Hirsute: Fix Committed Bug description: [Impact] Image is distorted with PRIME, caused by mismatch in stride alignment between intel and amdgpu/nvidia after intel bumped the alignment to 256 bytes. [Fix] Upstream fixed it in 21.2-series, and backport to 21.0.x needs four commits in total. [Test case] 1. Connect a monitor on the AMD GPU. 2. Power on the system and boot into OS. 3. Run below command to launch glxgears Cmd> DRI_PRIME=1 glxgears -info * Expected result The image is not distorted while running the glxgears * Actual result The image is distorted while running the glxgears [Where things might go wrong] This is a regression caused by the intel driver, so the backports merely fix what got broken. Regressions would only manifest on hybrid graphics platforms. --- Here is the upstream bug for tracking this issue. https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/11942?commit_id=505f815e5ead8c9872bbda4c1ff3aeaee7223d64 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1937988/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1937988] Re: The image is distorted while use iGPU rendering and output via AMD GPU
** Tags added: originate-from-1935587 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1937988 Title: The image is distorted while use iGPU rendering and output via AMD GPU Status in OEM Priority Project: Fix Committed Status in mesa package in Ubuntu: Fix Committed Status in mesa source package in Focal: Fix Committed Status in mesa source package in Hirsute: Fix Committed Bug description: [Impact] Image is distorted with PRIME, caused by mismatch in stride alignment between intel and amdgpu/nvidia after intel bumped the alignment to 256 bytes. [Fix] Upstream fixed it in 21.2-series, and backport to 21.0.x needs four commits in total. [Test case] 1. Connect a monitor on the AMD GPU. 2. Power on the system and boot into OS. 3. Run below command to launch glxgears Cmd> DRI_PRIME=1 glxgears -info * Expected result The image is not distorted while running the glxgears * Actual result The image is distorted while running the glxgears [Where things might go wrong] This is a regression caused by the intel driver, so the backports merely fix what got broken. Regressions would only manifest on hybrid graphics platforms. --- Here is the upstream bug for tracking this issue. https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/11942?commit_id=505f815e5ead8c9872bbda4c1ff3aeaee7223d64 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1937988/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1928200] Re: Prompt error message "Failed to unmount /oldroot" when shutdown or reboot
Upgraded to systemd 245.4-4ubuntu3.8 on ThinkPad P17, but this issue is still exist. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1928200 Title: Prompt error message "Failed to unmount /oldroot" when shutdown or reboot Status in OEM Priority Project: Confirmed Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Focal: Fix Committed Bug description: [impact] root fs is not cleanly unmounted on shutdown [test case] create a file in /etc/binfmt.d/TestFormat.conf with the following content: :TestFormat:M::XX::/bin/true:F reboot the system, and then shutdown or reboot again, and watch the serial console for the error message: sd-umount[1334]: Failed to unmount /oldroot: Device or resource busy [regression potential] any regression would likely cause problems on shutdown and/or reboot, or may cause problems with unmounted root fs on shutdown/reboot [scope] this is needed only for f this is fixed upstream with PR 15566 which is included in v246, so this is fixed already in g and later this isn't reproducable on b [original description] On ubuntu 20.04, with latest kernel and systemd, it will show error on ThinkPad X1. sd-umount[1334]: Failed to unmount /oldroot: Device or resource busy systemd 245.4-4ubuntu3.6 kernel: 5.8.0-53 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1928200/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1928200] Re: Prompt error message "Failed to unmount /oldroot" when shutdown or reboot
Checked the proposed channel, the 3.8 was not ready yet, will check it later. ** Changed in: oem-priority Assignee: (unassigned) => Bin Li (binli) ** Changed in: oem-priority Importance: Undecided => High ** Changed in: oem-priority Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1928200 Title: Prompt error message "Failed to unmount /oldroot" when shutdown or reboot Status in OEM Priority Project: Confirmed Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Focal: Fix Committed Bug description: [impact] root fs is not cleanly unmounted on shutdown [test case] create a file in /etc/binfmt.d/TestFormat.conf with the following content: :TestFormat:M::XX::/bin/true:F reboot the system, and then shutdown or reboot again, and watch the serial console for the error message: sd-umount[1334]: Failed to unmount /oldroot: Device or resource busy [regression potential] any regression would likely cause problems on shutdown and/or reboot, or may cause problems with unmounted root fs on shutdown/reboot [scope] this is needed only for f this is fixed upstream with PR 15566 which is included in v246, so this is fixed already in g and later this isn't reproducable on b [original description] On ubuntu 20.04, with latest kernel and systemd, it will show error on ThinkPad X1. sd-umount[1334]: Failed to unmount /oldroot: Device or resource busy systemd 245.4-4ubuntu3.6 kernel: 5.8.0-53 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1928200/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1860826] Re: pam_unix(sudo:auth): Couldn't open /etc/securetty: No such file or directory
After I upgraded libpam-runtime from 1.3.1-5ubuntu4.1 to 1.3.1-5ubuntu4.2, I also met this error. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pam in Ubuntu. https://bugs.launchpad.net/bugs/1860826 Title: pam_unix(sudo:auth): Couldn't open /etc/securetty: No such file or directory Status in pam package in Ubuntu: Confirmed Status in pam source package in Focal: Confirmed Status in pam source package in Groovy: Confirmed Status in pam package in Debian: Fix Released Bug description: Hello, after upgrading to focal I found the following in my journalctl output: Jan 24 23:07:00 millbarge sudo[32120]: pam_unix(sudo:auth): Couldn't open /etc/securetty: No such file or directory Jan 24 23:07:01 millbarge sudo[32120]: pam_unix(sudo:auth): Couldn't open /etc/securetty: No such file or directory The login package stopped packaging this file: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=731656 and now forcibly removes the file: https://paste.ubuntu.com/p/myh9cGWrHD/ However, the pam package's pam_unix.so module has not yet been adapted to ignore this file: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=674857#25 Thanks ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: libpam-modules 1.3.1-5ubuntu4 ProcVersionSignature: Ubuntu 5.4.0-9.12-generic 5.4.3 Uname: Linux 5.4.0-9-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu15 Architecture: amd64 Date: Fri Jan 24 23:35:33 2020 ProcEnviron: TERM=rxvt-unicode-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: pam UpgradeStatus: Upgraded to focal on 2020-01-24 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pam/+bug/1860826/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1928200] Re: Prompt error message "Failed to unmount /oldroot" when shutdown or reboot
Tried to back-port 4 patches from #2, it didn't work for me. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1928200 Title: Prompt error message "Failed to unmount /oldroot" when shutdown or reboot Status in OEM Priority Project: New Status in systemd package in Ubuntu: New Bug description: On ubuntu 20.04, with latest kernel and systemd, it will show error on ThinkPad X1. sd-umount[1334]: Failed to unmount /oldroot: Device or resource busy systemd 245.4-4ubuntu3.6 kernel: 5.8.0-53 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1928200/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1928200] Re: Prompt error message "Failed to unmount /oldroot" when shutdown or reboot
https://github.com/systemd/systemd/issues/14981 ** Tags added: oem-priority originate-from-1927884 sutton ** Bug watch added: github.com/systemd/systemd/issues #14981 https://github.com/systemd/systemd/issues/14981 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1928200 Title: Prompt error message "Failed to unmount /oldroot" when shutdown or reboot Status in OEM Priority Project: New Status in systemd package in Ubuntu: New Bug description: On ubuntu 20.04, with latest kernel and systemd, it will show error on ThinkPad X1. sd-umount[1334]: Failed to unmount /oldroot: Device or resource busy systemd 245.4-4ubuntu3.6 kernel: 5.8.0-53 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1928200/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1928200] [NEW] Prompt error message "Failed to unmount /oldroot" when shutdown or reboot
Public bug reported: On ubuntu 20.04, with latest kernel and systemd, it will show error on ThinkPad X1. sd-umount[1334]: Failed to unmount /oldroot: Device or resource busy systemd 245.4-4ubuntu3.6 kernel: 5.8.0-53 ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Attachment added: "error.jpg" https://bugs.launchpad.net/bugs/1928200/+attachment/5496620/+files/error.jpg -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1928200 Title: Prompt error message "Failed to unmount /oldroot" when shutdown or reboot Status in systemd package in Ubuntu: New Bug description: On ubuntu 20.04, with latest kernel and systemd, it will show error on ThinkPad X1. sd-umount[1334]: Failed to unmount /oldroot: Device or resource busy systemd 245.4-4ubuntu3.6 kernel: 5.8.0-53 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1928200/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1868210] Re: [SRU] Load ucm on Lenovo notebooks based on bios version
Tried libasound2 packages with the 5.0.0-10477-oem-osp1 kernel in proposed, the dmic works fine on bionic. libasound2:1.1.3-5ubuntu0.5 libasound2-data:1.1.3-5ubuntu0.5 ** Tags removed: verification-needed-bionic ** Tags added: verification-done-bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-lib in Ubuntu. https://bugs.launchpad.net/bugs/1868210 Title: [SRU] Load ucm on Lenovo notebooks based on bios version Status in HWE Next: New Status in alsa-lib package in Ubuntu: Invalid Status in alsa-lib source package in Bionic: Fix Committed Status in alsa-lib source package in Eoan: Fix Committed Status in alsa-lib source package in Focal: Invalid Bug description: This SRU is not backported from upstream of alsa-lib and this SRU is not going to be submitted to upstream. That is because the latest alsa-lib already supports ucm2, and with ucm2 all machines could share one ucm, so latest alsa-lib does not have this problem. This problem is only specific to the alsa-lib in Bionic and Eoan. [Impact] On some Lenovo notebooks, UCM files are not loaded and mic can't be used. [Fix] UCM was loaded based on cardlongname, but that can't cover all configs of the same model. Lenovo suggested to load ucm by the first 3 letters of /sys/devices/virtual/dmi/id/bios_version, so that all configs could use just one ucm. [Test Case] After applying this patch, install the testing alsa-lib on Lenovo X1C7 and Dell vostro 5390, which are all machines with the DMIC connected to PCH. After system bootup, check the /usr/share/alsa/ucm/ for the presence of LENOVO-BIOSID-xxx directories. Lenovo X1C7 should load the N2H/*.conf and verify the audio functionalities. The Dell machine should still load the ucm by cardname, and it should work as good as before. [Regression Potential] low, just add some new UCMs and let Lenovo machine find the UCM by bios_version if it fails by cardlongname. I've already tested the change on Lenovo and Dell machines. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1868210/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1772844] Re: snapd didn't initialize all the seeded snaps
@Peter, Yes, we met the same issue. https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1828604 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1772844 Title: snapd didn't initialize all the seeded snaps Status in OEM Priority Project: Fix Released Status in snapd: Fix Released Status in livecd-rootfs package in Ubuntu: Won't Fix Status in ubuntu-meta package in Ubuntu: Fix Released Status in livecd-rootfs source package in Bionic: Fix Released Status in ubuntu-meta source package in Bionic: Fix Released Bug description: snapd didn't initialize all the seeded snaps bionic-desktop-amd64.iso (20180522) ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: snapd 2.32.9+18.04 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue May 22 22:59:18 2018 InstallationDate: Installed on 2018-05-23 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180522) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: snapd UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1772844/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1811204] Re: login console don't show up when switching from graphic.target to multi-user.target
https://ubuntuforums.org/showthread.php?t=2330707 Here is the similar issue on 16.04. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1811204 Title: login console don't show up when switching from graphic.target to multi-user.target Status in systemd package in Ubuntu: New Bug description: We found the login console, like tty1, can't show up when we did below command in 18.04.1. $ sudo systemctl isolate multi-user.target or $ sudo init 3 After above command, it will show a cursor with black screen. I could switch to tty1 with 'Ctrl+Alt+F1', and login into system. $ sudo systemctl isolate graphical.target or $ sudo init 5 It could show the login GUI. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1811204/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1811204] [NEW] login console don't show up when switching from graphic.target to multi-user.target
Public bug reported: We found the login console, like tty1, can't show up when we did below command in 18.04.1. $ sudo systemctl isolate multi-user.target or $ sudo init 3 After above command, it will show a cursor with black screen. I could switch to tty1 with 'Ctrl+Alt+F1', and login into system. $ sudo systemctl isolate graphical.target or $ sudo init 5 It could show the login GUI. ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Summary changed: - No login console when switching from graphic.target to multi-user.target + login console don't show up when switching from graphic.target to multi-user.target -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1811204 Title: login console don't show up when switching from graphic.target to multi-user.target Status in systemd package in Ubuntu: New Bug description: We found the login console, like tty1, can't show up when we did below command in 18.04.1. $ sudo systemctl isolate multi-user.target or $ sudo init 3 After above command, it will show a cursor with black screen. I could switch to tty1 with 'Ctrl+Alt+F1', and login into system. $ sudo systemctl isolate graphical.target or $ sudo init 5 It could show the login GUI. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1811204/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1780076] Re: 18.04 login screen is skewed/distorted (incorrect stride) when using hibmc_drm graphics
@vanvugt, I've updated the Description with the 'Template of SRU', do you need anything else? Thanks! ** Description changed: - Upstream: https://gitlab.gnome.org/GNOME/mutter/issues/219 + [Impact] - We found the login screen is blur, with Huawei's chip. + * The login screen is blur, with Huawei's Hi1710 chipset. And below is + the hardware information. 05:00.0 VGA compatible controller [0300]: Huawei Technologies Co., Ltd. Hi1710 [iBMC Intelligent Management system chip w/VGA support] [19e5:1711] (rev 01) - When we set the Wayland to disable, it could login. + * It's really big effect for our customer when they use the arm server. + It's an hardware specific issue, and I've debugged with the mutter for a + while upstream's help, but no luck. And the workaround patches was + accepted by upstream and now in 18.10. - [daemon] - # Uncoment the line below to force the login screen to use Xorg - WaylandEnable=false + + [Test Case] + + * It's an hardware specific issue, installed the 18.04 on Huawei's + Hi1710 arm server. After boot up, you will found the login screen is + distorted. + + + [Regression Potential] + + * It's just a kind of workaround, we add one the udev rule to skip + Huawei's chipset, which won't affects other platform. + + [Other Info] + + * Upstream: https://gitlab.gnome.org/GNOME/mutter/issues/219 ** Changed in: gdm3 (Ubuntu) Assignee: Bin Li (binli) => (unassigned) ** Changed in: gdm3 (Ubuntu) Status: In Progress => New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1780076 Title: 18.04 login screen is skewed/distorted (incorrect stride) when using hibmc_drm graphics Status in gdm3 package in Ubuntu: Fix Released Status in mutter package in Ubuntu: Won't Fix Bug description: [Impact] * The login screen is blur, with Huawei's Hi1710 chipset. And below is the hardware information. 05:00.0 VGA compatible controller [0300]: Huawei Technologies Co., Ltd. Hi1710 [iBMC Intelligent Management system chip w/VGA support] [19e5:1711] (rev 01) * It's really big effect for our customer when they use the arm server. It's an hardware specific issue, and I've debugged with the mutter for a while upstream's help, but no luck. And the workaround patches was accepted by upstream and now in 18.10. [Test Case] * It's an hardware specific issue, installed the 18.04 on Huawei's Hi1710 arm server. After boot up, you will found the login screen is distorted. [Regression Potential] * It's just a kind of workaround, we add one the udev rule to skip Huawei's chipset, which won't affects other platform. [Other Info] * Upstream: https://gitlab.gnome.org/GNOME/mutter/issues/219 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1780076/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1780076] Re: 18.04 login screen is skewed/distorted (incorrect stride) when using hibmc_drm graphics
@vanvugt, Now the workaround patches were merged into 18.10, I thought we could start the SRU process for 18.04. Could you help it? Thanks! https://git.launchpad.net/~ubuntu-desktop/ubuntu/+source/gdm3 commit 53a5db08ae0b6e8e65b2bc0a99d374a5783a3e9b Author: Didier Roche Date: Wed Sep 5 09:40:04 2018 +0200 install udev rules in the correct folder * debian/gdm3.install: - install udev rules in the correct folder (following upstream build fixes) commit e7c108779b23f10da71953fefa2ba5eacc76fac1 Author: Bin Li Date: Wed Aug 29 16:47:46 2018 +0800 data: 61-gdm.rules.in Disable wayland for Huawei Hi1710 chipsets. The login screen is skewed/distorted on arm server, and I couldn't find root cause, and no other developer ever has access to the hardware. https://gitlab.gnome.org/GNOME/mutter/issues/219 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1780076 Title: 18.04 login screen is skewed/distorted (incorrect stride) when using hibmc_drm graphics Status in gdm3 package in Ubuntu: In Progress Status in mesa package in Ubuntu: New Status in mutter package in Ubuntu: New Bug description: [Impact] * The login screen is blur, with Huawei's Hi1710 chipset. And below is the hardware information. 05:00.0 VGA compatible controller [0300]: Huawei Technologies Co., Ltd. Hi1710 [iBMC Intelligent Management system chip w/VGA support] [19e5:1711] (rev 01) * It's really big effect for our customer when they use the arm server. It's an hardware specific issue, and I've debugged with the mutter for a while upstream's help, but no luck. And the workaround patches was accepted by upstream and now in 18.10. [Test Case] * It's an hardware specific issue, installed the 18.04 on Huawei's Hi1710 arm server. After boot up, you will found the login screen is distorted. [Regression Potential] * It's just a kind of workaround, we add one the udev rule to skip Huawei's chipset, which won't affects other platform. [Other Info] * Upstream: https://gitlab.gnome.org/GNOME/mutter/issues/219 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1780076/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1780076] Re: 18.04 login screen is skewed/distorted (incorrect stride) when using hibmc_drm graphics
The !35 has some side effect for other distribution, after discuss, I made a new patch !44, it was accepted by upstream. https://gitlab.gnome.org/GNOME/gdm/merge_requests/35 https://gitlab.gnome.org/GNOME/gdm/merge_requests/44 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1780076 Title: 18.04 login screen is skewed/distorted (incorrect stride) when using hibmc_drm graphics Status in gdm3 package in Ubuntu: In Progress Status in mesa package in Ubuntu: New Status in mutter package in Ubuntu: New Bug description: Upstream: https://gitlab.gnome.org/GNOME/mutter/issues/219 We found the login screen is blur, with Huawei's chip. 05:00.0 VGA compatible controller [0300]: Huawei Technologies Co., Ltd. Hi1710 [iBMC Intelligent Management system chip w/VGA support] [19e5:1711] (rev 01) When we set the Wayland to disable, it could login. [daemon] # Uncoment the line below to force the login screen to use Xorg WaylandEnable=false To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1780076/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1780076] Re: 18.04 login screen is skewed/distorted (incorrect stride) when using hibmc_drm graphics
** Changed in: gdm3 (Ubuntu) Assignee: (unassigned) => Bin Li (binli) ** Changed in: gdm3 (Ubuntu) Status: New => In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1780076 Title: 18.04 login screen is skewed/distorted (incorrect stride) when using hibmc_drm graphics Status in gdm3 package in Ubuntu: In Progress Status in mesa package in Ubuntu: New Status in mutter package in Ubuntu: New Bug description: Upstream: https://gitlab.gnome.org/GNOME/mutter/issues/219 We found the login screen is blur, with Huawei's chip. 05:00.0 VGA compatible controller [0300]: Huawei Technologies Co., Ltd. Hi1710 [iBMC Intelligent Management system chip w/VGA support] [19e5:1711] (rev 01) When we set the Wayland to disable, it could login. [daemon] # Uncoment the line below to force the login screen to use Xorg WaylandEnable=false To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1780076/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1780076] Re: 18.04 login screen is skewed/distorted (incorrect stride) when using hibmc_drm graphics
I made a merge request on packaging tree, is it ok? Thanks! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1780076 Title: 18.04 login screen is skewed/distorted (incorrect stride) when using hibmc_drm graphics Status in gdm3 package in Ubuntu: New Status in mesa package in Ubuntu: New Status in mutter package in Ubuntu: New Bug description: Upstream: https://gitlab.gnome.org/GNOME/mutter/issues/219 We found the login screen is blur, with Huawei's chip. 05:00.0 VGA compatible controller [0300]: Huawei Technologies Co., Ltd. Hi1710 [iBMC Intelligent Management system chip w/VGA support] [19e5:1711] (rev 01) When we set the Wayland to disable, it could login. [daemon] # Uncoment the line below to force the login screen to use Xorg WaylandEnable=false To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1780076/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1780076] Re: 18.04 login screen is skewed/distorted (incorrect stride) when using hibmc_drm graphics
@seb128, Could you help check if this debdiff is ok? Thanks! ** Attachment added: "gdm3_3.29.91-1ubuntu2_3.29.91-1ubuntu3.diff.gz" https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1780076/+attachment/5182212/+files/gdm3_3.29.91-1ubuntu2_3.29.91-1ubuntu3.diff.gz -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1780076 Title: 18.04 login screen is skewed/distorted (incorrect stride) when using hibmc_drm graphics Status in gdm3 package in Ubuntu: New Status in mesa package in Ubuntu: New Status in mutter package in Ubuntu: New Bug description: Upstream: https://gitlab.gnome.org/GNOME/mutter/issues/219 We found the login screen is blur, with Huawei's chip. 05:00.0 VGA compatible controller [0300]: Huawei Technologies Co., Ltd. Hi1710 [iBMC Intelligent Management system chip w/VGA support] [19e5:1711] (rev 01) When we set the Wayland to disable, it could login. [daemon] # Uncoment the line below to force the login screen to use Xorg WaylandEnable=false To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1780076/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1780076] Re: 18.04 login screen is skewed/distorted (incorrect stride) when using hibmc_drm graphics
Here is the patch for upstream, we need merge it into 3.29.91. https://gitlab.gnome.org/GNOME/gdm/merge_requests/35 ** Patch added: "0002-data-Makefile.am.patch" https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1780076/+attachment/5182208/+files/0002-data-Makefile.am.patch -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1780076 Title: 18.04 login screen is skewed/distorted (incorrect stride) when using hibmc_drm graphics Status in gdm3 package in Ubuntu: New Status in mesa package in Ubuntu: New Status in mutter package in Ubuntu: New Bug description: Upstream: https://gitlab.gnome.org/GNOME/mutter/issues/219 We found the login screen is blur, with Huawei's chip. 05:00.0 VGA compatible controller [0300]: Huawei Technologies Co., Ltd. Hi1710 [iBMC Intelligent Management system chip w/VGA support] [19e5:1711] (rev 01) When we set the Wayland to disable, it could login. [daemon] # Uncoment the line below to force the login screen to use Xorg WaylandEnable=false To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1780076/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1780076] Re: 18.04 login screen is skewed/distorted (incorrect stride) when using hibmc_drm graphics
Here is the patch for https://gitlab.gnome.org/GNOME/gdm/merge_requests/38 ** Patch added: "0003-data-61-gdm.rules.in.patch" https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1780076/+attachment/5182209/+files/0003-data-61-gdm.rules.in.patch ** Patch removed: "disable-wayland-bydefault.patch" https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1780076/+attachment/5159579/+files/disable-wayland-bydefault.patch ** Patch removed: "ubuntu_disable_wayland_huawei_chipsets.patch" https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1780076/+attachment/5160787/+files/ubuntu_disable_wayland_huawei_chipsets.patch ** Patch removed: "0001-Disable-wayland-for-Huawei-Hi1710-LP-1780076.patch" https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1780076/+attachment/5179560/+files/0001-Disable-wayland-for-Huawei-Hi1710-LP-1780076.patch -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1780076 Title: 18.04 login screen is skewed/distorted (incorrect stride) when using hibmc_drm graphics Status in gdm3 package in Ubuntu: New Status in mesa package in Ubuntu: New Status in mutter package in Ubuntu: New Bug description: Upstream: https://gitlab.gnome.org/GNOME/mutter/issues/219 We found the login screen is blur, with Huawei's chip. 05:00.0 VGA compatible controller [0300]: Huawei Technologies Co., Ltd. Hi1710 [iBMC Intelligent Management system chip w/VGA support] [19e5:1711] (rev 01) When we set the Wayland to disable, it could login. [daemon] # Uncoment the line below to force the login screen to use Xorg WaylandEnable=false To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1780076/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1780076] Re: 18.04 login screen is skewed/distorted (incorrect stride) when using hibmc_drm graphics
@seb128, Fine, let met try, could you tell me which one is used for packaging branch. Thanks! remotes/origin/ubuntu/cosmic remotes/origin/ubuntu/cosmic-devel remotes/origin/ubuntu/cosmic-proposed remotes/origin/applied/ubuntu/cosmic remotes/origin/applied/ubuntu/cosmic-devel remotes/origin/applied/ubuntu/cosmic-proposed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1780076 Title: 18.04 login screen is skewed/distorted (incorrect stride) when using hibmc_drm graphics Status in gdm3 package in Ubuntu: New Status in mesa package in Ubuntu: New Status in mutter package in Ubuntu: New Bug description: Upstream: https://gitlab.gnome.org/GNOME/mutter/issues/219 We found the login screen is blur, with Huawei's chip. 05:00.0 VGA compatible controller [0300]: Huawei Technologies Co., Ltd. Hi1710 [iBMC Intelligent Management system chip w/VGA support] [19e5:1711] (rev 01) When we set the Wayland to disable, it could login. [daemon] # Uncoment the line below to force the login screen to use Xorg WaylandEnable=false To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1780076/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1780076] Re: 18.04 login screen is skewed/distorted (incorrect stride) when using hibmc_drm graphics
Now the !38 was accepted too. https://gitlab.gnome.org/GNOME/gdm/merge_requests/38 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1780076 Title: 18.04 login screen is skewed/distorted (incorrect stride) when using hibmc_drm graphics Status in gdm3 package in Ubuntu: New Status in mesa package in Ubuntu: New Status in mutter package in Ubuntu: New Bug description: Upstream: https://gitlab.gnome.org/GNOME/mutter/issues/219 We found the login screen is blur, with Huawei's chip. 05:00.0 VGA compatible controller [0300]: Huawei Technologies Co., Ltd. Hi1710 [iBMC Intelligent Management system chip w/VGA support] [19e5:1711] (rev 01) When we set the Wayland to disable, it could login. [daemon] # Uncoment the line below to force the login screen to use Xorg WaylandEnable=false To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1780076/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1780076] Re: 18.04 login screen is skewed/distorted (incorrect stride) when using hibmc_drm graphics
I made two patches for upstream. Now the !35 was accepted, just wait for !38. https://gitlab.gnome.org/GNOME/gdm/merge_requests/35 https://gitlab.gnome.org/GNOME/gdm/merge_requests/38 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1780076 Title: 18.04 login screen is skewed/distorted (incorrect stride) when using hibmc_drm graphics Status in gdm3 package in Ubuntu: New Status in mesa package in Ubuntu: New Status in mutter package in Ubuntu: New Bug description: Upstream: https://gitlab.gnome.org/GNOME/mutter/issues/219 We found the login screen is blur, with Huawei's chip. 05:00.0 VGA compatible controller [0300]: Huawei Technologies Co., Ltd. Hi1710 [iBMC Intelligent Management system chip w/VGA support] [19e5:1711] (rev 01) When we set the Wayland to disable, it could login. [daemon] # Uncoment the line below to force the login screen to use Xorg WaylandEnable=false To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1780076/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1780076] Re: 18.04 login screen is skewed/distorted (incorrect stride) when using hibmc_drm graphics
@ubuntu-sponsors, Could you helped reviewed the 0001-Disable-wayland-for-Huawei- Hi1710-LP-1780076.patch for 18.10? Thanks! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1780076 Title: 18.04 login screen is skewed/distorted (incorrect stride) when using hibmc_drm graphics Status in gdm3 package in Ubuntu: New Status in mesa package in Ubuntu: New Status in mutter package in Ubuntu: New Bug description: Upstream: https://gitlab.gnome.org/GNOME/mutter/issues/219 We found the login screen is blur, with Huawei's chip. 05:00.0 VGA compatible controller [0300]: Huawei Technologies Co., Ltd. Hi1710 [iBMC Intelligent Management system chip w/VGA support] [19e5:1711] (rev 01) When we set the Wayland to disable, it could login. [daemon] # Uncoment the line below to force the login screen to use Xorg WaylandEnable=false To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1780076/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1780076] Re: 18.04 login screen is skewed/distorted (incorrect stride) when using hibmc_drm graphics
For 18.10, I made a patch for it. * Disable wayland for Huawei Hi1710. (LP: #1780076) + Add ubuntu_disable_wayland_huawei_chipsets.patch + gdm3.install: Fix udev path from /usr/lib/udev to lib/udev. And I my code is based on cosmic-devel. https://code.launchpad.net/~binli/ubuntu/+source/gdm3/+git/lp1780076 ** Patch added: "0001-Disable-wayland-for-Huawei-Hi1710-LP-1780076.patch" https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1780076/+attachment/5179560/+files/0001-Disable-wayland-for-Huawei-Hi1710-LP-1780076.patch -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1780076 Title: 18.04 login screen is skewed/distorted (incorrect stride) when using hibmc_drm graphics Status in gdm3 package in Ubuntu: New Status in mesa package in Ubuntu: New Status in mutter package in Ubuntu: New Bug description: Upstream: https://gitlab.gnome.org/GNOME/mutter/issues/219 We found the login screen is blur, with Huawei's chip. 05:00.0 VGA compatible controller [0300]: Huawei Technologies Co., Ltd. Hi1710 [iBMC Intelligent Management system chip w/VGA support] [19e5:1711] (rev 01) When we set the Wayland to disable, it could login. [daemon] # Uncoment the line below to force the login screen to use Xorg WaylandEnable=false To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1780076/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1780076] Re: 18.04 login screen is skewed/distorted (incorrect stride) when using hibmc_drm graphics
@Daniel, Got it, and the issue 412 was fixed. I will work on the patch today. Thanks a lot! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1780076 Title: 18.04 login screen is skewed/distorted (incorrect stride) when using hibmc_drm graphics Status in gdm3 package in Ubuntu: New Status in mesa package in Ubuntu: New Status in mutter package in Ubuntu: New Bug description: Upstream: https://gitlab.gnome.org/GNOME/mutter/issues/219 We found the login screen is blur, with Huawei's chip. 05:00.0 VGA compatible controller [0300]: Huawei Technologies Co., Ltd. Hi1710 [iBMC Intelligent Management system chip w/VGA support] [19e5:1711] (rev 01) When we set the Wayland to disable, it could login. [daemon] # Uncoment the line below to force the login screen to use Xorg WaylandEnable=false To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1780076/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1780076] Re: 18.04 login screen is skewed/distorted (incorrect stride) when using hibmc_drm graphics
@Daniel, Now this issue in my side is not related to https://gitlab.gnome.org/GNOME/mutter/merge_requests/160, I've updated the latest mutter(3.28.3-2~ubuntu18.04.1), this issue is still exist, and I tried to make it with small patch, but I'm failed. So could we used the patch in comment #7? Now I just found the gdm3 was updated to 3.28.3-0ubuntu18.04.1, the previous patch also need be changed. And I found the gdm-disable-wayland binary is missed, so I report an issue for it. https://gitlab.gnome.org/GNOME/gdm/issues/412 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1780076 Title: 18.04 login screen is skewed/distorted (incorrect stride) when using hibmc_drm graphics Status in gdm3 package in Ubuntu: New Status in mesa package in Ubuntu: New Status in mutter package in Ubuntu: New Bug description: Upstream: https://gitlab.gnome.org/GNOME/mutter/issues/219 We found the login screen is blur, with Huawei's chip. 05:00.0 VGA compatible controller [0300]: Huawei Technologies Co., Ltd. Hi1710 [iBMC Intelligent Management system chip w/VGA support] [19e5:1711] (rev 01) When we set the Wayland to disable, it could login. [daemon] # Uncoment the line below to force the login screen to use Xorg WaylandEnable=false To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1780076/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1780076] Re: 18.04 login screen is skewed/distorted (incorrect stride) when using hibmc_drm graphics
Talked with Jonas Ådahl, he suggest we try below patch, I will try it when back office. https://gitlab.gnome.org/GNOME/mutter/merge_requests/155 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1780076 Title: 18.04 login screen is skewed/distorted (incorrect stride) when using hibmc_drm graphics Status in gdm3 package in Ubuntu: New Status in mesa package in Ubuntu: New Status in mutter package in Ubuntu: New Bug description: We found the login screen is blur, with Huawei's chip. 05:00.0 VGA compatible controller [0300]: Huawei Technologies Co., Ltd. Hi1710 [iBMC Intelligent Management system chip w/VGA support] [19e5:1711] (rev 01) When we set the Wayland to disable, it could login. [daemon] # Uncoment the line below to force the login screen to use Xorg WaylandEnable=false To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1780076/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1780076] Re: 18.04 login screen is skewed/distorted (incorrect stride)
Daniel, Thanks for your help, I've report a new one. https://gitlab.gnome.org/GNOME/mutter/issues/219 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1780076 Title: 18.04 login screen is skewed/distorted (incorrect stride) Status in gdm3 package in Ubuntu: New Status in mesa package in Ubuntu: Incomplete Status in mutter package in Ubuntu: Incomplete Bug description: We found the login screen is blur, with Huawei's chip. 05:00.0 VGA compatible controller [0300]: Huawei Technologies Co., Ltd. Hi1710 [iBMC Intelligent Management system chip w/VGA support] [19e5:1711] (rev 01) When we set the Wayland to disable, it could login. [daemon] # Uncoment the line below to force the login screen to use Xorg WaylandEnable=false To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1780076/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1780076] Re: 18.04 login screen is skewed/distorted (incorrect stride)
Here is the log from Huawei arm server. Thanks! ** Attachment added: "lspci-k.log" https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1780076/+attachment/5161325/+files/lspci-k.log ** Changed in: gdm3 (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1780076 Title: 18.04 login screen is skewed/distorted (incorrect stride) Status in gdm3 package in Ubuntu: New Status in mesa package in Ubuntu: Incomplete Status in mutter package in Ubuntu: Incomplete Bug description: We found the login screen is blur, with Huawei's chip. 05:00.0 VGA compatible controller [0300]: Huawei Technologies Co., Ltd. Hi1710 [iBMC Intelligent Management system chip w/VGA support] [19e5:1711] (rev 01) When we set the Wayland to disable, it could login. [daemon] # Uncoment the line below to force the login screen to use Xorg WaylandEnable=false To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1780076/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1780076] Re: 18.04 login screen is skewed/distorted (incorrect stride)
Daniel, Thanks a lot! I will ask someone to help it. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1780076 Title: 18.04 login screen is skewed/distorted (incorrect stride) Status in gdm3 package in Ubuntu: Incomplete Status in mesa package in Ubuntu: Incomplete Status in mutter package in Ubuntu: Incomplete Bug description: We found the login screen is blur, with Huawei's chip. 05:00.0 VGA compatible controller [0300]: Huawei Technologies Co., Ltd. Hi1710 [iBMC Intelligent Management system chip w/VGA support] [19e5:1711] (rev 01) When we set the Wayland to disable, it could login. [daemon] # Uncoment the line below to force the login screen to use Xorg WaylandEnable=false To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1780076/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1780076] Re: 18.04 login screen is skewed/distorted (incorrect stride)
A new patch to disable Huawei chipsets in udev rules.
First, the udev rules was placed in wrong place. /usr/lib/udev/rules.d/
can't be read, we need push it into /lib/udev/rules.d/.
/usr/lib/udev/rules.d/61-gdm.rules => /lib/udev/rules.d/61-gdm.rules
Second, the rules need change the running time directory from /run/gdm
to /run/gdm3.
# disable Wayland on Hi1710 chipsets
ATTR{vendor}=="0x19e5", ATTR{device}=="0x1711", RUN+="/bin/sh -c '/bin/mkdir
/run/gdm3 ; /usr/bin/printf \"[daemon]\nWaylandEnable=false\" >>
/run/gdm3/custom.conf'"
** Patch added: "ubuntu_disable_wayland_huawei_chipsets.patch"
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1780076/+attachment/5160787/+files/ubuntu_disable_wayland_huawei_chipsets.patch
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1780076
Title:
18.04 login screen is skewed/distorted (incorrect stride)
Status in gdm3 package in Ubuntu:
Incomplete
Status in mesa package in Ubuntu:
Incomplete
Status in mutter package in Ubuntu:
Incomplete
Bug description:
We found the login screen is blur, with Huawei's chip.
05:00.0 VGA compatible controller [0300]: Huawei Technologies Co.,
Ltd. Hi1710 [iBMC Intelligent Management system chip w/VGA support]
[19e5:1711] (rev 01)
When we set the Wayland to disable, it could login.
[daemon]
# Uncoment the line below to force the login screen to use Xorg
WaylandEnable=false
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1780076/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1780076] Re: 18.04 login screen is skewed/distorted (incorrect stride)
Hi Daniel, Thanks for your review. I'm OoO and can't get it now. Will provide to you later. Thanks! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1780076 Title: 18.04 login screen is skewed/distorted (incorrect stride) Status in gdm3 package in Ubuntu: Incomplete Status in mesa package in Ubuntu: Incomplete Status in mutter package in Ubuntu: Incomplete Bug description: We found the login screen is blur, with Huawei's chip. 05:00.0 VGA compatible controller [0300]: Huawei Technologies Co., Ltd. Hi1710 [iBMC Intelligent Management system chip w/VGA support] [19e5:1711] (rev 01) When we set the Wayland to disable, it could login. [daemon] # Uncoment the line below to force the login screen to use Xorg WaylandEnable=false To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1780076/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1664880] Re: sed license mismatch
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=281638 sed (4.1.2-4) unstable; urgency=medium * Update copyright file to reflect an accurate URL for upstream source, current Debian maintainer, and the fact that the info manual is under the GNU FDL. closes: #281638. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to sed in Ubuntu. https://bugs.launchpad.net/bugs/1664880 Title: sed license mismatch Status in sed package in Ubuntu: New Bug description: The license specified in the /usr/share/doc/sed/copyright states that sed is GPLv2, whereas the license specified in "sed --version" is GPLv3. sed version: sed_4.2.2-4ubuntu1 ubuntu: 14.04, trusty To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sed/+bug/1664880/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1664880] Re: sed license mismatch
Now in sed-4.4 this issue was fixed by packager. Here is the patch. $ diff -Nuar sed-4.2.2/debian/copyright sed-4.4/debian/copyright --- sed-4.2.2/debian/copyright 2009-08-01 12:57:01.0 +0800 +++ sed-4.4/debian/copyright 2017-01-05 09:31:41.0 +0800 @@ -4,18 +4,18 @@ This package was assembled from sources obtained from: ftp://ftp.gnu.org/gnu/sed/ -It is currently maintained by Clint Adams +It is currently maintained by Clint Adams -Copyright: 2003 - Free Software Foundation, Inc. +Copyright: 1989,90,91,92,93,94,95,98,99,2002,2003,2006,2008,2009,2010 Free Software Foundation, Inc. GNU sed is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free -Software Foundation; either version 2, or (at your option) any later +Software Foundation; either version 3, or (at your option) any later version. On Debian GNU/Linux systems you can find a copy of the GPL in -/usr/share/common-licenses/GPL +/usr/share/common-licenses/GPL-3 The sed info manual is released under the terms of the GNU Free Documentation License as published by the Free Software Foundation; -either version 1.1, or (at your option) any later version. +either version 1.3, or (at your option) any later version. ** Bug watch added: Debian Bug tracker #281638 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=281638 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to sed in Ubuntu. https://bugs.launchpad.net/bugs/1664880 Title: sed license mismatch Status in sed package in Ubuntu: New Bug description: The license specified in the /usr/share/doc/sed/copyright states that sed is GPLv2, whereas the license specified in "sed --version" is GPLv3. sed version: sed_4.2.2-4ubuntu1 ubuntu: 14.04, trusty To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sed/+bug/1664880/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1664880] [NEW] sed license mismatch
Public bug reported: The license specified in the /usr/share/doc/sed/copyright states that sed is GPLv2, whereas the license specified in "sed --version" is GPLv3. sed version: sed_4.2.2-4ubuntu1 ubuntu: 14.04, trusty ** Affects: sed (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to sed in Ubuntu. https://bugs.launchpad.net/bugs/1664880 Title: sed license mismatch Status in sed package in Ubuntu: New Bug description: The license specified in the /usr/share/doc/sed/copyright states that sed is GPLv2, whereas the license specified in "sed --version" is GPLv3. sed version: sed_4.2.2-4ubuntu1 ubuntu: 14.04, trusty To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sed/+bug/1664880/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1664880] Re: sed license mismatch
Now in sed-4.4 this issue was fixed by packager, I think it's not easy to push it into ubuntu updates channel, I will try to push it. For siena, I could pushed it into our production repo first. $ diff -Nuar sed-4.2.2/debian/copyright sed-4.4/debian/copyright --- sed-4.2.2/debian/copyright 2009-08-01 12:57:01.0 +0800 +++ sed-4.4/debian/copyright 2017-01-05 09:31:41.0 +0800 @@ -4,18 +4,18 @@ This package was assembled from sources obtained from: ftp://ftp.gnu.org/gnu/sed/ -It is currently maintained by Clint Adams +It is currently maintained by Clint Adams -Copyright: 2003 - Free Software Foundation, Inc. +Copyright: 1989,90,91,92,93,94,95,98,99,2002,2003,2006,2008,2009,2010 Free Software Foundation, Inc. GNU sed is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free -Software Foundation; either version 2, or (at your option) any later +Software Foundation; either version 3, or (at your option) any later version. On Debian GNU/Linux systems you can find a copy of the GPL in -/usr/share/common-licenses/GPL +/usr/share/common-licenses/GPL-3 The sed info manual is released under the terms of the GNU Free Documentation License as published by the Free Software Foundation; -either version 1.1, or (at your option) any later version. +either version 1.3, or (at your option) any later version. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to sed in Ubuntu. https://bugs.launchpad.net/bugs/1664880 Title: sed license mismatch Status in sed package in Ubuntu: New Bug description: The license specified in the /usr/share/doc/sed/copyright states that sed is GPLv2, whereas the license specified in "sed --version" is GPLv3. sed version: sed_4.2.2-4ubuntu1 ubuntu: 14.04, trusty To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sed/+bug/1664880/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1643812] Re: There is no entry in 'Play sound through' list when plug in headset jack [8086:9d70].
@themuso, Done, I'd updated the description with the template of SRU. Thanks a lot! ** Description changed: + [Impact] + + * When plug in headset jack, you can't view any item in unity-control- + center, so you can't change the volume. + + * For the situation of one pulseaudio port has 2 or more jacks, it will + bring some change, in the past, if one of the jacks is plugged and other + jacks are not plugged, the pulseaudio will print out "Availability of + port '%s' is inconsistent!" and will not set this pulseaudio port to + available, this is a bug for pulseaudio. + + * After applying this patch, this issue can be addressed by this patch. + + [Test Case] + + * Reproduce steps: 1. Install 14.04.5 image on P50s 2. Login system 3. $ sudo apt-get update 4. $ apt-get dist-upgrade sudo apt-get install --install-recommends linux-generic-lts-xenial xserver-xorg-core-lts-xenial xserver-xorg-lts-xenial xserver-xorg-video-all-lts-xenial xserver-xorg-input-all-lts-xenial libwayland-egl1-mesa-lts-xenial 5. Reboot the system 6. Login system 7. Open Sound setting window 8. Plug headset jack, unplug headset jack. - The kernel is 4.4.0-47, and the pulseaudio is 1:4.0-0ubuntu1.1 + [Regression Potential] + + * For most of the situations like one pulseaudio port only has one + jack, this patch will not bring any change. So there is no potential + regression. + + [Other Info] + + * The kernel is 4.4.0-47, and the pulseaudio is 1:4.0-0ubuntu1.1 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1643812 Title: There is no entry in 'Play sound through' list when plug in headset jack [8086:9d70]. Status in HWE Next: New Status in pulseaudio package in Ubuntu: New Status in pulseaudio source package in Trusty: New Bug description: [Impact] * When plug in headset jack, you can't view any item in unity- control-center, so you can't change the volume. * For the situation of one pulseaudio port has 2 or more jacks, it will bring some change, in the past, if one of the jacks is plugged and other jacks are not plugged, the pulseaudio will print out "Availability of port '%s' is inconsistent!" and will not set this pulseaudio port to available, this is a bug for pulseaudio. * After applying this patch, this issue can be addressed by this patch. [Test Case] * Reproduce steps: 1. Install 14.04.5 image on P50s 2. Login system 3. $ sudo apt-get update 4. $ apt-get dist-upgrade sudo apt-get install --install-recommends linux-generic-lts-xenial xserver-xorg-core-lts-xenial xserver-xorg-lts-xenial xserver-xorg-video-all-lts-xenial xserver-xorg-input-all-lts-xenial libwayland-egl1-mesa-lts-xenial 5. Reboot the system 6. Login system 7. Open Sound setting window 8. Plug headset jack, unplug headset jack. [Regression Potential] * For most of the situations like one pulseaudio port only has one jack, this patch will not bring any change. So there is no potential regression. [Other Info] * The kernel is 4.4.0-47, and the pulseaudio is 1:4.0-0ubuntu1.1 To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1643812/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1643812] Re: There is no entry in 'Play sound through' list when plug in headset jack [8086:9d70].
@themuso I checked the trusty-propsed channel, there are still not new pulseaduio, what's the status of this issue? Thanks a lot! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1643812 Title: There is no entry in 'Play sound through' list when plug in headset jack [8086:9d70]. Status in HWE Next: New Status in pulseaudio package in Ubuntu: New Status in pulseaudio source package in Trusty: New Bug description: 1. Install 14.04.5 image on P50s 2. Login system 3. $ sudo apt-get update 4. $ apt-get dist-upgrade sudo apt-get install --install-recommends linux-generic-lts-xenial xserver-xorg-core-lts-xenial xserver-xorg-lts-xenial xserver-xorg-video-all-lts-xenial xserver-xorg-input-all-lts-xenial libwayland-egl1-mesa-lts-xenial 5. Reboot the system 6. Login system 7. Open Sound setting window 8. Plug headset jack, unplug headset jack. The kernel is 4.4.0-47, and the pulseaudio is 1:4.0-0ubuntu1.1 To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1643812/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1643812] Re: There is no entry in 'Play sound through' list when plug in headset jack [8086:9d70].
Here is the patch. ** Patch added: "multiple_jacks.patch" https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1643812/+attachment/4781414/+files/multiple_jacks.patch -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1643812 Title: There is no entry in 'Play sound through' list when plug in headset jack [8086:9d70]. Status in pulseaudio package in Ubuntu: New Bug description: 1. Install 14.04.5 image on P50s 2. Login system 3. $ sudo apt-get update 4. $ apt-get dist-upgrade sudo apt-get install --install-recommends linux-generic-lts-xenial xserver-xorg-core-lts-xenial xserver-xorg-lts-xenial xserver-xorg-video-all-lts-xenial xserver-xorg-input-all-lts-xenial libwayland-egl1-mesa-lts-xenial 5. Reboot the system 6. Login system 7. Open Sound setting window 8. Plug headset jack, unplug headset jack. The kernel is 4.4.0-47, and the pulseaudio is 1:4.0-0ubuntu1.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1643812/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1643812] Re: There is no entry in 'Play sound through' list when plug in headset jack [8086:9d70].
I built the pulseaudio with the patch in below, it works fine after test. commit d5fec4ca7af9241d0c2ae17df40d0fb1c18c74a0 Author: Sjoerd Simons Date: Sun Nov 16 23:15:50 2014 +0100 Alsa: Correct port availability with multiple jacks In case there are two independent jacks for one port (e.g. Dock Headphone Jack and Headphone Jack), the availability ends up being incorrect if the first one was _NO (not plugged) and the second gets _YES (plugged). Also pulse complains about the state being inconsistent which isn't true. Fix this by preferring more precise states (yes/no) over unknown and yes over others. However in case a plugged jack makes the port unavailable let that overrule everything else. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1643812 Title: There is no entry in 'Play sound through' list when plug in headset jack [8086:9d70]. Status in pulseaudio package in Ubuntu: New Bug description: 1. Install 14.04.5 image on P50s 2. Login system 3. $ sudo apt-get update 4. $ apt-get dist-upgrade sudo apt-get install --install-recommends linux-generic-lts-xenial xserver-xorg-core-lts-xenial xserver-xorg-lts-xenial xserver-xorg-video-all-lts-xenial xserver-xorg-input-all-lts-xenial libwayland-egl1-mesa-lts-xenial 5. Reboot the system 6. Login system 7. Open Sound setting window 8. Plug headset jack, unplug headset jack. The kernel is 4.4.0-47, and the pulseaudio is 1:4.0-0ubuntu1.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1643812/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1643812] [NEW] There is no entry in 'Play sound through' list when plug in headset jack [8086:9d70].
Public bug reported: 1. Install 14.04.5 image on P50s 2. Login system 3. $ sudo apt-get update 4. $ apt-get dist-upgrade sudo apt-get install --install-recommends linux-generic-lts-xenial xserver-xorg-core-lts-xenial xserver-xorg-lts-xenial xserver-xorg-video-all-lts-xenial xserver-xorg-input-all-lts-xenial libwayland-egl1-mesa-lts-xenial 5. Reboot the system 6. Login system 7. Open Sound setting window 8. Plug headset jack, unplug headset jack. The kernel is 4.4.0-47, and the pulseaudio is 1:4.0-0ubuntu1.1 ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1643812 Title: There is no entry in 'Play sound through' list when plug in headset jack [8086:9d70]. Status in pulseaudio package in Ubuntu: New Bug description: 1. Install 14.04.5 image on P50s 2. Login system 3. $ sudo apt-get update 4. $ apt-get dist-upgrade sudo apt-get install --install-recommends linux-generic-lts-xenial xserver-xorg-core-lts-xenial xserver-xorg-lts-xenial xserver-xorg-video-all-lts-xenial xserver-xorg-input-all-lts-xenial libwayland-egl1-mesa-lts-xenial 5. Reboot the system 6. Login system 7. Open Sound setting window 8. Plug headset jack, unplug headset jack. The kernel is 4.4.0-47, and the pulseaudio is 1:4.0-0ubuntu1.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1643812/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1625023] Re: switch to systemd on ubuntu phone xenial
I tried to install the lxc-android-config, but looks there are some errors. Preparing to unpack lxc-android-config_0.230+16.04.20160728-0ubuntu1_all.deb ... Unpacking lxc-android-config (0.230+16.04.20160728-0ubuntu1) over (0.230+16.04.20160728-0ubuntu1) ... dpkg: error processing archive lxc-android-config_0.230+16.04.20160728-0ubuntu1_all.deb (--install): unable to make backup link of './var/lib/lxc/android/pre-start.d/30-no-surface-flinger' before installing new version: Invalid cross-device link dpkg-deb (subprocess): decompressing archive member: lzma write error: Broken pipe dpkg-deb: error: subprocess returned error exit status 2 Errors were encountered while processing: lxc-android-config_0.230+16.04.20160728-0ubuntu1_all.deb -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-touch-meta in Ubuntu. https://bugs.launchpad.net/bugs/1625023 Title: switch to systemd on ubuntu phone xenial Status in Canonical System Image: Confirmed Status in android-tools package in Ubuntu: Confirmed Status in lxc-android-config package in Ubuntu: Confirmed Status in ubuntu-touch-meta package in Ubuntu: Confirmed Bug description: Snappy heavily rely on systemd system session and xenial has systemd by default. [steps to construct systemd-based avila] 1. flash images built from xenial branch [1]. This should gives a working xenial+upstart avila. 2. Install systemd-sysv rather than upstart-sysv (Bug 1625023) 2.1. rebuild latest ubuntu-touch package from source [2] with patch [3] applied. 2.2. download latest systemd-sysv package [4]. 2.3. dpkg -i ubuntu-touch_*.deb systemd-sysv_*.deb 3. Install android-tools-adbd for systemd (Bug 1627613) 3.1. download prebuilt package [5] or recompile it from source [6] with patch [7] applied. 3.2. Install the package from Terminal app because it will break adb connection and interrupt the installation process leaving a very bad state of the package. 4. Install prebuilt lxc-android-config package [8] or just correct its systemd service file by hand as the merge proposal [9] does. (Bug 1625445, bug 1625916 and bug 1626012). 5. Reboot. [1]: https://code.launchpad.net/~avila-private-team/avila-private/+git/platform_manifest/+ref/xenial [2]: http://ppa.launchpad.net/ci-train-ppa-service/stable-phone-overlay/ubuntu/pool/main/u/ubuntu-touch-meta/ [3]: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1625023/+attachment/4744047/+files/0001-depends-on-systemd-sysv-instead.patch [4]: http://ppa.launchpad.net/ci-train-ppa-service/stable-phone-overlay/ubuntu/pool/main/s/systemd/ [5]: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1625023/+attachment/4744111/+files/android-tools-adbd_5.1.1r36+git20160322-0ubuntu3.1~overlay1_arm64.deb [6]: http://ppa.launchpad.net/ci-train-ppa-service/stable-phone-overlay/ubuntu/pool/main/a/android-tools/ [7]: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1625023/+attachment/4746154/+files/force-adbd.patch [8]: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1625023/+attachment/4746148/+files/lxc-android-config_0.230+16.04.20160728-0ubuntu1_all.deb [9]: https://code.launchpad.net/~vicamo/lxc-android-config/fix-systemd-service-startup/+merge/306435 To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1625023/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1572041] [NEW] Can't create click target for armhf
Public bug reported: sudo click chroot -a armhf -f ubuntu-sdk-15.04 create The following packages have unmet dependencies: ubuntu-sdk-libs:armhf : Depends: ubuntu-html5-container:armhf E: Unable to correct problems, you have held broken packages. Command returned 100: schroot -u root -c source:click-ubuntu-sdk-15.04-armhf -- /finish.sh Traceback (most recent call last): File "/usr/bin/click", line 110, in sys.exit(main()) File "/usr/bin/click", line 106, in main return mod.run(args) File "/usr/lib/python3/dist-packages/click/commands/chroot.py", line 266, in run return args.func(parser, args) File "/usr/lib/python3/dist-packages/click/commands/chroot.py", line 68, in create return chroot.create(args.keep_broken_chroot) File "/usr/lib/python3/dist-packages/click/chroot.py", line 599, in create self.full_name, ret_code)) click.chroot.ClickChrootException: Failed to create chroot 'click-ubuntu-sdk-15.04-armhf' (exit status 100) ** Affects: click (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to click in Ubuntu. https://bugs.launchpad.net/bugs/1572041 Title: Can't create click target for armhf Status in click package in Ubuntu: New Bug description: sudo click chroot -a armhf -f ubuntu-sdk-15.04 create The following packages have unmet dependencies: ubuntu-sdk-libs:armhf : Depends: ubuntu-html5-container:armhf E: Unable to correct problems, you have held broken packages. Command returned 100: schroot -u root -c source:click-ubuntu-sdk-15.04-armhf -- /finish.sh Traceback (most recent call last): File "/usr/bin/click", line 110, in sys.exit(main()) File "/usr/bin/click", line 106, in main return mod.run(args) File "/usr/lib/python3/dist-packages/click/commands/chroot.py", line 266, in run return args.func(parser, args) File "/usr/lib/python3/dist-packages/click/commands/chroot.py", line 68, in create return chroot.create(args.keep_broken_chroot) File "/usr/lib/python3/dist-packages/click/chroot.py", line 599, in create self.full_name, ret_code)) click.chroot.ClickChrootException: Failed to create chroot 'click-ubuntu-sdk-15.04-armhf' (exit status 100) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/click/+bug/1572041/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
