d) is the new upstream version really necessary? In jammy only patches
are being applied. Are you claiming the SRU MRE exception[1] for this
update in noble?
1. https://canonical-sru-docs.readthedocs-
hosted.com/en/latest/reference/requirements/#new-upstream-microreleases
--
You received this b
a) Are these changes really needed for noble?
+ * debian/control
+- Bump minimum meson to 1.2.0 & GTK4 to 4.12.0
+- Replace GTK+ with GTK in package description
Noble has libgtk-4-dev 4.14.2+ds-1ubuntu1, and meson 1.3.2-1ubuntu1.
b) Considering this is a version upgrade, I would expect
The current apparmor profile for digikam in oracular has these rules:
/usr/lib/x86_64-linux-gnu/qt5/libexec/QtWebEngineProcess cx ->
&digikam//QtWebEngineProcess,
/usr/lib/aarch64-linux-gnu/qt5/libexec/QtWebEngineProcess cx ->
&digikam//QtWebEngineProcess,
/usr/lib/arm-linux-gnueabihf/qt5/
Please clarify the testing that was done, and *with which version
exactly* (as requested in comment #12). This package had to go through a
revert in the previous attempt to update to 1.72.4 (see version
1.72.4-0ubuntu0.22.04.3~really.is.1.72.2.0ubuntu2), and we need more
confidence.
** Tags remove
The verification of the Stable Release Update for evolution has
completed successfully and the package is now being released to
-updates. Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you encounter
The verification of the Stable Release Update for evolution has
completed successfully and the package is now being released to
-updates. Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you encounter
The verification of the Stable Release Update for gnome-shell has
completed successfully and the package is now being released to
-updates. Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you encount
The verification of the Stable Release Update for gnome-shell has
completed successfully and the package is now being released to
-updates. Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you encount
The verification of the Stable Release Update for gnome-shell has
completed successfully and the package is now being released to
-updates. Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you encount
The verification of the Stable Release Update for gnome-shell has
completed successfully and the package is now being released to
-updates. Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you encount
The verification of the Stable Release Update for gnome-shell has
completed successfully and the package is now being released to
-updates. Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you encount
The verification of the Stable Release Update for gnome-shell has
completed successfully and the package is now being released to
-updates. Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you encount
Adding a task for gdm3, since it seems affected by dropping
user_readenv=1 from its pam configuration.
--
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/2059859
Title:
pam_env(sshd:sessi
Regarding the LC_* variables in openssh's config, I understand it's not
a direct replacement for ~/.pam_environment, because that is on the
*server*, and we would be sending the *client* vars.
** Also affects: gdm3 (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug not
The verification of the Stable Release Update for file-roller has
completed successfully and the package is now being released to
-updates. Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you encount
The verification of the Stable Release Update for nautilus has completed
successfully and the package is now being released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you encounter a
If that is the underlying cause I wouldn't call it a hardware issue, I
would call it an implementation oversight.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubuntu.
https://bugs.launchpad.net/bugs/1832249
> this is an extremely easy fix in code to make
As this is a long bug, with many comments and different scenarios at
play, I'm a bit lost by now.
What is the easy code fix you are referring to, do you have a link to a
patch?
Also, please restate what is the scenario we are talking about here.
Ub
Public bug reported:
I'm seeing a number of issues with the on-screen keyboard.
* The on-screen keyboard pops up despite being disabled in the Ubuntu Settings.
* The on-screen keyboard pops up even though a physical keyboard is connected.
* When the on-screen keyboard is active, Ctrl+Tab in Firef
I can confirm the issue (I am on ubuntu 22.04 nvidia + x11). gnome-
terminal, emacs and similar applications was lagging. Starting an
application that updated the screen continuously (such as glxgears)
seems to have alleviated the problem.
Downgrading mutter to from 42.9-0ubuntu7 (which I got in t
The test failure on armhf persists:
939s # Running test: mutter-13/fullscreen-maximize.test
940s # Executing: mutter-13/fullscreen-maximize.test
941s # FAIL: mutter-13/fullscreen-maximize.test (Child process exited with code
1)
941s not ok - mutter-13/fullscreen-maximize.test
--
You received th
The test failure on armhf persists:
939s # Running test: mutter-13/fullscreen-maximize.test
940s # Executing: mutter-13/fullscreen-maximize.test
941s # FAIL: mutter-13/fullscreen-maximize.test (Child process exited with code
1)
941s not ok - mutter-13/fullscreen-maximize.test
--
You received th
There is an armhf DEP8 failure that I just retriggered, let's see if it
passes in the next run.
--
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/2054510
Title:
Incomplete screen redra
There is an armhf DEP8 failure that I just retriggered, let's see if it
passes in the next run.
--
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/2051074
Title:
Mirror mode doesn't wor
mantic verification
I used mutter from mantic-proposed:
andreas@nsnx2:~$ apt-cache policy mutter
mutter:
Installed: 45.2-0ubuntu2~really45.0
Candidate: 45.2-0ubuntu2~really45.0
Version table:
*** 45.2-0ubuntu2~really45.0 100
100 http://br.archive.ubuntu.com/ubuntu mantic-proposed
The DEP8 tests are green now.
I'm going to verify this revert for mantic, which is currently in
mantic-proposed. But note I have NOT been able to reproduce the stuttering in
firefox with the mutter package from mantic-updates (45.2-0ubuntu1). I tried:
- wayland
- xorg
- native resolution (2880x1
I see this was filed on the 13th. Had this been mentioned in the 45.2
mantic SRU bug[1], I wouldn't have released the package to updates on
the 14th :/
1. https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2043000
--
You received this bug notification because you are a member of Ubuntu
Deskt
Hello shine, or anyone else affected,
Accepted gnome-shell into focal-proposed. The package will build now and
be available at https://launchpad.net/ubuntu/+source/gnome-
shell/3.36.9-0ubuntu0.20.04.3 in a few hours, and then in the -proposed
repository.
Please help us by testing this new package
Hello Kai-Chuan, or anyone else affected,
Accepted gnome-shell into focal-proposed. The package will build now and
be available at https://launchpad.net/ubuntu/+source/gnome-
shell/3.36.9-0ubuntu0.20.04.3 in a few hours, and then in the -proposed
repository.
Please help us by testing this new pac
The verification of the Stable Release Update for mutter has completed
successfully and the package is now being released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you encounter a r
The verification of the Stable Release Update for mutter has completed
successfully and the package is now being released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you encounter a r
The verification of the Stable Release Update for mutter has completed
successfully and the package is now being released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you encounter a r
> I wanted to test the updated version of mutter so a couple of days ago I
> enabled the `proposed`
> repository, but I didn't receive any updates.
Jeremie, you also have to pass "-t mantic-proposed" in the apt command
line.
--
You received this bug notification because you are a member of Ubu
Also, before release, please someone clarify this statement about a mesa
regression in noble with 45.1 presumably:
"It will get updated to 45.2 (and eventually to 46) after a mesa
regression is handled."
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which
Hello Jeremie, or anyone else affected,
Accepted mutter into mantic-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/mutter/45.2-0ubuntu1
in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
https://wik
Hello Jeremy, or anyone else affected,
Accepted mutter into mantic-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/mutter/45.2-0ubuntu1
in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
https://wiki
Hello Gonzalo, or anyone else affected,
Accepted mutter into mantic-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/mutter/45.2-0ubuntu1
in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
https://wik
noble-proposed still only has 45.1-2ubuntu1, btw. It should get 45.2
before this update is released to mantic. I updated the main bug status
to reflect that noble isn't fixed nor committed yet.
** Changed in: mutter (Ubuntu)
Status: Fix Committed => Triaged
--
You received this bug notifi
The verification of the Stable Release Update for gnome-shell has
completed successfully and the package is now being released to
-updates. Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you encount
Marking as incomplete pending the completion of what was requested in
comment #2 above. I also added tasks for the missing ubuntu releases.
** Also affects: libfprint (Ubuntu Jammy)
Importance: Undecided
Status: New
** Also affects: libfprint (Ubuntu Noble)
Importance: High
St
The verification of the Stable Release Update for gnome-control-center
has completed successfully and the package is now being released to
-updates. Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that yo
Noble also has 1:45.0-1ubuntu3, with the same fix. This all started
before noble was released, hence the version collision, but I'm pretty
sure that throughout the devel cycle, noble will get a gnome-control-
center version bump, so no harm in releasing mantic with this version
now.
--
You receiv
The verification of the Stable Release Update for mutter has completed
successfully and the package is now being released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you encounter a r
This bug is ready for verification. Due to the status mantic was in when
the package was accepted, the tooling failed to add the template comment
to this bug, and add the tags, and I did all of that manually now.
** Tags added: verification-needed verification-needed-mantic
** Also affects: gnome
This bug is ready for verification. Due to the status mantic was in when
the package was accepted, the tooling failed to add the template comment
to this bug, and add the tags, and I did all of that manually now.
** Also affects: gnome-shell-extension-ubuntu-dock (Ubuntu Mantic)
Importance: Med
This bug is ready for verification. Due to the release status mantic was
in when the package was accepted, the tooling failed to add the template
comment to this bug, and add the tags, and I did all of that manually
now.
** Also affects: gnome-control-center (Ubuntu Mantic)
Importance: High
Hi Georgia, is this still pending an evince fix? Your PPA has an updated
evince package, but I don't think it was uploaded to unapproved yet,
without the recommends.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to evince in Ubuntu.
htt
Also, this but is missing the SRU template, in case the sssd upload I
mentioned in my previous comment is really addressing this bug.
--
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/18652
There is an sssd package in focal-unapproved that points at this bug,
with this d/changelog snippet:
* debian/patches: Backport patches atches to support properly GDM smartcard
login (LP: #1865226)
(sic)
But there is no sssd task in this bug.
I also don't see a gdm3 upload to focal unappro
Apparmor in jammy-proposed has the necessary changes, we just need a new
evince upload to jammy without the recommends then.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to evince in Ubuntu.
https://bugs.launchpad.net/bugs/1794064
Tit
The verification of the Stable Release Update for mutter has completed
successfully and the package is now being released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you encounter a r
The verification of the Stable Release Update for gnome-shell has
completed successfully and the package is now being released to
-updates. Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you encount
> (Except for the workrave extension but that was already broken when Ubuntu
> 23.04 was released and
> mentioned in every SRU since. I believed it's fixed in 23.10 so it needs to
> be SRU'd.)
https://bugs.launchpad.net/ubuntu/+source/workrave/+bug/2017302 I suppose, and
https://bugs.launchpa
The verification of the Stable Release Update for gnome-control-center
has completed successfully and the package is now being released to
-updates. Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that yo
Hello Fabio, or anyone else affected,
Accepted mutter into jammy-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/mutter/42.9-0ubuntu3
in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
https://wiki.u
Hello Daniel, or anyone else affected,
Accepted mutter into jammy-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/mutter/42.9-0ubuntu3
in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
https://wiki.
Hello Ionut, or anyone else affected,
Accepted mutter into jammy-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/mutter/42.9-0ubuntu3
in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
https://wiki.u
In the test plan, can you also please confirm it keeps working with the
current and upcoming HWE kernels for jammy?
** Changed in: mutter (Ubuntu Jammy)
Status: In Progress => Fix Committed
** Tags added: verification-needed verification-needed-jammy
--
You received this bug notification
Looks like we get this if evince is update, apparmor is not, and a link
in a pdf is clicked:
Jul 06 18:36:59 j-evince kernel: audit: type=1400
audit(1688668619.304:78): apparmor="DENIED" operation="exec"
info="profile transition not found" error=-13 profile="/usr/bin/evince"
name="/usr/bin/snap" p
> Do we need evince to be reuploaded for jammy there since the previous
upload was rejected by Steve?
I'm trying to see what type of error we get if we load a profile with
such a rule and the target profile does not exist:
/{,snap/core/[0-9]*/,snap/snapd/[0-9]*/}usr/bin/snap mrCx ->
snap_browse
The verification of the Stable Release Update for apparmor has completed
successfully and the package is now being released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you encounter a
The verification of the Stable Release Update for mutter has completed
successfully and the package is now being released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you encounter a r
The verification of the Stable Release Update for mutter has completed
successfully and the package is now being released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you encounter a r
It's my understanding that this should be released together with gnome-
shell 42.9-0ubuntu2 which is currently in jammy-proposed.
gnome-shell 42.9 is https://bugs.launchpad.net/ubuntu/+source/gnome-
shell/+bug/2023913 and has been in jammy-proposed for 5 days, and is
still pending verification.
-
It's my understanding that this should be released together with gnome-
shell 42.9-0ubuntu2 which is currently in jammy-proposed.
gnome-shell 42.9 is https://bugs.launchpad.net/ubuntu/+source/gnome-
shell/+bug/2023913 and has been in jammy-proposed for 5 days, and is
still pending verification.
-
** Description changed:
Impact
--
There is a new bugfix release in the stable 42 series.
https://gitlab.gnome.org/GNOME/mutter/-/blob/42.9/NEWS
The overall GNOME project considers GNOME 42 to be end of life now and
there are no more scheduled releases for mutter 42 after 42.9
evince and apparmor for lunar should be released together to fix this
bug, but there is still a DEP8 failure that needs clearing under
apparmor: libreoffice/armhf
https://ubuntu-archive-team.ubuntu.com/proposed-
migration/lunar/update_excuses.html#apparmor
It was retried a few times already, but
The verification of the Stable Release Update for gdm3 has completed
successfully and the package is now being released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you encounter a reg
Thanks for the lunar tests in comment #22, and also for confirming that
the problem you saw happened without this update. I think a separate
bug for that is appropriate, if you could please file one.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is
After some googling, maybe this is the fix?
https://gitlab.gnome.org/GNOME/gtk/-/merge_requests/5873
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to nautilus in Ubuntu.
https://bugs.launchpad.net/bugs/2022851
Title:
Inappropriate f
To illustrate this bug, in this video capture I:
- selected file3
- hit the delete key
- hit the F5 (refresh) key
** Attachment added: "deleted-file-3-and-refreshed.webm"
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/2022851/+attachment/5677929/+files/deleted-file-3-and-refreshed.we
> Marking verification-done-jammy. I'll verify lunar tomorrow.
Please note my request in comment #9 about a few extra test cases.
** Tags removed: verification-done-jammy
** Tags added: verification-needed-jammy
--
You received this bug notification because you are a member of Ubuntu
Desktop B
Hello Ghadi, or anyone else affected,
Accepted gdm3 into lunar-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/gdm3/44.0-1ubuntu2 in
a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
https://wiki.ubunt
Hello Ghadi, or anyone else affected,
Accepted gdm3 into jammy-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/gdm3/42.0-1ubuntu7.22.04.3 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
https://wi
Please include a "normal" test for gdm3 in the test case. Something like
testing that logins keep working after applying this update, a switch
between "init 3" and "init 5", and that user switching works (while
logged in as user A, with open apps, login as user B, launch an app, and
come back to us
It's particularly annoying if I have a maximized terminal window in one
monitor. Chrome on the monitor in its left "perturbs" the terminal
window, see the screenshot. It's like it's drawing beyond the window
limits, over the adjacent window.
The moment the terminal window that has the "corruption"
I disabled all extensions using gnome-extensions-app, logged out and
logged back in:
$ gsettings get org.gnome.shell enabled-extensions
@as []
andreas@nsnx2:~$
I don't know what `@as` is.
But I still see the same artifacts at the borders, and between monitors, as
before.
--
You rec
$ gsettings get org.gnome.shell enabled-extensions
['d...@rastersoft.com', 'ubuntu-d...@ubuntu.com', 'tiling-assist...@ubuntu.com']
--
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/20206
I filed https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2020674
about the above.
--
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/2020225
Title:
Update mutter to 44.1
To manage
Public bug reported:
I installed mutter 44.1 and gnome-shell 44.1 from proposed, and a few of
other related dependencies. I don't have everything at 44.1, I don't
know if we should expect more gnome-related updates in lunar-proposed.
For example, I have
gnome-shell-extension-prefs 44.1-0ubuntu1
Also happens with chromium (the snap).
--
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/2020225
Title:
Update mutter to 44.1
To manage notifications about this bug go to:
https://bug
Turns out I'm only seeing it with google-chrome. Tried firefox, and a
terminal, using the same reproducer, and it didn´t happen.
** Attachment added: "chrome-mutter-44.1.webm"
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2020225/+attachment/5675428/+files/chrome-mutter-44.1.webm
--
The artifact at the border also happens across monitors. The tall chrome
window on the right of the left monitor interferes with the windows
aligned to the left of the right monitor.
This happened immediately after updating mutter and gnome shell to 44.1,
it wasn't happening before.
--
You recei
I installed mutter 44.1 and gnome-shell 44.1 from proposed, and a few of
other related dependencies. I don't have everything at 44.1, I don't
know if we should expect more gnome-related updates in lunar-proposed.
For example, I have
gnome-shell-extension-prefs 44.1-0ubuntu1
but gnome-shell-extens
Hello Marcelo, or anyone else affected,
Accepted gnome-shell-extension-ubuntu-dock into jammy-proposed. The
package will build now and be available at
https://launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-
dock/72~ubuntu5.22.04.2 in a few hours, and then in the -proposed
repository.
P
Hello Marco, or anyone else affected,
Accepted gnome-shell-extension-ubuntu-dock into jammy-proposed. The
package will build now and be available at
https://launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-
dock/72~ubuntu5.22.04.2 in a few hours, and then in the -proposed
repository.
Ple
Hello Marco, or anyone else affected,
Accepted gnome-shell-extension-ubuntu-dock into lunar-proposed. The
package will build now and be available at
https://launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-
dock/79ubuntu2.23.04.1 in a few hours, and then in the -proposed
repository.
Plea
Is kinetic being skipped on purpose, or is it not affected?
--
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/2019751
Title:
Desktop area may get clipped to a small rectangle if t
This is still needing a kinetic verification.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to evolution in Ubuntu.
https://bugs.launchpad.net/bugs/1983794
Title:
Evolution not deleting autosave files
To manage notifications about t
The verification of the Stable Release Update for evolution-data-server
has completed successfully and the package is now being released to
-updates. Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that y
The verification of the Stable Release Update for evolution has
completed successfully and the package is now being released to
-updates. Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you encounter
The verification of the Stable Release Update for gdm3 has completed
successfully and the package is now being released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you encounter a reg
I verified the test results and am satisfied that they show the executed
planned test case, and that the results are correct.
Nice find, dannf! :)
The package built correctly in all architectures and Ubuntu releases it
was meant for.
There are no DEP8 regressions.
There is no SRU freeze ongoing
** Description changed:
[ Impact ]
Switching to a second user falls back to Wayland even when Xorg was
explicitly selected.
[ Test Plan ]
On an NVIDIA DGX Station (known to reliably reproduce the issue):
1. Start with a default Ubuntu 22.04 Desktop install
- 2. apt install dan
The verification of the Stable Release Update for glib2.0 has completed
successfully and the package is now being released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you encounter a
I verified that the test was executed according to the [test plan].
I understand kinetic is not part of this SRU. The reason wasn't
explained anywhere, but I'm assuming it's because it's a) ending support
soon; and/or b) this glib update is more useful for core22 snap and core
desktop deployments,
Hello Robert,
the [test plan] has very specific steps involving the calculator,
gsettings, and an expected result. Did you perform those specifically?
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to glib2.0 in Ubuntu.
https://bugs.lau
Hi Gunnar and others,
with Lunar just released, I'm going over the lunar unapproved queue to
pick out packages that should now become SRUs for lunar.
Could someone please add the SRU template to this bug's description, and
fill it out?
Since the package is in unapproved, and not proposed, I'm sw
Jaap, what's needed is a verification for kinetic. Please see the test
plan in the bug description at the very top, and try out the package
from proposed as outlined in comment #24.
And we also need a kinetic verification on
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1949200 which
Given comment #12, I'm adding a block-proposed tag to this bug. Is this
something we could use to improve the test plan of this package by any
chance? Since it seems to have introduced crashes on kinetic.
** Tags added: block-proposed-jammy
** Tags added: block-proposed-kinetic
--
You received
1 - 100 of 1004 matches
Mail list logo
