Hey Christian, not much from a first pass.
It's all GPL/LGPL code (check also https://salsa.debian.org/vmware-
packaging-team/pkg-open-vm-tools/-/blob/master/debian/copyright), while
I had to sign a CLA, but that's not a big deal.
--
You received this bug notification because you are a member
Branch supporting libfuse3 is ready at https://github.com/vmware/open-
vm-tools/pull/544
** Changed in: open-vm-tools (Ubuntu)
Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0)
** Changed in: open-vm-tools (Ubuntu)
Status: New => In Progress
--
You received th
I've done some code for this, the port is at
https://github.com/flatpak/xdg-desktop-portal/pull/634
** Changed in: xdg-desktop-portal (Ubuntu)
Status: Triaged => In Progress
** Changed in: xdg-desktop-portal (Ubuntu)
Assignee: James Henstridge (jamesh) => Marco Trevisan (T
Upstream fix https://gitlab.gnome.org/GNOME/gnome-
session/-/merge_requests/71
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1944223
Title:
Wayland Session can't be run on supported NVIDIA setups
(Ubuntu)
Importance: High
Assignee: Marco Trevisan (Treviño) (3v1n0)
Status: In Progress
** Tags: nvidia rls-ii-incoming
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1944223
Title
** Description changed:
GDM 41.alpha can start GNOME wayland sessions when used with the new
NVIDIA drivers 470 which natively support wayland.
It would be good to do proper testing of the new drivers in Impish to
ensure that most of the users can take advantage of the default ubuntu
Public bug reported:
GDM 41.alpha can start GNOME wayland sessions when used with the new
NVIDIA drivers 470 which natively support wayland.
It would be good to do proper testing of the new drivers in Impish to
ensure that most of the users can take advantage of the default ubuntu
desktop
I think wasn't built as per missing pango build on i386, that's now
fixed so shoudl just trigger a rebuild of gtk4 itself.
Probably though an upload though.
** Tags added: regression-update
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
** Summary changed:
- [MIR] fuse3 as a dependency of qemu 6.0
+ [MIR] fuse3 as a dependency of qemu 6.0 and GNOME apps
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1934510
Title:
[MIR] fuse3 as a
It seems it can't be verified with anything else that isn't a CD/DVD, I
tried to emulate it using vmware/virtualbox but no luck so far (at least
on 21.10 with GNOME 40).
In the same scenario nautilus updates the icon properly right?
Also, nothing from the journal mentions the dock, right?
--
This should be fixed by the new version of the dock.
** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Tags added: likely-dup
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1912211
Title:
Can't scroll pages in "Show Applications" when Ubuntu Dock is loaded
To manage notifications about this bug
Yeah, wasn't using the libgnome-desktop3 API though, so we should just
drop it from unity-settings-daemon.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1931901
Title:
Revert background key patch
So the function isn't really used anywhere we care about, so I think we
can just drop it
https://paste.ubuntu.com/p/tyN5Vp99Fj/
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1931901
Title:
Revert
** Changed in: gnome-control-center (Ubuntu)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1857340
Title:
Setting "IPv6 Method" to "Disable" does not
Public bug reported:
/etc/os-release can provide a logo file, this is now used by gnome-
control-center to show the logo into the info panel.
If ubuntu would provide its logo name in such file we would be able to
remove the downstream patch that forces the usage of
No hang reported with
$ apt-cache policy gnome-shell
gnome-shell:
Installed: 3.38.3-2ubuntu0.20.10.2
Candidate: 3.38.3-2ubuntu0.20.10.2
Version table:
*** 3.38.3-2ubuntu0.20.10.2 500
500 http://us.archive.ubuntu.com/ubuntu groovy-proposed/main amd64
Packages
100
$ apt-cache policy gnome-shell
gnome-shell:
Installed: 3.38.3-2ubuntu0.20.10.2
Candidate: 3.38.3-2ubuntu0.20.10.2
Version table:
*** 3.38.3-2ubuntu0.20.10.2 500
500 http://us.archive.ubuntu.com/ubuntu groovy-proposed/main amd64
Packages
100 /var/lib/dpkg/status
All works fine from my test
$ apt-cache policy gnome-shell
gnome-shell:
Installed: 3.38.3-2ubuntu0.20.10.2
Candidate: 3.38.3-2ubuntu0.20.10.2
Version table:
*** 3.38.3-2ubuntu0.20.10.2 500
500 http://us.archive.ubuntu.com/ubuntu groovy-proposed/main amd64
Packages
100
** Changed in: mutter (Ubuntu)
Status: Triaged => In Progress
** Changed in: gnome-shell (Ubuntu)
Status: Triaged => In Progress
** Changed in: gnome-shell (Ubuntu)
Status: In Progress => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
ntu Hirsute)
Importance: Undecided
Status: New
** Changed in: gdm3 (Ubuntu Hirsute)
Importance: Undecided => Medium
** Changed in: gdm3 (Ubuntu Hirsute)
Status: New => Fix Committed
** Changed in: gdm3 (Ubuntu Hirsute)
Assignee: (unassigned) => Marco Trevisan (Tre
As expained in IRC:
23:42 bdmurray: on https://bugs.launchpad.net/bugs/1917362 I did
upload ages ago in hirsute (at the time, as impish wasn't open yet). But it has
never been copied to impish (I feel)
23:42 Launchpad bug 1917362 in sssd (Ubuntu) "PAM: smartcard owner
isn't associated to
** Also affects: gnome-shell (Ubuntu Hirsute)
Importance: Undecided
Status: New
** Also affects: gnome-shell (Ubuntu Focal)
Importance: Undecided
Status: New
** Changed in: gnome-shell (Ubuntu Focal)
Status: New => Fix Committed
** Changed in: gnome-shell (Ubuntu
** Changed in: gnome-shell (Ubuntu Impish)
Status: Won't Fix => In Progress
** Changed in: gnome-shell (Ubuntu Impish)
Assignee: Daniel van Vugt (vanvugt) => Marco Trevisan (Treviño) (3v1n0)
--
You received this bug notification because you are a member of Ubuntu
Bugs,
** Tags added: fixed-in-3.38.5
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1915929
Title:
gnome-shell-calendar-server assert failure on arm64: double free or
corruption (fasttop)
To manage
Public bug reported:
We disabled RDP clipoard as part of gnome-remote-desktop 40.1-1 as it
requires libfuse-3 to be in main.
** Affects: gnome-remote-desktop (Ubuntu)
Importance: Medium
Status: Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs,
This was fixed in gnome-remote-desktop 0.1.9-3
** Changed in: gnome-remote-desktop (Ubuntu)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1916840
Title:
** Description changed:
+ [ Impact ]
+
On my laptop's 15.6 inch, 3840 x 2160 pixel (282 PPI) display, the
- available scaling options in the gnome-control-center (version:
- 1:3.30.0-0ubuntu1, on Cosmic) display settings are limited to 100, 200,
- 300, and 400%. This is insufficient as 200% is
Trevisan (Treviño) (3v1n0)
** Also affects: gnome-control-center (Ubuntu Focal)
Importance: Undecided
Status: New
** Changed in: gnome-control-center (Ubuntu Focal)
Importance: Undecided => Medium
** Changed in: gnome-control-center (Ubuntu Focal)
Status: New => Triaged
** Ch
padding
[1] https://gitlab.gnome.org/GNOME/gnome-shell/-/merge_requests/1415
** Affects: yaru-theme (Ubuntu)
Importance: Low
Assignee: Marco Trevisan (Treviño) (3v1n0)
Status: In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
Tested with another user with no enrolled prints, and login and locking
operations work fine.
❯ apt-cache policy gnome-shell
gnome-shell:
Installato: 3.36.9-0ubuntu0.20.04.1
Candidato: 3.36.9-0ubuntu0.20.04.1
Tabella versione:
*** 3.36.9-0ubuntu0.20.04.1 400
Hitting escape to cancel authentication works promptly now
❯ apt-cache policy gnome-shell
gnome-shell:
Installato: 3.36.9-0ubuntu0.20.04.1
Candidato: 3.36.9-0ubuntu0.20.04.1
Tabella versione:
*** 3.36.9-0ubuntu0.20.04.1 400
400
Chris, as said the change we did in yaru is just applying to gnome-shell
code, reflecting gnome-shell upstream code changes so putting it in
different bug wouldn't be correct in this case.
However I'm doing that.
Also, I can confirm gnome-shell 3.36.9 as verified here
❯ apt-cache policy
Both with fprintd-enroll and using g-c-c now a password prompt is
required when enrolling a new fingerprint.
This works concurrently when multiple users are trying to enroll.
❯ apt-cache policy fprintd
fprintd:
Installato:
The pam module side of this bugs is fixed here, tested with various
sensors.
❯ apt-cache policy fprintd
fprintd:
Installato: 1.90.9-1~ubuntu20.04.1
Candidato: 1.90.9-1~ubuntu20.04.1
Tabella versione:
*** 1.90.9-1~ubuntu20.04.1
Tested with various sensors, and all seems to behave as expected with
this version.
Plus the expected security fixes.
❯ apt-cache policy fprintd
fprintd:
Installato: 1.90.9-1~ubuntu20.04.1
Candidato: 1.90.9-1~ubuntu20.04.1
❯ apt-cache policy gnome-shell
gnome-shell:
Installato: 3.36.9-0ubuntu0.20.04.1
Candidato: 3.36.9-0ubuntu0.20.04.1
Tabella versione:
*** 3.36.9-0ubuntu0.20.04.1 400
400 http://archive.ubuntu.com/ubuntu focal-proposed/main amd64 Packages
Only one worker is
Confirmed working, errors will be handled properly and will be possible
to enroll a new finger afterwards.
❯ apt-cache policy gnome-control-center
gnome-control-center:
Installato: 1:3.36.5-0ubuntu2
Candidato: 1:3.36.5-0ubuntu2
Tabella
signed) => Marco Trevisan (Treviño) (3v1n0)
** Changed in: gjs (Ubuntu Hirsute)
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/1927840
Title:
[SRU] Update to 1.68.
Also gnome-shell has a dynamic runtime dependency on malcontent, so in
order to enable this on ubuntu we should have it in main
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1892456
Title:
[MIR]
** Tags added: rls-ff-incoming
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1918044
Title:
(Update libgweather to 3.36.2) Weather forecast and info is not
available anymore
To manage
Using this for a while, no regression spotted so far, while new emojis
are all showing
❯ apt-cache policy fonts-noto-color-emoji
fonts-noto-color-emoji:
Installato: 0~20200916-1~ubuntu20.04.1
Candidato: 0~20200916-1~ubuntu20.04.1
Tabella versione:
*** 0~20200916-1~ubuntu20.04.1 400
3.36.9-0ubuntu0.20.04.1 is still in proposed, so not yet released.
Monitor https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1919143 to
also mark this as released.
** Changed in: mutter (Ubuntu Focal)
Status: Fix Released => Fix Committed
--
You received this bug notification
No regression noticed so far.
❯ apt-cache policy mutter
mutter:
Installato: 3.36.9-0ubuntu0.20.04.1
Candidato: 3.36.9-0ubuntu0.20.04.1
Tabella versione:
*** 3.36.9-0ubuntu0.20.04.1 400
400 http://archive.ubuntu.com/ubuntu focal-proposed/main amd64 Packages
100
Sure, so yes 1.67.2 was a unstable version (in gnome, the libraries that
follow the old versioning schema use odd minor version numbers for
unstable versions).
The first stable version of the serie was 1.68.0, but it was affected by
mayor crashes [1] and so we decided to delay releasing it to the
** Description changed:
+ [ Impact ]
+
+ Gnome shell crashes when unexpected references happens on other threads
+
+ [ Test case ]
+
+ Createa file called modify.py:
+
+ #!/usr/bin/env python3
+
+ import time
+ import random
+
+ while True:
+ time.sleep(0.001)
+ with
** Changed in: gnome-control-center (Ubuntu)
Status: Confirmed => Triaged
** Changed in: gnome-control-center (Ubuntu)
Importance: Undecided => Medium
** Changed in: gnome-control-center (Ubuntu)
Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0)
--
You received
Do you have a reproducer for this?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1926863
Title:
gjs eats all available RAM and Freezes Computer
To manage notifications about this bug go to:
are kept referenced by gjs and not
released when nothing else
need them
2. New crashes or dead-locks when objects are (un)reffed from other threads
** Affects: gjs (Ubuntu)
Importance: Medium
Assignee: Marco Trevisan (Treviño) (3v1n0)
Status: Fix Committed
** Tags
The package is waiting in the SRU queue
https://launchpad.net/ubuntu/hirsute/+queue?queue_state=1_text=gjs
you may ask in #ubuntu-release to speed it up :)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Hi,
Related to the desktop team specific needs, I wanted to mention that at
the current state we don't expect to need or support pam-pkcs11 given
that we want to rely only on pam-sss (that should be at this time more
than enough for any need), other than being already in main.
So, while in
Christian, please submit another bug for the specific issue, so here we
can just track the update to 3.36.9 (and I've reproduced it once running
on pure mutter).
However, for some reason I can't either run your test case in latest
mutter.
--
You received this bug notification because you are a
Isn't better to use bindings now instead of those env variables?
As they tend to be a bit fragile...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1849478
Title:
[snap] (experimental) pipewire
** Changed in: ubuntu-dev-tools (Ubuntu)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1926166
Title:
DEBOOTSTRAP_PROXY and --debootstrap-proxy are undocumented
Public bug reported:
It's supported but not mentioned in the manual
** Affects: ubuntu-dev-tools (Ubuntu)
Importance: Undecided
Status: New
** Summary changed:
- DEBOOTSTRAP_PROXY is undocumented
+ DEBOOTSTRAP_PROXY and --debootstrap-proxy are undocumented
--
You received this
FYI SRU is now handled as part of
https://bugs.launchpad.net/ubuntu/+source/fonts-noto-color-
emoji/+bug/1926047
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1870794
Title:
Missing some unicode 13
** Description changed:
[ Impact ]
Many new emoji supported by various social platforms are not currently
visible in Ubuntu 20.04, because of old font (even though the shipped
ICU supports this version).
here's a list for Unicode 13.0 and 13.1:
-
** Summary changed:
- [SRU 缾] Update to 20201225 (to support missing emojis from unicode 13.1)
+ [SRU 缾] Update to 20200916 (to support missing emojis from unicode 13.1)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Tags added: rls-ff-incoming
** Also affects: gnome-shell-extension-desktop-icons-ng (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/1926070
ged in: fonts-noto-color-emoji (Ubuntu)
Assignee: Marco Trevisan (Treviño) (3v1n0) => (unassigned)
** Description changed:
[ Impact ]
Many new emoji supported by various social platforms are not currently
visible in Ubuntu 20.04, because of old font (even though the shipped
ICU su
** Description changed:
[ Impact ]
Many new emoji supported by various social platforms are not currently
- visible in Ubuntu 20.04, here's a list for Unicode 13 and Unicode 13.0:
+ visible in Ubuntu 20.04, because of old font (even though the shipped
+ ICU supports this version).
-
** Description changed:
[ Impact ]
Many new emoji supported by various social platforms are not currently
visible in Ubuntu 20.04, here's a list for Unicode 13 and Unicode 13.0:
https://emojipedia.org/emoji-13.0/
https://emojipedia.org/emoji-13.1/
[ Test case ]
This
Assignee: Marco Trevisan (Treviño) (3v1n0)
Status: In Progress
** Affects: fonts-noto-color-emoji (Ubuntu Focal)
Importance: Wishlist
Assignee: Marco Trevisan (Treviño) (3v1n0)
Status: In Progress
** Tags: upgrade-software-version
** Also affects: fonts-
** Tags removed: verification-needed verification-needed-hirsute
** Tags added: verification-done verification-done-hirsute
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1923267
Title:
Gjs promises
** Description changed:
+ [ Impact ]
+
+ As per glib commit
+ https://gitlab.gnome.org/GNOME/glib/-/commit/d52728f99
+ Gio.File.new_for_path("") returns a GDummyFile implementation, while
+ Gio._promisify relies on it being a LocalFile, so we don't promisify the
+ right methods.
+
+ [ Test case
** Summary changed:
- indicator-multiload app broken after upgrading libglib2.0-0 2.67.5-2 to
2.68.0-1
+ Gjs promises on Gio.File operations don't work anymore after upgrading
libglib2.0-0 2.67.5-2 to 2.68.0-1 (and indicator-multiload app broke)
--
You received this bug notification because
d in: gjs (Ubuntu)
Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0)
** Changed in: gjs (Ubuntu)
Importance: Medium => High
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1923267
Tit
** Description changed:
+ [ Impact ]
+
+ Smartcard user is not selected automatically when inserting a smartcard
+
+ [ Test case ]
+
Insert a smartcard that has an user associated to it:
- -> gdm is expected to select the user associated to it and allow
authentication
+ -> gdm is expected
> Does this mean that we can close this bug for SSSD, then?
I think no, as still the problem stands with multi-certificates cards.
But I think we can fix it in II.
> Does this mean that we can close this bug for SSSD, then?
Yeah, I'm doing it now, I prefer to have at least the GDM side to be in
ned) => Marco Trevisan (Treviño) (3v1n0)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1820859
Title:
nautilus --version segfaults in
g_application_impl_get_dbus_object_path
To manage notific
** Tags removed: 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/1820859
Title:
nautilus --version segfaults in
g_application_impl_get_dbus_object_path
To manage notifications
** 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/1820859
Title:
nautilus --version segfaults in
g_application_impl_get_dbus_object_path
To manage notifications about
Sergio, so thanks for this...
>From a further check I've seen that the main case (card with single
certificate) can be handled also without such commits, and I can't test
the multiple-certificates case locally.
So we can avoid picking this of if needed SRU it, there's a unit test
covering the
Testing this for a while now, no problem noticed
❯ apt-cache policy gjs
gjs:
Installato: 1.64.5-0ubuntu0.20.04.01
Candidato: 1.64.5-0ubuntu0.20.04.01
Tabella versione:
*** 1.64.5-0ubuntu0.20.04.01 400
** Tags removed: verification-needed
Using test indicator, and scrolling on a test label
Signal "scroll-event" emitted. Steps: 1, Direction: 1
Signal "scroll-event" emitted. Steps: 1, Direction: 1
Signal "scroll-event" emitted. Steps: 1, Direction: 1
Signal "scroll-event" emitted. Steps: 1, Direction: 1
Signal "scroll-event"
Confirmed working:
method call time=1618505915.474415 sender=:1.35592 -> destination=:1.34
serial=17 path=/StatusNotifierWatcher; interface=org.kde.StatusNotifierWatcher;
member=RegisterStatusNotifierItem
string "/org/ayatana/NotificationItem/Hello"
signal time=1618505915.487399
** Changed in: gnome-shell (Ubuntu)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1921465
Title:
gnome-shell crashed with SIGSEGV in
** Changed in: mutter (Ubuntu)
Importance: Undecided => Low
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1922539
Title:
Option "-listen" for file descriptors is deprecated. Please use
** Tags removed: rls-ff-incoming
** Tags added: rls-hh-incoming
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1922839
Title:
Opening new tab in gnome-terminal launched from nautilus loses most
** Tags added: rls-ff-incoming
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1922839
Title:
Opening new tab in gnome-terminal launched from nautilus loses most
environment variables
To manage
> Should the docs be clarified, so the case with no devices is covered?
I think this would be easier for now.
We can't easier expose to GCC whether an unsupported device is available
for now, so changing it could be not trivial.
** Changed in: ubuntu-docs (Ubuntu)
Status: Incomplete =>
Those will be generated as soon as mutter will hit proposed.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1919143
Title:
SRU mutter to 3.36.9
To manage notifications about this bug go to:
Yes, the fix is in the focal queue for some days now, once SRU team will
approve it will be available in proposed repositories for user
verification.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Amr,
Thanks for pointing it out!
I've uploaded a yaru package as well!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1921963
Title:
SRU 3.36.9
To manage notifications about this bug go to:
** Changed in: gdm (Ubuntu)
Status: In Progress => Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1865838
Title:
no error displayed on failed fingerprint authentication
To manage
Seb, I've pushed the relevant changes to salsa for focal, when you can
do a release please :)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1915174
Title:
Fingerprint enrollment error stops user to
Focal)
Status: New => In Progress
** Changed in: gnome-shell (Ubuntu Focal)
Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0)
** Changed in: gnome-shell (Ubuntu)
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Ubu
Hi Rex, took a while but it's now i focal queue.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1905825
Title:
[SRU] Disable CRTCs when system becomes headless
To manage notifications about this
Focal side of the bug should have been fixed by
https://launchpad.net/ubuntu/+source/mutter/3.36.6-1ubuntu0.20.04.1
** Changed in: mutter (Ubuntu Focal)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
This was fixed as part of
https://launchpad.net/ubuntu/+source/mutter/3.36.7+git20201123-0.20.04.1
** Changed in: mutter (Ubuntu Focal)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
signed) => Marco Trevisan (Treviño) (3v1n0)
** Changed in: mutter (Ubuntu)
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1919143
Title:
SRU mutter to 3.36.
** Changed in: gnome-shell (Ubuntu Focal)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1898005
Title:
gnome-shell crashed with SIGABRT in
** Summary changed:
- Update mutter to 3.36.9
+ SRU mutter to 3.36.9
** Tags added: upgrade-software-version
** Changed in: mutter (Ubuntu)
Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0)
** Changed in: mutter (Ubuntu)
Status: Triaged => In Progress
** Descr
** Description changed:
[ Impact ]
No fingerprint errors are exposed on fingerprint login failures.
from journalctl, gdm-fingerprint shows error there after retried 5 times
of fingerprint login failed, so I open this issue here.
-
[ Test case ]
1. enroll fingerprint for
** Description changed:
- This bug is for the login package. This only affects users of the development
release and does not affect stable users. The bug in the password entry causes
either the password to be entered only for the login to hang, or when
attempting to enter the password, the
of icons for notifications.
** Affects: gnome-shell-extensions (Ubuntu)
Importance: Wishlist
Assignee: Marco Trevisan (Treviño) (3v1n0)
Status: In Progress
** Tags: upgrade-software-version
** Changed in: gnome-shell-extensions (Ubuntu)
Assignee: (unassigned) => Ma
** Description changed:
+ [ Impact ]
+
My system version is 20.10. I upgraded from 20.04. I found such a
problem, the tray icon cannot be displayed when the system is turned on
or restarted, but if I kill the process and restart it, it will be fine.
I searched on Google and didn't see
/ password again
[ Regression potential ]
Authentication fails even if it should not, user authentication may lead
to user to see the user lists under gdm when not expected.
** Affects: gnome-shell (Ubuntu)
Importance: Medium
Assignee: Marco Trevisan (Treviño) (3v1n0)
Status: Fix
when *not* using -partial_chain
** Changed in: sssd (Ubuntu)
Status: New => In Progress
** Changed in: sssd (Ubuntu)
Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0)
** Changed in: sssd (Ubuntu)
Importance: Undecided => High
--
You received this bug not
Yeah, sure...
As per man page:
-partial_chain
Allow verification to succeed even if a complete chain cannot be
built to a self-signed trust-anchor,
provided it is possible to construct a chain to a trusted
certificate that might not be self-signed.
And you can test it
301 - 400 of 9418 matches
Mail list logo
