For what it worth that argbToRgba code (which I'd like to move to
GdkPixbuf asap) isn't really used in indicator-multiload as it provides
the actual icons to show, so the shell has "only" to paint them, and
unfortunately this is something that looks somewhat slow.
The argbToRgba function is unfort
This is the same of https://github.com/ubuntu/gnome-shell-extension-
appindicator/issues/236 and the situation seems improved after the
recent changes.
** Bug watch added: github.com/ubuntu/gnome-shell-extension-appindicator/issues
#236
https://github.com/ubuntu/gnome-shell-extension-appindica
This is the same of https://github.com/ubuntu/gnome-shell-extension-
appindicator/issues/226 and the situation seems improved after the
recent changes.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell-extension-appindicator
** Changed in: gnome-shell-extension-appindicator (Ubuntu)
Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0)
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell-extension-appindicator
in Ubuntu.
ht
*** This bug is a duplicate of bug 1558886 ***
https://bugs.launchpad.net/bugs/1558886
** This bug has been marked a duplicate of bug 1558886
gnome-shell crashed with SIGSEGV in _clutter_input_device_reset_scroll_info()
--
You received this bug notification because you are a member of Ubu
** Package changed: gnome-shell (Ubuntu) => mutter (Ubuntu)
** Changed in: mutter (Ubuntu)
Status: Confirmed => Fix Committed
** Changed in: mutter (Ubuntu)
Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0)
** Project changed: gnome-shell => mutter
** Descrip
** Description changed:
+ [ Impact ]
+
+ GNOME Shell starts with a wrong text size
+
+
+ [ Test case ]
+
+ In a terminal run:
+ - Xephyr :2
+
+ In another one:
+ - env DISPLAY=:2 dbus-run-session gnome-shell --x11
+
+ The shell should run in the embedded window, with the correct text siz
Shell and its components should continue working
[ Regression potential ]
There have been fixes in X11 device management, desktop background image
handling, screen-casting and night-switch.
** Affects: mutter (Ubuntu)
Importance: Medium
Assignee: Marco Trevisan (Treviño) (
The focal part of this bug is linked to #1894596 (I didn't include it in
the changelog for auto-closing the bug, sorry).
--
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/1894596
Title:
The focal part of this bug is linked to bug #1887998 (I didn't include
it in the changelog for auto-closing the bug, sorry).
--
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/1894596
Tit
Sorry, I meant bug #1896332
--
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/1894596
Title:
Night Light stays on
To manage notifications about this bug go to:
https://bugs.launchpad.
GNOME Shell and its components should continue working
[ Regression potential ]
There have been fixes in popup-grab handling, gdm view fixes, lockscreen
display changes in some hw, extensions updates
** Affects: gnome-shell (Ubuntu)
Importance: Medium
Assignee: Marco Trevisan (Treviño) (
FYI, I've uploaded the fixed package to focal queue
https://launchpad.net/ubuntu/focal/+queue?queue_state=1&queue_text= it
will take some time for the SRU team to review this.
Once it's ready, you will be notified in bug to test it to confirm it
works (please do it, together with bug #1896332 to m
** Summary changed:
- Update to 3.36.6 and SRU it
+ SRU 3.36.6
--
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/1896334
Title:
SRU 3.36.6
To manage notifications about this bug
gt; Marco Trevisan (Treviño) (3v1n0)
** Summary changed:
- Update to 3.36.6 and SRU it
+ SRU 3.36.6
** Also affects: mutter (Ubuntu Focal)
Importance: Undecided
Status: New
** Also affects: yaru-theme (Ubuntu Focal)
Importance: Undecided
Status: New
** Changed in: yaru-them
@ Marco Giannini,
for 20.10 the fix was ready even before, I didn't advertise it as it's
in a PPA with some more stuff as per the pipewire3 transition (build-
only for now).
But you can grab it at https://launchpad.net/~ci-train-ppa-
service/+archive/ubuntu/4265.1/
--
You received this bug noti
@ Cristiano Nunes,
Interesting, not sure how this is related... I will try to reproduce
that, although it seems unrelated to the fix, and probably something
upstream too.
Feel free to open another bug though (if you can using ubuntu-bug with
the crash file and debug symbols).
In any case we can
gt; Marco Trevisan (Treviño) (3v1n0)
** Also affects: gnome-shell (Ubuntu Focal)
Importance: Undecided
Status: New
** Also affects: yaru-theme (Ubuntu Focal)
Importance: Undecided
Status: New
** Changed in: gnome-shell (Ubuntu Focal)
Importance: Undecided => Medium
** Chang
** No longer affects: yaru-theme (Ubuntu Focal)
--
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/1896332
Title:
SRU 3.36.6
To manage notifications about this bug go to:
https://bugs.
edium
Assignee: Marco Trevisan (Treviño) (3v1n0)
Status: New
** Affects: pipewire (Ubuntu)
Importance: Undecided
Status: New
** Affects: weston (Ubuntu)
Importance: Undecided
Status: New
** Affects: xdg-desktop-portal (Ubuntu)
Importance: Unde
Given that the changes include xdg-desktop-portal implementations, it's
fair to underline that snaps using them have been tested successfully,
and no regression has been reported so far.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to
** Description changed:
[ Impact ]
That's the current GNOME stable update, including some fixes and translation
updates
https://gitlab.gnome.org/GNOME/gnome-shell/-/commits/3.36.6
Since the theme side of the project in ubuntu is shipped via Yaru theme,
that project is included in
This should be fixed by latest SRU in focal as well
** Changed in: gnome-shell-extension-desktop-icons (Ubuntu Focal)
Status: Fix Committed => Fix Released
** Changed in: gnome-shell-extension-desktop-icons (Ubuntu Focal)
Assignee: (unassigned) => Marco Trevisan (Treviño)
This bug has been already fixed as part of 3.36.4-0ubuntu0.20.04.2, and
opened by the SRU tool as it is included again in the changelog as it's
being part of a debian release we've merged with.
So marking as verified (as discussed with SRU team)
** Tags removed: verification-needed verification-n
This bug has been already fixed as part of 3.36.4-0ubuntu0.20.04.2, and
opened by the SRU tool as it is included again in the changelog as it's
being part of a debian release we've merged with.
So marking as verified (as discussed with SRU team)
** Tags removed: verification-needed verification-n
This bug has been already fixed as part of 3.36.4-0ubuntu0.20.04.2, and
opened by the SRU tool as it is included again in the changelog as it's
being part of a debian release we've merged with.
** Tags removed: verification-needed verification-needed-focal
** Tags added: verification-done verifica
This was fixed by gnome-shell-extension-appindicator 34-1
** Changed in: gnome-shell-extension-appindicator (Ubuntu)
Status: New => Fix Released
** Also affects: gnome-shell-extension-appindicator (Ubuntu Focal)
Importance: Undecided
Status: New
--
You received this bug notific
Upstream issue https://github.com/ubuntu/gnome-shell-extension-
appindicator/issues/246
** Description changed:
[ Impact ]
Padding on indicators is too wide, as per double-multiplication of the
same, leading to very spread icons:
https://user-
images.githubusercontent.com/16012374
two times.
--
Upstream fix: https://github.com/ubuntu/gnome-shell-extension-
appindicator/pull/219
** Affects: gnome-shell-extension-appindicator (Ubuntu)
Importance: Medium
Assignee: Marco Trevisan (Treviño) (3v1n0)
Status: Fix Released
** Affects: gnome-shell-extension-appindicat
** Changed in: gnome-shell-extension-appindicator (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell-extension-appindicator
in Ubuntu.
https://bugs.launchpad.net/bugs/1720334
Title:
Upstream issue:
https://github.com/ubuntu/gnome-shell-extension-appindicator/issues/235
Upstream fix:
https://github.com/ubuntu/gnome-shell-extension-appindicator/pull/231
** Description changed:
+ [ Impact ]
+
+ An app-indicator icon does not show when I login using the default gnome
+ sessio
This was fixed by version 34-1
** Changed in: gnome-shell-extension-appindicator (Ubuntu)
Status: New => Fix Released
** Changed in: gnome-shell-extension-appindicator (Ubuntu)
Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0)
** Also affects: gnome-shell-ext
** Tags removed: verification-needed verification-needed-focal
** Tags added: verification-done verification-done-focal
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1892440
Title:
** Changed in: gnome-shell-extension-appindicator (Ubuntu Focal)
Status: New => In Progress
** Changed in: gnome-shell-extension-appindicator (Ubuntu)
Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0)
** Changed in: gnome-shell-extension-appindicator (Ubuntu
: gnome-shell-extension-appindicator (Ubuntu)
Importance: Medium
Assignee: Marco Trevisan (Treviño) (3v1n0)
Status: Fix Released
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell-extension-appindicator
in Ubuntu.
ht
This has been fixed in 34-1
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell-extension-appindicator
in Ubuntu.
https://bugs.launchpad.net/bugs/1896785
Title:
Exported DBus interface is missing info or using wrong names
T
** Description changed:
[ Impact ]
GNOME shell when using this indicator should export the
org.kde.StatusNotifierWatcher dbus interface, although some methods and
properties are missing or invalid
-
[ Test case ]
-
Run:
- gdbus call --session --dest org.gnome.Shell --object
nee: (unassigned) => Marco Trevisan (Treviño) (3v1n0)
** Description changed:
- I had similar issues when 20.04 was released, then it disappeared with
- an upgrade - but sadly it's back. I have short intermittent freezings of
- the OS. About every 15-30 seconds Ubunut freezes for a second or two
** Description changed:
[ Impact ]
Indicators using (big) pixmap icons cause the shell to use a lot of CPU
computation, which interfere with user experience
-
[ Test case ]
- Install mega client from https://mega.nz/sync
- Run it in ubuntu and ensure it doesn't block the UI w
nee: (unassigned) => Marco Trevisan (Treviño) (3v1n0)
** Description changed:
+ [ Impact ]
+
+ Using discord application, causes the shell to slowdown and trigger lots
+ of "unable to lookup icon ..." errors
+
+ [ Test case ]
+
+ Install discord app:
+ - snap install discord
+
+ Run it,
@ David
I think pop-os disabled fractional scaling patch, so get in contact with them
please:
https://github.com/pop-os/mutter/commit/bc7c2658e4c873a28afeaf621fb24a1341c6d74c
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to mutter i
> I don't understand why yaru-theme needs to be updated, either. I see
> that this has been done for yaru-theme once before, but I've found no
> explanation as to why.
I will make it clearer in the top post, but it should be quite easy to
spot looking at the shell's (data subdir) and yaru diffs:
Ah about this:
> If this isn't used for generating the final packages at all, why do
you propose to make users download an update?
Those files aren't included at all into the package, the README.sources
there was included to explain why we have such files, even though they
are not built.
It's ju
@ Cristiano,
please fill another bug for that :)
--
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/1892440
Title:
Shell text with wrong size in mutter 3.36.4-0ubuntu0.20.04.2 (mostly
I've prepared a new package with the whole set of fixes:
https://launchpad.net/ubuntu/bionic/+queue?queue_state=1&queue_text
=gnome-shell
--
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
n the final mutter build
** Affects: mutter (Ubuntu)
Importance: High
Assignee: Marco Trevisan (Treviño) (3v1n0)
Status: Fix Released
** Affects: mutter (Ubuntu Bionic)
Importance: High
Assignee: Marco Trevisan (Treviño) (3v1n0)
Status: In Progress
** Also af
Oh, crazy... This was supposed to be fixed already, looks like something
broke when adapting the patch?!
--
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/1896818
Title:
Gnome-shell cr
I mean, this looks like bug #1889090 is back..
--
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/1896818
Title:
Gnome-shell crash after turn display off in mutter
3.36.6-ubuntu0.20.0
Shell crash and show us a blank screen with the message:
"Oh no! Something has gone wrong."
[ Regression potential ]
- This bug was introduced by Marco Trevisan (Treviño) in the bug 1892440.
+ This very fix was already handled as part of bug #1889090 and we had no
regression report
** Tags removed: verification-needed verification-needed-focal
** Tags added: verification-done verification-done-focal
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1896818
Title:
** Tags removed: verification-needed verification-needed-focal
** Tags added: verification-done verification-done-focal
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1896332
Title:
** Tags removed: verification-needed verification-needed-focal
** Tags added: verification-done verification-done-focal
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1892440
Title:
As per comment
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1887998/comments/13
We can mark this as verified.
** Tags removed: verification-needed verification-needed-focal
** Tags added: verification-done verification-done-focal
--
You received this bug notification because you are a
I forgot to mention this i changelogs, so this will be closed once bug
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1896332 will be
** Changed in: mutter (Ubuntu Focal)
Status: Triaged => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Deskt
As per comment
https://bugs.launchpad.net/mutter/+bug/1857947/comments/11
We can mark this as verified.
** Tags removed: verification-needed verification-needed-focal
** Tags added: verification-done verification-done-focal
--
You received this bug notification because you are a member of Ubunt
As per comment
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1870867/comments/27
We can mark this as verified.
** Tags removed: verification-needed verification-needed-focal
** Tags added: verification-done verification-done-focal
--
You received this bug notification because you are a
Public bug reported:
Fixes various bugs in AuthenTec chip, synapitcs and add goodix reader
support
** Affects: libfprint (Ubuntu)
Importance: Medium
Assignee: Marco Trevisan (Treviño) (3v1n0)
Status: In Progress
--
You received this bug notification because you are a member
signee: (unassigned) => Marco Trevisan (Treviño) (3v1n0)
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to libfprint in Ubuntu.
https://bugs.launchpad.net/bugs/1893719
Title:
Request for adding support for Synaptics fingerprint reade
Sure, but you need to enable Proposed repositories, see
https://wiki.ubuntu.com/Testing/EnableProposed
Remember to disable them once updated, as otherwise you may get earlier
updates that have still to be fully tested.
--
You received this bug notification because you are a member of Ubuntu
Desk
Cristiano, Tim:
This needs some days as all the bugs listed in
https://people.canonical.com/~ubuntu-archive/pending-sru.html (look for
mutter in focal) needs to be marked as "verified" and prove that they
don't cause regressions.
You can help testing the missing bug if you want (It's
https://laun
signed) => Marco Trevisan (Treviño) (3v1n0)
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to libfprint in Ubuntu.
https://bugs.launchpad.net/bugs/1897613
Title:
fprint hangs after first finger scan (fprintd-enroll - fprintd_demo)
Mh, so... I've just tried with the flameshot snap and the latest
extension version, but it works correctly here.
Please, try to do as follow:
- Start a session without flameshot started
In a terminal run:
journalctl -b0 /usr/bin/gnome-shell -ef
Launch flameshot
Tell me what debug output do
All green at
https://launchpad.net/ubuntu/+source/mutter/3.28.4+git20200505-0ubuntu18.04.2
** Tags removed: verification-needed verification-needed-bionic
** Tags added: verification-done verification-done-bionic
--
You received this bug notification because you are a member of Ubuntu
Desktop Bu
Daniel,
Detailed ways to reproduce the crash are explained upstream at
https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/823#note_866367
The crash was happening easily by using the above script, if it doesn't anymore
than it's a verification.
I also verified this in my setup, but preferred
*** This bug is a duplicate of bug 1558886 ***
https://bugs.launchpad.net/bugs/1558886
** This bug is no longer a duplicate of bug 1783673
gnome-shell crashed with SIGSEGV in
clutter_input_device_xi2_get_current_tool →
clutter_device_manager_xi2_translate_event →
clutter_backend_real_tra
*** This bug is a duplicate of bug 1558886 ***
https://bugs.launchpad.net/bugs/1558886
** This bug is no longer a duplicate of bug 1783673
gnome-shell crashed with SIGSEGV in
clutter_input_device_xi2_get_current_tool →
clutter_device_manager_xi2_translate_event →
clutter_backend_real_tra
*** This bug is a duplicate of bug 1558886 ***
https://bugs.launchpad.net/bugs/1558886
** This bug has been marked a duplicate of bug 1558886
gnome-shell crashed with SIGSEGV in _clutter_input_device_reset_scroll_info()
--
You received this bug notification because you are a member of Ubu
*** This bug is a duplicate of bug 1558886 ***
https://bugs.launchpad.net/bugs/1558886
** This bug is no longer a duplicate of bug 1783673
gnome-shell crashed with SIGSEGV in
clutter_input_device_xi2_get_current_tool →
clutter_device_manager_xi2_translate_event →
clutter_backend_real_tra
I think this may be related to
https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1371 I will look
into this
--
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/1899206
Title:
Tweakt
andEnabled=false
** Affects: gdm
Importance: Unknown
Status: Unknown
** Affects: gdm3 (Ubuntu)
Importance: Critical
Assignee: Marco Trevisan (Treviño) (3v1n0)
Status: In Progress
** Tags: groovy
** Bug watch added: gitlab.gnome.org/GNOME/gdm/-/issues #64
Upstream issue: https://gitlab.gnome.org/GNOME/gdm/-/issues/641
** Also affects: gdm via
https://gitlab.gnome.org/GNOME/gdm/-/issues/641
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to
This is critical as it corrupts the system configuration data, and more
importantly it will stop any Nvidia user to use Wayland whenever it's
supported by the closed drivers or switching to free ones.
As per this it needs to be fixed ASAP (when only a limited number of
affected versions are around
@mastorak:
Unfortunately they've only packaged the fixes coming from ubuntu:
https://github.com/pop-os/mutter/commits/master_focal
--
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/18707
Got the same once applied the change to enable fractional scaling in a
new NVIDIA install:
oct 20 18:18:05 marco-HP-Pavilion-Notebook-15-bc5xxx gnome-shell[1625]:
clutter_actor_add_child: assertion 'child->priv->parent == NULL' failed
oct 20 18:18:05 marco-HP-Pavilion-Notebook-15-bc5xxx gnome-she
** Tags removed: verification-needed verification-needed-focal
** Tags added: verification-done verification-done-focal
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell-extension-appindicator
in Ubuntu.
https://bugs.launchpa
** Description changed:
+ [ Impact ]
+
+ When I try to resize an xterm window the same way,
+ this happens instead: as the mouse is moved, the upper-right corner
+ does move, but it doesn't track with the mouse pointer like it should.
+ Meanwhile, the lower-left corner also moves (it should have
** Description changed:
Release: Ubuntu Groovy Gorilla (development branch) 20.10
Package version: 3.38.1-1ubuntu1
+
+ [ Impact ]
When I tile windows using edge tiling, I want the window to tile on the
same edge that I brought it to, however, if the window is mostly in
monitor 1 when
** Changed in: mutter (Ubuntu)
Status: Fix Committed => In Progress
** Changed in: mutter (Ubuntu Groovy)
Status: Fix Committed => In Progress
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to mutter in Ubuntu.
https://bug
in: gnome-settings-daemon (Ubuntu)
Status: New => In Progress
** Changed in: gnome-settings-daemon (Ubuntu)
Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0)
** Bug watch added: gitlab.gnome.org/GNOME/gnome-settings-daemon/-/issues #260
https://gitlab.gnome.org/GN
Anyone can please verify the SRU in focal-proposed?
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell-extension-appindicator
in Ubuntu.
https://bugs.launchpad.net/bugs/1884396
Title:
Ubuntu freezing intermittently when the
As per the comments, I think I can mark this as resolved, change it
otherwise if regressions are found
** Tags removed: verification-needed verification-needed-focal
** Tags added: verification-done verification-done-focal
--
You received this bug notification because you are a member of Ubuntu
While Bionic could be maybe supported, that would likely require newer
SSSD.
Maybe in such case a pam_pkcs11 based solution could be provided, but
it's quite a lot of backporting work which would need SRU team to agree
with.
--
You received this bug notification because you are a member of Ubunt
** Tags added: libfprint
** Tags removed: libfprint
** Tags added: fingerprint
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm3 in Ubuntu.
https://bugs.launchpad.net/bugs/1882884
Title:
FP Auth : Multi user Scenario
To manage
** Tags added: fingerprint
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm3 in Ubuntu.
https://bugs.launchpad.net/bugs/1865838
Title:
no error displayed on failed fingerprint authentication
To manage notifications about this bu
*** This bug is a duplicate of bug 1875845 ***
https://bugs.launchpad.net/bugs/1875845
** This bug has been marked a duplicate of bug 1875845
keyring cannot be unlocked if used fingerprint to login gnome session
--
You received this bug notification because you are a member of Ubuntu
Desk
Drivers requests are upstream bugs and as such should be redirected to
the official wiki
- https://gitlab.freedesktop.org/libfprint/wiki/-/wikis/Unsupported-
Devices
As per this, I'm closing all the requests, I please you to update that
wiki page if needed.
** Changed in: libfprint (Ubuntu)
Drivers requests are upstream bugs and as such should be redirected to
the official wiki
- https://gitlab.freedesktop.org/libfprint/wiki/-/wikis/Unsupported-
Devices
As per this, I'm closing all the requests, I please you to update that
wiki page if needed.
** Changed in: libfprint (Ubuntu)
Drivers requests are upstream bugs and as such should be redirected to
the official wiki
- https://gitlab.freedesktop.org/libfprint/wiki/-/wikis/Unsupported-
Devices
As per this, I'm closing all the requests, I please you to update that
wiki page if needed.
** Changed in: libfprint (Ubuntu)
Drivers requests are upstream bugs and as such should be redirected to
the official wiki
- https://gitlab.freedesktop.org/libfprint/wiki/-/wikis/Unsupported-
Devices
As per this, I'm closing all the requests, I please you to update that
wiki page if needed.
** Changed in: libfprint (Ubuntu)
Drivers requests are upstream bugs and as such should be redirected to
the official wiki
- https://gitlab.freedesktop.org/libfprint/wiki/-/wikis/Unsupported-
Devices
As per this, I'm closing all the requests, I please you to update that
wiki page if needed.
** Changed in: libfprint (Ubuntu)
Drivers requests are upstream bugs and as such should be redirected to
the official wiki
- https://gitlab.freedesktop.org/libfprint/wiki/-/wikis/Unsupported-
Devices
As per this, I'm closing all the requests, I please you to update that
wiki page if needed.
** Changed in: libfprint (Ubuntu)
Drivers requests are upstream bugs and as such should be redirected to
the official wiki
- https://gitlab.freedesktop.org/libfprint/wiki/-/wikis/Unsupported-
Devices
As per this, I'm closing all the requests, I please you to update that
wiki page if needed.
** Changed in: libfprint (Ubuntu)
Drivers requests are upstream bugs and as such should be redirected to
the official wiki
- https://gitlab.freedesktop.org/libfprint/wiki/-/wikis/Unsupported-
Devices
As per this, I'm closing all the requests, I please you to update that
wiki page if needed.
** Changed in: libfprint (Ubuntu)
Drivers requests are upstream bugs and as such should be redirected to
the official wiki
- https://gitlab.freedesktop.org/libfprint/wiki/-/wikis/Unsupported-
Devices
As per this, I'm closing all the requests, I please you to update that
wiki page if needed.
** Changed in: libfprint (Ubuntu)
Drivers requests are upstream bugs and as such should be redirected to
the official wiki
- https://gitlab.freedesktop.org/libfprint/wiki/-/wikis/Unsupported-
Devices
As per this, I'm closing all the requests, I please you to update that
wiki page if needed.
** Changed in: libfprint (Ubuntu)
Libfprint changed enough not to make this bug valid anymore, reopen if
needed but when testing with libfprint 1.90 or older.
** Changed in: libfprint (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed
That panel changed recently so please test it again with the new one.
** Changed in: libfprint (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to libfprint in Ubuntu.
https://bugs.launchpad.net/bugs
** Changed in: libfprint (Ubuntu)
Status: Triaged => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to libfprint in Ubuntu.
https://bugs.launchpad.net/bugs/1750467
Title:
Backport upstream security fix patch
To ma
Drivers requests are upstream issues and as such should be redirected to
the official wiki:
- https://gitlab.freedesktop.org/libfprint/wiki/-/wikis/Unsupported-
Devices
As per this, I'm closing all the requests, I please you to update that
wiki page if needed.
** Changed in: libfprint (Ubuntu)
Drivers requests are upstream bugs and as such should be redirected to
the official wiki
- https://gitlab.freedesktop.org/libfprint/wiki/-/wikis/Unsupported-
Devices
As per this, I'm closing all the requests, I please you to update that
wiki page if needed.
** Changed in: libfprint (Ubuntu)
301 - 400 of 2091 matches
Mail list logo
