The verification of the Stable Release Update for xserver-xorg-video-
amdgpu 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 th
Hello Kai-Chuan, or anyone else affected,
Accepted xserver-xorg-video-amdgpu into jammy-proposed. The package will
build now and be available at
https://launchpad.net/ubuntu/+source/xserver-xorg-video-
amdgpu/22.0.0-1ubuntu0.2 in a few hours, and then in the -proposed
repository.
Please help us b
An upload of xserver-xorg-video-amdgpu to jammy-proposed has been
rejected from the upload queue for the following reason: "This looks
good, but you've included two slightly different versions of the patch?
Please re-upload with just one :)".
--
You received this bug notification because you are
The verification of the Stable Release Update for libinput 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
Hello Timo, or anyone else affected,
Accepted mesa into jammy-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/mesa/23.0.4-0ubuntu1~22.04.1 in a
few hours, and then in the -proposed repository.
Please help us by testing this new package. See
https://w
Hello Timo, or anyone else affected,
Accepted mesa into jammy-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/mesa/23.0.4-0ubuntu1~22.04.1 in a
few hours, and then in the -proposed repository.
Please help us by testing this new package. See
https://w
Hello Mustafa, 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.13-1ubuntu1~20.04.7 in a few hours, and then in the
-proposed repository.
Please help us by testing this new pa
The verification of the Stable Release Update for xorg-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 you encount
Looks like the DEP8 test is flaky; it has failed with previous non-xorg-
server packages as well, and I've just retried it and it has passed.
--
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/1
Hello errors.ubuntu.com, or anyone else affected,
Accepted xorg-server into jammy-proposed. The package will build now and
be available at https://launchpad.net/ubuntu/+source/xorg-
server/2:21.1.3-2ubuntu2.6 in a few hours, and then in the -proposed
repository.
Please help us by testing this new
Hello errors.ubuntu.com, or anyone else affected,
Accepted xorg-server into kinetic-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/xorg-
server/2:21.1.4-2ubuntu1.4 in a few hours, and then in the -proposed
repository.
Please help us by testing this n
llvm-toolchain-15 will presumably need to be promoted to main in jammy-
proposed/-updates, yes? I'm not familiar with the process of backporting
NEW packages into main; presumably because it's in main in lunar that'll
be ok, but I'd like to check with the MIR team that my assumption is
correct.
--
Right, but as far as the archive is concerned, libdrm-tegra0 itself is
unused :)
What code *does* use libdrm-tegra0, and how sure are we that it doesn't
use those symbols (even accidentally)?
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to mesa
spirv-headers is build-depended on by several packages; could we do
test-rebuilds of those as a part of verification, please.
--
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/1991761
Title:
Backpo
Hello Timo, or anyone else affected,
Accepted spirv-headers into jammy-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/spirv-
headers/1.6.1+1.3.216.0-1~ubuntu0.22.04.1 in a few hours, and then in
the -proposed repository.
Please help us by testing thi
I know it doesn't have any rdepends in the archive, but this includes a
libdrm-tegra0 ABI break without bumping SONAME; what sort of consumers
of libdrm-tegra0 are likely to exist? What risk mitigations could we
implement?
--
You received this bug notification because you are a member of Ubuntu-X
Hello Timo, or anyone else affected,
Accepted directx-headers into jammy-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/directx-
headers/1.606.4-1~ubuntu0.22.04.1 in a few hours, and then in the
-proposed repository.
Please help us by testing this ne
Hello errors.ubuntu.com, or anyone else affected,
Accepted mesa into jammy-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/mesa/22.0.5-0ubuntu0.2
in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
ht
Hello Kai-Chuan, or anyone else affected,
Accepted mesa into jammy-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/mesa/22.0.5-0ubuntu0.2
in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
https://wi
Is there a particular reason why we should take the PCI-ID removals?
They seem safe enough, though.
--
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/1998893
Title:
NV reverse prime HDMI has no out
An upload of mesa to jammy-proposed has been rejected from the upload
queue for the following reason: "Looks like there's unintentional
changes in src/mesa/formats.csv".
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to mesa in Ubuntu.
https://bugs
An upload of mesa to jammy-proposed has been rejected from the upload
queue for the following reason: "Looks like there's unintentional
changes in src/mesa/formats.csv".
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to mesa in Ubuntu.
https://bugs
The verification of the Stable Release Update for xorg-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 you encount
Hello Yao, or anyone else affected,
Accepted xorg-server into jammy-proposed. The package will build now and
be available at https://launchpad.net/ubuntu/+source/xorg-
server/2:21.1.3-2ubuntu2.2 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 xserver-xorg-video-amdgpu into jammy-proposed. The package will
build now and be available at
https://launchpad.net/ubuntu/+source/xserver-xorg-video-
amdgpu/22.0.0-1ubuntu0.1 in a few hours, and then in the -proposed
repository.
Please help us by
An upload of xserver-xorg-video-amdgpu to jammy-proposed has been
rejected from the upload queue for the following reason: "This looks
like an SRU-acceptable bug, but the uploaded package has weirdly-doubled
patches and FTBFS. Please fix and reupload a package that builds! ☺".
--
You received thi
Ok. So it seems that the bug *exists* in Focal, so now we just need to
verify that the bug is *fixed* by the proposed package.
@angie78 - as you seem to suffer from the bug, can you try to verify
that the proposed packages (from
https://bugs.launchpad.net/ubuntu/+source/libx11/+bug/1782984/comment
For the nvidia-settings upload, the new wording looks somewhat strange:
++ " in on-demand mode (only if nvidia version >=
450; "
++ "otherwise, the behavior will approach to "
++ "performance mode). This opt
Hello jeremyszu, or anyone else affected,
Accepted ubuntu-drivers-common into focal-proposed. The package will
build now and be available at
https://launchpad.net/ubuntu/+source/ubuntu-drivers-
common/1:0.9.0~0.20.04.5 in a few hours, and then in the -proposed
repository.
Please help us by testin
Hello jeremyszu, or anyone else affected,
Accepted ubuntu-drivers-common into impish-proposed. The package will
build now and be available at
https://launchpad.net/ubuntu/+source/ubuntu-drivers-common/1:0.9.2.3 in
a few hours, and then in the -proposed repository.
Please help us by testing this n
I've accepted this, but have amended the test plan to try and ensure
this doesn't change the behaviour on the -450 series drivers.
I'm not entirely sure what the "" check
should be. @Alberto, @Jeremy: Could you please replace that part of the
test-plan with the steps required to check that on-dema
Hello Timo, or anyone else affected,
Accepted libdrm into focal-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/libdrm/2.4.107-8ubuntu1~20.04.1 in
a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
http
Well, that's a compelling reason.
** Changed in: libdrm (Ubuntu Focal)
Status: Incomplete => Fix Committed
--
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/1949553
Title:
Backport packages
Hello Timo, 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.5 in a
few hours, and then in the -proposed repository.
Please help us by testing this new package. See
https:/
@Timo: I notice the libdrm backport drops the valgrind integration. I
know it's disabled in (at least) impish, but is there any particular
reason for it to be disabled in the focal backport?
It seems pretty unlikely that anyone would notice, but the diff required
to keep the valgrind annotations e
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.13-1ubuntu1~20.04.1 in a few hours, and then in the
-proposed repository.
Please help us by testing this new packa
Hello Bin, 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.13-1ubuntu1~20.04.1 in a few hours, and then in the
-proposed repository.
Please help us by testing this new packag
Has anyone tried PCManFM or Inkscape on focal? It seems that this update
doesn't fix GNOME Shell on focal, but *maybe* that's because Shell is
hitting a different bug?
If this can be verified to fix PCManFM, Inkscape, or something on focal
we can release it and open a new bug for GNOME Shell on Fo
The verification of the Stable Release Update for linux-firmware 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 enco
Hello Timo, 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.3 in a
few hours, and then in the -proposed repository.
Please help us by testing this new package. See
https:/
That seems like we should be able to extract a verification from the
errors.ubuntu.com results. Is it possible to query crashes with a
specific dependency version? Seeing no crash reports with libx11
2:1.6.9-2ubuntu1.3 would suggest this is fixed.
On the other hand,
https://bugs.launchpad.net/ubun
The verification of the Stable Release Update for nvidia-modprobe 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 enc
Thanks for that. @Bin - thanks for checking that these fixes are in
hirsute. Are they also in groovy? If they're not in groovy's libwacom
we'll also need an upload to groovy, so people who update from focal to
groovy don't lose this fix.
** Also affects: libwacom (Ubuntu Groovy)
Importance: Und
Hello Bin, or anyone else affected,
Accepted libwacom into focal-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/libwacom/1.3-2ubuntu2
in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
https://wiki.
The verification of the Stable Release Update for mesa 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
Hello AaronMa, or anyone else affected,
Accepted xorg-server into bionic-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/xorg-
server/2:1.19.6-1ubuntu4.7 in a few hours, and then in the -proposed
repository.
Please help us by testing this new package.
This bug was fixed in the package wayland - 1.18.0-2~exp1.1
---
wayland (1.18.0-2~exp1.1) unstable; urgency=medium
* Non-maintainer upload.
* Add missing dependency on libffi-dev (closes: #969284).
-- Julien Cristau Mon, 31 Aug 2020 10:10:12
+0200
** Changed in: wayland (Ubun
Hello Martin, or anyone else affected,
Accepted gdm3 into focal-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/gdm3/3.36.3-0ubuntu0.20.04.1 in a
few hours, and then in the -proposed repository.
Please help us by testing this new package. See
https:/
Public bug reported:
The version of wayland-client.pc in groovy has a Requires.private:
libffi, which means “pkg-config --static --libs wayland-client” requires
libffi.pc to be installed, but libwayland-dev does not depend on libffi-
dev.
ProblemType: Bug
DistroRelease: Ubuntu 20.10
Package: libw
The verification of the Stable Release Update for libglvnd 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
Hello Timo, or anyone else affected,
Accepted libglvnd into focal-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/libglvnd/1.3.1-1ubuntu0.20.04.1 in
a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
ht
The verification of the Stable Release Update for libdrm 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 xorg-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 you encount
Mutter actually *does* support 10bpc, just not with zwp_linux_dmabuf_v1.
It seems that mesa will incorrectly try to use formats advertised by
wl_drm but not zwp_linux_dmabuf_v1.
https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/4294 fixes
this for me.
** Changed in: mesa (Ubuntu)
St
Hello Timo, or anyone else affected,
Accepted mesa into bionic-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/mesa/19.0.8-0ubuntu0~18.04.3 in a
few hours, and then in the -proposed repository.
Please help us by testing this new package. See
https://
Hello Alkis, or anyone else affected,
Accepted mesa into bionic-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/mesa/19.0.8-0ubuntu0~18.04.2 in a
few hours, and then in the -proposed repository.
Please help us by testing this new package. See
https:/
Hello Timo, or anyone else affected,
Accepted mesa into bionic-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/mesa/19.0.8-0ubuntu0~18.04.2 in a
few hours, and then in the -proposed repository.
Please help us by testing this new package. See
https://
Hello Jeremy, or anyone else affected,
Accepted systemd into bionic-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/systemd/237-3ubuntu10.26 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
https:/
The verification of the Stable Release Update for mesa 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 reg
Hello Timo, or anyone else affected,
Accepted mesa into disco-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/mesa/19.0.8-0ubuntu0~19.04.1 in a
few hours, and then in the -proposed repository.
Please help us by testing this new package. See
https://w
The verification of the Stable Release Update for mesa 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 reg
Oh, ignore the retracer. It's just complaining that the stacktrace is
from my -O0 nostrip build. The attached stacktrace is fully symbolic.
** Changed in: xorg-server (Ubuntu)
Status: Invalid => New
--
You received this bug notification because you are a member of Ubuntu-X,
which is subsc
** Information type changed from Private to Public
--
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/1742612
Title:
Xorg crashed with SIGABRT in glamor_make_current()
To manage notification
Hello Timo, or anyone else affected,
Accepted mesa into artful-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/mesa/17.2.4-0ubuntu1~17.10.1 in a
few hours, and then in the -proposed repository.
Please help us by testing this new package. See
https://
Hello Lawrence, or anyone else affected,
Accepted mesa into artful-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/mesa/17.2.4-0ubuntu1~17.10.1 in a
few hours, and then in the -proposed repository.
Please help us by testing this new package. See
http
Hello Timo, or anyone else affected,
Accepted mesa into artful-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/mesa/17.2.4-0ubuntu1~17.10.1 in a
few hours, and then in the -proposed repository.
Please help us by testing this new package. See
https://
It's certainly possible to log out, log in to an Xorg session, and then
log out again/reboot to switch to NVIDIA. *If* you know that's what you
need to do.
Since nvidia-settings silently fails *and* we default to Wayland if
possible users who don't know this is what you need to do will find it
ver
Public bug reported:
I've got an nvidia/intel hybrid laptop. In a Wayland session nvidia-
settings fails silently when started from the shell. When started from a
terminal, it prints:
ERROR: Unable to load info from any available system
and then quits.
ProblemType: Bug
DistroRelease: Ubuntu 17.
The verification of the Stable Release Update for libxfont 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 Timo, or anyone else affected,
Accepted mesa into zesty-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/mesa/17.0.7-0ubuntu0.17.04.1 in a
few hours, and then in the -proposed repository.
Please help us by testing this new package. See
https://w
So, the problem here is going to be the EGL platform detection - it's
failing to detect Mir, and is instead trying (and failing) to connect to
an X server.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net
Ah, OK. We've been arguing with different assumptions.
Symptom: Firefox's menus don't work
Bug: XMir's focus behaviour differs from a spec-compliant X11 window manager.
One solution here, which is what I've been suggesting, is to implement
spec-compliant focus behaviour in XMir.
But you're corre
So, specifically, in this paragraph:
“
In both cases the shell must not implicitly change the focus while the user is
interacting with Firefox, but Mir/Unity8 is doing just that. And the unfocus
event on the Firefox main window is tricking Firefox into closing the popup
(and menus) immediately.
I'm clearly communicating poorly, so I'll try again:
The X11 focus, and the Mir focus, do *not* need to be the same.
In fact, a stronger claim holds: X11 focus and Mir focus *cannot* be the
same unless we want to implement pieces of X11 window management in Mir.
This does not mean simply ignorin
Hm, that's correct. XMir *could* defer acting on focus lost until a
timeout or focus-gained event, but that would be a heuristic.
The “Locally Active focus model” is a fairly X11-specific thing. It's
from a time when applications were built in a one-X11-window-per-widget
fashion, and so a textbox
(The reason why bug 1671771 is not going to fix this is that Firefox¹
*may* set input focus to one of its subwindows, and will behave weirdly
if that doesn't work. You can't just set “no focus” on the Mir surface
corresponding to Firefox's subwindow and then delegate to Mir's input
focus.)
¹: And,
I think bug 1671771 is fundamentally the wrong solution (to this
problem; it does need to be fixed).
The problem here is that XMir is not behaving like a spec-compliant X11
window manager. Unless we want to require Mir servers to implement X11
window management, this is not something that we can d
Hello Timo, or anyone else affected,
Accepted xorg-server-lts-xenial into trusty-proposed. The package will
build now and be available at https://launchpad.net/ubuntu/+source/xorg-
server-lts-xenial/2:1.18.4-0ubuntu0.2~trusty1 in a few hours, and then
in the -proposed repository.
Please help us b
Hello Timo, or anyone else affected,
Accepted xorg-server-lts-xenial into trusty-proposed. The package will
build now and be available at https://launchpad.net/ubuntu/+source/xorg-
server-lts-xenial/2:1.18.4-0ubuntu0.2~trusty1 in a few hours, and then
in the -proposed repository.
Please help us b
Hello Alex, or anyone else affected,
Accepted xorg-server-lts-xenial into trusty-proposed. The package will
build now and be available at https://launchpad.net/ubuntu/+source/xorg-
server-lts-xenial/2:1.18.4-0ubuntu0.2~trusty1 in a few hours, and then
in the -proposed repository.
Please help us b
Hello Victor, or anyone else affected,
Accepted xorg-server-lts-xenial into trusty-proposed. The package will
build now and be available at https://launchpad.net/ubuntu/+source/xorg-
server-lts-xenial/2:1.18.4-0ubuntu0.2~trusty1 in a few hours, and then
in the -proposed repository.
Please help us
Hello Xinxiu, or anyone else affected,
Accepted xorg-server-lts-xenial into trusty-proposed. The package will
build now and be available at https://launchpad.net/ubuntu/+source/xorg-
server-lts-xenial/2:1.18.4-0ubuntu0.2~trusty1 in a few hours, and then
in the -proposed repository.
Please help us
Hello Albert, or anyone else affected,
Accepted xorg-server-lts-xenial into trusty-proposed. The package will
build now and be available at https://launchpad.net/ubuntu/+source/xorg-
server-lts-xenial/2:1.18.4-0ubuntu0.2~trusty1 in a few hours, and then
in the -proposed repository.
Please help us
Hello Daniel, or anyone else affected,
Accepted xorg-server-lts-xenial into trusty-proposed. The package will
build now and be available at https://launchpad.net/ubuntu/+source/xorg-
server-lts-xenial/2:1.18.4-0ubuntu0.2~trusty1 in a few hours, and then
in the -proposed repository.
Please help us
Hello Daniel, or anyone else affected,
Accepted xorg-server-lts-xenial into trusty-proposed. The package will
build now and be available at https://launchpad.net/ubuntu/+source/xorg-
server-lts-xenial/2:1.18.4-0ubuntu0.2~trusty1 in a few hours, and then
in the -proposed repository.
Please help us
Hello Daniel, or anyone else affected,
Accepted xorg-server-lts-xenial into trusty-proposed. The package will
build now and be available at https://launchpad.net/ubuntu/+source/xorg-
server-lts-xenial/2:1.18.4-0ubuntu0.2~trusty1 in a few hours, and then
in the -proposed repository.
Please help us
The verification of the Stable Release Update for xserver-xorg-video-
intel 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 tha
Not quite done - needs plumbing through nested platform, which needs
nested platform migration onto non-deprecated display configuration.
--
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/13935
So, migrating discussion from a bug marked as duplicate:
OK, there's a design discussion to be had here.
In these cases, mirout is correct - your display has exactly one mode it
can be driven at. X adds a whole bunch of fake “standard” modes, but
they're just that - fake. Selecting one of the fa
Hello Timo, or anyone else affected,
Accepted xorg-server into yakkety-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/xorg-
server/2:1.18.4-1ubuntu6.1 in a few hours, and then in the -proposed
repository.
Please help us by testing this new package.
Hello Timo, or anyone else affected,
Accepted xorg-server into xenial-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/xorg-
server/2:1.18.4-0ubuntu0.2 in a few hours, and then in the -proposed
repository.
Please help us by testing this new package. S
Urgh. Turns out that I had an xorg.conf that was just confusing enough
for Xorg to fail to load the radeon driver. Now that I've got rid of
that it autoloads radeon and everything is groovy.
** Changed in: xorg-server (Ubuntu)
Status: New => Invalid
--
You received this bug notification b
Public bug reported:
I have a rather strange setup, with an nvidia and AMD card, both with
connected displays. (Connected to the same monitors, in fact).
The AMD card is the EFI primary card, and is what drives the kernel
framebuffer. This is correct; it's the one that's plugged into both
monitor
Not an upstream bug; this is a semantic merge error when updating the
Mir EGL platform patch.
** Changed in: mesa (Ubuntu)
Status: Confirmed => In Progress
** Changed in: mesa (Ubuntu)
Assignee: (unassigned) => Chris Halse Rogers (raof)
--
You received this bug notification b
I'm +1 for Andreas' mir_surface_start_window_drag(MirEvent const*
initiator), -1 letting a client arbitrarily move their surfaces around.
This will be easier for GTK and Qt than mir_surface_move(), as this is
the behaviour already implemented by xdg-shell.
--
You received this bug notification b
There's no reason to provide pbuffers (and a number of platforms,
notably Wayland, do not). FBOs do the same thing, but better.
** Changed in: mesa (Ubuntu)
Status: New => Won't Fix
** Changed in: mir
Status: New => Won't Fix
** Changed in: mir (Ubuntu)
Status: New => Won't
What? The window *should* be realised on first map, which should happen
basically immediately (and is driven by the X11 client, not Mir).
--
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/15847
Hello Christopher, or anyone else affected,
Accepted xorg-server into xenial-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/xorg-
server/2:1.18.3-1ubuntu2.2 in a few hours, and then in the -proposed
repository.
Please help us by testing this new pack
Not wild about #if 0 debugging code making it into the SRU, but it *is*
small and dead.
--
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/1566487
Title:
Container apps should use same keyboa
>> My concern with adding cancellation behaviour is that there'll be no
existing client or toolkit that expects it, and we can't make it opt-in
(like the opt-in touch cancellation support).
>That's a good point but extra events are kind of opt-in already with
zero code change for most clients. If
1 - 100 of 1218 matches
Mail list logo
