Public bug reported:
New release 7.6.1 -> 7.7.0
Highlights:
* Option "TearFree" can now prevent tearing with rotation/reflection as
well (with Xorg >= 1.16).
* RandR CRTC transforms now work correctly (but for now still exhibit
tearing even with TearFree).
* The RandR 1.4 provider name is
** Package changed: xorg (Ubuntu) => unity (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1566957
Title:
Sloppy focus mode broken in 16.04 beta2
To manage notifications about this bug
[Expired for xorg (Ubuntu) because there has been no activity for 60
days.]
** Changed in: xorg (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
*** This bug is a duplicate of bug 1540774 ***
https://bugs.launchpad.net/bugs/1540774
** This bug has been marked a duplicate of bug 1540774
Light Display Manager fails to load
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to
** Bug watch removed: Debian Bug tracker #814682
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=814682
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-openchrome in Ubuntu.
https://bugs.launchpad.net/bugs/1540774
Title:
Did you test xserver-xorg-video-openchrome (1:0.3.3-1ubuntu1.1) in wily-
updates? It is not the same as the version in Debian. Only a small fix
was backported for Wily in that bug.
You can see the diff here: https://launchpadlibrarian.net/247897641
/xserver-xorg-video-
** Also affects: openchrome via
https://bugs.freedesktop.org/show_bug.cgi?id=94130
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-openchrome in Ubuntu.
Chromium seems to be very dependent on:
https://www.opengl.org/registry/specs/OML/glx_sync_control.txt
which Xmir doesn't implement yet.
I'm working on a solution to this in Mir that will allow it to be
implemented correctly in Xmir.
--
You received this bug notification because you are a
This bug was fixed in the package mesa - 11.2.0-1ubuntu1
---
mesa (11.2.0-1ubuntu1) xenial; urgency=medium
* Merge from debian. (LP: #1481832. #1548845)
mesa (11.2.0-1) experimental; urgency=medium
[ Andreas Boll ]
* control: Fix vdpau-va-driver Breaks/Replaces for
** Description changed:
On at least Ubuntu 15.10 and 16.04 with the radeon driver (version
7.5.0+git20150819-0ubuntu1 on 15.10, version 7.6.1-1ubuntu2 on 16.04)
trying to suspend or hibernate a Lenovo G50-80 with Intel HD Graphics
5500 (Broadwell GT2) and Advanced Micro Devices [AMD/ATI]
Adding more info:
The problem is that what's visible as the root window isn't really the
root window. It has some X client running on top of it, so it gets the
focus as the mouse enters it. I verified this by running xkill and
clicking the root window. It actually killed something, which
I'm testing it with the latest 16.04 update, running Unity.
I open a terminal, move the mouse into it, so it focuses and I can type
into the terminal. Then I move the mouse out of the window, to the root
window (no other window exists). I see the terminal lose focus, and if
I type anything, the
hrm, looks like I can reproduce this, which kinda is great
--
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/1566878
Title:
Alt-backtick regression
To manage notifications about this bug
ta, looks ok.
Override component to main
intel-vaapi-driver 1.7.0-1 in xenial: universe/libs -> main
i965-va-driver 1.7.0-1 in xenial amd64: universe/oldlibs/extra/100% -> main
i965-va-driver 1.7.0-1 in xenial i386: universe/oldlibs/extra/100% -> main
3 publications overridden.
** Changed in:
ta, looks ok.
Override component to main
vdpau-video 0.7.4-4 in xenial: universe/x11 -> main
vdpau-va-driver 0.7.4-4 in xenial amd64: universe/x11/optional/100% -> main
vdpau-va-driver 0.7.4-4 in xenial arm64: universe/x11/optional/100% -> main
vdpau-va-driver 0.7.4-4 in xenial armhf:
works here just fine
** Changed in: xorg (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1566957
Title:
Sloppy focus mode broken in 16.04 beta2
To
** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu)
** Changed in: xorg-server (Ubuntu)
Importance: Undecided => High
** Changed in: xorg-server (Ubuntu)
Status: New => Triaged
** Changed in: xorg-server (Ubuntu)
Assignee: (unassigned) => Timo Aaltonen (tjaalton)
--
You
** Also affects: gnome-shell via
https://bugzilla.gnome.org/show_bug.cgi?id=763531
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xdiagnose in Ubuntu.
https://bugs.launchpad.net/bugs/1483276
This needs to be fixed in xdiagnose's apport hook - ':' is an invalid
character in key names.
** Project changed: apport => xdiagnose (Ubuntu)
** Changed in: xdiagnose (Ubuntu)
Status: New => Triaged
--
You received this bug notification because you are a member of Ubuntu-X,
which is
You have been subscribed to a public bug:
I tried to use ubuntu-bug to report a problem with X and got an
AssertionError because ProblemReport wasn't expecting a key with colons
in it. I fixed this by using a regular expression.
Merge proposal coming up momentarily.
** Affects: xdiagnose
I just had a freeze using 4.0.3 so it's likely that the chance of
occurrence is just too low for me to properly bisect this if it truly is
a kernel problem. If someone knows whether this could be a kernel
problem or if it's likely to be something else, I would appreciate the
information.
--
You
I've some new info. I installed 15.10 in server mode, installed lubuntu-desktop
and ubuntu-desktop and started X without problem.
startx unity or startx both works.
But nor lightdm nor gdm start. lightdm crash and gdm gives a black
screen.
systemctl status lightdm.service
● lightdm.service -
I have reproduced it too, in 14.04 dock station (with display/s
connected) hangs the laptop and it doesn't even boot if it's docked. But
HDMI seems to work perfectly.
In 16.04 beta 2, connecting/disconnecting an HDMI display hangs the
laptop. When it's connected to the dock while it's running it
Public bug reported:
Switching to "sloppy" focus mode doesn't work and behaves like "mouse
mode".
I switched using unity-tweak-tool by going to Workspace Settings ->
Additional -> Focus mode. Both "mouse" and "sloppy" result in the same
behavior, with focus following mouse and not focusing on
I'll note that Alt-TAB still works.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1566878
Title:
Alt-backtick regression
To manage notifications about this bug go to:
I narrowed this down by doing a bisect dist-upgrade with disk snapshots.
I.e. take a snapshot, manually upgrade a few packages, reboot, test,
rinse, repeat. The only packages left are the three binary packages
mentioned in the bug report. With the snapshot before upgrading those
packages,
Public bug reported:
dist-upgrading to xorg-server (source package) 2:1.18.3-1ubuntu1 (binary
packages xserver-common, xserver-xorg-core, xvfb) introduces a
regression for Alt-backtick switching between windows of the same
application. Before the upgrade, Alt-backtick works by showing you the
** Package changed: gnome-terminal (Ubuntu) => xserver-xorg-video-intel
(Ubuntu)
** Also affects: linux (Ubuntu)
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.
** Changed in: linux (Ubuntu)
Status: New => Confirmed
--
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/1560524
Title:
Latitude E7470 crashes in DRM driver after
You have been subscribed to a public bug:
After attaching latitude E7470 laptop running
Linux sashas-work 4.2.0-30-generic #36-Ubuntu SMP Fri Feb 26 00:58:07 UTC 2016
x86_64 x86_64 x86_64 GNU/Linux
Distributor ID: Ubuntu
Description:Ubuntu 15.10
Release:15.10
Codename: wily
Looks like this has been fixed, indeed, in 16.04.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1523086
Title:
Ubuntu 15.10: GNOME Terminal window loses mouse cursor
To manage notifications
** Changed in: intel
Status: Confirmed => Fix Released
--
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/1234260
Title:
Package and use 'intel_l3_parity' binary
To manage
a quick review:
- all build-dependencies are now in main (including libva-dev)
- all runtime dependencies are in main
- actively maintained in Debian by a team
- no bugs open on LP
- no bugs open on Debian
- package is clean, uses dh
- license GPL-2+/LGPL-2+
- bug subscriber on Ubuntu set
a quick review:
- all build-dependencies in main
- all runtime dependencies in main
- actively maintained in Debian by a team
- one bug open on LP at the moment, unclear who to blame
- one bug open on Debian, more of a feature request
- package is clean, uses dh
- license Expat (MIT/X11?),
Note that although the debug files mention that the kernel was booted
with "intel_idle.max_cstate=1 " the issue reproduces with or without
this parameter.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
Another note:
The current dmesg reports an intel driver warning:
Apr 06 11:25:40 hostname kernel: WARNING: CPU: 1 PID: 6 at
/home/kernel/COD/linux/drivers/gpu/drm/i915/intel_pm.c:3572
skl_update_other_pipe_wm+0x16c/0x180 [i915]
followed by a stack trace. This is likely to be irrelevant to the
Public bug reported:
Running on a recently acquired Lenovo Yoga 260.
How to reproduce:
1. plug external screen
2. activate/configure monitor (either using GUI or xrandr)
3. set relative position of ext monitor to something else than the default
(e.g. above or below)
4. move cursor from laptop
No idea where the issue is, but it keeps on happening. Yesterday for
instance, I had to reboot again. When the system came up, I had a cursor
in lightdm, I logged in and the moment unity started, the cursor
disappeared and I had logout/login again to get it back.
--
You received this bug
Sorry, vmwgfx_dri.so actually belongs to Mesa.
binary package: libgl1-mesa-dri
source package: mesa
** Changed in: mir
Status: Invalid => New
** Changed in: mir (Ubuntu)
Status: Invalid => New
--
You received this bug notification because you are a member of Ubuntu-X,
which is
Digging into at least the latest 5 incidents, the crash is always from
vmwgfx_dri.so
So VMware's graphics driver is a problem. It should probably work better
than this already so I'm reluctant to make it a duplicate of bug
1118903.
** Summary changed:
- Unity8 crashed in
Note that a solution to bug 1118903 would allow us to avoid the
offending vmwgfx_dri.so here.
--
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/1560498
Title:
Unity8 using vmwgfx_dri.so crashed in
I promoted the two.
** Changed in: libset-scalar-perl (Ubuntu)
Status: Incomplete => Fix Released
** Changed in: libva (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to libset-scalar-perl in
** 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/1564955
Title:
Xorg crashed with SIGABRT
To manage notifications about this bug go to:
Public bug reported:
lsb_release -rd
Description:Ubuntu Xenial Xerus (development branch)
Release:16.04
apt-cache policy xorg
xorg:
Installé : 1:7.7+13ubuntu3
Candidat : 1:7.7+13ubuntu3
Table de version :
*** 1:7.7+13ubuntu3 500
500 http://archive.ubuntu.com/ubuntu
*** This bug is a duplicate of bug 1372967 ***
https://bugs.launchpad.net/bugs/1372967
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: xserver-xorg-input-synaptics (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because
I don't even understand the argument. Lets turn it around/right again:
Why not just dlopen libGL.so? Any application should be able to dlopen
libGL.so.
"libGL.so" is the library name everyone agrees to and everyone expects
to find, which is exactly why this file exists in the first place,
doesn't
Although the original reporter doesn't seem to get to the ASSERT. Two
other Pineview users have got that far. So I think safe to group all
these issues under "Pineview doesn't work".
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to mesa in
** Tags added: bq-feedback
--
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/1543351
Title:
Add on-screen-keyboard support for Xmir/Puritine apps
To manage notifications about this bug go
Note that the failing assertion is in qtubuntu ...
ASSERT: "eglDestroyContext(mEglDisplay, mEglContext) == EGL_TRUE" in
file ../../../src/ubuntumirclient/glcontext.cpp, line 71
** Package changed: unity8 (Ubuntu) => qtubuntu (Ubuntu)
** Summary changed:
- Unity 8/Mir doesn't load on Intel
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: mesa (Ubuntu)
Status: New => Confirmed
--
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/1549455
Title:
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: unity8 (Ubuntu)
Status: New => Confirmed
--
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/1549455
Title:
Keeping this bug open in the Mir project so we don't lose it. Looks like
a third Pineview user is reporting the same crash.
** Changed in: mir
Status: Invalid => Confirmed
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to mesa in Ubuntu.
52 matches
Mail list logo
