The root cause for this problem was fixed upstream and applied in the
ubuntu packages in virtualbox and the kernel (lp:1669807)
--
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/1639745
Title:
Mir
** Bug watch added: GNOME Bug Tracker #768138
https://bugzilla.gnome.org/show_bug.cgi?id=768138
** Also affects: gtk via
https://bugzilla.gnome.org/show_bug.cgi?id=768138
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member of
Yes those branches are not related at all. Unless we expect each client
to create a fullscreen transparent/empty surface on every output.
Do we really want to support client side decorations?
If so we could have a look at xdg-shells way of doing it. When a window
drag should be started (because
This bug cannot be fixed in mir or qtubuntu - applications like unity8
and the applications using qtdeclarative will be slow within x11 and
mir. A backend for fixed function gpus, i.e using only GL1.5 would be
required to fix that..
** Also affects: qtdeclarative (Ubuntu)
Importance: Undecided
i915 does not have native shader support so mesa simulate that with
llvmpipe, using i915 only for blitting.. So a less demanding - (but also
not existing) fixed-function gl-1.x backend is the probably your best
chance to use that gpu with unity8.
--
You received this bug notification because you
Mesa in Ubuntu has a patch for i915 that disables OpenGL 2.0 but not
GLES 2,0. Thats why all mir clients and the unity8 session starts up..
since mirserver always use GL|ES.
Regular qt clients do the EGL init in a different path and they insist
on GL 2.0.
When you recompile mesa without that
** Changed in: mir
Status: New => Invalid
** Also affects: mesa (Ubuntu)
Importance: Undecided
Status: New
--
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:
Unity
We might not need to emit 'cancel' for keys being pressed while
switching away - it might be enough to treat vt switching as focus
gaining state change.. during which we have to inform the client about
all currently pressed keys and buttons..
--
You received this bug notification because you are
So the touchscreen tries to mimic a UI button that only sends a release
when the finger is released while inside the button area.
Since mir does not receive a release event from libinput we send repeat
events instead.
Should we define a cancel key press event type? That might be useful in
other
Wrt to the segmentation fault more details in
https://bugs.launchpad.net/mir/+bug/1526658
--
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/1526209
Title:
[regression] Clients of nested Mir
Yes i can also remember seeing that stacktrace when toying around with
our reload hack, to get mesa to find our symbols during egl display
detection. But I dont get that anymore on xenial with lp:mir or
lp:mir/0.18
--
You received this bug notification because you are a member of Ubuntu-X,
which
** Description changed:
The mx4 touch screen sends a BTN_TOOL_FINGER key event during the touch
down and up.. This interferes with position tracking inside libinput and
leads to invalid positions being reported and in some cases jumping of
the position just before the release of a touch
This bug is mostly relevant for the phone images. So whenever released I
would forward it to the current set of phone-overlays..
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to libinput in Ubuntu.
https://bugs.launchpad.net/bugs/1504168
Title:
Public bug reported:
The mx4 touch screen sends a BTN_TOOL_FINGER key event during the touch
down and up.. This interferes with position tracking inside libinput and
leads to invalid positions being reported and in some cases jumping of
the position just before the release of a touch contact.
Public bug reported:
Please make a new release of libevdev which also includes this patch for
krillin and vegetahd touchscreens:
http://cgit.freedesktop.org/libevdev/commit/?id=0028174c0bcefb1ea8923c9a7978a18568797dc4
** Affects: libevdev (Ubuntu)
Importance: Medium
Assignee: Robert
** Summary changed:
- please update to 0.99 / 1.0 of libinput
+ please update to 0.99 of libinput
** Summary changed:
- please update to 0.99 of libinput
+ add support for touchscree contact properties
--
You received this bug notification because you are a member of Ubuntu-X,
which is
** Description changed:
- libinput will release 1.0 this week (end of august 2015)
- http://cgit.freedesktop.org/wayland/libinput/log/
+ Mir needs access to touchscreen contact information (pressure, size,
+ orientation) to switch to libinput.
- Two vital patches for extended touchscreen
Public bug reported:
libinput will release 1.0 this week (end of august 2015)
http://cgit.freedesktop.org/wayland/libinput/log/
Two vital patches for extended touchscreen support are still missing:
http://lists.freedesktop.org/archives/wayland-devel/2015-August/023992.html
and
I can reproduce here locally, I have a fix.. cursor buffers now are
allowed to have arbitrary sizes, even when you request a different one..
** Changed in: mir
Assignee: Daniel van Vugt (vanvugt) = Andreas Pokorny (andreas-pokorny)
--
You received this bug notification because you
** Changed in: mir
Status: Confirmed = 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/1391975
Title:
USC - mouse cursor on AMD graphics is drawing incorrectly
To manage
Public bug reported:
There is a bugfix in 10.3.1 that will fix dma-buf handling in i915. So
we would like to see the newest minor release of mesa, which is 10.3.1
This will fix:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1275398 and
basically enable i915 devices to run mir.
[Impact]
It is in the 10.3. branch but a few commits after the 10.3 tags. So it
will be in 10.3.1.
Or we cherry pick that into 10.3?
--
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/1275398
Title:
i915
Which intel driver is meant in the spreadsheet?
--
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/1364003
Title:
[FFE] mesa 10.3
To manage notifications about this bug go to:
I think this failure is resolved with the updated mir platform patch and
bugfixes for i915 that have been sent upstream. Waiting for those to get
applied.
But the story does not end there. Now when running unity8-dash it fails
because mesa claims it only supports OpenGL 1.4. And that because of
Yes the stack trace is from the lightdm restart attempt, when I tried to
manually resolve the freeze.
--
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/1353926
Title:
Xorg on
needs a new mir platform patch and a one liner in 915 - so it seems
** Changed in: mesa (Ubuntu)
Assignee: (unassigned) = Andreas Pokorny (andreas-pokorny)
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to mesa in Ubuntu.
https
no change needed in mir
** Changed in: mir
Status: Triaged = Invalid
--
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/1275398
Title:
i915 driver/i945 hardware: Mir GL clients are rendered
needs a new mir platform patch and a one liner in 915 - so it seems
--
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/1275398
Title:
i915 driver/i945 hardware: Mir GL clients are rendered as black
just a mesa patch needed
** Changed in: mesa (Ubuntu)
Status: Confirmed = In Progress
** Changed in: linux (Ubuntu)
Status: Incomplete = Invalid
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to mesa in Ubuntu.
29 matches
Mail list logo