Public bug reported:
# lsb_release -rd
Description:Ubuntu Trusty Tahr (development branch)
Release:14.04
Installed all relevant clang 3.4 packages including libclang-3.4-dev and
libclang1-3.4.
Expected a libclang.so with version suffix in /usr/lib/x86_64-linux-gnu/ and
plain in
** Branch linked: lp:~andreas-pokorny/mir/pixel-format-utils
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1256702
Title:
[enhancement] Allow a Mir nested server to have a transparent
background
The recently released lttng-modules 2.4 works.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1267652
Title:
lttng-modules-dkms 2.3.2-1: lttng-modules kernel module failed to
build
To manage
** Branch linked: lp:~andreas-pokorny/platform-api/opaque_by_default
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1227739
Title:
Mir continues to render background application surfaces even when
** Changed in: mir (Ubuntu)
Status: Triaged = In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1240400
Title:
dialer-app crashed with SIGSEGV in __GI___pthread_mutex_lock()
To
I can reproduce the issue easily too. But only when I start dialer-app
from the command line. Additionally dialer-app does not crash as far as
I can tell, it only terminates due to unity8 crashing.
** Also affects: unity8
Importance: Undecided
Status: New
--
You received this bug
just a short update - the crash does not occur when the application is
launched with upstart-launch-app
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1240400
Title:
dialer-app crashed with SIGSEGV
A fix for that bug would hide the issue here, but we should not crash in
that case.
When the incoming call is accepted another session is created for
another dialer-app which for some reason is not launched. The final
crash happens in unity-mir ApplicationManager::suspendApplication
** No longer affects: unity8
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1240400
Title:
dialer-app crashed with SIGSEGV in __GI___pthread_mutex_lock()
To manage notifications about this bug go
Status: New
** Changed in: unity-mir
Assignee: (unassigned) = Andreas Pokorny (andreas-pokorny)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1240400
Title:
dialer-app crashed with SIGSEGV
Public bug reported:
The cmake modules found in cmake 2.8.12.2-0ubuntu1 contain a qt moc
configuration template file that gets generated into the build directory of a
qt based project.
--- snip
set(AM_QT_MOC_EXECUTABLE @_qt_moc_executable@)
if(DEFINED ENV{DEB_BUILD_MULTIARCH} AND DEFINED
-compositor
Importance: Undecided
Status: New
** Changed in: unity-system-compositor
Assignee: (unassigned) = Andreas Pokorny (andreas-pokorny)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net
** Changed in: unity-system-compositor
Status: New = In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1297876
Title:
Screen turns on when a new session/surface appears
To manage
Just had a discussion in the mir team. Changing Nested constructor is a
simpler change.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1297876
Title:
Screen turns on when a new session/surface
.. simpler than making usc delay the focus setting until the display is
powered on again.
** No longer affects: unity-system-compositor
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1297876
Title:
There seem to be use cases where it makes sense - maybe not the power
mode changes.. The fix supplied is only a workaround. We are looking for
a cleaner solution..
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
The i915 driver seems to use a separate path for buffer allocation,
which is not patched for allocating buffers for fd. So mesa on mir
platform will not work.
** Also affects: mir
Importance: Undecided
Status: New
** No longer affects: mir
** Package changed: mir (Ubuntu) = mesa
--
Could not upload a crash report either - I am not also affected after applying
updates from utopic:
# gdb --version
GNU gdb (Ubuntu 7.7.1-0ubuntu1) 7.7.1
Copyright (C) 2014 Free Software Foundation, Inc.
...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
Bug seems to be unrelated to the gdb version it also happens for
7.7-0ubuntu3
and valgrind says:
Stack overflow in thread 1: can't grow stack to 0xffe801f48
==13825==
==13825== Process terminating with default action of signal 11 (SIGSEGV)
==13825== Access not within mapped region at address
I made some further attempts with older versions of mir_unit_tests.
Binaries built with g++-4.8.2-1ubuntu6 or maybe even before that work
while all binaries built with g++-4.8.2-4ubuntu1 have the issue.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
no need to change usc
** Changed in: powerd
Status: New = In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1367341
Title:
proximity sensor blanks screen when dialer is not active
no change needed so far communication of necessary powerd state changes
has to happen through telepathy-ofono
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1353560
Title:
Don't black screen when on
in: telepathy-ofono
Status: New = In Progress
** Changed in: telepathy-ofono
Assignee: (unassigned) = Andreas Pokorny (andreas-pokorny)
** Changed in: unity-system-compositor
Status: New = Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
Pokorny (andreas-pokorny)
** Changed in: unity-system-compositor (Ubuntu)
Status: New = Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1353560
Title:
Don't black screen when on call
Public bug reported:
Steps to reproduce - take
* flash ubuntu-touch/devel-proposed reviosion 245 or later to mako
* configure pin, developer mode, writable-image, network, ..
* sudo apt-get install unity8-autopilot
* sudo powerd-cli display on bright
* autopilot run -v unity8-autopilot unity8
** Branch unlinked: lp:~andreas-pokorny/powerd/blank-on-proximity-
powerstate
** Branch unlinked: lp:~andreas-pokorny/telepathy-ofono/control-
proximity-handling-in-powerd
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https
** Branch linked: lp:~andreas-pokorny/powerd/blank-on-proximity-
powerstate
** Branch linked: lp:~andreas-pokorny/telepathy-ofono/control-proximity-
handling-in-powerd
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https
The proposed solution will deactivate proximity sensor when a different
than the default output is used for a call. So the screen will stay on,
when someone interacts with the phone...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Which intel driver is meant in the spreadsheet?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1364003
Title:
[FFE] mesa 10.3
To manage notifications about this bug go to:
The assumption here is that the speaker ouput mode or a blue tooth evice
is used for the call?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1347913
Title:
Turn screen on when phone is moved during
Keyboard works for me within greeter and unity8-dash on the desktop.
Keyboard on side stage does not work.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1354564
Title:
Keyboard no longer works in
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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1275398
Title:
i915 driver/i945 hardware: Mir GL clients are rendered as black or
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
Bugs, which is subscribed to 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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1275398
Title:
i915 driver/i945 hardware: Mir GL clients are rendered as
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
Bugs, which is subscribed to Ubuntu.
Public bug reported:
Steps to reproducde:
1 start the ubuntu touch notes-app
2 start editing a note or add a new note
3 hit the text field with two or more fingers
ProblemType: Crash
DistroRelease: Ubuntu 14.10
Package: qmlscene 5.3.0-3ubuntu8
Uname: Linux 3.4.0-6-manta armv7l
ApportVersion:
Public bug reported:
Since image 188 or maybe before and also on 189 the SIM card is no
longer detected.
On first boot with 188 the Network Indicator line that used to show the
cellular status stayed empty.
For every further reboot and also after the update to 189 the line claims No
SIM
**
Same when updating to image 193.
but .. when I bootstrap the device instead Sim card is detected again.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1357023
Title:
No SIM is shown in network
** Also affects: telepathy-ofono
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1357023
Title:
No SIM is shown in network indicator on mako
To manage
Public bug reported:
It is not possible to enter long numbers into the dialog it seems to
stop after 20 digits. Long numbers are necessary for charging prepaid
sim cards.
It worked for me by dialing the number using ofono scripts.
** Affects: dialer-app (Ubuntu)
Importance: Undecided
Yes works now as expected. I can see all digits including the hash at
the end. Tested with a fake charging number, and it also gives me the
right service response.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
Make sure n10 is locked
swipe left from the right edge
enter the pin
error: unity8-dash is shown in the application spread.
expected: gestures never bypass the greeter
This happens only with the tablet interface on nexus 10, tested with
#289.
** Affects: unity8 (Ubuntu)
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]
Public bug reported:
I experienced this with mako and manta. After updating to #229 I tried
to configure a pin/passphrase to enable developer mode, but setting the
pin failed, and entering a password fails too.
Open System Settings - About this phone - Developer mode - Lock security -
4 digit
** Description changed:
I experienced this with mako and manta. After updating to #229 I tried
to configure a pin/passphrase to enable developer mode, but setting the
pin failed, and entering a password fails too.
Open System Settings - About this phone - Developer mode - Lock
Description sounds different - unity8 greeter did request a password in
case of mako (where I managed to lock myself out, because inactivity
timer disabled the screen while I was puzzled about system setting). In
manta going switching around between pin entry and no pin entry finally
resolve the
Apart from the strange errno in the logs above.. to allow mir to run on
vbox we need to add page flipping and the default implementation of
prime to the vbox drm driver:
http://www.virtualbox.org/svn/vbox/trunk/src/VBox/Additions/linux/drm/
page flipping has been adde here:
Public bug reported:
The factory default wlan ESSID of AVM routers is a name like: FRITZ!Box
Fon WLAN 7360 containing the brand and device name. For some time now
phablet-network fails because of the !, it used to work in the past.
$ phablet-network
Network file is
I cannot remember the exact message. I thought I could reproduce it
easily but after some trial and error that part of the issue
disappeared. I thought it was something with 'failed'.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Ok bootstrapped to our oldest still available image which does not require a
pin entry to lock phablet - 282
Then upgraded to the newest available image 232 on manta.
And tried the exact same steps again and it works now.
But unity8 greeter only requests the pin after rebooting another time?
image version 182 instead of 282 was meant in the last comment
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1366814
Title:
Configure lock pin or passphrase initially fails after upgrade to 229
To
** Also affects: powerd
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1367341
Title:
proximity sensor blanks screen when dialer is not active app
To
** Changed in: powerd
Assignee: (unassigned) = Andreas Pokorny (andreas-pokorny)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1367341
Title:
proximity sensor blanks screen when dialer
** Changed in: mir
Milestone: 0.8.0 = 0.7.3
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1350207
Title:
A frozen client can hang the whole server
To manage notifications about this bug go to:
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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1275398
Title:
i915
also on mako
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1380120
Title:
Manage Scopes - All Is Unusable
To manage notifications about this bug go to:
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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1391975
Title:
USC - mouse cursor on AMD graphics is drawing incorrectly
To manage
I tried on a N270 with 950GMA - older than N450 - the gpu is separate
but the feature level is similar so it also uses the i915 driver. ,Mir
demo shell works well. All software based clients work. eglplasma
crashes inside the dri i915 driver code with a segmentation fault within
glDrawArrays when
** Changed in: unity-system-compositor
Status: New = In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1376240
Title:
pressing power button should silence incoming call
To manage
** Branch linked: lp:~andreas-pokorny/unity-system-compositor/expose-
powerkey-state-and-screen-toggle-controller-interface
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1376240
Title:
pressing
Had the same issue today when upgrading from utopic to vivid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/985228
Title:
[USB-Audio - Logitech USB Headset, playback] Can not set USB headset
as
I doubt that the error is invalid, there seems to be an issue with
upgrading.
** Changed in: pulseaudio (Ubuntu)
Status: Invalid = New
** Summary changed:
- [USB-Audio - Logitech USB Headset, playback] Can not set USB headset as
active device for playback and recording in sound
The issue disappeared after removing ~/.config/pulse and rebooting
twice.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/985228
Title:
[USB-Audio - Logitech USB Headset, playback] Can not set USB
Does that happen after using certain applications or scopes? Or will
refuse to lock just after boot login?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1398020
Title:
Device is not getting auto
could not reproduce with vivid-proposed #39.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1398020
Title:
Device is not getting auto locked after 1 min
To manage notifications about this bug go
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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1353926
Title:
Xorg on haswell freezes on high
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
Public bug reported:
qtmultimedia plugins like libgstcamerabin.so or libgstmediaplayer.so link
against gstreamer-0.10:
ldd /usr/lib/x86_64-linux-gnu/qt5/plugins/mediaservice/libgstcamerabin.so
[]
libgstinterfaces-0.10.so.0 =
** Description changed:
I'm getting:
unity-system-compositor: symbol lookup error: /usr/lib/arm-linux-
gnueabihf/libmirserver.so.24: undefined symbol: _ZTIN7android7RefBaseE
$ system-image-cli -i
current build number: 13
device name: krillin
channel:
The last time I tested those systems the main blocker I saw was our mesa
package reporting a too low OpenGL version (the ES support would be fine
enough for QtQuick btw). After some digging it seemed that the GL
version is limited to 1.X, to avoid usage of certain full screen effects
in unity7.
Shall we differ between 'keep display on' due to a notification and
other cases. Like the media player requesting the screen to stay on
during playback.
I believe that all the other use cases involve user interaction, and
will probably involve the user touching the screen (-inactivity timeout
** Tags added: pm-fail
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1376240
Title:
[dialer] pressing power button should silence incoming call
To manage notifications about this bug go to:
** Changed in: mir
Milestone: 0.14.0 = 0.15.0
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1391976
Title:
Loading libmirclient.so twice leads to a segfault in libmirprotobuf.so
To manage
** Changed in: mir
Milestone: 0.14.0 = 0.15.0
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1270245
Title:
Backward frame jumps on mali (Nexus 10 krillin)
To manage notifications about this
** Changed in: mir/0.14
Milestone: 0.14.0 = 0.15.0
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1425307
Title:
[regression] Exception when running phablet-screenshot
[std::exception::what:
** Changed in: mir
Milestone: 0.14.0 = 0.15.0
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1455109
Title:
Using installed mir it is easy to break the system
To manage notifications about this
** Changed in: mir
Milestone: 0.14.0 = 0.15.0
** Changed in: mir
Milestone: 0.15.0 = None
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1460868
Title:
[regression] Mir demo servers don't
** Changed in: mir
Milestone: 0.14.0 = 0.15.0
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1373696
Title:
Android overlay mode ping-pongs constantly with touchspots or software
cursor
** Changed in: mir
Milestone: 0.14.0 = 0.15.0
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1397375
Title:
[enhancement] need fd (file descriptor) and dispatch function
To manage notifications
** Changed in: mir
Milestone: 0.14.0 = 0.15.0
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1454142
Title:
[regression] mirscreencast 0.13 and later gives error and exception
Public bug reported:
The pkg-config file is no longer present. It is still available in
vivid, though.
** Affects: gflags (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: mir (Ubuntu)
Assignee: (unassigned) = Andreas Pokorny (andreas-pokorny)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1458689
Title:
[vivid-overlay] input-stub.so fails to load
** Changed in: mir (Ubuntu)
Status: New = Confirmed
** Changed in: mir
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1458689
Title:
[vivid-overlay]
Has already been fixed in lp:mir.
** Changed in: mir
Status: Confirmed = Fix Committed
** Changed in: mir (Ubuntu)
Assignee: Andreas Pokorny (andreas-pokorny) = (unassigned)
** Changed in: mir
Assignee: Andreas Pokorny (andreas-pokorny) = (unassigned)
--
You received this bug
** Also affects: mir
Importance: Undecided
Status: New
** Changed in: mir
Milestone: None = 0.14.0
** Changed in: mir
Assignee: (unassigned) = Andreas Pokorny (andreas-pokorny)
** Branch linked: lp:~andreas-pokorny/mir/fix-1458689
--
You received this bug notification
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
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
** 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
Bugs, 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
The error message in the log above means that the server hit input-
stub.so while looking for graphics modules. It fails to load input-
stub.so since it does not explicitly link to libmirclient.so which
contains the given missing symbol. Additionally because qtmir is loaded
as a plugin the
could it be that you excluded mesa-kms from the build i.e. maybe by still
having 'mesa' inside MIR_PLATFORM (CMakeCache.txt).
Additionally the why is that log so short. It should mention the other drivers
found.. so even if the MIR_PLATFORM is wrong android platform binary should be
listed.
** Branch linked: lp:~afrantzis/mir/fix-1514391-mircookie-nettle-dev-
dependency
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1513792
Title:
mircookie requires nettle but libmircookie-dev doesn't
** 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
Another recent example now with the mir_client_basic:
https://jenkins.qa.ubuntu.com/job/mir-mediumtests-runner-
touch/7015/console
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1502896
Title:
CI
Look for lp:1506137 which also mentions the above scenario with
mir_client_basic.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1502896
Title:
CI segfault in mir-mediumtests-runner-mako in client
set to commited tsince we do have two other bugs to track similar
behavior.
** Changed in: mir
Status: Confirmed => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1502896
Title:
Why do we provide touch contact size as a single value? This is not a
value that we get directly from the device, instead it is calculated
from major/minor.. which we also provide.. and which are well defined
(but mostly badly scaled).
On that topic since at least nexus 10 provides an orientation
A fix for this issue was released in 0.9.0 and backported to 0.8.2:
https://bugs.launchpad.net/ubuntu/+source/unity-system-
compositor/+bug/1376324
** Changed in: mir (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
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.
1 - 100 of 270 matches
Mail list logo
