** 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 Desktop
P
** 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
** 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 Desktop
Packages, which is subscribed to gnome-session in Ubuntu.
https://bugs.launchpad.net/bugs/2077451
Title:
GNOME 47: GNOME apps don't launch for around the first 20 seconds
after login
** 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
** Tags added: jira-somerville-1469 oem-priority
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/1853094
Title:
[modeset] Screen tearing when using multiple monitors
Status in OEM
MR proposed: https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/4188
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/2087831
Title:
On a laptop with NVIDIA graphics and touchscreen,
** Bug watch added: gitlab.freedesktop.org/pipewire/pipewire/-/issues #4461
https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/4461
** Also affects: pipewire via
https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/4461
Importance: Unknown
Status: Unknown
--
You recei
Public bug reported:
We found that with certain hardware configs, such as whether NVIDIA GPU
is/is not available (but not always), can affect HSP/HFP profile after
suspend/resume. We will post debug information later on affected
configs.
[Reproducible Steps]
1. Connect Bluetooth headphones
2. Ch
For OEM we are targeting the fix on 24.04, mainly on a PC config with
Intel + NVIDIA GPUs where display is on NVIDIA only
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-control-center in Ubuntu.
https://bugs.launchpad.net/bugs/2037
** Changed in: mutter (Ubuntu)
Status: New => In Progress
** Changed in: oem-priority
Status: New => In Progress
** Changed in: oem-priority
Assignee: (unassigned) => Yao Wei (medicalwei)
** Changed in: mutter (Ubuntu)
Assignee: (unassigned) => Yao Wei
** No longer affects: nvidia-graphics-drivers-550 (Ubuntu)
** No longer affects: gnome-shell (Ubuntu)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/2087831
Title:
On a laptop wi
** Changed in: xserver-xorg-input-libinput (Ubuntu)
Status: New => Invalid
** Changed in: nvidia-graphics-drivers-550 (Ubuntu)
Status: New => Invalid
** Changed in: gnome-shell (Ubuntu)
Status: New => Invalid
** Bug watch added: gitlab.gnome.org/GNOME/mutter/-/issues #3834
** Changed in: oem-priority
Status: New => In Progress
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-control-center in Ubuntu.
https://bugs.launchpad.net/bugs/2037076
Title:
System Details incorrectly shows multiple GPUs
Note about enabling/disabling input on Mutter side, it is under
`mutter/src/backends/meta-input-
mapper.c:input_mapper_power_save_mode_changed_cb`
I will start tracing from there and see whether there's changes between
GNOME versions.
--
You received this bug notification because you are a membe
On Ubuntu 23.10 VNP, could you confirm that NVIDIA driver is installed in the
system?
They might be running on Nouveau especially the apt repository for 23.10 is now
unavailable.
I can reproduce the issue on 23.10 after changing sources to old-
releases.ubuntu.com, then install NVIDIA driver usi
** Also affects: nvidia-graphics-drivers-550 (Ubuntu)
Importance: Undecided
Status: New
** Summary changed:
- touchscreen has no response after resume from suspend in Xorg session
+ On a laptop with NVIDIA graphics and touchscreen, touchscreen gets disabled
after resume from suspend in
This issue can be linked to Bug #1952823 for NVIDIA driver, except the
different version.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/2087831
Title:
touchscreen has no response afte
Furtuer investigation turned out that there's something to do with
NVIDIA driver, that when starting suspend, the display would wake for a
moment before really entering suspend.
When display is turned on or turned off, gnome-shell files an event to
enable/disable touchscreen, so that the touchscre
We found out that the touchscreen is disabled by libinput after suspend/resume:
Check the following properties (the touchscreen is id=10 for our DUT, see
`xinput list`)
before suspend:
$ xinput list-props 10
Device 'CUST:00 0EEF:C003':
[...snip...]
libinput Send Events Mode En
** Changed in: oem-priority
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/1990456
Title:
xorg reports bogus 1600x1024 resolution
Sta
This issue should be already closed by gnome-initial-setup
46.2-1ubuntu0.24.04.1, the changelog mentioned LP: #2071449 and did not
refer to this issue.
** Changed in: oem-priority
Status: New => Fix Released
** Changed in: gnome-initial-setup (Ubuntu)
Status: In Progress => Fix Rele
.
Note that, this SRU will be sent as a Merge Request on Debian Salsa:
https://salsa.debian.org/ubuntu-dev-team/libfprint
** Affects: libfprint (Ubuntu)
Importance: Undecided
Assignee: Yao Wei (medicalwei)
Status: New
** Changed in: libfprint (Ubuntu)
Assignee: (unassigned
** Changed in: oem-priority
Importance: Undecided => Low
** Changed in: oem-priority
Assignee: (unassigned) => Yao Wei (medicalwei)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-control-center in Ubuntu.
** Tags added: jira-fxn-16 oem-priority
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-control-center in Ubuntu.
https://bugs.launchpad.net/bugs/2037076
Title:
System Details incorrectly shows multiple GPUs
Status in gnome-cont
Trying to test with vanilla Xorg by stopping gdm3 and using Xorg by
itself:
0. Install xterm since we are going to use it later.
1. Switch to tty3 by using Ctrl-Alt-F3
sudo systemctl stop gdm3
sudo Xorg &
DISPLAY=:0 xterm
2. Switch to blank Xorg session using Ctrl-Alt-F1, then in xterm run xev
Public bug reported:
This issue happens in ubuntu 24.04.1, gnome-shell-extension-desktop-
icons-ng 46+really47.0.9-1
The icon grid is off when scaling from 2x to 1x in wayland GNOME
desktop, attaching video recording
** Affects: gnome-shell-extension-desktop-icons-ng (Ubuntu)
Importance: Un
** Bug watch added: gitlab.gnome.org/GNOME/gnome-initial-setup/-/issues #222
https://gitlab.gnome.org/GNOME/gnome-initial-setup/-/issues/222
** Also affects: gnome-initial-setup via
https://gitlab.gnome.org/GNOME/gnome-initial-setup/-/issues/222
Importance: Unknown
Status: Unknown
** Tags added: jira-somerville-1221
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to ubuntu-settings in Ubuntu.
https://bugs.launchpad.net/bugs/2078759
Title:
Ability to use comments in YAML generated by Netplan
Status in OEM Priority
We intended to do SRU for libmbim to noble for pwl-pc-services package
to enter multiverse, as it requires functions that came from libmbim
1.31.4:
https://bugs.launchpad.net/ubuntu/+bug/2084776
That pwl-pc-services is the packaging name for the
https://github.com/palcomwireless/linux_pkgs
--
Y
** Tags added: jira-somerville-1014
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to ubuntu-settings in Ubuntu.
https://bugs.launchpad.net/bugs/2078759
Title:
Ability to use comments in YAML generated by Netplan
Status in OEM Priority
Public bug reported:
When there is one letter in the time zone search input, the suggestion
popup would wobble.
Video and sosreport will be attached after this report.
** Affects: oem-priority
Importance: Undecided
Status: New
** Affects: gnome-initial-setup (Ubuntu)
Importan
Something I've discovered so far:
If the monitor is scaled up it has a chance that the active region and
the background drawing region is unchanged, causing glitches like broken
shadow, as well as unclickable UI elements outside the original box.
This might have something to do with detecting cha
*** This bug is a duplicate of bug 1924689 ***
https://bugs.launchpad.net/bugs/1924689
** Summary changed:
- In Xorg, when changing display scale, window shadow may have artifacts
+ In Xorg, when changing display scale, window shadows have artifacts
** Description changed:
Under Xorg (Tes
Public bug reported:
Under Xorg (Tested NVIDIA GPU and Intel Graphics) Changing display scale
in gnome-control-center causes artifacts on the shadow.
[Steps to reproduce]
1. Enter GNOME Desktop in Xorg mode
2. Open Settings and another window
3. Change scale from from 1x to 2x and 2x back to 1x
** Attachment added: "lp2084229-artifacts-change-scale.mov"
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2084229/+attachment/5826984/+files/lp2084229-artifacts-change-scale.mov
** Tags added: jira-somerville-1137 oem-priority
--
You received this bug notification because you are a m
** Package changed: pipewire (Ubuntu) => wireplumber (Ubuntu)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to wireplumber in Ubuntu.
https://bugs.launchpad.net/bugs/2083798
Title:
bluetooth headsets do not switch to handsfree profile a
Public bug reported:
Problem:
When using Bluetooth headset, the audio profile won't switch to Handsfree when
an application is using the microphone. e.g. "arecord", or Firefox with
conference call services.
Note that, manually switching the profile to Handsfree does make the
recording work, the
Tested on a unit that with gnome-control-center 1:46.0.1-1ubuntu7, the
issue is reproducible.
After updating the package to 1:46.4-0ubuntu0.24.04.1, this issue is no
longer reproducible. Tested by enrolling all fingers and the enrolled
fingers do not display in the "Scan new fingerprint" list.
*
Should we fix this issue by bumping minor version, or adding a patch to
this package?
I see 46.3 is in Noble at the moment.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-control-center in Ubuntu.
https://bugs.launchpad.net/bugs/2
** Description changed:
[ Impact ]
* This issue causes other random fingers not able to enroll for
authentication, once one or more fingers are enrolled.
- * This issue is going to be fixed by SRUing minor updates of gnome-
+ * This issue is going to be fixed by SRUing minor updates
ingerprint" are incorrect when one or more finger is
enrolled
** Changed in: oem-priority
Importance: Undecided => Medium
** Changed in: oem-priority
Assignee: (unassigned) => Yao Wei (medicalwei)
** Summary changed:
- List of "Scan new fingerprint" are incorrect when one or
from Bug #2076142:
A known commit exists to fix this issue:
https://gitlab.gnome.org/GNOME/gnome-control-
center/-/commit/3b7ea05d43c0dce4201279d5945488795b66bce7
** Also affects: oem-priority
Importance: Undecided
Status: New
** Tags added: oem-priority
** Changed in: oem-priority
*** This bug is a duplicate of bug 2076164 ***
https://bugs.launchpad.net/bugs/2076164
** This bug has been marked a duplicate of bug 2076164
fingerprint mismatch and disconnect with name
--
You received this bug notification because you are a member of Desktop
Packages, which is subscrib
Public bug reported:
On gnome-control-center 1:46.0.1-1ubuntu7 in Ubuntu 24.04, the list of
unenrolled fingers are wrong due to a filtering bug
Reproducible steps:
Enroll "Left ring finger" in a fingerprint-enabled system.
Expected:
The list in "Scan new fingerprint" hides "Left ring finger".
A
Public bug reported:
If gnome-shell is launched directly instead of launched through gnome-
session, the process spawning `ibus-daemon` might cause deadlock and
unable to start the graphics.
Since `ibusManager.js` checks whether service
`org.freedesktop.IBus.session.GNOME.service` exists. In our
This issue is also verified on 2:21.1.4-2ubuntu1.6 on kinetic
** Tags removed: verification-needed-kinetic
** Tags added: verification-done-kinetic
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg-server in Ubuntu.
https://bugs.launc
This issue is verified on 2:21.1.3-2ubuntu2.8 on jammy, that switching
from text terminal to X session the keyboard LED status would recover.
** Tags removed: verification-needed-jammy
** Tags added: verification-done-jammy
--
You received this bug notification because you are a member of Deskto
** Description changed:
[ Impact ]
* This change will force update keyboard LED status after calling
EnableDevice, in order to resolve LED status not syncing after switching
VT to a X session.
* This also fixes the issue with NVIDIA driver and Xorg, that after
resuming from sus
** Changed in: xorg-server (Ubuntu)
Assignee: (unassigned) => Yao Wei (medicalwei)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/1993621
Title:
Force update keyboard L
** Patch added: "xorg-server_21.1.4-2ubuntu1.6.debdiff"
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1993621/+attachment/5648816/+files/xorg-server_21.1.4-2ubuntu1.6.debdiff
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed t
** Patch added: "xorg-server_21.1.3-2ubuntu2.8.debdiff"
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1993621/+attachment/5648799/+files/xorg-server_21.1.3-2ubuntu2.8.debdiff
** Patch removed: "xorg-server_21.1.3-2ubuntu2.8.debdiff"
https://bugs.launchpad.net/ubuntu/+source/xo
Attached is the debdiff for the following Merge Request merged upstream:
https://gitlab.freedesktop.org/xorg/xserver/-/merge_requests/1070
Please review
** Description changed:
+ [ Impact ]
+
+ * This change will force update keyboard LED status after calling
+ EnableDevice, in order to resolv
** Summary changed:
- Switching virtual terminals [Ctrl-Alt-F1 - F7] to a X session turns off
keyboard LEDs
+ Force update keyboard LEDs after calling EnableDevice to fix its state after
VT switching
--
You received this bug notification because you are a member of Desktop
Packages, which is s
Related MP for this issue, however the MP does not fix the issue, and we
are proposing a similar patch:
https://gitlab.freedesktop.org/xorg/xserver/-/merge_requests/764
** Bug watch added: gitlab.freedesktop.org/xorg/xserver/-/issues #1234
https://gitlab.freedesktop.org/xorg/xserver/-/issues/12
** Tags added: originate-from-1996036
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1966635
Title:
can't move file/directory by drag and drop by using touch monitor
Status in Mutter:
** Tags added: originate-from-1997210
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1966635
Title:
can't move file/directory by drag and drop by using touch monitor
Status in Mutter:
Verified that this issue is fixed in gnome-shell 42.5-0ubuntu1
Thanks!
** Tags removed: verification-needed verification-needed-jammy
** Tags added: verification-done verification-done-jammy
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed
Public bug reported:
Switching virtual terminals [Ctrl-Alt-F1 - F7] to a X session turns off
keyboard LEDs.
This issue is reproducible on 2:21.1.3-2ubuntu2.1 (on 22.04)
To reproduce:
1. Log on a X session desktop (GNOME Xorg for example)
2. Turn on NumLock
3. Use Ctrl-Alt-F3 to switch to a text
** Changed in: gnome-shell (Ubuntu Jammy)
Status: In Progress => Confirmed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1984147
Title:
Monitor switcher popup (Super-P) is
*** This bug is a duplicate of bug 1988301 ***
https://bugs.launchpad.net/bugs/1988301
** This bug has been marked a duplicate of bug 1988301
Does not implement data-ciphers, only cipher which OpenVPN 2.5+ ignores,
hence can fail to connect
--
You received this bug notification because y
The fix is committed in 2022-10-04:
https://gitlab.gnome.org/GNOME/NetworkManager-
openvpn/-/commit/020ab0c4b872fa5415ed1a5e682acb3343c7b9f3
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager-openvpn in Ubuntu.
https://bugs.l
Before installing xorg-server 2:21.1.3-2ubuntu2.2, xrandr gives
1600x1024 resolution which was not able to use on the test unit.
After upgrading to xorg-server 2:21.1.3-2ubuntu2.2 from jammy-proposed,
that resolution is removed from xrandr.
ubuntu@ubuntu:~$ DISPLAY=:0 xrandr
Screen 0: minimum 320
** Description changed:
xorg reports 1600x1024 bogus resolution
[ Impact ]
- * User of NVIDIA GPU is able to switch to 1600x1024 resolution but
+ * User of NVIDIA GPU is able to switch to 1600x1024 resolution but
cannot display anything under the resolution
[ Test Plan ]
- 1.
Public bug reported:
xorg reports 1600x1024 bogus resolution
[ Impact ]
* User of NVIDIA GPU is able to switch to 1600x1024 resolution but
cannot display anything under the resolution
[ Test Plan ]
1. Find a test unit with NVIDIA GPU, or anything but using Xorg mode to enter
desktop
2. Type
This is the debdiff for gnome-shell 42.4-0ubuntu0.22.04.1 from jammy.
We would like this to be included in -proposed before next weekend
(2022-09-23), so I am doing SRU in spite of Salsa merge request.
** Description changed:
- Monitor switcher popup (Super-P) is not displayed on desktop with jo
Jammy)
Assignee: (unassigned) => Yao Wei (medicalwei)
** Changed in: oem-priority
Assignee: (unassigned) => Yao Wei (medicalwei)
** Changed in: oem-priority
Status: New => In Progress
** Patch removed: "lp1984147.patch"
https://bugs.launchpad.net/ubuntu/+source
The above MR is accepted upstream.
** Patch added: "lp1984147.patch"
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1984147/+attachment/5612602/+files/lp1984147.patch
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-
Note that https://gitlab.gnome.org/GNOME/gnome-
shell/-/merge_requests/2056 is doing the opposite of the feature
request.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1983717
Titl
MR on upstream: https://gitlab.gnome.org/GNOME/gnome-
shell/-/merge_requests/2451
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1984147
Title:
Monitor switcher popup (Super-P) is
** Changed in: gnome-shell (Ubuntu)
Assignee: (unassigned) => Yao Wei (medicalwei)
** Changed in: gnome-shell (Ubuntu)
Status: New => In Progress
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
** Tags added: oem-priority originate-from-1981417 somerville
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1984147
Title:
Monitor switcher popup (Super-P) is not displayed on de
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1984147/+attachment/5607596/+files/ProcEnviron.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpa
apport information
** Attachment added: "ShellJournal.txt"
https://bugs.launchpad.net/bugs/1984147/+attachment/5607597/+files/ShellJournal.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launch
apport information
** Attachment added: "monitors.xml.txt"
https://bugs.launchpad.net/bugs/1984147/+attachment/5607598/+files/monitors.xml.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launch
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1984147/+attachment/5607595/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https:/
apport information
** Attachment added: "GsettingsChanges.txt"
https://bugs.launchpad.net/bugs/1984147/+attachment/5607594/+files/GsettingsChanges.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bug
apport information
** Attachment added: "Dependencies.txt"
https://bugs.launchpad.net/bugs/1984147/+attachment/5607593/+files/Dependencies.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launch
Public bug reported:
Monitor switcher popup (Super-P) is not displayed on desktop with joined
display on GNOME 3 in Wayland mode
[Reproduce Steps]
1. Use a desktop PC and start GNOME 3 in Wayland mode (therefore using NVIDIA
GPU does not trigger the bug)
2. Connect the PC with 2 monitors
3. Use
** Description changed:
[Summary]
Firefox on Ubuntu 20.04 (99.0build2-0ubuntu0.20.04.2) window could be
glitched with laptops with Intel + NVIDIA GPU, and prime-select set to intel.
Either setting gfx.x11-egl-force-disabled to true in about:config, or
setting prime-select to on-demand
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1977790/+attachment/5595167/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to firefox in Ubuntu.
https://bug
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1977790/+attachment/5595161/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to firefox in Ubuntu.
https://bugs.launchpad.
apport information
** Attachment added: "IpAddr.txt"
https://bugs.launchpad.net/bugs/1977790/+attachment/5595163/+files/IpAddr.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to firefox in Ubuntu.
https://bugs.launchpad.net/bugs/1977
apport information
** Attachment added: "PciNetwork.txt"
https://bugs.launchpad.net/bugs/1977790/+attachment/5595166/+files/PciNetwork.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to firefox in Ubuntu.
https://bugs.launchpad.net/
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1977790/+attachment/5595165/+files/Lspci.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to firefox in Ubuntu.
https://bugs.launchpad.net/bugs/197779
apport information
** Attachment added: "Dependencies.txt"
https://bugs.launchpad.net/bugs/1977790/+attachment/5595162/+files/Dependencies.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to firefox in Ubuntu.
https://bugs.launchpad.
apport information
** Tags added: apport-collected focal
** Description changed:
[Summary]
Firefox on Ubuntu 20.04 (99.0build2-0ubuntu0.20.04.2) window could be
glitched with laptops with Intel + NVIDIA GPU, and prime-select set to intel.
Either setting gfx.x11-egl-force-disabled to tr
Public bug reported:
[Summary]
Firefox on Ubuntu 20.04 (99.0build2-0ubuntu0.20.04.2) window could be glitched
with laptops with Intel + NVIDIA GPU, and prime-select set to intel.
Either setting gfx.x11-egl-force-disabled to true in about:config, or
setting prime-select to on-demand or nvidia, ma
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 this
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 Desktop
Packages, which is subscribed to ibus in Ubuntu.
https://bugs.launchpad.net/bugs/1966356
Title:
ibus i
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to iio-sensor-proxy in Ubuntu.
https://bugs.launchpad.net/bugs/1963628
Title:
Force IIO_SENSOR_PROXY_TYPE to iio-buffer-als for some Dell models
Status in OEM Priority Project:
New
Status
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"
https://bugs.launchpad.net/ubuntu/+source/iio-sensor-prox
> 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 Desktop
Packages, which is subscribed t
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
-
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 stable
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 ar
** Tags added: originate-from-1933628
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1951667
Title:
[SRU] pulseaudio: restore hdmi audio be active output after resume
Status in HW
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 Desktop
Pack
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: gnome-initial-setup
1 - 100 of 105 matches
Mail list logo
