Here's Salsa MR: https://salsa.debian.org/gnome-team/gnome-initial-
setup/-/merge_requests/31
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2067979
Title:
Language selection is skipped for new
Here's the debdiff (against noble, since I am testing on noble and we
plan to move away from g-i-s on oracular or 26.04 at least) that enables
language page, and fixes segfault when language is selected.
The reason why it is not using ubuntu_page_table, is that at the time it
runs
OK I tried to install g-i-s within the installation of OEM image, now it went
like:
- Language Selection
- Ubuntu Pro
- Metrics Permission
- User Account
- Password
- Store
- Enter Desktop prompt
It is missing location permission (if we don't disable that) and timezone
selection,
and it didn't
> What do you mean? The language and welcome pages are different, they
cannot be added one inside another.
Sorry I don't mean the welcome page, I mean another gnome-initial-setup
screen when user is greeted into the desktop
--
You received this bug notification because you are a member of
Correct, we have most (if not all) language packs installed instead of
having only the one chosen.
However I also discovered that the language packs in the image are not
installed as many as we thought to be, but this is out of scope of this
issue.
--
You received this bug notification because
That MR fixed the missing language page, but also added language page in
the desktop welcome. I suppose that "ubuntu_page_table" is used when
user enters the desktop for the first time.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Description changed:
Cannot get timezone automatically recognized despite geoclue is
available in the desktop.
Reproduction steps:
1. Install stock Ubuntu desktop
- 2. Change /etc/geoclue/geoclue.conf to use Google as source (I took API key
from Arch Linux for testing purpose, see
> Just for confirmation: In your OEM case, gnome-initial-setup currently
does ask for account and password creation, right?
Affirmative. There are realname/username and password/confirm pages.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
** Attachment added: "lp2068000-journal"
https://bugs.launchpad.net/ubuntu/+source/gnome-initial-setup/+bug/2068000/+attachment/5785790/+files/lp2068000-journal
** Description changed:
Cannot get timezone automatically recognized despite geoclue is
available in the desktop.
Public bug reported:
Cannot get timezone automatically recognized despite geoclue is
available in the desktop.
Reproduction steps:
1. Install stock Ubuntu desktop
2. Change /etc/geoclue/geoclue.conf to use Google as source (I took API key
from Arch Linux for testing purpose, see
Public bug reported:
For OEM use case, we need language selection in the gnome-initial-setup
account creation. We created an autoinstall to install Ubuntu that does
not create a user, so that it boots into first boot screen when booting
into the system:
user-data:
users: {}
I found that
** Summary changed:
- When setting up RAID installation, curtin tried to run partprobe on imsm
container and failed
+ When setting up RAID installation, curtin failed to wipe imsm RAID block
device
** Summary changed:
- When setting up RAID installation, curtin failed to wipe imsm RAID block
Public bug reported:
The following error in curtin is captured when using ubuntu-desktop-
installer to install noble:
Running command ['partprobe', '/dev/md127'] with allowed return codes
[0, 1] (capture=False)
Warning: Error fsyncing/closing /dev/md127: Input/output error
I retried these configurations in cloud-init 24.1.2-0ubuntu1 in noble
and this seems to be resolved.
Thanks, and sorry for the noise!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2047796
Title:
** Changed in: oem-priority
Assignee: (unassigned) => Yao Wei (medicalwei)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2056730
Title:
noble-daily (20240310) cannot be installed offl
** Also affects: oem-priority
Importance: Undecided
Status: New
** Changed in: oem-priority
Importance: Undecided => Critical
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2056730
Attach oem-somerville-delibird-meta_20.04~ubuntu1.debdiff by oem-scripts
1.40.
** Summary changed:
- [DRAFT][MIR] oem-somerville-delibird-meta
+ [MIR] oem-somerville-delibird-meta
** Description changed:
- [DRAFT][Availability]
+ [Background]
+
+ Please see
Thanks. These are reported by our OEM customers, and (IMO more
importantly) is visible during installation, so it has certain kind of
priority here.
I am trying to do the part in Traditional Chinese translations
(unreviewed), and calling for translation should be quite helpful.
--
You received
Could you report which version of Ubuntu and kitty are you using?
Thanks.
** Bug watch added: Debian Bug tracker #990316
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=990316
** Also affects: kitty (Debian) via
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=990316
Importance:
Public bug reported:
Because there was a change that made the string "wi-fi" to "Wi-Fi"
(changeset 2a8983ca), this made all translations involving with "wi-fi"
unable to match the translation string.
diff --git a/debian/ubiquity.templates b/debian/ubiquity.templates
index c7ad49cb9c..4c4a8a840b
** Attachment added: "lp1967067-bt-test.tar.xz"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1967067/+attachment/5579243/+files/lp1967067-bt-test.tar.xz
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
With linux-oem-5.14/5.14.0-1033.36, this issue is not reproducible
within 20 cold reboots.
A script is used to run rtcwake to cold boot 20 times and attach
`bluetoothctl scan on` result to a log file. If the bluetooth device
cannot be probed, the scan should output "No default controller
Updating debdiff for focal to correct the bug number and use the
upstream fix.
** Patch added: "iio-sensor-proxy_2.8-1ubuntu2.debdiff"
https://bugs.launchpad.net/ubuntu/+source/iio-sensor-proxy/+bug/1963628/+attachment/5575435/+files/iio-sensor-proxy_2.8-1ubuntu2.debdiff
--
You received
Can confirm that 5.14.0-9031.34+exp.62 fixed this bug. cold-boot 50
times by script and BT can scan normally in all reboots.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1967067
Title:
WCN6856 BT
Could you give us steps to reproduce? It works for me after adding
Others/Chewing in keyboard setup in the jammy VM.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1966356
Title:
ibus input method
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1963628
Title:
Force IIO_SENSOR_PROXY_TYPE to iio-buffer-als for some Dell models
To manage notifications about this bug go to:
I'd like to add another debdiff to jammy which resolves the issue from
the patch upstream
Upstream MR: https://gitlab.freedesktop.org/hadess/iio-sensor-
proxy/-/merge_requests/355
** Patch added: "iio-sensor-proxy_3.3-0ubuntu6.debdiff"
The following tests has been done:
1. Use a clean install image, and enable -proposed repo, run `ubuntu-drivers
list`, oem-somerville-hotpie-meta is shown
2. `ubuntu-drivers install` installs oem-somerville-hotpie-meta 20.04~ubuntu1,
and then bootstrapped into oem-somerville-hotpie-meta
The following tests has been done:
1. Use a clean install image, and enable -proposed repo, run `ubuntu-drivers
list`, oem-somerville-ellaria-meta is shown
2. `ubuntu-drivers install` installs oem-somerville-ellaria-meta 20.04~ubuntu1,
and then bootstrapped into oem-somerville-ellaria-meta
The following tests has been done
1. ubuntu-drivers list-oem lists this package on the target platform
2. apt install oem-somerville-matira-5-7-meta can install the package, and can
be upgraded into the one in the oem archive.
3. Installed oem-somerville-matira-5-7-meta through `ubuntu-drivers
Attach oem-somerville-zuma-p-meta_20.04~ubuntu1.debdiff by oem-scripts
1.29.
** Patch added: "oem-somerville-zuma-p-meta_20.04~ubuntu1.debdiff"
https://bugs.launchpad.net/bugs/1920206/+attachment/5566384/+files/oem-somerville-zuma-p-meta_20.04~ubuntu1.debdiff
** Tags added: oem-needs-upload
** Tags removed: oem-scripts-0.8
** Tags added: oem-scripts-1.29
** Changed in: oem-priority
Status: Confirmed => Fix Committed
** Changed in: ubuntu
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Checked the following:
1. Test that `ubuntu-drivers list-oem` lists the meta-package on the
relevant hardware
2. Test that fully installing the meta-package (upgrading to the OEM
archive if relevant) works properly on the hardware
3. Do an offline install. Boot the system. Run
> isn't that the real issue? is that an hardware or firmware bug? could
it be fixed rather than worked around in udev rules?
It's their hardware limitation that vendors are unable to handle.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
This is debdiff for iio-sensor-proxy for jammy, which is also based on
the same version in impish.
** Patch added: "iio-sensor-proxy_3.3-0ubuntu4.debdiff"
https://bugs.launchpad.net/ubuntu/+source/iio-sensor-proxy/+bug/1963628/+attachment/5565596/+files/iio-sensor-proxy_3.3-0ubuntu4.debdiff
This is debdiff for iio-sensor-proxy for focal
** Patch added: "iio-sensor-proxy_2.8-1ubuntu2.debdiff"
https://bugs.launchpad.net/ubuntu/+source/iio-sensor-proxy/+bug/1963628/+attachment/5565591/+files/iio-sensor-proxy_2.8-1ubuntu2.debdiff
--
You received this bug notification because you
Public bug reported:
We are encountering issues, that when enabling some Dell laptops, the readings
from iio-poll-als are unstable, or could freeze on certain value. On these
systems they have ENV{IIO_SENSOR_PROXY_TYPE}="iio-poll-als iio-buffer-als", and
removing iio-poll-als makes reading
Attaching debdiff from 20.04~ubuntu1 to 20.04~ubuntu2
** Patch added: "oem-somerville-matira-5-7-meta_20.04~ubuntu2.debdiff"
https://bugs.launchpad.net/oem-priority/+bug/1921907/+attachment/5565427/+files/oem-somerville-matira-5-7-meta_20.04~ubuntu2.debdiff
** Changed in: ubuntu
With Linux kernel 5.14.0-1024-oem and linux-firmware 1.187.27 (in
-proposed), it is confirmed that both WiFi and Bluetooth on WCN6856 A00
can be probed and used.
Excerpt from dmesg:
[6.188795] kernel: ath11k_pci :02:00.0: BAR 0: assigned [mem
0x7520-0x753f 64bit]
[6.188815]
** Tags removed: verification-failed verification-failed-focal
** Tags added: verification-needed verification-needed-focal
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1921907
Title:
[MIR]
There are missing BIOS IDs in this package. We are attaching another
with missing IDs added.
** Tags removed: verification-needed verification-needed-focal
** Tags added: verification-failed verification-failed-focal
--
You received this bug notification because you are a member of Ubuntu
Confirmed that after enabling focal-proposed:
1. `ubuntu-drivers list-oem` lists the package `oem-stella.cmit-deoxys-meta`
2. `ubuntu-drivers install` installs the package `oem-stella.cmit-deoxys-meta`
3. Clean install stock Ubuntu then enable focal-proposed, update-manager offers
installation
** Tags removed: verification-needed verification-needed-focal
verification-needed-impish
** Tags added: verification-done verification-done-focal
verification-done-impish
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Tested on SKU 0A36 (Latitude 7420) and is PASS for both focal and
impish.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1943561
Title:
Add ACCEL_LOCATION=base property for 6 Dell clamshell models
Tested on SKU 0B0B for both impish and focal. Both fixed. Waiting for
results from other SKUs.
The following logs are from impish:
# before upgrade udev
ubuntu@CANONICALID:~$ cat /sys/devices/virtual/dmi/id/product_sku
0B0B
ubuntu@CANONICALID:~$ dpkg -l udev
Could you try updating the BIOS firmware, and see whether this issue is
still reproducible?
I cannot observe the issue with BIOS firmware version 1.13.0 with
docking station DA310.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Attach oem-stella.cmit-deoxys-meta_20.04~ubuntu1.debdiff by oem-scripts
1.25.
** Changed in: oem-priority
Status: In Progress => Fix Committed
** Changed in: ubuntu
Status: New => Confirmed
** Patch removed: "oem-stella.cmit-deoxys-meta_20.04~ubuntu1.debdiff"
> Could you please clarify this situation for Impish, or ideally provide
a debdiff as you did for the other series? Thanks!
After looking into linux-source in impish, I can determine that it
should be safe removing the modalias names. The reply saying that it had
regression was my mistake.
--
** Attachment added: "lp1952823.webm"
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-470/+bug/1952823/+attachment/5544516/+files/lp1952823.webm
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Description changed:
[Summary]
- The system screen turns on for a moment after entering suspend.
+ The screen turns on for a moment when laptop is entering suspend.
This issue happens on Dell Latitude 5421.
[Steps to reproduce]
1. Enter suspend via power menu
2. Observe the
** Tags added: oem-priority originate-from-1952020 somerville
** Tags added: originate-from-1945730
** Tags added: originate-from-1949668
** Tags added: originate-from-1947975
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Description changed:
[Summary]
The system screen turns on for a moment after entering suspend.
This issue happens on Dell Latitude 5421.
[Steps to reproduce]
1. Enter suspend via power menu
2. Observe the display
(Note that `rtcwake` may not able to reproduce this issue.
** Attachment added: "nvidia-bug-report.log.gz"
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-470/+bug/1952823/+attachment/5544481/+files/nvidia-bug-report.log.gz
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
[Summary]
The system screen turns on for a moment after entering suspend.
This issue happens on Dell Latitude 5421.
[Steps to reproduce]
1. Enter suspend via power menu
2. Observe the display
(Note that `rtcwake` may not able to reproduce this issue. `systemctl
suspend`
** Tags added: originate-from-1947661
** Tags added: originate-from-1947678
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1951861
Title:
Fix non-working e1000e device after resume
To manage
** Tags added: originate-from-1933628
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1951667
Title:
[SRU] pulseaudio: restore hdmi audio be active output after resume
To manage notifications about
Verified pass on focal that the system can enter PC10 and SLP_S0.
On 5.14.0-1007-oem:
turbostat --quiet -S --show Pkg%pc2,Pkg%pc3,Pk%pc10,CPU%LPI,SYS%LPI
rtcwake -m freeze -s 15 | tee s0ix-diag.txt
rtcwake: assuming RTC uses UTC ...
rtcwake: wakeup from "freeze" using /dev/rtc0 at Thu Nov 11
Public bug reported:
This issue is found in usb-creator 0.3.11 in impish.
I found that creating USB disks in GNOME Disks is 2x faster than Startup
Disk Creator, and here's the comparison:
Startup Disk Creator: 1:52
GNOME Disks: 0:37
With a Sandisk Extreme Pro USB drive (CZ880) and a 4.0G image
Any updates to this SRU? What's the expected date to include this patch?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1943561
Title:
Add ACCEL_LOCATION=base property for 6 Dell clamshell models
** Tags added: oem-needs-upload
** Changed in: oem-priority
Status: Confirmed => Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1945186
Title:
Update the hardware support for HP Z2
** Summary changed:
- [DRAFT] Update the hardware support for HP Z2 Mini G5 Workstation, SFF G5
Workstation, TWR G5 Workstation in oem-stella.cmit-ivysaur-meta
+ Update the hardware support for HP Z2 Mini G5 Workstation, SFF G5
Workstation, TWR G5 Workstation in oem-stella.cmit-ivysaur-meta
**
** Changed in: oem-priority
Status: In Progress => New
** Changed in: systemd (Ubuntu)
Status: In Progress => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1943561
Title:
Add
New SRU bug has been opened at LP: #1943561
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1938259
Title:
Add ACCEL_LOCATION=base property for Dell clamshell models
To manage notifications about
** Changed in: systemd (Ubuntu)
Status: New => In Progress
** Changed in: oem-priority
Status: New => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1943561
Title:
Add
** Changed in: oem-priority
Status: New => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1938259
Title:
Add ACCEL_LOCATION=base property for Dell clamshell models
To manage
** Patch added: "debdiff for hirsute from 247.3-3ubuntu3.6"
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1943561/+attachment/5525169/+files/systemd_247.3-3ubuntu3.6-247.3-3ubuntu3.7.debdiff
** Tags added: oem-priority originate-from-1895110 somerville
** Tags added:
** Patch added: "debdiff for focal from 245.4-4ubuntu3.13"
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1943561/+attachment/5525168/+files/systemd_245.4-4ubuntu3.13-245.4-4ubuntu3.14.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** Description changed:
This hwdb update is to avoid unwanted screen rotation when tilting the
laptop.
+
+ This is the update to the previously rolled back SRU LP: #1938259
[Impact]
* This fixes unwanted rotations on certain Dell clamshell laptop models
with accelerometer.
Public bug reported:
This hwdb update is to avoid unwanted screen rotation when tilting the
laptop.
[Impact]
* This fixes unwanted rotations on certain Dell clamshell laptop models
with accelerometer.
[Test Plan]
* On Dell laptops with model SKU 0A36, 0A3E, 0B09, 0B0B, 0B0D, 0B11, install
** Tags added: originate-from-1942834
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1930754
Title:
e1000e extremly slow
To manage notifications about this bug go to:
** Tags added: fossa-edge-staging
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1930754
Title:
e1000e extremly slow
To manage notifications about this bug go to:
We found that Dell Latitude 7420 is not actually fixed, and may cause
Impish to have regression due to the removal of the product name
modalias.
** Changed in: systemd (Ubuntu Focal)
Status: Fix Committed => In Progress
** Changed in: systemd (Ubuntu Hirsute)
Status: Fix Committed
** Tags added: verification-failed-focal
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1938259
Title:
Add ACCEL_LOCATION=base property for Dell clamshell models
To manage notifications about this
Is it possible to respin the SRU for now? I need to correct the sku
number, that 0B0B isn't correct one. The correct one is 0A36.
I will upstream the fix first.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Splitting RTX A5000 from Dell to LP: #1942080
** Tags removed: originate-from-1941823 somerville
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1940262
Title:
The modalias in 470 is not compatible
Public bug reported:
Split from bug LP: #1940262
The following modalias of RTX A5000 (notably, for Dell OEM) is missing:
pci:v10DEd2231sv1028sd147Ebc03sc00i00
This results in ubuntu-drivers not suggesting nvidia-driver-470.
** Affects: oem-priority
Importance: Undecided
Reuploading the script
** Attachment removed: "nvidia_supported"
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-470/+bug/1940262/+attachment/5521045/+files/nvidia_supported
** Attachment added: "nvidia_supported"
** Tags added: originate-from-1941823 somerville
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1940262
Title:
The modalias in 470 is not compatible to 460
To manage notifications about this bug go
I would like to propose fix to nvidia_supported script that parses
README.txt.
On the line with RTX A5000, there are 2 spaces after the PCI IDs.
Current nvidia_supported script assumes there are at least 3 spaces
before VDPAU features column, which is not the case in this line.
My proposal of
Change to In Progress for switching to HWE kernel
** Changed in: oem-priority
Status: Fix Committed => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1932555
Title:
[MIR]
** No longer affects: oem-priority
** Tags removed: oem-priority originate-from-1939083
** Tags removed: somerville
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1930903
Title:
Frequent kernel
Attach oem-somerville-bowen-meta_20.04~ubuntu1.debdiff by oem-scripts
1.7.
** Patch added: "oem-somerville-bowen-meta_20.04~ubuntu1.debdiff"
https://bugs.launchpad.net/bugs/1932555/+attachment/5517654/+files/oem-somerville-bowen-meta_20.04~ubuntu1.debdiff
** Tags removed: oem-scripts-0.98
**
** Summary changed:
- [DRAFT][MIR] oem-somerville-bowen-meta
+ [MIR] oem-somerville-bowen-meta
** Description changed:
- [DRAFT][Availability]
+ [Background]
+
+ Please see https://wiki.ubuntu.com/MIRTeam/Exceptions/OEM and
+ https://wiki.ubuntu.com/StableReleaseUpdates/OEMMeta for details.
+
** Tags added: oem-priority originate-from-1939083 somerville
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1930903
Title:
Frequent kernel oops related to nvidia / nv_drm_master_set
To manage
When will we upload the changes to -proposed?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1938259
Title:
Add ACCEL_LOCATION=base property for Dell clamshell models
To manage notifications about
> I pushed your commits to f/h/i, can you check to make sure they look
ok?
That focal change is okay after discussion with our PM.
Other than for h/i the changelog doesn't contain file path (I forgot
about it), everything else seems okay to me.
--
You received this bug notification because you
> For hirsute, what about existing users, should the patch retain the
old matches? Like this:
The old matches might match the same model name but with different form
factor, although we are already trying to avoid that confusion by
matching chassis type.
Also hirsute kernel is also going to
** Patch added: "debdiff for hirsute from 247.3-3ubuntu3.4"
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1938259/+attachment/5514282/+files/systemd_247.3-3ubuntu3.4-247.3-3ubuntu3.5.diff
** Tags added: oem-priority originate-from-1895110 somerville
** Description changed:
We are
** Description changed:
We are planning to do SRU to systemd in focal, to avoid unwanted screen
rotations on some Dell laptop models.
[Impact]
- * This fixes unwanted rotations on certain Dell clamshell laptop models
+ * This fixes unwanted rotations on certain Dell clamshell laptop
** Description changed:
We are planning to do SRU to systemd in focal, to avoid unwanted screen
rotations on some Dell laptop models.
[Impact]
- This fixes unwanted rotations on certain Dell clamshell laptop models
+ * This fixes unwanted rotations on certain Dell clamshell laptop
** Description changed:
We are planning to do SRU to systemd in focal, to avoid unwanted screen
rotations on some Dell laptop models.
+ [Impact]
+
+ This fixes unwanted rotations on certain Dell laptop models with
+ accelerometer in their clamshell models.
+
[Test Plan]
- * On Dell
** Tags added: block-proposed-focal
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1938259
Title:
Add ACCEL_LOCATION=base property for Dell clamshell models
To manage notifications about this bug
** Patch added: "systemd_245.4-4ubuntu3.11-245.4-4ubuntu3.12.diff"
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1938259/+attachment/5514270/+files/systemd_245.4-4ubuntu3.11-245.4-4ubuntu3.12.diff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
Public bug reported:
We are planning to do SRU to systemd in focal, to avoid unwanted screen
rotations on some Dell laptop models.
[Test Plan]
* On Dell laptops with model SKU 0A3E or 0E0E, install this package and kernel
5.13, or kernel with this patch backported:
Reported to upstream with stripped test case:
https://gitlab.gnome.org/GNOME/mutter/-/issues/1875
** Bug watch added: gitlab.gnome.org/GNOME/mutter/-/issues #1875
https://gitlab.gnome.org/GNOME/mutter/-/issues/1875
--
You received this bug notification because you are a member of Ubuntu
Public bug reported:
gnome-initial-setup detects size-changed event on GdkScreen, but when
screen scale is changed the resize event is not triggered, causing it
not reevaluating the small screen detection.
Replacing it with monitors-changed can resolve this issue.
** Affects:
** Summary changed:
- When changing screen scale in X11, gnome-initial-setup's window shadow should
not be glitched
+ When changing screen scale in GNOME Xorg, gnome-initial-setup's window shadow
should not be glitched
--
You received this bug notification because you are a member of Ubuntu
** Summary changed:
- Can see some garbage at the edge of the window after changing scale
+ When changing screen scale in X11, gnome-initial-setup's window shadow can be
glitched
** Summary changed:
- When changing screen scale in X11, gnome-initial-setup's window shadow can be
glitched
+
Tried modifying the source code of gnome-initial-setup, found that this
issue cannot be reproduced, if the titlebar of the window (gis-
assistant) is not set in the main (gis-driver) window.
I think this issue can be worked around in gis-assistant, but the root
cause might be either
*** This bug is a duplicate of bug 1071389 ***
https://bugs.launchpad.net/bugs/1071389
** This bug has been marked a duplicate of bug 1071389
nvidia-current conflicts with fglrx (both cards present)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
1 - 100 of 116 matches
Mail list logo
