Status: New
** Affects: libfprint (Ubuntu)
Importance: Undecided
Assignee: Yao Wei (medicalwei)
Status: New
** Tags: oem-priority originate-from-2025413 somerville
** Changed in: libfprint (Ubuntu)
Assignee: (unassigned) => Yao Wei (medicalwei)
** Tags added:
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
*** 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 Ubuntu
Desktop Bugs, which is subsc
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
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
** 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
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
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 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
-
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
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
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 gnome-initial-
** 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
+ When
** 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
De
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
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
Deskt
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
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 Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
https://bugs.lau
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 Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
https://
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 Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
https://bugs.lau
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 Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
https://bugs.lau
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 Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
http
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 Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launc
** Tags added: oem-priority originate-from-1981417 somerville
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1984147
Title:
Monitor switcher popup (Super-P) is not displayed on
** 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 Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in
MR on upstream: https://gitlab.gnome.org/GNOME/gnome-
shell/-/merge_requests/2451
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1984147
Title:
Monitor switcher popup (Super-P)
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 Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1983717
T
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 Ubuntu
Desktop Bugs, which is subscribed to gno
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
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
** Changed in: gnome-shell (Ubuntu Jammy)
Status: In Progress => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1984147
Title:
Monitor switcher popup (Super-P)
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 Ubuntu
Desktop Bugs, which is subscrib
** Tags added: originate-from-1997210
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, 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
To manage noti
** Tags added: originate-from-1996036
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, 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
To manage noti
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
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
** 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
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
*** 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
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 Ubuntu
Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu.
https://bugs.launchpad.net/bug
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.
*
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
.
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
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
Importance: Undecided => Low
** Changed in: oem-priority
Assignee: (unassigned) => Yao Wei (medicalwei)
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, 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 Ubuntu
Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu.
https://bugs.launchpad.net/bugs/2037076
Title:
System Details incorrectly shows multiple GPUs
To manage notific
** 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 Ubuntu
Desktop Bugs, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/2087831
Title:
touchscreen has no response a
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
** 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
** 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:
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
** Changed in: oem-priority
Status: New => In Progress
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu.
https://bugs.launchpad.net/bugs/2037076
Title:
System Details incorrectly shows multiple G
** 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
** 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 Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/2087831
Title:
On a laptop
** 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
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 Ubuntu
Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu.
https://bugs.launchpad.net/bugs/2
MR proposed: https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/4188
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/2087831
Title:
On a laptop with NVIDIA graphics and touchscre
** 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
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
** Changed in: oem-priority
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/2087831
Title:
[SRU] On a laptop with NVIDIA graphics and touchscreen, to
** No longer affects: gnome-shell
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, 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 logi
** 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
@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
** 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
Desktop Bugs, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/2069564
Ti
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
Desktop Bu
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
Desktop Bugs, which is subscribed t
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
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
@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
De
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
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 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
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
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
** 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/
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
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
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
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
Desktop Bugs, which is su
83 matches
Mail list logo
