noble debdiff
** Patch added: "bluez_5.72-0ubuntu5.3.debdiff"
https://bugs.launchpad.net/oem-priority/+bug/2092158/+attachment/5870675/+files/bluez_5.72-0ubuntu5.3.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bu
plucky debdiff
** Patch added: "bluez_5.79-2ubuntu1.1.debdiff"
https://bugs.launchpad.net/oem-priority/+bug/2092158/+attachment/5870677/+files/bluez_5.79-2ubuntu1.1.debdiff
** Changed in: bluez (Ubuntu Noble)
Assignee: (unassigned) => Yao Wei (medicalwei)
** Changed in:
oracular debdiff
** Patch added: "bluez_5.77-0ubuntu2.2.debdiff"
https://bugs.launchpad.net/oem-priority/+bug/2092158/+attachment/5870676/+files/bluez_5.77-0ubuntu2.2.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https:/
> Hm. But by my understanding of the input stack, *this* will result in
both Wayland and Xorg sessions seeing the extra key as F20, which is a
change of behaviour for Wayland sessions which would currently see
KEY_MICMUTE and which users could have configured bindings for?
That is the convention u
Setting this issue as Incomplete and waiting for upstream to review the
updated PR.
** Changed in: nvidia-settings (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bu
I've posted the alternative proposal on fixing the intended issue on Bug
2105957
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2103967
Title:
[SRU] Include a patch that forcibly maps mic mute key an
Yes, however Bug 2103967 is less likely to get a pass from SRU
maintainers, as the change is probably unsuitable for SRU, and this only
affects only one series of Dell systems.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bu
On noble with bluez 5.72.0-0ubuntu5 with a unit with NVIDIA GPU,
connected to Jabra Speak2 55 UC Bluetooth speaker, this issue is
reproducible. Updating to -proposed (5.72.0-ubuntu5.2), this issue is
still reproducible, considering it validation failed.
--
You received this bug notification becau
On oracular with bluez 5.77.0-ubuntu2 with a unit with NVIDIA GPU with
Jabra Speak2 55 UC, this issue is reproducible. Updating to -proposed
(5.77.0-ubuntu2.1), this issue is still reproducible, considering it
validation failed.
(p.s. this issue cannot be reproduced with AirPods Pro 2, probably t
It is not needed for plucky as we have tested that the changes in
xserver-xorg-input-libinput which is included in plucky fixed this
issue.
The main reason for mapping micmute key to f20 is thst Xorg does not
take key code > 255 (in wayland, usually it takes the key code as-is
from libinput) but m
ersion should display normally (1.29) in NVIDIA X Server
Settings.
[Actual Result]
NV-CONTROL version shows "Unknown" in NVIDIA X Server Settings.
Note that this issue does not apply to NVIDIA drivers for 560 and below.
** Changed in: nvidia-settings (Ubuntu)
Assig
debdiff for plucky
** Patch added: "nvidia-settings_510.47.03-0ubuntu4.25.04.1.debdiff"
https://bugs.launchpad.net/ubuntu/+source/nvidia-settings/+bug/2104094/+attachment/5868794/+files/nvidia-settings_510.47.03-0ubuntu4.25.04.1.debdiff
--
You received this bug notification because you are a
debdiff for noble
** Patch added: "nvidia-settings_510.47.03-0ubuntu4.24.04.1.debdiff"
https://bugs.launchpad.net/ubuntu/+source/nvidia-settings/+bug/2104094/+attachment/5868792/+files/nvidia-settings_510.47.03-0ubuntu4.24.04.1.debdiff
--
You received this bug notification because you are a
debdiff for oracular
** Patch added: "nvidia-settings_510.47.03-0ubuntu4.24.10.1.debdiff"
https://bugs.launchpad.net/ubuntu/+source/nvidia-settings/+bug/2104094/+attachment/5868793/+files/nvidia-settings_510.47.03-0ubuntu4.24.10.1.debdiff
--
You received this bug notification because you are
** Patch added: "oracular debdiff"
https://bugs.launchpad.net/ubuntu/+source/systemd-hwe/+bug/2105957/+attachment/5868787/+files/systemd-hwe_256.4.2.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net
** Tags added: jira-cpl-119 oem-priority
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2105957
Title:
[SRU] Add micmute key for Dell Pro Max series
To manage notifications about this bug go to:
htt
** Patch added: "noble debdiff"
https://bugs.launchpad.net/ubuntu/+source/systemd-hwe/+bug/2105957/+attachment/5868786/+files/systemd-hwe_255.1.5.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bu
Public bug reported:
[ Impact ]
* This patch adds hwdb entries to map mic mute keycode to F20, so that
the key is usable in Xorg.
[ Test Plan ]
* On targeted unit, under Xorg, test that mic mute does not work
* Update the package to -proposed and restart desktop, test the same
key, the mic
Filed another patch for upstream review: https://lore.kernel.org/linux-
bluetooth/20250401020221.119615-1-yao@canonical.com/T/#t
I've tested it against BlueZ 5.80
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launch
** Tags removed: verification-needed verification-needed-noble
verification-needed-oracular
** Tags added: verification-failed verification-failed-noble
verification-failed-oracular
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
htt
I believe this would not impact users with those keys working, and it
will enable the function of those keys if they did not function in Xorg.
The only problem I can currently think of is if the user has remapped
F20-F23 for other keys, those keys would not function according to their
labels.
The
Memo: might be a related issue:
https://gitlab.gnome.org/GNOME/mutter/-/issues/73
** Bug watch added: gitlab.gnome.org/GNOME/mutter/-/issues #73
https://gitlab.gnome.org/GNOME/mutter/-/issues/73
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
Public bug reported:
[Summary]
NV-CONTROL version shows "Unknown" in NVIDIA X Server Settings.
[Steps to reproduce]
Boot to OS.
Install 570-open NVIDIA driver.
Launch the NVIDIA X Server Settings in Show Apps.
[Expected result]
NV-CONTROL version should display normally (1.29) in NVIDIA X S
Issue and Pull Request filed upstream:
https://github.com/NVIDIA/nvidia-settings/issues/116
https://github.com/NVIDIA/nvidia-settings/pull/117
** Tags added: jira-cpl-152 oem-priority
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
h
** Changed in: oem-priority
Importance: Undecided => High
** Changed in: xserver-xorg-input-libinput (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 i
** Patch added: "xserver-xorg-input-libinput_1.4.0-1ubuntu24.10.1.debdiff"
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-libinput/+bug/2103967/+attachment/5866786/+files/xserver-xorg-input-libinput_1.4.0-1ubuntu24.10.1.debdiff
--
You received this bug notification because you a
** Patch added: "xserver-xorg-input-libinput_1.4.0-1ubuntu24.04.1.debdiff"
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-libinput/+bug/2103967/+attachment/5866785/+files/xserver-xorg-input-libinput_1.4.0-1ubuntu24.04.1.debdiff
** Description changed:
[ Impact ]
== Backgr
or other features, it may be
in conflict.
** Affects: oem-priority
Importance: Undecided
Status: New
** Affects: xserver-xorg-input-libinput (Ubuntu)
Importance: Undecided
Assignee: Yao Wei (medicalwei)
Status: New
** Tags: jira-cpl-119 oem-priority
** Ch
debdiff for oracular
** Patch added: "bluez_5.77-0ubuntu2.1.debdiff"
https://bugs.launchpad.net/ubuntu/+source/pipewire/+bug/2092158/+attachment/5865703/+files/bluez_5.77-0ubuntu2.1.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
debdiff for noble
** Patch added: "bluez_5.72-0ubuntu5.2.debdiff"
https://bugs.launchpad.net/ubuntu/+source/pipewire/+bug/2092158/+attachment/5865704/+files/bluez_5.72-0ubuntu5.2.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubu
debdiff for plucky
** Description changed:
+ [ Impact ]
+
+ * On system with NVIDIA proprietary driver and Bluetooth interface,
+ when connecting to a Bluetooth headset, after doing a round of
+ suspend/resume, A2DP interface would be reconnected, but not HSP/HFP.
+
+ * This fix is suggested
** Summary changed:
- With certain configs (such as with NVIDIA GPU driver), Bluetooth HSP/HFP
profile may be missing after suspend/resume
+ [SRU] With certain configs (such as with NVIDIA GPU driver), Bluetooth
HSP/HFP profile may be missing after suspend/resume
--
You received this bug notif
** Changed in: bluez (Ubuntu)
Assignee: (unassigned) => Yao Wei (medicalwei)
** Changed in: bluez (Ubuntu)
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/2
This is reproduced in the git HEAD version, I would like to point out it
is not the top left "Trash" icon missing, but the bottom right "Home"
icon.
** Attachment added: "lp2086840.mov"
https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-desktop-icons-ng/+bug/2086840/+attachment/58
Confirmed drag and drop outside window under Wayland session is working
in 47.0-1ubuntu4.3 in oracular, by dragging a selection outside nautilus
and drag it back, the selection won't be cancelled due to touch draging
outside window.
The test case described is also tested, as scrolling the list whi
** Bug watch added: gitlab.gnome.org/GNOME/gnome-control-center/-/issues #3375
https://gitlab.gnome.org/GNOME/gnome-control-center/-/issues/3375
** Changed in: gnome-control-center
Status: Fix Released => Unknown
** Changed in: gnome-control-center
Remote watch: gitlab.gnome.org/GNOME/
** Changed in: pipewire (Ubuntu)
Status: New => Invalid
** Also affects: bluez (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2092158
Title:
Continue at: https://gitlab.gnome.org/GNOME/gnome-control-
center/-/issues/3362, though I guess I should open another issue.
Maybe their method of getting the name of the renderer is not always
stable.
** Bug watch added: gitlab.gnome.org/GNOME/gnome-control-center/-/issues #3362
https://gitla
I can now reproduce the issue on a desktop:
ubuntu@localhost:~$ switcherooctl list
Device: 0
Name:NVIDIA Corporation AD106 [GeForce RTX 4060 Ti]
Default: yes
Environment: __GLX_VENDOR_LIBRARY_NAME=nvidia __NV_PRIME_RENDER_OFFLOAD=1
__VK_LAYER_NV_optimus=NVIDIA_only
Device: 1
What I discovered with the above fix, on the laptop, is that, when you
use
prime-select nvidia
this issue is reproducible, which can also indicate that, switcheroo cannot
actually switch which GPU to render.
The previous fix assumes the renderer can be switched by switcheroo normally.
However I
libfprint itself is LGPL-2.1 licensed, and fprintd is GPL-2, but is
communicating with libfprint using D-Bus, and the prebuilt binary
Broadcom provides dynamically links to libfprint. I don't sense there's
a GPL license violation by that. We could consult our legal team if
further clarification i
Remote doesn't tell wontfix or fixed
** Changed in: pipewire
Importance: Unknown => Undecided
** Changed in: pipewire
Status: Fix Released => New
** Changed in: pipewire
Remote watch: gitlab.freedesktop.org/pipewire/pipewire/-/issues #4461 => None
--
You received this bug notificati
Remote doesn't tell wontfix or fixed
** Changed in: pipewire
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2092158
Title:
With certain configs (such as with NVIDIA GPU
Updated package to 5.14.83-5.14.003.0-0ubuntu1~oem4
In postinst I added a error handling if connection dbus is not available
it will display a message and skip (as the message is in a chroot
environment). As well I added a message if there's no device available
for the firmware update.
Pednatic
On Jammy on an affected system, using pci.ids version 0.0~2022.01.22-1,
lspci shows "Wi-Fi 6 AX201 160MHz":
$ lspci -nnnvvv
00:14.3 Network controller [0280]: Intel Corporation Wi-Fi 6 AX201 160MHz
[8086:4df0] (rev 01)
Subsystem: Intel Corporation Wi-Fi 6 AX201 160MHz [8086:4030]
On Oracular on an affected system, using pci.ids version
0.0~2024.09.12-1, lspci shows "Wi-Fi 6 AX201 160MHz":
00:14.3 Network controller [0280]: Intel Corporation Wi-Fi 6 AX201 160MHz
[8086:4df0] (rev 01)
Subsystem: Intel Corporation Device [8086:4030]
Control: I/O- Mem+ BusMaste
On Noble on an affected system, using pci.ids version 0.0~2024.03.31-1,
lspci shows "Wi-Fi 6 AX201 160MHz":
00:14.3 Network controller [0280]: Intel Corporation Wi-Fi 6 AX201 160MHz
[8086:4df0] (rev 01)
Subsystem: Intel Corporation Wi-Fi 6 AX201 160MHz [8086:4030]
Control: I/O- Me
Confirmed opening a popup menu by long-touching in Nautilus under
Wayland session is working properly (does not disappear on release) in
47.0-1ubuntu4.3 in oracular.
** Tags removed: verification-needed verification-needed-oracular
** Tags added: verification-done verification-done-oracular
--
Y
Confirmed nautilus icon drag and drop under Wayland session is working
in 47.0-1ubuntu4.3 in oracular.
** Tags removed: verification-needed verification-needed-oracular
** Tags added: verification-done verification-done-oracular
--
You received this bug notification because you are a member of
On Oracular, mutter 47.0-1ubuntu4.1, under Xorg, this issue is
reproducible as the touchscreen is not responsive after suspend/resume.
Updating to -proposed version mutter 47.0-1ubuntu4.3, this issue is no
longer reproducible.
** Tags removed: verification-needed verification-needed-oracular
** Ta
My testing was on a vanilla Ubuntu installation, and by default it has a
Home link placed on the bottom-right of the display, which gets hidden
when the window size changed not to reveal the icon. If you need a demo
video I can try to make one.
--
You received this bug notification because you a
Uploaded 6.1.155-6.1.028.0+1-0ubuntu1~oem1 for the issues found in Bug
#2099655, as for the upstream version change, I found I was uploading a
repacked package instead of the original, and I was trying to correct it
back.
--
You received this bug notification because you are a member of Ubuntu
Bu
** Changed in: oem-priority
Assignee: (unassigned) => Yao Wei (medicalwei)
** Changed in: oem-priority
Importance: Undecided => Medium
** Changed in: oem-priority
Status: New => In Progress
** Changed in: pci.ids (Ubuntu)
Assignee: (unassigned) => Yao Wei
debdiff for jammy
** Patch added: "pci.ids_0.0~2022.01.22-1ubuntu0.1.debdiff"
https://bugs.launchpad.net/ubuntu/+source/pci.ids/+bug/2100918/+attachment/5862435/+files/pci.ids_0.0~2022.01.22-1ubuntu0.1.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, whi
debdiff for noble
** Patch added: "pci.ids_0.0~2024.03.31-1ubuntu0.1.debdiff"
https://bugs.launchpad.net/ubuntu/+source/pci.ids/+bug/2100918/+attachment/5862436/+files/pci.ids_0.0~2024.03.31-1ubuntu0.1.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, whi
debdiff for oracular
** Patch added: "pci.ids_0.0~2024.09.12-1ubuntu0.1.debdiff"
https://bugs.launchpad.net/ubuntu/+source/pci.ids/+bug/2100918/+attachment/5862437/+files/pci.ids_0.0~2024.09.12-1ubuntu0.1.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs,
** Description changed:
[ Impact ]
- * Intel AC9560 on Jasper Lake by CNVi is mislabeled as AX201
+ * Jammy and Noble: Intel AC9560 on Jasper Lake by CNVi is mislabeled as
+ AX201
+
+ * Oracular: Intel AX201 on the same platform is mislabeled as AC9560
* This would cause problems on
** Description changed:
[ Impact ]
- * Intel AC9560 on Jasper Lake by CNVi is mislabeled as AX201
+ * Intel AC9560 on Jasper Lake by CNVi is mislabeled as AX201
- * This would cause problems on users looking into the hardware
+ * This would cause problems on users looking into the hard
Public bug reported:
[ Impact ]
* Intel AC9560 on Jasper Lake by CNVi is mislabeled as AX201
* This would cause problems on users looking into the hardware
configurations
[ Test Plan ]
* On the platforms where the issue happens, run lspci and ensure the
Wi-Fi interface name is "Wi-Fi 6 AX20
In that branch the start position of the grid is fixed, but the size is
still incorrect (it is still at the size of 200%), which causes the Home
icon at the bottom right does not appear.
Until the focus is on the hidden window, the window is still at the old
size.
** Attachment added: "Screenshot
I can verify in mutter 46.2-1ubuntu0.24.04.6, that when dragging a
window the damage is constrained to the window itself plus the shadow
around the window.
** Tags removed: verification-needed verification-needed-noble
** Tags added: verification-done verification-done-noble
--
You received this
In noble I am able to verify with mutter 46.2-1ubuntu0.24.04.6 the crash
does not happen using the webpage supplied in the attachment, which does
requestPointerLock() call to lock the pointer.
I would like to confirm the expected behavior is that when the screen is
touched, the pointer lock is lif
After updating to 46.2-1ubuntu0.24.04.6 this bug still exists, as the
dragged icon is sticked to the pointer but cannot be moved and released
properly.
Attaching video for reference
** Attachment added: "IMG_5243.MOV"
https://bugs.launchpad.net/oem-priority/+bug/1966635/+attachment/5861993/+f
Confirmed nautilus icon drag and drop under Wayland session is working
in 46.2-1ubuntu0.24.04.6 in noble.
** Tags removed: verification-needed-noble
** Tags added: verification-done-noble
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu
Sorry I am going to redo this under Wayland session, I was doing
verification under Xorg
** Tags removed: verification-failed verification-failed-noble
** Tags added: verification-needed verification-needed-noble
--
You received this bug notification because you are a member of Ubuntu
Bugs, whic
On Noble, this issue (touchscreen not responsive under Xorg session) is
reproducible in version 46.2-1ubuntu0.24.04.5, upgrading to
46.2-1ubuntu0.24.04.5, the issue is no longer reproducible.
We are waiting for packages in oracular in order to finish SRU.
** Changed in: oem-priority
Status
@jackyclee: yes you should be able to validate the issue by enabling
noble-proposed, then
sudo apt install -t noble-proposed gir1.2-mutter-15 libmutter-15-0
mutter-common mutter-common-bin
I am now validating this issue
--
You received this bug notification because you are a member of Ubuntu
Bu
** Tags removed: verification-done verification-done-oracular
** Tags added: verification-failed verification-failed-oracular
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2069564
Title:
[SRU] gnome
@nteodosio: who owns /tmp/.X11-unix after you login? in the case I can
reproduce it is owned by gdm, and I can confirm it is a regression
compared to *u4.1 as it does not happen if /tmp/.X11-unix is owned by
gdm, and if it is not owned by gdm nor root nor user, I am able to login
into the desktop b
@nteodosio regarding to issue from Gre0, I found it reproducible if
/tmp/.X11-unix is removed before starting GDM, as the ownership of that
directory became "gdm" (user 120), however after reboot the issue is
gone. I am wondering this is related to how that directory is created.
--
You received
Hi, just by judging from the SRU test case above, I can test that the
issue is present on 47.0-1ubuntu4.1 but not on 47.0-1ubuntu4.2. Logs
from both versions are attached.
However, I have no idea for the root cause of the permission change of
/tmp/.X11-unix directory. I am only here to unblock th
They support different hardware, and I'm not sure whether using version
number as suffix is required in this context as that is not the
difference of library ABI version.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.lau
** Changed in: oem-priority
Status: New => In Progress
** Changed in: ubuntu
Status: New => In Progress
** Changed in: oem-priority
Assignee: (unassigned) => Yao Wei (medicalwei)
** Changed in: oem-priority
Importance: Undecided => High
** Changed in: ubuntu
Public bug reported:
Firmwares and shared libraries for fingerprint support on Dell
ControlVault3
URL: https://packages.broadcom.com/artifactory/dell-controlvault-drivers/
License: Proprietary
Note: We will also need this to be backported to noble for OEM support. The
upstream release versioning
This package currently resides in:
https://launchpad.net/~medicalwei/+archive/ubuntu/dell-cv3-cv3plus
Packaging source:
https://git.launchpad.net/libfprint-2-tod1-broadcom
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.l
** Tags added: needs-packaging
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2099289
Title:
[needs-packaging] libfprint-2-tod1-broadcom-cv3plus
To manage notifications about this bug go to:
https:/
This package currently resides in:
https://launchpad.net/~medicalwei/+archive/ubuntu/dell-cv3-cv3plus
Packaging source:
https://git.launchpad.net/~oem-solutions-engineers/pc-enablement/+git/libfprint-2-tod1-broadcom-cv3plus
** Changed in: ubuntu
Assignee: (unassigned) => Yao Wei (medical
** Description changed:
Firmwares and shared libraries for fingerprint support on Dell
- ControlVault3 Plus
+ ControlVault3 Plus, note that the package should be versioned in 6.x.x
URL: https://packages.broadcom.com/artifactory/dell-controlvault-drivers/
License: Proprietary
Note: We wi
** Description changed:
Firmwares and shared libraries for fingerprint support on Dell
ControlVault3 Plus
URL: https://packages.broadcom.com/artifactory/dell-controlvault-drivers/
License: Proprietary
+ Note: We will also need this to be backported to noble for OEM support.
** Tags add
Public bug reported:
Firmwares and shared libraries for fingerprint support on Dell
ControlVault3 Plus
URL: https://packages.broadcom.com/artifactory/dell-controlvault-drivers/
License: Proprietary
** Affects: ubuntu
Importance: Undecided
Status: New
--
You received this bug noti
Confirmed gnome-snapshot USB webcam issue is fixed on noble:
Issue is reproducible with pipewire 1.0.5-1ubuntu2
Issue is not reproducible with pipewire 1.0.5-1ubuntu3
** Tags removed: verification-needed verification-needed-noble
** Tags added: verification-done verification-done-noble
--
You r
=== Feature test ===
On a unit with Lunar Lake CPU (202412-36119) where "Unsupported
condition 59 (UNKNOWN)" and "Unsupported condition 60 (UNKNOWN)" appears
in thermald 2.5.6-2ubuntu0.24.04.1, the message does not appear in
2.5.6-2ubuntu0.24.04.2
On a unit with Meteor Lake CPU (202404-33961), th
I dput an updated upstream version (1.0.8) with binary and changelog
changes, and also changed debian/* copyright to GPL-3 per Copyright
Policy in Canonical. Also I included the changes @waveform has made.
I would like to request another review.
--
You received this bug notification because you
Thanks, I am asking our customer for validating this issue with your
PPA.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2087858
Title:
Snapshot doesn't work on Ubuntu 24.04
To manage notifications
Continuing from LP: #2061687
(@nteodosio considered backporting !2145 but that does not work for him,
but it works in my case)
Here I found the following for 1.0.5-1ubuntu2 after enabling wireplumber
debug log:
Jan 21 13:23:02 ubuntu wireplumber[2249]: /dev/video0 accessible:0
Jan 21 13:23:02 ub
@nteodosio, I can confirm that backporting
https://gitlab.freedesktop.org/pipewire/pipewire/-/merge_requests/2145
instead of just
https://gitlab.freedesktop.org/pipewire/pipewire/-/merge_requests/2118
can fix the issue for noble.
The one that's currently uploaded in -updates contains only the
** Changed in: oem-priority
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2087831
Title:
[SRU] On a laptop with NVIDIA graphics and touchscreen, touchscreen
gets d
I filed a Salsa MR for noble (as mutter in noble does not have SRU
exception), and we should be waiting for next point release of GNOME 47
for fixing the issue in plucky:
https://salsa.debian.org/gnome-team/mutter/-/merge_requests/138
** Description changed:
+ [ Impact ]
+
+ * When user using
** Summary changed:
- On a laptop with NVIDIA graphics and touchscreen, touchscreen gets disabled
after resume from suspend in Xorg session
+ [SRU] On a laptop with NVIDIA graphics and touchscreen, touchscreen gets
disabled after resume from suspend in Xorg session
--
You received this bug not
Changes regarding moving away from /opt is much more difficult to handle, as
1. we need to test whether the package can work with the path change.
2. vendors do prefer putting packages they release into /opt instead of FHS
standard paths.
I'll check with vendor and our team how we should handle t
Files in pwl-unlock/* are distributed without source code, or preferred
format for making modifications.
If this requires clarification in d/copyright I can add it.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpa
** Bug watch added: github.com/bluez/bluez/issues #1069
https://github.com/bluez/bluez/issues/1069
** Also affects: bluez via
https://github.com/bluez/bluez/issues/1069
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member of Ubuntu
Bu
I've tested ubuntu-desktop-provision by refreshing it in the live
environment using the following command:
# sudo snap refresh --channel=24.04/edge ubuntu-desktop-bootstrap
ubuntu-desktop-bootstrap (24.04/edge) 0+git.61036cc38 from Canonical✓ refreshed
This includes subiquity from current ubuntu/
** Description changed:
+ [ Impact ]
+
+ * In gnome-control-center (Settings), when user has multiple GPUs and
+ the main display is on a discrete GPU (for example, PC with Intel and
+ NVIDIA GPUs, and display is on the NVIDIA GPU), in System -> About ->
+ System Details page, it will show multi
** Description changed:
[ Impact ]
* when using Subiquity's autoinstall feature, once can use "match"
directives at the storage->layout level to find the right drive.
However, the match directives where silently ignored when using mode:
use_gap.
* This makes it difficult for the
** Bug watch added: gitlab.gnome.org/GNOME/xdg-desktop-portal-gnome/-/issues
#154
https://gitlab.gnome.org/GNOME/xdg-desktop-portal-gnome/-/issues/154
** Also affects: xdg-desktop-portal via
https://gitlab.gnome.org/GNOME/xdg-desktop-portal-gnome/-/issues/154
Importance: Unknown
S
** No longer affects: gnome-shell
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2077451
Title:
GNOME 47: GNOME apps don't launch for around the first 20 seconds
after login
To manage notification
** Bug watch added: gitlab.gnome.org/GNOME/xdg-desktop-portal-gnome/-/issues
#154
https://gitlab.gnome.org/GNOME/xdg-desktop-portal-gnome/-/issues/154
** Also affects: gnome-shell via
https://gitlab.gnome.org/GNOME/xdg-desktop-portal-gnome/-/issues/154
Importance: Unknown
Status:
I'd like to confirm a workaround/fix (idk, just judging from the
symptom), I tried removing:
Requisite=graphical-session.target
from /usr/lib/systemd/user/xdg-desktop-portal-gnome.service, and the
x-d-p-gnome service can be started normally so the launch timeout is
gone.
Otherwise x-d-p-gnome di
*** This bug is a duplicate of bug 2042301 ***
https://bugs.launchpad.net/bugs/2042301
** This bug has been marked a duplicate of bug 2042301
Windows are slow to open shortly after login under X11 session
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
1 - 100 of 320 matches
Mail list logo
