For me I found much improved stability on client disconnection after
this fix:
https://git.launchpad.net/~xmir-team/xorg-
server/+git/xmir/commit/?id=9287786b58a90cf376c05692fe4d6d0712946337
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: fglrx-installer (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to fglrx-installer in Ubuntu.
Same with the AMD Radeon 6600M and 6700M Series, even with the newest
4.2-10 version.
--
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/1493888
Title:
FGLRX incompatible with kernel 4.2
Public bug reported:
Xmir using glamor on mako shows wrong colours.
Test case (after applying the fix for bug 1494240):
$ xlogo -fg orange -bg purple
shows blue on magenta.
Workaround:
$ Xmir -sw -damage
renders colours correctly.
** Affects: xorg-server (Ubuntu)
Importance: Undecided
Workaround at the moment: Still booting up with the 4.1.0-3 kernel
version.
--
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/1493888
Title:
FGLRX incompatible with kernel 4.2
To
** Tags added: xmir
--
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/1494240
Title:
Xmir crashes immediately on startup using glamor on Nexus4
To manage notifications about this bug go
** Tags added: xmir
--
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/1493625
Title:
Fails to generate texture when running zenity on Nexus 4
To manage notifications about this bug go to:
It works fine with nvidia-355.
** 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/1494488
Title:
Xorg crashed with SIGABRT in
** Tags added: mako
--
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/1493596
Title:
Glamor chooses texture format that don't work on Nexus 4
To manage notifications about this bug go to:
** Tags added: mako
--
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/1493625
Title:
Fails to generate texture when running zenity on Nexus 4
To manage notifications about this bug go to:
** Tags added: mako
--
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/1494240
Title:
Xmir crashes immediately on startup using glamor on Nexus4
To manage notifications about this bug go
As far as I can tell "-rootless" mode actually is not implemented yet. I
can't make it crash but I can see that it mistakenly maps each X Window
(some of which could be menus or even individual widgets like in xedit)
to separate Mir surfaces. If we're going to continue on this path then
Mir needs
This behaviour is still present with kernel 4.2.0-7-generic - when an
external display is connected the desktop becomes incorrect
tiled/scaled, and the displays rapidly (~10 Hz) flicker.
Having the external display (Apple Cinema 27) plugged in during boot is
no longer a reliable workaround.
** Tags added: mako
--
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/1494634
Title:
Xmir using glamor on mako shows wrong colours
To manage notifications about this bug go to:
Also, each compositor (including QtMir) would need to be modified to
support subsurface placement for rootless to work.
--
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/1472097
Title:
XMir
** Tags removed: need-duplicate-check
--
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/1494915
Title:
fglrx-core 2:15.200-0ubuntu4.2: fglrx-core kernel module failed to
build
To
Public bug reported:
i report and came with normal update of kernel from 27 to 28, but even
before reboot with install(update manager?)my system got broken,and have
broken package,even i try SMART type of upgrade,
so i coose to report as new ,but i know this was very popular bug in
aug/2015
** Branch linked: lp:~equinox-i/xfce4-volumed-pulse/add-support-for-mic-
mute
** Branch unlinked: lp:~equinox-i/xfce4-volumed-pulse/add-support-for-
mic-mute
** Branch linked: lp:~equinox-i/xfce4-volumed-pulse/add-support-for-mic-
mute
** Branch unlinked:
** Tags removed: need-duplicate-check
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to fglrx-installer-updates in Ubuntu.
https://bugs.launchpad.net/bugs/1494932
Title:
fglrx-updates-core 2:15.200-0ubuntu4.2: fglrx-updates-core kernel
module
Public bug reported:
The DKMS (2.2.0.3-2ubuntu3) can't build module for fglrx-updates
(2:15.200-0ubuntu4.2) with kernel 4.0.9 on Ubuntu 15.04
ProblemType: Package
DistroRelease: Ubuntu 15.04
Package: fglrx-updates-core 2:15.200-0ubuntu4.2
ProcVersionSignature: Ubuntu 3.19.0-28.30-generic
Hello Shih-Yuan, or anyone else affected,
Accepted xorg-server-lts-vivid into trusty-proposed. The package will
build now and be available at https://launchpad.net/ubuntu/+source/xorg-
server-lts-vivid/2:1.17.1-0ubuntu3.1~trusty1 in a few hours, and then in
the -proposed repository.
Please help
Hello Shih-Yuan, or anyone else affected,
Accepted xorg-server into vivid-proposed. The package will build now and
be available at https://launchpad.net/ubuntu/+source/xorg-
server/2:1.17.1-0ubuntu3.1 in a few hours, and then in the -proposed
repository.
Please help us by testing this new
Hello Doug, or anyone else affected,
Accepted mesa-lts-vivid into trusty-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/mesa-lts-
vivid/10.5.9-2ubuntu1~trusty3 in a few hours, and then in the -proposed
repository.
Please help us by testing this new
** Branch linked: lp:ubuntu/trusty-proposed/mesa-lts-vivid
--
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/1424059
Title:
libosmesa6 conflicts with libglapi-mesa-lts-utopic
To manage
Still here on Wily
--
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/941826
Title:
dlopen(libGL.so) resolves to mesa rather than nvidia
To manage notifications about this bug go to:
** Tags removed: need-duplicate-check
--
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/1449319
Title:
package fglrx 2:14.501-0ubuntu1 failed to install/upgrade: package
fglrx is
** Tags removed: need-duplicate-check
--
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/1387424
Title:
package x11-common 1:7.7+7ubuntu2 failed to install/upgrade:
subprocess installed
** Changed in: xorg-lts-vivid (Ubuntu)
Status: Confirmed => Fix Released
--
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/1132736
Title:
Xorg fails to start after installing the Hardware
I've just updated another computer's HWE stack from Trusty (xserver-
xorg) to Vivid (xserver-xorg-lts-vivid) and can confirm again that this
bug has been fixed, starting from when you update to Vivid HWE stack.
The /etc/X11/X symlink is still deleted when one purges the remnants of
the previous
29 matches
Mail list logo
