OK, thanks. I guess we can review the Jammy upload for now then on the
assumption that the Mantic upload won't have substantial changes until
it arrives in the queue.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to adsys in Ubuntu.
Currently the version of adsys in Mantic is 0.13.1ubuntu0.1, which is
lower than the version in Jammy Unapproved. What's your plan for Mantic
and/or users upgrading to Mantic please?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to adsys
The verification of the Stable Release Update for libreoffice 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
Thank you for working on this!
> Can I suggest ubuntu adds the debian delta as well as the ubuntu delta
patch as part of this sync & merge
Sorry, I don't follow. It looks like lp-2037569-skip-
bd_part_get_disk_spec.patch is part of the Ubuntu delta uploaded in
ubuntu1. A sync would drop this,
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-0ubuntu7
in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
Hello Kai-Heng, 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-0ubuntu7
in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
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-0ubuntu7
in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
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-0ubuntu7
in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
Rejecting from the Unapproved queues as Steve's request above has not
been addressed in over a month.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/2007702
Title:
[SRU] Deb
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
** Tags removed: verification-needed verification-needed-lunar
** Tags added: verification-done verification-done-lunar
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to transmission in Ubuntu.
https://bugs.launchpad.net/bugs/1973084
The removal of pptpd seems like something that should be release noted
to me, to give enquiring users somewhere to refer to.
** Also affects: ubuntu-release-notes
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Desktop
Packages,
The verification of the Stable Release Update for fonts-noto-color-emoji
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
Hello Steve, or anyone else affected,
Accepted ubuntu-settings into mantic-proposed. The package will build
now and be available at https://launchpad.net/ubuntu/+source/ubuntu-
settings/23.10.5.1 in a few hours, and then in the -proposed repository.
Please help us by testing this new package.
> It is unlikely but possible that the removal of the raspi binary
package from this source package will have inadvertently modified the
contents of the other remaining binary packages.
It might be worth running a binary debdiff for SRU verification then,
against the binary packages built in
Could someone also test the proposed fix for Lunar please, and report
the version tested? Otherwise releasing the fix for Jammy will result in
users being regressed if upgrading from Jammy to Lunar.
--
You received this bug notification because you are a member of Desktop
Packages, which is
I understand that qpdf in Noble will auto-sync when Noble opens.
** Changed in: qpdf (Ubuntu)
Status: Triaged => Fix Committed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to qpdf in Ubuntu.
The development release isn't open yet. We will need to sync across from
Debian when it opens. I am subscribed to this bug. Feel free to ping me
here if it's not been done in a few weeks.
** Changed in: qpdf (Ubuntu)
Status: Confirmed => Triaged
--
You received this bug notification
Thank you for the discussion. On balance I think what you've said makes
sense and it's not worth going further, but I think it's important to
have the trade-offs and choices documented here and that's done now.
--
You received this bug notification because you are a member of Desktop
Packages,
Hello Jay, or anyone else affected,
Accepted qpdf into lunar-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/qpdf/11.3.0-1ubuntu1
in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
Hello Jay, or anyone else affected,
Accepted qpdf into mantic-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/qpdf/11.5.0-1ubuntu1
in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
** Summary changed:
- SRU request: qpdf: data loss bug affecting versions 11.0.0 through 11.6.2
+ Data loss: qpdf discards the character in a binary string following an octal
quoted character with 1 or 2 digits
--
You received this bug notification because you are a member of Desktop
Packages,
> The patch doesn't include the new test cases, but it does include all
the old ones, which should demonstrate that there is no regression.
OK, but doesn't that just leave a problem behind for the next person who
tries to do an SRU to this package? Can't we just include the tests?
--
You
Thank you for contributing this fix!
Could you please expand on the Test Plan?
For manual testing, what are the exact steps that a user would perform,
what results would indicate that the bug is present, and what results
would indicate that the bug is fixed? For example, I don't see a command
to
The verification of the Stable Release Update for libreoffice 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
Thank you for the report. It would be smoothest if upstream released a
version with that change. I see that is requested in
https://gitlab.freedesktop.org/xdg/desktop-file-utils/-/issues/69
** Bug watch added: Debian Bug tracker #1041654
Thank you for the verification jenhsun!
There was also a plan to carry out testing as documented at
https://wiki.ubuntu.com/DesktopTeam/TestPlans/RemoteDesktop. See the
plan in the bug description above. Was this done? If so, please document
that and flip the tag back.
** Tags removed:
Thank you for the detailed analysis! So to make sure I understand: we
think adsys 0.9.2 was broken in Kinetic all along due to some problem at
the Kerberos end. You isolated this issue to outside adsys using
ldbsearch. This issue with ldbsearch does not occur with Jammy. So
you're confident that
Releasing this to Jammy is blocked on understanding what happened with
Kinetic. Not necessarily for the Kinetic release, but I think we should
understand what happened first in case it has implications for Jammy.
** Tags removed: verification-done-focal verification-done-jammy
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-0ubuntu2
in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
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-0ubuntu2
in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
Accepting into Jammy. I can see that the code changes appear already
present in lunar-proposed. Please could you confirm the status of the
fix in lunar-updates please, so we can avoid introducing a regression
when users upgrade?
On test plans, I see both this bug and the other one will be
The verification of the Stable Release Update for gjs 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 think it's OK to skip Kinetic if you don't want to proceed with it.
However, what are the implications of that severe regression for the QA
process for other releases? Are there QA gaps that could also affect a
release into Jammy, for example? Is it worth investigating the Kinetic
failure
The verification of the Stable Release Update for gnome-remote-desktop
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
Hello errors.ubuntu.com, or anyone else affected,
Accepted gnome-remote-desktop into jammy-proposed. The package will
build now and be available at
https://launchpad.net/ubuntu/+source/gnome-remote-
desktop/42.8-0ubuntu0.22.04.1 in a few hours, and then in the -proposed
repository.
Please help
(and it's a current topic in the ubuntu-release@ thread, so sort of
unresolved generally)
** Changed in: gnome-remote-desktop (Ubuntu Jammy)
Status: Incomplete => Fix Committed
** Tags added: verification-needed verification-needed-jammy
--
You received this bug notification because you
Hello Jeremy, or anyone else affected,
Accepted gnome-remote-desktop into jammy-proposed. The package will
build now and be available at
https://launchpad.net/ubuntu/+source/gnome-remote-
desktop/42.8-0ubuntu0.22.04.1 in a few hours, and then in the -proposed
repository.
Please help us by
I'm accepting as this question can be resolved after accept but before
release.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-remote-desktop in Ubuntu.
https://bugs.launchpad.net/bugs/2024240
Title:
[rdp]
Hello errors.ubuntu.com, or anyone else affected,
Accepted gnome-remote-desktop into jammy-proposed. The package will
build now and be available at
https://launchpad.net/ubuntu/+source/gnome-remote-
desktop/42.8-0ubuntu0.22.04.1 in a few hours, and then in the -proposed
repository.
Please help
Accepting, thanks. FTR, I think it's fine to have made improvements in
testing without a separate SRU bug. I have reviewed this change and
testing looks objectively better now.
** Changed in: gnome-remote-desktop (Ubuntu Jammy)
Status: In Progress => Fix Committed
** Tags added:
Hello Marco, or anyone else affected,
Accepted gjs into jammy-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/gjs/1.72.4-0ubuntu0.22.04.1 in a
few hours, and then in the -proposed repository.
Please help us by testing this new package. See
Hello Vladimir, or anyone else affected,
Accepted gjs into jammy-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/gjs/1.72.4-0ubuntu0.22.04.1 in a
few hours, and then in the -proposed repository.
Please help us by testing this new package. See
This looks good. Accepting, but subject to test plan review. See
https://discourse.ubuntu.com/t/scope-of-gnome-mru/18041/61?u=rbasak.
It's probably worth waiting on SRU verification until the test plan is
approved.
** Tags added: verification-needed verification-needed-jammy
--
You received
** Description changed:
[ Impact ]
That's the GNOME 42 stable update, including some fixes:
https://gitlab.gnome.org/GNOME/gjs/-/commits/1.72.4
[ Test case ]
The update is part of GNOME stable updates
https://wiki.ubuntu.com/StableReleaseUpdates/GNOME
- Gjs applications
An upload of jansson to jammy-proposed has been rejected from the upload
queue for the following reason: "Questions in
https://bugs.launchpad.net/ubuntu/+source/jansson/+bug/1987678 remain
unresolved after many months".
--
You received this bug notification because you are a member of Desktop
An upload of gnome-session to jammy-proposed has been rejected from the
upload queue for the following reason: "Questions in
https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1970424
oustanding for two months".
--
You received this bug notification because you are a member of Desktop
Thank you for the report. I noted this in
https://wiki.ubuntu.com/DesktopTeam/TestPlans/Mutter for future updates
that rely on the exception. Would it be appropriate to add this Test
Plan to future mutter updates that are based on the exception? If so,
please could you amend the wiki? Thanks!
--
Please also adjust the bug title to describe what the actual problem is
that you're fixing. Depending on what that is, it may be appropriate to
mark one bug as a dupe of the other (or not if they then describe
obviously separate things).
It's fine if they end up distinct but with a single Test
Just driving past while someone mentioned it and and trying to help this
along.
I suggest that you combine this with bug 2023215 and arrange a
comprehensive Test Plan which verifies that both issues are fixed as
well and that "normal" use cases (whatever they might be - I don't know)
aren't
I think this should probably be fixed in SRUs together with bug 2006110
and verified together. See my comment 6 there for further comment.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to appstream-glib in Ubuntu.
> Therefore, the crash is fixed even though there is still a remaining
bug.
Does this bug need reopening then, or a new bug filed? I leave that up
to you - setting Incomplete for now since that's better than Fix
Released and this being forgotten.
** Changed in: gnome-shell (Ubuntu Lunar)
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
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
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
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
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
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
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
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
I don't see a report so I presume this is OK to release?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/2015861
Title:
cursor does not track window when dragging between monitors with
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
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
> bug added by the previous revision
Tagging regression-update then, FTR, for future regression risk
analysis.
> That fix isn't relevant for releases after Focal; The necessary API
exists for Jammy onwards.
OK thanks. Then the correct bug task status for Jammy onwards is Invalid
or maybe Fix
Thanks. I agree and I've added a hint. This should hopefully clear the
flag on the next (Jammy) britney run.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to glib2.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1998267
Title:
glib not
In the meantime, please could you confirm what [sorry, that's ambiguous;
I mean *how*] you tested?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to glib2.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1998267
Title:
glib not aware of
Marking as Incomplete for the benefit of SRU reviewers. Please set back
once my questions are answered.
** Changed in: gnome-session (Ubuntu Jammy)
Status: In Progress => Incomplete
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to
> What Could Go Wrong
Adding a dependency can cause unintended side effects. For example,
users may now (directly or indirectly) pull in a package that conflicts
with something else they have installed. Have you looked for these? Does
the alternative provided definitely cover all cases?
> I
Could you please confirm that this fix isn't relevant for releases after
Focal - ie. that the necessary API exists in Jammy onwards? It may be
that you implied this already, but the bug status isn't set separately
and I can't find anything that states this unambiguously so I want to
make sure it
Hello Gunnar, or anyone else affected,
Accepted im-config into jammy-proposed. The package will build now and
be available at https://launchpad.net/ubuntu/+source/im-
config/0.50-2ubuntu22.04.1 in a few hours, and then in the -proposed
repository.
Please help us by testing this new package. See
Gunnar, I suspect you know more about this area than anyone else in
Ubuntu at the moment. So accepting on the basis that you think it makes
sense to make this change. I do agree that the bug is significant enough
for SRU.
But please could you expand the Test Plan to check for inadvertent
The verification of the Stable Release Update for libreoffice 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
Hello Aurora, or anyone else affected,
Accepted language-selector into jammy-proposed. The package will build
now and be available at https://launchpad.net/ubuntu/+source/language-
selector/0.219.1 in a few hours, and then in the -proposed repository.
Please help us by testing this new package.
Hello Aurora, or anyone else affected,
Accepted language-selector into kinetic-proposed. The package will build
now and be available at https://launchpad.net/ubuntu/+source/language-
selector/0.219.22.10.1 in a few hours, and then in the -proposed
repository.
Please help us by testing this new
Thank you for the updates! It looks like you responded appropriately to
all of my points, but I'd like to clarify one thing about version
numbers and Kinetic.
> If a user with an updated jammy (including this fix) upgrades to
kinetic, they will still have version 0.219.1 of the
Thank you for working on this!
What's the plan for Kinetic? Please see:
https://wiki.ubuntu.com/StableReleaseUpdates#Newer_Releases
If the goal is to make Sinhala text more readable on Ubuntu, please
could you make that an additional part of the Test Plan, instead of only
checking the order of
Thank you for the verification, and for leaving the note about glib2.0.
I think this package is fine to release, but I believe it's blocked on
the verification and autopkgtest failure analysis of glib2.0 in bug
1999098? Otherwise AIUI the package would become uninstallable?
--
You received this
> 3) the other minor changes in the new upstream release all seemed
conservative fixes addressing simple issues that seemed LTS worthy (some
even seemed to border on improving the security of some functions)
The catch is that these changes then need individual review and
consideration as to
OK, so to make sure I understand: nothing in the archive is directly
affected by this bug. But if a user builds their own thing with both
jansson and json-c, then the symbol conflict arises.
I think this is still fine in principle to SRU, but I would like your
out-of-archive component (vvas)
Possibly fixed in jammy-proposed with bug 1996148. If this fixes this
for you, please let us know.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1987631
Title:
Screencast only
Thanks. I accepted the upload but changed the bug reference to point to
bug 1996148 instead, since landing the revert shouldn't close this bug.
I'll reopen this bug since the revert reverts it.
** Changed in: pipewire (Ubuntu Jammy)
Status: Fix Released => Triaged
--
You received this
Public bug reported:
The SRU in bug 1985057 resulted in regression reports, including bug
1987631, currently marked as duplicates bug 1993912 and bug 1995358, and
possibly bug 1994928. It's clear that we need to revert, but I don't
want the metadata to close all of those regression bugs since it
Hello Robie, or anyone else affected,
Accepted pipewire into jammy-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/pipewire/0.3.48-1ubuntu3 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
@vanvugt what about pipewire in Jammy? Based on the duplicate report,
isn't this a regression in Jammy?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1987631
Title:
Screencast
regression-updates based on duplicate report
https://bugs.launchpad.net/ubuntu/+source/pipewire/+bug/1995358
** Tags added: regression-update
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
Is there a specific user story that you're looking to fix here? Eg.
crash reports in specific apps? What are you planning to rebuild to use
the newly versioned symbols? If possible, I'd like to see these verified
in proposed at the same time.
On the specific fix, there is quite a bit of noise
The test plan looks good - thanks!
On reviewing the patch itself, it looks quite complex. We took a look
upstream to see if there were any further fixes on the commit being
cherry-picked, and found at least one. See
Apparently upstream don't want us to cherry-pick the fix. It's probably
fine legally, but I don't think it's worth getting into that given that
I was only volunteering my time to try and help.
Setting Won't Fix since it seems that this is unlikely to get fixed in
Jammy then. I've not checked the
Upstream fix here:
https://github.com/josephwright/beamer/commit/f769f2ff60f3ade9b920f743ff65b46e5013758a
** Summary changed:
- Bug in beamer with fix in v3.66
+ beamer fails to handle the xcolor package options
** Also affects: texlive-base (Ubuntu Jammy)
Importance: Undecided
I'm not doubting that the revert was correct for upstream. But we have a
different context in a stable release, where users may be relying on
behaviours that upstream are at liberty to change in their main
development branch, but we are not in our stable releases. Further, we
can't just assume
This is definitely a bug that we want to fix in Focal. But is this
particular code change the correct way to do it?
Won't reverting this commit regress the fix that was introduced by the
commit in the first place? I think this needs a proper analysis of the
possible implications for unaffected
** Information type changed from Public to Public Security
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to policykit-1 in Ubuntu.
https://bugs.launchpad.net/bugs/1535768
Title:
pkexec tty hijacking via TIOCSTI ioctl
Status in
The verification of the Stable Release Update for xdg-utils 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
Hello Marco, or anyone else affected,
Accepted gnome-shell into jammy-proposed. The package will build now and
be available at https://launchpad.net/ubuntu/+source/gnome-
shell/42.4-0ubuntu0.22.04.1 in a few hours, and then in the -proposed
repository.
Please help us by testing this new package.
Hello Marco, or anyone else affected,
Accepted gnome-shell into jammy-proposed. The package will build now and
be available at https://launchpad.net/ubuntu/+source/gnome-
shell/42.4-0ubuntu0.22.04.1 in a few hours, and then in the -proposed
repository.
Please help us by testing this new package.
> Verify that they can all be enabled without showing an error.
IIRC the original request was to ensure that the extensions actually
work (ie. a basic smoke test), not just that they can be enabled without
error. I'll adjust your Test Plan accordingly.
Really the Test Plan should be approved
> Therefore the functionality of all other portals should be thoroughly
tested to ensure there are no functional regressions.
This seems sensible, so, please add this to the Test Plan.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to
Hello Olivier, or anyone else affected,
Accepted xdg-desktop-portal into focal-proposed. The package will build
now and be available at https://launchpad.net/ubuntu/+source/xdg-
desktop-portal/1.6.0-1ubuntu2 in a few hours, and then in the -proposed
repository.
Please help us by testing this new
Hello Olivier, or anyone else affected,
Accepted xdg-desktop-portal into jammy-proposed. The package will build
now and be available at https://launchpad.net/ubuntu/+source/xdg-
desktop-portal/1.14.4-1ubuntu2~22.04.1 in a few hours, and then in the
-proposed repository.
Please help us by testing
The verification of the Stable Release Update for xserver-xorg-video-ati
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
1 - 100 of 583 matches
Mail list logo
