** Summary changed:
- Xmir: Fullscreen apps never go full screen
+ Xmir -rootless: Fullscreen apps never go full screen
** Description changed:
- Xmir: Fullscreen apps never go full screen.
+ Xmir -rootless: Fullscreen apps never go full screen.
E.g. Press F11 in Gnome Terminal or in Chrome
*** This bug is a duplicate of bug 1627311 ***
https://bugs.launchpad.net/bugs/1627311
OK, I've generalised bug 1627311. This appears to be the same issue.
** This bug has been marked a duplicate of bug 1627311
Xmir crashed with SIGABRT in send_message() from mir_buffer_stream_release()
-
** Summary changed:
- Xmir crashed with SIGABRT in send_message() from release_buffer_stream() from
FreeCursor()
+ Xmir crashed with SIGABRT in send_message() from mir_buffer_stream_release()
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg
*** This bug is a duplicate of bug 1627311 ***
https://bugs.launchpad.net/bugs/1627311
Oh here it is from the JournalErrors.txt. It appears Gnome Screensaver
failing to connect to the server (which is expected with Unity8 since it
will reject regular apps) has indirectly led to Xmir crashing.
*** This bug is a duplicate of bug 1627311 ***
https://bugs.launchpad.net/bugs/1627311
** This bug is no longer a duplicate of bug 1666514
Xmir crashed with SIGABRT [libmirclient crashed in send_message()]
** This bug has been marked a duplicate of bug 1627311
Xmir crashed with SIGABRT i
Public bug reported:
$ rendercheck -o add -t blend
...
Beginning Add blend test on b8g8r8a8
Add blend test error of 64. at (0, 0) --
RGBA
got: 0.00 0.00 0.00 1.00
expected: 1.00 1.00 1.00 1.00
src color: 0.00 0.00 0.00 1.00 (a8)
dst color: 1.00 1.00 1.00 1.00
src:
I'm not sure this is useful to assign to that milestone. The bug and the
fix are in the nouveau driver.
Although each GL client could work around it by moving all their GL
rendering to a single thread, we really shouldn't have to do that just
to support nouveau.
--
You received this bug notifica
*** This bug is a duplicate of bug 1560498 ***
https://bugs.launchpad.net/bugs/1560498
More recently I had (somewhere) suggested the Mir server interfaces for
testing the alpha channel are inadequate. Mir should be able to support
the case where an alpha channel exists but is unwanted (similar
The libpciaccess commit we need picked is:
https://cgit.freedesktop.org/xorg/lib/libpciaccess/commit/?id=099489b7917da44de57f3214425ea9b4a8f36482
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to libpciaccess in Ubuntu.
https://bugs.launchpad.net/b
In that case we'll actually have one Xmir process per app (which is
probably OK for resources).
That's more elegant, and more secure, than trying to hack Xmir to emit
multiple connections to the Mir server. And it works right now without
modifying code.
Also, it appears you can uniquely identify
If MirAL can't be fixed right now, that suggests we need to modify
libmirserver first, to separate input focus from the stacking order.
--
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/1625846
** Changed in: mir
Status: Fix Committed => In Progress
--
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/1211700
Title:
[gallium] EGL clients using a gallium driver (radeon, nouveau,
free
** Changed in: mir
Status: Fix Committed => In Progress
--
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/1665802
Title:
[regression] mir_demo_client_eglplasma results in 100% cpu and hardly
FWIW, the new EGL backend for Mir shouldn't suffer from this issue as it
respects the config selected by the app. Here's the PPA if someone wants
to try [1].
https://launchpad.net/~cemil-azizoglu/+archive/ubuntu/mesa-rs
[1] Note that the new EGL will NOT work with the old (existing) EGL apps
yet.
** Changed in: canonical-devices-system-image
Assignee: (unassigned) => Stephen M. Webb (bregma)
** Changed in: canonical-devices-system-image
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ub
** Also affects: canonical-devices-system-image
Importance: Undecided
Status: New
** Tags added: unity8-desktop
--
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/1625846
Title:
Xm
** Information type changed from Proprietary to Public
** Also affects: libpciaccess (Ubuntu)
Importance: Undecided
Status: New
** Changed in: libpciaccess (Ubuntu)
Assignee: (unassigned) => Robert Hooker (sarvatt)
** Changed in: libpciaccess (Ubuntu)
Status: New => In Prog
Probably also relevant: https://bugs.launchpad.net/mir/+bug/1560498
** Tags added: unity8-desktop
--
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/1670717
Title:
Unity8/mir working on VMware due
Nope, shared Xmir not a solution, we need each client to connect in a
separate session, to securely identify it. And there's security
considerations for that as well.
Not to mention gtk, for example, just probes available display servers
and uses the first one that works, which could very well res
Public bug reported:
Related to this bug (bug #1480755) - this is the issue preventing
unity8/mir working in VMware.
Bringing it out into its own issue to improve visibility.
Choice quotes from previous bug:
The problem is (annoyingly) that Mesa 10.5.9 on wily (Intel Haswell)
returns 7 compatib
Almost 2 months have passed since I posted the patch. Martin, if you are
still tracking this bug, does this patch work stable for you?
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-nouveau in Ubuntu.
https://bugs.launchpad.ne
** Tags removed: need-duplicate-check
--
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/1670665
Title:
package libglapi-mesa:amd64 12.0.6-0ubuntu0.16.10.1 failed to
install/upgrade: package libgl
Public bug reported:
During VLC install I had a conflict and the only valid solution to resolve it
and still install VLC would be to delete:
[REMOVE, DEPENDENCIES] libgl1-mesa-glx:i386 12.0.3-1ubuntu2
[REMOVE, DEPENDENCIES] libqt4-opengl:i386 4:4.8.7+dfsg-7ubuntu1
[REMOVE, DEPENDENCIES] libqtwebk
Fix committed into lp:mir at revision None, scheduled for release in
mir, milestone 1.0.0
** Changed in: mir
Status: In Progress => 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/b
Fix committed into lp:mir at revision 4072, scheduled for release in
mir, milestone 1.0.0
** Changed in: mir
Status: In Progress => 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/b
** Branch linked: lp:~vanvugt/mir/workaround-1665802
--
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/1665802
Title:
[regression] mir_demo_client_eglplasma results in 100% cpu and hardly
any upd
vboxvideo_drv was removed on purpose it seems, but seems that the
modeset driver can't enable glamor because of the separate EGL/GL libs?
btw, you probably can drop Provides: xorg-driver-video
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg
attached xorg log after installing xdiagnose
** Attachment added: "xorg.log"
https://bugs.launchpad.net/ubuntu/+source/virtualbox/+bug/1666059/+attachment/4832789/+files/xorg.log
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in
well, sounds like a vbox issue to me:
[18.775] (EE) Failed to load module "vboxvideo" (module does not
exist, 0)
which then results in:
[18.790] (EE) modeset(0): eglInitialize() failed
[18.790] (EE) modeset(0): glamor initialization failed
which probably causes the DM to fail, not s
** Summary changed:
- Main virtualbox window resizes itself 4 or 4 times - then no start
+ Main virtualbox window resizes itself 3 or 4 times - then no desktop start
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to mesa in Ubuntu.
https://bugs.la
mesa has been at 13.0.x for a while now.. xserver hasn't changed either
--
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/1666059
Title:
Main virtualbox window resizes itself 4 or 4 times -
and no logs saying otherwise
--
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/1666059
Title:
Main virtualbox window resizes itself 4 or 4 times - then no start
To manage notifications abou
32 matches
Mail list logo
