Hello Hector, or anyone else affected,
Accepted intel-gpu-tools into jammy-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/intel-gpu-
tools/1.26-2ubuntu0.1 in a few hours, and then in the -proposed
repository.
Please help us by testing this new packag
Hello Leonardo, or anyone else affected,
Accepted intel-gpu-tools into jammy-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/intel-gpu-
tools/1.26-2ubuntu0.1 in a few hours, and then in the -proposed
repository.
Please help us by testing this new pack
Hello Leonardo, or anyone else affected,
Accepted intel-gpu-tools into mantic-proposed. The package will build
now and be available at https://launchpad.net/ubuntu/+source/intel-gpu-
tools/1.27.1-1ubuntu0.1 in a few hours, and then in the -proposed
repository.
Please help us by testing this new p
This should be Fix Released for the development release, right?
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to intel-gpu-tools in Ubuntu.
https://bugs.launchpad.net/bugs/2061324
Title:
Error when re-building package from source
To manage not
@Sean
Thank you for the patch. This looks too big to review to me, although
other sponsors may disagree. So, though I don't usually work in the
desktop area, I disagree with your statement "Regression potential here
seems minimal". This might be why some other sponsors have been
unwilling to touch
** Tags added: regression-update
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-graphics-drivers-304 in Ubuntu.
https://bugs.launchpad.net/bugs/1639663
Title:
vdpau permissions incorrect in 304.132-0ubuntu0.16.04.2
To manage notificat
Alberto, what's the plan here please? With 34 people reporting a
regression, should this not be reverted?
** Tags added: regression-update
** Changed in: nvidia-graphics-drivers-304 (Ubuntu)
Importance: Undecided => Critical
--
You received this bug notification because you are a member of U
It looks like your backport also pulled in upstream commit
116cddba69b37246db564c1ddf772c0144c589f0. Was this intentional?
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-input-libinput in Ubuntu.
https://bugs.launchpad.net/bugs/1655
12.0.6-0ubuntu0 doesn't exist. Which package versions were tested?
12.0.6-0ubuntu0.16.04.1? 12.0.6-0ubuntu0.16.10.1? Something else?
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1652486
Title:
Which package versions were tested? 12.0.6-0ubuntu0.16.04.1?
12.0.6-0ubuntu0.16.10.1? Something else?
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1641017
Title:
Mesa 12.0.6 - multiple importa
13:17 sil2100, tjaalton: in bug 1639896, is there any thought
to testing users who are on AMD but not using Polaris?
13:17 bug 1639896 in xserver-xorg-video-amdgpu (Ubuntu Xenial)
"Backport support for AMD Polaris" [Undecided,Fix committed]
https://launchpad.net/bugs/1639896
13:17 We don't wan
13:19 rbasak: all such tests use pci-id's. this adds new to
support polaris
13:19 old radeons use -ati
13:20 this is for gcn1.0 and up iirc
13:20 I'm talking of "regression risk in case our understanding
is wrong", not "what is our understanding".
13:21 "code that detected" is in the drive
The verification of the Stable Release Update for xserver-xorg-video-
amdgpu has completed successfully and the package has now been 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 th
This has a couple of reverse dependency autopkgtest failures in Yakkety.
I have requested retries as it isn't clear to me if they are
intermittent or not.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/
** Bug watch added: github.com/pyca/pyopenssl/issues #542
https://github.com/pyca/pyopenssl/issues/542
** Also affects: pyopenssl via
https://github.com/pyca/pyopenssl/issues/542
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member of
Upstream pyopenssl consider this fixed in 16.2.0, which is in Zesty, so
marking Fix Released. 16.10 has 16.1.0, so the problem still exists in
Yakkety. To fix this in Yakkety, it may be sufficient to cherry-pick
https://github.com/pyca/pyopenssl/pull/552/commits/a84a52ceeb8deb602515ebf76d3de3ec0e24
Presumably this is also Won't Fix for the proposed SRUs then? Marking as
such and unsubscribing ~ubuntu-sponsors.
** Changed in: xserver-xorg-video-mga (Ubuntu Xenial)
Status: New => Won't Fix
** Changed in: xserver-xorg-video-mga (Ubuntu Yakkety)
Status: New => Won't Fix
--
You r
@TJ
Please could you explain what you tested and what the results were?
Please also confirm the package version of the package you tested.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-input-libinput in Ubuntu.
https://bugs.launch
The verification of the Stable Release Update for xserver-xorg-input-
libinput has completed successfully and the package has now been
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
> 13:47 Hi guys, anybody from Bug Control here can please switch
bug 1132736 xorg-lts-trusty from Confirmed to Won't Fix? Please see last
comment for rationale. Thanks!
Users may still want to upgrade from an EOL release to a supported
release though. Surely we should encourage this!
I think the
** Tags added: regression-update
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1735594
Title:
[regression] compiz crashes after Mesa upgrade
To manage notifications about this bug go to:
https
The verification of the Stable Release Update for libinput has completed
successfully and the package has now been 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 libinput has completed
successfully and the package has now been 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
Hello Martin, or anyone else affected,
Accepted nux into bionic-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/nux/4.0.8+18.04.20180613.5-0ubuntu1
in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
It seems to me that the most likely area of SRU regression would be an
accidental functional change in 50_check_unity_support in the case of a
user using a previous release. For SRU verification, in addition to the
test case, please could you also check that the previous release
correctly sets LIBG
Hello Martin, or anyone else affected,
Accepted nux into artful-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/nux/4.0.8+17.10.20180613.3-0ubuntu1
in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
Hello Martin, or anyone else affected,
Accepted nux into xenial-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/nux/4.0.8+16.04.20180613.1-0ubuntu1
in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
** Tags added: regression-update
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/1780664
Title:
Recent libgl-mesa graphics update prevents drop down list menu
appearing in apps like fire
This is in the SRU queue but it looks like the security pocket might be
a better target? I asked Timo to liase with the security team to get a
decision on that.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to libxkbcommon in Ubuntu.
https://bugs.
An upload of libxkbcommon to bionic-proposed has been rejected from the
upload queue for the following reason: "Please use the security
pocket/process or else explain why this is using the SRU process over
the security process in the SRU information provided in the bug.".
--
You received this bug
An upload of libxkbcommon to bionic-proposed has been rejected from the
upload queue for the following reason: "Please use the security
pocket/process or else explain why this is using the SRU process over
the security process in the SRU information provided in the bug.".
--
You received this bug
This needs Regression Potential SRU information completed please.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/1792932
Title:
Desktop fails to boot in vbox: Xorg assert failure: Xorg:
Please provide:
1. An explanation of the bug on users and justification for backporting
the fix to the stable release.
2. A discussion of how regressions are most likely to manifest, or may
manifest even if it is unlikely, as a result of this change.
3. The version in which this bug is fixed in
This SRU upload is missing SRU information. Please follow
https://wiki.ubuntu.com/StableReleaseUpdates#Procedure. Thanks!
** Changed in: mesa (Ubuntu Focal)
Status: Triaged => Incomplete
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to mes
Hello Jean-Baptiste, or anyone else affected,
Accepted mesa into focal-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/mesa/21.0.3-0ubuntu0.3~20.04.4 in a
few hours, and then in the -proposed repository.
Please help us by testing this new package. Se
Missing SRU information: no regression analysis (ie. "Where things go
wrong" formerly "Regression Potential").
Please follow https://wiki.ubuntu.com/StableReleaseUpdates#Procedure
properly.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-
An upload of ubuntu-drivers-common to focal-proposed has been rejected
from the upload queue for the following reason: "See
https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-
common/+bug/1957094/comments/12".
--
You received this bug notification because you are a member of Ubuntu-X,
which
An upload of nvidia-settings to impish-proposed has been rejected from
the upload queue for the following reason: "See
https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-
common/+bug/1957094/comments/12".
--
You received this bug notification because you are a member of Ubuntu-X,
which is s
An upload of nvidia-settings to focal-proposed has been rejected from
the upload queue for the following reason: "See
https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-
common/+bug/1957094/comments/12".
--
You received this bug notification because you are a member of Ubuntu-X,
which is su
An upload of ubuntu-drivers-common to impish-proposed has been rejected
from the upload queue for the following reason: "See
https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-
common/+bug/1957094/comments/12".
--
You received this bug notification because you are a member of Ubuntu-X,
whic
Hi Jeremy,
It's not your fault. This is something your sponsor is supposed to have
checked.
@Alberto
Please could you properly review this, make sure it meets SRU policy,
try to anticipate and answer any questions the SRU team might have in
advance, and then work with Jeremy to resubmit to the q
Hello Daniel, or anyone else affected,
Accepted xserver-xorg-video-ati into jammy-proposed. The package will
build now and be available at
https://launchpad.net/ubuntu/+source/xserver-xorg-video-
ati/1:19.1.0-2ubuntu1 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
Hello Łukasz, or anyone else affected,
Accepted xorg-server into focal-proposed. The package will build now and
be available at https://launchpad.net/ubuntu/+source/xorg-
server/2:1.20.11-1ubuntu1~20.04.2 in a few hours, and then in the
-proposed repository.
Please help us by testing this new pac
Hello Timo, or anyone else affected,
Accepted xorg-server into focal-proposed. The package will build now and
be available at https://launchpad.net/ubuntu/+source/xorg-
server/2:1.20.11-1ubuntu1~20.04.2 in a few hours, and then in the
-proposed repository.
Please help us by testing this new packa
Hello Łukasz, or anyone else affected,
Accepted xorg-server into hirsute-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/xorg-
server/2:1.20.11-1ubuntu1.1 in a few hours, and then in the -proposed
repository.
Please help us by testing this new package
What testing did you perform?
** Tags removed: verification-done verification-done-cosmic
** Tags added: verification-needed verification-needed-cosmic
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bu
If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-cosmic to verification-done-cosmic.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed
Accepting the fix into stable releases. Note that the fix only prevents
new breakages; existing affected users will not be unbroken without
rebooting (or rebooting X).
** Description changed:
-
(console-setup)
[Impact]
- * keyboard-configuration's postinst changes keyboard mode breaking
Hello David, or anyone else affected,
Accepted console-setup into disco-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/console-
setup/1.178ubuntu12.1 in a few hours, and then in the -proposed
repository.
Please help us by testing this new package. S
Hello David, or anyone else affected,
Accepted console-setup into cosmic-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/console-
setup/1.178ubuntu9.2 in a few hours, and then in the -proposed
repository.
Please help us by testing this new package. S
Hello David, or anyone else affected,
Accepted console-setup into bionic-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/console-
setup/1.178ubuntu2.9 in a few hours, and then in the -proposed
repository.
Please help us by testing this new package. S
** Package changed: openssh (Ubuntu) => xserver-xorg-video-intel
(Ubuntu)
** Summary changed:
- ssh X11 forwarding has screen issue with Java applications
+ Screen issue with Java applications
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xse
** Also affects: xserver-xorg-video-intel (Ubuntu Xenial)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-intel in Ubuntu.
https://bugs.launchpad.net/bugs/1568604
Title:
Mouse curs
> afaics, exynos.conf is now shipped in xserver-xorg-video-armsoc
package.
It's not in xserver-xorg-video-armsoc 0.0+git20121019+rebdf1e3-0ubuntu1,
which is current. I had to hardcode the driver name in a new
/etc/X11/xorg.conf file to make it work.
** Also affects: xf86-video-armsoc (Ubuntu)
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
/etc/X11/Xsession.d/90x11-common_ssh-agent is actually provided by
x11-common (source package xorg), and it makes sense to me for XDG
related code to stay in there anyway.
** Package changed: openssh (Ubuntu) => x
Unsubscribing ~ubuntu-sponsors as there is nothing left to sponsor.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to egl-wayland in Ubuntu.
https://bugs.launchpad.net/bugs/1965563
Title:
GNOME apps crash with "Protocol error" in NVIDIA Wayland
Hello Gunnar, or anyone else affected,
Accepted egl-wayland into jammy-proposed. The package will build now and
be available at https://launchpad.net/ubuntu/+source/egl-
wayland/1:1.1.9-1.1ubuntu0.1 in a few hours, and then in the -proposed
repository.
Please help us by testing this new package.
SRU review:
1) debian/patches/egl-wayland-retrieve-DRM-device-name-before-
acquiring-.patch is being modified for no good reason (at least, it
isn't documented) and the dep3 headers are being dropped. Please explain
or fix.
2) Not essential, but the expected package version string would be
1:1.1.
Alessandro informs me that this was caused by some combination of kernel
6.8.0 and a nvidia-driver-550 update, so tagging regression-update, and
I'll review the proposed fix next.
** Tags added: regression-update
--
You received this bug notification because you are a member of Ubuntu-X,
which i
Hello Dave, or anyone else affected,
Accepted mesa into noble-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/mesa/24.0.9-0ubuntu0.2
in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
https://wiki.ub
The final upload to Noble unapproved cherry-picks the required fixes
rather than bumping to 24.2, right? So this bug is presumably better
described for the actual problem being solved rather than one presumed
solution that is no longer the plan?
** Summary changed:
- [SRU] Mesa bump to 24.2 requi
The bug title is much better - thanks. The test plan you describe in
comment 15 is much better, but I think there are a couple of things
still needed, please. Since this is hardware specific, what matrix of
hardware are you intending to test? For example, if using ffmpeg, then
are you testing both
> Since the new package isn't in the archive yet, we have to install
these separately.
Please *do not* install these from a PPA for the purposes of SRU
verification. If this is necessary then you're not really testing what
would land in the SRU, and there is no real justification for a hardware
en
This seems like an appropriate fix for future releases. However, is it
appropriate for SRU? Won't it change existing behaviour for existing
users?
> We happened to have some devices having Mic Mute key untranslated by
hwdb, typically we just add entries in hwdb to fix the issue
This seems like a
65 matches
Mail list logo
