New => Fix Released
** Changed in: x11proto-composite (Ubuntu)
Assignee: (unassigned) => Łukasz Zemczak (sil2100)
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to x11proto-dri2 in Ubuntu.
https://bugs.launchpad.net/bugs/1765662
Title:
$ remove-package -m "Obsolete; LP: #1765662" x11proto-bigreqs
Removing packages from bionic:
x11proto-bigreqs 1:1.1.2-1 in bionic
Comment: Obsolete; LP: #1765662
Remove [y|N]? y
1 package successfully removed.
** Changed in: x11proto-bigreqs (Ubuntu)
Assignee: (unassigned)
I'm on it.
** Changed in: x11proto-bigreqs (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to x11proto-dri2 in Ubuntu.
https://bugs.launchpad.net/bugs/1765662
Title:
Remove from the archive, xorgproto
Ok, this is a big change but I'd also prefer this happening before the
release instead of afterwards. Please perform some upgrade-testing on
the packages built in a PPA and if things look good, we can approve this
FFe.
Thanks!
--
You received this bug notification because you are a member of Ubu
What additional changes will have to be pulled in with 1.15rc in
comparison to the 1.14 we have in the archives? Any other features in
that version that need to be considered while reviewing this FFe?
Did you do a test-build of these changes in some PPA, along with testing
if upgrades from the pre
FFe approved.
** Changed in: libxcb (Ubuntu)
Status: New => Triaged
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xcb-proto in Ubuntu.
https://bugs.launchpad.net/bugs/1755717
Title:
FFE: xcb-proto/libxcb 1.13
To manage notifications
The verification of the Stable Release Update for libjogl2-java 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 encou
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
As per Timo's proposition, I'm publishing artful right now and after a
day or two I'll release xenial if no errors are reported for the artful
version. We want to play it safe as this version will be included in
16.04.4.
The libkscreen test suite is completely unreliable so ignoring that
failure.
Hello Timo, or anyone else affected,
Accepted mesa into xenial-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/mesa/17.2.8-0ubuntu0~16.04.1 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 artful-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/mesa/17.2.8-0ubuntu0~17.10.1 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 xserver-xorg-video-nouveau-hwe-16.04 into xenial-proposed. The
package will build now and be available at
https://launchpad.net/ubuntu/+source/xserver-xorg-video-nouveau-
hwe-16.04/1:1.0.15-2~16.04.1 in a few hours, and then in the -proposed
repository
Hello Timo, or anyone else affected,
Accepted xserver-xorg-video-ati-hwe-16.04 into xenial-proposed. The
package will build now and be available at
https://launchpad.net/ubuntu/+source/xserver-xorg-video-ati-
hwe-16.04/1:7.10.0-1~16.04.1 in a few hours, and then in the -proposed
repository.
Pleas
Hello Timo, or anyone else affected,
Accepted xserver-xorg-video-amdgpu-hwe-16.04 into xenial-proposed. The
package will build now and be available at
https://launchpad.net/ubuntu/+source/xserver-xorg-video-amdgpu-
hwe-16.04/1.4.0-1~16.04.1 in a few hours, and then in the -proposed
repository.
Pl
Hello Norbert, or anyone else affected,
Accepted libjogl2-java into xenial-proposed. The package will build now
and be available at
https://launchpad.net/ubuntu/+source/libjogl2-java/2.3.2+dfsg-
4ubuntu0.16.04.1 in a few hours, and then in the -proposed repository.
Please help us by testing this
Hello Norbert, or anyone else affected,
Accepted libjogl2-java into artful-proposed. The package will build now
and be available at
https://launchpad.net/ubuntu/+source/libjogl2-java/2.3.2+dfsg-
5ubuntu0.17.10.1 in a few hours, and then in the -proposed repository.
Please help us by testing this
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
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
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
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
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 xenial-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/mesa/17.2.4-0ubuntu1~16.04.3 in a
few hours, and then in the -proposed repository.
Please help us by testing this new package. See
https://
Hello Falk, or anyone else affected,
Accepted mesa into xenial-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/mesa/17.2.4-0ubuntu1~16.04.3 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 artful-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/mesa/17.2.4-0ubuntu1~17.10.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 artful-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/mesa/17.2.4-0ubuntu1~17.10.2 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.2 in a
few hours, and then in the -proposed repository.
Please help us by testing this new package. See
http
Hello Falk, 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.2 in a
few hours, and then in the -proposed repository.
Please help us by testing this new package. See
https://
Can we get this tested for artful as well?
--
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/1727401
Title:
Corruption on windowed 3D apps running on dGPU (Intel/AMD)
To manage notifications about
Hello Timo, or anyone else affected,
Accepted vulkan into xenial-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/vulkan/1.0.61.1+dfsg1-1ubuntu1~16.04.1
in a few hours, and then in the -proposed repository.
Please help us by testing this new package.
The verification of the Stable Release Update for libdrm 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 r
Lawrence/Florian: could one of you verify if the xenial-proposed mesa
package also fixes the issue on a xenial system? This is blocking the
mesa release for this series.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to mesa in Ubuntu.
https://bugs
Hello Seth, or anyone else affected,
Accepted nvidia-graphics-drivers-304 into xenial-proposed. The package
will build now and be available at https://launchpad.net/ubuntu/+source
/nvidia-graphics-drivers-304/304.135-0ubuntu0.16.04.2 in a few hours,
and then in the -proposed repository.
Please he
** Also affects: nvidia-graphics-drivers-304 (Ubuntu Xenial)
Importance: Undecided
Status: New
--
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/1724871
Title:
nvid
** Changed in: gdm3 (Ubuntu)
Importance: High => Critical
--
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/1723577
Title:
Artful won't start with Wayland activated (AMD?)
To manage notificatio
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
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
So what's the final status of the SRU? It was verified before but then
got held off. Does it need another re-test?
--
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/1687981
Title:
Backport packages
The verification of the Stable Release Update for libepoxy 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 Robert, or anyone else affected,
Accepted libepoxy into xenial-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/libepoxy/1.3.1-1ubuntu0.16.04.2 in
a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
Hello Robert, or anyone else affected,
Accepted libepoxy into zesty-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/libepoxy/1.3.1-1ubuntu1.17.04.2 in
a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
As part of a recent change in the Stable Release Update verification
policy we would like to inform that for a bug to be considered verified
for a given release a verification-done-$RELEASE tag needs to be added
to the bug where $RELEASE is the name of the series the package that was
tested (e.g. v
As part of a recent change in the Stable Release Update verification
policy we would like to inform that for a bug to be considered verified
for a given release a verification-done-$RELEASE tag needs to be added
to the bug where $RELEASE is the name of the series the package that was
tested (e.g. v
As part of a recent change in the Stable Release Update verification
policy we would like to inform that for a bug to be considered verified
for a given release a verification-done-$RELEASE tag needs to be added
to the bug where $RELEASE is the name of the series the package that was
tested (e.g. v
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.6-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
** Changed in: canonical-devices-system-image
Status: In Progress => Fix Released
--
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/1604851
Title:
Missing arm64 xmir binaries
To mana
Hello Timo, or anyone else affected,
Accepted xserver-xorg-video-amdgpu into xenial-proposed. The package
will build now and be available at https://launchpad.net/ubuntu/+source
/xserver-xorg-video-amdgpu/1.1.2-0ubuntu0.16.04.1 in a few hours, and
then in the -proposed repository.
Please help us
We have tested this change using xenial-overlay PPA for the phone and
the earlier issues with segmentation faults during tests is gone. Not
sure if there's anything else we need to test, didn't see an explicit
test-case here. But all in all the ubuntu-touch problems caused by this
bug are now gone.
The new xorg-server in -proposed successfully builds arm64 xmir
binaries, as expected. That's all we need for now.
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server
Thanks Timo! Sorry for interrupting your workflow. I coordinated it with
Robert and didn't know you already had any work ongoing. As long as
these changes are kept with the new version it's all ok with me.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscr
For the record, version from the development series:
https://launchpad.net/ubuntu/+source/xorg-server/2:1.18.4-1ubuntu2
--
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/1604851
Title:
Missi
Pushing simultaneously to both yakkety and xenial as the only way to
basically test this is to get the packages building (which I already
tested in a devirt PPA).
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
https://bugs
The change for this already landed in the xenial stable-phone-overlay
and the packages seem to look ok.
https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/stable-
phone-overlay/+sourcepub/6737397/+listing-archive-extra
--
You received this bug notification because you are a member of Ub
testing.
[Regression Potential]
No risk potential on existing platforms as it only involves packaging
changes enabling the new architecture for xmir. No source changes
required.
** Affects: canonical-devices-system-image
Importance: Undecided
Assignee: Łukasz Zemczak (sil2100
This bug was fixed in the package xserver-xorg-video-intel
2:2.99.917-1~exp1ubuntu2.3~overlay1 in https://launchpad.net/~ci-train-
ppa-service/+archive/ubuntu/stable-phone-overlay
---
xserver-xorg-video-intel (2:2.99.917-1~exp1ubuntu2.3~overlay1) vivid;
urgency=medium
[ Robert Ance
This bug was fixed in the package xserver-xorg-video-ati
1:7.5.0-1ubuntu2.1~overlay1 in https://launchpad.net/~ci-train-ppa-
service/+archive/ubuntu/stable-phone-overlay
---
xserver-xorg-video-ati (1:7.5.0-1ubuntu2.1~overlay1) vivid;
urgency=medium
[ Robert Ancell ]
* debian/patc
This bug was fixed in the package xserver-xorg-video-nouveau
1:1.0.11-1ubuntu2.1~overlay1 in https://launchpad.net/~ci-train-ppa-
service/+archive/ubuntu/stable-phone-overlay
---
xserver-xorg-video-nouveau (1:1.0.11-1ubuntu2.1~overlay1) vivid;
urgency=medium
[ Robert Ancell ]
* d
top next
and similar. Anyway, probably not top priority tasks.
** Also affects: xserver-xorg-video-intel (Ubuntu RTM)
Importance: Undecided
Status: New
** Changed in: xserver-xorg-video-intel (Ubuntu RTM)
Assignee: (unassigned) => Łukasz Zemczak (sil2100)
** Changed in: xserver-xorg-
** Branch unlinked: lp:~sil2100/compiz-core/fglrx_decor_fix
** Branch linked: lp:~sil2100/compiz/fix_770283
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to fglrx-installer in Ubuntu.
https://bugs.launchpad.net/bugs/770283
Title:
[fglrx]title
** Branch linked: lp:~sil2100/compiz-core/decor_bindtexture
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to fglrx-installer in Ubuntu.
https://bugs.launchpad.net/bugs/770283
Title:
[fglrx]title bar does not update on non-maximized windows
To
** Changed in: compiz (Ubuntu)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to fglrx-installer in Ubuntu.
https://bugs.launchpad.net/bugs/770283
Title:
[fglrx]title bar does not update on non-maximiz
** Description changed:
+ [Impact]
+ The following bug has high impact on all users using fglrx ATI drivers since
a long time. For every user using this proprietary driver the window
decorations will not update besides on window resize - which is very confusing,
since it's hard to know which wi
** Branch linked: lp:~sil2100/compiz/workaround_770283
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to fglrx-installer in Ubuntu.
https://bugs.launchpad.net/bugs/770283
Title:
[fglrx]title bar does not update on non-maximized windows
To manag
** Changed in: compiz (Ubuntu)
Assignee: (unassigned) => Łukasz Zemczak (sil2100)
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to fglrx-installer in Ubuntu.
https://bugs.launchpad.net/bugs/770283
Title:
[fglrx]title bar does not upd
I'm really glad that it works for everyone ;) I'm in the middle of
preparing paper-work for this fix to land into the nearest SRU. Since
it's only a temporary ugly workaround, there were more steps required
for it to get merged. But it's getting closer and closer. Also, I hope
having this issue fix
** Branch linked: lp:~sil2100/compiz-core/fglrx_decor_fix
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to fglrx-installer in Ubuntu.
https://bugs.launchpad.net/bugs/770283
Title:
[fglrx]title bar does not update on non-maximized windows
To ma
Ok, I woke up, tested my changes a bit and it doesn't seem to hang up anymore.
So I pushed the new version to my PPA, it should be published by now. Same as
before:
ppa:sil2100/ppa (precise only for now).
Please test it if it has any additional side-effects. Thanks!
I talked with Sam Spilsbury
I think I found the reason why my workaround had those side-effects that were
hanging up compiz, I'll test this more in the morning and push to my PPA for
everyone interested (if it works). It seems I didn't ungrab the X server when
there was a failure with rebinding the texture, which essential
Thanks for confirming! I also experienced hangs when using this
workaround, since as I mentioned - it might have some buggy side-
effects. But at least I know that this is what fixes the problem. I'll
do my best to provide a stable and 'good-looking' workaround as soon as
possible.
Thank you for y
404? Where? I hope you are using the instructions provided on
https://launchpad.net/~sil2100/+archive/ppa to adding this PPA?
Please remember that the compiz workaround might have some buggy side-
effects as well. I just would like to know if it's 'the right way' with
the bug fix.
--
You receive
For those that are experiencing the problem - I have uploaded a compiz
package with the temporary workaround to my local PPA. You can try
installing it and checking, if this workaround fixes the problem in
mention. Be aware that it's not the final solution, as including such
fixes in the main compi
I already have a simple workaround prepared for this bug, but exporting
it nicely is a bit more complicated, since its the decorator plugin that
I'm hacking. Just a bit more...
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to fglrx-installer in Ub
I have finally got into tracking this issue again. I did some tests and
it really seems like some driver weirdness: I modified the gtk-window-
decorator to send PropertyNotify events (complete redraws) on every
decoratation change (like title change or button change) and also the
decor plugin to sa
I'm suspecting the problem being in fglrx for the following reasons:
- It only happens for fglrx systems
- Compiz doesn't differentiate between small windows and big windows - the
Pixmap allocated is the same, just bigger in size. And both the Pixmap and the
corresponding texture are X and OpenGL
On a side-note - it seems multi-screen arrangements also affect this
problem. With dual-screen my decorations are refreshed correctly
regardless of window size. This really seems like an issue with fglrx -
I will conduct more experiments and send some questions to the ATI guys.
--
You received th
Thanks for confirming - I can also reproduce that changing the width
makes the decorations refrashable again. This is a very useful clue!
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to fglrx-installer in Ubuntu.
https://bugs.launchpad.net/bugs/7
Actually, I rechecked once again and once again I see that damage events
are correctly being sent for the decorations. Damage events are correct.
Even forcing NotifyProperty events every time does not help - the
decorations still don't get refreshed. The only way to force the
decorations to be actu
I'll try reproducing the problem on the open radeon driver later on too.
I checked again and It seems the problem lies somewhere else. Since it
seems even though draws are made to the pixmap by the gtk-window-
decorator, sometimes the changes aren't forwarded to compiz at all.
Damage events don't
** Branch linked: lp:~sil2100/compiz-core/fglrx_win_focus
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to fglrx-installer in Ubuntu.
https://bugs.launchpad.net/bugs/781384
Title:
active/inactive window decorations are wrong, do not update (onl
Ok, I have some leads as to this bug. For now it seems it's somehow
related to XChangeProperty() and PropertyNotify events in the decorator
codes (both in gwd and in compiz). There might be something that fglrx
does funny (or buggily) - but I'll know for sure tomorrow in the
morning.
--
You recei
Thanks for the info. Yes, I'm running fglrx and I can easily reproduce
the problem now. So I'm looking into possibilities of what is causing
this bug and to why it's only fglrx specific. This might take a bit
though.
As for LightDM, I'm still using GDM on my system, so I can't really help
here. Ne
** Changed in: compiz-core
Status: Confirmed => In Progress
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to fglrx-installer in Ubuntu.
https://bugs.launchpad.net/bugs/781384
Title:
active/inactive window decorations are wrong, do not up
Ok, I'm able to reproduce it now on my system. I'll try to find out why
it suddenly started working yesterday as well.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to fglrx-installer in Ubuntu.
https://bugs.launchpad.net/bugs/781384
Title:
act
-core revision 3013 (currently latest), so maybe it got fixed
by some of the ubuntu package patches?
** Changed in: compiz-core
Assignee: (unassigned) => Łukasz Zemczak (sil2100)
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to fglrx-instal
301 - 383 of 383 matches
Mail list logo
